How to Publish an Answer-Ready Page on Your CMS
Publishing an AEO page yourself: one H1, real heading styles, clean pastes, the WordPress and hosted-builder paths, and verifying the live page's structure.
What makes a page answer-ready
Four things, in order of how often they lose a citation. The direct answer to the question appears in the first two sentences, not after the introduction. The page has exactly one H1, and the subheadings below it are real headings rather than bold paragraphs. The facts are the same ones on your schema and your directory listings. And the page has a named author. A page missing any one of these can still rank in Google; it is much less likely to be quoted by an answer engine, because a model choosing what to quote is looking for a passage that answers a question cleanly and can be attributed.
Before you start
Have the drafted copy, the target question it is answering, and your verified business facts — service area, phone, services, credentials — in front of you together. Almost every rejected piece comes from writing the copy first and inventing or half-remembering a fact while typing it. If the draft was written for you, the facts in it came from your onboarding record; do not edit them from memory without checking, because the whole value depends on every page agreeing with every other.
The one rule about formatting
Use the editor's heading styles rather than making text bigger and bolder. Your CMS writes a heading tag when you choose Heading 2; when you instead select a normal paragraph and make it bold and larger, it looks identical on screen and produces no heading at all, so the page has no structure a machine can read. This is the single most common problem in content we audit, and it is invisible unless you view the page source. If you take one thing from this guide, take this one.
On WordPress
Pages → Add New. Put the heading in the title field. Write the opening answer as the first normal paragraph. For each subheading choose Heading 2 from the block toolbar rather than styling a paragraph. Use the Paragraph block for body text and the List block for lists. Paste the copy as plain text first if it came from a document: pasting directly carries fonts and colours across from the source and produces markup that fights your theme. Drafts often arrive with the FAQ answers as a list — keep them as a list, and add the questions as Heading 3 so each question is a heading a model can match against.
On Squarespace, Wix, and other hosted builders
The mechanism is the same and the trap is the same: select the built-in heading style for headings rather than setting font size and weight manually. Hosted builders make manual styling very easy and it is the usual cause of a page with no readable structure. Where possible use a text block rather than separate blocks for each line, so the copy stays as continuous prose instead of the builder splitting every sentence into its own element. Check the result by viewing the published page's source, not by looking at the editor — the editor shows you what it looks like, not what it produces.
If your site has a developer
Send them the copy with the structure marked: which line is the H1, which are H2, which are H3, and where the FAQ sits. Ask them to confirm four things when it is live: one H1 on the page; subheadings marked up as heading elements; the page publicly reachable without sign-in; and FAQ structured data validating in Google's Rich Results Test if the draft includes a FAQ section. Also ask them to add the page to your internal links from a relevant service page, using descriptive anchor text rather than "click here" — an orphaned page is much weaker, and this is the step most often forgotten.
Publish, then verify — not the other way round
Draft previews are usually blocked from crawlers by design, so a piece only starts counting once it is published and public. After publishing, open the live URL in a private window and confirm it loads for someone who is not logged in. Then view the page source and search for "<h1" and "<h2": you should find exactly one H1 and your subheadings as H2. This takes about thirty seconds and catches the formatting fault that would otherwise waste the whole piece.
What to send back
Record the live URL on the task card, because that URL is what your monthly report measures and what gets listed in your llms.txt. If the draft included a FAQ section, note whether the structured data validated. If something had to change — a service name, a price, a claim you were not comfortable making — say so on the card rather than leaving the published page to differ from the record, so the next piece is written against the corrected version of your business rather than the old one.
A note on publishing rhythm
A handful of pages that each answer a real customer question well outperforms a large volume of general articles. Answer engines quote specific, verifiable passages; posting weekly for its own sake produces pages that compete with each other for the same question. If you are publishing yourself, it is better to publish the two or three pieces that matter in a month and let them mature than to publish twelve that each answer nothing in particular.
Did this guide answer your question?
See how visible your business is to AI
Get your free 0–100 AEO score across ChatGPT, Perplexity, Gemini, Claude, and Google AI Overviews.