Skip to article content

Changing your website: what to check to look after search visibility

Before launching your new website, identify pages that receive visits, addresses that will change and who will check the transition. Use this guide to prepare the work with your team.

Establish what is actually changing

Looking after search visibility during a website change starts with knowing which existing pages will remain, where they will be and how visitors will reach them. Prepare that transition before launch.

Changing colours and typography while retaining pages and content is different from changing domains, reorganising services or moving to another platform. Ask for a list covering addresses, copy, navigation, languages and functions. If rebuilding is still undecided, first compare a focused improvement, partial renewal and a new website.

A hosting change that keeps public addresses has its own process. Google distinguishes it from moving to new URLs in its hosting migration guide. Establish which situation applies before agreeing checks.

Keep a record of the pages already serving your business

Gather pages that receive search visits, bring enquiries or hold information customers need. Include addresses used in campaigns, links from other websites and downloadable documents. The homepage is only part of that inventory.

If you have Search Console, its performance report shows pages, queries, impressions and clicks. Save a baseline with its period and filters, using Google’s report explanation. Compare this with available business information; a low-traffic page may still be necessary.

Record gaps where data is unavailable. Start with known pages and journeys and extend the inventory with your team. You do not need an invented financial value for every address to decide it deserves a planned transition.

Map old addresses to their intended destinations

This document prevents pages disappearing from the project without a decision about their future. A shared spreadsheet is enough if decisions have owners and checks.

A record for each page or equivalent group of pages
RecordPurposePlanned check
Current addressIdentify the page and its purpose.Open it and keep the reference.
DecisionKeep, move, combine or retire.Confirm necessary information remains covered.
DestinationIdentify the corresponding page when content moves.Open the destination and review its content.
Treatment of the old addressAgree a redirect or retirement for the situation.Test the old address after launch.
Owner and outcomeIdentify who prepares and validates it.Record the date, evidence and open issues.

For a permanent move, the team can configure a server redirect to the equivalent page. Google documents 301 and 308 redirects and how they differ from temporary redirects. The technical choice depends on the circumstances.

Avoid making the homepage the default destination for every retired page: someone looking for a service or product needs relevant information. Record cases without an equivalent so the team can decide how to handle them.

What to check before approving launch

Choose pages and tasks to review with your team on the test version: a service, a product category, a product, a form and the languages you use. Check content as well as appearance. Titles, links and essential copy belong in delivery too.

  • Planned addresses exist and show the correct content.
  • Menu and body links lead to the intended place.
  • Forms and important functions pass the agreed tests.
  • The team has prepared redirects and the sitemap, and reviewed which pages can be indexed.
  • Someone owns publication, verification and any issues arising from the change.

The test version may use a noindex instruction to keep it out of search results. Private information also needs access controls: noindex does not stop someone opening the page. Before the public launch, confirm which restrictions should be removed and which should stay. Google explains how that instruction works; blocking a page in robots.txt is a different measure.

An example: combining two service pages

Fictional example explaining a decision. It does not describe a client migration or results.

A business has two service pages and wants to combine them. Before removing either, it compares their information, the queries they addressed and questions the sales team still receives.

If the new page adequately serves both needs, the map can record that shared destination and checks of old addresses. If one service is barely mentioned, resolve the content gap first: a redirect does not replace missing information.

The decision is documented and can be reviewed with people who know the business. It does not depend on the new design looking more attractive.

Checks continue after the new website goes live

At launch, open old and new addresses from the sample, test functions and save the results. Subsequently review important pages in available search tools and compare trends over meaningful periods. Analytics should also continue recording the enquiries, purchases or other actions you need to understand.

Google explains that migrations can bring fluctuations while pages are recrawled and reindexed. Its guide to moves with URL changes covers preparation and monitoring. Passing initial checks does not guarantee unchanged rankings.

If visits fall, use the saved baseline to separate search changes from measurement changes. When a particular page is missing, check its indexing status before attributing the drop to the whole redesign.

Include these checks in the project

Document the inventory to be prepared, who will validate destinations and what review follows publication. If teams are changing, share that record during the provider handover.

Nodo91 can assess your website’s search visibility signals and help define appropriate checks within an agreed scope. The proposal sets out any internal investigation and migration work separately.