Structured Data, Explained Simply
A search result that shows a star rating, a price, or a set of breadcrumbs above the title is not doing anything the site next to it could not do. It is using structured data: a small block of machine-readable facts added to the page, in a format Google already knows how to read.
What structured data is
Your page says, in prose, that a recipe takes forty minutes and serves four. A human reads that instantly. A search engine has to infer it from a sentence, and inference is where things go wrong.
Structured data removes the guessing. It is a block of code, usually placed in the page's <head>, that states the same facts in a fixed vocabulary — this is a Recipe, cooking time is forty minutes, yield is four servings. The vocabulary comes from schema.org, a shared standard, and Google's recommended format for writing it is JSON-LD: a self-contained script block that does not touch your page's visible markup.
A minimal example, for an article:
{ "@context": "https://schema.org", "@type": "Article", "headline": "How to shape a sourdough loaf", "datePublished": "2026-03-14", "author": { "@type": "Person", "name": "Sara Ahmadi" } }
Nothing there is new information. It is the same facts the page already shows, written where a machine cannot misread them.
What it does, and what it does not
Structured data makes a page eligible for a rich result — the enhanced listing with extra detail attached. Eligible is the operative word. Google decides whether to show one, and it often does not. Valid markup is a requirement, not a promise.
It also helps Google understand what the page is about with less inference, which matters more as search results are increasingly assembled rather than simply listed.
What it is not is a ranking lever. Adding markup to a thin page does not make the page good, and Google does not publish structured data as a general ranking factor. The honest expectation is a better-looking, better-understood listing for a page that already deserved to be there — which, on a result page competing on titles and descriptions, is worth having.
One firm rule: the markup must describe content the visitor can actually see on the page. Marking up a rating nobody left, or a price the page does not show, is against Google's guidelines and is the fastest way to lose rich results entirely.
What to do
- Start with what your site actually is. An
Articlefor blog posts,Productfor products,LocalBusinessfor a shop with an address,BreadcrumbListfor the navigation trail. One accurate type beats five speculative ones. - Use JSON-LD. It sits in one block, and it does not break when someone edits the page's layout.
- Check the current documentation for which types are eligible for rich results. The supported list changes — types have been added and removed over the years — so the docs are the source, not a blog post from three years ago.
- Test every template once with Google's Rich Results Test, then watch the enhancement reports in Search Console, which check the pages Google actually crawled rather than one you pasted in.
- Fill in the required properties for your type. Missing ones make the block ineligible; the test names them.
Common mistakes
Marking up what is not on the page. Review stars for reviews that do not exist, an FAQ block whose questions appear nowhere in the text. This is the violation Google acts on most visibly.
Installing three plugins that each add their own. The result is several conflicting blocks on one page describing it as different things. Pick one source of markup and turn the others off.
Treating a warning as an error. Google's tools distinguish the two. Errors make the block ineligible; warnings are recommended properties you have left out. Chasing every warning to zero is rarely worth the afternoon.
Sources: Introduction to structured data markup and Structured data general guidelines.
Was this useful?
Counts appear once there are 5 votes.
Related posts
Canonicals and Duplicate Content
The same page usually has several addresses, and Google picks one to show. There is no duplicate content penalty — but there is a way to lose a whole site to one tag.
ReadCore Web Vitals, Explained Simply
"Make your site faster" turned into three specific numbers you can measure, with Google's published thresholds and the usual causes of a bad score.
ReadSitemaps and robots.txt
Two small files that decide what Google may look at and what it knows exists. They do opposite jobs, and one of them can remove your whole site from Google.
ReadTechnical SEO for Founders
A technical SEO guide for founders: the handful of fixes that actually move rankings (indexing, canonicals, speed, structure) and the things you can safely drop.
Read