Good link text names the place the link goes or the action it starts, and it still makes sense when read alone. "Read the volunteer handbook" works. "Click here" does not. If a reader pulled your links out of the page and lined them up, each one should still say something.

That is the whole idea. This page shows why it matters, gives you a few patterns to copy, and covers the awkward cases: long web addresses, lists, repeated links and file downloads.

Why "click here" fails

Assistive software can list every link on a page. WCAG's Understanding document for 2.4.4 says that meaningful link text helps people choose from that list. It also helps people who tab from link to link.

Picture the list for a page that uses weak links: "click here", "read more", "click here", "more". The reader cannot tell them apart. The sentences around each link are gone.

WCAG 2.4.4 (Link Purpose, In Context) asks that a reader can work out the purpose of each link. That can come from the link text alone, or from the link text together with its context. Context counts when it sits in the same sentence, paragraph, list item or table cell. The one exception is a link whose purpose is unclear to everyone.

The W3C's writing tips say it plainly: describe the content of the link target, and avoid ambiguous text such as "click here" or "read more".

Patterns that work

Weak link textBetter link textWhat changed
Click hereRead the volunteer handbookNames the destination
Read moreRead more about the autumn clean-upAdds the topic
https://example.org/forms/2026/signupOpen the sign-up formPlain words replace the address
DownloadDownload the meeting notes (PDF, 4 pages)Adds the file type and length
MoreRoom booking rulesSays what is behind the link

Each better version is short and tells the reader what to expect.

Before: For the full schedule, click here.

After: See the full volunteer schedule (PDF, 2 pages). The bold words are the link.

Before: Our rules are at https://example.org/community/guidelines/v2/final.

After: Read the community guidelines before you post.

What the sources recommend

  • Say where it goes. WCAG says that if a link leads to a document or an application, naming it is enough.
  • Match the page. WCAG adds that link text and the destination's page title agreeing, or being very similar, is good practice.
  • Show the file details. The W3C tips suggest adding the document type and size. Digital.gov goes further. For a download, it asks for the type, the size, the page count and the date inside the link text, so readers know what they are opening.
  • Do not overuse links. Digital.gov warns that too many cross-references can confuse readers and strain short-term memory.

Long addresses

A raw web address makes poor link text. It tells a reader nothing, and it is hard to read aloud. The W3C also notes it can break the layout. Technique C33 says long strings, such as URLs shown as content, can cause sideways scrolling when a page is zoomed. It states that a human-readable text link is better for usability and accessibility than a long address.

Browsers usually wrap an address at certain characters, such as the slash, hyphen, ampersand and question mark. C33 says that is sometimes not enough. For people who build the page, it suggests a CSS rule, overflow-wrap: break-word, on links.

If a reader must be able to copy a full address, say so, and put the address on its own line. The phone text guide explains why sideways drift is a problem on small screens.

Lists are where link text goes wrong fastest. Imagine ten items, each followed by "read more".

WCAG gives a neat example. A list of books is offered in three formats. To avoid hearing each title three times, the first link is the book's title, the second says "PDF" and the third says "mp3". The list item itself gives the context.

The same document says context works best when it comes before the link. If you must use a vague phrase, put it at the end of the sentence that describes the destination, not at the start.

Two more rules from WCAG:

  1. Links with the same destination should use the same text.
  2. Links with different destinations should use different text.

When a link wraps a picture and text together, the picture often adds nothing. The WCAG example gives the icon an empty alt value, because the text already says it. See writing alt text. If you are building a list of links, lists covers the layout.

Writing it yourself

Write the sentence first. Then pick the words that carry the meaning and make only those the link. Keep the link short, but complete enough to stand alone.

If you are tightening the sentence around it, the Easy-Read Editor can help you shorten and simplify it.

Link text also appears in PDFs. If you export one, the same rules apply. See making a PDF that reads well on screen.

Common mistakes

  • Using "here" or "this page" as the link. The words say nothing out of context.
  • Linking a whole sentence. The link becomes long and hard to scan.
  • Pasting the raw address. It is unreadable and may break the layout.
  • Giving two destinations the same text. Readers cannot tell them apart.
  • Hiding the file details. Readers do not know they are about to open a download.
  • Stacking many links in one paragraph. The text turns into a maze.

FAQ

Is "read more" ever acceptable?

WCAG allows it when the context in the same sentence, paragraph, list item or table cell makes the purpose clear. The W3C's writing tips still advise avoiding it. A longer phrase takes a few extra words and removes the doubt.

It helps. WCAG says that when the link and the title agree, or are very similar, readers feel continuity between the link they clicked and the page they land on.

Long enough to carry the whole meaning, and no longer. Digital.gov says link text should contain all the information the reader needs to decide whether to click.

Yes. Digital.gov says file information belongs in the link text, so readers know they are about to open a file, not a web page.

Sources

Each page below was opened and read on the date shown. Where a fact comes from one of them, the guide says so.

This guide gives general information about readability. See the Disclaimer. To report a mistake, use the Corrections page.