Search and Organic Discovery

Internal Link Opportunity Map

Map useful contextual links between related pages by matching real reader journeys, destination intent, anchor context, authority, and maintenance ownership.

Free editable Markdown · SEO specialists, content strategists, and editors · Updated July 30, 2026

Download Markdown

Accessible HTML preview

Blank template

The downloaded file contains the same fields in editable Markdown.

Topic and journey

Topic group: [Enter]
Primary audience situation: [Describe]
Entry task: [What brings the reader here?]
Next questions: [List in likely order]
Completion action: [What useful endpoint exists?]
Pages with no clear destination: [List content gaps]
Map owner and review date: [Name, YYYY-MM-DD]

Destination inventory

Duplicate for each destination.

Destination URL: [Enter canonical route]
Destination title: [Enter current visible title]
Search or user intent: [Explain one task it serves]
Unique contribution: [Why this is the best destination]
Audience and prerequisite: [Describe]
Status: [Live / Planned / Refresh needed / Merge candidate]
Locale coverage: [List actual available locales]
Maintenance owner: [Name/team]

Link opportunity

Duplicate for every proposed link.

Source URL and section: [Enter]
Source passage context: [Summarize nearby idea]
Reader's likely next need: [State]
Destination URL: [Enter]
Proposed anchor text: [Descriptive natural wording]
Placement: [Sentence / Callout / Navigation / Related resources]
Reader benefit: [Explain]
Priority: [High / Medium / Low and reason]
Conflict or distraction risk: [Describe or None]
Implementation owner: [Name]

Quality and implementation checks

The destination directly fulfills the anchor's promise.
The source and destination serve complementary rather than duplicate intent.
Anchor text is understandable without relying on the URL.
Links are not repeated unnecessarily in one small section.
The link does not interrupt a critical form, warning, or task sequence.
Localized pages use a real equivalent destination rather than an assumed route.
The rendered link, focus state, and destination status were tested.

Maintenance record

Implemented date and version: [Enter]
Redirect or canonical concern: [Describe or None]
Broken-link monitor: [Owner/process]
Recheck trigger: [Destination update, migration, quarterly review, other]
Observed reader evidence: [Queries, feedback, navigation behavior]
Decision after review: [Keep / Change anchor / Change destination / Remove]

How to use this template

Define a topic group and list the distinct tasks readers need to complete.
Inventory the strongest existing destination for each task and identify genuine gaps.
Find source passages where a destination resolves the reader's likely next question.
Write descriptive anchors, prioritize by reader value, and implement without disrupting the page.
Test rendered links and schedule review for moves, merges, localization, and content changes.

Map reader transitions before scanning for keywords

Choose one topic group and list the different tasks a reader may have: understand a concept, compare choices, perform a procedure, troubleshoot, verify evidence, or start using a tool. Identify the best existing page for each task and note gaps where no useful destination exists. This creates a journey map rather than a web of arbitrary phrase matches. A methodology page might appropriately link to a score-interpretation guide because limitations raise a practical next question. Two broad marketing pages may mention the same term but offer no meaningful reason to send readers between them. A link should reduce effort, add necessary depth, or reveal a related decision.

Evaluate both the source context and destination promise

For every opportunity, record the source passage, intended anchor, destination, and reader benefit. The anchor should describe what the reader will find without stuffing exact-match phrases or repeating “click here.” Read the sentences around it: a standalone “related article” box may be useful, but a contextual link placed at the moment of need is usually easier to understand. Open the destination and verify that its title, main content, and current behavior fulfill the promise. Avoid pointing many different intents to one generic page when a precise help, research, or product page exists. Also protect important actions from being surrounded by distracting links.

Prioritize, implement, and maintain the map

Rank opportunities by reader value, content relationship, discoverability, and page importance—not by imagined ranking guarantees. Begin with orphaned or hard-to-find resources that clearly complete common journeys, then repair misleading anchors and outdated destinations. Record the implemented URL and verify it in rendered content, including localized paths. Internal links can fail when routes move, canonicals change, pages are merged, or translations lag. Assign an owner and a recheck trigger. Use Search Console and on-site behavior as clues about unmet journeys, but interpret data alongside page purpose rather than adding links solely because a query contains the same words.

See the fields in context

Fictional example: detector interpretation journey

This mapping illustrates an editorial decision and does not claim that a link will cause a search ranking change.

Source context: A methodology section explains that detector scores are uncertain and should not prove authorship.
Reader's next need: Understand what to do with a mixed result.
Destination: A fictional score-interpretation help article with decision steps and limitations.
Anchor: “how to interpret a detector score,” placed after the limitation rather than in the opening.
QA decision: Keep the contextual link and avoid adding a second identical link in the same section.

Frequently asked questions

How many internal links should a page contain?

There is no useful universal count. Add links that serve relevant next steps without making the page difficult to read or distracting from its main task.

Should anchor text exactly match a keyword?

Use concise language that accurately sets destination expectations. Natural variations are fine; forced repetition can reduce clarity and trust.

How should orphan pages be handled?

First ask whether the page remains useful and current. If it does, connect it from relevant journeys and navigation; if not, refresh, merge, redirect, or retire it deliberately.

Do links need to be the same across translations?

The reader need may be equivalent, but each locale should link only to a real, reviewed destination in that language or clearly signal a language change.