By Mehdi HassanWhat is a pre redesign SEO audit?
A pre redesign SEO audit is a snapshot of everything your current site earns in search, taken before the redesign begins, so you can protect it. It's narrower than a full audit: the goal isn't to find every problem but to record what must not be lost.
Redesigns are where rankings most often disappear. URLs change, pages get merged or cut, copy gets shortened to fit a new layout and nobody notices until traffic falls. Our research found that SEO redirect and content-migration work, an extra 10–20% on a redesign, is usually left out of agency quotes, which tells you how often it's treated as an afterthought. This audit bridges the two projects: it turns your current SEO into a brief for the new site. For the wider audit discipline, see our guide to SEO audits.
What SEO data should you capture before a website redesign?
Capture six things before a redesign: every URL, the pages that drive traffic and conversions, the queries you rank for, the pages other sites link to, your on-page elements and your technical setup. Together they're your baseline and your redirect plan.
Export a full URL inventory
Combine a crawl of the live site, your XML sitemap, Search Console's indexed pages and analytics landing pages. Each source finds URLs the others miss, especially old campaign pages and PDFs.
Record top pages by clicks and conversions
From Search Console, export clicks and impressions per page for at least the last twelve months, to cover seasonality. From analytics, add conversions per landing page.
Save ranking queries per page
Export the queries each important page ranks for, with position and clicks. This tells the copywriter which terms the new page has to keep answering.
List pages with backlinks
Use a backlink tool or Search Console's links report to find every URL other sites link to. These URLs must redirect to a close match, never to the homepage.
Snapshot on-page elements
Crawl and save titles, meta descriptions, H1s, headings, word counts, canonicals and structured data for every page.
Document the technical setup
Record robots.txt, sitemap structure, redirects already in place, hreflang if any, and Core Web Vitals field data per template.
Save copies of key pages
Archive the full HTML and copy of priority pages. When rankings drop later, a side-by-side comparison of old and new content is the fastest diagnosis.
How do you build a URL inventory for a redesign?
Build the URL inventory as a single spreadsheet with one row per current URL, its performance data and its planned future. It becomes the redirect map, the content brief and the post-launch checklist in one file.
Column | What goes in it | Why it matters |
|---|---|---|
Current URL | Every URL from crawl, sitemap, Search Console and analytics | Nothing gets forgotten |
Clicks and impressions | Last 12 months from Search Console | Shows which pages earn search traffic |
Conversions | Leads or signups per landing page | Protects pages that make money, not just traffic |
Top queries | Main ranking terms and positions | Brief for the new page's copy |
Referring domains | Count of sites linking to the URL | Flags pages whose links must be preserved |
Action | Keep, merge, rewrite, redirect or remove | The decision for each page |
New URL | Destination on the new site | Becomes the redirect map |
Owner and status | Who handles it and whether it's done | Makes launch QA possible |
If you're also cutting or merging content, run a content audit alongside this one. Our website content audit template and method covers the quality side: which pages are worth rewriting and which can go.
Which pages and rankings should you protect?
Protect pages that score on any of three measures: search traffic, conversions or backlinks. A page with modest traffic but strong links, or few visits but high conversions, deserves as much care as your top blog post.
- Traffic pages. Pages with consistent clicks from search. Keep their URL where you can, and keep the content that answers their top queries.
- Money pages. Pricing, product, integration and comparison pages that convert. Changing their copy is fine; losing their intent match is not.
- Linked pages. URLs with referring domains. If they go, redirect each to the closest equivalent.
- Ranking near the top. Queries where you sit just outside the first few positions are both at risk and full of upside.
- Pages answer engines cite. If you know a page is cited in AI answers, keep its answer-first structure and facts intact.
Turn this into a short "must protect" list of the twenty or so URLs that matter most, and put it in the design brief. A full spreadsheet gets ignored; a one-page list gets designed around. Our guide to redesigning without losing SEO rankings covers what to do with that list during design and build.
How do you protect backlinks during a redesign?
You protect backlinks by redirecting every linked URL with a permanent 301 to the closest matching page on the new site. Redirecting everything to the homepage throws most of that value away.
Start from the referring domains column in the inventory. For each linked URL, choose the new page that answers the same intent. If a page is being removed with no equivalent, redirect to the nearest parent topic, and consider keeping the content if the links are strong. After launch, test every redirect in the list, not a sample: a single typo in a redirect rule can break dozens of linked URLs.
Hypothetical example: a merged features section
For example, suppose a SaaS site has eight separate feature pages and the redesign merges them into three. The inventory shows two of the old pages have links from industry blogs and one ranks well for a specific integration query.
The plan: map each old page to the new page that covers its topic, keep a dedicated section with its own heading for the integration query so the copy still answers it, and redirect the two linked pages to the exact section's page. The linked pages keep their value, and the ranking query still has a clear answer.
What should the redesign team get from the audit?
The redesign team should get three things: the must-protect list, the redirect map and a content brief for each priority page. Those turn SEO from a launch-week checklist into a design input.
Designers need to know which pages must keep long-form content, so layouts don't squeeze it out. Copywriters need the top queries for each page. Developers need the redirect map, the canonical rules and the rendering requirement: key content must be in the server HTML. Working out these constraints before design is part of a good website strategy workshop, and the launch steps are covered in our technical SEO checklist for new website launches. This is also why we start projects with the words: the copy plan carries most of the SEO you're protecting.
How do you know if the redesign hurt SEO?
You know a redesign hurt SEO when traffic to protected pages falls well below the baseline and doesn't recover after search engines recrawl. The pre-redesign audit is what makes that comparison possible.
According to the recovery sources in our research, a dip under 10% that recovers within weeks is normal after a redesign. A drop of 30–50% that persists needs action, and the usual causes are missing redirects, accidental noindex tags, wrong canonicals and lost content. Compare Search Console clicks for each protected URL before and after, check the indexing report for excluded pages, and diff old and new copy for pages that fell. Our guide to benchmarking a site before a migration covers the same comparison for platform switches.
