Moving a Website Without Breaking Its Evidence: A GEO Guide to Domain and URL Migrations

A website migration can preserve the homepage while breaking the pages that support an AI answer. Old citations may point to specifications, research, policies, or installation instructions whose URLs have changed. A redirect that reaches the new site is useful only if its destination still answers the original question. For GEO, a migration needs a record of those evidence relationships, a deliberate treatment of retired information, and verification after launch. This guide explains how to protect the meaning of important links, distinguish technical continuity from continued citation, and review a move without promising that answer engines will immediately replace their old references.

The homepage is a poor migration test

A team launches a redesigned site, opens the homepage, and confirms that the contact form works. Meanwhile, an old integration guide redirects to the new homepage. A buyer following an AI citation arrives at a polished introduction with no integration details.

The request succeeded in a narrow technical sense. The evidence path failed.

That difference matters because a citation often represents a particular claim. A source for a compatibility condition is not interchangeable with the company's general brand story. A maintenance guide is not interchangeable with a catalog. A dated report is not interchangeable with the current research index.

The migration should preserve a route from the old question to the relevant information. Where the information has changed, it should make that change understandable.

This requires more than a list of old and new addresses. It requires knowing why important pages are used.

What official search guidance says—and where it stops

Google's site-move documentation recommends mapping old URLs to appropriate destinations, avoiding irrelevant mass redirects, and keeping redirects for as long as possible, generally at least one year. It warns that sending many unrelated pages to a homepage can be treated as a soft 404. These are Google Search instructions, not a retention guarantee for citations in every AI assistant. Google: Site moves with URL changes.

Google also documents permanent server-side redirects such as 301 and 308 as signals that a new location should be treated as canonical. A redirect provides a location signal; the content at the destination still needs review. Google: Redirects and Search.

For Google's AI search features, a supporting page must be indexed and eligible for a snippet. Google does not guarantee crawling, indexing, or serving merely because requirements are met. Google: AI features and your website.

The GEO extension proposed here is to evaluate semantic continuity alongside those technical checks. The public guidance does not disclose how quickly each AI product updates an old citation, whether it follows every redirect, or whether it preserves the original source identity.

Build an inventory of evidence relationships

Start with the complete URL inventory available from the current site and known publishing systems. Add the pages that appear in recorded AI answers, backlinks, sales documentation, support links, and important buyer journeys.

An AI citation sample is useful, but it is incomplete. Pages absent from the sample can still matter to customers or search systems.

For each important URL, record the following:

A row might say that an old compatibility page supports whether a particular gateway revision is supported. Its acceptance condition should include the gateway revision and status, not just an HTTP response code.

Prioritize pages using observed use and the consequence of error. A rarely visited safety-relevant installation note can deserve more attention than a frequently visited introductory article. The inventory should explain the chosen priority rather than equate traffic with importance.

Decide what each old page should become

There are several legitimate treatments.

A direct move preserves the information and changes its location. The new page should retain the relevant conditions, references, and document identity.

A consolidation combines related material. The destination should contain the substantive content the old page supported, with an identifiable section where practical.

A revision changes the underlying answer. The destination should explain the material change and distinguish the current information from the earlier version.

An archive preserves historical information that remains useful for old products, past research, or a previous policy period. The page needs a visible historical label and a route to current information.

A removal is appropriate when there is no useful or legitimate replacement. Do not invent an equivalent destination merely to avoid a missing-page response. The removal decision should be reviewed, especially if customers still rely on the information.

This classification is an editorial decision framework. It does not prescribe a single indexing policy for every archived document. Public historical material, confidential records, and obsolete instructions can require different handling.

A fictional migration map

Suppose a fictional supplier moves from an older website to a new international domain.

The dangerous shortcut is to send the first five resources to “Products.” A buyer then has to reconstruct the missing relationship, and a fetched destination may provide none of the original supporting information.

A less obvious problem is redirecting the revision 2 specification to the current revision 3 sheet. The new document may be accurate for the current product while being wrong for the installed equipment the buyer asked about.

The map should therefore preserve both identity and applicability. This is a hypothetical design example, not a migration performed for a named company.

Test technical reachability and meaning separately

For each priority path, test the request from the old address through to the final destination. Record status codes, redirects, final URL, and the content actually returned.

Then conduct a subject-matter check. Does the destination still contain the supported claim? Is the correct product revision visible? Are qualifications adjacent to the relevant values? Do cited attachments still resolve? If a section fragment is used, does that section still exist?

A page can pass the first review and fail the second. The reverse is possible too: correct content exists but is hidden behind a login, blocked by an edge rule, or available only through a route the old link no longer reaches.

