Completely Check Internal Linking After a Relaunch
After a relaunch, navigation, templates, context links, breadcrumbs, and redirect targets must be crawled and compared with the old link graph.
For SEO and content teams, "Comparable Inventory" and "Complete Crawl" are crucial when "Checking Internal Links After a Relaunch." The perspective "Link Quality and Ongoing Monitoring" shows how these two points work together in practice.
Published: 3 min read · Author: Sebastian Geier
Which checks reliably detect lost internal paths after a relaunch?
Before and after, URLs, inbound links, click depth, status, and canonical tags are compared. Additionally, rendered samples check navigation, JavaScript components, and critical tasks that a pure HTML crawl might miss.
Error codes only
Error codes only – All links respond successfully, but lead to generic hubs or new, irrelevant destinations and lose their original context.
Hidden rendering – Dynamic navigation does not appear in the browser or appears differently, even though the unfiltered source code contains links for crawling.
Missing Baseline – Without an old crawl, declines in inbound traffic and depth go unnoticed because only the new state can be viewed.
Practical Example: “Only Error Codes”
After the relaunch, all previous advice addresses respond successfully via redirects. However, the comparison shows that a new topic hub does not provide links to three important target pages; a browser test confirms the error in the dynamic map component.
Comparable Inventory
Test criterion
Comparable Inventory
Old important URLs and their inbound traffic are linked to the new target pages, so that lost relationships become visible instead of just missing addresses.
Test criterion
Full Crawl
Status, canonical, internal source, anchor, click depth, and redirects are captured for the entire reachable target state.
Rendered Path Critical templates and tasks are manually checked with the actual running interface, focus, and dynamic links.
Full Crawl
Before switching, old URLs, internal sources, anchors, depth, and priority paths are saved as a reliable comparison basis.
After publication, a full crawl captures the same data set and maps differences to the planned target relationships.
Rendered tests on key templates and user tasks close gaps in JavaScript, navigation, and actual usability.
Rendered Path
Important landing pages with less relevant inputs, greater click depth, incorrect canonical tags, or inappropriate redirect assignments.
Rendered links and critical user paths that are missing, hidden, or unusable despite correct crawl data.
What questions arise next?
A suitable in-depth resource is available Strengthening priority pages without linking to them on every page."Which internal links strengthen a priority page better than a sitewide link?"
In addition: Change URL structures without disrupting the content logic..
If you want to practically implement "Checking Internal Links After a Relaunch," you can find more information at [link to relevant resource]. Robust Website Systems Refer back to this. The focus there is on "Link Quality and Ongoing Monitoring" and "Comparable Inventory."
Conclusion: Check Internal Links After the Relaunch
A relaunch audit must compare relationships and paths, not just status codes. Crawl and rendered usage cover different error classes.
Sources and Further Information
These primary sources make the assumptions, system boundaries, and testing methods for "Checking Internal Links After the Relaunch" comprehensible.
Search Analytics: query – Google Search Console APIThe official API reference defines segmentable search performance data by page, search query, country, and device; internal click data must be collected separately.
Link best practices for Google – Google Search CentralThe official documentation provides verifiable technical and semantic requirements for internal links.
Key Thesis
A full crawl compares old and new URLs, inbound links, click depth, status codes, and canonical targets. Critical templates and user paths are also manually checked in their rendered state.
What This Is Not About
Testing individual menu items and error-free start pages does not cover lost internal paths after a migration.
What it's about
A complete comparison combines crawl data, old mappings, and rendered user paths across all relevant templates.
Internal Linking & Topic Clustering
Treating Broken Internal Links as a Quality and Process Problem
"Checking Internal Links After Relaunch" includes the question, as a separate check step, of how a process prevents the same types of broken internal links from recurring.
Internal Linking & Topic Clustering
Automatically Linking New Articles Internally in a Controlled Manner
"Checking Internal Links After Relaunch" is supplemented with a separate decision: How are new articles automatically integrated without creating irrelevant link patterns?
Insights Overview
All VELUNO Insights at a Glance
Further analyses on Website Systems, digital visibility, and robust working models.
Full Crawl: First Check Step
The old crawl is linked to the new targets as a target relationship. Deviations in entry point, depth, and target type then form the prioritized manual checklist.