Old and revised paper page layouts arranged across a design studio wall
Web Development

Website Redesign SEO Checklist: Protect Your Search Visibility at Launch

By Drashti Patel8 min readUpdated

A redesigned website can look better while making important pages harder to find. The risk often comes from small decisions: changing a service address, removing useful copy, or leaving a test-site setting active. This website redesign SEO checklist helps business owners and their development teams plan those decisions before launch and investigate problems afterwards.

1. Decide what is actually changing

Start by separating a visual refresh from a migration. Updating colours and layouts while retaining page addresses is different from replacing the platform, combining services, and moving to another domain. Write down which of those changes your project includes. Give each one an owner and a review step.

Google recommends changing one major thing at a time when moving a site, and warns that search visibility can fluctuate while changes are processed. Treat that as a reason to reduce unnecessary complexity, rather than a promise that a careful redesign will preserve every ranking.

For example, a local service business could improve its navigation and enquiry experience first, keeping familiar service URLs. A domain change could be a separate project if there is no business reason to combine it. This is a planning example, not a reported client result.

2. Record what the existing website contributes

Before approving page removals, assemble a simple inventory. Include current URLs, page purposes, enquiries where measurable, and available search performance. Add downloadable brochures and important images. Ask the team which information comes from measurement and which is an assumption.

  • Export available landing-page and enquiry data for a representative period.
  • Record important search queries and landing pages from Search Console.
  • List URLs used in advertising, business listings, email signatures and printed material.
  • Save current page titles, headings, copy and a backup of the existing site.

Choose a comparison period that makes sense for the business. A holiday week may be a poor baseline for ordinary trading. Keep the measurement setup consistent where possible, and note any tracking changes alongside the release date. Otherwise a broken enquiry event can look like a loss of customers.

Give priority to pages that answer important customer questions even when their traffic is modest. A detailed service page may help a few qualified buyers make a decision. Page value should not be reduced to a single traffic number.

3. Map old addresses to purposeful destinations

Create a spreadsheet with one row per existing URL. Decide whether to keep it, revise its content, merge it into a relevant replacement, or remove it. Review this document before the new navigation is finalised. It is much easier to spot a missing service in a table than during launch.

An illustrative URL decision sheet
Existing pageDecisionLaunch check
/services/web-designKeep the address; improve contentPage loads and describes the same service
/old-mobile-servicesMerge into a relevant app service pagePermanent redirect reaches the replacement
/offers/expired-eventRemove with no equivalent replacementHelpful missing-page response with correct status

Have a business reviewer approve the relevance of each replacement. A technically working redirect can still confuse someone who expected a specific service. For a permanently moved page, Google recommends a permanent server-side redirect such as 301 or 308. Ask developers to test the response, not just whether the browser eventually shows something.

Point old addresses directly to their final destinations where possible. Include variations that people actually use, and test representative deep links. Google’s migration guidance recommends 404 or 410 responses for removed content without a suitable replacement; redirecting every deleted page to the homepage is not a useful substitute.

4. Improve the design without losing the answer

Review the old and proposed versions of each important page side by side. Does the new page still explain the service, who it suits, what is included, and how to enquire? A short slogan and a large photograph may be attractive, but they do not necessarily replace a useful explanation.

You do not need to preserve every sentence. Remove repetition, correct outdated material, and make information easier to scan. Keep the customer question visible during editing. Ask someone outside the project to find a specific answer without coaching them through the navigation.

Content review question: What could a customer learn or do on the old page that they can no longer learn or do here?

Assign approval responsibility for service claims and contact details. Ask the development team to retain descriptive headings, meaningful link labels and accessible image alternatives. If the redesign also needs a clearer project scope, use a brief to document these responsibilities before requesting implementation estimates.

Use our website development brief guide to define responsibilities

5. Check the signals behind each page

Ask for a technical handover report that shows the final URL, response status, title, description, canonical address and indexability of important pages. Include examples from each page template, not only the homepage. Business owners do not need to inspect source code themselves, but they should know who has checked it.

Canonical tags identify a preferred URL among duplicate or similar pages. Google treats redirects and canonical annotations as strong canonicalisation signals, while sitemap inclusion is weaker. Keep those signals consistent: use final preferred URLs in internal links and the sitemap, and avoid canonicals pointing to the staging domain.

