DTC technology × growth systems — built to compound.
DTCUP / FIELD NOTES / ACQUIRE

Plan a Website Migration Without Losing Track of Search Traffic

Connect page inventory, destination decisions, content, technical checks and post-launch investigation in a practical website migration plan.

Published Apr 20, 2026Updated Sep 20, 202611 min read
Jack Hu
Jack Hu

7 years of experience building and operating brand websites, specializing in website development, paid advertising and SEO. Built a brand website from launch to US$10 million in annual sales.

The Short Answer

Define which infrastructure, addresses and content will change, then inventory the pages and assets that serve real customer tasks. Decide useful destinations, preserve the information that matters and verify that redirects, canonical preferences, indexing controls and site references match the plan.

Test the release candidate and the live result, with named owners and a recovery boundary that protects current business activity. Treat sitemap submission as one check, not proof of completed indexing. Investigate changes by page group, measurement and concurrent business conditions; maintain redirects and the decision record after launch.

Key takeaways

  • A rebuild, hosting move and domain change need different checks.
  • Approve destinations by customer purpose rather than matching URL words.
  • Verify delivered behavior and the public result, not only saved settings.
  • Diagnose post-launch changes before assigning a cause or making a broad rollback.

A rebuilt website can look better while making useful pages harder to find. Product addresses change, guides disappear from navigation, old links reach the wrong destination, or a setting used to hide the preview remains active after launch.

I would treat search continuity as part of the rebuild from the beginning. The team needs to know what visitors currently find, what each important page will become and how it will prove that the new experience works. An SEO check requested the evening before launch cannot easily recover decisions that were never recorded.

The plan below connects the page inventory, content, technical migration and business review. It applies whether the website uses Shopify, WordPress or another system. Platform details differ; the responsibility for delivering a useful destination remains with the team making the move.

Define what is actually changing

Separate a hosting change, a visual redesign, a content rewrite, a platform move and a change of domain. They can happen together, but they create different questions. Keeping the same visible address does not establish that its content, navigation or technical behavior stayed the same.

For a move that keeps user-visible URLs unchanged, Google's hosting-change guidance emphasizes preparing and testing the new infrastructure, switching traffic and monitoring before retiring the old setup. That is different from mapping old addresses to new ones.

Write the scope in ordinary language. A hypothetical homewares brand might keep its domain, move to another platform, change product URL patterns and rewrite selected buying guides. The product mapping and the rewritten guides need their own review; neither is proved correct by a working homepage.

Where possible, avoid adding unrelated changes merely because a rebuild is already underway. If the business must change several things together, record them. The aim is to understand the consequences, not to promise that a particular project sequence removes all search risk.

Give search work an owner with access to the people controlling content, development, hosting and measurement. The store launch and migration guide covers the wider customer and operating handoffs that this search plan must fit within.

Build an inventory that reflects the real website

Collect addresses from the content system, current sitemaps, a permitted crawl, search reports and relevant traffic records. Compare the lists instead of assuming one export contains every useful destination. Record missing access or incomplete history so the inventory's limits remain visible.

Include products, categories, articles, important service pages and useful files or images whose addresses change. Also identify regional or language versions and customer-facing tools. An old campaign destination may still receive visits even if the current menu no longer links to it.

Build a working register with a row for each meaningful page or a carefully defined group. Suggested fields are old address, page purpose, content owner, observed demand, planned action, new address, review state and exceptions. Keep raw crawl findings separate from the approved decisions so an automatically discovered URL does not silently become a page you promise to preserve.

Prioritize review using business purpose as well as recent visits. A seasonal guide may look quiet outside its season. A support document may prevent costly confusion without creating many purchases. A high-volume page can also be obsolete. Use the evidence to ask why the page matters rather than letting a single metric decide its fate.

Google's site-move guide provides the underlying migration reference. The register is your team's operating document: it should show an explicit decision for the important destinations and name the person resolving each gap.

Decide the destination by customer purpose

Map the old page to the experience that best continues its job. Similar words in two URLs are not enough. A visitor looking for instructions for an older product should not be sent to a new product sales page simply because both contain the same product family name.

Use these hypothetical cases to make the decision concrete:

Old page and situation Decision to investigate Evidence before approval
Current product with a new platform address Continue the same product at its new address Product identity, variant and public information match
Useful guide whose address can remain Keep the address and improve the content The revised guide still answers its established reader task
Two guides genuinely combined into one Use the complete combined resource Important information from both survives in a usable form
Retired product with ongoing support needs Preserve a useful support destination where appropriate Owners can still find the information they came for
Obsolete page with no relevant replacement Decide an honest removal response The business has reviewed demand, obligations and remaining links

