How to prevent broken internal links in WordPress

Go to Settings → Permalinks and choose a structure you expect to keep. Avoid changing the structure on an established site unless you have mapped the old URLs to their replacements. WordPress describes permalinks as permanent URLs, but changing the structure can alter many existing addresses at once.

After any deliberate permalink change, click Save Changes. This applies the rewrite rules for the selected structure. Check a few posts, pages, categories, and custom post types before declaring the change complete.

When editing content, select the text, choose the link control, and search for the destination by page or post title. WordPress can search your own content and insert its URL, which is safer than typing a relative link such as page-name. A relative link can resolve against the current page path and produce a 404 after a parent page changes.

For menus, buttons, widgets, and reusable blocks, open each item and confirm that it points to the intended page. Do not assume that changing a page title also updates every URL already stored in post content.

If a link is produced by a theme, template, shortcode, or custom PHP, avoid hard-coding the page URL. Pass the destination post or page ID to WordPress’s get_permalink() function so the current permalink is generated when the page is displayed.

This approach is useful for repeated calls to action, breadcrumbs, related-content controls, and parent-page links. It does not automatically repair URLs already saved inside ordinary post content, menus, or third-party fields, so those still need an audit.

When you rename a slug, move a page, or change a permalink structure, keep the old address redirecting to the exact new address. WordPress stores old slugs for published posts and has core logic that can redirect some old post URLs, but this is not a complete migration plan: hierarchical pages and complex structure changes need deliberate checking.

Update your internal links to the final URLs as well. A redirect is a safety net for old bookmarks and external links, not a reason to leave your own site linking through old addresses. Avoid redirect chains, redirect loops, and sending several unrelated old URLs to the home page.

Run a crawl after changing slugs, parent pages, domains, HTTPS, or permalink settings. Review 404 responses, redirecting internal links, links pointing to staging URLs, mixed HTTP and HTTPS URLs, and links that resolve differently depending on the current page path.

Do not rely on a broken-link checker alone. A support case showed that a checker could miss links which still contained an old URL after a page was moved, even though visitors reached a 404. Open representative links in a private browser window and check important templates manually.

The manual approach is fine for a small, stable site: use WordPress’s internal search, generate template links from IDs, and maintain redirects when URLs change. For a multilingual WPML site with frequent page moves, slug edits, or parent changes, consider WPML Sticky Links Addon as the fast route.

It associates internal links with page IDs and resolves the current permalink when the page is displayed, including links between language versions. That reduces the number of saved URLs you need to repair after structural changes, but you should still crawl the site after major migrations.