Why Search Traffic Dropped After a Website Redesign

The new website is live.

It looks better. It loads correctly. The forms work. Everyone approved it.

Then traffic starts falling.

Google Analytics shows fewer organic sessions. Search Console reports fewer clicks. Important pages no longer appear where they used to. Leads may also be slowing down.

Because the redesign happened at the same time, the redesign is the obvious suspect. That still leaves a much harder question:

What actually changed in a way that affected search traffic?

A redesign can alter far more than the visible design. It may also change:

• URLs
• Page content
• Navigation
• Internal links
• Canonical tags
• Indexing settings
• Structured data
• Page templates
• JavaScript rendering
• Site speed
• Analytics tracking
• Cookie consent behavior
• Hosting
• Domain settings
• Redirects
• XML sitemaps

Any one of these can affect the numbers you see after launch.

The fastest way to find the cause is to diagnose the shape of the drop before changing the website again.

First, confirm what actually dropped

“Traffic dropped” can describe several different problems.

You may be seeing a decline in:

• GA4 organic sessions
• Search Console clicks
• Search Console impressions
• Rankings for specific queries
• Indexed pages
• Leads or purchases
• Traffic to one important landing page
• Traffic across the entire website

These are related, but they do not prove the same thing.

Google Analytics measures activity on the website after its tracking code runs.

Google Search Console measures how the website performs in Google Search, including impressions and clicks.

If GA4 organic sessions dropped while Search Console clicks remained stable, tracking may have broken during the redesign.

If Search Console clicks and impressions both dropped, the website may have lost search visibility or demand may have changed.

If impressions stayed steady but clicks declined, the website may still be appearing in search while receiving a lower click-through rate.

If only a few pages declined, the problem may be tied to those pages rather than the entire redesign.

Google recommends comparing the affected periods and reviewing which pages, queries, countries, devices, and search types lost traffic before treating the decline as one sitewide issue.

Compare GA4 and Search Console before touching the site

This is the first comparison I would make.

Search Console stayed steady, but GA4 dropped

Investigate:

• Missing GA4 tags
• A missing Google Tag Manager container
• Tags excluded from certain templates
• Consent settings preventing tags from loading
• A new cookie banner
• Changed cross-domain tracking
• Internal traffic filters
• A different GA4 property
• Broken referral handling
• Tags firing only after an interaction
• Reporting changes around the launch date

Google Analytics and Search Console measure different parts of the visitor journey, so their totals will never match exactly. A major disagreement beginning on the redesign date can still be extremely useful evidence. Google specifically recommends moving into Search Console when organic traffic changes significantly because it provides the search-side data needed for further diagnosis.

GA4 and Search Console both dropped

The decline is more likely to involve actual search visibility, changed demand, or both.

Check:

• Pages and queries that lost the most traffic
• Indexing status
• URL changes
• Redirects
• Canonicals
• Removed content
• Internal linking
• Search intent
• Technical accessibility
• Performance by device and country
• The timing of Google search updates
• Seasonality and market demand

Search Console impressions stayed steady, but clicks dropped

Review:

• Average position
• Title changes
• Search snippets
• Which queries lost clicks
• Competitor results
• Search features appearing above the page
• Branded versus nonbranded searches
• Whether a different page now ranks
• Changes in customer demand

A click decline does not always mean the website disappeared from Google.

Clicks remained stable, but leads dropped

The SEO problem may be further down the workflow.

Investigate:

• Form submissions
• Phone tracking
• CRM integrations
• Booking embeds
• Ecommerce tracking
• Call-to-action changes
• Mobile usability
• Conversion events
• Lead notifications
• Sales routing

A redesigned website can preserve search traffic while reducing the number of visitors who become customers.

Mark the exact redesign launch date

Identify the date and approximate time the redesigned site became public.

Then create comparisons in both GA4 and Search Console.

Useful comparisons include:

• Four weeks before launch versus four weeks after
• The same days of the week
• The same period from the previous year
• The launch period versus a normal seasonal period
• The most recent complete weeks rather than partial weeks

