...

Schema Markup for Beginners: A Plain-English Guide to Structured Data

Schema markup is a small block of code you add to a web page to tell search engines, in a standard language, exactly what the page is about. Instead of leaving Google to guess whether a number on your page is a price, a rating or a phone number, schema markup labels it clearly. That labelled code is a form of structured data, and Google describes structured data as a standardized format for providing information about a page and classifying the page content.

In plain English, your visible page is written for people, and your schema markup is a set of labels attached to that same page for machines. Readers never see the labels, but search engines can read them, understand the page with less guesswork, and sometimes show it in a richer format in search results.

What is schema markup, in plain English?

Three terms get mixed up, so it helps to separate them.

Structured data is the general idea: information in a standard, organized format that machines can read reliably.

Schema.org is the vocabulary used for that information. Schema.org describes itself as a collaborative, community activity that creates and maintains schemas for structured data on web pages, founded by Google, Microsoft, Yahoo and Yandex. Its vocabulary defines types, such as Article, Product or LocalBusiness, and the properties each type can have, such as a headline, price or opening hour.

Schema markup is what you add to your page: structured data written using the Schema.org vocabulary.

One limit matters from the start. Google says its own documentation, not Schema.org, is the definitive source for Google Search behaviour, because Schema.org contains many attributes Google does not require or use, a distinction made in Google’s introduction to structured data. Choose types from Google’s documentation first.

What does schema markup actually do?

First, schema markup helps Google understand the page. Google states that it uses structured data to understand the content of a page, and to gather information about the people, books and companies mentioned in the markup, as explained in its structured data introduction. On a recipe page, for example, the markup labels the ingredients, cooking time and calories instead of leaving them buried in a paragraph.

Second, it can make a page eligible for a rich result: a listing that goes beyond the standard title link and snippet, showing extra information such as a price, a rating, an event date or a breadcrumb trail. Google’s structured data gallery lists the features it supports.

Eligibility is not a guarantee. Google says plainly in its Article structured data documentation that it does not guarantee features consuming structured data will show up in search results. Valid markup opens the door; Google still decides whether to walk through it. Anyone selling schema as a guaranteed rich result or ranking boost is promising something Google itself does not promise.

Which format should you use, JSON-LD, Microdata or RDFa?

Google supports three formats: JSON-LD, Microdata and RDFa. Its guidance, in the introduction to structured data, is that all three are equally fine as long as the markup is valid and properly implemented for the feature you want.

That said, Google recommends JSON-LD in most cases, because it is generally the easiest format to implement and maintain. JSON-LD sits in a script block in the head or body of the page, separate from the visible text, so you can edit the labels without touching the page design. Microdata and RDFa instead add attributes inside the visible HTML itself.

What are the most useful schema types for beginners?

You do not need dozens of types. Most sites need a small, accurate set matching their main page types, each documented in Google’s structured data gallery.

Organization describes your company, including its logo, legal name, address and contact information, which can appear in knowledge panels and other visual elements.

Article, NewsArticle and BlogPosting describe articles and blog posts. Google’s Article documentation says this markup can help Google understand the page and show better title text, images and date information in results. Recommended properties include headline, author, date published and image.

BreadcrumbList describes where a page sits in your site hierarchy, for example Home, then Blog, then this article. Google’s breadcrumb documentation explains that a breadcrumb trail indicates the page’s position in the hierarchy and may help users explore a site.

LocalBusiness describes a business with a location or service area, covering hours, departments and address. Google’s local business documentation shows how it tells Google about hours and other details that can surface in Search and Maps. This type belongs with the wider work covered by our local SEO services, not as a replacement for it.

Product describes an item for sale. Google’s Product documentation explains that Product structured data means information such as price, availability, review ratings and shipping details can appear in richer ways in Search, Google Images and Google Lens. For the bigger picture, read our guide on how to optimize product pages for SEO, which covers Product schema in practice.

VideoObject, Event and Recipe are worth knowing if you publish those formats regularly, since each has its own Google documentation. Add them only when the page genuinely is a video, event or recipe page.

For larger ecommerce sites, markup also needs planning around categories, filters and variants. Our guide to faceted navigation SEO covers that context in depth.

What does schema markup look like? A simple example

Here is a short JSON-LD example for a blog article, simplified for learning, so treat it as an illustration of the shape, not copy and paste production code.

{
  "@context": "https://schema.org",
  "@type": "BlogPosting",
  "headline": "Schema Markup for Beginners",
  "datePublished": "2026-11-13",
  "author": {
    "@type": "Person",
    "name": "Muhammad Waqas Dilzak"
  }
}

Read it line by line: @context names the vocabulary, Schema.org. @type says what kind of thing this is, a BlogPosting. headline carries the article title, and datePublished states when it was first published. author names the writer, and the nested Person type makes clear the author is a person, not a company.

That nesting, one type inside another, is normal. Google’s Article guidance in its Article structured data documentation also recommends including every author shown on the page.

How do you add schema markup to a page?

Google gives the same basic workflow across its feature guides, including the local business guide. Adapted for a beginner:

  1. Choose the type that matches the page, and read that feature’s documentation before writing any code.
  2. Add the required properties first, then the recommended ones that apply. Google states that all required properties must be included for an object to be eligible for enhanced display, in its structured data introduction, and that fewer, complete and accurate recommended properties beat every possible property supplied badly.
  3. Follow the general guidelines below, especially the rule that markup must match visible content.
  4. Validate the code before you publish, using the tools in the next section.
  5. Deploy on a few pages first, check them, then roll out. Google recommends testing deployed pages with the URL Inspection tool before wider release.
  6. Keep Google informed of changes, for example by submitting a sitemap.

