If you have ever searched for a recipe and seen star ratings, cooking times or calorie counts sitting right there in the Google results before you have clicked anything, you have seen schema markup at work. It is a way of labelling the parts of your page so that search engines can read them as data.
What schema markup actually is
Schema markup is a small block of code added to a web page that describes what the content on that page means. A search engine reading ordinary HTML (the code that builds a web page) can tell that a paragraph contains numbers and words, but it cannot easily tell whether those numbers are a price, a phone number, or a star rating. Schema markup answers that question directly, using a shared vocabulary that Google, Bing and other search engines have agreed to recognise.
The vocabulary itself comes from a project called Schema.org, maintained jointly by the major search engines. It defines types such as LocalBusiness, Product, Review, Event and FAQPage, each with its own set of properties. A recipe page might mark up prep time and calories; a plumber's site might mark up opening hours and service area; an online shop might mark up price and stock availability.
Why it is worth adding to your site
Search engines can already read your page without schema markup, so nothing on your site stops working if you skip it. What you lose is the chance at what is called a rich result: an enhanced listing in the search results that might show a star rating, a price range, an FAQ dropdown or a business address. Rich results tend to take up more space on the results page and give the searcher more reason to click, which is why marking up the right content can improve your click-through rate (CTR), the proportion of people who see your listing and actually click it.
It matters more for some businesses than others. A local tradesperson with a Google Business Profile gains relatively little from LocalBusiness schema on their own site, because Google already pulls opening hours and reviews from the profile itself. A small e-commerce shop selling products with genuine customer reviews, or a site with a well-built FAQ section, tends to see the clearer benefit, because those are the page types most likely to trigger a visibly different result.
A worked example
Take a small business selling handmade furniture online, with a product page for an oak dining table priced at £450 and carrying eleven customer reviews averaging 4.6 out of 5. Without schema markup, that page shows up in search results as a plain title and a snippet of text pulled from the page. With Product and Review schema added correctly, the same listing can show the price, the star rating and the review count directly beneath the title, before anyone has clicked through. The page has not changed for a visitor who lands on it. What has changed is how much a searcher can see before deciding to visit.
How the SEO Schema Generator builds your markup
Writing schema markup by hand means learning the exact property names Schema.org expects and nesting them correctly, which is easy to get slightly wrong. The SEO Schema Generator takes the details you already know about your business or page, such as your business name, address, opening hours, or a list of FAQ questions and answers, and assembles them into the correct code structure for you.
The output is written in a format called JSON-LD, which is the format Google recommends and the one used in the vast majority of schema examples you will see elsewhere. JSON-LD sits inside a single script block that you paste into your page, which is part of why Google favours it: it is easier to add without accidentally breaking the rest of the page.
Because the generator only knows what you tell it, the code it produces is only as accurate as the information you enter. It cannot check that your opening hours are actually correct, or that the reviews you describe genuinely exist on the page, and Google can and does penalise markup that claims something the page itself does not show. Treat the generator as a way of formatting information correctly.
Adding the code to your site
Where to paste it
The JSON-LD block the generator produces needs to sit within the <head> section of the page it describes, or in some page builders, in whatever field is labelled 'custom code' or 'header scripts'. Most modern website platforms, including WordPress with a plugin such as Yoast or Rank Math, have a dedicated field for this, so you rarely need to edit the page's raw code directly. If you manage your site's HTML yourself, the block goes once per page, describing that specific page.
Testing it works
Once the code is on the page, it is worth checking that it parses correctly before assuming it will show anywhere in search results. Google's own Rich Results Test tool will read a live page and tell you which schema types it has found and whether they are eligible for a rich result. This step catches the two most common problems: a stray comma that breaks the whole block, or a property spelled slightly differently from what Schema.org expects.
Even with valid markup, showing a rich result in Google's actual search pages is never guaranteed. Google decides whether to display one, and the same correctly marked-up page can appear as a rich result for some searches and a plain listing for others. Adding schema markup is best understood as making your page eligible.
Common mistakes worth avoiding
- Marking up content that is not visible on the page. If your schema describes reviews, a price or an FAQ that a visitor cannot actually see when they land on the page, that counts as misleading markup and can lead to a manual penalty.
- Adding the same schema to every page. A block written for your homepage rarely fits a product page or a blog post, because the properties each type expects are different. Generate markup per page type.
- Leaving old markup in place after a page changes. If a product's price changes or an FAQ answer is rewritten, the schema needs updating alongside it, since a mismatch between the two is exactly what the mistake above describes.
- Assuming schema alone will improve rankings. Schema markup affects how a listing can be displayed. A page with excellent markup and thin content will not outrank a page with strong content and no markup at all.
When schema markup will not help
Schema markup has no effect on a page that has little to say in the first place. If your site is new, has few pages, or has not yet had time to be properly indexed, the priority is usually getting the basics in place first: a working robots.txt file so search engines know what to crawl, and a Google Search Console account (a free tool from Google that shows how your site appears in search) so you can see whether your pages are being indexed at all. Schema markup is a refinement for a site that already has visible, well-structured content, not a substitute for it.
For a broader view of where schema fits alongside the rest of your promotion work, the Website Promotion Playbook sets out the fuller sequence, and the glossary is worth keeping open in another tab if any of the terms here, JSON-LD, rich result, or Schema.org itself, need a second explanation.