To check for omissions in a URL migration, start by compiling a list of old URLs, verify where each one should lead, and investigate anything missed after launch. If URLs will change, build the list using data from crawlers, search indexes, traffic, backlinks, sitemaps, and your CMS. Then use 301 redirects to send the old URLs of migrated content to their corresponding new pages. Continue logging and reviewing requests that return a 404 during the first few months after launch. These steps can help uncover omissions, but they cannot guarantee that search rankings or traffic will remain unchanged.
Start with the old URLs, not just the pages on the new site
When planning a migration, start by asking “Which URLs existed before?” rather than simply checking the completed pages on the new site. Semrush recommends compiling a list from multiple sources when URLs will change, reducing the chance of overlooking important content. Each source can help with a different check:
- Crawler and search index data: Check URLs that have been crawled or indexed.
- Traffic data: Identify pages users have visited.
- Backlink data: Confirm which old pages still have external links pointing to them.
- XML sitemaps and your CMS: Add content URLs listed in these sources.
Use the combined list as the basis for later checks; do not assume that any single source includes every URL. If URLs will remain entirely unchanged, there is no need to create a separate old-to-new URL mapping solely for the migration.
Plan each page’s destination, then check the redirects
Once the list is ready, distinguish content that will move to a new location from content that will be deliberately deleted. For content being moved, the recommendation is to use server-side 301 redirects from old URLs to their corresponding new pages. Check not just whether each redirect is configured, but whether its destination is correct.
- Content being retained at a different URL: List the old URL and its corresponding new URL, and verify each pair.
- Content being deliberately deleted: Record the decision clearly to distinguish these pages from those accidentally left behind.
- Old pages with existing rankings or external links: Double-check that they are included and redirect to the correct destinations.
For example, if a tutorial is being retained but moved to a new path, check that its old path redirects to the article’s new location, rather than merely confirming that the article loads there. Search Engine Journal notes that missing or incorrect 301 redirects may affect whether link equity passes from old pages to new ones. Missing even one high-authority URL could cause a noticeable drop in traffic, though not every omission will have that result.
Investigate 404s after launch to find URLs missing from the list
A pre-launch inventory is no substitute for post-launch checks. A community answer on Webmasters Stack Exchange recommends logging all requests that return a 404 and reviewing them regularly during the first few months after launch to identify URLs that may have been overlooked.
Compare these requests with the old URL inventory and migration plan: Are the requested URLs for pages you intended to keep but never redirected, or for content you deliberately deleted? A 404 is a clue to investigate, not proof on its own that the migration went wrong. The recommendation to keep checking during the first few months after launch is practical advice from the community, not a timeframe required by a search platform.
Website URL migration: perspectives from across the web
Can a sitemap replace redirects?
It should not be treated as a replacement. A community answer on Webmasters Stack Exchange describes a sitemap as a supplement to redirects, intended to help search engines discover new links, and recommends checking whether the sitemap has been processed successfully. The answer also mentions notification and crawl-rate practices used at the time, but the supplied material does not establish whether those features still apply today, so they should not be treated as current platform rules.
If pages cannot be found after a migration, what can you check besides their URLs?
If pages cannot be found in search results, check the source code for robots and noindex tags. You can also use a crawler or site audit tool to list pages containing the relevant tags, then investigate further in the CMS or code. This troubleshooting approach comes from a 2016 Semrush article. It does not mean that tags are necessarily responsible for missing pages, nor does it establish current search platform rules.
Do you still need to check for issues after changing hosting or your CMS if most URLs stay the same?
Checking is still worthwhile. Semrush’s 2016 article notes that major changes, such as switching your CMS, theme, hosting, or protocol, may affect how search engines understand your site. Even after a migration is complete, revisiting a migration checklist can help identify omissions. This is advice for investigating potential risks, not a claim that every change will cause search problems, and the checklist from that time should not be treated as current rules.
References
- How You Can Avoid an SEO Disaster During Your Website Redesignwww.warriorforum.com — Source used in the article above.
- What Is A Migration Hangover Traffic Drop & How Do You Avoid It?www.searchenginejournal.com · 2026-06-05T10:00:34+00:00 — Source used in the article above.
- Moving from a static site to a CMS with new URLs and meta-data for pageswebmasters.stackexchange.com — Source used in the article above.
- The Complete Website Migration Checklist [SEO-Friendly]www.semrush.com · 2019-03-25T13:30:00Z — Source used in the article above.
- Moving from a static site to a CMS with new URLs and meta-data for pageswebmasters.stackexchange.com — Discusses: Can a sitemap replace redirects?
- SMB Issues: Why Isn’t My Website Showing Up on Google?www.semrush.com · 2016-12-30T17:30:00Z — Discusses: If pages cannot be found after a migration, what can you check besides their URLs?; Do you still need to check for issues after changing hosting or your CMS if most URLs stay the same?



