Traffic dropped after a redesign: what changed and how to fix it
Traffic drops after a redesign when URLs, content, internal links, titles or rendering changed. Diff the old and new site on each and fix what moved.
LLaunchScaler·Published ·7 min read
Traffic drops after a redesign when the new site changed something Google ranked the old pages on: URLs that moved without redirects, copy cut to fit the new layout, internal links dropped from the navigation, titles and headings rewritten, or content moved into client-side rendering. Find it by comparing the old and new versions of the pages that lost the most clicks, check by check, then restore what carried the rankings.
A visual change alone rarely costs rankings. The loss comes from what changed along with the visuals, and each cause leaves a clear trace.
What changes in a redesign that costs rankings?
The changes that cost rankings are the ones to the parts of a page Google reads: the URL, the text, the links in and out, the head tags, and the HTML delivered before JavaScript runs. A redesign often touches all of these at once, because new templates, a new CMS or a new component library replace the old markup wholesale.
What changed
How it shows in Search Console
How to confirm it
The fix
URLs changed without redirects
Old URLs under Not found (404), clicks gone from those pages
Request old URLs with curl -sI
301 each old URL to its new equivalent
Content cut from pages that ranked
Position falls on the queries that page answered
Compare word count and sections, old vs new
Questions, answered
What people ask about this
01
Why did my traffic drop after a website redesign?
A redesign usually changes something Google ranked the old pages on: URLs without redirects, copy cut to fit the new layout, internal links removed from the navigation, titles and headings rewritten, or content moved into client-side JavaScript. Compare the old and new versions of your top pages on each of those.
Crawl both versions and compare inbound links per page
Put the links back in navigation, footer or body
Titles and headings rewritten
CTR or position changes on the page's main queries
Diff <title>, <h1> and <h2>s, old vs new
Restore the terms searchers used
Content moved to client-side rendering
Pages indexed with thin content, or not at all
curl the page and grep for body text
Render the main content on the server
How do you compare the old site with the new one?
Start from the pages that lost the most, not from the whole site. In the Search Console Performance report, compare the weeks since launch with the same number of weeks before it, open the Pages tab and sort by the change in clicks. The top ten losers often point to one or two causes that repeat across the site.
For each of those pages, you need the old version to compare against:
Your own records first: a crawl export taken before launch, the old templates in your repository history, or the old CMS if it still runs.
If you kept nothing, look the URL up in the Internet Archive's Wayback Machine at web.archive.org and open a snapshot from before the launch date.
Fetch the new version the way a crawler does: curl -s https://yoursite.com/page > new.html.
Compare the URL and status code, the <title>, the <h1> and <h2>s, the body text, the number of internal links pointing to the page and the canonical tag.
Keep a table of what differs per page. Patterns show up quickly: every blog post lost its FAQ section, every feature page moved to a new path, every docs page lost its sidebar.
Did URLs change without redirects?
If the redesign changed URL paths and old URLs now return 404, Google drops them over time and the traffic they earned goes with them. Check it first, because it is the fastest to confirm: request a handful of old URLs from your analytics or the Performance report and read the status codes.
Google's status code documentation says that for a 404, "the indexing pipeline removes the URL from the index if it was previously indexed." Every old URL with a replacement needs a permanent redirect to it, in one hop. Google treats a 301 as "a strong signal that the redirect target should be processed," while a 302 is only a weak signal. Do not send every old URL to the new homepage; Google says redirecting "many old URLs to one irrelevant single URL destination" can be "treated as a soft 404 error."
If the redesign also changed the domain or platform, it was a migration, and the full checklist is in the site migration SEO checklist.
Was content cut from pages that ranked?
New designs often have less room for text. Long explanations, FAQs, comparison tables, specifications and customer examples get trimmed or moved behind tabs, and those were often the passages that answered the queries the page ranked for. The page still exists at the same URL, but it no longer answers what searchers asked.
Look at the queries each losing page ranked for before the launch (Performance report, filter by page, Queries tab, date range before the redesign). For each query, find the passage on the old page that answered it, then look for it on the new page. A query with no answering passage on the new page is a query you should expect to lose.
Restore those passages on the new design. They do not need the old layout, only the substance: the same facts, steps, numbers and definitions, in HTML that is present on load.
Were internal links and navigation removed?
A cleaner navigation often drops links to deeper pages: the old mega-menu linked forty pages, the new one links six. Pages that lost their internal links become harder for Google to find and recrawl, and they stop receiving the anchor text that described them. Google's guidance is plain: "Every page you care about should have a link from at least one other page on your site."
Crawl the old site (from your export or archived pages) and the new one, and compare the count of internal links pointing at each important page. Also check how links are built. Google says it "can only crawl your link if it's an <a> HTML element with an href attribute," so a menu rebuilt with onclick handlers, <span> elements or router components that do not render an href hides every destination from Google even though visitors can click through.
Restore links to key pages from the navigation, the footer, or related-content blocks in the body, with descriptive anchor text rather than "read more."
Were titles and headings rewritten?
Redesigns often come with new copy, and new copy often trades the plain terms people search for with brand language. A page that ranked for "invoice software for freelancers" under that title loses relevance when the title becomes "Get paid, beautifully." Google builds its title links from the <title> element, the main visual title, heading elements such as <h1>, and other prominent text.
Diff the <title>, <h1> and <h2> of each losing page against the old version. Google's advice is to write "descriptive and concise text for your <title> elements" and avoid "repeated or boilerplate text," which rules out a new template that appends the same long tagline to every title. Put the searched terms back where they were, in your new voice.
Check the other head tags at the same time: a missing or changed canonical, a dropped meta description, and structured data that the old theme output and the new one does not.
Did content move to client-side rendering?
A redesign built on a new front-end framework can move content that used to be in the server HTML into JavaScript that runs in the browser. The page looks the same to you, while crawlers that do not run JavaScript receive an empty shell, and Google has to queue the page for rendering before it sees anything.
Google's JavaScript documentation says pages can stay in the render queue "for a few seconds, but it can take longer than that," and recommends server-side or pre-rendering because "not all bots can run JavaScript." To test a page, run curl -s https://yoursite.com/pricing | grep -c "a sentence from the page". A count of 0 means the sentence is not in the server HTML. In Search Console, URL Inspection's Test live URL and View tested page show what Google rendered.
The fix is to render the main content, links and head tags on the server. The same regression can arrive in any later release, not only in a redesign; SEO regressions after a deploy covers the post-release checks.
What if none of these explains the drop?
If URLs, content, links, titles and rendering all match the old site, the redesign may have coincided with something else. Check that tracking survived the redesign (a new theme often drops the analytics tag or changes the consent banner), then compare the launch date with Google's ranking updates on the Search Status Dashboard. Google's debugging guide also names site migrations as a reason "you may experience ranking fluctuations while Google recrawls and reindexes your site," so give a large change a few weeks before concluding it failed.
The full order of checks for a drop with no obvious cause is in the organic traffic drop diagnosis. Once you have fixed the cause, request indexing for the most important pages in URL Inspection; Google says recrawling "can take anywhere from a few days to a few weeks."
Keep the next release from undoing the fix
A redesign is rarely the last big change: new templates, a new CMS plugin or a component refactor can repeat the same losses months later. LaunchScaler Watch re-scans your site every two weeks for $29/mo, emails a diff on every run showing which checks moved and the evidence behind each change, runs uptime checks on your health endpoint in between, and alerts you when a check drops below the bar. Start watching.
02
How long does it take to recover rankings after a redesign?
Once the cause is fixed, Google has to recrawl the affected pages, which it says can take anywhere from a few days to a few weeks. Pages whose content was restored usually need a recrawl before Google reassesses them.
03
How do I see what my site looked like before the redesign?
Use your own crawl export or repository history if you kept them, or look up your URLs in the Internet Archive's Wayback Machine at web.archive.org. Compare titles, headings, body copy and internal links on the pages that lost the most clicks.
04
Should I roll back a redesign that lost traffic?
Only if you cannot find the cause quickly. Most redesign losses come from a few specific changes, such as missing redirects or removed copy, and restoring those on the new design keeps the work you did while recovering the signals Google relied on.
05
Does changing the design itself hurt SEO?
Colours, fonts and layout do not decide rankings on their own. What hurts is what changes along with them: URLs, the text on the page, the links between pages, the head tags and how the content is rendered.
Eight website change monitoring tools, from LaunchScaler Watch to Visualping and Distill.io, judged on whether they catch the changes that cost rankings.
Track AI visibility with a fixed prompt set, the same engines and a fixed schedule, scoring mention, citation and accuracy, and watch your AI access too.
