Planning, buying, redesigning and choosing the right architecture for business websites and commerce.
View topic guides01 / GUIDE
The biggest SEO migration mistake is treating the old website as disposable
A redesign is usually judged by the new website. Search engines also care about the history of the old one: which URLs are indexed, which pages attract links, which queries generate impressions, which pages convert, and how those signals are transferred.
If a rebuild changes URLs, removes useful content, weakens internal links or launches with broken redirects, a visually better website can still lose search visibility.
02 / GUIDE
Before the redesign: capture the current search estate
Before changing anything, create an inventory of the existing site. At minimum capture:
- all crawlable URLs;
- XML sitemap URLs;
- Google Search Console landing-page and query data;
- pages with external backlinks;
- current titles, descriptions, headings and canonicals;
- robots directives;
- important internal links;
- top organic landing pages and conversions where analytics is available.
This baseline tells you what must be preserved, intentionally consolidated or retired.
03 / GUIDE
Create a URL migration map before launch
Every important old URL should have an intentional destination. If the content still exists, redirect the old URL to the closest equivalent new URL. Do not send every retired page to the homepage simply because it is easy.
Where a page has no genuine replacement, a 404 or 410 can be more honest than an irrelevant redirect. Redirect chains should be avoided where practical: old URL → final new URL is cleaner than old URL → temporary URL → another URL.
04 / GUIDE
Preserve search intent, not just keywords
If an old page ranks because it answers a specific query, the replacement must still satisfy that need. A redesign sometimes collapses several useful pages into one visually minimal page and accidentally removes the substance Google and users relied on.
Preserve the topic, useful information, evidence, FAQs, product details, service scope and internal relationships that made the old page valuable. Improve weak content, but do not delete strong content merely to make the new design cleaner.
05 / GUIDE
Technical checks before launch
- Final URLs return the intended status codes.
- Canonical tags point to the correct production URLs.
- No staging-domain canonicals remain.
- No accidental
noindexdirectives remain. - robots.txt does not block assets or sections needed for crawling.
- XML sitemaps contain canonical, indexable production URLs.
- Internal links point directly to final URLs rather than redirects.
- Structured data still matches visible content.
- Mobile rendering, forms and navigation work.
- HTTPS, mixed content and certificate behaviour are correct.
06 / GUIDE
Launch day: what to do
Deploy the redirect map with the new site, not days later. Verify representative old URLs manually. Crawl the new site. Check the homepage, major service pages, top organic landing pages, forms and transaction paths. Submit the current sitemap in Search Console.
If the domain itself changes, use Google’s documented site-move process and the Search Console Change of Address tool where applicable. If only paths change on the same domain, the redirect and sitemap work still matters even though Change of Address is not used.
07 / GUIDE
After launch: monitor what actually changed
Expect some fluctuation while search engines recrawl and reprocess the site. Watch index coverage, crawl errors, redirect failures, top landing pages, query impressions, clicks and conversions. Compare against the pre-launch baseline rather than relying on a single headline traffic number.
Investigate sharp page-level losses. Common causes include missing redirects, changed intent, accidental noindex, poor canonicalisation, orphaned pages, removed content or internal-link dilution.
08 / GUIDE
Primary Google guidance
Google documents URL changes and redirects in Search Central, including guidance on site moves with URL changes and redirects. Those are the baseline references PluginPip uses when separating migration facts from SEO folklore.