SEO migration for a site relaunch and AI visibility

What does an SEO migration protect during a relaunch?

An SEO migration coordinates the technical and content changes that can affect how people find your site. The practical deliverable is a documented plan for what moves, where each old URL should lead, and how the new site will be checked after launch.

A migration can cover a redesign, a domain change, a rebrand or a CMS move. The work starts with a baseline, because a clear record of the current site makes it easier to spot omissions and investigate changes later. For AI visibility, we also record the pages and citations that matter to the project, then revisit those observations after launch. This is a visibility check, not a claim about how any assistant ranks or selects sources.

The plan is useful for marketing leads, developers and content owners. It gives each team a shared reference instead of separate lists of URLs, metadata and launch tasks. Depending on scope, the working file can include:

• A crawl and traffic baseline, with priority pages identified.
• A URL map that pairs existing pages with their new destinations.
• Redirect, metadata and structured-data checks.
• Staging and launch-day checks, plus a recovery plan.

For a broader view of how AI-answer visibility fits with search work, see AI search visibility and our SEO services.

How do we establish a reliable pre-migration baseline?

A useful baseline records the site as it exists before the move, so the team can compare like with like after launch. We review crawlable URLs, available traffic data, page titles and descriptions, structured data, and the pages the client identifies as important to search and AI-answer visibility.

For AI assistants, a citation observation is tied to a specific prompt or question, the date checked and the answer or source shown. The record is a snapshot, not a promise that the same source will appear every time. We note which pages are cited or mentioned and whether the destination is the current, intended page. This creates a practical comparison point for ChatGPT, Perplexity or Google AI Overviews when those surfaces are in scope.

Our Evidence Pack brings the baseline and migration references together. A client can prepare by sharing:

• The current domain and any planned domain or brand changes.
• The intended launch window and a staging address, when available.
• Analytics and search data access, plus known priority pages.
• Existing redirect rules, sitemap and structured-data documentation.
• Important AI prompts, answers or citations the team wants reviewed.

Where technical risk needs a separate diagnosis, connect this work with a GEO audit. For a continuing view after launch, see AI visibility monitoring.

How should URL mapping and redirects work?

The URL map should give every important old page a clear destination on the new site. It prevents a launch from relying on broad redirects or leaving useful pages without an intentional successor.

We compare the existing URL inventory with the proposed site structure, then record the intended destination for each priority page. When a page is being removed or consolidated, the team decides whether a genuinely relevant replacement exists. Redirect checks then confirm that the old address resolves to the mapped destination, rather than an unrelated page or an avoidable dead end. The development team can use the map as an implementation and review checklist.

The map should be settled before launch, not assembled from memory on launch day. Content owners should flag pages with continuing value, while developers confirm which redirects and URL rules are ready in the build. During staging, we sample the mapped paths and check for mismatches between navigation, canonical destination, metadata and page content.

For a smoother handoff, keep the working map in a shared format with columns for old URL, new URL, page owner, redirect status and review note. Mark unresolved destinations clearly so they are visible before launch. If the move includes a change in what the business is known for, entity and knowledge graph building can complement the migration plan by helping align the site’s identity and supporting information.

What should be checked on staging for AI SEO?

Staging checks help catch migration issues while the team can still correct them before the new site is public. We review whether priority pages are present, readable and aligned with their intended URLs, and whether their metadata and structured data have been carried across appropriately.

For AI SEO, the important operational question is whether the new page preserves clear, consistent information that a visitor can verify—not whether a file or markup change will force an AI assistant to cite it. We compare selected pages with the baseline and check that key descriptions, product or service details, and references have not disappeared during the redesign. Structured data is checked against the content the page actually presents.

A staging review can cover:

• Priority page availability and intended URL.
• Page title, description and key copy transfer.
• Structured data presence and consistency with visible content.
• Internal navigation to important pages and resources.
• AI citation observations selected for the baseline.

Treat llms.txt as a separate technical consideration rather than a substitute for sound pages, URL handling or crawl checks. If the scope includes broader technical answer-engine work, we can coordinate with technical AEO. Content revisions that clarify answers and page structure can be planned alongside content for AI answers.

What happens on launch day and after the site moves?

Launch monitoring checks whether the public site matches the approved migration plan. We compare key destinations, redirects and page elements against the baseline, log issues and share the items that need action from the client or development team.

The sequence is practical: confirm the intended live domain and key pages, test priority old-to-new URL paths, review the new pages, and check for missing or inconsistent metadata and structured data. We also revisit the agreed search and AI visibility observations. If something is absent or points to the wrong destination, the team can prioritize a correction and verify it again. The Proof Log records what was checked, what was found and what remains open.

Some fluctuation in search visibility after launch is normal. That is why the work includes follow-up rather than treating the launch itself as the end of the project. The schedule is agreed around the site’s release plan and the scope of pages, domains and technical changes. A concise handoff should identify the issue, the affected URL, the requested correction and the next verification point.

The client receives a clear record for internal teams: baseline references, URL mapping, review notes and post-launch findings. When migration work is complete, ongoing AI visibility monitoring can track selected observations as a separate service.

What can an SEO migration team control, and what is outside its control?

A migration team can plan and verify agreed site changes; it cannot dictate how an external search engine or AI assistant processes a relaunched site. Search results may fluctuate after launch, and ChatGPT, Perplexity and Google AI Overviews control their own answer display, citations and update timing, so a particular ranking or citation cannot be promised.

That distinction keeps the work accountable. We can commit to the agreed baseline, mapping, checks, monitoring and documentation, and show the evidence for those tasks. We cannot represent an observed citation as permanent or claim that correct redirects alone will preserve every search position. A useful report separates completed work, observed outcomes and open technical actions.

The service is available from $2,130 / month. Scope is shaped by the site structure, the type of move, the priority pages and the launch schedule. Send us the current domain, the planned change, an approximate launch window and any priority search or AI citations. We will review the scope, identify the materials needed for a baseline, and return a migration plan for discussion. If you already have a launch checklist, include it so we can align the review with your team’s process.

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. Share the migration briefSend the current domain, planned change, launch window, staging details and priority pages or citations.
2. Set the baselineWe review crawl and traffic references and record the selected pages and AI visibility observations.
3. Map the moveWe document URL destinations, redirect checks and the metadata or structured data to review.
4. Check staging and launchWe compare the build with the plan, then verify agreed priority paths and page elements after release.
5. Deliver the Proof LogYou receive findings, evidence of completed checks and a clear list of open follow-up actions.