Colquhoun.AI
← All guides

Research Guides

An Internal Link Audit for a Small Website

· Colquhoun.shop editorial

A useful page can be difficult to find even when its address works perfectly. A customer reads your explanation of a service, wonders what happens next, and has to start searching again. An internal link audit finds those gaps between pages you already control.

Start with one customer journey and a small set of public pages. The result should be a short list of justified changes, each with an owner and a test. You do not need to invent a link score or add links to every sentence.

Write a concrete task, such as “Understand the maintenance service, check what is included, then find the enquiry instructions.” Select the starting page and the destinations that genuinely help with that task.

For a first pass, review five to ten pages that your team considers important. That is a practical work limit, not an SEO benchmark. Keep a separate list of pages you have not inspected. Exclude private customer areas and anything that should not be publicly discoverable.

Google recommends that important pages have an incoming link from another page on the site. It also says there is no ideal link count for a page. Use relevance and the reader's next question to decide where links belong. Google's link guidance explains these principles.

For each destination, ask which existing page creates a natural reason to visit it. A service explanation might lead to its inclusions; a troubleshooting article might lead to the exact setup instructions. A distant footer link may provide a route, but it does not necessarily answer the question at the point where it arises.

Record the route, not just the destination

Create one row for each proposed or observed connection. Two links from the same page may serve different purposes, so include their positions rather than collapsing everything into a URL count.

Keep recommendations separate from observations. “Readers will probably want pricing here” is a hypothesis. “The pricing section contains no link to the public plans page” is something another reviewer can check.

This record also helps reject unnecessary work. If an existing link is clear, useful and functioning, “leave unchanged” is a valid result. If the destination needs substantial revision first, use our content workflow guide to prepare a page worth directing readers to.

Check whether the label sets the right expectation

Read the link wording before opening its destination. Can you predict whether it leads to an explanation, a form, a file or a different service? Then follow it and compare that expectation with what appears.

For example, replace an isolated “More” beside a maintenance summary with “See the maintenance tasks included,” if that accurately describes the destination. Do not label a sales page as a free checklist when it contains no checklist.

W3C's explanation of link purpose in context allows purpose to be conveyed by the link text alone or together with programmatically determined context. Clear standalone wording is a useful editing goal, but a short label is not automatically an accessibility failure. Check the associated sentence, paragraph or other supported context before making that judgment.

Avoid changing every link to the same keyword-heavy phrase. Different destinations should be distinguishable to the person choosing between them. Describe what the page actually offers in the language your customers use.

A card that responds to a mouse click is not enough evidence about how its destination is represented. Ask the implementer to inspect the rendered markup. Google generally recommends an HTML anchor whose href attribute specifies a resolvable destination address. Record what was inspected rather than inferring the implementation from the design. See the crawlable-link examples.

JavaScript can insert valid links into a page. An initial HTML response that lacks a link is therefore different from a rendered page that lacks it. Google's JavaScript SEO guide explains that it extracts links during initial processing and again after rendering. Note whether your evidence came from the initial response, a rendered browser page or a search-engine inspection. None of those observations alone proves that the destination is indexed.

Also test the intended route with a keyboard. Standard HTML links provide native keyboard operation and expose information to assistive technologies, as described in W3C technique H91. Check that the user can reach and activate the link, see where keyboard focus is and recognize its purpose. This is a focused check, not a claim that the entire website meets an accessibility standard.

Treat a missing report entry as a question

If you have access to Search Console, its internal-links report can help identify pages and connections to investigate. It is not a complete, current map of your website. Google documents sampling, URL grouping, table limits and historical links that may have disappeared. Read the Links report limitations.

Do not label a page “orphaned” solely because it is absent from that report or from a small manual review. An orphan-page finding needs an adequate search for incoming internal links across the relevant site. If your inspection covered eight pages, report “no incoming link found in these eight pages.”

A crawler can widen the review, but its scope and rendering settings still matter. Keep those settings with the findings. An access refusal or incomplete crawl should remain an evidence gap, not become a confident zero.

A fictional review with three different decisions

Imagine a small consultancy reviewing its service, inclusions and enquiry pages. These examples are invented; they are not observations about a real business or Colquhoun.shop.

On the service page, a paragraph explains that support includes routine checks, but gives no route to the detailed inclusions. The reviewer proposes one contextual link labeled “See the routine maintenance checks.” The destination already contains that list. This is a relevant addition with a specific purpose.

On the inclusions page, a link labeled “Get a quote” opens a general contact page whose only visible details are office hours. The reviewer assigns a content decision: provide real quotation instructions or relabel the link to match what exists. They do not declare the route fixed merely because the page loads.

On the enquiry page, a footer link already leads to the privacy notice with clear wording. It works and serves the form's context. The reviewer leaves it alone. Adding several more privacy links would not address either of the first two findings.

The review produces two actions and one confirmed no-change decision. It does not establish a ranking improvement, and it does not require rebuilding the site navigation.

Retest the journey after the edit

Begin from the original starting page, rather than opening the destination directly. Check the wording, activation, final page and promised content. For a shared navigation or card component, also inspect other pages that use it so that a local improvement does not create a wider mistake.

Record what changed and what passed. “Link added” describes implementation; “reviewer reached the stated instructions from the service page” describes the tested result. Leave untested device, browser or accessibility conditions visible.

If useful analytics already exist, review relevant onward visits or completed tasks over a sensible period. Keep those observations separate from claims that the link caused a search-traffic change. The immediate achievement is simpler: a visitor can reach the next useful page, and your team has evidence that the route works.

This guide describes the built-in Web Reader and Keyword Density behavior verified for this publication. Available data depends on the page response; these tools do not measure visits or search rankings.