Inline links need surrounding context, not just anchor text
The anchor text isn't doing the work you think it is
Most guidance on inline links focuses exclusively on the anchor text itself—make it descriptive, avoid "click here," front-load keywords. All true, but insufficient. The real job of an inline link is collaborative: the anchor text and the surrounding sentence have to work as a unit. If you write "Learn more about our pricing plans" you've technically met the descriptive-anchor-text requirement, but you've also written a sentence that does nothing except point elsewhere. The link becomes a crutch for weak prose.
Anchor text inherits its meaning from context. "See the documentation" tells a reader nothing about why they'd want to see it or what they'll find there. "The API rate limit resets every hour—see the documentation for caching strategies" gives the link a reason to exist. The sentence establishes a problem (rate limits) and the link promises a solution (caching strategies). You can evaluate whether to click without re-reading the paragraph.
Write the sentence, then choose what to underline
If you're starting with the decision to insert a link, you're working backwards. Start with what the reader needs to know in this sentence, on this page. Then decide whether a link adds value or just fragments attention. Most inline links exist because the writer didn't want to finish explaining something. That's fine—links are for escaping the constraints of linear text—but the escape route needs a sign.
The sentence "Our new editor supports Markdown" assumes the reader already knows what Markdown is and why they'd care. "Our new editor supports Markdown so you can write formatted text without lifting your hands from the keyboard" gives non-experts a reason to click and experts a reason to skip. The context teaches; the link offers depth.
Test the sentence with the link removed
If removing the link turns the sentence into gibberish, you've written a sentence that only exists to hold a link. "Check out our latest blog post" has no meaning without the link. "We've added bulk image upload—read the setup guide if you're managing more than fifty files" still tells you what changed and who should care. The link becomes optional, which paradoxically makes it more useful.
This is particularly important for accessibility. Screen reader users navigating by links hear the anchor text out of context. "Latest blog post" in a list of links is meaningless. "Setup guide" is better, but "bulk image upload setup guide" is a complete thought. You can build that meaning into the anchor text itself (verbose but functional) or into the sentence structure (usually cleaner). Either way, the surrounding sentence has to do some of the work.
Match link density to page purpose
A blog post can afford to be stingy with links—you're asking readers to stay and finish the piece. A documentation page needs more links because users are hunting for a specific answer. A landing page should link exactly once per section, because every additional link is a decision point that delays conversion. The context around each link has to justify the interruption.
If you're linking to related content, write a transition that explains the relationship. "This builds on our earlier post about heading hierarchy" is weaker than "Heading hierarchy establishes the structure—then subheadings fill it with meaning." The first link is a footnote; the second is an argument.
Front-load the destination, not just the keywords
SEO advice will tell you to put keywords at the start of the anchor text. Fine, but more important: tell readers where the link goes before they hover. "Read more in the API reference documentation" buries the destination. "The API reference includes rate limit details and error codes" tells you what you're clicking toward. If the reader already knows they need the API reference, they've clicked before finishing the sentence. If they're not sure, the surrounding context helps them decide.
This isn't about longer anchor text; it's about purposeful sentence structure. You're writing for the person who's skimming, the person who's using a screen reader, and the person who's deciding whether to interrupt their current task. The anchor text gets the underline, but the sentence does the persuading.