Also mark other events that happened near the launch:

• Domain changes
• Hosting migrations
• Analytics updates
• Consent platform changes
• Advertising changes
• Seasonal demand changes
• Major promotions
• Google search updates
• Changes to business hours or services

The redesign may be part of the explanation without accounting for the entire decline.

Look at the shape of the traffic drop

The graph itself can provide clues.

Traffic dropped immediately on launch day

Prioritize:

• Analytics tracking
• noindex settings
• Robots directives
• URL changes
• Redirects
• Canonicals
• Server errors
• Domain configuration
• Template-wide problems

An immediate decline often points to something that changed across the site at launch.

Traffic declined gradually over several weeks

Prioritize:

• Content changes
• Internal linking
• Page intent
• Google replacing old URLs with new ones
• Crawl and indexing changes
• Performance regressions
• Competitor movement
• Search demand
• Algorithmic reevaluation

Google may need time to crawl and process redesigned pages, especially when the website’s URLs, templates, content, or internal relationships changed. The amount of time depends on the size of the website, the extent of the changes, server performance, crawl frequency, and the number of URLs involved.

Only certain sections dropped

Look for something shared by those pages:

• The same template
• The same content type
• A changed directory
• A missing navigation link
• A common canonical error
• A JavaScript component
• A category removed during the redesign
• A group of URLs without redirects
• An SEO plugin setting
• A particular mobile layout

Mobile traffic dropped more than desktop traffic

Review:

• Mobile navigation
• Responsive content
• Page speed
• Cookie banners
• Popups
• JavaScript errors
• Viewport problems
• Tap targets
• Content hidden on mobile
• Mobile form usability

One major page accounts for most of the decline

Start with that page.

A sitewide percentage can make the damage look broad when one high-traffic article or service page caused most of the loss.

Google recommends sorting affected pages by click difference so the URLs with the largest losses can be investigated first.

Confirm that the analytics tags survived the redesign

Tracking problems are common after a redesign because analytics code may be tied to the old theme, template, plugin, or consent configuration.

Check whether GA4 or Google Tag Manager loads on:

• The homepage
• Service pages
• Blog posts
• Landing pages
• Thank-you pages
• Product pages
• Checkout pages
• Embedded booking pages
• Mobile layouts
• Logged-out sessions

Use:

• GA4 Realtime
• GA4 DebugView
• Google Tag Assistant
• Browser developer tools
• Google Tag Manager preview mode
• Network requests in the browser
• The live HTML source

Do not test only the homepage.

The homepage may use one template while important landing pages use another.

Also confirm that the correct measurement ID or container ID is present. A developer may have copied a staging tag, created a new property, or omitted the production tracking code.

Check whether consent settings changed

A redesign often introduces a new cookie banner or consent platform.

That can affect reporting when:

• Analytics waits for consent
• The consent banner fails to load
• Consent Mode is configured incorrectly
• Returning users keep an old consent state
• Tags fire before consent on some pages and after consent on others
• The banner blocks tags indefinitely
• Different templates use different consent logic
• Consent settings vary by region

Some reduction in measured traffic may be legitimate when tracking becomes more privacy-conscious. A sudden, unusually large decline still deserves a configuration review.

Compare the redesign launch date with:

• The date the consent system was installed
• Consent rates
• Tag Assistant results
• GA4 Realtime activity
• Search Console clicks

When Search Console remains steady while GA4 drops, consent and measurement should move near the top of the investigation.

Check whether important URLs changed

Even small URL changes matter.

For example:

/services/web-design/

may become:

/website-design/

Or:

/blog/post-name/

may become:

/resources/post-name/

Other common changes include:

• Removing .html
• Adding or removing a trailing slash
• Changing capitalization
• Changing category folders
• Renaming service pages
• Consolidating several pages
• Moving content between subdomains
• Changing from HTTP to HTTPS
• Changing from www to non-www
• Moving to a new domain

Create a list of the old URLs and compare it with the new website.

Ideally, this list comes from:

