Schema Markup for Websites: Types and Validation Guide

Updated October 2026. Schema markup for websites is structured information that helps search engines interpret a page’s entities and content. For example, a blog post can identify its real author and publication date; an actual business can identify its legitimate location; and an ecommerce product page can describe an item and its genuine offer. Structured data does not make false information trustworthy, and valid code does not guarantee a special Google Search result.

Quick answer: start with the page’s real purpose, select a relevant schema type, use accurate information that matches what people can see, let one system manage each entity and test the rendered live page. On WordPress, inspect existing Rank Math, theme and plugin output before inserting another generator.

This practical guide covers Article, BlogPosting, Organization, LocalBusiness, BreadcrumbList, Product and other website schema considerations; the difference between schema.org and Google’s supported rich results; WordPress implementation; validation; duplicate-markup fixes; and an owner-friendly publication checklist. It includes Google’s important 2026 FAQ rich-results retirement.

1. What is structured data, and what can it actually do?

Structured data uses recognised vocabularies to describe facts about a page or a real-world entity. Google’s introduction to structured data explains that this information can help Search understand website content and may make certain pages eligible for richer search appearances.

Schema.org is the broader vocabulary that defines types such as Organization, Person and Product. Google Search Central documents which types and properties it uses for particular Search features. A type’s existence on schema.org does not mean Google displays a dedicated rich result for it.

Google’s general structured-data policies say a correctly marked-up page may still be ineligible or may not display a rich result. Content quality, policy compliance, access and the current feature’s requirements matter alongside syntax.

2. Choose schema by page purpose—not by the number of keywords

Before adding markup, list your important page templates and the main thing each represents. A post about ecommerce is not itself a product for purchase. An agency writing about restaurants is not a restaurant. A guide to web design prices is an article, not an actual catalogue Offer simply because the article mentions prices.

For current Google-supported rich-result features, consult its Search Gallery. Supported features can be added, changed or retired; a plugin template’s list of schema types may not match current Search features.

3. Why Google recommends JSON-LD—and what the alternatives are

Google supports JSON-LD, Microdata and RDFa for its relevant structured-data implementations, subject to type-specific requirements. JSON-LD is generally recommended because it separates the data description from the visible HTML and is easier for many website teams to manage consistently.

The site’s theme, SEO plugin or application typically generates JSON-LD inside a structured-data script in the rendered HTML. For a nontechnical owner, the safer path is usually to configure a maintained existing system rather than copy scripts from a random online generator into every page.

Illustrative BlogPosting data example

The following is an educational example only, using fictional example.org data. It is a readable code illustration—not markup to be pasted into this VYLINO article or a substitute for the website’s existing BlogPosting schema.

{
  "@context": "https://schema.org",
  "@type": "BlogPosting",
  "headline": "A Practical Guide to Website Planning",
  "author": {
    "@type": "Person",
    "name": "Example Author"
  },
  "datePublished": "2026-08-01",
  "dateModified": "2026-10-01",
  "mainEntityOfPage": "https://example.org/guide/"
}

In a real implementation, use the correct live headline, appropriate author identifier and dates. When possible, let WordPress output the values dynamically so future edits do not leave stale hard-coded information behind. Review Google’s Article structured-data documentation for current properties and implementation guidance.

4. Article and BlogPosting schema: real authors, headlines and dates

For an educational WordPress post, BlogPosting is often a sensible Article subtype. It can help clarify that the page is editorial content and may support Google’s interpretation of title, byline and dates. It does not mean an article will rank first or receive a dedicated article box.

Check that the structured headline agrees with the actual article title. The author should be a genuine person or appropriate organisation that actually produced the content. Do not switch every author to a business founder merely for branding if the articles were not authored or approved by that individual.

Google’s byline date guidance distinguishes the original publication date from a genuinely meaningful update. Changing dateModified can be appropriate for substantive revisions, but altering datePublished or displaying artificial “freshness” dates without a real update can mislead both readers and systems.

