Internal Linking Audit Checklist for WordPress Sites
An internal linking audit should tell you more than whether links exist. It should show whether the site is structurally coherent, whether important pages can be reached easily, whether topical clusters are supported properly, and where links are missing, noisy, or misaligned. On WordPress sites, this work matters because pages accumulate quickly while structure often lags behind. Posts are published, products are added, category pages grow, and old content stays live without being reconnected. A good audit turns that drift into an actionable map: what is underlinked, what is overlinked, what is disconnected, and what should be fixed first.
What an internal linking audit should detect
A useful audit is not just a spreadsheet of URLs and link counts. It should surface structural patterns.
At minimum, the audit should help you detect:
- orphan pages and near-orphan pages;
- pages that are too deep in the site structure;
- important pages that receive only menu or archive links;
- repetitive or vague anchor text;
- clusters with weak cross-support;
- broken pathways between informational and commercial content;
- template-generated links that create noise without context;
- WooCommerce or taxonomy pages that exist but are not truly integrated.
In other words, the audit should answer a practical question: does the site use links to explain its own structure, or are pages simply coexisting?
Step 1: map the page types before counting links
Start by classifying the pages you have. If you skip this step, you will treat every link as equivalent, which leads to weak recommendations.
For a typical WordPress site, separate at least these groups:
- homepage and key commercial pages;
- blog posts and guides;
- category or hub pages;
- feature or product pages;
- WooCommerce product pages, if relevant;
- FAQ, help, and documentation pages.
Each page type serves a different job. A category page is supposed to act like a hub. A product page may need links from guides. A blog post may need both incoming support and outgoing paths.
If you do not map page roles first, you cannot judge whether the links they receive are appropriate.
Step 2: identify orphan and near-orphan pages
Orphan pages are the clearest structural warning sign. If a page has no meaningful internal links pointing to it, search engines and users both receive a signal that the page is not deeply integrated into the site.
Near-orphan pages are only slightly better. They may receive one weak archive link or a buried category mention, but still lack strong contextual access paths.
During the audit, ask:
- Which pages have zero contextual internal links?
- Which pages are only reachable through tags, search, or a deep archive?
- Which pages matter commercially or strategically but receive almost no internal support?
On content-heavy sites, these pages are often old articles, migration leftovers, or pages created in campaigns that were never integrated into the wider site.
Step 3: evaluate click depth and structural distance
A page does not need to sit one click from the homepage to perform well, but extreme depth is still a warning sign.
The audit should highlight pages that require too many hops from strong entry points, especially when they are supposed to matter.
Look for patterns such as:
- commercial pages buried behind several navigational layers;
- guides that do not link onward to related product or action pages;
- documentation pages that are technically available but not integrated from support content;
- product category pages with no body-link support from adjacent informational content.
Depth is not only a navigation issue. It is often a sign that the site has not decided what deserves more internal visibility.
Step 4: review body links, not just navigation links
Many site owners assume the internal linking problem is “covered” because menus, breadcrumbs, and related widgets exist.
That is not enough.
Navigation links provide broad access. Body links provide contextual intent. During the audit, review whether important pages receive links inside meaningful paragraphs, not only inside templates.
Ask questions like:
- Which key pages receive contextual body links?
- Which pages rely almost entirely on menus, archives, or footers?
- Are the strongest articles sending readers toward the most useful next pages?
A healthy site usually has both: stable navigation paths and contextual cross-linking.
Step 5: inspect anchor text quality
Anchor text is often where weak linking habits become visible.
Common audit findings include:
- generic anchors such as “here,” “this page,” or “read more”;
- the same exact anchor repeated across many unrelated pages;
- anchors that match mechanically but do not fit the sentence;
- anchors that point to pages with overlapping rather than distinct intent.
You do not need to chase artificial anchor variation for its own sake. But you do need anchors that help clarify destination intent.
A useful audit notes whether anchors are:
- descriptive;
- contextually relevant;
- varied where appropriate;
- tied to the right destination pages.
This is also where a keyword layer can help. If target phrases are defined more clearly through Auto Focus Keyword for SEO, the linking workflow becomes easier to review later.
Step 6: evaluate hub pages and cluster support
Most sites have a few pages that are supposed to organize a topic: category pages, resource hubs, cornerstone articles, product collections, or feature overviews.
The audit should verify whether these hubs actually function as hubs.
Check whether they:
- receive links from relevant supporting pages;
- link back out to the right cluster members;
- connect informational and commercial content logically;
- avoid becoming dead ends.
A strong topic cluster usually has visible two-way support: the hub points to the supporting pages, and the supporting pages reinforce the hub and adjacent key pages.
Without that structure, the site may have all the right pages but still fail to present them as a coherent system.
Step 7: audit WordPress-specific traps
WordPress creates several structural illusions that can make a site look more connected than it really is.
Archive dependency
Posts may technically appear in categories, tags, or date archives, but those archive links often do not replace meaningful body links.
Builder-heavy pages with weak editorial linking
Pages built with page builders may look complete visually while containing very little contextual linking between related documents.
Auto-generated related posts blocks
These can be helpful, but they are not always topically precise. They should be reviewed as a supplement, not treated as a full strategy.
Legacy content after redesigns
Old posts stay indexed, but lose the internal support they once had because menus, categories, and templates changed.
Plugin-generated links left unreviewed
Automation can accelerate the work, but the audit must still identify edge cases, irrelevant matches, and pages that need exclusion.
Step 8: if the site is WooCommerce, review buying paths separately
WooCommerce stores need a dedicated linking lens because products, categories, and informational content often live in separate silos.
Your audit should ask:
- Do category pages support product discovery well?
- Do buying guides link to relevant category and product pages?
- Do product pages receive links from adjacent educational content?
- Are there meaningful paths between blog content and commercial pages?
A store can have excellent product data and still have weak internal structure. That is why internal linking for WooCommerce deserves its own treatment.
Step 9: prioritize fixes by impact, not by volume
The audit becomes useful only when it leads to prioritized action.
A practical prioritization model is:
High priority
- orphan or near-orphan commercial pages;
- important guides with no onward paths;
- weak hub pages in valuable topic clusters;
- broken buying paths on WooCommerce sites.
Medium priority
- repetitive anchors;
- overlinked template areas;
- deep pages that still have some support but not enough.
Lower priority
- aesthetic anchor refinements;
- minor cluster expansion opportunities;
- pages with limited business or traffic value.
The goal is not to “perfect” every page equally. The goal is to strengthen the parts of the site where structure has the highest return.
What can be automated and what should stay editorial
This is where many teams either over-automate or under-automate.
Automation is strong for:
- discovering pages without keyword support;
- generating repeatable internal links from a declared keyword layer;
- scaling first-pass structural coverage across large sites.
Editorial review should stay strong for:
- high-value pages;
- nuanced service pages;
- cluster strategy;
- anchor quality in sensitive contexts;
- exclusions and edge cases.
That is why the strongest workflow is hybrid:
- use Auto Focus Keyword for SEO for coverage,
- use Automatic Internal Links for SEO for scalable execution,
- then review strategically important pages manually.
A practical 30-minute audit example
If you need a fast first pass, do this:
- List your top 20 commercial or strategic pages.
- Check whether each one receives contextual links from at least two relevant pages.
- Review the top 20 traffic-driving articles and see whether they link onward to useful destinations.
- Inspect anchor text on a sample of 10 pages.
- Flag any page reachable only through archives or search.
- Note where product, category, and guide relationships are missing.
You will not finish the whole audit in 30 minutes, but you will identify the most obvious structural leaks.
FAQ
How often should an internal linking audit be done?
Large or active sites benefit from a light review monthly and a deeper audit quarterly. Smaller sites can often review less often, especially after major content pushes.
Are orphan pages always bad?
Not always. Some pages are intentionally isolated. But if an important page is orphaned, that is usually a structural problem.
Should I audit menus and footers too?
Yes, but do not stop there. The more important audit work happens in contextual body links and cluster relationships.
Can plugin automation replace the audit?
No. Automation can improve execution and scale, but the audit is what tells you where structure is weak and what should be fixed first.
The practical takeaway
A strong internal linking audit does not chase vanity metrics. It reveals whether the site is actually connected in a way that supports discovery, understanding, and conversion.
If the answer is no, the next step is not random link insertion. It is a structured plan: define the keyword layer, identify the pages that matter most, repair the cluster logic, and use automation where scale makes manual work too slow.