On this page
Search engines, bookmarks, email campaigns and other websites all point to specific addresses on your site. When those addresses change without a plan, links break and accumulated signals can be lost. The single most useful SEO task before a migration is therefore unglamorous: build a complete list of URLs that exist today.
Why one source is never enough
Your CMS knows about pages and posts it manages, but not about old addresses that were redirected years ago or files uploaded directly to the server. Your XML sitemap often omits archives, tags or paginated pages. Analytics only knows about URLs that received visits in the selected period. Each source sees part of the picture, so the inventory comes from combining them.
Sources to collect
Gather URL lists from as many of these as you can:
- The CMS: export of all published pages, posts and custom content with their permalinks.
- XML sitemaps: every sitemap file, including nested sitemap indexes.
- Search console data: pages reported as indexed and pages receiving impressions.
- Analytics: landing pages over the last twelve months or longer.
- Backlink reports: target URLs that external sites link to.
- A crawl: a crawler starting from the home page will find linked URLs the other sources miss.
- Server or CDN redirect rules: old paths already being forwarded.
- Campaign materials: printed QR codes, email templates and ad destinations.
Normalise before you merge
Different tools format URLs differently. Before merging, decide on rules: lowercase the host, choose whether to keep trailing slashes, strip tracking parameters such as campaign tags, and keep meaningful parameters such as pagination or filters only when they produce distinct content. Then deduplicate.
Add useful columns
A plain list becomes a planning tool when each row carries context:
- Current status code (200, 301, 404 and so on).
- Page type, such as service page, article, category or file.
- Traffic or impressions over a fixed period.
- Whether external links point to it.
- The proposed destination on the new site.
- A decision: keep the same path, redirect, or retire.
Decide on paths early
The simplest migration keeps important paths identical. When the new site needs a different structure, each changed path needs a one-to-one redirect to the most relevant new page. Redirecting everything to the home page is a common shortcut that tends to frustrate visitors and gives search engines little to work with.
Do not forget non-HTML assets
PDF brochures, price sheets, downloadable forms and images are often linked from other websites. List them, decide where they will live and include them in the redirect plan when their paths change.
Keep the inventory alive
The inventory is not a one-time document. Use it during build to confirm every important page has a destination, during testing to check redirects return the expected status, and after launch to compare crawl results. Teams that maintain the inventory through launch usually catch problems while they are still small.
A realistic expectation
A careful inventory and redirect plan reduces avoidable losses, but nobody can promise rankings will hold or improve after any migration. Search performance depends on many factors outside the move itself. What the inventory guarantees is that you will know what changed and where to look if something needs attention.
Turn this topic into a project plan
Use these supporting guides to prepare the details for your seo discussion.
Put this into practice
Planning a move like this?
See how a scoped seo-safe migration project handles content, URLs, integrations and launch.
