Why a page that ranks still doesn't get picked

The short answer

Because ranking only gets the page seen. The pick happens after that, in a few seconds, between answers that all look fine. People pick the answer they can check (who made it, how they know, when it was last true), the one that gives them a reason to act on their own situation, and the one that puts the next step right where their question ends. AI answers make a pick too, when they choose which pages to cite.

When a page shows up in search but gets few clicks, I check what it offers someone deciding which answer to open. If you're still reading the gap itself, the chart that shows up but doesn't get clicked, start with why impressions rise while clicks stay flat. This post is about the step after that, the third outcome in my system: get chosen. It comes after get understood, which is about making the page make sense to people and to the systems reading it for them.

Why doesn't found and understood mean chosen?

Found means the page shows up. Understood means the reader can tell what it says. Chosen is a separate decision: the person looks at a few answers that all seem fine and picks one, usually in seconds and usually without reading any of them closely.

So the question changes. It stops being "can they find it?" and becomes "what can they check, and what can they do, before they leave?" The get chosen page shows the evidence from my own sites; this post is the working checklist behind it, and why content that ranks still fails to move people covers the same gap one stage of a decision at a time.

What does E-E-A-T ask for on the page?

E-E-A-T is experience, expertise, authoritativeness and trustworthiness. Google explains it in its guide to helpful, reliable, people-first content (last updated October 5, 2026), and two lines from it get skipped a lot: “Of these aspects, trust is most important.” And: “E-E-A-T itself isn't a specific ranking factor”.

So there's no score to raise. The same guide asks three questions instead, who made the content, how and why, and each has an answer a reader can see.

Google asks What I put on the page
Who created it? My name, and a byline that leads to who I am and what I've built. Google warns against invented authors and AI-made headshots.
How was it created? The method and the count: how many, from which report, through what date. Google's own example is a product review that says how many products were tested and how. When AI did part of the work, say how. On my About page I say I write the specs and the checks, use AI to write the code to them, and check every change before it ships.
Why does it exist? To help the person who searched. Google says content made mainly to attract search visits isn't what its systems seek to reward.
Is it still true? A last-checked date, “not announced” where nothing is, and a correction that says what changed. This row is mine, not Google's.

I added the last row because I broke it once, on my fan reference. Plausible and accurate are not the same thing, and on reference sites, the gap between the two has real consequences if not done right.

At my full-time job, how much weight trust carries depends on the industry. For a professional or regulated service, trust decides it: plain-language explanations, named credentials and a review step for every claim, because a wrong fact there costs more than a lost click. How I work at my full-time job has the rest of that list.

Why do people act on one answer and not another?

This is the psychology of action, part of the pillar of my system I call start from the person. Three moves I use when reviewing the next step:

  • The why before the what. The reader gets a reason before they get the details.
  • A personal reason to act. The page talks about their situation: their city, their wire, their game.
  • A smaller ask. One tap beats a form, and a number they already know beats a table they have to read.

When I built UpOrbit, a task list, the brief was my own: I needed something simpler: one thing per day, a reason attached to it, and a system that does not punish me for losing momentum. A reason attached to it is the why before the what.

Testing the smaller ask

The smaller ask is the one I test most, because it's the easiest to get wrong without noticing. The test I keep coming back to is plain: can someone who already has the number they need reach the answer without reading anything else? On WireRef that question came from watching where visitors clicked first on its heatmap, which the WireRef case shows, along with what the wrong ask cost on a phone.

Where should the next step go?

Beside the decision, after the reader has made it. One next step, with no popup, countdown or form between the reader and the answer. “This page helps someone who searched [X] decide [Y].” If you can’t finish that sentence, the page needs work. The next step is whatever comes after Y, and the answer that earns it can be "you don't need anything", which is what my water-quality site tells most Seattle readers.

This site runs the same rule as a check. Every page gets a written entry before it's built: who lands there, the question they bring and one next step. The build fails when a page ships with no next step, with two, or with one that goes somewhere the entry doesn't say. Psychology: building for the person searching shows one entry in full.

Two older posts cover each end of a decision. On a page with no answer to give yet, the next step did the job, and the tap data is in why informational content stalls. On a buying page, the next step should feel like a confirmation, which is the argument in why transactional pages fail ready buyers.

Can you measure mentions and citations?

Citations, partly. Mentions, not yet on my sites.

An AI answer makes a pick when it chooses which pages to cite, and Bing's AI Performance report shows a sample of the searches its AI ran before citing a page. What that sample says about my sites is in search intent when AI does the searching, and how AI decides which brands to name is in the recommendation layer. The short version for this post: the pages that get cited are the ones that are easiest to check.

Mentions

Mentions are people and publications talking about you, with a link or without one. I don't have mentions data for my own sites yet, so there's no number in this section, and I won't put one here until I do. What I can share is the method from my full-time job: a page earns a mention when it has something worth repeating, usually original data or a clear story, and the page PR points people to has to be ready to be checked when they arrive.

When I have mentions data for my sites, this section gets a dated number, good or bad.

Written for this site and first published October 30, 2026. Every number in it comes from my own exports and is dated where it appears.

Use arrow keys to move. Enter opens. Esc closes.

Ask Bella

Ask Bella Hayden's corgi, who answers from this site and cites every fact.

BELLA

WOOF. I'm Bella, Hayden's corgi. He's my human. Ask me about him; every answer cites its source.

Reading this page? The top button is my short version of it.

How it works: the answers are written ahead from this site's pages, and anything else gets a search of the site that shows you its exact words. Every claim has a numbered source you can tap. Nothing is generated while you wait, nothing is made up, and nothing you type leaves your browser. Every answer, in plain HTML

Top

This page was last updated