• The old XML sitemap
• A crawl of the old website
• Search Console exports
• GA4 landing-page reports
• Backlink tools
• Server logs
• A website backup
• The Wayback Machine
• The original development environment

Every valuable old URL should have a documented outcome:

• It stayed the same
• It moved to a relevant new URL
• It was intentionally removed
• It was consolidated into another page
• It redirects elsewhere
• It currently returns an error

Audit the redirect map

When a URL changes, the old URL should generally redirect to the most relevant new location.

For example:

Old:
/services/seo-services/

New:
/seo/

The old URL should return a permanent redirect to the new SEO page.

Google recommends permanent server-side redirects when page URLs change. Its site-move guidance also emphasizes mapping old URLs to their new destinations and updating internal links to use the new URLs directly.

Check for:

• Old URLs returning 404 errors
• Redirects pointing to the homepage
• Redirect chains
• Redirect loops
• Temporary redirects used for permanent moves
• Redirects pointing to irrelevant pages
• HTTP URLs that fail to redirect
• www and non-www inconsistencies
• Query-string URLs being mishandled
• Redirects that work in a browser but return an unexpected status
• Plugins or server rules that conflict

Avoid sending every removed page to the homepage

A redirect should lead visitors to a relevant replacement.

If an old article about pool resurfacing redirects to a general homepage, the destination may provide little continuity for the visitor or search engine.

Better options include:

• A direct replacement page
• A closely related service page
• A consolidated guide containing the original topic
• A relevant category page when no closer match exists

Some old URLs may properly return a 404 or 410 response when the content was intentionally removed and no useful replacement exists.

Check whether the live site can be indexed

Staging websites are commonly hidden from search engines.

That protection may involve:

• A noindex directive
• A robots rule
• HTTP authentication
• A maintenance plugin
• Password protection
• Hosting-level privacy
• An SEO plugin setting
• WordPress’s “Discourage search engines” setting

Any of those settings can cause problems if carried onto the production site.

Inspect:

• The homepage
• Major service pages
• Popular blog posts
• Product or category pages
• Pages that lost traffic
• New pages replacing old URLs

In Search Console, use URL Inspection to review:

• Whether indexing is allowed
• The Google-selected canonical
• The last crawl
• The retrieved page
• The rendered page
• Any robots or indexing issues

Also check the live page source for:

<meta name="robots" content="noindex">

and review:

example.com/robots.txt

A robots rule can prevent crawling. A noindex directive can prevent a page from remaining in Google’s index. JavaScript should not be relied on to remove an initial noindex directive because Google may skip rendering after encountering that directive.

Review canonical tags

A canonical tells search engines which URL represents the preferred version of duplicate or very similar content.

Redesigns can introduce canonical problems when:

• Pages point to the staging domain
• Every page points to the homepage
• Service pages point to an older version
• HTTP canonicals remain after an HTTPS launch
• www and non-www versions conflict
• Pagination is canonicalized incorrectly
• Product variants point to the wrong product
• Templates output the same canonical everywhere
• Canonicals use URLs that redirect or return errors

For each important page, compare:

• The live URL
• The declared canonical
• The Google-selected canonical
• The sitemap URL
• The redirect destination
• Internal links pointing to the page

Google treats canonical declarations as signals rather than absolute commands. Redirects, sitemap inclusion, rel="canonical" declarations, internal links, and page similarity can all affect which URL Google ultimately selects.

Compare the old and new content

A redesigned page can retain the same URL and still lose traffic because its content changed substantially.

This often happens when a redesign replaces a detailed page with:

• A large hero image
• A short paragraph
• A few icon boxes
• An accordion
• A contact form
• A call-to-action section

The new page may look cleaner while answering fewer questions.

Compare the old and new versions of important landing pages.

Review:

• Title tag
• Meta description
• H1
• Subheadings
• Main copy
• Service details
• Geographic information
• Frequently asked questions
• Product information
• Supporting examples
• Image alt text
• Internal links
• Calls to action
• Structured data

Pay special attention to content that previously supported long-tail searches.