This is an editorial and customer decision before it is a redirect rule. Record why a destination is relevant. Ask a colleague unfamiliar with the mapping to follow representative old links and explain whether the result makes sense.

Do not approve a broad “everything missing goes to the homepage” rule. Google's move guidance warns against irrelevant redirects. A correct technical response should communicate the actual outcome; concealing every missing page behind a successful homepage response makes faults harder to find and visitors harder to help.

For repeated URL patterns, verify exceptions before turning the pattern into an automated rule. Similar slugs can refer to different variants, markets or past content. Keep the approved mapping and the generated implementation distinguishable so the team can inspect both.

Preserve the information that made the page useful

A migration is a good opportunity to remove confusing or outdated content, but a shorter page is not automatically a better replacement. Compare the old and new versions against the customer's task. Check the product facts, useful explanations, supporting images, instructions and relevant links.

For the hypothetical homewares brand, a buying guide might contain a dimension diagram customers rely on. A new template that imports the text but drops that diagram has not preserved the whole useful page. The same problem can occur with downloadable instructions or a comparison table hidden by a mobile layout.

Keep title, description, main heading and the visible introduction consistent with the actual revised content. Update the page's contents navigation when headings change, and preserve useful old fragment destinations where practical. Recheck topic assignments and site filters after import; a page in the database can still be difficult to discover through the website.

Review internal links as part of the reading path. If a guide recommends comparing products, the comparison destination should still exist and answer that next question. The internal-linking guide helps evaluate those relationships without turning the project into an arbitrary link-count exercise.

Keep a record of substantial content changes. If search performance later shifts, the team needs to know whether the page only moved or also changed its subject, evidence and purpose. A migration label should not hide a simultaneous editorial overhaul.

Make the new technical signals agree

Have the implementer explain how old routes, preferred page addresses, indexing controls and sitemaps fit the approved mapping. Check the delivered output rather than relying only on settings shown in an administration screen.

For permanent moves, Google's redirect documentation identifies server-side 301 and 308 responses as permanent redirect methods. A canonical tag is not the same action: it does not move the visitor to another page. Test the status and final destination of the actual request, including important parameters when they affect the customer experience.

Google's canonical guidance describes signals used to indicate a preferred version among duplicate or similar pages. Confirm that templates do not point production pages at a preview hostname, an unrelated product or an outdated URL. Keep internal references consistent with the intended destination; do not expect a tag to repair a contradictory site structure automatically.

Review indexing exclusions separately. Google's noindex guidance explains that the crawler must be able to access a page to read that rule. A robots.txt block and a noindex instruction are different controls. Remove preview-only restrictions from pages intended for search while preserving deliberate exclusions and actual access controls for private material.

For multilingual content, have the responsible specialist check the relationships between real language and market pages after the move. Also compare structured data with the visible product or article information. Importing old markup unchanged can leave old addresses or facts even when the visible template looks right.

Test the migration as a set of real journeys

Use automated checks for breadth and manual journeys for meaning. A tool can identify response codes and many broken references. A person still needs to decide whether an old buying guide now reaches a useful equivalent and whether the customer can continue from there.

Test representative page types and every high-consequence exception. Include a current product, a variant-specific route, a category, an article, an important file, a regional page and a deliberately removed destination where they exist. Record which samples were tested and which rules were checked across the full inventory.

The acceptance record can stay compact:

Check A useful result to record
Old address Observed response and final destination agree with the approved decision
Destination Correct content loads, important media works and the next customer action is possible
Search-facing output Intended canonical, indexability and relevant page information are delivered
Discovery Navigation, topic pages and internal links reach the appropriate new location
Measurement The defined visit and business actions remain observable within the approved tracking setup

Run the checks on the release candidate, then repeat the important ones publicly after launch. Preview access, hostnames and infrastructure can differ from production. State those differences in the test record rather than claiming that one environment proves the other.

Agree on what blocks launch. A missing lower-priority image may have an owned repair plan. A shared template that excludes all products from indexing or sends them to the wrong location needs a different decision. Make that distinction before deadline pressure arrives.

Launch with owners and a recovery boundary

Schedule a period when the relevant people can observe the release and respond. Save the approved mapping, content versions, configuration and suitable recovery material. Record what was deployed and when; a general “website updated” note is not enough for later investigation.

If the domain changes, check whether Google's Change of Address tool applies and follow its current requirements. Do not treat it as a routine step for every redesign or change of paths. Confirm access to the required properties before the launch depends on it.

