Website Redesign SEO Checklist: What Must Be Preserved Before Launch

A website redesign can improve usability, accessibility, conversion paths, and visual clarity—but it can also disrupt organic search performance if important signals are changed or lost. The safest approach is to treat SEO preservation as a release requirement, not a final review task.

This website redesign SEO checklist covers the main items to audit before launch: URL structure, content, metadata, internal links, redirects, canonicals, structured data, crawl controls, analytics, performance, accessibility, and post-launch monitoring. It is designed for marketing teams, business owners, developers, and designers coordinating a redesign.

What should be preserved during a website redesign?

Before launch, preserve the signals that help search engines understand your pages and help users reach them:

• Important URLs and their search intent
• Valuable page content and heading structure
• Title tags, meta descriptions, and indexation directives
• Internal links and navigational relationships
• Canonical URLs and structured data
• Image context, alt text, and media assets
• Analytics, conversion tracking, and reporting continuity
• Mobile usability, accessibility, and page performance

Not every existing element must remain unchanged. A redesign is often the right time to consolidate weak pages, improve content, or simplify navigation. The key is to document what is changing, why it is changing, and how important URLs and signals will be handled.

1. Establish a pre-redesign SEO baseline

Start by recording the current site before templates, content, or URLs are modified. This baseline gives the team something to compare against after launch and helps identify pages that cannot be accidentally removed.

Capture the current site inventory

• Export all indexable URLs, including important landing pages, blog posts, resource pages, and location pages.
• Record organic traffic, conversions, rankings, impressions, clicks, and top landing pages from your analytics and search platforms.
• Identify pages with backlinks, referring domains, strong engagement, or meaningful business value.
• Save current title tags, meta descriptions, headings, canonicals, robots directives, status codes, and structured data.
• Document the current XML sitemap, robots.txt file, navigation, footer links, and major internal-link paths.

A crawl is useful, but do not rely on a crawl alone. Check analytics and search data to find pages that may be poorly linked internally yet still attract valuable visitors.

Create a page decision log

For every existing URL, assign a clear outcome: keep, revise, consolidate, redirect, or retire. Include the reason for the decision and the destination URL where applicable. This log becomes the foundation for content migration, redirect mapping, QA, and stakeholder sign-off.

2. Map old URLs to new URLs before development ends

URL changes are one of the most common sources of redesign-related search disruption. A redirect plan should be created while the information architecture is still flexible—not after the new site is already live.

Use a one-to-one redirect to the closest relevant replacement. Avoid sending many unrelated URLs to the homepage simply because it is available. A redirect should help both users and crawlers understand where the original resource moved.

Test for redirect chains, loops, incorrect protocols, trailing-slash inconsistencies, and redirects that point to irrelevant content. Update internal links so they point directly to final URLs rather than relying on redirects.

3. Protect content and search intent during migration

A visual redesign can unintentionally remove the wording that explains what a page is about. Preserve the content that supports the page’s purpose, then improve it where the new user experience exposes gaps.

Review each important page for:

• A clear primary topic and user need
• Unique, useful body copy
• Descriptive headings and logical hierarchy
• Relevant supporting sections and calls to action
• Accurate claims, examples, dates, and product or service details
• Search-relevant text that is visible and accessible to users

Do not hide essential content behind interactions solely to create a cleaner layout. Accordions, tabs, and expandable sections can be appropriate for usability, but important information should remain discoverable and technically accessible.

For editorial content, preserve publication dates, author information, category relationships, images, and related-article links where they contribute to context or trust. If content is consolidated, ensure the replacement page fully addresses the old page’s intent before redirecting it.

4. Preserve titles, descriptions, headings, and image context

Metadata should be migrated deliberately rather than regenerated from generic templates. Review high-value pages individually and use scalable rules only where they produce accurate results.

• Keep title tags specific, descriptive, and aligned with the page’s primary topic.
• Write meta descriptions for clarity and relevance; do not treat them as a substitute for page content.
• Use one clear primary heading and organize subheadings in a logical sequence.
• Retain meaningful image filenames, captions, and alt text where appropriate.
• Check Open Graph and social-sharing metadata if social distribution matters to the business.

Do not copy the same title, description, heading, or alt text across large groups of unrelated pages. Template logic should include page-specific variables and sensible fallbacks.

5. Review internal linking and information architecture

Redesigns often change menus, footer structures, breadcrumbs, filters, and cross-linking. These changes affect how users navigate and how search engines discover and interpret important pages.

Before launch, confirm that:

• Every important indexable page is reachable through useful internal links.
• Primary navigation reflects the approved information architecture.
• Breadcrumbs, where used, match the visible page hierarchy.
• Links use descriptive, relevant anchor text.
• Retired or renamed pages are removed from navigation and content links.
• Pagination, faceted navigation, search results, and filter URLs have an intentional crawl strategy.

Design and SEO decisions should be made together here. A visually elegant navigation system can still create unnecessary depth, obscure key content, or generate large numbers of low-value URLs. For broader guidance on coordinating visual systems and user-facing structure, see the design services resource.

6. Preserve canonical tags, robots directives, and indexation controls

Technical templates should be checked in the staging environment and again in production. A staging site may intentionally block crawling, but those restrictions must not be carried into the live environment by accident.

• Confirm canonical tags use the preferred protocol, hostname, and URL format.
• Check that canonical URLs are self-referencing where appropriate and point to live, indexable pages.
• Review noindex, nofollow, nosnippet, and other robots directives.
• Verify robots.txt does not block important assets, directories, or pages.
• Remove temporary staging authentication and crawl restrictions at launch.
• Check HTTP-to-HTTPS and hostname redirects.

