How should SEO be handled during a website redesign?

A redesign changes URLs, templates, content and often the platform, all things search engines use to understand a site. Handled carelessly, it can undo years of accumulated visibility in a week. Handled properly, it is an opportunity to fix structural problems and come out stronger.

1. Inventory what exists

Before any design work is signed off, build a complete list of the current site’s URLs:

• every page in the current sitemap,
• pages found by crawling the site,
• URLs receiving organic traffic in analytics,
• URLs with impressions in Search Console,
• URLs with inbound links from other sites.

The last three matter most. A page that is not in the navigation but still receives search traffic or links is easy to lose and expensive to lose.

2. Decide what happens to each URL

For every URL, choose one of:

• Keep, the same URL continues to exist.
• Move, the content moves to a new URL, with a permanent (301) redirect from the old one.
• Merge, several thin pages become one stronger page; each old URL redirects to it.
• Retire, the content is genuinely obsolete. Redirect to the most relevant equivalent if one exists; otherwise return a proper 404 or 410.

Avoid redirecting everything to the homepage. It discards the relevance the old pages had and is often treated like a missing page.

3. Protect content that earns traffic

Redesigns frequently replace detailed, specific pages with shorter, more “designed” versions. If a page ranks because it answers a question thoroughly, keep that substance. Improve it, restructure it, make it easier to read, but do not strip out the information that earned its position.

4. Get the technical foundation right before launch

• Canonical URLs point to the correct final canonical page.
• The XML sitemap lists only indexable, canonical URLs.
• Robots rules allow crawling of the production site, and the staging site’s blocking rules are not copied to production.
• Page titles, meta descriptions and headings are unique and meaningful.
• Structured data describes what is actually on the page.
• Internal links point directly to final URLs, not through redirects.
• Important content is rendered as HTML, not only after client-side scripts run.
• Pages are fast and accessible on mobile.

5. Launch in a controlled way

Launch when someone can watch the result, not at the end of a Friday. Keep the redirect map, the crawl of the old site and the Search Console property ready to compare.

6. Verify in the first days after launch

• Crawl the new site and test every old URL against the redirect map.
• Check for redirect chains and loops.
• Confirm no unintended noindex tags or robots blocks.
• Submit the new sitemap in Search Console and watch coverage reports.
• Confirm analytics and conversion tracking are firing on the new templates.
• Test every form end to end.
• Watch impressions and clicks for the most valuable pages.

Some fluctuation after a large migration is normal. Sustained drops on specific pages usually point to a specific cause, a missing redirect, a changed canonical, thinner content, and can be fixed if they are noticed.

Who should own each step

Step	Typical owner
URL inventory and traffic data	Search specialist or the team operating the site
Keep, move, merge or retire decisions	Business owner with search input
Redirect map	Search specialist, implemented by developers
Content preservation and improvement	Content lead with subject-matter experts
Technical checks before launch	Developers, verified by the search specialist
Post-launch monitoring	Whoever operates the site after launch

Problems usually appear where ownership is unclear, most often in the last row.

Special cases

Changing domain. Everything above applies, plus domain-level redirects, a change-of-address notification in Search Console and updates to external profiles and links you control. Expect a longer period of fluctuation.

Changing platform without changing design. Easy to underestimate. URL formats, rendering, metadata handling and structured data can all change underneath an identical-looking site.

Merging several sites into one. Each site needs its own inventory and redirect map, and overlapping content needs deliberate consolidation rather than duplication.

Common migration mistakes

• Launching with the staging site’s noindex or robots blocking still active.
• Redirecting every old URL to the homepage.
• Leaving internal links pointing at old URLs, creating chains of redirects.
• Dropping content that ranked because it did not fit the new design.
• Changing analytics setup at the same time, so nobody can tell what actually changed.

What to watch in the first three months

Coverage and indexing reports, impressions and clicks for the most valuable pages, crawl errors, organic inquiries, and page speed on real devices. Compare against the pre-launch baseline you recorded, which is one more reason to record one.

Why operation after launch matters

Most migration damage is done in the weeks after launch, by problems nobody was checking for. A team that is still responsible for the property after go-live catches them while they are cheap to fix.

That is why Colorbull’s builds include managed operation: Search Console monitoring, indexability, redirects, metadata, schema, sitemap and robots health continue as part of the operating base. If you are planning a redesign, request an assessment and we will include a view of your current search footprint and what a migration would need to protect.

---

About this guide. Written by Colorbull Agency. Colorbull prices quoted here come from our published pricing and change only when that page changes. Market figures are broad planning ranges, not quotes, every engagement is scoped after an assessment.

Related services: SEO & AI Search Visibility · Custom Web Design & Development · Managed Websites