Make the current sitemap available and verify it can be read. Google's sitemap guidance describes submission through Search Console and notes that submission is a hint rather than a guarantee of crawling or use. A successful submission is one check, not proof that the migration has been indexed correctly.

Define recovery in terms of the affected component. Reverting a template is different from restoring a database that has accepted new orders. Protect recent customer activity and involve the technical owner before a broad rollback. Search uncertainty alone is not a reason to overwrite current business records.

Keep the people owning paid destinations, email links and important partner references informed through the business's approved process. They need the actual destination changes and their timing, not a vague announcement that the new site is live.

Investigate post-launch changes before assigning a cause

Review technical health immediately, then watch search and business outcomes as sufficient data arrives. Separate missing pages, crawling failures and wrong destinations from changes in impressions, clicks and customer behavior. One blended traffic number cannot identify the problem.

Compare like with like: page groups, markets, devices and query types where the reports support them. Annotate promotions, stock, seasonality, advertising and tracking changes. If measurement changed during the rebuild, a difference in recorded visits may not describe a difference of the same size in actual visits.

For a fictional example, suppose article visits appear lower while order records remain broadly steady. First check whether the analytics implementation changed, whether the decline is isolated to migrated articles and whether their search impressions and destinations also changed. Those observations support different next actions. They do not justify immediately rewriting every page again.

Keep a prioritized investigation list with evidence and owners. Widespread server errors or a wrong shared directive deserve prompt attention. A small early reporting movement may need a defined review window and more context. Avoid both dismissing every decline as normal and reacting to every incomplete report with another major release.

Google's move guidance notes that search visibility can fluctuate while a move is processed. It does not promise a fixed recovery date for your project. Fix verified faults, preserve the change record and state the limits of the evidence when reporting progress.

Keep the migration record after the launch team leaves

Assign ownership of redirects, domains, content and monitoring to the people maintaining the website. Include renewal and hosting dependencies for any old addresses that still need to resolve. A redirect plan can stop working later if the infrastructure serving it disappears.

Google recommends retaining redirects for as long as possible, generally at least a year. Plan the ongoing responsibility rather than setting an automatic deletion date without review. Update controllable links to the intended destination and keep checking important incoming routes.

Close the project with the actual outcomes, unresolved issues and next review. The useful handover is a website the team understands and can maintain, plus a record explaining what moved and why. A launch celebration and a screenshot of the homepage are not that record.

Questions about migration and search traffic

Do we need redirects if the page addresses stay the same?

Not solely because the website was rebuilt. Verify that the same public addresses still deliver the intended content and technical behavior. Redirects are needed where the actual routing decision changes; a hosting-only move has different implementation work from a URL move.

Does submitting the sitemap complete the search migration?

No. It makes a list available to the search engine but does not verify the content, destinations, indexing state or customer journey. Check the live pages and monitor the move after submission. Keep the sitemap aligned with the site's intended current pages.

Should we reverse the migration as soon as traffic falls?

First identify a verified fault or a supported reason for the change. Check measurement, affected pages, search observations and concurrent business changes. Repair the responsible component where possible, and assess any broader rollback against current orders and data before acting.

Explore the SEO and website discovery guides for related decisions about useful pages, technical controls and maintaining visibility.

Sources

  1. developers.google.com — site-move-with-url-changes
  2. developers.google.com — site-move-no-url-changes
  3. developers.google.com — 301-redirects
  4. developers.google.com — consolidate-duplicate-urls
  5. developers.google.com — block-indexing
  6. developers.google.com — build-sitemap
  7. support.google.com — 9370220

Still have a question?Ask the DTCUP Community ↗

FAQ

Questions related to this insight.

Clear scope, practical constraints and direct answers for the decision ahead.

Do we need redirects if the page addresses stay the same?

Not solely because the website was rebuilt. Verify that the same public addresses still deliver the intended content and technical behavior. Redirects are needed where the actual routing decision changes; a hosting-only move has different implementation work from a URL move.

Does submitting the sitemap complete the search migration?

No. It makes a list available to the search engine but does not verify the content, destinations, indexing state or customer journey. Check the live pages and monitor the move after submission. Keep the sitemap aligned with the site's intended current pages.

Should we reverse the migration as soon as traffic falls?

First identify a verified fault or a supported reason for the change. Check measurement, affected pages, search observations and concurrent business changes. Repair the responsible component where possible, and assess any broader rollback against current orders and data before acting.

Your workspace

Selected services

DTCUP / YOUR NEXT PERSPECTIVE

Stay curious.
Stay connected.

Ideas for the work behind growth—websites, brands and the apps that connect them.