Schema markup is a small block of code that tells a search engine what a page is about in a form it does not have to guess at. A page about a recipe says it is a recipe. A page answering questions says which questions. A product page says the price and whether the item is in stock.
Being clear about what it does not do: adding schema does not raise your position. Google has said this repeatedly and the evidence agrees. What schema changes is the appearance of your result once you already rank, and that is worth having, because a result carrying star ratings or a set of expandable questions takes up more of the screen and draws more clicks than a plain blue link sitting beside it.
The other reason to care is that search results are increasingly assembled rather than listed. AI answers, knowledge panels and voice responses all pull from structured data because it is the only part of a page that states facts in a machine-readable form. A page without it can still be read; a page with it is easier to quote.
How markup actually reaches a search result
The chain is short and every link can break independently, which is why so much schema work quietly does nothing.
The most common failure is the last step, and it has nothing to do with code. If your markup describes content the visitor cannot see on the page, the result is not just ignored, it is a policy violation, and Google can remove your rich results across the whole site. Marking up questions and answers that only exist in the markup is the classic version of this.
- PageThe visible content a reader gets
- MarkupJSON-LD in the head describing that content
- CrawlGoogle reads both and checks they match
- ResultThe listing gains stars, questions or a price
The types actually worth adding
There are hundreds of schema types and you will use about five. Adding more is not better; each one you add is another thing that can fall out of sync with the page.
Start with Organization on your homepage, because it is what feeds a knowledge panel and it is the one piece of markup that describes the whole business rather than a page. Then add the type that matches what each template publishes.
- Organization, once, on the homepage: name, logo, social profiles, contact
- Article or BlogPosting on every post: headline, author, date published, date modified
- FAQPage on any page that visibly answers questions, and only those
- Product on anything you sell: price, currency, availability
- BreadcrumbList so the result shows your site structure instead of a raw URL
- LocalBusiness if you have a physical address people visit
Adding it without a developer
Use JSON-LD, which is a script tag in the head of the page rather than attributes woven through your HTML. Google prefers it, and more importantly it means your markup lives in one place instead of being tangled into the layout, so a design change cannot silently break it.
If you run WordPress, an SEO plugin will output most of this from fields you fill in. If you run something custom, it is a single script tag per template. Either way, generate it from the same data the page renders from rather than typing it separately, because two sources of the same fact drift apart within a month.
Then test it. Google's Rich Results Test tells you what it can read and what it will show. Search Console has an Enhancements section listing errors across every page it has crawled, which catches the case where one template is fine and another has been broken for six weeks.
The mistakes that undo the work
Marking up invisible content is the serious one, covered above. The rest are ordinary and easy to avoid.
Marking up the wrong thing is common: a category page describing itself as a single Product, or a blog index claiming to be one Article. The markup should describe the page it is on, not the site it belongs to.
Letting dates go stale is the quietest. If your Article markup says dateModified and that value never changes, you are telling a search engine the page has not been touched since publication, which is exactly the signal you do not want on content you have been diligently refreshing.
Common questions
- Does schema markup improve rankings?
- Not directly. Google has stated that structured data is not a ranking factor, and the evidence supports that. What it changes is how your result looks once you already rank. A listing with review stars or expandable questions occupies more space and attracts more clicks than a plain link, so the traffic can improve while the position does not move at all.
- What is the difference between schema, structured data and JSON-LD?
- They are three names for parts of the same thing. Schema.org is the shared vocabulary that defines the types. Structured data is the general term for marking content up in any machine-readable way. JSON-LD is the specific format Google recommends, a script tag in the page head. In practice people use all three words to mean the same activity.
- Can I mark up FAQs that are not visible on the page?
- No, and this is the one mistake worth being genuinely careful about. Marking up content a visitor cannot see violates Google's structured data guidelines. It does not merely fail to work, it can trigger a manual action that removes rich results across your whole site. Only mark up questions the page actually displays.
- How do I check my schema markup is working?
- Use Google's Rich Results Test on individual URLs to see what it can read and which enhancements it qualifies for. Then check the Enhancements section of Search Console, which reports errors across every page it has crawled. The second one matters more, because it catches a template that broke weeks ago on pages you were not thinking to test.
Keep reading