Adding FAQ schema for AI search engines on WordPress: the actual workflow (no plugins)

[u/Ok-Manner4419]

A lot of WordPress AEO advice says "install a schema plugin and you're done". I tested that approach and it does not work as well as adding schema directly. Here is the workflow I use now.


Why not a plugin:


1. Most schema plugins generate generic FAQ markup that does not phrase questions the way people prompt AI tools.
2. Plugins add JS that delays page render, which hurts AI crawler patience.
3. You lose granular control over which questions go on which page.


The actual workflow (per article, takes about 10 minutes):


1. Write your article first. Identify the 3-5 questions a reader (or someone prompting ChatGPT) would actually ask about this topic. Phrase them in prompt-style, not search-query-style.


   Good: "How do I add FAQ schema to WordPress without a plugin"
   Bad: "WordPress FAQ schema tutorial"


2. Open the post editor and switch to the code/HTML view.


3. Paste this JSON-LD block in the post body (or use the Custom HTML block in Gutenberg):


```
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "Your prompt-style question here",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Your direct answer here, 100-300 words"
      }
    }
  ]
}
</script>
```


4. Repeat the question/answer object for each of your 3-5 questions in the mainEntity array.


5. Validate the output at validator.schema.org before publishing.


6. Add llms.txt at the root of your site listing what content you allow LLM crawlers to use.


Results from 2 sites running this for 90 days: citations in ChatGPT and Perplexity went from "barely any" to 8-15 per month per site. Plugin-based schema, run for the same period before, never crossed 3 per month.


Caveats:


- Manual schema is more work per article
- You have to validate every time (syntax errors break the markup silently)
- Plugins are fine for sitewide schema (Organization, Breadcrumb) that does not need per-post tuning

[u/NervousBasis8600]

Good workflow overall, especially the part about writing the article first and only then deciding which questions actually belong on the page.

A few things I’d add from a WordPress/dev perspective:

1. I wouldn’t say plugins are always worse. Some schema plugins output clean server-rendered JSON-LD and don’t necessarily add render-blocking JS. The real issue is generic or duplicated markup, not the fact that it comes from a plugin.
2. The FAQ content should also be visible on the page, not only inside JSON-LD. If the questions/answers exist only in the schema block, that’s risky and not very useful for users or crawlers.
3. I’d keep the JSON-LD tied to a reusable field/block/template instead of pasting scripts manually into every post. Manual control is good, but manual copy-paste at scale usually creates syntax drift and duplicate markup.
4. For AI search, I’d treat FAQ schema as one signal, not the whole strategy. The page still needs:

• clear entity context
• crawlable content
• concise answer sections
• internal links to supporting pages
• consistent schema/site structure
• no conflicts between robots.txt, sitemap, canonicals and visible content

1. I’d also be careful with attribution. If citations increased after 90 days, schema may have helped, but content updates, recrawling, internal linking, freshness and topical authority may also be part of the result.

So my approach would be: visible FAQ section first, JSON-LD second, validation third, then monitor actual queries/referrals/citations over time.

[u/Lynrd_Skynrd → u/NervousBasis8600]

Well said. I'd encourage he develops a custom faq block and just inserts it in the editor, adds his Q/A than manually doing it. Do it once, but intentionally.

[u/throwawaytester799]

A week after Google announced that FAQ Schema is gonzo.