A page may keep ranking for its main service term while losing dozens of smaller queries that collectively produced meaningful traffic.

Look for pages that were removed or consolidated

Redesign projects often reduce the number of pages.

That can be appropriate, but the search value of each page should be evaluated first.

A removed page may have had:

• Organic traffic
• Backlinks
• Local relevance
• Rankings for a specific service
• Product information
• Referral traffic
• Years of search history
• Internal links from important pages
• A role in the customer journey

When several focused pages are condensed into one general page, the replacement may struggle to rank for every topic the old pages covered.

For example, a contractor may combine separate pages for:

• Kitchen remodeling
• Bathroom remodeling
• Cabinet installation
• Countertop replacement

into one page called “Our Services.”

The new page may mention each service briefly. Google now has less specific information for the individual searches.

Before restoring everything, identify which removed pages actually contributed traffic, rankings, backlinks, leads, or useful customer information.

Check whether the search intent changed

A redesign may preserve the topic while changing the page’s purpose.

An informational guide can become a short sales page.

A product category can become a visual gallery.

A detailed service page can become a general brand statement.

Google may then choose different pages for the queries that previously sent traffic.

Compare the redesigned page with the current search results.

Look at what Google appears to favor:

• Detailed guides
• Service pages
• Product pages
• Category pages
• Local businesses
• Videos
• Tools
• Forum discussions
• Comparison pages

The page should fulfill the type of need behind the search.

Review title tags and headings

Title tags and headings may be rewritten during a redesign to sound cleaner, shorter, or more creative.

For example:

Before:
Jacksonville Pool Resurfacing and Repair Services

After:
Bring Your Pool Back to Life

The new title may fit the visual design while providing less context to search engines and searchers.

Review whether important pages still clearly communicate:

• The service
• The product
• The location, when relevant
• The page’s purpose
• The specific problem addressed

Avoid stuffing every variation into the title. The title still needs to explain the page plainly.

Also confirm that templates have not:

• Removed the H1
• Added several competing H1s
• Turned visual headings into plain <div> elements
• Repeated the site name excessively
• Replaced descriptive headings with vague slogans
• Hidden important headings from the rendered output

Audit internal links

Redesigns frequently change the site’s navigation and internal linking structure.

A page that once received links from the homepage, main menu, service overview, footer, and related articles may now receive one link from a dropdown.

That changes how visitors and search engines reach the page.

Review whether important pages are still linked from:

• The primary navigation
• The homepage
• Relevant service pages
• Related blog posts
• Category pages
• Breadcrumbs
• The footer, where appropriate
• Product or collection pages
• Location pages

Also check the anchor text.

Descriptive links help clarify the relationship between pages.

For example:

Read our website migration checklist

provides more context than:

Click here

Update internal links to point directly to the final URLs rather than relying on redirects. Google includes this in its site-move recommendations.

Check whether pages became orphaned

An orphan page has no meaningful internal links pointing to it.

It may still appear in the XML sitemap and remain indexed, but the website provides very little context about its importance.

Compare:

• URLs in the XML sitemap
• URLs found by crawling the website
• URLs receiving Search Console impressions
• URLs receiving GA4 landing-page traffic

A sitemap URL that cannot be reached through normal site navigation deserves review.

Some pages may be intentionally isolated, such as paid campaign landing pages. Important organic landing pages should generally be connected to the rest of the website.

Review the XML sitemap

After a redesign, the sitemap should contain the preferred live URLs.

Check for:

• Old URLs
• Staging URLs
• Redirecting URLs
• 404 URLs
• Duplicate URLs
• Noncanonical URLs
• Pages marked noindex
• Unimportant parameter URLs
• Missing service pages
• Missing articles
• Incorrect last-modified dates

Submit the correct sitemap in Search Console and monitor how many submitted URLs Google indexes.

A sitemap can help Google discover the new structure, but it does not repair broken redirects, weak content, incorrect canonicals, or missing internal links.

Confirm that Google can render the page

Modern redesigns often rely heavily on JavaScript.

