# Internal links after a URL restructure: a release checklist Source: https://insights.ramfaseo.se/internal-links-after-url-restructure/ Author: Ramin Amirhaeri Published: 2026-10-23T21:22:07+00:00 Updated: 2026-10-23T21:22:07+00:00 Publisher: RamfaSeo Insights. Public article text; menus, forms and visual presentation are omitted. Refer to the original page for full context. A redirect map can be correct while the site still sends every visitor through old URLs. It can also hide a more serious problem: a useful page survives the migration but loses every sensible route into it. This checklist is for the point where the new URL structure is known and you need to verify the links around it. It complements the [WordPress migration checklist](https://insights.ramfaseo.se/wordpress-migration-checklist-a-tested-redirect-map-and-rollback-exercise/); it does not repeat the full migration process. ## Keep three lists, not one Start with the old-to-new URL map, the inventory of public pages that should remain available, and the links discovered by a crawl starting from the homepage. Each list answers a different question: where old addresses go, what should exist, and what people can reach. Do not use the XML sitemap as your only inventory. Compare it with published CMS content and the agreed list of important pages. Equally, do not assume every URL in a historical export should remain indexable. Removed products, internal search results and duplicate variants need explicit decisions. ## Test the destination and the route into it For each changed page, record the old URL, intended destination, referring page, link location, current href and observed final destination. Add the response status and any fragment identifier. These fields make a failed check actionable: the editor knows which paragraph to change and the developer knows which component produced it. Google's [site-move guidance](https://developers.google.com/search/docs/crawling-indexing/site-move-with-url-changes) includes updating internal links to the new URLs. Redirects remain useful for old external references, but internal links should point to the intended current pages. ## A small release matrix you can copy These are illustrative paths, not real Ramfa URLs: - Header: /services/old-audit/ becomes /services/technical-review/. Check both the desktop navigation and the mobile menu. - Article body: a guide links to the old service URL. Replace the href and check that the anchor still describes the new page accurately. - Fragment: /services/technical-review/#scope reaches the right page but the section was renamed. Update the fragment or preserve a stable section ID. - Pagination: a category has more articles than fit on the first page. Follow its next-page link and confirm that older articles remain reachable. - Language switch: the English service should open the equivalent Persian or Swedish service, where that version exists, rather than silently returning to a language homepage. A successful HTTP response is only part of the check. A link can return 200 and still send someone to the wrong product, the wrong language, or a page whose main content has disappeared. ## Check shared components before fixing individual pages Review the header, footer, breadcrumbs, category cards, related-content components, language selector and any dynamically loaded navigation. One shared fix may correct many links. Then check article bodies, reusable blocks, buttons and downloadable documents separately; those often retain manually entered URLs. Google recommends links that use an anchor element with an href and descriptive text in its [crawlable-links documentation](https://developers.google.com/search/docs/crawling-indexing/links-crawlable). A button that only changes JavaScript state is not a substitute for a normal article link. The [JavaScript launch checklist](https://insights.ramfaseo.se/javascript-seo-launch-checks/) covers rendering checks when the visible navigation and initial HTML differ. ## Find orphan pages by comparing the inventory with the crawl Crawl from the homepage using ordinary HTML links, then compare the reachable URLs with the public inventory. Investigate each missing page: is it intentionally excluded, linked only through search, or missing a parent or related article? An archive link counts as a real discovery path. An article deep in pagination is not automatically a strict orphan, but it may still be difficult to find. Record both zero-link pages and pages whose only route is a generic archive. For important guides, add a relevant link from an established article or topic page where a reader would need the extra detail. The [orphan-page guide](https://insights.ramfaseo.se/orphan-pages-how-to-find-them-why-they-dont-rank-and-how-to-fix-internal-linking-without-turning-your-site-into-a-link-farm/) covers the wider publishing problem. For large generated collections, use the [programmatic internal-linking guardrails](https://insights.ramfaseo.se/internal-linking-programmatic-seo-guardrails/) to decide which relationships belong in templates. Avoid adding an indiscriminate list of every article to every page. ## Decide what should block release I would treat broken routes to an agreed critical service, a language selector that loses the equivalent page, and an important retained page with no incoming path as release issues. A redirected editorial link still deserves correction, but its urgency depends on the journey and scope. Separate a confirmed 404 from a timeout or a third-party site that refuses automated requests. Recheck failures in a browser before removing useful external references. Record exceptions with a reason instead of making the final report appear clean by excluding difficult URLs. ## Keep the evidence small and useful Save the URL inventory, source-to-destination checks and any exceptions. Repeat the affected checks on the live site after release because production routing and caches can differ from staging. The completion statement should describe what passed and when; it should not promise that future edits can never create a broken link. If the project needs redirect design or release coordination, see [WordPress and migration support](https://ramfaseo.se/en/services/wordpress-seo-migration/). If the structure itself is unclear, begin with [technical SEO](https://ramfaseo.se/en/services/technical-seo/) before moving URLs again.