Content
How to write an answer-first page
Put a question-shaped heading at the top, answer it completely in 40 to 60 words directly beneath, then add the depth. The answer must make sense lifted out of the page entirely, because that is exactly what an answer engine does with it.
Before you start
- A specific question worth answering
- Something genuine to say about it
The steps
-
Step 1: Write the question as the heading
Phrased the way someone would actually type or say it.
-
Step 2: Answer it immediately
40 to 60 words, directly beneath, with no preamble or throat-clearing.
-
Step 3: Make the answer self-contained
No "as mentioned above", no pronouns pointing backwards, units and currency inside the sentence.
-
Step 4: Add specifics
Numbers, dates, prices, versions. "Fast turnaround" is unquotable; "seven days from signed scope" is a fact with a shape.
-
Step 5: Then add the depth
Qualification, evidence and nuance for the reader who stayed.
-
Step 6: Use extractable formats
Tables, ordered lists and definition lists survive extraction with meaning intact; prose often does not.
-
Step 7: Mark it up
QAPage or FAQPage, with the markup text identical to the visible text.
The failure mode this avoids
Burying the answer under context. "Before we discuss pricing, it is important to understand that every project is different" answers nothing, and an extractor takes it at face value: this page does not contain the answer.
It is better for humans too
Answer-first is how reference documentation and good journalism have always worked, because most readers want the answer and only some want the reasoning. Optimising for extraction and optimising for impatient readers produce the same page.
The background behind this
Answer Engine Optimization: writing the passage that gets quoted covers the reasoning in about 3 minutes — free, ungated, written from client work.
Who wrote this
Anas Bin Masud builds e-commerce sites and does technical SEO for businesses in the UK, Canada, Ireland and Pakistan. These procedures are the ones I run on client work, written down rather than invented — including the ones where the honest answer is that the fix is not available on your current hosting.