Crawlable and meaningful links
Make the link work as a route, not just a visual cue.
A useful link combines a real destination, understandable wording and a reason to continue. Styling a phrase like a link does not give it a URL or make it usable by readers and crawlers.
Use an anchor with a real destination.
For navigation to a page, use an HTML <a> element with an href pointing to a real URL. A site-relative path can work; an absolute URL can work too. The relevant distinction is a resolvable address in the right attribute, not if the visible link resembles a button.
Google recommends this structure because it can generally extract those links. A span with a URL-like attribute or an anchor without href is not equivalent. Scripts can insert valid anchors, but a script event alone is an unreliable substitute for a destination. A real anchor also supplies ordinary browser behaviors such as opening the destination in another tab.
Check what the destination provides.
Open the target through the permitted review process and confirm its final URL, page purpose, relevant passage and access conditions. The title alone is insufficient. A destination that redirects to a generic homepage, requires an unexpected account, or has disappeared can fail the reader even if the link markup is correct.
Record source page and passage, target URL, purpose, destination status, intended reader and reason for linking. Hold a proposed link when the destination’s identity or usefulness is unverified. Do not guess a route from a keyword or create a different page merely to make the graph look dense.
Worked example: real navigation versus inert markup.
The following local comparison shows the difference without placing a dead control in the page. The real link below leads to the existing internal-linking learning hub. Its purpose is clear from the sentence. The inert version is escaped teaching code, not an invitation to click.
real destination: internal linking learning hub. Use it to choose the next relationship or anchor-writing topic. Inert imitation: <span class="link">Internal linking learning hub</span>. That span has no destination, despite any underline a stylesheet might add.
Recommended markup: <a href="https://semantecseo.com/internal-linking/hub-10/">Internal linking learning hub</a>. A misleading alternative such as <a onclick="goSomewhere()">Read more</a> hides both the address and the purpose. Do not add such a control as a functional example.
| Test | Real anchor | Inert styled span |
|---|---|---|
| Destination | href holds the hub URL | No navigable destination |
| Purpose | Names the learning hub in useful context | May look clickable but says nothing about behavior |
| Ordinary browser use | Native link behaviors available | Requires extra behavior that is absent here |
| Repair | Check target and accessible presentation | Replace with an anchor if navigation is intended; plain text if no route is needed |
Explain the relationship in the surrounding passage.
Link when the destination defines, supports, contrasts, extends or follows the current idea in a way useful to the reader. Shared vocabulary alone does not establish that relationship. A beginner explanation may need a definition; a specialist troubleshooting step may need a version-specific check instead.
Place the link beside the need it serves and describe what the reader will find. A route to a commercial page can be appropriate when the reader is choosing a service, but can interrupt a purely explanatory task if presented too early. Preserve hubs, related specialist pages and proof sources as distinct roles rather than linking every page to every other page.
Make the link usable beyond a mouse.
Use native link semantics and a meaningful accessible name. Check keyboard focus, a visible focus indication, activation and sensible focus order. Do not rely on color alone to communicate that text is linked. Where an image is the only link content, its text alternative needs to explain the destination or action; do not leave an unnamed image-only link.
WCAG’s link-purpose criterion at Level A allows purpose to come from the link text together with programmatically determined context. Descriptive standalone wording often helps readers using link lists. This is distinct from claiming that every link must satisfy the stricter link-only criterion. Review the real output with assistive technology and keyboard access before calling the component accessible.
Keep navigation and interface actions distinct.
A link takes the reader to a resource or location. A button normally performs an action such as submitting a form or opening a dialog. Use the native element matching the behavior. Do not turn an unavailable action into a fake navigation link or use an empty href as a placeholder in published copy.
If a planned destination is not ready, describe the pending information plainly or omit the route until it exists. Fragment links also need a real matching target on the page; an href ending in a missing ID is not a complete route.
Check the final page, not only the draft map.
Inspect generated HTML, the destination response and the rendered interaction as separate checks. Confirm that the visible wording, href and final landing page agree. Check repeated navigation, inserted content and template changes, because an approved spreadsheet row does not prove a working live link.
A crawlable link does not guarantee that a search engine will fetch, index or rank the destination. Robots rules, access limits, indexing decisions and destination quality remain separate questions. Likewise, a successful HTTP response alone does not prove that the page answers the linked question.
Keep a link decision that another editor can maintain.
Store the source passage, destination, relationship, anchor, placement, reviewer and next review event. Explain rejected opportunities: phrase-only overlap, wrong audience, duplicate route, unavailable target or unsupported timing. This preserves useful reasoning when another editor revisits the page.
After a destination moves or changes purpose, recheck the link’s sentence as well as its URL. A technically repaired redirect can still leave misleading anchor text. Remove a route when it no longer helps; link counts and exact phrase repetition are not substitutes for a coherent reader path.
Sources and related learning
Google link documentation. WCAG 2.2.
Teaching scenarios are labelled in the article. No search or client performance is claimed.
Continue with semantic SEO learning and internal linking. Write descriptive anchor text. Plan navigation and hierarchy.