What is an answer-shaped page?

An answer-shaped page uses the customer's question as the H1, answers it in the first screen, then adds who it is for, steps or a comparison, sources, and four FAQs. It is usually 600 to 900 words. This page is written in that shape, so you can read the method and the specimen at the same time.

Who this is for

• — Anyone writing pages they want an AI engine to quote.
• — Owners who want a template their staff can follow without a copywriter.
• — Editors auditing an existing library of blog posts.

Who this is not for

• — Narrative essays, brand manifestos, and launch announcements. Those have a different job.
• — Pages whose real purpose is to hold ads.

The skeleton

1. H1 = the question, in the customer's words.
2. Direct answer, first 80 words, no preamble, with the number or condition stated plainly.
3. For / not for — two short lists that tell a reader and a model when this answer applies.
4. Steps or comparison — an ordered list if it is a process, a table if it is a choice.
5. Cost or time — only if you have a real range you will stand behind.
6. Sources — primary documentation, named in the text.
7. FAQ — four questions, each answered in one to three sentences, matched by FAQPage JSON-LD.
8. Author and updated date, visible on the page.

How long each part should be

Common mistakes

• — Opening with context. "As the internet evolves…" pushes the answer below the fold and out of the quote window.
• — Hedging the number. "It depends" with no range is not an answer; give the range and the conditions.
• — Twelve FAQs of padding. Four real ones outperform twelve invented ones.
• — Schema that does not match the visible text. That is a correctness problem, not a clever trick.
• — No date. An undated page reads as unmaintained to both people and engines.

How we use it

Every page we publish for a client follows this skeleton. The variation is in the middle: a contractor page gets steps, a comparison page gets a table, a pricing page gets a range and the conditions attached to it. The first screen and the last screen are always the same shape, which is what makes a set of pages feel like a library rather than a pile of posts.

Sources

Structured-data requirements come from Google's structured data documentation. Everything else here is our editorial standard, stated as ours.

A quick self-check

Before publishing, read only the first eighty words and ask three questions. Does that text answer the H1 on its own, with no surrounding context? Does it contain a number, a range, or a clear condition? Would you be comfortable if an engine quoted it word for word next to your business name? If any answer is no, rewrite the opening before touching anything else. Then check the last screen: author, date, four FAQs, and matching schema. Those two screens carry almost all of the weight. The middle of the page is for the reader who wants detail, and it is where you can safely be longer.