Writing a page that ranks

You've picked the keyword, opened a blank document, and the first instinct is to write an introduction. Three paragraphs later you're explaining why the topic matters, and the person who typed that keyword has already hit the back button. The pages that rank almost never begin like that.

A page that ranks is built from the search backwards: the one question it answers, the order a searcher needs the answers in, and the discipline to leave out everything else. Get the structure right and the words become the easy part.

Decide the one question the page answers

Every search is a question, even when it's typed as two words. "Trail shoes wet rock" means "which shoes grip on wet rock, and which should I buy". Before you write a heading, write that question out in full and keep it at the top of the document. Every section either helps answer it or doesn't belong.

Then check what Google already shows for it, because the results tell you which kind of page can rank: if the first page is full of buying guides, a product page won't get in. Search intent covers how to read this.

One page, one primary question. A page that tries to answer "what are trail shoes", "which are best" and "how do I clean them" competes with itself and with three better pages. Give each its own page and link them, which is the whole idea behind topic clusters.

Put the answer first, then earn the depth

Open with the answer. Not the context, not the history of the subject, the answer: the shoe, the price range, the rule of thumb, the yes or no. A searcher who sees their answer in the first screen stays to read the reasoning; a searcher who has to hunt for it leaves. Whether Google measures that directly is contested, but a page that loses its readers in the first screen has failed the search either way.

This ordering also decides how your page gets quoted. Featured snippets, AI Overviews and assistants like ChatGPT lift a passage, not a page, and they favour passages that stand on their own: a heading that states the question, followed by a short paragraph that answers it completely. Write every section so it could be read in isolation and still be correct. The AI search chapter goes deeper on why.

After the direct answer comes the depth: the why, the trade-offs, the exceptions, the examples. This is where you show you know the subject, and it comes second because nobody reads your reasoning before they know you have an answer.

Build the skeleton before the sentences

Google reads a page's structure before its prose. The title tag, the main heading and the subheadings tell it what the page is about and which sub-questions it covers, and a clean skeleton is the cheapest ranking work you'll do.

1. Write the title tag and the H1 so both say, in a searcher's words, what the page answers. A reader should never feel they landed somewhere other than where the result promised.
2. List the sub-questions a searcher has on the way to the main answer. Google's "People also ask" boxes for your keyword are a direct readout of these.
3. Turn the sub-questions into ## headings, in the order a searcher would ask them.
4. Under each heading, write the answer first and the explanation second, the same pattern as the page as a whole.
5. Add links to the pages on your site that answer the neighbouring questions, and at least one link out to a source you relied on.

The primary keyword belongs in the title, the H1 and the first paragraph, in natural language. After that, write like a person. Google's own guidance on creating helpful content says it has no preferred word count, and it judges a page on whether it satisfies the searcher, not on how many times a phrase appears.

Leave out what the searcher didn't ask for

The most common way a good writer produces a page that doesn't rank is by including too much. An introduction that explains why the topic matters. A section on the history of the thing. A paragraph that restates the keyword four ways. A closing summary that repeats what the page already said. Each one pushes the answer further down and dilutes what the page is about.

Google's helpful content guidance comes down to one question you can ask of every paragraph: was this written to help the person who searched, or to look like a page that should rank? Sections added to hit a length, to chase an unrelated keyword, or to copy what a competitor covered without knowing why, fail that test. Google's spam policies also name "scaled content abuse" for pages produced in bulk to fill search results, so volume without purpose is a risk rather than a strategy.

A useful edit pass: read every section and ask whether deleting it would make the page worse for the searcher. If not, delete it. Shorter pages that answer completely beat longer pages that answer eventually.

What to take away

• A page ranks for one question, and that question, written out in full, decides everything else on the page.
• The answer goes first and the reasoning second, both for the page as a whole and inside every section.
• Headings are the skeleton Google reads: the title, the H1 and the sub-questions in the order a searcher would ask them.
• Anything the searcher didn't ask for costs you, so cut introductions, padding and repeated keywords before you publish.

Next

One page answers one question; a set of pages can own the whole subject. Continue with Topic clusters: own a subject, not a keyword.