Use case · FAQPage schema attacher
Add Schema.org FAQ markup to any post in chat.
Pass the agent 5 question-and-answer pairs; it attaches a FAQPage JSON-LD block to the post. The plugin emits it in the page head automatically. Google rich-results-eligible in one turn.
The problem you actually have
Adding Schema.org FAQPage markup to a post is a one-time job that takes 20 minutes if you know what you’re doing — write the JSON-LD, escape the strings, paste it in a code block, hope the SEO plugin doesn’t collide with it. RankMath has a Schema builder; Yoast has one too. Both add complexity to a workflow that should be a 30-second chat turn.
And you can’t bulk-do it. Most pricing pages, comparison pages, and feature pages should have FAQ schema. Your site has 14 pages that should and 1 that does.
You want: list the pages that should have FAQ schema, draft 5 Q&As for each (the agent reads the page content), apply via a single tool call. Plugin emits the JSON-LD in <head> automatically.
How the assistant solves it
You type the request in plain English inside wp-admin. The agent picks wp_set_faq_schema (plus wp_search_posts, wp_audit_schema as needed) and walks the steps below.
- You ask: “add FAQ schema to my pricing page with 5 common questions.”
- The assistant calls
wp_search_poststo find the pricing page, then reads its content. - It drafts 5 question/answer pairs that match the page’s scope (pricing tiers, what’s included, refund policy, etc.). Presents them in chat.
- You edit / approve / strike. “Drop question 3, replace with: ‘do you support EU VAT MOSS?'”.
- The assistant calls
wp_set_faq_schemawith the page ID and the approved pairs. The plugin stores the JSON-LD in post_meta and emits it in the page<head>. - It runs
wp_audit_schemato confirm the attachment landed.
Before vs after
| Without the assistant | With the assistant | |
|---|---|---|
| Time per page | 15-25 minutes (write JSON, paste, validate, troubleshoot) | 2-3 minutes per page including review |
| Validity | You debug rich-results-test errors yourself | JSON-LD generated correctly first time, validates against Schema.org |
| SEO plugin collision | RankMath and Yoast may emit competing JSON-LD blocks | Animam JSON-LD is namespaced and additive, doesn’t collide |
| Coverage | You schema-tag the 1-2 most visited pages | Schema-tag every page that should have it |
Where it stops
- Google’s FAQ rich results are limited (since 2023, only government/health/non-profit sites get FAQ rich snippets in search). The schema is still useful for AI search engines (Perplexity, ChatGPT search) and for general semantic clarity. Don’t expect FAQ rich snippets in Google search results unless you fit the narrow remaining categories.
- Schema is post-meta-stored: if you delete the post, the schema goes with it. If you switch SEO plugins, Animam’s JSON-LD survives because it’s in our own meta key.
- For non-FAQ schemas (Article, SoftwareApplication, Product), use the more general
wp_set_schema_jsonldtool — same idea, broader scope.
FAQ
Does Google show FAQ rich results from this?
Since 2023, Google only shows FAQ rich snippets for government, health, and non-profit sites. The schema is still indexed and used by AI search engines (Perplexity, ChatGPT search), and helps general semantic understanding of the page. Don’t deploy it expecting Google rich snippets unless your site fits.
Will it conflict with RankMath or Yoast schema?
No — Animam emits its JSON-LD in a separate <script type="application/ld+json"> block. Multiple JSON-LD blocks on the same page are valid Schema.org. RankMath’s Article schema and Animam’s FAQPage schema coexist fine.
Plan?
Admin or Bundle.
Schema-tag every pricing and comparison page.
Free plan, no card. Or read the full admin assistant page.