Your site has Article schema.
You know this because you installed Yoast three years ago and clicked through the setup wizard. The default Article schema fired. You moved on. You have not thought about schema since.
Somewhere in your organization, there is a page that answers ten frequently asked questions. It does not have FAQ schema. There is a page that walks users through a six-step process. It does not have HowTo schema. There is an author page for your most credible subject-matter expert. The structured data on that page does not connect the author to the topics they’ve published on.
This is not a technical failure. Technical failures get fixed when someone notices them. This is an organizational failure — nobody is responsible for schema as an editorial decision, so it doesn’t get made.
What schema markup actually does
Schema markup is a structured data vocabulary that tells search engines what your content means, not just what it says. It’s not for human readers. It’s a signal to machines — a layer of explicit meaning that sits underneath the prose.
In JSON-LD format, schema markup tells a search engine: this page is an article written by this named expert on this date. This section is a list of frequently asked questions. This is a process with these specific steps. Without schema, the search engine infers meaning from the content. With schema, you state it directly.
Why this matters for AI search: inference is uncertain. When an AI engine is deciding whether to cite your page as a source, it is making a judgment about what your page is and whether it can be trusted. FAQ schema removes the ambiguity about whether your page answers questions. HowTo schema removes the ambiguity about whether your process is genuinely sequential. Author schema removes the ambiguity about whether a named expert is responsible for the content.
The engine doesn’t have to guess. You told it. That’s the difference between content that gets cited and content that gets passed over.
The schema types that matter for content-heavy B2B sites
Article schema is the floor. If you’re publishing, you should have Article schema with a named author entity, correct publication dates, and a headline that matches your H1. Most sites have this. Most sites have it set to “Organization” as the author rather than a named person, which is weaker. Fix that.
FAQ schema is the gap. If you have a page that answers multiple discrete questions — and most content-heavy sites have dozens of them — FAQ schema tells search engines explicitly that this content is structured for answer delivery. This directly increases the probability of AI citation. The pages on your site that answer questions but don’t have FAQ markup are invisible to AI engines as FAQ content.
HowTo schema is underused everywhere. If you have any process content — guides, frameworks, step-by-step explanations — HowTo schema marks each step explicitly. The engine can extract and present individual steps without presenting the whole page. For AI search, this is significant: your step two can be cited on its own if it’s the best answer to a specific question.
BreadcrumbList schema handles site navigation and is often handled automatically by Yoast when configured correctly. But “configured correctly” is doing a lot of work in that sentence.
The organizational gap
Here is the question: who decides which pages get FAQ schema?
Not which pages have it, because Yoast installed Article schema everywhere. Who is making the active decision that a specific page should be marked up as FAQ content? Who is reviewing new content before it publishes and asking whether it qualifies for HowTo markup? Who is validating that the Article schema on your highest-traffic posts correctly names the author and links to their author page?
In most companies, the answer is nobody, in the sense that it’s theoretically someone’s job but practically nobody’s priority. It might be in the SEO vendor’s scope. The vendor isn’t reading every post before publication. It might be in the content team’s scope. The content team is writing to a brief that doesn’t include a schema decision.
This is an editorial infrastructure gap. Schema decisions aren’t technical decisions — they’re content decisions. Which pages are genuinely FAQ pages? That requires reading them and making a judgment. Which processes are sequential enough to warrant HowTo markup? That requires editorial judgment about structure. What expertise credentials should be surfaced in the Article schema author entity? That requires knowing what the author actually knows.
Someone with editorial authority over the content operation makes these calls. In the absence of that authority, schema stays at defaults, and defaults are not a strategy.
The credibility problem this creates
There is an additional issue worth naming directly. If your company publishes content about SEO or content strategy or search visibility, and your own site has mediocre schema implementation, you are broadcasting a credibility gap to every prospect who checks.
This is not a hypothetical. The Rich Results Test is a free tool. Anyone evaluating your site for editorial credibility can run it in thirty seconds. What they find tells them whether you practice what you publish.
Every recommendation your content makes about search performance should be implemented on your own site. Schema is the most visible version of this. A site that writes about schema and hasn’t validated its own FAQ markup is not a site you should trust to tell you how to do content strategy.
Get the function in place. Run the Rich Results Test on your ten highest-traffic posts. Look at what’s missing. Then ask who in your organization is responsible for making sure it’s never missing again.
Why schema decisions belong to editorial in the first place, rather than to the dev team or the SEO vendor, is the argument here.
Schema markup is structured data added to web pages that tells search engines explicitly what the content is — what type of page, who wrote it, what questions it answers, what steps it contains. It’s the machine-readable layer beneath the human-readable content. Without it, Google infers meaning from content. With it, you declare it directly. The difference is precision, and precision is a trust signal. Most sites have incomplete schema and don’t know it.
At minimum: Organization schema on your About page with sameAs attributes, Person schema for each named author linked to external profiles, Article schema on every post, and FAQPage schema on posts that answer specific questions. Add HowTo schema for instructional content and LocalBusiness schema if you have a local presence. Start with what closes the biggest credibility gap — usually Organization and Author schema — not the most technically complex options.
The most reliable method for content-heavy sites is JSON-LD delivered via an invisible HTML block in the Gutenberg editor, placed at the bottom of each post. Yoast handles basic Article and Organization schema automatically, but for Author schema with sameAs, FAQPage schema, and HowTo schema, manual JSON-LD blocks give you precise control over every property without depending on plugin defaults that may be incomplete or incorrect.
Article schema identifies the post type, author, publication date, and publisher — it establishes who produced the content and when. FAQ schema identifies specific question-and-answer pairs within the content, making them eligible for rich results and AI citation. Both should be present on most blog posts. Article schema builds the entity record. FAQ schema surfaces specific answers. They serve different purposes and are not interchangeable.
Test every piece of schema in Google’s Rich Results Test immediately after publishing. Search Console’s Rich Results report shows which pages are generating rich results and flagging errors. For FAQ schema specifically, watch for featured snippet appearances on your target questions in the months after implementation. If schema is correct but rich results aren’t appearing, the issue is usually topical authority or content quality, not the schema itself.