Schema markup will not move you from position eight to position three. What it does is make your result look better, make you eligible for features other pages cannot get, and give AI systems a structured version of what your page says. That is worth doing, selectively.
What schema markup does
Schema, added as JSON-LD, labels the parts of your page: this is the author, this is the price, this is the rating, this is a step. Search engines use it to show rich results, and language models use it as a clean signal of what the page and its entities are.
Which types are worth it
| Type | What it can earn | Worth it for |
|---|---|---|
Organization / Person | Knowledge panel, entity links | Every site, once, sitewide |
Article | Author, date and headline in results and AI answers | Any blog or news content |
BreadcrumbList | Breadcrumb trail in the result | Any site with a hierarchy |
Product + AggregateRating | Price, stock and stars | E-commerce, with real reviews only |
FAQPage | Expandable Q&A, now limited | Sparingly, genuine FAQs only |
LocalBusiness | Hours, area, contact in local results | Any business with a location |
VideoObject | Video thumbnail and key moments | Pages where video is the main content |
Warning: only mark up content that is actually visible on the page. Schema for things a user cannot see is a structured-data manual-action risk.
Schema checklist
- Organization or Person schema sitewide, with sameAs links
- Article schema on every post, with a real author
- Breadcrumb schema matching your visible navigation
- Product and rating schema only where real reviews exist
- One consistent @id per entity, cross-referenced in a @graph
- Validated with the Rich Results Test, monitored in Search Console
By the numbers
HM Towhidul Islam · Senior Technical SEO Lead
Use one @id per entity and reference it everywhere in a @graph. Most sites emit five disconnected blocks per page. Connecting them is what turns markup into an entity signal.
Short case study
A recipe site
Recipe schema was present but incomplete: no ratings, no cook times, no video object on pages with video. We completed the markup, fixed a batch of validation errors, and connected the Organization and Person nodes.
Rich result impressions rose 60% and average click-through on recipe pages improved from 3.1% to 4.4%.