Internal Link Modules: Anchor Text, Density and Placement

An internal link module is a deliberately authored link inside the main content, together with enough surrounding language to explain why its destination matters now. It is not a random keyword link or an end-of-page recommendation widget. Its smallest useful form is one sentence: “After the workflow is stable, document it as a how-to guide ; when the same workflow solves a buyer’s named problem, connect it to the relevant use-case page .”

That sentence is the element rendered. The anchors predict two different destinations, while the surrounding clauses explain the informational-to-commercial progression. The link is visually quiet because its job is to remove friction from reading, not interrupt it.

Why this element matters

Readers click internal links when the cost of staying on the current page becomes greater than the cost of following a useful route. A definition may be unfamiliar, a procedure may require a prerequisite, or an educational explanation may have made the reader ready to evaluate a solution. A contextual link works because it appears at that precise decision point. The reader does not have to search the menu, interpret a generic “learn more” label, or remember a page mentioned several paragraphs earlier.

Machine extractability is the ability of a crawler, search engine, or AI retrieval system to recover a relationship from the HTML without inferring it from visual styling. A normal <a href> creates a crawlable edge between the source and destination. Descriptive anchor text names the destination subject, and the containing sentence adds the relationship: defines, explains, compares, proves, applies, or sells. Together they make a stronger content-architecture statement than a bare URL, a JavaScript click handler, or the word “more.”

Internal links also distribute discovery and internal authority. They help a newly published page become reachable from established pages and show how broad pages, narrower answers, and commercial destinations fit together. That benefit is earned only when the relationship is real. Adding links for density alone teaches readers and machines that anchors are noise.

Use the element writing rules as the precedence rule. When a passage’s purpose is to connect the current idea to a specific internal destination, use this typed module even if the final rendering is an ordinary inline link. A heading, bold text, or manually styled sentence does not preserve its destination, relationship, variant, and review rules across publishing systems.

When to use it

Use an internal link module when the destination answers a likely next question created by the current sentence or section. Strong reasons include defining an unfamiliar concept, supplying a prerequisite, expanding a deliberately summarized subtopic, showing supporting implementation detail, comparing options, providing proof, or moving from an understood problem to a relevant commercial solution.

The editorial test is simple: finish the sentence “A reader should follow this link now because …” If the answer names a concrete next need, the link has a purpose. If the answer is “because we want this page to rank,” “because the keyword appears here,” or “because the template expects three links,” remove it.

Near-miss cases are common:

• A citation is not automatically an internal link module. A source proves a claim; a contextual destination continues the journey. If an internal research page does both, identify its evidence role clearly.
• A glossary link is unnecessary when the term is already defined in place. Link only if the destination adds depth the current reader may reasonably need.
• A related-content block is not contextual linking. It offers several next pages after the article is complete. This element sits at the point where one destination becomes relevant.
• A breadcrumb is structural navigation. It expresses hierarchy independent of the surrounding sentence.
• A call to action asks for a conversion. A commercial bridge prepares the reader for a relevant commercial page without turning every educational sentence into a sales prompt.

Do not link every first mention automatically. First mention is a useful review trigger, not a mandate. A familiar term needs no detour, while a later technical distinction may be the exact point at which a deeper page becomes useful.

Ready to Monitor Your AI Visibility?

Track how AI chatbots mention your brand across ChatGPT, Perplexity, and other platforms.

Get Started Contact

Where to place it

Place the link immediately after the current page creates the need for its destination. This preserves cause and effect: state the concept or problem, explain enough for the current page to remain complete, then offer the route to deeper or more commercial material. The current page must still satisfy its own intent without requiring the click.

Do not put links on adjacent words, link an entire sentence, or place three destinations in one sentence. When two destinations are genuinely required, separate their roles with clear clauses. When three are required, use a list or related-content element.

For the informational-to-commercial bridge, place the link only after the educational passage has established a recognizable need. A paragraph explaining category criteria can then link to a matching category page. A diagnostic passage can link to a product capability once it has explained the symptom and the kind of solution required. Do not place the commercial route in the opening definition, the direct answer, or a neutral warning; those positions make the page feel captured by the sale.

Anatomy

The labelled anatomy contains six parts:

1. Need statement: the concept, question, prerequisite, or decision that makes another page relevant.
2. Anchor text: the visible linked words that predict the destination without relying on nearby text.
3. Destination URL: one canonical internal path that resolves without an avoidable redirect.
4. Relationship phrase: language such as “use,” “compare,” “see evidence,” or “evaluate” that explains why the reader should move.
5. Variant: the editorial role: prerequisite, depth, lateral, or commercial bridge.
6. Context boundary: the complete sentence or short paragraph that remains intelligible when the link styling is removed.

