What is structured data and why does it matter for SEO?

Structured data is a standardised format for organising and labelling information on a webpage so that search engines can understand it unambiguously. Rather than relying on a search engine to infer the meaning of your content from plain text, structured data provides explicit signals — telling Google not just that a page mentions "4.8 stars" but that this is an AggregateRating for a specific Product, from 312 verified Reviews, applied to an item priced at $49.99 that is currently InStock. The dominant vocabulary for structured data on the web is schema.org, which was jointly developed by Google, Bing, Yahoo, and Yandex in 2011 to create a shared language for describing content types. Schema.org defines hundreds of types — from Article and Product to Event, Recipe, LocalBusiness, and MedicalCondition — each with specific properties that describe them in detail. For SEO, structured data matters in several concrete ways. First and most visibly, it enables rich results — the enhanced search listings that show star ratings, FAQs, product prices, breadcrumbs, cooking times, and other details directly in the search results page. Rich results typically achieve 20–30% higher click-through rates than standard blue link results, making them one of the highest-ROI SEO investments available. Second, structured data feeds Google's Knowledge Graph — the database of entities and relationships that powers Knowledge Panels, featured snippets, and entity-based search. When you mark up your o

What is JSON-LD and how is it different from Microdata?

JSON-LD (JavaScript Object Notation for Linked Data) and Microdata are both valid formats for implementing schema.org structured data, but they work very differently and have different practical implications for your website. Understanding the distinction helps you choose the right approach and avoid common implementation mistakes. JSON-LD is a standalone script block — specifically, a element — that can be placed anywhere in your page's or . It contains a JSON object describing your page's structured data independently of the page's visible HTML content. The key advantage of this separation is that you can add, modify, or remove structured data without touching your page's design, markup, or existing content. Your developer or SEO team can manage schema entirely in one place without risk of breaking the visual layout. Google officially recommends JSON-LD for all new implementations and uses it in all of its own documentation and tools. Microdata, by contrast, embeds structured data attributes directly into your existing HTML tags using itemscope, itemtype, and itemprop attributes. A product name marked up in Microdata might look like: Product Name . This approach ties your structured data to your HTML structure, meaning any change to the visual markup risks breaking or altering your schema. It is harder to maintain at scale, harder to audit, and harder to debug. Microdata was Google's original rec

How does schema markup improve local SEO and Google Maps rankings?

Schema markup — specifically LocalBusiness schema and its dozens of subtypes — is one of the most powerful and underutilised tools for local SEO. While Google My Business (now Google Business Profile) is the primary signal for local pack rankings, structured data on your website reinforces and validates the information in your Google Business Profile, contributing to the NAP consistency (Name, Address, Phone) that local search algorithms depend on. The most important schema type for local businesses is LocalBusiness (or a more specific subtype such as Restaurant, MedicalClinic, LegalService, AutoDealer, Hotel, RealEstateAgent, or any of the 200+ subtypes that schema.org defines). A well-implemented LocalBusiness schema block communicates your exact business name, street address, city, state, postal code, country, phone number, email, website URL, opening hours, price range, geographical coordinates (latitude and longitude), and accepted payment methods — all in a machine-readable format that Google can cross-reference against your Google Business Profile. The geo element of LocalBusiness schema is particularly important and often overlooked. The GeoCoordinates property, which specifies exact latitude and longitude, provides a precision signal that supports local pack appearance for searches with geographic intent. When Google is deciding which businesses to surface for "schema audit tool near Austin" or "best coffee shop in Brooklyn," the presence of accurate GeoCoordinates

What are rich results and how do I get them in Google Search?

Rich results (previously called rich snippets) are enhanced search listings that display additional visual elements beyond the standard title, URL, and meta description. They can include star ratings, FAQ dropdowns, product prices and availability, event dates, recipe details, job posting information, breadcrumb trails, video thumbnails, and more. Rich results are powered by schema.org structured data on your page and are earned — not bought — by correctly implementing the schema types that Google supports for rich result generation. The most commonly seen rich results and their corresponding schema types include: FAQPage schema, which generates expandable question-and-answer dropdowns directly below your search listing — one of the most impactful rich results in terms of SERP real estate; Product schema with AggregateRating, which displays star ratings, review counts, price ranges, and availability directly in both organic results and Google Shopping; Article and NewsArticle schema, which qualifies content for the Top Stories carousel and article rich results with publication date and author; HowTo schema, which generates numbered step previews in search results for tutorial and guide content; BreadcrumbList schema, which replaces the URL with a clean navigational path; Event schema, which displays event date, location, and registration information for event pages; and Recipe schema, which shows cooking time, ratings, and calorie information for recipe pages. Getting rich

