Schema Markup Is the Most Underrated Technical SEO Investment You Can Make
Written by Gabriel Bertolo
May 21, 2026
Most businesses treat schema markup like a box to check at the bottom of a technical SEO to-do list. Something the developer adds after launch. Maybe.
That’s a mistake. And it’s one I see in almost every audit I run.
Schema markup is one of the highest-ROI technical SEO investments available right now. It’s also the single most important factor for getting your business cited in AI search results from ChatGPT, Google AI Overviews, Perplexity, and Gemini.
And yet
Only about 30% of websites have implemented it, while 72.6% of pages ranking on Google’s first page use schema. Source: Backlinko and Searchmetrics via Search Engine Land
Read that again. Nearly three-quarters of pages that rank on page one have schema. Seven out of ten websites don’t. If you’re in that 70%, you’re competing with a disadvantage you might not even know about.
Schema markup is code you add to your website that tells search engines and AI platforms what your content means. Not what it says. What it means.
Your website might mention “Gabriel Bertolo” and “Northampton” and “SEO” on the same page. A human reads that and understands I’m an SEO professional based in Northampton. But a search engine is guessing. Schema removes the guessing. It explicitly declares: this is a Person, this is their job title, this is their business, this is where they’re located, and here are their social profiles.
That clarity is what separates entities that get rich results, Knowledge Panels, and AI citations from entities that don’t.
Now here’s the nuance. Google has said schema markup is not a direct ranking factor. And that’s technically true. But calling it “not a ranking factor” is like saying the foundation of a house isn’t a room. It’s not a room. But nothing works without it.
Schema enables rich results. Those enhanced search listings with star ratings, pricing, FAQ dropdowns, and event details that take up more space and grab more attention in the SERPs.
Rich results receive 58% of clicks in search results compared to 41% for non-rich results. Nestle reported an 82% higher CTR for pages displaying rich results, and Rakuten saw 2.7x more organic traffic after implementing structured data. Source: Google Case Studies
More clicks from the same ranking position. More traffic without building a single additional backlink. That’s the ROI of schema.
The format that matters is JSON-LD. Google recommends it. It lives in the head of your page, separate from your HTML, which makes it easier to implement, maintain, and scale. If your site is still using Microdata or RDFa, it’s time to migrate.
There are over 800 schema types on Schema.org. You don’t need 800. You need about six. And you need them implemented correctly.
If you have a physical location or serve a specific geographic area, this is non-negotiable. LocalBusiness schema declares your name, address, phone number, hours, service area, and business category in a format machines can read without ambiguity.
This feeds Google Maps, the local Map Pack, and your Knowledge Panel. Without it, you’re relying on Google to piece together your local entity from scattered signals across the web. With it, you’re telling Google exactly who you are and where you operate.
This declares your entity at the highest level. Business name, logo, contact information, founding date, and social profiles. The sameAs property is especially important. It connects your website to your LinkedIn, Facebook, Google Business Profile, and other platforms. This is how you tell search engines “all of these are the same entity.”
Entity coherence matters. When every platform tells the same story about who you are, search engines resolve your entity with confidence. When signals conflict, they hedge. We’ve written extensively about this because it’s foundational to everything we do.
Every blog post and article on your site should have Article or BlogPosting schema. It connects content to authors, which builds the E-E-A-T signals that Google evaluates when deciding whether to trust your content.
This is where Person schema nests inside Article schema. The author isn’t just a name on the page. It’s a declared entity with credentials, a URL, and connections to other platforms. That distinction matters for topical authority.
FAQ schema enables FAQ rich results in search. Google has limited these to authoritative sites for certain query types since 2024. But even where the rich result doesn’t display, FAQ schema feeds AI platforms structured Q&A data that can be used in AI Overviews and chatbot responses.
If you have a FAQ section on a page, mark it up with FAQ schema. It takes 10 minutes and the upside is significant.
For e-commerce and service businesses with reviews. Product schema enables star ratings, pricing, and availability directly in search results. Review schema aggregates your ratings into a visible trust signal.
Search Pilot ran a controlled test and found that adding Review schema alone to product pages increased traffic by 20%. That’s a 20% traffic lift from one schema type.
Underused and underrated. Service schema declares what services you offer, where you offer them, and at what level. For service businesses, this is how you explicitly tell search engines what queries you should show up for.
This is where schema goes from “nice SEO tactic” to “critical business infrastructure.”
AI search platforms like ChatGPT, Google AI Overviews, Perplexity, and Gemini need to understand your content to cite it. They’re building knowledge networks that connect entities, facts, and relationships. Schema markup is the most direct way to feed those networks.
Microsoft’s Bing team stated explicitly that schema markup helps their LLMs understand content. Google has said the same. When AI systems evaluate whether to cite your website as a source, structured data gives them machine-readable clarity about what your content covers and who is behind it.
And the data backs this up.
A controlled Search Engine Land experiment in 2025 tested three nearly identical pages with the only variable being schema markup. Only the page with well-implemented JSON-LD appeared in a Google AI Overview. The page without schema never even got indexed. Source: Search Engine Land experiment, cited by GWContent
That’s not a marginal advantage. That’s the difference between existing in AI search and not existing at all.
We’ve built our entire Generative Engine Optimization methodology around this reality. Schema is one of the foundational layers of how we prepare websites for AI search visibility. And our AI Visibility Scanner checks for schema implementation as one of the first diagnostic steps.
Schema implementation doesn’t have to be complicated. But it does have to be correct. Bad schema is worse than no schema because it sends conflicting signals that undermine your entity coherence.
Start with Google’s Structured Data Markup Helper and the Schema.org documentation. These give you templates for every schema type.
JSON-LD goes in the head section of your page. Each page should have schema relevant to its content type. Your homepage gets Organization schema. Your service pages get Service schema. Your blog posts get Article schema with author attribution. Your location pages get LocalBusiness schema.
Validate everything with the Google Rich Results Test before deploying. After deployment, monitor the Enhancements section in Google Search Console. It shows which schemas Google has recognized, any errors, and your rich result performance.
Common mistakes I see in technical SEO audits:
Marking up content that isn’t visible on the page. Google requires that schema reflect what users actually see. If your schema says the product costs $49.99 but the page shows $59.99, that’s a problem.
Duplicate schema blocks on the same page. Multiple conflicting instances of the same schema type create confusion. Consolidate into one schema block.
Mismatched data between schema and other sources. Your schema says your business is at 123 Main St. Your Google Business Profile says 456 Oak Ave. That inconsistency fragments your entity signals.
Here’s how I think about schema markup, and it’s the framing that separates good implementation from great implementation.
Schema isn’t just structured data. It’s an entity declaration. It’s how you tell every search engine, every AI platform, and every knowledge system on the internet who you are, what you do, where you operate, and how your content relates to the broader web.
That declaration needs to be coherent. Your schema should tell the same story as your Google Business Profile, your about page, your social profiles, your citations, and your on-page content. When every signal aligns, search engines resolve your entity with confidence. When signals conflict, resolution becomes uncertain. And uncertain entities don’t rank.
This is the foundation of our entire approach to SEO. Entity coherence. Clear signals. No ambiguity.
Schema is where it starts.
Does schema markup directly improve rankings?
No, and Google has confirmed this. But schema enables rich results that dramatically improve click-through rates, and higher CTR from the same position drives more traffic and sends positive engagement signals. Schema also feeds AI systems structured data that influences whether you get cited in AI search. So while it’s not a direct ranking factor, its indirect impact on visibility and traffic is enormous.
What is the best format for schema markup?
JSON-LD. Google explicitly recommends it. It separates structured data from your HTML, which makes it easier to implement, maintain, and debug. If you’re using Microdata or RDFa, consider migrating.
How long does it take for rich results to appear?
Typically 1-4 weeks after implementation. CTR improvements are often measurable within 2 weeks. But you need to validate your schema with the Rich Results Test first to make sure it’s eligible.
Do I need schema markup for AI search visibility?
Yes. AI crawlers rely on structured data as a trust signal when deciding which sources to cite. Testing has shown that pages without schema are significantly less likely to appear in AI Overviews. If AI search visibility matters to your business, schema is not optional.
Can schema markup hurt my site?
Only if it’s implemented incorrectly. Inaccurate schema, marking up content that doesn’t exist on the page, or conflicting data can create negative signals. Validated, accurate schema has no downside.
If you’re not sure whether your site has schema, whether it’s implemented correctly, or whether you’re missing rich result opportunities, run a free check with our AI Visibility Scanner. It takes less than 30 seconds.
Or if you want a full technical assessment, get in touch. Schema implementation is one of the fastest wins we deliver for new clients. And the ROI compounds over time as AI search continues to grow.
For the complete picture of how schema fits into a broader SEO strategy, read our ultimate guide to SEO for small and mid-sized businesses.
Gabriel Bertolo is a 3rd generation entrepreneur who founded Radiant Elephant over 13 years ago after working for various advertising and marketing agencies.
He is also an award-winning Jazz/Funk drummer and composer, as well as a visual artist.
His Web Design, SEO, and Marketing insights have been quoted in Forbes, Business Insider, Hubspot, Entrepreneur, Shopify, MECLABS, and more.
Check out some publications he's been quoted in:
Quoted in HubSpot's AI Search Visibility Article and HubSpot's Article on 6 Best Wix Alternatives
Quoted in DesignRush Dental Marketing Guide
Quoted in MECLABS
Quoted in DataBox Website Optimization Article and DataBox Best SEO Blogs
Quoted in Seoptimer
Quoted in Shopify Blog