WordPress answer-engine eligibility is the same as ordinary search eligibility: a crawlable public URL, a useful visible answer, and structured data that does not invent facts. No special AI markup is required. This page describes eligibility. It does not guarantee citation, ranking, traffic, or placement in ChatGPT, Google or Bing.
Method
Treat each WordPress URL as a source document. Write the answer in HTML first. Add schema only for facts already visible. Then confirm the canonical URL, HTTP status and sitemap entry. Headless builds use the same rule: the CMS field is not public until the rendered page matches it. See headless WordPress release evidence and the AEO service page. Paid, agreed page work that follows the same eligibility rules is described on AI Citation Optimisation.
Eligibility checks
| Check | Pass | Fail |
|---|---|---|
| Public URL | The WordPress or headless URL is reachable without login. | Useful answers sit behind a form, paywall or admin cookie. |
| Visible answer | The page states the definition or method in ordinary HTML before any optional widget. | The only answer lives in an image, PDF or closed accordion with no text equivalent. |
| No special AI markup | The page uses ordinary HTML plus schema that repeats visible facts. | A hidden AI-only block, empty FAQ, or invented entity layer is added for crawlers. |
| Accurate JSON-LD | WebPage, Service or FAQ schema names match headings a person can see. | Schema lists questions, prices or URLs that are not on the page. |
| Canonical agreement | Canonical, sitemap loc and internal links use one public URL. | AMP, query and www variants advertise different answers. |
| Fresh sitemap | The sitemap lists the canonical URL and updates lastmod only from a real source date. | lastmod is fabricated or the URL is omitted after publish. |
| Measurement access | Reporting is planned only for tools the client can open. | A citation count is asserted without Search Console, Bing or identifiable referral access. |
Measurement
Measurement uses Google Search Console (including any generative-AI reporting the property actually exposes), Bing Webmaster tools including AI Performance where that report is available, and identifiable referrals such as chatgpt.com only when the client grants access to those properties. Citation counts, clicks and leads are separate signals. Do not infer one from the others.
Limits
A clean WordPress page can still be unused by an answer engine. Schema does not create an enhanced result. Blocking a bot, serving different HTML to users and crawlers, or publishing an empty page will fail eligibility even if a plugin claims “AI SEO.” Practical ChatGPT discovery notes are on Show up in ChatGPT.
Common questions
- How do we measure AI citation or AEO work?
- Measurement uses Google Search Console, Bing Webmaster Tools, and chatgpt.com referral data only when the client provides access to those properties, plus crawl, index, canonical and sitemap evidence. We never promise a citation, ranking or traffic outcome.
- Do we need special AI markup or a WordPress plugin?
- No special AI markup is required. A WordPress plugin or schema output is useful only when it matches public visible facts and does not duplicate or invent data.
- What should a public source page contain?
- A public source page should contain a visible useful answer, truthful claims with supporting evidence, and one canonical public URL. Structured data belongs only when it matches those visible facts.
Sources
Record
Author and reviewer: The Dot Dev. First published 23 August 2026. Review when the cited publisher guidance changes.