How does schema markup support Google's E-E-A-T quality signals?

E-E-A-T stands for Experience, Expertise, Authoritativeness, and Trustworthiness — the four qualities that Google's Search Quality Rater Guidelines use to evaluate the quality of web content, particularly for YMYL (Your Money or Your Life) topics such as health, finance, legal advice, and news. While E-E-A-T is not a direct algorithmic ranking factor, it reflects the qualities that Google's systems are trying to reward, and schema markup plays a meaningful role in communicating these signals. The most direct schema contribution to E-E-A-T is Person schema for authors and contributors. When you mark up your article authors with Person schema — including their name, job title, professional affiliation, credentials, and links to authoritative external profiles — you are giving Google machine-readable evidence of who created the content and what their qualifications are. This is particularly important for medical, legal, financial, and scientific content where author expertise is a primary quality signal. The sameAs property within Person schema links your author to their LinkedIn profile, academic publications, speaking profiles, or other authoritative sources, creating a verifiable entity that Google can cross-reference. Author Schema should include the author's name, URL to their bio page, their job title, their organisation, and sameAs links to professional profiles. Organisation schema contributes to the Trustworthiness and Authoritativeness dimensions by establishing your

How do I implement Product schema for an e-commerce site?

Product schema is one of the highest-value schema implementations for any e-commerce website. When correctly implemented, it enables rich product snippets in organic search — showing your price, availability, and star rating directly in the SERP — and improves visibility in Google Shopping. With Google's continued expansion of free product listings, accurate Product schema is now a prerequisite for appearing in Shopping results without a paid campaign. A complete Product schema implementation includes several required and recommended properties. The required fields that Google needs for rich results are name (the product's title), image (at least one high-quality product image URL), and offers (a nested Offer block containing the price, priceCurrency, and availability). Without these three elements, your Product schema will be valid but ineligible for rich results. The recommended properties that significantly enhance your rich result eligibility and Shopping presence include: sku (your unique product identifier); brand with a nested Organization or Brand type; description (a complete product description); gtin13 or gtin12 (barcode/EAN); mpn (Manufacturer Part Number); aggregateRating with ratingValue, reviewCount, and bestRating; review with individual Review objects; and the Offer properties priceValidUntil (for sale prices), hasMerchantReturnPolicy (for return policy rich results), and shippingDetails (for shipping cost and delivery time rich results — increasingly impor

Should I add FAQPage schema to my website and what are the benefits?

FAQPage schema is arguably the highest return-on-investment schema type available to most websites in 2026. The reason is straightforward: when Google chooses to display FAQPage rich results, it adds expandable question-and-answer dropdowns directly below your search listing, dramatically increasing the vertical space your result occupies in the SERP. A standard search result might occupy 60–80 pixels. A listing with three expanded FAQs can occupy 300–400 pixels — without any change to your rankings, titles, or meta descriptions. The impact on CTR is significant and well-documented. FAQPage rich results appear for pages that have genuine FAQ content — either a formal FAQ section or a page structured around questions and answers — and that implement FAQPage schema accurately. The schema must reflect questions and answers that are actually present and visible on the page. Google will not generate FAQ rich results for schema that marks up questions not actually answered on the page, and will penalise sites that use FAQPage markup misleadingly. The eligibility criteria for FAQPage rich results are relatively accessible compared to other rich result types. You do not need a high domain authority, a large number of backlinks, or a long publishing history. You need page content quality that meets Google's basic standards and accurate schema markup that correctly represents that content. This makes FAQPage schema particularly valuable for newer sites or pages on sites that do not y

What schema markup is most important for a small local business?

For a small local business — whether a restaurant, dental practice, law firm, retail store, plumber, or any other service or brick-and-mortar business — structured data has a uniquely high return because local search is intensely competitive and rich results plus entity signals can distinguish your listing from dozens of similar businesses in the same area. Unlike large e-commerce sites or media publishers that need to implement schema across thousands of pages, a small local business typically has a small number of key pages where a focused schema effort delivers outsized results. The single most important schema type for any local business is LocalBusiness, or a more specific subtype if one exists for your industry. Schema.org defines over 200 LocalBusiness subtypes, and using the most specific applicable subtype — DentalClinic instead of just LocalBusiness, or ItalianRestaurant instead of just FoodEstablishment — provides stronger signals. The core properties to include are: name (your exact legal or trading name, matching your Google Business Profile exactly), address with PostalAddress including streetAddress, addressLocality, addressRegion, postalCode, and addressCountry; telephone; url; openingHours or the more detailed openingHoursSpecification; geo with GeoCoordinates latitude and longitude; priceRange (typically expressed as $ to $$$$); image; and sameAs linking to your Google Business Profile URL, Yelp, Facebook, and any relevant industry directories. The name an

Does schema markup affect page speed or Core Web Vitals?

This is one of the most common misconceptions about schema markup — that adding JSON-LD script blocks will slow down your page and negatively affect Core Web Vitals scores. In practice, schema markup implemented correctly has a negligible impact on page speed and no measurable impact on Core Web Vitals, and the SEO benefits it delivers far outweigh any trivial performance consideration. The reason schema has minimal performance impact is the nature of JSON-LD itself. A typical JSON-LD block — even a comprehensive one with multiple schema types — is a plain text data structure, typically between 500 bytes and 5 kilobytes. For context, a single compressed JPEG hero image on a modern website is usually 50–200 kilobytes. Your JSON-LD schema is orders of magnitude smaller than a single image. The browser parses JSON-LD script blocks rapidly, and because they contain no executable JavaScript (they are data, not code), they add no CPU execution time. The one performance consideration worth noting is where in the HTML you place your JSON-LD. Placing it in the of your document means it is parsed before the visible page content renders, which is correct from a search engine crawlability standpoint but adds a tiny amount of parsing time. In practice, for a typical schema implementation, this is measured in microseconds and has no measurable effect on any Core Web Vitals metric — not LCP (Largest Contentful Paint), not FID or INP (Interaction to Next Paint), and not CLS (Cumulat

How should I implement schema markup for multilingual and international websites?

Multilingual and international websites face specific structured data challenges that domestic single-language sites do not encounter. The core issue is that schema.org structured data, like hreflang and other international SEO elements, needs to accurately reflect the language and regional context of each page rather than using a single global schema implementation across all URL variants. The most important principle for international schema is that each language or regional variant of a page should have its own schema block that matches the content on that specific page. If you have a French-language version of your homepage at yoursite.com/fr/, the JSON-LD on that page should be in French — the name, description, and content properties should use French text matching the French page content. Serving English JSON-LD on a French page creates a mismatch between your structured data and your page content, which can confuse search engines and reduce schema eligibility. The inLanguage property is essential for international schema implementations. Add it to your Article, WebPage, or WebSite schema blocks to specify the language of the content using BCP 47 language tags (e.g., "en", "en-US", "fr-FR", "de-DE", "ja", "zh-Hans"). For WebSite schema, if your site serves multiple languages, either create separate WebSite schema blocks for each language root or use the inLanguage property to specify the primary language for each URL variant. For Organisation schema, the situation i

What is a schema.org validator?

A schema.org validator checks whether a website's structured data markup follows schema.org specifications correctly. It verifies JSON-LD, Microdata, and RDFa markup to ensure search engines like Google can read and use the data for rich results.

What is JSON-LD and why does it matter for SEO?

JSON-LD (JavaScript Object Notation for Linked Data) is Google's preferred format for structured data markup. It allows search engines to understand your content's context, enabling rich results like star ratings, FAQs, breadcrumbs, and product details in search results.

What schema types does SchemaScan validate?

SchemaScan validates 10 high-impact schema types: Organization, WebSite with SearchAction, BreadcrumbList, Article/BlogPosting, FAQPage, Product, AggregateRating/Review, Person/Author, HowTo, and JSON-LD syntax validity.

Is SchemaScan free to use?

Yes, SchemaScan is completely free to use with no account or login required. Simply paste any public URL to get an instant schema audit score and structured data report.

How do I fix schema.org errors on my website?

After scanning your URL, SchemaScan identifies missing or broken schema types and provides plain-English fix instructions for each issue. Enter your email address to receive a detailed fix-it report with specific recommendations for your site.

Home/FAQ

Schema.org & Structured Data FAQ

Expert answers to the most common questions about schema markup, JSON-LD, rich results, and structured data SEO — each written in depth to give you the full picture.

Ready to audit your structured data?

Use SchemaScan to instantly check your website's schema.org implementation and get a free fix-it report.

Run a free schema audit →