All capabilities · Search & AI visibility

Implement schema and entity markup

Describe a brand, its products and its answers in schema.org JSON-LD so search engines and AI assistants can identify the entity and quote it correctly; validate it and keep it in step with the page.

~12 focused hoursbeginner
Explore 4 tools for this project
Market relevance

Which roles ask for this — and how often

Share of job postings in India, per role, that name this capability.

What employers mean

You should be able to…

  1. Write schema.org JSON-LD for Organization, Product, Article and BreadcrumbList that matches what the page visibly says
  2. Build an entity record for the brand: name, logo, url, contact details and sameAs links to its official profiles
  3. Validate markup with the Rich Results Test and Schema Markup Validator and fix every error before release
  4. Audit structured data across a whole site with a crawler and find templates where it is missing or broken
  5. Monitor Search Console's structured data reports and fix the errors and warnings they raise
  6. Keep prices, availability and ratings in markup in step with the page so the data does not go stale or mislead
  7. Know which schema types Google supports for rich results and which are only descriptive

Needs first: Run technical and on-page SEO for a website

Learn — free, link-checked

The few resources that matter

Tools for practice

Choose a tool for the job

Start with one tool for each part of your project. You don’t need to learn them all.

Go to the practice brief

4 tools to explore

Google Rich Results Test

Test

Paste a URL or code to see which rich results its structured data is eligible for and fix the errors Google reports.

Schema Markup Validator

Test

Check any schema.org markup — including types Google does not show as rich results — against the vocabulary itself.

Google Search Console

Monitor · Test

Verify a site you own, inspect why a URL is or is not indexed, and track impressions, clicks and structured data issues from Google Search.

Screaming Frog SEO Spider

Test · Data

Crawl a website like a search engine and export broken links, redirects, titles, canonicals and structured data issues for an audit.

Free version

The free download crawls up to 500 URLs per crawl; a paid licence removes the limit.

Practice

Schema.org JSON-LD pack for a small business website, validated and monitored

Build a small multi-page site on GitHub Pages for your own or an imagined Indian small business (a home-baker, a D2C skincare label, a coaching centre): home, about, two product or service pages and an article. Write JSON-LD by hand for Organization (with sameAs and logo), Product with Offer, Article and BreadcrumbList, keeping every value identical to the visible page. Validate each page in the Rich Results Test and the Schema Markup Validator, crawl the site to confirm every template carries its markup, then verify the site in Search Console and record what its structured data reports show.

Start from

Your own five-page GitHub Pages site for a real or imagined small business — you write the copy, prices and product details

Milestones
  1. Publish the five-page site with visible business details, prices and an article · ~2h
  2. Write JSON-LD for Organization, Product with Offer, Article and BreadcrumbList on the right pages · ~3.5h
  3. Validate every page in the Rich Results Test and Schema Markup Validator, fix errors and plant one mismatch to show you can catch it · ~3h
  4. Crawl the site to confirm markup on each template, verify it in Search Console and write a one-page markup map · ~2.25h
Done when
  • Every page has JSON-LD that validates with zero errors in both the Rich Results Test and the Schema Markup Validator
  • Every marked-up value (name, price, availability, author, date) matches the visible page text
  • The Organization entity includes logo, url and at least two sameAs links to profiles you control
  • A markup map lists each page, its schema types, the rich result it is eligible for (or 'descriptive only') and its validation status
Prove it

Evidence a recruiter can check

  • Rich Results Test and Schema Markup Validator screenshots for each page showing zero errors
  • The JSON-LD source for each template beside the visible page section it describes
  • A before/after pair showing the mismatch you planted (for example a stale price) caught by validation and fixed
  • The markup map: page, schema types, rich-result eligibility and Search Console status
Signal it

Hand-wrote and validated schema.org JSON-LD (Organization, Product, Article, Breadcrumb) for a five-page business site — zero validator errors and every value kept in step with the visible page.

Interview

Questions you'll get asked

  1. Why does Google prefer JSON-LD over microdata, and when would you still see microdata on a site?
  2. What goes into Organization markup for a brand, and what is sameAs for?
  3. The Rich Results Test passes but no rich result appears in Search. What are the possible reasons?
  4. Can you mark up reviews or FAQs that are not visible on the page? Why not?
  5. How would you add Product markup to 5,000 product pages on Shopify without hand-editing each one?
  6. What is the difference between a structured data error and a warning, and which do you fix first?
  7. How does entity markup help AI assistants identify a brand correctly?