Redesigns are the single most common way established sites lose half their organic traffic overnight. A website redesign SEO audit is the work you do before, during, and after launch to make sure the new site inherits everything the old one earned — the URLs, the content depth, the internal link equity, and the technical signals Google has spent years learning.
The pattern is always the same. Design and development go well, the site looks dramatically better, it launches on a Thursday, and by the following Tuesday rankings are gone. Nobody set out to break anything. The damage comes from decisions that seemed cosmetic — shorter page copy, a cleaner navigation, tidier URLs — each of which quietly removed a ranking signal.
Before anything else: capture the baseline
You cannot diagnose a loss you cannot measure. Two to four weeks before launch, freeze a complete snapshot of the current site.
- Full URL inventory. Crawl every indexable URL and export it with status code, title, meta description, H1, word count, and canonical.
- Traffic and ranking data per URL. Twelve months of Search Console data at page level — clicks, impressions, average position — plus GA4 sessions and conversions.
- Top-100 rank snapshot for your tracked keyword set, with the ranking URL recorded for each. That last field is what tells you later whether Google switched which page it prefers.
- Backlink profile. Referring domains mapped to the specific pages they point at. Pages with external links are the ones a redirect mistake hurts most.
- Core Web Vitals field data as it stands, so you can prove the new build is faster rather than assuming it.
Store this somewhere permanent. Six weeks after launch, when someone asks whether a given page used to rank, the baseline is the only answer that will not be a guess.
Identify the pages you are not allowed to break
Sort the baseline by clicks over twelve months and take the top 20 percent. On most sites that set delivers 80 percent or more of organic traffic. Add every page with three or more referring domains, and every page that ranks in the top ten for a commercial term.
That combined list is your protected set. Every one of those URLs needs either an identical URL on the new site or a one-hop 301 to the closest equivalent, and every one needs its content substantially preserved. Not “the topic is still covered somewhere” — preserved. If the old page ran 1,800 words with a comparison table and the new design allows 400 words of hero copy, you are removing the reason it ranked.
This is where design and SEO actually collide, and it is worth having the argument early. A page can be beautiful and substantial. It cannot be beautiful and empty and still rank.
URL mapping is the core deliverable
Build a spreadsheet with one row per old URL and these columns: old URL, new URL, redirect type, status, and notes. Every old URL needs a destination. There are only three legitimate answers.
- Same URL — best case. If the URL structure works, keep it. Nothing about a redesign requires changing paths.
- 301 to the closest equivalent — a real replacement covering the same topic and intent. One hop, no chains.
- 410 or a genuine 404 — for content deliberately retired with no equivalent. Do not redirect these to the home page; Google treats mass home-page redirects as soft 404s and you lose the signal anyway.
The failure mode to hunt for is the lazy bulk rule — redirecting an entire directory to a single new landing page. It preserves nothing and it strips relevance from every URL in the group.
Audit the staging site before launch
Crawl staging as if it were live, with authentication configured so the crawler can reach everything. Compare against the baseline crawl and check for these specifically.
Word count per template — new designs routinely cut copy by half without anyone noticing until traffic drops. Title tags and meta descriptions — many CMS migrations reset these to defaults, so verify titles stay under roughly 60 characters and descriptions land in the 140 to 155 character range where they render fully. Heading structure — confirm one H1 per page and that it is the page topic, not the site name. Internal links — count links per page and compare; a simplified navigation can remove hundreds of internal links and flatten the link graph that was distributing authority. Structured data — schema is easy to lose in a template rebuild. Canonicals — check they point at the new production domain, not at staging.
And the one that ends careers: confirm the staging noindex directive and any robots.txt disallow are removed at launch. Set a calendar reminder. Check it within an hour of going live.
Launch day sequence
Go live early in the week, never on a Friday, and ideally during your lowest-traffic window. Then run this in order.
- Verify robots.txt is the production version and does not block the site.
- Spot-check 20 URLs from the protected set — confirm each resolves with a single 301 and lands on the intended page.
- Run the full redirect map through a bulk status checker. Look for 404s, redirect chains, and loops.
- Submit the new XML sitemap in Search Console. Keep the old sitemap accessible for a few weeks so Google recrawls the old URLs and discovers the redirects faster.
- Confirm analytics and conversion tracking fire on the new templates.
- Re-verify Search Console and GA4 connections if the domain or property changed.
The four-week monitoring window
Expect turbulence. A degree of ranking movement after a redesign is normal even when everything was done correctly, because Google has to recrawl, re-render, and re-evaluate every URL. Daily swings of two or three positions are noise on any site; after a migration the noise band is wider.
What matters is the shape over four to six weeks. Watch Search Console’s Pages report for a rise in “Not found (404)” or “Page with redirect” volumes, watch impressions rather than clicks in week one because impressions move first, and watch the ranking URL field in your tracker — if a keyword’s ranking URL changed from a deep page to the home page, you have a redirect or canonical problem, not a content problem.
Running a full crawl at week two and week six catches what launch-day checks miss. A workspace that keeps the crawl, the rank tracking with movement deltas, and Search Console side by side makes this a twenty-minute review rather than an afternoon of spreadsheet reconciliation; SEO Rocket covers that combination at a flat US$50 a month, with audits reporting the actual titles, URLs, and H1 text so you can diff against the baseline directly.
If traffic drops anyway
Work in this order. Check indexation first — are the pages in the index at all? Then redirects — is the old URL reaching the right new one in one hop? Then content — did the page lose substance relative to the version that ranked? Then internal links — is the page still linked from where it used to be linked? Then technical — rendering, speed, mobile usability.
Resist the urge to make ten changes at once. Fix the highest-confidence issue, wait two weeks, and read the trend. Diagnosis after a redesign is slow by nature, and the baseline you captured in week one is what makes it possible at all.