Stay Updated on AI Visibility Trends

Get the latest insights on AI mentions, brand monitoring, and optimization strategies.

Email address

Subscribe

Design examples

The visual treatment stays consistent; the variants are defined by editorial relationship. This prevents authors from choosing a bright card when what they really need to choose is the correct destination.

Prerequisite link: routes to knowledge or an action the reader needs before continuing. Use “Before you configure X, verify Y” rather than hiding the dependency after the step.

Depth link: offers detail the current page intentionally summarizes. The source paragraph gives a sufficient answer; the destination serves readers who need the full method, specification, or evidence.

Lateral link: connects a related concept, alternative, or adjacent task at the same journey stage. State the distinction so the link does not imply that two merely similar pages are interchangeable.

Commercial bridge: moves from education to a product, category, service, solution, or use-case page because the reader’s recognized need now matches that destination. Name the fit; do not substitute promotional adjectives for a relationship.

All four variants use standard link styling and visible focus. Color cannot be the only signal; use an underline or another persistent non-color cue.

Parameters

The body is the canonical source of reader-facing context. If anchor is omitted, derive it from the first and only link in the body. If both are present, they must match. A body with no link is invalid; multiple links require separate modules unless a paired relationship is reviewed.

title cannot hide necessary meaning because its tooltip is inconsistently available. Omit it by default. Never use rel="nofollow" to sculpt internal authority; remove or restructure a link that should not participate in discovery.

Syntax and code examples

The canonical component name is internal-link. The body form keeps the link inside its natural sentence while preserving the relationship as structured metadata.

Portable Markdown directive

:::internal-link{relationship="commercial" destinationType="solution"}
Once the workflow and success condition are clear, evaluate the [AI visibility solution for SaaS teams](/solutions/for-saas/) against those requirements.
:::

Hugo shortcode

{{< internal-link relationship="commercial" destinationType="solution" >}}
Once the workflow and success condition are clear, evaluate the [AI visibility solution for SaaS teams](/solutions/for-saas/) against those requirements.
{{< /internal-link >}}

This is the target contract, not a claim that this repository registers the shortcode. A Hugo implementation should render normal inline content and add no invalid block wrapper inside a paragraph.

WordPress block

<!-- wp:amicited/internal-link {"relationship":"commercial","destinationType":"solution"} -->
<p>Once the workflow and success condition are clear, evaluate the <a href="/solutions/for-saas/">AI visibility solution for SaaS teams</a> against those requirements.</p>
<!-- /wp:amicited/internal-link -->

WordPress should store this as a registered block or controlled inline format. Saved HTML must contain an ordinary anchor so the link survives disabled JavaScript, feeds, export, and migration.

Examples

Good: the link completes a thought

Start with pages that already earn impressions but no longer answer the current query completely. Use the [content refresh checklist](/seo-playbook/process/checklists/content-refresh/) to verify claims, examples, links, screenshots, and the publication date before republishing.

This is good because the first sentence identifies the candidate, the second explains what the destination helps the reader do, and “content refresh checklist” predicts the page. The source remains useful without a click, while the destination supplies an actionable process.

Bad: density replaces judgment

For more information, [click here](/seo-playbook/process/checklists/content-refresh/) to learn about [content](/seo-playbook/) and read our [best guide](/seo-playbook/post-types/ultimate-guide/) for more details.

This fails for several independent reasons. Three links compete in one sentence. “Click here,” “content,” and “best guide” do not predict their destinations. “Best” makes an unsupported claim. The sentence creates no reader need, and “more information” explains neither the relationship nor the expected outcome. Removing two links and rewriting the remaining anchor is better than adjusting colors or adding title attributes.

Anchor text and density rules

Anchor text is the visible linked phrase. Its purpose is prediction, so write the destination’s stable subject in the language that fits the current sentence. Prefer a noun phrase such as “content refresh checklist,” “category-page criteria,” or “API authentication guide.” Add a verb outside the anchor to express the relationship: run, compare, verify, diagnose, or evaluate.

Exact-match anchor text is allowed when natural, but repetition is not a goal. Keep the same core noun for one destination and vary qualifiers only when context differs. Never use the same anchor for two destinations or promise a subject the destination does not cover.

