Use audit for relaunch and migration
Relaunches often change URLs, templates, content, tracking and technology simultaneously. An audit before and after the migration reduces the risk of losing visibility due to avoidable errors.
A relaunch audit does not protect against every fluctuation, but against many classic technical and structural losses.
Why relaunches need their own audit
During a relaunch, several SEO basics often change at the same time. Even small errors in forwardings, canonicals, noindex rules or internal linking can affect important pages.
A pre-audit documents the initial state. An after-audit shows whether the new website delivers the same important signals cleanly.
- URL structure and redirects
- Canonical, noindex and robots.txt rules
- Sitemap and internal links
- Tracking, performance and central templates
What controls are important before the go-live
Before relaunch, important URLs, rankings and page types should be known. This results in the checklist for forwardings, templates and content.
Particularly risky are pages with organic visibility, backlinks, sales reference or many internal links.
- Invent important old URLs
- Check Redirect Targets and Avoid Chains
- Control staging on noindex and robots rules
- Templates for Title, H1, Canonical and Structured Data Test
Classic Relaunch Risks in Audit
Many losses are caused by technical details that are overlooked in project stress. Old URLs provide 404, redirects pointing to incorrect targets or sitemaps still contain staging paths.
Content can also suffer: If search intentions, internal links or snippets become weaker in the new design, the technical migration remains clean, but the performance does not.
- Missing or incorrect redirects
- noindex from the staging environment
- Canonical on Old, Wrong or Blocked URLs
- Tracking and Consent Setup Changed After Go-Live
Audit process for relaunch projects
Schedule audits as fixed milestones instead of as an emergency measure after the go-live. Risks become visible early on.
- Create a pre-audit of the existing website
- Mark critical URLs and rankings
- Perform redirect and template testing in staging
- Crawl directly to Go-live again
- Prioritize deviations and correct them promptly
Check directly with your website
Check the existing website before the relaunch and the new version directly after the go-live. The comparison shows whether important signals have remained stable.
Frequent questions
When should the first relaunch audit take place?
Before the go-live, as long as old website and staging are comparable. After that, it should be re-examined immediately after publication.
Which URLs are particularly important when migrating?
Pages with organic traffic, backlinks, revenue reference, strong rankings, many internal links or strategic importance belong in the first checklist.
Can a relaunch succeed without ranking fluctuations?
Variations are possible. A clean audit reduces avoidable errors and makes deviations explainable faster.