Schema markup is a block of code that labels what's on a page: this is an article, this is its author, this is the date it was published. Google reads it to understand the page and, for some content types, to show a richer search listing.
It won't get you star ratings just because you added it, and it doesn't push a page up the rankings. What it does is make a page eligible for certain rich results. Google decides whether to show them, and its structured data guidelines say plainly that correct markup is no guarantee.
For a small content site the useful work is short: Article markup on posts, breadcrumbs, and an Organization or Person block on your home or about page. Product markup only belongs on pages about a single product. The rest of this guide covers what each one does, how to add it, and the star-rating rules that get people in trouble.
What schema markup can and can't do
A search engine can read your text, but it has to guess what a given number or name means. Structured data removes the guess. You use the shared vocabulary from schema.org, usually written as JSON-LD, to state it outright.
In return, Google may use that information in the listing: a breadcrumb trail in place of a raw URL, a correct date and author on an article, price and availability on a product.
What it can't do:
- Raise your rankings on its own. Google's documentation describes structured data in terms of understanding a page and eligibility for rich results. It doesn't describe it as a ranking boost, and I wouldn't add markup expecting one.
- Force a rich result. Valid markup makes you a candidate. Google still chooses.
- Describe things that aren't on the page. Google's rules say not to mark up content readers can't see.
Which types are worth adding on a small site
| Type | Where it goes | What Google may do with it |
|---|---|---|
| Article | Every post | Better title, image and date in results |
| BreadcrumbList | Every post and category page | Breadcrumb trail on desktop results |
| Organization or Person | Home or about page | Helps Google identify who runs the site |
| Product | Pages about one product | Price, availability, review details |
Article is the one to start with. Google lists no required properties for it, only recommended ones: headline, image, publish date, modified date, and author. Give the author a name and a URL that points to a page about them, and keep job titles out of the name field.
BreadcrumbList describes where a page sits in your site. It works best when the trail matches a real structure, which is one more reason to sort out your internal links and categories first. Google's docs currently list this feature as available on desktop.
Organization belongs on one page, usually the home page. Name, URL, logo, and links to your social profiles are enough for most blogs. If the site is really one person, describe yourself as the author with a Person block and link it to your about page.
Product is for a page focused on a single product. Google requires a name plus at least one of an offer, a review, or an aggregate rating. If you sell your own ebook or course, mark up the name and price. If you publish a hands-on review of someone else's product, the same docs cover editorial review pages, including pros and cons. A roundup of ten products is not a Product page. If you run a business with a physical location, LocalBusiness markup matters too, and it fits into the wider work of showing up in local results.
What about FAQ and HowTo markup?
Skip both. Google removed HowTo rich results in 2023. It restricted FAQ rich results to well-known government and health sites that same year, then retired the feature completely: Google's documentation changelog says FAQ rich results stopped appearing in search in May 2026, and the FAQ documentation was removed in June 2026.
A lot of older tutorials still tell you to add FAQPage markup for an expandable listing. That listing no longer exists. Leaving old FAQ markup in place does no harm, but there's no reason to add it now. An FAQ section can still help readers. Write it for them.