Where the code goes depends on how your site is built. On WordPress, in our experience, basic markup typically comes from your theme or SEO tooling, while page specific types often need a template level or per page addition. Our WordPress SEO work treats schema as part of a wider setup covering templates, indexing and structure. On other platforms the implementation point is your own templates, which is why schema usually sits inside a wider technical SEO review, not as a standalone task.

How do you test schema markup?

Testing is not optional, because a single missing bracket can make a whole block unreadable. The main tool is Google’s Rich Results Test, which Google describes as a way to test a publicly accessible page, or a code snippet, to see which rich results its structured data can generate. Run it while you build, and fix critical errors before publishing.

After publishing, keep monitoring. Google recommends the rich result status reports in Search Console after deployment, since templating or serving changes can break markup later. The URL Inspection tool shows how Google itself sees the page.

What changed with FAQ and HowTo schema?

This is where older guides mislead people, so here is the current position from Google’s own announcements.

In August 2023, Google announced that FAQ rich results would only be shown for well known, authoritative government and health websites, and that HowTo rich results would only be shown for desktop users. Google also said there is no need to proactively remove markup that is no longer used, since unused structured data does not cause problems for Search but also has no visible effects. Both points are in Google’s August 2023 announcement on HowTo and FAQ changes.

Google’s documentation updates page records what followed: in September 2023 it removed the HowTo documentation because the rich result was no longer shown on desktop or mobile, and in May 2026 the FAQ rich result feature was deprecated because it would no longer appear in Google Search starting May 7, 2026, with the FAQ documentation removed in June 2026.

So, two conclusions. First, do not add FAQPage or HowTo markup expecting a Google rich result, because that appearance is no longer on offer. Second, do not confuse markup with content. A clear, visible FAQ section and a clear step by step guide still help readers. Only the extra search display went away, which is why this article keeps a visible FAQ below.

Does schema markup help with AI search?

In Google’s own words, structured data is not required for generative AI search, and there is no special schema.org markup you need to add for it. Google’s guide to optimizing for generative AI features makes that point directly, while also saying to continue using structured data as part of your overall SEO strategy, because it helps with eligibility for rich results.

That is the balanced position we work to. Add accurate schema to help search engines understand your pages and keep you eligible for rich results. Write clear, useful content, because that is what AI search features draw on. Our AI search optimization service follows that order: content and technical clarity first, markup as supporting evidence, not a shortcut. Claims that a schema type guarantees AI citations go beyond what Google documents.

What are the most common schema mistakes?

Most schema problems are basic accuracy problems, and Google’s general structured data guidelines cover them directly:

  • Marking up content readers cannot see. If the markup describes it, the page must show it.
  • Marking up misleading content. Fake reviews and content unrelated to the page are named examples of what not to do. Misleading markup can lead to a manual action, which removes rich result eligibility, although Google notes it does not affect how the page ranks in web search.
  • Missing required properties. Items missing them are not eligible for rich results, so check the list for your type every time.
  • Blocking the page. Do not block structured data pages from Googlebot with robots.txt, a noindex tag or other access controls.
  • Using a vague type when a specific one exists. Google advises using the most specific applicable type and property names.
  • Letting the data go stale. Prices, availability and hours change. Markup that no longer matches the page misleads both Google and the searcher who trusts the result.

Where should a beginner start?

In our experience, this order works well for a typical small or mid sized site. Start with Organization and BreadcrumbList, since both are site wide and low risk. Add Article or BlogPosting to your blog template, LocalBusiness to location or contact pages, and Product to product pages if you sell online. Test each template in the Rich Results Test before rollout, then check the Search Console reports later to confirm Google is reading the markup as expected. Add further types only when a page type genuinely needs one. Schema rewards accuracy and restraint more than volume.

Conclusion

Schema markup is not magic, and it is not a ranking trick. It is a labelling system: a standard way to tell search engines what your page already says, so they can understand it with confidence and, where eligible, show it in a richer format. Learn the small set of types your site needs, write them in JSON-LD, keep them honest, test them, and keep them up to date.

At SWAF Digital, we approach schema as an SEO first agency. Structured data sits inside technical SEO, alongside crawlability, indexing, site structure and content quality, because that is where it does its real job. A beautifully labelled page that search engines cannot crawl, or that readers find useless, gains nothing. Get the foundations right, then let accurate markup explain them clearly.

FAQ

What is schema markup in simple terms?

Schema markup is code added to a page that labels what the content is, using a standard vocabulary, so search engines can understand it without guessing. It can state clearly that a page is an article, who wrote it, and when it was published.

Is schema markup the same as structured data?

Not exactly. Structured data is the general concept of information organized in a standard format for machines. Schema markup is structured data written using the Schema.org vocabulary.

Does schema markup improve rankings?

There is no documented guarantee that schema markup improves rankings, and Google does not present it that way. Its documented role is helping Google understand a page and making the page eligible for rich results, which are worthwhile but are not a ranking promise.

Which schema format should beginners use?

JSON-LD, the format Google recommends in most cases, because it is generally the easiest to implement and maintain. Microdata and RDFa are also supported, and Google says all three are equally fine when the markup is valid and properly implemented.

Do I still need FAQ schema?

You should not add FAQPage markup expecting a Google rich result, because Google restricted FAQ rich results in 2023 and retired the feature in 2026. A visible FAQ section is still useful for readers, so write good questions and answers for people, and treat any markup decision separately.

How do I check if my schema markup is working?

Test the page or code in the Rich Results Test and fix any critical errors it reports. After publishing, use the URL Inspection tool and the rich result status reports in Search Console to confirm Google is reading the markup and to catch later errors.

About the author: Muhammad Waqas Dilzak is co-founder of SWAF Digital and an SEO specialist with 10+ years of experience across SEO, AI search optimisation, and WordPress.