Internal linking and useful reader routes
Give navigation and context links different jobs.
Navigation gives readers predictable routes through a site. Context links lead from a specific idea or question to the explanation needed there. Use both when they serve distinct purposes, and remove repetition that adds no useful choice.
Free learning from Semantec SEO.
Classify a link by its purpose.
Navigation links provide repeatable orientation: a menu exposes broad areas, a breadcrumb shows the current page’s place in a hierarchy, and a local contents list moves between blocks on the same resource. A context link is introduced by the surrounding explanation and answers a more specific need, such as seeing a worked calculation or checking a term.
Location is a clue, not a complete classification. A related resource card after a paragraph may be contextual if the paragraph establishes the next task. A repeated sidebar of categories remains navigation even when it sits beside the article. Record the job before deciding to keep, move or remove the link.
The same destination can legitimately appear in a menu and in prose. The menu supplies a stable route; the sentence explains why that destination is relevant now. Judge the second placement by the help it offers a reader following the argument, rather than applying an absolute ban on repeated destinations.
Before adding a route, identify the source passage, the destination’s owned question and the reader’s next decision. If the destination cannot fulfill the promise made by the anchor, revise the wording, select the right page or leave the phrase unlinked. A familiar name alone does not establish a reading need.
Use menus and breadcrumbs for orientation.
A main menu should expose enduring areas that help readers choose where to start. A narrow example rarely needs its own global menu item merely because it exists. A branch hub can introduce such examples where their purpose is easier to explain. Keep the names and order of repeated navigation predictable across pages.
A breadcrumb represents a chosen hierarchy, not a transcript of the browser’s history. A page reached through search can still show a route to its contextual parent. Use readable parent labels and distinguish the current item from linked ancestors. If a page could belong to more than one branch, choose a coherent hierarchy and explain other relationships through content.
Do not expect a breadcrumb to teach a prerequisite or a menu to explain a specialist term. Those are different needs. Also, do not force a reader to rediscover the site’s main areas through scattered body links. Structure and explanation should complement each other.
WCAG 2.2 addresses link purpose in context and consistent navigation. Those criteria inform the route review; a tidy menu or readable label alone does not establish that the complete interface meets accessibility requirements. Keyboard focus, reading order and behavior also need observed checks.
Place related detail where the question arises.
Introduce the reason to leave the page before the link. A reader who has just learned what a concept means may benefit from an example. A reader blocked by an unfamiliar term may need a glossary entry first. The destination and the anchor should describe that next job rather than a vague invitation.
Choose between inline explanation and a separate route. Define a short term locally when understanding the sentence depends on it. Link to deeper detail when it would interrupt the main task, supports a different starting level or needs its own maintained resource. Do not hide a condition that changes the current answer on another page.
For ordinary crawlable HTML links, use an anchor element with an href and meaningful visible text. Google’s link documentation supports descriptive, contextual anchors. This technical form does not establish that the destination is useful; the editorial relationship still needs review.
Avoid packing many competing links into one short phrase. If readers need to choose among an example, a definition and a practical route, give each an identifiable label and enough surrounding context to distinguish them.
Worked example: connect an introduction, example and glossary.
This is a fictional learning resource about room planning. Its introduction explains that usable occupancy is the number of people a room can support for the intended arrangement, subject to the venue’s current restrictions. It is an editing example, not venue or safety advice.
Weak draft: “Occupancy limits help with room planning. Read more. For more information, read more.” Both links lead elsewhere, but neither identifies the destination as a definition, an example or a booking route. The global menu already contains “Learning,” which does not solve this local ambiguity.
Repaired introduction: “Room occupancy must be checked for the arrangement you intend to use. The worked seating example shows how a fictional planner compares two layouts. If the difference between seated and standing occupancy is unfamiliar, use the occupancy glossary before comparing the layouts.” The example and glossary have distinct jobs; neither substitutes for checking a real venue’s restrictions.
When adding the links, make “worked seating example” the anchor to the accepted example owner and “occupancy glossary” the anchor to the relevant glossary entry. The illustrative labels here are plain text because they are not approved pages in this site’s inventory. The table records the complete route plan without inventing live destinations.
| Placement | Reader need | Destination job | Decision |
|---|---|---|---|
| Main menu | Choose a broad learning area | Learning entry | Keep as navigation |
| Breadcrumb | Identify the parent branch | Room planning hub | Keep as orientation |
| Introduction after occupancy explanation | Apply the distinction | Worked seating example | One context link after explaining its purpose |
| Unfamiliar occupancy terms | Resolve a definition | Occupancy glossary entry | Context link beside the term |
| Repeated generic sentence | No new question | Same worked example | Remove redundant repetition |
Remove repetition without losing a useful route.
In the example, keep the broad Learning menu entry and the breadcrumb to the room planning branch. Keep one context link to the worked example where the reader is ready to apply the concept. Keep the glossary route beside the unfamiliar distinction. Remove a second “read more” link immediately repeating the same example without a new purpose.
A longer resource may need the same destination again after a distinct decision or in a usable summary. That is a contextual judgment, not a link quota. A footer contact route also has a different purpose from a source citation in the article. Review the reader’s situation rather than treating every repeated URL as an error.
Check the final destination, anchor, paragraph and interaction together. Test that the final page and any fragment exist, that the anchor’s promise is still accurate, and that navigation remains usable in the narrow layout. Record the source, link type, reason, owner, review date and next action so later edits preserve the distinction.
Sources and further reading.
The platform documents explain technical link handling. The decision records and fictional examples on this page are editorial methods; they do not report a live audit or guarantee a search outcome.
Continue learning
Choose the next related task.
Use the internal linking learning hub for related route decisions, or return to the semantic SEO learning overview to choose another subject.