Do not treat changing a user-agent string as proof of access by a real platform crawler. Such a request can help investigate server behavior, but authentic access requires appropriate platform tools or verified request evidence where available.

The acceptance record should state what was checked and how. “All redirects pass” is too vague if the test only checked whether some response was returned.

Review the evidence inside the new page

A migration often coincides with a redesign, content rewrite, new CMS, or localization project. That creates several ways to weaken a previously useful source.

Specifications may move from HTML into a download. Footnotes may disappear. A concise limitation may be removed during a copy edit. An integration table may be replaced with customer logos. The new page can look more persuasive while becoming less useful for verification.

Retain a before-and-after record for priority claims. It can be simple: old passage, new passage, applicable source, and approval. The purpose is to detect substantive loss, not to insist that every sentence remains unchanged.

Check visible text and any structured data together. If a redesign updates the visible offer but leaves an old description in metadata, different consumers can receive different claims. Also review internal links, canonical annotations, and any existing language relationships as part of the migration checklist.

For overseas content, preserve the distinction between a language change and an offer change. Translating a page into English does not establish that its delivery terms apply to the US or Europe.

Notify discovery systems without confusing notification with inclusion

Use the platform-specific tools applicable to the actual move. Google's documentation explains when its Change of Address tool is appropriate, including domain or subdomain moves. It is not a universal announcement endpoint for all assistants. Google: Site-move guidance.

IndexNow allows participating search engines to be notified of content changes. Its FAQ explicitly says submission does not guarantee indexing, and participating engines make their own decisions. A successful submission is evidence that the notification was accepted, not that a future answer will cite the new page. IndexNow FAQ.

Maintain separate states for submitted, fetched, indexed where observable, and seen in an answer. If a state cannot be verified, leave it unknown.

This prevents a launch report from claiming complete AI migration based on an API response or a sitemap update. The observed evidence may show technical readiness long before it shows changed citations.

Measure citation continuity after launch

Keep a small, documented set of relevant questions and historical citation paths. Repeat the question sample under comparable conditions and review old links when they appear.

Classify the observations:

• A new citation reaches the correct current evidence.
• An old citation reaches equivalent evidence through a redirect.
• An old citation reaches a historical page that correctly explains its scope.
• An old citation reaches an unrelated destination or broken resource.
• The answer no longer contains the previously reviewed claim.

The second category is not necessarily a failure. A reader can still verify the statement. The fourth category requires action even if total brand mentions stay unchanged.

One practical descriptive measure is the fraction of reviewed historical citation paths that still reach an applicable supporting passage. Report the count, the sample, and the review date. It is not a population estimate of every citation on the internet.

Also review the answer's factual continuity. A redirect can work while the assistant continues describing an obsolete package. Technical preservation and correction of the answer are separate outcomes.

Agree on completion and rollback criteria

A migration should have clear acceptance criteria before launch. For priority evidence paths, define the required destination, claim preservation, accessibility, and supporting-document status. Define which failures justify delaying launch or restoring a route.

After launch, keep the original map, observations, and unresolved items. A temporary failure may require a redirect fix; a changed citation pattern may require a longer observation period. Neither should be concealed inside a broad “migration successful” label.

Xindar's monitoring service describes timestamped answer archives and source monitoring. For a website move, the proposed scope should add historical-path review and content-equivalence checks. Those are specific deliverables a client can inspect without relying on a promised ranking outcome.

Start by protecting the pages that support consequential buyer decisions. Preserving their evidence is useful even when no AI system immediately updates the visible source URL.

Frequently asked questions

Will a permanent redirect transfer an AI citation automatically?

There is no universal documented guarantee. Verify that the route works, preserve the relevant evidence, and observe the answer product separately.

Can we redirect every old article to the homepage?

That usually loses the relationship between the old question and its evidence. Google also warns about irrelevant mass redirects in its Search guidance.

Should old specifications be replaced with the newest ones?

Only when the old and new documents are applicable to the same question. Installed older products may need a clearly labeled historical specification.

When is the migration finished for GEO purposes?

Technical acceptance can have a definite completion point. Citation and answer continuity require documented observation, with remaining unknowns stated rather than a universal all-clear.

Sources and limits

Sources were reviewed on October 9, 2026. The evidence inventory, acceptance criteria, fictional map, and citation categories are the article's proposed operating method. Official guidance establishes platform-specific behavior and requirements, not a universal AI migration timetable.

• Google: Site moves with URL changes — mapping, redirects, and move tooling.
• Google: Redirects and Search — permanent location signals.
• Google: AI features and your website — supporting-page eligibility.
• IndexNow FAQ — notification and indexing boundaries.