Blog / Technical SEO /

How to review internal links after a content migration

The migration is declared finished because every article has a new URL. Then a reader follows an old internal link and lands on a page that no longer exists, or a key guide now sits three clicks deeper than it did. Redirect mapping protects some old entry points, but it doesn’t update the site’s own routes.

Internal links deserve their own migration review. The objective is to keep useful paths accurate and direct, which means checking links in source content, navigation, templates and structured components, not just asking whether old URLs redirect.

Build a source inventory

Before launch, I crawl the old site and export internal links for priority pages. Record source URL, target URL, anchor text, status code and whether the destination should survive. Include links generated by menus, breadcrumbs, related content blocks and product modules where you can. A crawl shows what’s rendered, while a CMS export can reveal links inside unpublished or hidden content.

After migration, crawl the new site and compare it with the inventory. Flag links that error, redirect somewhere unexpected, point to an outdated path or lose meaningful anchor text. A direct link is usually clearer than one routed through several redirects, though redirects still matter for external references and old bookmarks.

Distinguish broken from intentionally changed

Not every old link must point to a page with the same title. Content may be consolidated or retired. For each changed destination, ask whether the new page meets the original visitor’s need. A redirect from a detailed guide to a generic homepage works technically and fails the reader.

Keep an exception list with reasons: content merged, product retired, policy replaced, link no longer relevant. That lets reviewers tell planned removals from accidental gaps. If a replacement isn’t ready, decide whether to keep the source page for now or offer another useful destination.

Review anchor context

An anchor that says “read this guide” gets confusing once its destination changes. Check the surrounding sentence and update it when the new destination serves a different purpose. Descriptive anchors help readers know where a link goes, and they make the relationship between pages clearer.

Don’t force exact keywords into every link. Natural wording beats repetitive, awkward anchors. I care more that the reader can decide whether to follow the link and that the destination keeps the promise.

Navigation and reusable components are easy to miss. Check menu items, footer links, breadcrumbs, product recommendations, category cards, author profiles, image links and calls to action. A theme can hard-code URLs that never appear in the content export, so test important templates in a browser and inspect the rendered links.

On a multilingual site, review each language path on its own. A link in an Arabic page shouldn’t jump to an unrelated English destination unless that’s deliberate and clearly useful. Check the language switcher and internal links together.

Include non-HTML destinations such as PDFs, images and downloadable guides. A document can keep an old title or outdated policy information even when its URL works. Confirm it’s the intended version and the link text says what will open. Links in transactional and campaign templates may sit outside what a crawler reaches, so ask the owners for representative examples and test them separately.

Preserve useful context during redirects

Some links carry tracking parameters or a selected product option. Test those separately from a plain article URL. Keep useful context where the destination supports it and drop only parameters that are truly obsolete. If a parameter can’t be kept, make sure the destination still explains what the visitor has reached, not a surprising generic page.

Prioritise repairs

Fix broken links on pages with meaningful visits, external links or strategic importance first. Then links that interrupt a task, like reaching a product or support page. A long tail of obscure legacy links can wait for a separate batch, but record the decision and keep monitoring for new errors.

Use automated checks for status and redirect chains, then inspect ambiguous cases by hand. A tool can tell you a page returns 200. It can’t tell you whether that page answers the sentence that linked to it.

Make migration QA repeatable

Give editors a clear way to report links the automated checks can’t find. They may know a sentence points to a specific older resource, or that a campaign reuses a saved block. A migration is a team change, so make it easy to flag examples and see them fixed.

Keep a representative test list for every future migration: core navigation paths, high-value content, product journeys, policies and language pairs. Rerun it after deployment and after material redirect changes, noting the date and release reference so a later issue can be traced.

Choose one migrated article with several internal links and follow each one as a reader. Which link still leads where the sentence promises?