Canonical tags are signals, not substitutes for redirect mapping or consistent internal links. If a page has permanently moved, use a redirect. If duplicate or near-duplicate versions remain, define the canonical strategy and test it.

7. Rebuild and validate structured data

Structured data is frequently lost when a site moves to a new CMS or template system. Inventory the markup currently in use, determine which types remain accurate, and implement them in the new templates.

Validate that structured data:

• Describes content that is visible and accurate on the page
• Uses the correct page-specific values
• Does not contain outdated names, URLs, prices, dates, or images
• Remains consistent with the site’s canonical URL
• Is present on the templates where it is intended to appear

Do not add schema solely because it is available. The correct markup depends on the page type and the information genuinely presented to users.

8. Validate the new CMS and content migration

The CMS controls many SEO details that are easy to overlook during a redesign. Test both migrated content and the editing workflows your team will use after launch.

CMS migration checks

• Existing page slugs are retained or mapped to approved replacements.
• Authors, categories, tags, dates, and media references migrate correctly.
• Editors can manage titles, descriptions, headings, alt text, canonicals, and redirects where appropriate.
• Draft, preview, attachment, and search-result URLs follow an intentional indexation policy.
• Templates do not create duplicate pages through parameters or alternate paths.
• Broken internal links and missing media are identified before launch.

Content migration should be tested with representative samples: a standard page, a long article, a page with images, a page with structured data, a redirect, and any specialized template used by the business.

9. Test performance, mobile usability, and accessibility

SEO preservation is not limited to rankings and metadata. A redesign should maintain or improve the experience for people using phones, assistive technology, slow connections, and different browsers.

• Test responsive layouts at common viewport sizes.
• Check navigation, forms, menus, dialogs, and interactive elements with keyboard input.
• Confirm sufficient color contrast, visible focus states, meaningful link text, and usable heading structure.
• Optimize image dimensions, formats, loading behavior, and responsive delivery.
• Reduce unnecessary scripts, styles, third-party requests, and layout shifts.
• Test important templates on real devices and representative network conditions.

Performance work should prioritize real user tasks. A technically lightweight page is not successful if its navigation, forms, or primary content becomes harder to use.

10. Reconnect analytics and conversion tracking

Analytics continuity is essential for distinguishing a ranking problem from a measurement problem after launch. Document every tracking dependency before the old site is retired.

Verify:

• Analytics tags load on the new templates.
• Consent and privacy controls work as intended for the site’s audience and jurisdictions.
• Forms, phone links, downloads, purchases, bookings, and other priority events are recorded.
• Search Console or equivalent property settings cover the relevant domain and URL variations.
• Campaign parameters and referral attribution are not stripped by redirects or new scripts.
• Dashboards and alerts use the new URL structure where necessary.

Complete a test conversion on staging when possible, then repeat a controlled test in production immediately after launch.

11. Run a launch-day technical QA

Before announcing the new site, crawl the production environment as a search engine would. Compare it with the baseline and the approved migration plan.

1. Confirm the production site is accessible and the intended canonical domain resolves.
2. Check status codes for key old and new URLs.
3. Test redirect rules at scale and investigate chains or unexpected destinations.
4. Verify titles, headings, canonicals, robots directives, and structured data on representative templates.
5. Check XML sitemaps and robots.txt.
6. Test navigation, forms, search, media, checkout or booking flows, and critical integrations.
7. Review mobile layouts, accessibility basics, and performance on important pages.
8. Submit updated sitemaps and inspect priority URLs in the relevant search platform.

Keep the old site, crawl exports, redirect file, and baseline reports available for comparison. Do not delete them immediately after launch.

12. Monitor the first days and weeks after launch

Post-launch monitoring is part of the redesign, not an optional follow-up. Some issues appear only when real users and crawlers encounter the new site.

Monitor:

• 404 and 5xx errors
• Redirect errors and unexpected redirect volume
• Organic clicks, impressions, rankings, and landing pages
• Indexed-page counts and excluded-page reasons
• Traffic and conversions by landing page
• Core templates, forms, search, and checkout or lead flows
• Server logs or crawl activity where available
• Page speed and real-user experience signals

Investigate changes by URL and template, not only at the domain level. A decline concentrated in one migrated directory may point to a mapping or template problem, while a tracking issue may affect reporting without changing search visibility.

Practical rule: Do not declare a redesign successful based on launch-day appearance alone. Confirm that users can find, load, understand, and convert on the pages that matter.

Common redesign SEO mistakes to avoid

• Launching with the staging noindex directive still active
• Changing URLs without a complete redirect map
• Redirecting every retired page to the homepage
• Replacing useful copy with image-only layouts
• Allowing the CMS to generate duplicate or thin archive pages
• Removing internal links that support important pages
• Dropping structured data during a template rebuild
• Forgetting analytics events and consent behavior
• Measuring only traffic while ignoring conversions and indexation
• Making large post-launch changes before identifying the actual cause of a problem

How this checklist fits into a broader redesign plan

SEO preservation works best when it is integrated with discovery, content strategy, information architecture, UX, development, QA, and measurement. For a broader look at the redesign process and project scope, review the guide to redesigning a website without losing SEO. If you are evaluating outside support, the website redesign agency evaluation guide can help clarify questions about process, migration ownership, and post-launch support.

Use this checklist as a shared handoff document between marketing, design, development, content, and analytics teams. For the service scope itself, visit website redesign.