Internal link coverage is a proportion of priority pages with useful incoming routes, not a fixed number of links per article. Define the page set and link types before calculating a percentage.
Work through the decision
Use a small, dated sample before applying the method across a whole site or team. Record the exact input and intended outcome so another reviewer can reproduce the decision. The example below illustrates the method; it is not a claimed Megvi client result.
| Step | Practical check |
|---|---|
| Set the denominator | List published, indexable guides and service pages that matter to the current cluster. Exclude drafts and deliberate redirects. |
| Count useful incoming | Require at least one checked contextual link from a live page. Count navigation separately. |
| Prioritize gaps | Rank uncovered pages by commercial value, evidence and reader task rather than age alone. |
| Re-audit after edits | Confirm the source still contains the link and the target resolves to the intended page. |
Worked example
Illustrative cluster: 12 priority guides, eight have a verified contextual incoming link, three have only archive links and one redirects. After excluding the redirect, coverage is 8 of 11, not 8 of 12. The team repairs the three live gaps and records the source URLs; it does not aim for ten links on every article.
When this approach can fail
Coverage is only as accurate as the crawl scope and classification. A link hidden in a script or removed from a page can make an old audit stale.
Verification checklist
Save the URL set, crawl date, source-target edge list, exclusion reasons and a manual sample of at least three counted links.
Next step
If two linked guides compete for the same query, evaluate Recognizing Query Cannibalization Without Overreacting. To apply this to a live business, review Megvi’s SEO services and bring the current page, report or workflow plus the result you want to verify.
Reference: Google Search Central: Link best practices, checked 23 October 2026. The example above is illustrative; check the current platform and site configuration before acting.