Schema markup is code that tells search engines and AI assistants exactly what a page is about: a business, a product, an article, an event or a recipe. This guide explains structured data in plain terms, shows why Google prefers JSON-LD, covers the types that still earn rich results in 2026, and walks you through testing with the Rich Results Test, with a ready example of LocalBusiness schema for a small business.
Quick answer: Schema markup is structured data, written with the schema.org vocabulary, that you add to a page so machines can read its facts. Google recommends the JSON-LD format. As of November 2026, Google still supports rich results for types such as Article, Breadcrumb, Local business, Product, Review snippet, Event, Recipe, Video and Organization, but it stopped showing FAQ rich results on 7 May 2026. Markup never guarantees a rich result; it only makes a page eligible.
What is schema markup?
Schema markup is a shared vocabulary, published at schema.org, for describing things on the web. Search engines founded the project so that everyone uses the same names for the same facts. For example, "telephone", "openingHours" and "priceRange" mean the same thing on every site that uses them.
Without markup, a search engine has to guess that "08:00 to 17:00" on your contact page means opening hours. With schema markup, you state it directly. As a result, your facts are easier to trust, show and reuse.

Structured data and rich results: what you can still get
Structured data is the general term; schema markup is the most common way to write it. When Google understands your structured data, it may show a rich result, such as star ratings, prices, event dates or a breadcrumb trail.
However, the list of rich results changes. Google deprecated HowTo rich results in 2023, and its Search Central changelog says FAQ rich results stopped appearing in Google Search on 7 May 2026. The FAQ documentation was removed on 15 June 2026. FAQPage is still a valid schema.org type, so existing markup does no harm, but it no longer earns that special result.
Here are useful types for small businesses, based on Google's search gallery as of November 2026:
| Type | Good for | Possible result |
|---|---|---|
| Organization | Any business site | Logo and company details in knowledge panels |
| LocalBusiness | Shops, hotels, clinics, restaurants | Business details for local searches |
| Article | Blog posts and news | Better title, image and date display |
| BreadcrumbList | Sites with categories | A breadcrumb path instead of a raw URL |
| Product and Review snippet | Online shops | Price, stock and rating details |
| Event | Workshops, concerts, festivals | Dates and venue in event results |
| VideoObject | Pages with videos | Video thumbnail and key moments |
So, pick the types that match what is truly on the page. Marking up content that visitors cannot see breaks Google's guidelines and can lead to a manual action.
Why JSON-LD is the best format
There are three ways to write schema markup: JSON-LD, Microdata and RDFa. Google says JSON-LD is the format it recommends, because it is the easiest to add and maintain at scale. JSON-LD sits in a single script block, so you do not need to wrap every piece of visible HTML in extra attributes.
In addition, JSON-LD is easy to generate. Most SEO plugins for WordPress output it automatically for articles, breadcrumbs and your organization. Then you only add the extra types your pages need.
LocalBusiness schema example
LocalBusiness schema is the most valuable type for a business that serves customers in one area. Here is a short example you can adapt. Replace every value with your real details, and only include facts that also appear on the page.
{"@context": "https://schema.org", "@type": "LocalBusiness", "name": "Example Coffee House", "url": "https://example.com/", "telephone": "+66-2-000-0000", "address": {"@type": "PostalAddress", "streetAddress": "1 Example Road", "addressLocality": "Krabi", "postalCode": "81000", "addressCountry": "TH"}, "openingHours": "Mo-Su 08:00-17:00", "priceRange": "$$"}
On a real site, place this inside a script tag with the type application/ld+json in the page head or body. Also, pick the most specific subtype you can, such as Restaurant, Hotel or Dentist, because schema.org offers hundreds of them.
Finally, keep the same name, address and phone number everywhere. Your schema, your contact page and your Google Business Profile should match. Our Google Business Profile guide shows how to set that up.
How to add schema markup to a WordPress site
You have three practical options, and most sites combine the first two:
- Use your SEO plugin. Yoast SEO, Rank Math and similar plugins add Organization, WebSite, Article and Breadcrumb markup without code.
- Add custom JSON-LD for special pages. For example, a plugin that inserts code into the head, or a block that outputs a script, works well for LocalBusiness or Event markup.
- Edit the theme. Developers can print JSON-LD from a child theme, but this needs care during theme updates.
Whichever route you choose, avoid two plugins that both output the same type. Duplicate or conflicting markup makes your data harder to trust. If you are still building the site, our guide on how to build a WordPress website covers the SEO plugin setup.
How to test with the Rich Results Test
Always test before and after you publish. Google names three tools for this job:
- Rich Results Test. Paste a URL or a code snippet to see which rich results the page can earn and which fields are missing.
- Rich result status reports in Search Console. Watch these after launch, because they show errors across many pages.
- URL Inspection tool. Confirm that Google has crawled the live page and found the markup.
In addition, the Schema Markup Validator at validator.schema.org checks any schema.org type, including ones Google does not use for rich results. That is useful because other search engines and AI tools read schema too.
When the Rich Results Test shows a warning, it usually means an optional field is missing. Errors, on the other hand, can block the rich result, so fix those first.
Schema markup, AI search and AEO
Clear structured data also helps answer engines. Tools that build AI answers need facts they can trust, such as your opening hours, prices and location. Because schema markup states those facts plainly, it supports Answer Engine Optimization and Generative Engine Optimization. Read what is AEO and what is GEO to see how markup fits into those strategies.
Still, markup is not magic. The page itself must answer the question well, load fast and be easy to read. Our Core Web Vitals guide covers the speed side.
Need help with schema markup?
Develop Marketing helps businesses with WordPress websites, SEO, AEO and GEO, social media, AI content and advertising, including structured data for local businesses and hotels. See our services page (in Thai), our hotel direct booking roadmap (in Thai), or contact us.
Frequently asked questions
Google does not describe schema markup as a direct ranking factor. It helps Google understand a page and can make it eligible for rich results, which may improve how the listing looks.
Google stopped showing FAQ rich results on 7 May 2026, according to its Search Central changelog. FAQPage is still valid schema.org markup, so it does no harm, but it no longer creates that rich result in Google.
Structured data is the general idea of labelling page facts in a machine-readable way. Schema markup is structured data written with the schema.org vocabulary, which is what Google and most search engines use.
Use JSON-LD. Google recommends it because it sits in one script block and is the easiest to add and maintain.
No. Markup only makes a page eligible. Google decides whether to show a rich result, and the markup must follow its guidelines and match visible content.
Final thoughts
Schema markup is one of the cheapest ways to make your facts clear to search engines and AI tools. Start with Organization and LocalBusiness, add Article, Breadcrumb or Product where they fit, write everything in JSON-LD, and test each template with the Rich Results Test. Keep the markup honest and in sync with the page, and review Google's supported list every few months, because it keeps changing.










