Blog / Technical SEO /

The technical SEO questions to ask before a redesign

The new design looks great. Cleaner, lighter, very modern. Then launch week arrives and half the old URLs return a 404, the headings have vanished from the templates and nobody can say where the product pages went.

A redesign can improve how a site looks while quietly changing URLs, headings, content, internal links or crawl access. Ask the technical SEO questions before the work starts, and you keep the routes that matter while still making real design improvements.

Inventory the current site

Record the important page types, their URLs, traffic and business purpose. Include product and category pages, articles, forms, local pages and resources. Flag pages with backlinks or ongoing customer use. A crawl, analytics and Search Console reports all help, but each has limits. Save the exports and dates so you can compare later.

Then map current navigation, redirects, canonical signals, robots directives, sitemap behaviour and structured data. Note what the CMS, theme, apps or server generate. Ask the developers where content and templates will move. When I look at a redesign plan, that’s the first thing I check: a “visual only” change rarely leaves the technical structure alone.

Decide what changes and what stays

Build a URL mapping for every route that will change. For each old URL, pick a relevant destination or a clear retirement path. Don’t point everything at the homepage. Plan how to keep page content, metadata, headings, internal links, image alt text and language versions. Decide whether pagination and filters change.

Set acceptance criteria for templates: correct status, indexable where intended, coherent canonical, useful headings, accessible navigation, mobile rendering and no broken internal links. Confirm how staging will be kept out of the index and how production launch will be verified.

Test before and after launch

Crawl staging and compare page types with the current site. Test forms, navigation, search, product flows and key events, and check rendered output wherever JavaScript is involved. Keep a list of representative URLs and user tasks. At launch, verify redirects, robots access, sitemaps and high-priority pages, then watch logs and reports after deployment.

Assign owners and recovery

Name who approves URL decisions, content migration and technical checks. Agree a rollback or correction process and what triggers it. Bring SEO review in alongside design, engineering, content and operations so fixes aren’t left to the end.

Keep launch day controlled

Write a short launch checklist with representative URLs, expected statuses, redirect destinations, form tests and key event checks. Assign a person to each item and report issues through one channel. Avoid changing unrelated campaign or analytics settings in the same window. A smaller change set is easier to diagnose.

Check that monitoring can reach the new site and that old systems aren’t still serving cached content. Confirm domain, protocol, sitemap and robots behaviour. Make sure staging protections don’t carry over to production, and that production content isn’t exposed through staging.

Communicate what changed

Tell content owners which URLs or templates moved, where pages were redirected and what to check after launch. Share the URL map and the known exceptions. A redesign affects more than the engineering team, and support may get questions about changed navigation.

After launch, review errors and search reports, but don’t react to a single fluctuation without checking the evidence underneath. Keep a timeline of fixes and note any concurrent changes.

Include content and accessibility in migration

A migration should keep useful copy and accessible labels, not just URLs. Check headings, image descriptions, link text, form labels and language versions. If content is rewritten, track whether the approved facts and meaningful internal links survive. A cleaner design can still strip out essential context.

Review the new mobile layout and performance on representative templates. Check the main content appears without blocking scripts and interactive elements still work. If a performance change affects third-party tools, understand what functionality you lose before removing them.

Keep evidence before and after

Save a crawl, URL list, key screenshots and measurement definitions before launch, and repeat comparable checks afterwards. That shows what changed and helps diagnose problems, though it can’t isolate every cause. Record concurrent campaigns, tracking changes and inventory shifts.

Check continuity for returning visitors

Returning customers rely on bookmarks, saved product pages and links in old order emails. Test those routes after the redesign. A redirect should keep access to a relevant item or explanation. If an item is retired, say so plainly and offer a replacement only when one really fits.

Review forms and account pages carefully. A design change can alter validation, confirmation or privacy messaging. Test what happens after errors and make sure submissions reach the right team. Don’t use real customer data in staging tests unless the environment and access controls are approved.

Prepare customer support with a simple map of changed navigation and known issues. Keep the old and new URL maps together so later audits can tell planned redirects from accidental gaps. And review analytics definitions before comparing results, especially if tags or consent behaviour changed at launch.

So here’s the question to put to your team before design sign-off. Can you say what will happen to every important URL, and how you’ll prove the new site works after launch?