Include a launch-specific check for test-environment restrictions. Google’s site-move guidance calls out removing temporary noindex directives and crawl blocks when the public site goes live. Agree exactly who makes that change and who verifies the production response afterwards.

For websites built with JavaScript, ask the team how search engines can access the primary page content and navigation. Verify actual production output. A development preview that displays correctly on one laptop is not enough evidence for a release decision.

6. Rehearse the customer journey before launch

Several phones and a tablet arranged for responsive layout testing
Test the mobile journey alongside redirects and page content. Generated illustrative photography.

Create a short acceptance sheet covering both search entry points and customer actions. Start from an old service link, reach the replacement page, read the content on a phone, and submit an enquiry. Check the confirmation and receipt of the message. Use agreed test details so staff can recognise test submissions.

  • Test important old URLs and verify their final destinations.
  • Check menus, text wrapping, image loading and forms on mobile and desktop.
  • Open a genuinely unknown address and check the missing-page response.
  • Review page metadata and sharing images on the production build.
  • Confirm backups, release access, rollback responsibility and the support contact.

Plan the release when the people needed to resolve problems are available. Set a clear threshold for postponement: broken enquiries or inaccessible core services deserve attention before launch. Keep a list of cosmetic issues separate so the team can make a proportionate decision.

7. Monitor evidence, then investigate changes

On launch day, repeat the critical checks on the public domain. During the following days and weeks, compare important page groups and customer actions with the baseline. Keep a dated change log so an unexpected decline can be connected to a deployment, tracking edit or content decision.

Search Console provides performance and indexing information; URL Inspection helps investigate individual pages. Use these alongside server responses and enquiry records. An indexing report and a completed enquiry count answer different questions, so neither should replace the other.

If results change, narrow the problem before rewriting the entire site. Is it one service, one device category, or all landing pages? Are visits down, or only recorded conversions? Check broken links, redirects, indexing restrictions and tracking first. Assign each finding to an owner and verify the fix.

A useful redesign handover contains more than approved screenshots: it includes a URL map, retained customer information, tested journeys and a monitoring owner. Start with those four deliverables. Kesari Nandan Infotech’s existing services include website development and digital marketing; these areas should be coordinated when planning a redesign.

Explore our website development and digital marketing services

A little more clarity

Frequently asked questions

Can a website redesign affect existing search rankings?

Yes. Changes to page addresses, content and technical access can affect how pages are discovered and understood. A planned migration reduces avoidable mistakes, but no checklist guarantees unchanged positions.

Should we change every URL to match the new navigation?

No. Navigation labels and page addresses can be considered separately. Keep useful existing URLs unless there is a clear reason to change them, and document replacements before development begins.

What is the difference between a redirect and a canonical tag?

A redirect sends the visitor to another address. A canonical tag indicates a preferred version of similar content without moving the visitor. Choose the mechanism that matches the actual page relationship.

Can we send all removed service pages to the homepage?

That often leaves visitors searching again for the information they expected. Choose a genuinely relevant replacement for each page. Where none exists, use an appropriate missing-page response instead of an unrelated destination.

Do we need to keep all the old website copy?

No. Keep useful answers and accurate information, while improving clarity and removing obsolete material. Review important pages with someone who understands customer questions before approving substantial cuts.

Who should own the redirect spreadsheet?

Assign one project owner to maintain the list. The business should approve destination relevance, while the development team implements and tests the responses. Keep the approved version with the handover documents.

How should we test a redesign when most enquiries come from phones?

Prioritise the full mobile journey: open an old link, read the service, use the form, and confirm that the message reaches your team. Include long text, validation errors and a small screen.

Does submitting a sitemap guarantee that new pages will be indexed?

No. A sitemap is a discovery and canonicalisation signal, not an indexing promise. Also check that important pages are accessible, internally linked and suitable for indexing. Investigate individual problems through Search Console.

Should we launch a new domain and a new platform together?

Separate major changes when practical so faults are easier to isolate. If business constraints require a combined launch, expand the migration plan, assign clear owners and rehearse the critical checks.

What if enquiries drop but search traffic appears stable?

Check the enquiry journey and measurement before assuming a ranking issue. A form delivery failure, changed event name or confusing mobile layout can affect enquiries independently of search traffic.

When can we consider the redesign handover complete?

Agree acceptance criteria before launch. Require evidence that key pages and redirects work, enquiries arrive, access is transferred, and someone owns monitoring. Keep unresolved items visible with a named owner and next review date.