A redesign changes more than the appearance of a website. It can change URLs, page content, navigation, templates and tracking. A pre-redesign SEO audit gives the team a clear record of what exists and a plan for handling each important page. It reduces avoidable migration errors, but cannot guarantee that rankings or traffic will stay the same.
Key checks
- Record the current URLs, search performance, important links and conversions.
- Decide whether each page will stay, change, merge or be removed.
- Test redirects, indexability, analytics and key tasks before launch.
- Monitor the new site and fix issues according to business impact.
1. Capture a reliable baseline
Crawl the current site and save each URL with its status code, title, meta description, canonical, indexation directives and internal links. Include pages that matter to customers even if they receive little search traffic, such as support pages, forms and checkout steps.
Export a consistent period of Google Search Console and analytics data. Record landing pages, queries, clicks, impressions and properly configured conversions. Note the measurement dates and any privacy or consent settings that affect the data. Keep copies of content, media and configuration needed for recovery.
2. Decide the future of every URL
Google’s site-move guidance recommends preparing and testing URL mappings when a site moves or changes URLs. For each page, decide whether to retain, improve, combine or remove it. If its URL changes, map it to the closest relevant replacement. Do not send every retired URL to the homepage. A redirect should help visitors reach a page that fulfils their original intent.
Agree the URL structure, navigation and content responsibilities before development is complete. Preserve valuable information and links unless there is a clear reason to change them.
3. Test before and after launch
On staging, check representative pages on mobile and desktop. Test redirects, internal links, canonical URLs, robots directives, sitemap entries, forms and analytics events. Confirm that important content is present in crawlable HTML and that structured data matches what users can see.
After launch, check real responses, old and new URLs, Search Console coverage and key conversions. Compare results with the baseline while accounting for seasonality, campaigns and other changes. Fix errors that affect important pages or customer tasks first. Search engines need time to recrawl and process a site change, so monitor rather than treating an immediate fluctuation as a final result.
Questions
Will an audit prevent ranking losses?
No. It helps the team find and manage risks. It cannot control how search engines process a redesign or guarantee rankings, traffic or leads.
When should the audit happen?
Before URL, content and template decisions are locked. Later checks are still useful, but leave less time to correct the plan.