Technical SEO Checklist for a Website Redesign

Before the redesign: create an SEO inventory

Crawl the current website and combine that list with sitemap, analytics, Search Console and backlink data. Record each indexable URL, title, canonical, status code, organic traffic and conversion role where available. This becomes the control sheet for content decisions and launch testing.

Mark each URL as keep, improve, consolidate, redirect or retire. When a URL changes, map it to the closest relevant replacement. Do not redirect every removed page to the homepage; an irrelevant destination can confuse users and may be treated as a soft 404.

• Export current URLs, metadata, canonicals and status codes.
• Identify pages with traffic, conversions and valuable backlinks.
• Preserve content that continues to satisfy search intent.
• Prepare a one-to-one old-to-new URL mapping where possible.
• Benchmark organic traffic, rankings and key landing pages.

On staging: verify crawl and page signals

A staging environment may be protected from indexing, but that protection must not reach production. Review robots.txt, robots meta tags and response headers as part of the launch checklist. Confirm that indexable pages render their important content and links without requiring unusual user actions.

Each preferred page should declare an accurate self-referencing canonical. Titles and descriptions should be unique and useful, headings should reflect the visible page structure, and internal links should point directly to final URLs rather than old addresses or redirecting paths.

Redirects, status codes and removed content

Google recommends server-side permanent redirects such as 301 or 308 when URLs move. Redirect directly to the final relevant destination and avoid chains because each extra hop adds latency and another failure point. Test the complete mapping in bulk before and after launch.

Keep genuinely removed content as a clear 404 or 410 when no suitable replacement exists. Preserve redirects for at least a year for a site move, and preferably longer when people or external sites may still use the old addresses.

Launch-day technical SEO checklist

Crawl production as a search engine would and compare the result with the approved inventory. Inspect representative service pages, articles, categories and forms manually. Submit the canonical sitemap in Search Console; you do not need to request indexing for every page individually when the pages are internally linked and included in a valid sitemap.

• Confirm HTTPS, preferred host and a single canonical version of each URL.
• Remove unintended noindex directives and production crawl blocks.
• Test old URLs, redirect destinations, 404s and redirect chains.
• Validate titles, canonicals, structured data and social metadata.
• Check navigation, breadcrumbs and contextual internal links.
• Publish an XML sitemap containing canonical indexable URLs.
• Verify analytics, Search Console ownership and conversion events.
• Test mobile usability, forms and critical page performance.

Monitor the redesign after launch

Expect Google to recrawl and reprocess changed pages over time, and allow for temporary ranking fluctuation after significant URL changes. Monitor the Indexing report, sitemap processing, crawl errors, organic landing pages and server logs. Compare results with the pre-launch benchmark instead of relying on total traffic alone.

Measure real-user performance as data accumulates. Core Web Vitals focus on loading, interaction responsiveness and visual stability, but they should be reviewed alongside accessibility, content usefulness and conversion behavior. Fix template-wide problems first because one change can improve many pages.