Schema Markup for Beginners: What It Is and Which Types You Need

Your page might say "Open Monday to Saturday, 10 to 7" and "4.6 stars from 120 reviews". A person understands that instantly. A search engine sees words and has to guess which numbers are opening hours and which are a rating. Schema markup removes the guessing by labelling the facts in a format machines read directly.

This guide explains what schema is, which types are worth adding, what changed with FAQ schema, and how to test your markup. For the two types with the biggest payoff for businesses, local businesses and products, see the business and product schema guide.

What schema markup is

Schema is a shared vocabulary, published at schema.org and supported by Google, Bing and others. It has types, such as LocalBusiness, Product, Article and FAQPage, and properties, such as name, address, price and openingHours.

You add it to a page as a small block of code that visitors never see. The format Google recommends is JSON-LD:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "LocalBusiness",
  "name": "Shree Textiles",
  "telephone": "+91-98765-43210",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "Ring Road Textile Market",
    "addressLocality": "Surat",
    "addressCountry": "IN"
  },
  "openingHours": "Mo-Sa 10:00-19:00"
}
</script>

It's just labelled facts: this is a local business, and here are its name, phone number, address and hours.

Why it's worth adding

• Rich results. Some types change how your result looks. Products can show price and stock, articles can show a larger image, and breadcrumbs replace the plain URL with a readable path.
• Clearer understanding. Schema confirms which business, product or person a page is about. That helps search engines connect your website, your Google Business Profile and mentions of you elsewhere.
• AI and new search features. AI assistants and newer search features rely on structured facts, and clean facts are easier for any system to use.

Schema isn't a direct ranking boost, and valid markup doesn't guarantee a rich result, because Google decides when to show them. But it removes ambiguity, and that rarely hurts.

The types most sites need

What Rankdesk uses on its own pages

You can see real examples by viewing the source of any page here, or by running one through Google's Rich Results Test:

• The home page has Organization and WebSite, which state the site's name, web address and logo.
• Each tool page has WebApplication (a free tool, with its name and description), BreadcrumbList, and FAQPage for the questions shown at the bottom of the page.
• Each guide has BlogPosting with the headline, cover image, word count, the date first published and the date last updated, and author as a Person linked to my author page. The breadcrumb trail is Home, Blog, category, guide.

All of it is generated from the same data that renders the page, so the markup and what you see can never disagree. That's the safest way to add schema on any site.

FAQ schema after 2023

For a few years, FAQ schema was the easiest way to make a search result bigger. Add questions in structured data and Google might show them as drop-downs under your link. Many sites added FAQ markup to every page for that reason.

In August 2023 Google limited FAQ rich results to well-known, authoritative government and health websites. For everyone else, the drop-downs no longer appear in normal results, even with valid markup. Google also stopped showing HowTo rich results.

So is FAQ schema useless now?

• It doesn't hurt. Google said there's no need to remove existing markup.
• It labels content clearly for other search engines and AI tools.
• It was never a ranking boost.

The real value was always the visible FAQ section, and that hasn't changed. A good FAQ on a service or product page answers the questions that stop people buying (price, time, warranty, delivery), matches the questions people actually search, can be picked for "People also ask" and featured snippets without any markup, and cuts down repeat calls.

Add FAQ schema when the page has a real FAQ visible to visitors, the answers are yours (questions with several user answers suit QAPage instead), and your plugin or a generator makes it easy. Skip it if you'd be adding questions only for the markup, or if more valuable markup like LocalBusiness or Product isn't done yet.

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [{
    "@type": "Question",
    "name": "How long does terrace waterproofing last?",
    "acceptedAnswer": {
      "@type": "Answer",
      "text": "A properly applied membrane system usually lasts 8 to 10 years. We give a 5-year written warranty."
    }
  }]
}

Write FAQ answers with the direct answer first, in two to four sentences, using the words customers use on calls and WhatsApp. Update them when prices or policies change.

The rules that keep you safe

1. Mark up only what's visible. If the schema says 4.8 stars, the page must show that rating. Hidden or invented data breaks Google's guidelines and can lead to a manual penalty.
2. Be accurate. Prices, hours and stock should match the page and stay current.
3. Use the most specific type. Dentist or ClothingStore says more than LocalBusiness, and they accept all the same properties.
4. One main thing per page. A product page is about one product.
5. No advertising in FAQs. "Why are we the best?" followed by a sales pitch isn't a real question.
6. Avoid duplicates. Themes, plugins and apps often add their own schema. Check before adding more.

How to add it

• WordPress: Yoast and Rank Math add Organization, Article and Breadcrumb schema automatically. WooCommerce adds Product schema.
• Shopify: most themes include Product schema. Check it before installing an app that adds a second copy.
• Hand-coded sites: paste the JSON-LD block into the page, usually just before </head> or </body>. Better still, generate it from the same data as the page.

Test before and after

1. Google's Rich Results Test shows which rich results a page qualifies for and any errors.
2. The Schema Markup Validator (validator.schema.org) checks every type, including those Google doesn't show as rich results.
3. Search Console reports schema problems across the whole site under its Enhancements section, after Google recrawls your pages.

Build yours

The Rankdesk schema generator builds valid JSON-LD for local businesses, organizations, products, FAQ pages and articles. Enter your website and it fills the fields from your existing pages, including any schema you already have, so you only check and copy. The SEO audit shows which schema types a page already has.