Write for the answer, not the click

2 min

The BetterCMS team Marketing

Summarize with AI

TL;DR, key takeaways

  • Answer engines quote pages that state things plainly.
  • Lead with the answer and make each heading the question a person asks.
  • Avoid pronouns across sentences so a quoted line still makes sense alone.
  • Mark up only what the page shows, and serve a version machines can read.

A growing share of the people who need your documentation never see it. They ask an assistant, the assistant reads the page, and the answer arrives without the page around it. Whether that counts as a lost visit or a served customer depends on whether the answer was right.

Making it right is mostly editing, and it is the same editing that makes a page better for a person in a hurry.

What is answer engine optimisation?

Answer engine optimisation is the practice of structuring a page so that a language model can extract a correct, quotable answer from it. It overlaps with search optimisation and differs in one way that matters: the target is not a ranking, it is a sentence the model can lift without changing its meaning.

Lead with the answer

Put the answer in the first sentence under the heading. Not the context, not the history of the problem, the answer. A model summarising the section will take the top of it, and a reader skimming will do the same thing.

This is the single highest value edit available on most pages, and it is free.

Make headings the question

A heading that reads "Pricing" tells a model that a topic is nearby. A heading that reads "How much does BetterCMS cost?" tells it that an answer to that exact question is directly below. Write the heading as the sentence somebody would type.

  • One question per heading. A heading covering three questions answers none of them cleanly.
  • Name the subject in the heading rather than relying on the page title for context.
  • Keep the answer in the same section as its heading.

Do not lean on pronouns

An extracted paragraph arrives without the paragraph before it. "It supports that out of the box" is meaningless on its own. Repeat the noun even when it feels repetitive, because the sentence that gets quoted is the one that has to stand up alone.

Write every paragraph as if it will be read without the one above it.

Mark up what the page actually shows

Structured data helps when it describes the page honestly. An article marked as an article, a set of questions marked as an FAQ, a definition marked as a defined term. Marking up content the page does not display is a policy violation and a good way to lose the benefit entirely.

Serve a version machines can read

HTML carries navigation, cookie banners and analytics around a few hundred words of content. A plain markdown version of the same page is smaller, unambiguous and cheaper for a crawler to parse.

Publishing markdown alongside HTML costs nothing when the content is structured, because both are rendered from the same fields.

JSON

GET /content/faq/what-is-a-headless-cms

{
  "_type": "faqAnswer",
  "question": "What is a headless CMS?",
  "answer": "A headless CMS stores content as structured data and serves it over an API, with no opinion about how it is displayed.",
  "updatedAt": "2026-10-14",
  "topic": { "_ref": "architecture", "label": "Architecture" },
  "sources": ["/glossary/headless-cms", "/glossary/api-first"]
}

More articles

View all

Your next website starts here

See BetterCMS running on your pages, not on a sample site.