On VYLINO, each completed article should keep its correct article identity and genuine author details. Structured data should describe the published article—not insert fictional services or review ratings to produce more markup.

5. Organization schema: one consistent business identity

Organization markup helps describe the real publishing organisation. Google’s Organization documentation covers applicable identity details such as name, URL, logo and supported contact or organisational information. Include only values that accurately represent the business and that the owner has approved.

For a small company operating across multiple regions, a central Organization entity can represent the company, while real, separately eligible locations or specific pages can describe appropriate local details. Do not create different fictional organisations for every keyword-targeted article.

Use a stable identifier, often an @id based on the canonical website, when one organisation is referenced repeatedly. Ensure an SEO plugin’s central company settings match public business identity details, site logo and genuinely associated profiles.

Example for VYLINO: the agency’s Organisation information should represent VYLINO as a website development business. A VYLINO article about clinics should not claim VYLINO itself is a medical clinic or that its author is a healthcare provider.

6. LocalBusiness schema: actual locations and accurate details

LocalBusiness and its subtypes may be relevant when a page describes an actual local operation. Google’s LocalBusiness documentation says to use the most specific applicable type and give accurate business details.

A restaurant can use an appropriate Restaurant subtype on a real restaurant location page; a genuine service location may be represented where applicable. But a blog article about restaurants does not become a restaurant listing, and a service-area business should not invent a customer-facing address to qualify for local search.

LocalBusiness markup does not replace an eligible Google Business Profile or guarantee placement in the local pack. See VYLINO’s Google Business Profile optimisation guide for eligibility and real-world business representation.

7. BreadcrumbList schema: navigation paths that make sense

Breadcrumb structured data describes a page’s place in a navigation hierarchy. It can help Google understand context and may support a breadcrumb appearance in results. Google’s BreadcrumbList documentation specifies the sequence of ListItem elements, positions, names and appropriate destination links.

Choose a meaningful path such as Home → Blog → Technical Guides → Article, if that reflects the site’s real organisation. Do not assemble an exaggerated hierarchy just to insert extra search phrases. Ensure the actual navigation and markup remain consistent after categories or permalinks change.

Many WordPress SEO themes or plugins already produce BreadcrumbList markup. Check the front-end output before enabling a second theme breadcrumb system, and verify there are no contradictory hierarchies for the same primary page.

8. Product and Offer schema: only real, verifiable ecommerce information

Product markup can help Google understand eligible product pages, but product snippets and merchant listings have different requirements. Google’s Product introduction and merchant listing guidance distinguish product information pages from pages where a shopper can actually buy the product.

Use real product names, visible price and currency, actual availability and genuine offer details as applicable. A “request quotation” service cannot be converted into an eligible merchant purchase simply by inventing a price. Do not attach Product, Offer or star-rating markup to generic blog articles about website design packages.

Where a WooCommerce plugin, SEO tool or theme generates product schema, review which one is authoritative. Duplicate graphs containing conflicting price or availability values can make maintenance harder and may lead to eligibility errors.

9. Service schema: descriptive vocabulary is not a guaranteed rich result

Schema.org includes a Service type, and it may be useful for expressing the meaning of a real service. But do not equate “there is a Service schema type” with “Google offers a dedicated Service rich result for every service page.” Google supports a defined set of current features, and those may change.

For a WordPress web development service page, the basics remain a helpful description, correct pricing or quotation conditions, actual company identity and a working enquiry route. Adding unsupported types or fictional offers cannot compensate for thin content or missing business information.

In a technical review, distinguish vocabulary correctness from eligibility for a particular Google feature. Google’s Search Gallery is the appropriate place to check current rich-result support.

10. FAQ schema changed in 2026: do not promise FAQ rich results

Important update: Google discontinued the FAQ rich result feature on 7 May 2026 and removed the related feature documentation in June 2026, according to the Google Search documentation changelog. Older tutorials that promise expandable FAQ rich results for ordinary business websites are outdated.

