WordPress Permalink Checklist After Migration: Catch URL Problems Early
A post-migration WordPress permalink checklist for checking rewrite rules, post URLs, archives, and redirect noise.
Published
May 21, 2026
Reading Time
3 min read
Updated
May 21, 2026
Implementation Notes
Extension points, code paths, and implementation choices that should survive contact with production.
Best For
WordPress developers, agencies, and technical teams building custom plugin or theme functionality with cleaner operational defaults.
Primary Topics
Editorial Focus
Build Pattern: Extension points, code paths, and implementation choices that should survive contact with production. Updated on May 21, 2026.
Full Report
Last reviewed: May 21, 2026
Permalink problems after a WordPress migration are deceptively expensive. The site may look “mostly fine” on the homepage while deeper URLs start returning 404s, old links redirect inconsistently, post slugs no longer match expectations, or category and tag paths behave differently than they did before the move. By the time someone notices, search signals and internal links may already be drifting.
The problem is not that WordPress permalinks are mysterious. The problem is that teams often treat migration as a hosting move instead of a URL system move. WordPress’s own documentation is clear that permalinks are the permanent URLs of posts, pages, and archives. That is exactly why they deserve a deliberate check after migration, not a quick glance at the homepage.
Who this checklist is for
This article is for WordPress site owners, agencies, developers, and support teams who have just moved a site between hosts, environments, domains, or paths and want to verify that the permalink structure still behaves correctly.
Key takeaways
- Permalinks are infrastructure, not decoration. WordPress documentation defines them as the permanent URLs used to link to content, which makes them a migration-critical surface.
- Saving Permalink settings is often part of the fix, not the whole fix. It can refresh rewrite rules, but it does not automatically validate redirects, slugs, or internal links.
- Migration checks should include posts, pages, categories, tags, and custom URL paths. A homepage-only test is not enough.
Post-migration permalink checklist
- Open Settings > Permalinks and confirm the expected structure. WordPress supports plain, day-and-name, month-and-name, numeric, post name, and custom structures. Do not assume the target environment carried the same setting correctly.
- Click Save Changes once even if the structure looks correct. This is the fastest safe way to refresh rewrite behavior after a move.
- Test several real post and page URLs directly. Not just the latest article. Test older posts, pages, and any high-traffic landing pages.
- Test category and tag archive paths. If custom bases were used before migration, verify that they still resolve properly.
- Check one edited post slug in the editor sidebar. The Page/Post settings sidebar controls the post URL segment, and it is worth confirming that the saved slug matches what the front-end resolves.
What commonly breaks after migration
- Rewrite rules not refreshed. The structure is right in the database, but the site still serves stale route behavior until Permalinks are saved again.
- Domain or path assumptions inside content and links. The site resolves on the new host, but internal content still references the old URL pattern.
- Category and tag base mismatches. Teams forget that archive URLs may use custom bases, not only post slugs.
- Plain permalink mode where pretty URLs were expected. If the environment falls back unexpectedly, the editor and public URL behavior stop matching what users expect.
Why this matters for SEO and cleanup
WordPress documentation on search optimization has always treated permalinks as part of how the site presents content clearly to search engines and users. After migration, permalink issues can also create redirect noise, broken internal links, or stale sitemap expectations. That is why this is not only a routing concern. It is also an indexing concern.
If migration problems start surfacing in search reporting, pair this checklist with our articles on Page With Redirect in Search Console and Excluded by Noindex Tag.
What not to do
- Do not judge the migration by the homepage alone. Permalinks fail deeper than the front page.
- Do not change permalink structure casually on a live migrated site. Confirm whether you are fixing a broken carryover or creating a new URL pattern.
- Do not ignore archive URLs. Categories and tags are part of the public URL system too.
Bottom line
After a WordPress migration, permalinks deserve a direct validation pass. Confirm the structure, save the settings once, test representative URLs, and review archive behavior. Teams that do this immediately catch route problems while they are still cheap. Teams that skip it often find out later through 404s, redirect reports, or search traffic drops.
