Schema markup, explained without the code

Schema markup is a block of labelling that sits in your page’s code. Visitors never see it. Its only job is to tell a machine what kind of thing the page describes.

Without it, a search engine reads your page and infers. It’s usually right, and sometimes it isn’t. With it, there’s nothing to infer.

What it actually changes

Two things. The first is rich results, the extra detail that sometimes appears under a search listing. Star ratings, FAQ dropdowns, prices, opening hours. Those come from schema. You can’t get them without it.

The second matters more now. AI assistants and answer engines lean on structured data because it removes ambiguity. A page marked up as a Product with a specific SKU and specification is far easier to quote correctly than a page of unlabelled text.

The types worth having

• Organization. Your company name, logo, address, contact details. Goes on every page. This is the baseline.
• LocalBusiness. If you have a physical location buyers visit. Adds opening hours and geography.
• Product. One per product page. Name, description, specification, brand. The single highest value type for a manufacturer.
• FAQPage. For any page with genuine questions and answers. This one can produce visible dropdowns in search results.
• BreadcrumbList. Shows the path to the page. Small win, cheap to add.
• Article. For anything written. Author, date published, headline.

How to check what you have

Google has a free tool called the Rich Results Test. Paste in a page URL and it tells you what structured data it found and whether anything is broken. Schema.org also has a validator that’s stricter and more detailed.

Run it on your home page and one product page. Most dated sites come back with nothing at all, which is useful to know.

The mistake worth avoiding

Don’t mark up things that aren’t on the page. This falls under Google’s spam policies. Adding review schema for reviews that don’t exist, or FAQ schema for questions nobody asked, is a manual action waiting to happen. Google does check this and the penalty is losing rich results entirely.

The rule is simple. Schema describes what’s genuinely on the page. If you want FAQ markup, write real answers to real questions first.

Who does this work

It’s a developer job, and it’s a small one. Adding schema to an existing site is usually a day or two of work for a decent developer, less if the site is already well structured. It’s not a monthly retainer item and anybody charging you one for it is overcharging.

If your site is being rebuilt, it should be in the build from the start. Ask the vendor which schema types they’re implementing. A blank look is informative.

Written by Sameer Gaikwad, founder of Buildgin. Thirty three years in electrical power systems across global MNCs, now applying the same condition monitoring habit to websites.