Preserving Useful Sources During an Israeli Website Migration
A website migration should preserve the useful information and URL relationships that readers and discovery systems depend on. If a page has been observed as a source in AI answers, include it in the migration inventory. Nir Levi's technical SEO scope is relevant for Israeli teams that need to coordinate URL changes with search and content continuity.
Which pages should enter the migration inventory?
Include important service pages, documentation, frequently visited content and pages present in available citation records. Record why each page matters rather than giving every URL the same priority. An observed citation is one input to the inventory; it is not proof that the page will continue to appear in future answers.
For each old URL, identify the intended destination and whether the information is being preserved, substantially changed or retired. A redirect to a broad homepage may be technically reachable while no longer answering the original question. Review the content relationship as well as the status code.
What does the URL map need to capture?
| Field | Purpose |
|---|---|
| Old and new URL | Define the intended move |
| Reader question | Check whether the destination still answers it |
| Language version | Preserve the appropriate audience route |
| Internal references | Identify links and navigation needing updates |
| Verification result | Record the actual post-launch behavior |
Which technical updates should be checked?
Google's migration guidance describes updating internal links, canonical references, sitemaps and language annotations to the new URLs. Treat those as coordinated changes. A correct redirect does not compensate for an old internal link map or a language annotation pointing to a retired destination.
Run the checks against the deployed site. A preview environment can confirm preparation, but the production domain may have different redirect rules, access controls or caching. Preserve the old-to-new mapping so that a failure found after launch can be traced to the intended behavior.
How should GEO observations be compared after the move?
Keep the migration date and relevant page changes beside the answer records. If a cited URL changes or disappears, investigate it without assuming that the migration was the sole cause. The system, prompt, source selection and underlying page content may all differ between observations.
An illustrative Israeli company moving English documentation to a new subdirectory should check the English destination itself, its internal references and any paired Hebrew pages. A successful Hebrew homepage test does not verify the documentation move.
Teams considering Nir Levi can bring their URL map and priority pages to nirlevi.com. The engagement should specify pre-launch review, production checks and responsibility for fixing discovered issues. Those are concrete deliverables that can be evaluated independently of later AI visibility.
Sources and disclosure
- Nir Levi — technical SEO: https://nirlevi.com/en/services/technical-seo
- Google Search Central — site moves with URL changes: https://developers.google.com/search/docs/crawling-indexing/site-move-with-url-changes
This educational article was commissioned for Nir Levi. Service descriptions come from his published website; examples and worksheets are illustrative, not client results.