How to audit internal links on a small website
Crawl the site, group pages by reader task, and inspect incoming links to each important URL. Fix broken paths, orphan pages, vague anchors, and misplaced links first.
Written for a founder, publisher, or freelancer managing a website small enough to review page relationships by hand.
Key facts
- A real HTML anchor with an href gives users and crawlers a dependable path.
- Incoming-link count needs context; one relevant hub link can help more than repeated footer links.
- Anchor text should describe the destination's subject or task in the surrounding sentence.
A useful rule: make each important claim understandable and verifiable without requiring the reader to reconstruct your meaning from the rest of the page.
The direct answer
Export or crawl the site's canonical pages and count crawlable incoming links to each one. Mark the homepage, conversion pages, topic hubs, tools, and high-value articles. For every important page, identify at least one relevant parent or neighbouring page that should link to it. Repair broken links and orphan pages first, then improve anchor text and placement where a reader needs the destination. The finished work should let a reader or reviewer identify the subject, the intended result, the evidence behind the recommendation, and the next action without reconstructing your reasoning. Keep material conditions in the same passage as the claim they limit. Use the canonical public page as the source of truth, since search engines and answer systems retrieve pages rather than private briefs. Google describes useful, reliable, people-first content and ordinary search eligibility as the foundation for both search results and its AI features. No heading pattern or schema type can compensate for a page that gives a vague answer, hides its evidence, or serves a different intent from its title. Complete the task for one named reader first, then check how the result appears to crawlers and extraction tools.
- A real HTML anchor with an href gives users and crawlers a dependable path.
- Incoming-link count needs context; one relevant hub link can help more than repeated footer links.
- Anchor text should describe the destination's subject or task in the surrounding sentence.
Prepare the page and evidence before editing
Create a list of indexable canonical URLs from the sitemap and a crawl. Add page type, primary question, conversion role, incoming-link count, and the shortest click path from the homepage. Keep redirects and noncanonical parameters in a separate repair list. Save a baseline before you change anything: the public URL, response status, canonical, visible title, main heading, opening answer, source links, and the date you checked them. Record the target question in the reader's words and write one sentence describing the decision the page supports. This baseline prevents a common measurement error where several edits ship together and nobody can tell which one improved the result. It also gives editors a compact source ledger. A reviewer can compare each material statement with the cited page, its jurisdiction or product version, and its checked date. If the task affects a generated template, inspect several representative URLs rather than assuming one record proves the template works for every content shape.
- Compare sitemap URLs with crawl discoveries and explain every mismatch.
- Mark URLs with zero crawlable incoming links from indexable pages.
- Collect the anchor text and source page for links into priority URLs.
Complete the process in five controlled steps
Work through the five steps in order and keep one output from each step. The order protects you from polishing copy while a crawl, canonical, intent, or evidence problem still blocks the page. Each output should be small enough for another person to verify from the public URL. Use plain labels and stable entity names throughout the page. When a changing fact controls the answer, cite the primary source beside that fact and include the relevant date or version. After each step, compare the output with the primary question. Remove any section that serves a different reader decision, and link to a separate guide when the adjacent task deserves its own page. This creates a focused answer instead of a broad page assembled from loosely related keywords.
- 1. Clean the graph: Replace broken targets, redirecting links, and parameter variants with final canonical destinations. Evidence of completion: Internal navigation reaches a 200 canonical URL in one request.
- 2. Connect orphans: Add each valuable orphan to the hub, tool result, or guide where a reader needs it. Evidence of completion: The next crawl finds at least one contextual incoming link.
- 3. Clarify anchors: Replace vague labels with concise destination names that fit the source sentence. Evidence of completion: A reader can predict the page before opening it.
- 4. Strengthen journeys: Link problem pages to diagnosis, diagnosis to action, and action to the relevant tool or dataset. Evidence of completion: The path supports a real task instead of a generic related-post loop.
- 5. Control repetition: Remove sitewide or template links that add no navigation value and drown useful relationships. Evidence of completion: Repeated chrome no longer dominates the link report.
A worked example
A 24-page site has a strong guide on fixing sitemap exclusions, but only the XML sitemap references it. The audit links to the guide from the SEO checker result that flags sitemap trouble and from the indexing hub. It changes “learn more” to “fix a sitemap URL that is discovered but not indexed.” The crawler now reaches the guide in two clicks from the homepage, and the anchors explain its task. The team leaves footer links alone because they already serve global navigation and do not replace the contextual paths. Treat the example as a model of the reasoning, not as a universal benchmark. The useful part is the chain from question to evidence to action. Preserve the exact entity names, scope, and conditions that a reader would need if an answer engine quoted the passage outside the page. If a number comes from a report, state the reporting window. If a result comes from a test, state the URL type, device or crawler, and date. A compact example earns its space when it helps the reader make the same decision on another page. Remove invented precision, anonymous authority, and conclusions that reach beyond the recorded evidence.
- Sitemaps support discovery but do not explain a page's relationship to readers.
- Contextual links connect a current problem to the next useful action.
- Anchor text can be descriptive without repeating one exact phrase sitewide.
Avoid the mistakes that weaken the result
Link audits go wrong when a raw count becomes the goal. Sitewide navigation, pagination, and repeated cards can inflate counts while an important page still lacks a meaningful route. Fix the first mistake that changes eligibility or meaning before editing smaller presentation details. Keep source boundaries visible: one citation should support the nearby claim, while a separate claim should receive its own source. Do not repeat the target phrase to manufacture relevance. Search systems can use titles, headings, visible text, links, structured data, and other signals, so those elements should agree on the subject without copying one sentence across the page. Check the public result after deployment because a correct content record can still produce the wrong page through caching, layout inheritance, JavaScript failure, or a stale build.
- Adding links to every page makes the site harder to scan. Correction: Place links at the decision point where the destination helps.
- Using JavaScript click handlers without anchors removes a dependable crawl path. Correction: Render standard links and add interaction as enhancement.
- Forcing exact-match anchors into unrelated sentences damages readability. Correction: Name the destination in language that belongs in the source page.
Verify the result and choose the next action
Run the same crawl after deployment and compare broken links, redirect hops, orphan count, depth, and incoming anchors for priority URLs. Then review navigation clicks and query impressions for the linked pages without assuming that one link caused any change. Use a fixed observation window and compare like with like. Record the query set, country, device, page version, and publication or change date. Search impressions can show discovery and query matching; clicks and useful sessions show whether the result attracted the intended reader. Observed AI citations add a separate retrieval signal, but a citation count does not prove traffic or revenue. Review the cited passage when you can and check whether the answer preserved its subject, scope, conditions, and source. Keep the page stable long enough to collect evidence unless you find a factual error, broken route, security problem, or misleading claim. The next edit should respond to the strongest observed failure instead of a generic scoring recommendation.
- Require zero broken internal destinations in the canonical crawl.
- Require a contextual incoming link for each indexable priority page.
- Sample links in rendered HTML and keyboard navigation, not the crawl export alone.
Put it to work
Find the highest-impact fix on your site.
Check crawlable anchors, broken destinations, redirect hops, and page context.
Inspect internal link evidenceSources
- 1.Google Search Central: Make links crawlableChecked 2026-07-26
- 2.Google Search Central: SEO Starter GuideChecked 2026-07-26
- 3.Google Search Central: Build and submit a sitemapChecked 2026-07-26