This does not mean good question-and-answer content should be deleted. Visitors still appreciate accurate FAQs about appointments, quotations, costs and the next step. But adding FAQPage markup should not be sold as a dependable way for VYLINO or similar business websites to gain an expanded FAQ listing in Google Search.

If a WordPress plugin already outputs FAQPage schema, review whether it is needed for any other supported consumer or business reason, whether its questions match visible page content and whether it duplicates another generator. Do not install more FAQ generators solely to chase a Google feature that is no longer displayed.

11. WordPress and Rank Math: find the current schema source first

A WordPress installation can output schema through Rank Math, the theme, WooCommerce, specialist plugins, custom functions or a code-injection tool. Before making changes, inspect the public page and the existing SEO settings. Otherwise, adding a supposedly helpful “schema booster” may create multiple conflicting entities.

1. Read the live HTML: Inspect the rendered JSON-LD or use a structured-data test on the actual URL.
2. Identify generators: Check what Rank Math, WordPress theme and other plugins already produce.
3. Compare with visible content: Titles, authors, dates, organisation identity, price and availability must match.
4. Choose one owner: Let the appropriate plugin or codebase manage each entity consistently.
5. Keep identifiers stable: Confirm related entities use compatible @id and URLs rather than contradictory descriptions.
6. Test and document: Record the result on representative article, service and product pages before rolling out changes.

It is possible for multiple JSON-LD blocks to be technically legitimate if they describe compatible entities. The problem is conflicting or duplicated responsibility—for example, two Product offers with different prices or two organisation identities with different addresses—not simply the number of blocks.

Review existing WordPress plugin selection guidance before adding software that reproduces markup already handled by your SEO system.

12. Canonical URLs, duplicates and indexing: schema cannot fix every problem

Schema alone cannot force Google to index a page independently. If an article has a canonical tag pointing to a service page, Google may treat the article as a duplicate or alternative regardless of its BlogPosting markup. Likewise, a noindex instruction or a redirect may prevent the intended article from becoming a standalone search result.

When reviewing a real site, inspect the HTML canonical, the declared structured-data URL and Google’s chosen canonical where Search Console provides it. These are related but distinct observations. Never rewrite canonical URLs indiscriminately just to align a plugin’s schema test.

13. Validate schema using the correct testing tools

The most reliable validation process uses two complementary tests. Google’s Rich Results Test focuses on currently supported Google rich-result features and their requirements. The Schema Markup Validator checks broader schema.org vocabulary and syntax. Google’s testing tools guide explains why those tools answer different questions.

1. Choose representative live URLs: a blog post, main business information page, service page and real product page when applicable.
2. Check the raw or rendered structured data and the responsible source plugin.
3. Run the URL through the Rich Results Test for Google-supported features.
4. Use Schema Markup Validator for general schema vocabulary or types without a Google rich-result feature.
5. Correct missing required properties and actual factual mismatches, not just cosmetic warnings.
6. Verify canonical, indexability, crawl access, status code and public image URLs.
7. Use Google Search Console URL Inspection and appropriate enhancement reports after publication.
8. Retest after content, theme, plugin, pricing or template changes.

Testing limitation: a “valid” result does not promise Google will show the enhancement or even select the intended page as canonical. Conversely, a schema type that does not appear as a supported Rich Results Test item is not necessarily invalid vocabulary; it simply may lack that Google rich-result feature.

14. Common schema mistakes and how to repair them

15. Roll out schema changes safely on a WordPress website

Changing a site-wide Rank Math setting can affect many pages, so test a few representatives before deploying a new template rule. Record which plugin or theme owns each schema type and which staff member approves business identity or product information.

Use a controlled staging or preview workflow where available, but verify the actual public URL after release. A staging site may use noindex, test domains or placeholder company information and should not be evaluated as if it represents the final indexed page.

Keep a change log with date, affected page types, plugin/version, schema source, test outcome and rollback plan. For a store, verify that the live product price, availability and markup continue to agree when inventory or variations change. For an article template, test headlines, bylines and substantive update dates after edits.

