ZINC / Demand

Internal Link Audit: Find the Pages Your Site Hides

October 6, 2026 / / Demand

Overhead illustration of a guide linked to a how-to, checklist and service beside an internal-link audit.
TL;DR

Find important pages that relevant parts of the site do not link to. Add descriptive links where they help readers move from a question to a useful answer or service. Repair broken destinations and verify the resulting journey; link counts alone are not the goal.

A useful page is easy to miss when visitors can reach it only through site search. An internal-link audit checks the routes people actually use.

Begin with important reader tasks, using the four-pillar framework.

1. Name the pages worth reaching

List important services, categories and core guides. Write each page's purpose and the reader task it supports. For ZINC’s service-aligned model, record each article’s single primary service, matching pillar and exact destination URLs.

Do not prescribe an arbitrary link count. Decide which connections help someone use the content. The content-hub planning guide shows how to connect a service-aligned category with its supporting articles.

2. Walk the public routes

Browse from the homepage, relevant overview and article hub. Repeat with mobile navigation. Record unclear labels, dead ends and pages reachable only through search.

Google's ecommerce structure guidance explains navigational discovery and notes that Google generally does not submit site-search queries.

3. Inspect destinations and labels

Compare two lists: the pages you intend to publish, and the URLs discoverable by following internal links from the homepage. Export the intended list from the current CMS or route inventory and reconcile it with the sitemap. A sitemap can itself be incomplete, so do not treat it as the only inventory.

Use an existing crawler to follow internal links from the homepage, or inspect the links manually for a small site. If the crawler also accepts a supplied URL list, keep that inspection separate: a page fetched because you supplied its address has not thereby been discovered through an internal link. Compare the intended URLs with the crawl's discovered URLs and incoming-link report. Normalise the verified preferred hostname and redirects before declaring a mismatch.

A published page missing from the homepage crawl is a candidate orphan, not an automatic verdict. Check whether navigation needs rendering, a section requires access, or the crawl stopped early. Resolve those limits, then inspect the page's actual incoming links. Record source, destination and visible text. Google's link guidance recommends real crawlable destinations and descriptive text.

Check missing pages, unnecessary redirects and label/destination disagreements. Resolve canonical questions before replacing URL versions everywhere.

4. Add the connection where it helps

Read the likely introducing page. Link at the point where the reader needs a deeper explanation, relevant service or product choice.

Check direct article-to-pillar and article-to-service links, then the pillar and service routes back to relevant articles. Connect useful peers within the pillar first; add cross-pillar references when they answer the reader’s next question. Skip links that repeat the same answer. Our content brief guide helps plan these relationships before drafting.

Illustrated reader questions and article outlines connected to a content guide.
One reader question, a clear answer and a useful next page.

5. Repair shared defects at the source

Fix a broken header link in the header. Fix outdated generated URLs in the template, rather than editing isolated output.

Web development owns navigation behavior; SEO work defines useful content relationships. Retest the original journeys after release.

Use this link repair record

  • Important destination and reader task.
  • Source page and existing link text.
  • Observed problem or missing connection.
  • Preferred destination and proposed wording.
  • Template or editorial owner.
  • Mobile and desktop retest result.

A newly added link should explain a relationship. Verify that the intended page became easier to reach before calling the audit complete.

A missing-link finding you can actually repair

Illustrative inventory: the CMS lists /blog/net-sales-definition/, and it loads successfully, but the homepage crawl finds no incoming internal links. The business-intelligence category lists the other reporting articles but omits this one. Searching for the URL directly proves the page exists; it does not prove visitors can discover it.

The category omission belongs in its article-listing logic. A second useful editorial route is the existing dashboard-preparation article's paragraph about inconsistent revenue: link “define net sales” to the definition article there. After repair, rerun the crawl from the homepage without supplying the missing URL. Confirm the category and contextual links are recorded, and follow both on mobile. That verifies the specific discovery gap rather than merely increasing a link count.

Map one useful path

Take a hypothetical reporting service and its business-intelligence category. The category should help readers find the metric-definition and data-preparation articles. A metric article might link to data preparation when the reader is ready to gather records, and to the service when implementation help becomes relevant.

Introducing page Reader's next question Useful destination Retest
Reporting service What guidance supports this service? Business-intelligence blog category Follow its link from the service page
Reporting category How should this number be defined? Metric-definition article Find it by browsing the category
Metric-definition article Which records do I need? Data-preparation article Follow the descriptive link in context
Metric-definition article Who can implement the reporting? Relevant reporting service Check scope and the inquiry route

This is a hypothetical relationship map, not a claim that those example URLs are published. Replace it with actual pages in your inventory.

Record the source page, reader’s next question, destination, proposed anchor and result. “Define net revenue” tells a reader more than “click here”. Open every changed destination and confirm that it returns the intended content without a redirect chain. Check mobile and keyboard navigation too. A page with many links can still hide its most important next step.

Retest the route that was missing

Use one row per relationship. Record the introducing page, reader task, anchor and destination, then follow the repaired route on mobile and desktop. Keep crawl discovery separate from a URL fetched because you supplied it.

Download the internal-link repair sheet. Open the CSV in your spreadsheet application, keep the specimen labelled, and add your own rows. Pending observations are work to complete, not failed or successful results.

Sources

A question about this article? Message Wendy

ZINC / Request for proposal

SEO

A clear brief.
A useful next step.

Turn search priorities into a scoped plan. Tell us about your business, scope and timing.

01 / Your business
02 / What you need
Build
Demand
Intelligence
03 / The context

Jaymie receives your request and coordinates the next step.

Tell us about your project and how to reach you.

ZINC DIGITAL.
ZINC / A conversation
Projects & conversations

Message Jaymie.

Have a question before writing a brief? Jaymie manages incoming inquiries and will help with the next step.

Delivered by email. Jaymie can reply to the address you provide.

ZINC / A conversation
Articles & editorial

Message Wendy.

Ask about an article, a source or an editorial detail. Your message goes directly to Wendy.

Delivered by email. Wendy can reply to the address you provide.