Link density is the concentration of links in a passage. Too many links increase visual noise, expand the reader’s choice set, and make every individual relationship look less deliberate. Because paragraph length and reader intent vary, there is no universal ranking formula. The production rule is a review threshold: average no more than one contextual link per 100 words in ordinary prose, allow no more than two within one H2 section unless that section is explicitly navigational, and avoid more than one link in a sentence. This is an editorial ceiling, not a target to fill.

There is no minimum. Count only editorial links in main content against the threshold; breadcrumbs, table-of-contents anchors, citations, and footer navigation have different purposes.

For a commercial bridge, use one destination per distinct buyer need and normally link that destination once. Repetition turns a helpful route into pressure. The destination must substantiate the promised fit with its own copy, proof, specifications, or workflow; it cannot be a generic sales page selected merely because it converts.

Schema markup and accessibility

Contextual internal links do not feed a dedicated Schema.org type. They remain part of the enclosing Article, TechArticle, Product, or WebPage. Do not invent InternalLink, add ItemList markup to ordinary prose, or duplicate visible links as hidden structured data. If a link points to an entity described elsewhere in page schema, its visible URL and name should remain consistent with that entity, but the anchor itself needs no JSON-LD.

Use a real <a href="/canonical-path/"> element. An onclick span can fail keyboard navigation, copying, crawling, and non-JavaScript rendering. Open internal links in the same tab by default; warn users if a product requirement forces a new one.

The visible anchor must make sense when assistive technology presents links out of context. “Content refresh checklist” works; repeated “learn more” links do not. Keep the keyboard focus indicator visible, maintain a non-color link cue, and do not override the accessible name with an aria-label that contradicts the text. Avoid wrapping multiple paragraphs, controls, or an entire card in one anchor. Ensure the destination exists and the link works at keyboard and touch zoom sizes.

Writing rules

These rules exist to protect comprehension before they protect internal-link metrics:

• Write anchors as two to eight words where possible and never exceed 75 characters. A short, specific noun phrase is easier to scan and announce than a linked sentence.
• Give every link a relationship that can be expressed as prerequisite, depth, lateral, or commercial. If none applies, remove the link.
• Keep one link per sentence by default. Two are allowed only when the sentence explicitly distinguishes paired destinations; three require a different structure.
• Keep the source page complete. A link may offer depth, but it must not outsource the direct answer, a necessary warning, a critical step, or the evidence required for the current claim.
• Use neutral, factual tone. “Compare the plans” is credible; “discover our amazing solution” is promotional noise.
• Link to canonical, indexable destinations with leading and trailing slashes. Remove tracking parameters and avoid redirecting URLs.
• Review the anchor when a destination changes title, scope, status, or canonical URL. A technically working link can still become a broken promise.
• Never put a naked URL, “click here,” “read more,” unsupported superlative, coupon code, price claim, testimonial, citation marker, or multiple competing calls to action inside the module.
• Never hide a link in punctuation, an empty element, an image without an accessible name, or text styled to resemble ordinary non-interactive copy.
• Never create reciprocal links automatically. Link back only when the reverse route also serves a real reader need.

Post types that use it

The postTypes frontmatter defines the eligible cross-pillar relationships for this element. Each post type still applies the module only where the current page creates a credible next need.

The table describes eligibility, not a quota. Use zero modules when no destination fits; use several only when separate sections create separate needs within the density ceiling.

QA checklist

• Every link answers a specific next question created by the nearby sentence or section.
• The relationship is classified as prerequisite, depth, lateral, or commercial.
• The visible anchor predicts the destination without relying on “click here,” a tooltip, or the URL.
• The source passage remains complete if the reader does not follow the link.
• The link appears after the need is established and does not interrupt a direct answer, claim-and-evidence pair, warning, or conversion action.
• Ordinary prose averages no more than one contextual link per 100 words and no section exceeds two without an explicit navigational purpose.
• No sentence contains more than one link unless two destinations are deliberately contrasted.
• Informational-to-commercial links state the reader need and destination fit without unsupported promotional language.
• Each destination is canonical, internal, indexable, current, and free of tracking parameters or avoidable redirects.
• Duplicate links to the same destination have a documented, materially different reason.
• The rendered HTML uses a real anchor with an href and works without JavaScript.
• Link styling is distinguishable without color alone, and keyboard focus remains visible.
• Accessible names match visible anchors; no contradictory aria-label or image-only link is present.
• The module contains no prices, coupons, testimonials, citation markers, or competing calls to action.
• Frontmatter postTypes agrees with the rendered post-type table.
• A reviewer can explain every link’s benefit to the reader without mentioning rankings or a template quota.

FAQ

The academy template renders the FAQ entries from frontmatter.