A changed document URL should not break search identity or create a duplicate source. Resolve current location through a stable resource reference where the source system supports it, and keep old-link behaviour explicit.
URLs are locations, not universal identities
A URL can change after a rename, move, migration, or sharing-policy update. Different URLs can refer to one resource, while a reused location can later identify different content. The connector needs the provider’s documented lifecycle semantics.
For a proposed mapping, retain source namespace, stable identity, current URL, version, relevant alias history, and permissions. Update citations and previews through a controlled resolver rather than embedding permanent privileged locations everywhere.
Do not follow arbitrary redirects as proof of source authority. A destination change can cross account, system, or disclosure boundaries and should remain subject to the approved retrieval policy.
Test a fictional knowledge-site migration
A company moves an approved guide from an old wiki path to a new document system. The content owner establishes the replacement relationship. Search should point to the approved current resource and avoid treating the old copy as independent current evidence.
A second fixture reuses the old path for another article. Existing answer references must not silently claim that the new content proves the earlier answer. Historical source version and current navigation are different concerns.
| Location change | Expected behaviour |
|---|---|
| Rename with stable identity | Update current location |
| Supported move | Preserve lineage and recheck inherited access |
| Migration to new identity | Approved replacement mapping |
| Redirect outside allowed scope | Controlled handling, not blind fetch |
| Old URL reused | Historical evidence not silently replaced |
Replay delayed old-link events after the migration. Inspect current search, aliases, citations, and cached answers for duplicate or stale locations.
Keep discoverability separate from access
An old title or URL alias can help authorised users find moved material, but it may itself reveal restricted context. Apply the relevant audience policy to suggestions and redirect explanations.
Resolvers add a dependency and mapping maintenance. Direct source links are simpler but can become stale and expose long-lived capability tokens. Choose the actual supported design, state its limits, and test failure of the resolver as well as normal moves.
This link design is proposed. The voice integration case study describes related knowledge work. Pair it with renamed-file handling.
Changed-URL FAQ
Should the URL be the sole document key?
Use a documented stable source identity when available and preserve location separately.
Can an old citation open the latest unrelated page?
Not while implying historical support. Make version and replacement semantics explicit.
What should migration tests inspect?
Check identity, authority, permissions, redirects, aliases, duplicate count, previews, and cached references.