Website Traffic Dropped After a Redesign? Find Out What Broke

If your website traffic dropped after a redesign, don’t start changing titles, rewriting pages, or buying links. First find out whether visitors disappeared or your measurement did.

A redesign can change more than colors and layouts. Page addresses may move. Useful copy may be shortened. Internal links may vanish. A development setting may tell search engines not to index the new site. The analytics code may simply be missing.

Treat the launch date as the start of an investigation, not proof of one cause.

Confirm that the traffic really fell

Open the analytics system you used before the redesign. Compare the period after launch with a similar period before it. Look at total visits, traffic sources, landing pages, leads, calls, sales, and any other outcome the business records.

If all traffic sources fall to almost nothing on the launch date, measurement is the first suspect. Load several pages and check whether the analytics code is present and sending data. Test the home page, service pages, articles, and any separate booking or checkout area. A redesign may have carried the code onto one template but not another.

Also check whether the new site changed cookie consent, tracking settings, the website address, or the analytics property receiving the data. Don’t assume a blank report means nobody came.

Then separate organic search traffic from direct visits, ads, email, referrals, and social traffic. If only organic search fell, move to Google Search Console. If Search Console clicks stayed steady while analytics visits fell, the stronger explanation is a tracking problem between the search result and the analytics report.

You can check this yourself if you have access to both systems. Write down the launch time, any analytics changes, and what each report shows before asking someone to alter the website.

Match the drop to the launch, pages, and searches

Open the Search Console Performance report and place the launch date inside the chart. Google’s guide to debugging Search traffic drops recommends comparing the drop period with a similar period, then checking whether the change affects particular queries, pages, countries, devices, or search appearances.

Start with clicks and impressions. An impression means a page from your site appeared in a Google search result. A click means someone selected it.

Compare the same number of days before and after launch. If the business is seasonal, also compare the period with the same dates last year. The goal is to see whether the fall begins at launch and whether it is site-wide or concentrated.

Select the Pages tab and sort by the largest loss in clicks. Save the old addresses of the pages that lost the most. Then select Queries to find the searches that stopped bringing people. The Performance report documentation confirms that the report can group data by queries and pages and lets you change date ranges, metrics, and search types.

This gives you a short, evidence-based list. Ten lost pages that once generated inquiries matter more than hundreds of old addresses nobody visited.

Test the old URLs before inspecting the new design

Open each valuable old address in a private browser window. It should either load the same useful page or send you directly to its closest replacement.

A redirect is an instruction that sends an old address to a new one. Google’s site-move guidance recommends mapping old URLs to their new destinations, using server-side permanent redirects such as 301 or 308, and testing them. It also advises against sending many unrelated old pages to the home page because that can be treated as a soft 404.

Check for these failures:

  • an old page returns a 404 “not found” response even though its content still exists elsewhere;
  • every old address goes to the home page;
  • one redirect leads to another and then another;
  • an old service page redirects to an unrelated new page;
  • the new page’s canonical points to the wrong address; or
  • a noindex instruction remains on the live page.

A canonical is a tag that identifies the preferred address for a page. noindex is an instruction asking search engines not to include a page in results. Both are useful when set deliberately and damaging when copied from a development site by mistake.

Google specifically warns site owners to remove development noindex rules at launch and to make each new page’s canonical point to its new URL. Use Search Console’s URL Inspection tool on a few high-value pages to see the address Google selected and whether it can be indexed.

You can test a handful of old addresses yourself. A larger migration usually needs a crawl: an automated check of all known URLs, response codes, redirects, canonicals, and index instructions.

A cleaner page isn’t automatically a better search landing page. Compare the old version of each losing page with the new one.

Look for useful sections that disappeared: service details, locations served, process explanations, product specifications, answers to buying questions, qualifications, examples, and language that matched the searches people used. Don’t restore text merely because it existed. Restore what helped a prospective customer understand the offer and choose a next step.

Check page titles and main headings too. A redesign may replace a specific heading with a vague slogan or put several distinct services onto one thin page. The Query data you saved shows which subject each page previously answered.

Then inspect internal links, which are links from one page of your site to another. Navigation simplification often removes links to deeper service or article pages. Body copy may also lose descriptive links that showed visitors where to go next. Google’s migration guidance says to update internal links to the new URLs after creating the old-to-new mapping.

Rebuild links around the customer’s path, not around an SEO checklist. Important service pages should be reachable from relevant navigation, related articles, location pages, and other service pages where the connection makes sense.

Check whether slower pages played a part

Test the pages that lost valuable traffic, not only the home page. Use PageSpeed Insights on mobile and open the redesigned pages on an ordinary phone.

Performance reports may show lab data and field data. Lab data comes from a controlled test with fixed device and network settings. Field data comes from real visits. The web.dev explanation of lab and field data says field data reflects users’ actual devices, networks, and locations, while lab data is useful for controlled debugging. When both exist, it recommends using field data to prioritize work.

Compare old and new evidence if you have it. Look for oversized images, delayed main content, layout movement, heavy scripts, slow server responses, and buttons that take too long to react. Speed may not explain the entire traffic loss, but a redesign shouldn’t make important pages harder to use while you repair indexing and content.

Don’t rebuild again because of one colored score. Fix repeatable problems on pages tied to inquiries or sales, then retest the same pages.

Fix by business value, not URL count

Put the findings in one list. For each affected old page, record its previous clicks, the searches it served, its current destination, index status, missing content, internal links, performance problem, and business purpose.

Fix complete blockers first: missing analytics, accidental noindex, broken high-value URLs, wrong canonicals, and failed redirects. Next restore useful content and internal routes on pages that once produced qualified visits. Then improve speed and lower-value coverage.

This order prevents a common waste of time: clearing hundreds of harmless warnings while a small group of service pages remains invisible or broken.

After each group of fixes, annotate the date and monitor the same Search Console comparisons. Google’s traffic-drop guide notes that URL changes can cause ranking fluctuations while Google recrawls and reindexes the site. That possibility isn’t a reason to wait on obvious mistakes. It is a reason to avoid making unrelated changes every few days, because you need to know which repair affected the result.

Send me the evidence for a written answer

Send me the website address, the redesign launch date, and screenshots or exports showing the before-and-after traffic. Include Search Console’s losing pages and queries, plus any old URL list, redirect map, sitemap, or launch notes you have.

Tell me which pages produce inquiries or sales and what changed during the redesign. I’ll review the evidence and reply in writing with what appears broken and what I would fix first.

Send me your obstacle.

More articles