16. Measure outcomes without inventing a schema ROI figure

Schema changes may help search engines interpret content or make a page eligible for particular search appearances. But a traffic or sales movement after a deployment cannot automatically be attributed to markup alone. Google Search Central suggests comparing relevant pages and monitoring Search Console data over time.

If an individual page does not receive an enhancement, examine both feature eligibility and search context before declaring the code broken. Avoid publishing client success percentages without actual tracked evidence and relevant comparison periods.

Practical schema markup launch checklist

1. Identify the site’s real important page types and expected content entities.
2. Choose schema types based on actual purpose and Google’s current Search Gallery.
3. Check existing Rank Math, theme, WooCommerce and custom output before adding markup.
4. Verify the headline, publisher identity, author and appropriate publication/update dates.
5. Use genuine business name, contact details and location information where relevant.
6. Make sure real products use accurate details, prices, currencies and availability.
7. Remove unsupported review ratings, fake testimonials and invented commercial offers.
8. Do not promise FAQ rich results that Google retired in May 2026.
9. Ensure the same entity has compatible identifiers and no conflicting descriptions.
10. Check canonical URL, HTTP status, redirects and indexability for intended pages.
11. Validate supported features using Google’s Rich Results Test.
12. Use Schema Markup Validator when general schema.org types need inspection.
13. Use live rendered URLs, not just stored WordPress plugin fields.
14. Test representative articles, service pages and products before broad rollout.
15. Assign named owners for content accuracy, plugins and subsequent changes.
16. Monitor Search Console reports and retest after meaningful page or plugin updates.

Frequently asked questions about schema markup

Does schema markup improve Google rankings automatically?

No. It helps describe content and may support eligibility for certain Search features, but it cannot guarantee a ranking, indexation or rich result. Google’s guidelines and page quality still apply.

Should every WordPress post use BlogPosting schema?

BlogPosting is appropriate for many genuine blog articles. Product, service, contact and other page types serve different purposes, so do not force the same article identity onto every page.

Is JSON-LD better than Microdata or RDFa?

Google supports all three formats for its relevant features and generally recommends JSON-LD for ease of implementation and maintenance. Correctness and page relevance matter more than the file format alone.

Can FAQPage schema create expandable FAQ results in 2026?

Google retired its FAQ rich result feature on 7 May 2026. Helpful FAQ content remains useful, but an ordinary business website should not expect FAQ expansion in Google Search from FAQPage markup.

Should I install another schema plugin if Rank Math already handles articles?

Not without inspecting the current output. Additional generators can be appropriate for a specific, separately managed need, but they should not create conflicting identities, dates or product data.

Why is my structured data valid but not showing in Google?

Validation indicates that the tested data meets relevant technical requirements. Search appearance also depends on indexing, current feature support, policy compliance and Google’s selection of result presentation.

Can I use Product schema on a quotation-only service page?

A service page is not automatically a purchasable product. Avoid fabricated offers or merchant data; use suitable types that accurately represent the real content and current eligibility rules.

Does LocalBusiness schema replace Google Business Profile?

No. A real local business may use both its website’s structured data and an eligible Google Business Profile, but each has its own requirements. Neither should invent business locations.

What tools can validate schema on WordPress?

Use Google’s Rich Results Test for current supported rich-result features, Schema Markup Validator for broad vocabulary checks, and Search Console or URL Inspection for available published-page status and problems.

Next steps: audit what your WordPress website already outputs

Start with the website URL, its key content templates, current SEO plugin, any WooCommerce setup and the fields that staff update. Inspect the live structured data before deciding whether a new type or plugin is necessary. The goal is a consistent, maintainable source of truth—not the largest possible number of schema properties.

For related implementation planning, read VYLINO’s WordPress security checklist, WordPress developer hiring guide and Google Business Profile guide. To discuss a page-specific structured data audit with VYLINO, email contact@vylino.com with the relevant URL and the actual markup or search appearance concern. Testing and remediation require inspection of the specific live site.