What Yoast SEO actually outputs in your page source
Yoast SEO has been injecting structured data into WordPress sites for years. If you install it and do nothing else, it will automatically add a JSON-LD block to every page. That block typically includes a WebPage or Article schema type, a WebSite entity on the homepage, a BreadcrumbList for navigation, and a Person or Organization entity depending on what you've configured in the settings.
That's a reasonable baseline. It's certainly better than no schema at all. The question is whether it's the right schema for the job when the job is getting cited by AI search engines like ChatGPT, Perplexity, and Gemini, rather than simply earning a rich snippet in Google.
The honest answer: Yoast does a decent job for traditional SEO. For AI visibility, it leaves significant gaps that you'll need to fill yourself.
Where Yoast's schema holds up well
Let's be fair first. Yoast's automatic schema graph is genuinely useful for a few things.
The Organisation entity
Yoast will publish an Organization schema on your homepage if you tell it your site represents a business. It pulls in your site name, URL, and logo. For AI search engines trying to understand who is behind a website, this is valuable. Large language models use entity information to build an understanding of your brand, and having a well-formed Organization block helps establish that identity clearly.
That said, Yoast's Organization output is fairly minimal. It won't include your sameAs array of social profiles, your founding date, or your areas of service without additional configuration or manual overrides. Those fields matter more for AI context than they do for Google rich results.
Article schema for blog posts
When you mark a post as an article in Yoast, it will output Article or BlogPosting schema. This includes the headline, date published, date modified, author, and a reference back to the publisher. That's a solid foundation. AI crawlers like Perplexity's index and GPTBot do read and use this metadata to assess the credibility and freshness of content.
If you want to understand how Article schema works specifically in the context of AI citation, the post on how to use Article schema to get your blog posts cited by AI goes into much more depth on the individual fields that carry the most weight.
BreadcrumbList
Yoast automatically outputs BreadcrumbList schema based on your category and page hierarchy. For AI engines that are trying to understand site structure and topical authority, this actually helps. It signals that a page sits within a particular content category, which reinforces topical clustering.
Where Yoast falls short for AI search
This is where things get more interesting, and more consequential.
No FAQ schema by default
Yoast Premium used to have a FAQ block feature that would output FAQPage schema. Google then deprecated FAQ rich results for most sites in 2023, and Yoast subsequently removed the feature from its block in later versions. The practical result: if you're using a recent version of Yoast, you won't get FAQ schema automatically at all.
This is a problem for AI visibility. FAQ schema is one of the most directly useful schema types for large language models. When an LLM is looking for a clear, citable answer to a question, a well-structured FAQPage block with explicit question-and-answer pairs makes that extraction trivial. You're essentially pre-formatting your content in the shape AI engines prefer to cite.
You'll need to add FAQ schema manually, either through a separate plugin or via custom JSON-LD. The post on how to add FAQ schema to product pages covers the mechanics even if you're on WordPress rather than Shopify.
Product schema is shallow
If you're running a WooCommerce store alongside Yoast, you'll find that the product schema output is basic at best. Yoast does output Product schema, but it often lacks Review aggregates, proper Offer nesting with availability and price validity dates, and brand information. AI search engines use product schema to understand what you sell and whether your pages are authoritative sources for specific products. Thin product schema means thin AI understanding.
No Speakable schema
Yoast does not output Speakable schema. This is a schema type that explicitly tells AI and voice assistants which sections of a page are the best candidates for reading aloud or quoting directly. It's niche, but increasingly relevant as AI-driven voice search and AI answer summaries become more common. If you want to understand what it does and how to implement it, the guide on how to use Speakable schema to get cited in AI voice answers is worth reading.
No ItemList or Dataset schema
Yoast has no built-in support for ItemList schema, which is useful for category pages, roundup posts, or any page that lists products, services, or articles. It also doesn't output Dataset schema, which is the schema type that can help you get cited as a primary data source by AI engines. These are specialist schema types, but they're precisely the kinds of structured data that differentiate an AI-visible site from one that's merely Google-optimised.
The schema graph can conflict with custom additions
One practical issue that comes up a lot: Yoast outputs its schema as a single interconnected JSON-LD graph using @graph. That's technically correct and Google-approved, but it can create headaches when you try to add custom schema types on top. If you add a separate FAQPage block manually and Yoast is already outputting a WebPage node, validators can flag duplicate or conflicting entities on the same page.
The cleanest way to handle this is to either extend Yoast's graph programmatically using its Graph API (which requires PHP knowledge), or to add your supplementary schema in a way that doesn't create conflicting @id references. Neither option is particularly beginner-friendly.
The bigger picture: Yoast was built for Google, not for LLMs
This isn't a criticism of Yoast as a tool. It's genuinely excellent at what it was designed to do: help WordPress sites rank in Google. The schema it outputs aligns with Google's rich result guidelines, Google's Search Console expectations, and Google's structured data documentation.
AI search engines have different priorities. They're not primarily looking for signals that a page deserves a rich snippet. They're trying to identify authoritative, citable content that clearly answers questions. The schema types that matter most for that goal (FAQ, Speakable, ItemList, HowTo, Dataset, Person with detailed credentials) are largely absent from Yoast's default output.
There's also the question of what AI engines actually crawl. ChatGPT's GPTBot, Perplexity's PerplexityBot, and Google's Gemini-linked crawlers all have their own indexing behaviours. The assumption that ranking well in Google automatically means being visible to AI search is increasingly unreliable. The post on whether ChatGPT uses Google's index or its own crawl explains the distinction clearly.
At FlinnSchema, we work with WordPress and WooCommerce sites that have been using Yoast for years. The pattern we see consistently is that Yoast has done a reasonable job with the baseline, but every site needs a layer of AI-specific schema added on top: custom FAQ blocks, richer Organisation entities with sameAs profiles, HowTo schema for tutorial content, and properly structured Product or Service schema for commercial pages.
What to add on top of Yoast
If you're already using Yoast and want to improve your AI search visibility without replacing it entirely, here's where to focus.
Extend your Organisation entity
Go into Yoast's settings and fill in every field it offers. Then, separately, add a custom JSON-LD block to your homepage that extends the organisation with fields Yoast doesn't include: sameAs pointing to your LinkedIn, Twitter/X, Facebook, Wikipedia page (if you have one), and any relevant directory listings. Also add foundingDate, areaServed, and a detailed description. AI engines use these to build a richer picture of your brand.
Add FAQ schema to key pages manually
Identify your highest-value pages, whether that's service pages, product pages, or cornerstone blog posts, and write 3 to 5 genuine question-and-answer pairs for each. Add these as FAQPage JSON-LD directly in the page's head or body. Make sure the answers are complete and self-contained. AI engines are more likely to quote an answer that makes sense without needing additional context.
Use HowTo schema for process content
If you have any content that walks readers through steps, a recipe, a setup guide, a tutorial, adding HowTo schema makes that content dramatically more parseable by AI. Yoast won't add this automatically. You'll need to write it yourself or use a plugin that supports it.
Audit what Yoast is actually outputting
Use Google's Rich Results Test or Schema.org's validator to see exactly what JSON-LD Yoast is generating on each page type. You may find it's adding schema you don't need, or missing schema you assumed it was adding. If you're unsure where to start, a free AI visibility audit from FlinnSchema will show you precisely what structured data is present and what's missing across your site.
Frequently Asked Questions
Does Yoast SEO automatically add schema markup to every page?
Yes, Yoast adds JSON-LD schema to every page by default. The specific type depends on the page: posts get Article or BlogPosting, the homepage gets WebSite and Organization, and most pages get a WebPage node. BreadcrumbList schema is also added throughout. However, many schema types relevant to AI visibility are not included automatically.
Can I use Yoast and add custom schema at the same time?
Yes, but you need to be careful about conflicts. Yoast uses a connected @graph structure, so adding a competing JSON-LD block with the same entity types can create validation warnings. The cleanest approach is to use Yoast's Graph API to add nodes programmatically, or to add supplementary schema types (like FAQPage or HowTo) that don't overlap with what Yoast already outputs.
Is Yoast SEO enough for AI search visibility on its own?
For most sites, no. Yoast provides a useful baseline of structured data aligned with Google's requirements, but it doesn't output several of the schema types most relevant to AI citation: FAQPage, Speakable, HowTo, ItemList, Dataset, and richer Person or Organisation entities. You'll need to supplement it to be genuinely visible to AI search engines like ChatGPT and Perplexity.
Does updating Yoast to the latest version improve AI visibility?
Keeping Yoast updated is always a good idea for security and compatibility, and newer versions do refine the schema graph output. However, the core limitations around AI-specific schema types are not a versioning issue. They reflect the fact that Yoast is built primarily around Google's structured data guidelines, which predate AI search as a meaningful channel. Updates won't close the gap on their own.