Google can process JavaScript, but blocked resources, failed requests, delayed content, and implementation problems can affect what appears in the rendered page. Google describes JavaScript processing as a sequence involving crawling, rendering, and indexing.

Use URL Inspection to compare:

• The visible page in your browser
• The rendered page available to Google
• The HTML response before JavaScript
• The final rendered HTML

Confirm that Google can see:

• The H1
• Main text
• Product or service information
• Internal links
• Navigation
• Canonical tags
• Meta robots directives
• Structured data
• Images and supporting content

Common redesign problems include:

• Content loaded only after a click
• API requests failing for crawlers
• Links built without crawlable URLs
• Text injected after a long delay
• Important resources blocked
• Client-side errors
• Empty HTML shells
• Mobile-specific rendering failures

Check server responses and availability

A site may look functional during a quick browser test while returning errors intermittently.

Review:

• Server logs
• Hosting error logs
• Uptime reports
• CDN settings
• Firewall rules
• Rate limits
• Bot protection
• DNS configuration
• SSL certificates
• Cache behavior
• Origin server performance

Look for:

• 500 server errors
• 502 gateway errors
• 503 unavailable responses
• 403 blocks
• Timeouts
• Excessive redirects
• Different responses for bots
• Errors tied to specific templates

A hosting change can temporarily affect Googlebot’s crawl rate even when URLs remain the same. Google advises monitoring server logs and crawl behavior during hosting migrations.

Check page speed and Core Web Vitals

A redesigned website may be heavier because of:

• Larger images
• Video backgrounds
• More fonts
• Page builders
• Animation libraries
• Tracking scripts
• Chat widgets
• Review widgets
• Third-party embeds
• Unused JavaScript
• Large CSS files

Performance can affect user experience and search performance, but it should be evaluated alongside the larger evidence.

A major traffic loss beginning on launch day is more likely to involve indexing, URLs, tracking, server access, or template-wide issues than a modest change in a Lighthouse score.

Review:

• Largest Contentful Paint
• Interaction to Next Paint
• Cumulative Layout Shift
• Mobile performance
• Server response time
• Image sizes
• JavaScript execution
• Third-party scripts
• Field data in Search Console
• Real-user data when available

Do not focus only on a single lab score.

Check structured data, but keep it in perspective

A redesign may remove or break structured data for:

• Organization information
• Articles
• Products
• Breadcrumbs
• Events
• Local business details
• Reviews
• Videos

This can affect eligibility for certain search features and change how Google understands parts of the page.

Use the Rich Results Test and Search Console enhancement reports to identify errors.

A general organic traffic collapse usually warrants checking indexing, tracking, redirects, content, canonicals, internal links, and server behavior first.

Restore only structured data that accurately represents visible content and follows Google’s current eligibility requirements.

Determine whether Google is choosing the wrong page

After a redesign, Google may begin ranking a different URL for an important query.

This can happen when:

• Two pages overlap
• A category page and service page target the same intent
• The new page is less specific
• Canonical signals conflict
• Internal links favor another URL
• Several old pages redirect to one broad page
• Page titles became too similar
• The previous ranking page was removed

In Search Console:

1. Filter by the query.
2. Review the Pages tab.
3. Compare the period before and after the redesign.
4. See whether the ranking URL changed.

A traffic decline may reflect Google switching to a weaker page rather than removing the website entirely.

Separate branded and nonbranded traffic

Branded searches include the company or product name.

Nonbranded searches describe a need without naming the business.

Examples:

Branded:
Kismet Creative Co.

Nonbranded:
technical website assessment company

A redesign can affect these differently.

Branded traffic may remain stable because people are already looking for the company.

Nonbranded traffic may decline because service pages, content, titles, internal links, or search intent changed.

Create separate Search Console filters where possible and compare:

• Branded clicks
• Branded impressions
• Nonbranded clicks
• Nonbranded impressions
• Pages associated with each group

This helps show whether the website lost general visibility or only experienced a change in brand demand.

Compare search demand and seasonality

