An answer engine optimization plan for a WordPress site
An AEO plan for a WordPress site has four phases: choose the questions you want to be the source for, make sure the crawlers behind each answer engine can reach the pages that answer them, rewrite those pages so each answer stands on its own, and check the results every month. A small site can get through the first three phases in a few weeks of part-time work. The fourth never ends.
The plan below assumes you already have the basics of SEO in place. If you want the background on why answers differ from rankings, read what answer engine optimization is first. This page is the working plan: what to do, in what order, and which WordPress settings are involved.
Phase 1: build the question inventory
Start from questions people really ask, not from keywords. Pull them from four places:
- Search Console. In the Performance report, add a query filter with a custom regex to surface question phrasing, then sort by impressions.
- Your own site search. If analytics records the WordPress
?s=parameter, those searches are questions your pages failed to answer at first glance. - Support and sales. The inbox and call notes hold the questions buyers ask right before they decide.
- People Also Ask boxes for your main topics, which show how Google groups the follow-ups.
^(how|what|why|when|which|who|can|does|do|is|are|should)\b
Score each question on three things: how much a good answer is worth to your business, whether AI answers already appear for it, and whether you hold first-hand knowledge nobody else has. Keep the top 20 to 30 and assign each one to a single page on your site. Where no page fits, note a gap rather than forcing it into an unrelated post.
Phase 2: clear the path for answer engine crawlers
On WordPress, three things commonly stop AI search agents before they read a word.
robots.txt rules. Copied "block all AI" lists often catch search agents along with training crawlers. Check for groups naming OAI-SearchBot, PerplexityBot, Claude-SearchBot or Bingbot. You can keep training crawlers such as GPTBot out while letting search agents in. Hydrogen SEO's robots.txt editor edits the file from wp-admin; open the live /robots.txt after saving and read it line by line.
Security layers. Bot protection in a CDN or a security plugin can serve a challenge page to anything that is not a browser. Look at the firewall log for blocked requests from the agents above and add allow rules that check their published IP ranges.
Content that only appears after JavaScript runs. Page builder tabs loaded over AJAX, "load more" review widgets and pricing tables drawn by scripts may never reach a crawler that reads raw HTML. View the page source, not the rendered page, and search for your key answer. If it is missing, move it into the initial HTML.
Phase 3: rewrite pages as answer blocks
Each assigned question gets its own section on its page, built the same way every time:
- A heading that states the question in the reader's words.
- A first paragraph that answers it completely in two or three sentences, including the condition that changes the answer ("for a single-story home", "on the free plan").
- The evidence: numbers, steps, a table, a photo you took.
- Detail and edge cases after that.
In the block editor, save the heading-plus-answer layout as a synced pattern so writers reuse it instead of improvising. Use real List and Table blocks, not line breaks or screenshots of tables.
Then make the page's identity explicit. Give each author a profile page with a short bio, keep an About page that names the business and its people, and add schema that matches what the page shows. In Hydrogen SEO, the SEO Settings sheet (⌘E or Ctrl+E) sets the schema type per post: Article for most posts, FAQ where the page answers several distinct questions, HowTo for procedures. Check the output with the JSON-LD validator. Schema will not win a citation by itself, but it removes doubt about who wrote the page and what it is.
Phase 4: test, log and refresh
Once a month, run your question list through ChatGPT, Perplexity, Gemini, Copilot and Google's AI Mode, and log whether your site is cited, who is cited instead, and whether what the answer says about you is correct. Keep the prompts fixed so month-to-month changes mean something. The method, and the analytics setup that goes with it, is on the AI visibility measurement page.
Every quarter, reopen the pages where a competitor keeps getting cited instead of you. Read the cited page and note what it states that yours does not: a price range, a date, a named method, a comparison. Add the missing facts if you can back them up, and update the page's visible "last reviewed" note only when something really changed.
What this plan cannot do for you
The plan makes your site eligible and easy to quote. It does not decide selection. Engines weigh sources they already trust, and a new site with perfect structure can still lose to an established one. Third-party pages about you, such as reviews, directories and forum threads, are often cited instead of your own. And every engine changes its behavior without notice. Judge the plan on a trend over two or three quarters, and see what is documented about AI search factors before adding any tactic that promises more.
Common questions
How many pages should an AEO plan start with?
Ten to fifteen pages is a manageable first cycle for a small team. Pick the pages that answer your highest-value questions, finish them properly, and measure before widening the scope.
Do I need FAQ schema on every page?
No. Use FAQ schema only where the page visibly answers several separate questions. Most posts are better described as Article, and procedures as HowTo.
Should I write separate pages just for AI engines?
No. AI answer engines retrieve the same pages people read. Writing duplicate thin pages for machines tends to hurt the site and gives the engines nothing new to cite.
Does WordPress need a special AEO plugin?
Not a separate one. You need schema output, control over robots.txt, fast server-rendered pages and optionally an llms.txt file, which a capable SEO plugin already covers.