# What Is Schema Markup? 2026 Guide to Types That Still Work **URL:** https://mettevo.com/blog/article/what-is-schema-markup **Published:** 2026-09-11 **Updated:** 2026-09-11 **Author:** Oleg Silin **Category:** Blog | Mettevo > Learn what schema markup is, how structured data works, and why it matters for SEO. Discover how schema markup can help search engines understand your website content. ![what is schema markup](https://stage.mettevo.com/wp-content/uploads/2026/09/Team_analyzing_website_code_on_20260911100908.jpeg) --- Schema markup is structured data, usually written in JSON-LD (JavaScript Object Notation for Linked Data), that you add to a page's HTML so search engines can identify entities such as products, events, or organizations. It does not change rankings directly, but it can unlock rich results such as star ratings, prices, and visual elements in Google Search. - Schema markup is JSON-LD code added to a page that labels entities like products, events, and articles so search engines can parse them directly. - Google discontinued FAQ (Frequently Asked Questions) rich results entirely on May 7, 2026, roughly two years and eight months after restricting them to government and health sites in September 2023. - HowTo rich results disappeared from Search on both desktop and mobile in that same September 2023 update. - Google's structured data gallery still lists 25 active feature types, including Product, Review snippet, Event, and JobPosting. - Valid markup does not guarantee a rich result. Check it with the Rich Results Test, the Schema.org Validator, and Search Console's Rich result report. ## **What Is Schema Markup, in Plain Terms?** Schema markup translates page content into a vocabulary search engines can parse without guessing. A blog post is just text to a crawler until markup declares it an Article with a headline, an author, and a publish date. A product page becomes a Product with a price and an availability status instead of a wall of unlabeled paragraphs. The vocabulary comes from [Schema.org](https://schema.org/docs/gs.html), which describes itself as "a collection of shared vocabularies webmasters can use to mark up their pages in ways that can be understood by the major search engines." Those search engines include Google, Microsoft, Yandex, and Yahoo. The vocabulary covers hundreds of types, from Recipe to JobPosting to LocalBusiness, far more than any single site will ever need. Markup does not add new content to a page. It labels content that is already visible, in a format a machine can read directly instead of inferring meaning from layout and phrasing. ## **How Schema.org and JSON-LD Work Together** Schema.org and JSON-LD solve two different problems. Schema.org is the vocabulary, defining what a Product or Event is and which properties each type can carry, such as price, startDate, or aggregateRating. JSON-LD, Microdata, and RDFa are the three syntaxes available to write that vocabulary into HTML. Google treats all three formats as valid, but its [own documentation](https://developers.google.com/search/docs/appearance/structured-data/intro-structured-data) recommends one by default, JSON-LD. The stated reason is practical rather than technical. JSON-LD is "the easiest solution for website owners to implement and maintain at scale," according to Google's own guidance. For a closer look at the Microdata syntax specifically, and where it still fits inline in HTML, see our Schema.org microdata guide. In practice, JSON-LD is a single script block placed in a page's head or body, separate from the visible HTML. That separation is why most CMS (content management system) platforms and tag managers can inject it without touching page templates. A minimal example for this article looks like this: {   "@context": "https://schema.org",   "@type": "Article",   "headline": "What Is Schema Markup?",   "author": {     "@type": "Person",     "name": "Oleg Silin"   },   "publisher": {     "@type": "Organization",     "name": "Mettevo"   },   "datePublished": "2026-08-27" } Every property in that block maps to a schema.org type. Article, Person, and Organization all exist in the vocabulary with their own defined property lists. Nothing here is Google-specific. The same JSON-LD would validate against schema.org's own rules regardless of which search engine reads it. ## **Why Is Schema Important in SEO?** Schema markup matters for search engine optimization (SEO) mainly because search engines use it to decide whether a page qualifies for a rich result. That eligibility check happens automatically, based on which entity types and properties a page declares. Adoption keeps growing regardless. JSON-LD structured data now appears on 41% of pages, up from 34% in 2022, according to the [2024 Web Almanac from HTTP Archive](https://almanac.httparchive.org/en/2024/structured-data). That growth happened while Google was cutting the number of rich result types available, which means sites still investing in schema are competing for a smaller, more selective set of opportunities. Rich results themselves do not move rankings. Google's [general structured data guidelines](https://developers.google.com/search/docs/appearance/structured-data/sd-policies) are explicit that structured data is a discovery signal, not a ranking one. As the documentation states, "Google does not guarantee that your structured data will show up in search results, even if your page is marked up correctly according to the Rich Results Test." What changes is how an eligible result looks on the page, through elements such as star ratings, prices, or event details, not where it ranks. For the fuller picture of where schema fits into local search, voice results, and overall [SEO performance](https://mettevo.com/seo), see our guide to structured data's role in SEO success. ## **Which Schema Types Still Earn Rich Results in 2026?** Most explanations of schema markup treat every type as equally useful. They are not, and the gap widened considerably over the past three years. Google restricted FAQ rich results on September 14, 2023, updating its [FAQ rich result documentation](https://developers.google.com/search/docs/appearance/structured-data/faqpage) to state the feature "is only shown for well-known, authoritative government and health websites." That excluded nearly every business blog and marketing site overnight. The restriction turned out to be a transition, not an endpoint. Google's [Search Central changelog](https://developers.google.com/search/updates) confirms FAQ rich results stopped appearing in Search entirely on May 7, 2026. In June 2026, Google also dropped the FAQ search appearance filter, the FAQ rich result report in Search Console, and Rich Results Test support for the feature. On June 15, 2026, a separate changelog entry titled "Removing documentation for the FAQ rich result feature" confirms Google removed the FAQ documentation page itself. Its URL now redirects to the general changelog. The documentation redirect is about Google's own pages, not about the schema.org vocabulary. FAQPage remains a valid Schema.org type, and the markup itself still causes no validation errors. It simply produces no visible result in Google Search. As of today, FAQ markup earns no rich result for anyone, government and health sites included. HowTo rich results went the same way earlier. The same September 14, 2023 changelog update states plainly that the HowTo rich result "is no longer shown in search results, on both desktop and mobile devices." That leaves a real question. Which types are still worth the effort today? Google's [structured data gallery](https://developers.google.com/search/docs/appearance/structured-data/search-gallery) lists 25 active feature types. FAQ and How-to are not among them. The table below covers the types most business and publishing sites can realistically use. Type What it unlocks Best fit Product Price, availability, and rating badges in Search and Shopping Ecommerce, marketplaces Review snippet Star ratings next to a listing Products, services, local businesses Event Date, location, and ticket details Venues, courses, webinars JobPosting Job title, salary range, and location in Google for Jobs Recruiting, HR pages LocalBusiness Address, hours, and map data in local results Any business with a physical location Organization Logo and brand facts in the Knowledge Panel Every company site VideoObject Thumbnail and duration in video results Sites hosting original video BreadcrumbList A breadcrumb trail instead of a raw URL in the snippet Any multi-level site Article Headline, author, and date on news and blog content Blogs, editorial sites Q&A (QAPage) Question and top answer for community Q&A threads Forums, support communities Two of these deserve a caution. Review snippet has a sharp restriction. If a business marks up reviews of itself, such as on a testimonials page, Google's [review snippet guidelines](https://developers.google.com/search/docs/appearance/structured-data/review-snippet) make that ineligible outright. In Google's own words, "if the entity that's being reviewed controls the reviews about itself, their pages that use LocalBusiness or any other type of Organization structured data are ineligible for star review feature." Third-party review platforms are unaffected. Q&A markup carries a restriction of its own, and it is often confused with the FAQ format that just disappeared. Google's [Q&A structured data guidelines](https://developers.google.com/search/docs/appearance/structured-data/qapage) require that "users must be able to submit answers to the question," and they say plainly, "Don't use QAPage markup for FAQ pages or pages where there are multiple questions per page." A static FAQ accordion written by your own team does not qualify. ## **How to Implement Schema Markup: A 5-Step Process** Implementing schema markup follows the same five steps regardless of which type you choose. 1. **Pick the type that matches the page**, not the type you wish applied. A services page is Service or LocalBusiness, not Product. A blog post is Article, not a generic WebPage. 2. **Write it in JSON-LD.** Start from the schema.org type definition for the type you picked, and include every required property plus the recommended ones that apply to your content. 3. **Place the script on the page**, either directly in the template's head, through a plugin that generates JSON-LD automatically, or through a tag manager if you cannot edit templates directly. 4. **Test the exact URL before it goes live**, using the Rich Results Test or the Schema.org Validator, both covered below. 5. **Re-check after any template or CMS update.** Markup breaks silently when a theme update changes how a plugin renders the page head, and nothing in the visible content shows that it happened. Schema markup is one line item inside a larger technical audit, not a standalone project. If you are auditing a site for the first time, our technical SEO audit checklist for 2026 places structured data validation alongside crawlability, Core Web Vitals, and the other checks that determine whether a page can rank at all. ## **How Do I Know If My Website Has Schema Markup?** Three tools answer this without guesswork, and each checks something slightly different. 1. [**Google's Rich Results Test**](https://search.google.com/test/rich-results) takes a live URL or a raw HTML snippet and shows exactly which rich result types Google's parser detects, plus any errors. It is the fastest way to check a single page. 2. [**Schema.org's own Validator**](https://validator.schema.org/) checks markup against the schema.org vocabulary itself rather than against any one search engine's eligibility rules. Use it when the Rich Results Test says a type is not supported by Google but you still want to confirm the JSON-LD itself is valid. 3. [**Search Console's Rich result report**](https://support.google.com/webmasters/answer/7552505) works at the site level instead of one URL at a time. It shows a sample of detected items and tracks how many are valid versus invalid over time. That catches what a single-page test misses. A template change can break markup across hundreds of pages at once without any visible warning on the page itself. None of the three confirms that a rich result will actually appear. Valid markup is necessary but not sufficient. Google decides what to display "depending on many variables, including search history, location, and device type," according to its own structured data guidelines. ## **What the Top-Ranking Pages for "What Is Schema Markup" Actually Look Like** Advice about ideal length or structure is easy to state and hard to verify. We pulled the top 10 US Google results for "what is schema markup" through the Ahrefs API on August 27, 2026, then loaded each page to count word count, H2 headings, and whether FAQPage schema was present in its own JSON-LD. Five of the ten results could actually be measured. The sample excludes Reddit, YouTube, and npm listings that ranked in the top 10, since none of those are comparable article pages. Pages that returned a 403 error or timed out during the fetch were dropped rather than estimated. A few of the remaining URLs point to a documentation section rather than a standalone article, so the word counts below are a lower-bound estimate, not an exact measurement of full article length. Across those five pages, the median length was 3,089 words, ranging from 405 to 7,118 words, a spread of more than 17 times between the shortest and the longest page. The median H2 count was 8. None of the five pages used FAQPage schema on themselves, the same feature Google stopped rewarding in Search. We are not claiming that absence caused their ranking; we simply did not find a single page in the sample using it. That range makes "match the average competitor's word count" useless as a target. What the five pages share is not length. It is a working code example, at least one comparison table, and a direct answer to the query within the first screen, the same structure this page follows. ## **Common Schema Markup Mistakes to Avoid** - **Marking up content that is not on the page.** Google's guidelines are direct: "Don't mark up content that is not visible to readers of the page." A price in your JSON-LD that does not match what a visitor sees is a policy violation, not a technical detail. - **Publishing FAQ or HowTo markup and expecting a rich result.** Both stopped working. The code is still valid JSON-LD; it just earns nothing in Search anymore. - **Marking up self-published testimonials as reviews.** Google excludes LocalBusiness and Organization pages from the star review feature when the business controls the reviews shown on its own site. - **Skipping required properties.** A Product without price and availability, or an Event without a date, fails validation even when the type declaration itself is correct. - **Deploying once and never checking again.** Template updates and CMS migrations break JSON-LD silently. Only the Rich Results Test or the Search Console Rich result report will catch it after the fact. ## **FAQ** ### **What is a schema markup example?** A minimal example is a Product page marked up in JSON-LD with name, image, offers (containing price and priceCurrency), and aggregateRating. That markup lets a search result show a price and a star rating next to the listing instead of a plain link. The same pattern applies to any type. Declare the entity, then fill in its defined properties. ### **What is a schema with an example?** In schema.org's vocabulary, a schema is a type such as Event, together with the properties it can carry, including name, startDate, location, and offers for ticket price. For a conference page, that means declaring Event in JSON-LD and filling those properties with the real name, date, venue, and price. ### **Does schema markup directly improve rankings?** No. Schema markup is a discovery and presentation signal, not a ranking factor. Google states plainly that valid structured data does not guarantee a rich result will appear. What it can influence is click-through rate, through star ratings, prices, or other visual elements shown directly in the result, not position in search results. ### **Is schema markup still worth doing in 2026?** Yes, for the types that still generate rich results, including Product, Review snippet, Event, JobPosting, and [LocalBusiness](https://mettevo.com/seo/local-seo). FAQ and HowTo no longer earn anything in Google Search regardless of implementation quality. The return depends on which type you pick, not on whether you add schema markup at all.