A redesign can launch during a normal seasonal decline.

Before attributing the entire loss to the website, review:

• The same period last year
• Google Trends
• Sales patterns
• Industry seasonality
• Weather
• Holidays
• School calendars
• Local events
• Product availability
• Advertising activity

Google recommends using Google Trends alongside Search Console when investigating whether demand changed for the affected queries.

This does not excuse technical problems. It prevents the redesign from receiving blame for traffic that would have declined anyway.

Check for a Google search update near the launch

Search rankings can change because Google updated its systems near the redesign date.

Review:

• Google Search Status Dashboard
• Search Console annotations
• Industry reporting
• The pages and queries affected
• Competitor movement
• Whether sites across the same industry changed

A search update and redesign can overlap.

That makes page-level evidence even more important.

If only changed URLs declined, investigate the redesign first.

If unchanged pages across the site also declined and competitors shifted at the same time, a broader search update may be involved.

Compare the old and new site systematically

The best evidence often comes from a direct comparison.

For each important old URL, record:

Compare the old and new site systematically

The best evidence often comes from a direct comparison.

Start with the pages that previously produced the most traffic, leads, sales, or backlinks. For each important old URL, compare the following:

• URL: Did the address stay the same? If it changed, where does the old URL lead?
• Status code: Does the old URL return a 200, 301, 302, 404, or another response?
• Redirect destination: Does the old page redirect to the closest relevant replacement?
• Title tag: Did the new page retain the topic, service, and location language that previously performed well?
• H1: Does the primary heading still clearly describe the page?
• Content: Was useful copy removed, shortened, consolidated, or hidden inside interactive elements?
• Canonical: Does the page identify the correct live URL as its preferred version?
• Robots directive: Is the page indexable?
• Internal links: Does the new site still link to the page from relevant navigation, service pages, and articles?
• Search Console clicks: How many clicks did the page receive before and after launch?
• Search Console impressions: Is the page appearing less often, or are people simply clicking it less?
• GA4 organic sessions: Does the analytics decline agree with the Search Console data?
• Primary queries: Did the page lose visibility for specific searches?
• Backlinks: Do external links still reach a valid and relevant page?
• Structured data: Was useful and valid schema removed or broken during the redesign?

There is little value in treating every URL as equally important. Begin with the pages responsible for the largest losses and work downward from there.

Start with the pages that previously produced the most traffic, leads, sales, or backlinks.

There is little value in treating every URL as equally important.

A practical diagnostic order

I would investigate a post-redesign traffic drop in this order.

1. Confirm the dates

Record the launch date and every major technical or marketing change around it.

2. Compare Search Console with GA4

Determine whether the decline appears in search performance, website measurement, or both.

3. Identify the affected pages

Sort by the pages that lost the most clicks or organic sessions.

4. Check indexability

Inspect robots directives, noindex settings, canonicals, and Google’s indexed version.

5. Compare old and new URLs

Find missing redirects, broken paths, chains, loops, and irrelevant destinations.

6. Compare content and intent

Review what was removed, rewritten, merged, or made less specific.

7. Audit internal links

Confirm that valuable pages remain connected to the website.

8. Test rendering and templates

Make sure Google receives the content, links, metadata, and canonical signals you expect.

9. Review performance and server behavior

Look for errors, blocking, timeouts, and major regressions.

10. Account for outside factors

Check seasonality, demand, competitor changes, and search updates.

This order prioritizes the issues most likely to explain a sudden redesign-related decline while keeping the investigation grounded in evidence.

Common mistakes during recovery

Changing the URLs again

Another round of URL changes can create additional redirects, new crawl requirements, and more uncertainty.

Keep the current URLs unless there is a clear reason to change them.

Rewriting every page at once

Broad rewrites make it difficult to see which change helped.

Start with the pages responsible for the largest losses.

Redirecting every old URL to the homepage

Map old pages to their closest relevant replacements.

Requesting indexing repeatedly

Indexing requests can help Google revisit a limited number of important pages. They do not replace a correct sitemap, strong internal links, stable server access, or proper redirects.

