When "Learn More" Is the Wrong Button

Buttons are the most honest part of a website. The rest of the page can gesture and imply, but a button makes a claim: click me and a specific thing will happen. Which is why “Learn More” is such a strange label. It’s a button that refuses to say what it does.

I audit a lot of websites, and “Learn More” shows up on most of them, often several times on one page. When I trace where those buttons actually go, the destinations are wildly different. One goes to a features page. One opens a demo video. One starts a signup flow, which is a genuinely rude thing to hide behind “Learn More.” The label is the same because the writer, at the moment of writing, didn’t want to commit to what the click delivers. “Learn More” is not a decision. It’s a deferral.

The visitor pays for that deferral. A first-time visitor is doing a cost-benefit calculation on every click: what will I get, and is it worth the interruption? A specific label — “See pricing,” “Watch a 2-minute demo,” “Read the API docs” — lets them do the calculation instantly. “Learn More” forces them to click to find out what clicking gets them, which is the calculation running backwards. Some will click anyway. Many will not, and the ones who don’t aren’t lazy. They’ve been burned before by vague buttons that led somewhere they didn’t want to go.

There’s a second cost that most people never see, because it falls on people using screen readers. A common way to navigate a page with a screen reader is to pull up a list of all the links, out of context. Do that on a typical marketing page and you hear: Learn More. Learn More. Learn More. Learn More. Four identical links going four different places, and no way to tell them apart without backtracking into the surrounding text. This is exactly why the accessibility guidelines ask that a link’s purpose be discernible from its text. The fix for blind visitors and the fix for distracted sighted visitors turns out to be the same fix, which should tell you something. Vagueness isn’t a style problem with an accessibility side effect. It’s one problem, visible from two angles.

Here’s the diagnostic I use, and it’s simple enough to run in your head. Cover everything on the page except the button. Read the label alone. Can you say what happens next? “Start free scan” passes. “Download the checklist” passes. “Get started” half-passes; at least it admits a process begins. “Learn More” fails completely. So does “Discover,” “Explore,” and my least favorite, “See what’s possible,” which manages to be both vague about the destination and vague about the subject.

The usual defense is that specific labels are long and ugly, and there’s some truth to that. “Learn More” is short, symmetrical, and fits nicely in a card layout. But notice what’s happening: the design system is dictating the copy. The cards were designed first, each needed a button, the buttons needed to be the same width, and “Learn More” fits everywhere precisely because it means nothing anywhere. The label isn’t serving the visitor. It’s serving the grid. When I find a page with six identical “Learn More” buttons, I usually find a designer who made a beautiful template and a writer who filled in the blanks under constraint. Neither of them ever asked what the visitor needed to know before clicking.

When my scanner at GazeSite flags this, the interesting cases aren’t the pages with too many “Learn More” buttons. They’re the pages where “Learn More” is arguably right — and there are some. If the surrounding card already says exactly what the topic is, and the destination really is just a longer explanation of that topic, then “Learn more about pricing” collapses reasonably to “Learn More” sitting under a heading that says “Pricing.” Context can carry the meaning. But this only works when the context is doing the work the label isn’t, and it stops working the moment the links are read out of context, which screen readers do routinely. The safe version costs you two words: put the topic in the label, or at minimum in an aria-label, so the link makes sense standing alone.

The deeper issue is what a vague button reveals about the funnel behind it. A site with sharp buttons has a theory of its visitor: first they’ll want to see the product, then the price, then they’ll try it. Each button is a step in that theory. A site papered with “Learn More” has no theory. It’s saying: here is some stuff, wander around, maybe something will happen. Sometimes something does. But you can’t improve wandering. You can only improve a path, and a path is made of buttons that say where they go.

So go look at your site and read only the buttons, top to bottom, ignoring everything else. That sequence of labels is the story you’re telling a visitor about what to do. If the story reads “Learn More, Learn More, Learn More, Contact Us,” you haven’t written a page yet. You’ve written a lobby.