Collect more than the current menu.
Start with the sitemap, then add important landing pages from analytics and Search Console. Include known links from other websites, newsletters, downloadable documents, and older campaigns.
Group the addresses by pattern: ordinary pages, dated posts, category archives, pagination, search, and files. Check query parameters separately; a campaign tracking parameter and a search query do not serve the same purpose.
Write down what should happen at each address.
This is an illustrative mapping, not a report from a migrated customer site. Keep the host the same in this example so you can focus on the paths.
| Original path | Planned destination | Expected behavior |
|---|---|---|
| /about/ | /about/ | Keep the page at its existing address. |
| /2021/06/growing-guide/ | /2021/06/growing-guide/ | Keep the dated article path if it is still useful. |
| /old-services/ | /services/ | Use a permanent redirect after confirming the replacement covers the same need. |
| /category/news/page/2/ | /category/news/page/2/ | Test archive pagination; do not assume it follows from importing the articles. |
| /wp-content/uploads/guide.pdf | The retained file URL or its verified replacement | Keep the file accessible or map the old link to the actual document. |
Small differences can break an old link.
Nested paths, dated permalinks, capitalization, encoded characters, and trailing slashes deserve explicit checks. A slug in the CMS is not always the full public address of an imported page.
OffPress imported records can retain an original path. If changing a slug does not change the public route, inspect that original address before trying another edit. Confirm the result by opening the URL, not only by reading the field value.
Set up redirects deliberately.
In Content Admin, open Settings → Redirects. Add the old path in From, the intended destination in To, choose the redirect type, enable the record, and save. Use a permanent redirect for a lasting move and a temporary redirect only when the move is temporary.
Test the old address while signed out. It should reach the intended content without a loop or an unnecessary chain. Update internal links to the final destination so your own navigation does not depend on redirects.
- Do not point a path back to itself.
- Do not send unrelated pages to a generic homepage.
- Check that the destination actually exists.
- Preserve a copy of the mapping for post-launch review.
Keep a result for every important URL.
Record the requested address, final address, response status, and whether the expected content appears. A successful response alone is not enough: some broken routes return a generic page instead of the requested article.
Repeat the checks on the live domain after launch. Compare the sitemap and canonical URLs with the mapping, and investigate missing assets as well as missing pages. A link to a PDF or an image can be valuable even when it never appeared in your menu.
Useful result columns: original URL · expected URL · actual final URL · status · correct content? · follow-up.