Treating every Search Console 404 as an emergency

Some 404s are expected after content is intentionally removed.

Prioritize old URLs that had traffic, backlinks, internal links, or a clear new replacement.

Assuming a plugin will handle the entire migration

SEO plugins can help manage metadata, sitemaps, canonicals, and redirects. They still require correct configuration and a complete understanding of what changed.

Focusing only on the homepage

Most organic traffic often lands on service pages, articles, products, categories, or location pages.

A healthy homepage does not prove the rest of the site survived the redesign correctly.

Waiting without establishing a baseline

Some processing time is normal after major changes.

Waiting is reasonable once the technical setup has been verified.

Waiting without checking tracking, indexability, redirects, canonicals, content, and internal links can allow a preventable problem to continue.

How quickly can search traffic recover?

There is no universal recovery period.

Recovery depends on:

• The cause
• The number of affected URLs
• The size of the website
• Crawl frequency
• Server performance
• How quickly the problem was corrected
• Whether content was removed
• Whether authority was consolidated properly
• Whether the new pages satisfy the same intent
• Whether the old site can still be reconstructed
• Whether outside search conditions also changed

A tracking correction may make the reported traffic return immediately.

A missing redirect can begin passing visitors as soon as it is added, while search systems may take longer to process the relationship.

Content and ranking recovery may take considerably longer because Google needs to crawl, index, compare, and reassess the affected pages.

Google notes that some changes can be reflected within days while broader reassessment may take weeks or months.

Avoid promising a fixed recovery date before the cause is known.

What should happen before a future redesign

A redesign is much safer when search considerations are included before launch.

Preserve or document:

• A full crawl of the old website
• Existing URLs
• Search Console exports
• GA4 landing-page data
• Top-performing queries
• Backlinks
• Title tags
• Meta descriptions
• Headings
• Canonicals
• Structured data
• Internal links
• XML sitemaps
• Robots settings
• Redirect requirements
• Analytics and conversion tags

Before launch:

1. Map old URLs to new URLs.
2. Compare high-value old and new pages.
3. Crawl the staging site.
4. Confirm canonicals.
5. Confirm production analytics.
6. Test forms and conversion events.
7. Prepare redirects.
8. Review the XML sitemap.
9. Confirm the production site will be indexable.
10. Establish a post-launch monitoring plan.

After launch:

1. Crawl the production website.
2. Test old URLs.
3. Check important redirects.
4. Verify GA4 and Google Tag Manager.
5. Inspect key pages in Search Console.
6. Monitor server errors.
7. Compare clicks, impressions, and landing pages.
8. Check the Google-selected canonicals.
9. Review conversions and lead delivery.
10. Document any changes made after launch.

When a technical assessment makes sense

A focused technical review may be useful when:

• Traffic fell after a redesign
• The redesign agency says everything is working
• Search Console and GA4 tell different stories
• Nobody has a complete list of the old URLs
• Redirects were added after launch without a documented map
• Important content disappeared
• Several vendors handled different parts of the migration
• The website also changed hosts or domains
• Google is choosing unexpected canonical URLs
• Leads declined along with traffic
• Tracking and search visibility may both be involved
• The old website is no longer accessible
• Previous fixes have not produced a clear recovery

Kismet’s Technical Website Assessment can review the redesign, search data, URLs, redirects, indexing signals, templates, tracking, and connected systems to determine what changed and where the decline is coming from.

The goal is to identify the evidence before recommending another redesign, rebuild, migration, or large batch of SEO changes.

We also provide ongoing WordPress support and troubleshooting in Jacksonville for businesses that need help maintaining or stabilizing an existing site.

—

Find out what changed during the redesign

A post-redesign traffic decline can involve search visibility, website tracking, content, redirects, templates, hosting, or several of these at once.

Kismet can investigate the website and document the most likely causes, affected pages, and recommended next steps.

Request a Technical Website Assessment

—

Written by Joey Zuccarini
COO at Kismet Creative Co.