Use case · Schema.org attacher (any type)
Tag any post with any Schema.org type in chat.
Article, SoftwareApplication, Product, Organization, BreadcrumbList — any Schema.org @type. The agent drafts the JSON-LD body from the page content, you review, plugin emits it in the page head.
The problem you actually have
Beyond FAQ, your pricing pages need SoftwareApplication, your blog posts need Article, your e-commerce pages need Product, your homepage needs Organization, your category pages need BreadcrumbList. Every one of these is a JSON-LD block you have to write, validate, and paste in.
RankMath’s Schema builder is good but locked into the RankMath UI; Yoast’s is paywalled. Either way, it’s a per-page click-fest with a steep learning curve for anyone who’s not already fluent in Schema.org.
You want: tell the agent what type the page should have, it drafts the body from the page content, you review, it attaches. Audit coverage across the site to find which pages still need schema.
How the assistant solves it
You type the request in plain English inside wp-admin. The agent picks wp_set_schema_jsonld (plus wp_audit_schema, wp_search_posts as needed) and walks the steps below.
- You ask: “audit my schema coverage and tell me what’s missing.”
- The assistant calls
wp_audit_schema: returns counts of pages with no schema, pages with FAQ schema, pages with custom schemas (per type). - You pick a category to fix: “tag my 6 product pages with Product schema.”
- For each, the agent reads the page, drafts a Product JSON-LD body (name, description, brand, sku, offers.price, etc.), presents it for review.
- You approve / edit. The agent calls
wp_set_schema_jsonldwith @type=Product and the approved body. Stored as_animam_jsonld_productmeta. Emitted in<head>. - Re-audit confirms coverage.
Before vs after
| Without the assistant | With the assistant | |
|---|---|---|
| Per-page time | 20-40 minutes (Schema.org docs, write JSON, validate) | 3-5 minutes including review |
| Validation | Hand-validate each in Google’s Rich Results Test | Drafted to validate first time; you can re-validate as a sanity check |
| Coverage map | You don’t have one | wp_audit_schema gives you a dashboard count + per-page sample |
| Type diversity | You only tag the easy ones (FAQ, Article) | Article, Product, SoftwareApplication, Organization, BreadcrumbList all in scope |
Where it stops
- For Schema.org types with many required properties (Recipe, Event, JobPosting), expect to provide more guidance to the agent. It still drafts a starting point but a full Recipe needs ingredients, instructions, nutritional info — you may have to feed it the data.
- The plugin doesn’t replace Yoast/RankMath schema entirely — they may still emit Article schema automatically. Multiple JSON-LD blocks for the same page are valid; just be aware Animam’s schema is additive, not exclusive.
data: nullremoves the schema. Useful for cleanup.
FAQ
Can I attach multiple schema types to the same page?
Yes — call the tool once per type. They’re stored under different meta keys (_animam_jsonld_article, _animam_jsonld_product, etc.) and emitted as separate JSON-LD blocks. Schema.org allows this.
Does Google use these for rich snippets?
For some types yes (Product price, Recipe), for others not directly (Organization is mostly used in knowledge graph). All types help AI search engines (Perplexity, ChatGPT) understand your pages semantically.
Plan?
Admin or Bundle.
Get to schema-coverage parity in an afternoon.
Free plan, no card. Or read the full admin assistant page.