Anchors and surrounding context
Let the anchor tell readers what comes next.
Anchor text should describe the destination honestly within the current sentence. Readers should be able to predict why following the link will help, without decoding a repeated keyword or vague instruction.
Start with the destination job before choosing words.
Read the real target and name what it provides: a definition, comparison, procedure, source record or next stage. Then identify what the source reader needs at that point. An anchor promising a comparison should not land on a general definition or a purchase form.
Use the source sentence, reader state, target purpose and verified URL as the input record. A shared noun can suggest a relationship but cannot establish a useful route by itself. If the destination is unverified, hold the wording rather than attach a confident label to a guessed page.
Use descriptive wording without stuffing the sentence.
Choose a short natural phrase that identifies the subject or task. The exact page title is not mandatory, and a direct subject phrase is not inherently wrong. Add the distinction needed to separate this target from nearby pages. Avoid repeating every keyword or location variant in one anchor.
Google’s link guidance favors descriptive, reasonably concise wording relevant to both source and target. It also emphasizes surrounding context. Treat that as a reader aid, not a formula for an exact-match ratio. Forced substitutions can make a sentence harder to understand without changing its destination meaning.
Find the ambiguity that repeated wording creates.
Identical visible phrases can be appropriate when they consistently refer to the same purpose. They become confusing when the same “explanation” label sends readers to three different jobs. Different natural anchors can describe the same destination without being a problem if they preserve its meaning.
Ask what readers can predict from the link alone and then from the surrounding sentence. WCAG Level A allows link purpose to be understood through programmatically determined context; the stricter link-only criterion is different. Clear standalone phrasing often improves a link list, but do not claim that every generic word automatically violates the Level A requirement.
Worked example: repair three identical anchors.
An imaginary editorial checklist contains three links labelled “SEO resource”. They lead to existing Semantec learning pages with different subjects. The repair keeps each real destination and changes the sentence to explain its distinct use. The before text below is a teaching record, not three live ambiguous links.
| Before anchor | real destination subject | Repaired wording and sentence purpose |
|---|---|---|
| SEO resource | Search intent layers | Identify the reader task with the search intent layers explanation before outlining. |
| SEO resource | Entity disambiguation | Resolve ambiguous names using the entity disambiguation explanation. |
| SEO resource | Content brief requirements | Specify the assignment using the content brief requirements before drafting. |
Read the complete repaired sentences with their real links.
Before outlining, identify the reader task with the search intent layers explanation. When names could refer to different subjects, use the entity disambiguation explanation. Before handing the work to a writer, specify required answers and evidence with the content brief requirements.
Each repaired phrase names a different job without promising a result the destination cannot supply. The source checklist can retain all three when the reader needs those separate tasks; it should not repeat a route just to increase link counts.
Use the surrounding sentence to supply the reason for the click.
Explain the condition or next question before presenting the route. “If the name has more than one plausible referent” tells readers why disambiguation matters. The linked phrase identifies the destination; the sentence supplies timing and relevance. Do not bury the purpose in a remote paragraph that assistive technology cannot associate with the link.
Avoid a chain of adjacent links with no connective explanation. Do not link the same phrase repeatedly within a short passage unless each placement serves a distinct need. If the context already supplies enough information and no next task exists, plain text may be the best choice.
Keep natural alternatives inside the same meaning.
For a single destination about disambiguation, “resolve ambiguous entity names” and “entity disambiguation explanation” can be honest alternatives in different sentences. “Get verified business data” would promise a different service and should be rejected unless that is what the page supplies. Variation is a consequence of context, not a requirement to manufacture synonyms.
Record the approved phrase, acceptable alternatives, source placement and rejected misleading terms when different editors reuse a destination. Labels in menus may need greater consistency than one contextual sentence. Keep a stable subject while adapting the wording to the reader’s learning, diagnosis or comparison task.
Review the visible phrase, code and landing page together.
Confirm a real anchor with href, a meaningful accessible name and a working intended destination. Check the full sentence aloud, then read only the anchors to expose ambiguity. Review keyboard focus and visual identification in the rendered page separately; copy approval alone cannot prove those behaviors.
When a target changes its purpose, revisit the anchor and its context rather than only replacing the URL. Keep the link decision, source evidence, owner and next review trigger. There is no universal anchor count or variation quota that makes a misleading destination honest.
Sources and related learning
Google link documentation. WCAG 2.2.
Teaching scenarios are labelled in the article. The dated Google feature change is a real documented event; no search or client performance is claimed.
Continue with semantic SEO learning and internal linking. Make links crawlable and meaningful. Keep navigation labels coherent.