Today I want to tell you a story. It’s about two friends competing for a specific search query.
Thank you for reading this post, don’t forget to subscribe!So there are these two websites competing for the same high-value informational keyword. Similar domain authority. Similar content quality. Similar backlink profiles.
One has been doing it for five years. The other started eighteen months ago.
And the newer site is winning. Featured snippets, AI Overview citations, voice search results. Not everywhere, but in a pattern that shouldn’t be possible given the time gap.
The difference, when you dig into it, isn’t content quality. It isn’t publishing frequency, or social signals, or link building.
If you guessed it would be schema, you’re ahead of literally 90% of your peers.
(Go do some scheming right now, this post isn’t for you. Or go do ten pushups [internal links] to build up your core [semantic map]. Or something else you’ve been putting off.)
The newer site has indeed implemented comprehensive structured data markup, across every content type. The older site has none, or has the bare minimum that WordPress or Yoast do by default and that nobody ever touches because JSON is scary to a content person.
Google could read both sites. But it could truly understand, really get to know, really learn to care about, only one of them.
This is the schema difference. JSON simply cannot be scary enough to stop you from making this difference.
Here’s What Schema
Actually Is
Schema markup — formally, Schema.org vocabulary implemented as JSON-LD, Microdata, or RDFa — is a standardized way of telling search engines explicitly what your content means, not just what it says.
Without schema, Google reads your page and infers. It sees a block of text with a question/answer format and guesses, This might be a FAQ. It sees a byline and a date and infers, This is probably an article. It sees a business name and an address and constructs its own local entity model.
These inferences are increasingly good, possibly they are the future of us all, but they are still just inferences.
With schema, you tell Google directly:
Look. This is an Article. This is its author, who is a Person with these credentials, affiliated with this Organization. These are the FAQs on this page, and here are their exact and correct answers. This is a HowTo, with these specific steps. This is a Product, with this price — and these reviews.
The difference between inferred and declared only matters more as search automates itself. AI systems that synthesize answers from multiple sources are, in part, working from structured data.
Rich results — the featured snippets, knowledge panels, People Also Ask boxes, and AI Overviews chomping down on above-the-fold SERP real estate — are disproportionately fed by schema.
You are leaving all of that on the table if you are not implementing structured data.
Get To Scheming.
Why Nobody Does It,
Or Does It Very Well
Schema has an image problem — a semantic web of them, if you will:
- It sounds technical, which means it sucks.
- It lives in the backend, which Content avoids harder than a millennial making a phone call: Here be dragons.
- It appears to require code fluency, or at least a plugin you’ll have to configure correctly, either of which is a drag.
- The results are not immediately visible in the same way a published post is immediately visible, which makes it easy to overlook when you’re already unconsciously motivated by #1-3.
Also: the SEO industry, which should be championing structured data, has largely deprioritized it in favor of the old things, which are easier to sell:
keyword research, content volume, link building.
tools of yesterday’s trade.
These things are all real and important and good. They produce visible outputs on predictable timelines.
Schema produces invisible infrastructure and pays off in subtle ways that are hard to attribute to any specific action.
This is exactly why it is a competitive advantage.
In certain olden times, you would leave out a bowl of milk for the little people who lived out in the forest. And in return they would chase the foxes away from your hens, and do your laundry with their little hands, do your cobbling if you happened to be a shoemaker. Did they exist? No, probably not. But why risk it? It’s a simple bowl of milk, not something as onerous as learning code.
The things that are easy to sell, and easy to execute, get saturated. The things that require tiny bits of patience and a little technical attention and a slightly longer view stay undercrowded.
The things that are almost, but not quite, a matter of faith.
And listen: Your competitors are not doing schema well if they are doing it at all. The barrier to outcompeting them on this dimension is not high. It is simply unglamorous.
Schema That
Actually Matter
Not all schema is equally valuable. Here is where to put your focus when you arrive at the destination.
Organization and Person Schema
These establish your entity identity, which is as useful to your purposes as it is fun to say. Entity identity.
Google models the web, remember, as a graph of entities and their relationships.
If you have not declared who you are — your name, your website, your social profiles, your founding date, your areas of expertise — Google is building a model of you anyway, from spotty inference.
Declaring it — openly, loudly, boldly, proudly — gives you control over your own entity representation. This matters directly for brand searches, knowledge panels, and the quality and variety of your AI citations.
Do you know your own name, or do you want Google to guess it?
This one is easy. It can also be made so full of facts about you! A whole little profile, all about special. unique, hardworking you. But instead of being a book on a shelf, it knits you into the fabric of Google’s known universe.
Article Schema
This goes on every piece of editorial content. Include:
- Author (as a declared Person entity, not just a string — you get to be famous!)
- Pub date
- Modified dates
- Headline
- A l’il description
This is the baseline. Understand that I am going easy on you.
Most sites implement some version of this one automatically, through their CMS. Most do it incompletely, if not wholly by accident.
FAQ Schema
For any page with a question-and-answer structure. FAQs are disproportionately represented in AI Overviews and People Also Ask results, as you well know.
But take it a step further: If you have FAQ content and you are not marking it up, you are generating those results on behalf of your competitors.
We do not do the enemy these favors. We Schema.
“HowTo” Schema
For instructional content. Same logic as the FAQ — structured, edible, step-by-step content gets preferential treatment in rich results.
Breadcrumb Schema
Yes. And on every page. This is purely navigational — it tells Google how your content is organized hierarchically.
Simple to implement. Consistently ignored.
Local Business Schema
This is not only appropriate but crucial if you have any physical or service-area presence. This is the layer that feeds Google Business Profile, local pack results, and voice search* for local queries.
If you are in any way a local or regional business and you have not implemented this, with care and correctly: you are making yourself invisible to entire, crucial categories of search.
*(A Big Deal, on the level of Schema! We should talk more about it sometime. that’s a blog.)
Grand Totals
So altogether that’s Article Schema + Breadcrumb Schema + the Type, if it’s a special type. three things, that’s all I’m asking. (Well, three things times whatever’s in your library.)
That’s the floor, true. there’s a lot more you can do! But the basics are so easy and the benefits are so important.
Certainly you can do this. Go make your own Person Schema & some Organization Schema and stash ’em somewhere, as a snippet. Now you have them forever and you never have to do it again. This is the way.
Our Zero-Click Future
Because here is what relly makes all of this so urgent:
The trajectory of search, at a meteoric rate, is toward zero-click results. AI Overviews, featured snippets, knowledge panels, direct answers — an increasing, not-quite-yet-majority of queries resolve without a click ever happening.
Google gets the ad impression. Searcher gets their answer. Your content, which provided the answer, gets nothing.
You get nothing.
The Internet falls apart.
This is what is right now happening. It is not a prediction. If you look at your GSC data, and your impressions are holding or growing while your click-through rate is declining, and I bet you $10 it is, you are already in the future.
The response that makes sense is not to try to fight zero-click by making your content harder to extract. That is futile and punishing to users, and weird.
The response that makes sense is to make sure that you are a source of the zero-click answers, and that Google knows this and can credit you appropriately — through rich results, citation in AI answers, and through the kind of entity authority that gets your brand mentioned even in contexts where you did not necessarily publish.
Schema is the primary mechanism for building that authority. It is how you tell the system:
It is I who am the source.
I am that which is authoritative.
It is I, the entity you should be citing.
The content team that builds this infrastructure now, while your competitors are still ignoring it, is building for a considerably better position, as zero-click continues to expand at roughly the speed of our expanding universe.
Implementation
Priorities
If you are starting from scratch, or close to it, first check out your CMS’s automatic Schema to see what you can cross off the list. Most SEO plugins do some amount of this, but you can tweak and supplement that.
Then, do these in order.
- Organization and Person Schema on your homepage and about page. Declare your entity Identity. This is the foundation everything else builds on.
- Article Schema on every published post. Get these right — complete author entity, correct dates, accurate descriptions.
As in life, if you treat yourself like you matter, you will. - FAQ schema on your highest-traffic pages that are mostly question-and-answer content or could easily be rewritten that way. Start there, at the top of your traffic, and work backward through the library.
- Breadcrumb Schema, sitewide. This will be largely automated, again, if you’re on a major CMS with a decent SEO plugin.
- Any other specialized Schema relevant to your content type — HowTo, Product, Event, Review, whatever fits the actual content.
- Get comfortable validating everything in Google’s Rich Results Test. Fix what’s broken. Check it again after major site changes.
This is not glamorous work. But it is honestly not particularly hard either — and it compounds.
Every page you mark up is a page mama Google can understand more precisely, cite more confidently, and surface in the AI formats whilst she ignores the enemy entirely.
So you do the unglamorous work.
Generally speaking — but especially here, where it’s literally existential — that’s where the advantage lives. Get to scheming. Schema is one piece of the full SEO framework for content teams, the structured data layer of semantic SEO, and the foundation for agent-ready content.
I write about content strategy, editorial leadership, and apparently sometimes the future of search.
For inquiries: jacob@cliftoncreative.agency & cal.com/cliftoncreative