SEO Migration: Protect Search Visibility and AI Citations

When do you need an SEO migration plan?

You need a migration plan when the site address, structure, design, or content management system changes. Without prior verification, you can lose the match between old and new pages, important metadata, or the availability of content that search engines and AI services reference.

Before starting, record exactly what is changing:

• domain, subdomains, and protocol;
• page addresses or URL formation rules;
• CMS, templates, navigation, and internal linking;
• texts, headings, metadata, and structured data;
• pages that are merged, removed, or created from scratch.

This helps separate the technical transfer from content updates. If domain, structure, and texts change at the same time, it is harder to understand what caused any subsequent visibility changes. We collect the baseline picture before launch and flag decisions that need approval from your team. To assess current issues before migration, you can add a GEO audit, and for the overall AI search visibility task, see the GEO and AI visibility page.

How do you preserve URLs, redirects, and search signals?

Keeping page addresses is the simplest path if the new site structure allows it. When URLs change, each important old page needs a relevant new counterpart, and redirects should be tested before publication.

The transfer map should be a working document, not just a list of addresses for the developer. For each row, specify the old URL, new URL or decision to close the page, type of change, and verification status. Separately mark pages with organic traffic, external links, and important links from other site sections.

Before launch, check that:

• redirects lead to corresponding pages, not mass-redirect to the homepage;
• internal links are updated and do not point to old addresses;
• pages that should be accessible open in the staging environment;
• metadata and structured data are transferred to the current templates.

We cross-check the URL map against the new structure and note discrepancies for correction before release. If the redesign includes schema and technical setting changes, it helps to coordinate with the Technical AEO team so the transfer does not conflict with structured data requirements.

What happens to ChatGPT and Perplexity citations?

During the transfer, it is important to preserve pages that serve as clear sources of information about the company, products, and services. Their availability, structure, and content should be included in the migration map, not checked only after launch.

Compile a list of important materials: product pages, documentation, frequently asked questions, about pages, and publications you want to keep. For each material, decide whether the URL stays the same, gets a new address, or the content is merged with another page. If the text changes, verify that key facts, names, and connections between pages are not lost during editing.

To monitor original mentions and citations, record the pages and queries the team considers a priority. Then check them after the transfer and add any changes found to the overall task list. To assess current presence before launch, you can use AI visibility monitoring, and for working with the materials themselves, content for AI answers.

This approach provides a verifiable baseline for comparison before and after launch. It does not require rewriting all materials for the migration: first transfer important pages without losing meaning, and plan editorial improvements separately.

What checks should you run before and after launch?

Pre-launch checks find errors in the staging environment, while post-launch checks show what visitors and search engines actually saw. To do this, compare the previously recorded site state with the new version using the same list of pages and technical elements.

Before launch, we check the URL map, selectively open important pages, verify redirects, and ensure metadata and structured data are in place in the templates. The development team should know which addresses to check and who confirms fixes. If the site is still closed to public access, coordinate separately how to test it technically and remove temporary restrictions at publication.

At launch, do not limit yourself to checking the homepage. Verify key sections, redirects, and pages that were transferred or merged. After publication, monitor page availability, transitions to new addresses, and changes in search traffic. Log unexpected deviations with the URL, observation, and person responsible for the fix.

MediaHype cross-checks the URL map against actual pages and provides the team with a clear list of issues. After launch, we keep an observation log and agree on fix priorities so the technical team can act without guesswork.

What determines the timeline and scope of work?

The migration scope is determined by the number of important pages, the nature of the changes, and how early the team gets involved in release preparation. The sooner the new structure and staging environment are ready, the more issues can be found before publication rather than after.

Work typically includes the following deliverables:

• a baseline snapshot of pages and visibility for comparison;
• a map matching old and new URLs;
• a list of requirements for transferring metadata and structured data;
• a review of the staging site and a list of fixes;
• launch monitoring and an action plan for error detection.

Before the estimate, prepare a link to the current site, a description of planned changes, known launch dates, and a contact for the technical person responsible. If you have a map of the new structure or access to the staging version, include them: this allows faster risk assessment. The cost of support starts from the monthly rate specified in the brief, and the exact scope is agreed after reviewing the site and release plan.

Timelines are coordinated considering team availability and material readiness. It is important to leave time for fixes before launch and observation after it, rather than planning the migration as a one-time publication at the end of the project.

What can the migration not control, and what should you do next?

A migration plan helps maintain technical continuity of the site but does not control the decisions of search engines and AI platforms. Even with correct redirects, Google may process page updates in its own way, and the presence of previous material does not oblige ChatGPT or Perplexity to show it as a source.

Therefore, evaluate the work by what can be verified: the URL map matches the new structure, important redirects work, needed pages are accessible, metadata is transferred, and post-launch errors are logged and handed over to the responsible people. Record visibility changes separately from the list of completed technical tasks: this makes it easier to distinguish implementation quality from external platform dynamics.

If the migration is part of broader organic search work, it can be linked to SEO services and tasks for visibility in ChatGPT. Write to us about the type of transfer planned, which sections are affected, and when the team expects the launch. MediaHype will review the initial inputs, request missing materials, and propose a scope of work with responsible checkpoints.

Prices

Starting prices in USD. Custom bundles and volume discounts on request. Payment in USDT, USDC, BTC, ETH, SOL, TON or your project token.

How it works

1. Gather inputsYou send the current site address, a description of the redesign or transfer, the expected timeline, and a contact for the technical person responsible.
2. Record the baseline stateWe collect a list of important pages and baseline data so that after launch we can compare the site against a specific reference.
3. Prepare the transfer mapWe map old and new URLs, note redirects, and coordinate the transfer of metadata and structured data.
4. Check the staging versionWe verify pages and technical settings before publication, and hand over any discrepancies to the team for correction.
5. Monitor the launchWe check important pages after publication, keep an observation log, and agree on the priority of next steps.