Broken internal links after a CMS migration are caused by changed URLs, IDs, and content structures that old links still point to. An internal link is a link from one page on your site to another page on the same site. A CMS migration moves content from one content management system to another, such as WordPress to Drupal. Page addresses, folder names, and link formats often change in that move, so links that were not updated or redirected now lead to missing pages.
Official resource:
- Follow Google's site-move checklist for URL changes — Verify URL mapping, redirects, and internal link updates to prevent broken links during migration.
Table of Contents
- How do changed URL structures break links?
- Why do hardcoded links survive the move?
- What content problems create missing destinations?
- How do you find and fix them before they cost traffic?
- How do you prevent repeat breaks?
- Frequently Asked Questions
How do changed URL structures break links?
Most migrations change how page addresses are built. A page that lived at /blog/my-post may move to /news/my-post or lose its date and category folders. Any menu item, button, or in-text link using the old address will fail unless it is mapped to the new one. Permalink and routing settings also differ between systems.
One CMS may add trailing slashes, file extensions, or language prefixes while the other does not. Even a small difference makes the old URL a separate, missing destination. Content IDs and media paths change too. Embedded images, PDFs, and related-post blocks often store full internal paths. When those files move to a new library or folder, the stored path points to nothing.
Why do hardcoded links survive the move?
Many links are typed directly into page text, widgets, buttons, and templates. Export and import tools carry that text across unchanged. The result is a new site full of old addresses. Theme files, headers, footers, and call-to-action blocks are common hiding places.
A contact button in the footer may still point to /node/142 or /index.php?page=about. Readers hit those links on every page, so one missed template can create hundreds of errors. Shortcodes, blocks, and embeds add another layer. A WordPress shortcode, Drupal token, or reusable block may not exist in the new system. When the code is stripped or ignored during import, the link it produced disappears or breaks.
What content problems create missing destinations?
Not all content makes the move. Drafts, archived posts, landing pages, taxonomies, and author pages may be left behind on purpose. Links that pointed to them now have no target. Merges and splits are also risky.
Two service pages may become one, or one long guide may become four shorter pages. Old anchors like #pricing or #faq often point to headings that were renamed or removed. Redirect gaps finish the damage. Common issues include:.
- No redirect map for renamed slugs and moved sections
- Redirects that point to other redirects instead of the final page
- Case changes, such as /Services to /services, treated as different URLs
- Staging-domain links, such as dev.example.com, left in live content
How do you find and fix them before they cost traffic?
Start with a before-and-after URL list. Export the full sitemap and internal link inventory from the old site, then crawl the new site after launch. Match every old address to its new counterpart or to a relevant replacement. Fix the source first, then add redirects as backup.
Update menus, templates, and high-traffic articles to use the new addresses directly. Use permanent 301 redirects for renamed pages so bookmarks and search engines land in the right place. Test like a visitor and a search crawler. Click key paths for checkout, signup, contact, and support. Recrawl for 404s, check Search Console coverage, and watch for spikes in "page not found" visits after go-live.
How do you prevent repeat breaks?
Freeze content edits during final export so writers do not add new old-style links. Use relative links or a central link picker where the new CMS supports it.
Document slug rules for dates, categories, and media folders. Assign one owner for the link map through launch. That person approves URL changes, keeps the redirect table current, and reruns the crawl after each content fix until errors stay at zero.
Frequently Asked Questions
Do redirects alone fix broken internal links?
No. Redirects help visitors and search engines reach the new page, but you should still update the link source to avoid extra hops and maintenance debt.
Why do links break even when all pages were migrated?
The pages may exist under new addresses while old hardcoded links, menu entries, and embeds still use the former addresses.
What should be checked first after launch?
Homepage navigation, footer links, top service and product pages, checkout and contact flows, and media downloads, because errors there affect the most visitors.




