SEO and Marketing · 11 min read · Updated

Search Everywhere: Structured Data and Schema Markup: What Works in 2026

Which schema types Google still supports, how to build a connected JSON-LD graph, copy-ready templates, testing tips, and how AI systems use markup.

Structured Data and Schema Markup Guide (2026): featured image for the webocreation.com guide

This post is Chapter 7 of Search Everywhere: The Practical Guide to SEO, AEO and GEO, the free online edition. Chapter and appendix references link to the matching post.

Structured data is machine-readable information about a page, added to the HTML in a standard vocabulary. It tells search engines explicitly what a page is (an article, a product, a how-to, an organisation), who created it, and how its parts relate. The vocabulary used by all major search engines is Schema.org, and the preferred format is JSON-LD: a block of JSON inside a <script type="application/ld+json"> tag.

Structured data does three things for you:

  1. Eligibility for rich results. Product prices and ratings, breadcrumbs, video thumbnails, recipe cards, event dates, and other enhanced listings require structured data.
  2. Entity clarity. It connects your pages to entities (your organisation, your authors, your products) and to the knowledge graph, which supports both classic search and how AI systems understand who you are.
  3. Consistency. It forces you to state key facts (name, logo, address, author, dates) in one canonical form.

It does not directly boost rankings, and as discussed in Chapter 2, there is little public evidence that LLMs read JSON-LD when composing answers. Think of it as precise labelling that helps every system that does read it.

What Google supports in 2026

Google supports a defined list of structured data features. The list changes; some features have been retired over the years. Key points as of late 2026:

  • Still widely useful: Article, BreadcrumbList, Product (with Offer, AggregateRating, Review), Merchant listing, Organization, LocalBusiness, VideoObject, Event, Recipe, JobPosting, ProfilePage, DiscussionForumPosting, QAPage, SoftwareApplication, Dataset, Course (in some forms), and Review snippets.
  • Restricted: FAQ rich results have been shown only for well-known, authoritative government and health websites since 2023. FAQPage markup on other sites is still valid Schema.org and harmless, but it will not produce the expandable FAQ display in Google.
  • Retired: HowTo rich results were removed in 2023. Google has continued to simplify, phasing out several lesser-used features in 2025. Check Google’s Search Gallery documentation for the current list before investing in a niche type.

Even when a type no longer produces a rich result, the markup can still help with understanding, and other systems (Bing, AI tools, browser extensions) may use it.

The core graph for a content and services site

Most sites need the same backbone, ideally expressed as a connected graph where each entity has an @id that other entities can reference:

  • WebSite – the site itself, with its name and publisher.
  • Organization (or a more specific type such as ProfessionalService) – the business, with logo, contact details, address and sameAs links to official profiles.
  • Person – each author, with job title, description, image and sameAs links to their profiles (LinkedIn, X, GitHub, Amazon author page, Wikidata if available).
  • WebPage – each page.
  • Article or BlogPosting – each post, with headline, dates, author (referencing the Person @id), publisher (referencing the Organization @id) and image.
  • BreadcrumbList – the breadcrumb trail.

Yoast SEO generates a graph like this automatically, using the settings you enter in its configuration (site representation, logo, social profiles) and the author’s user profile. The quality of the output depends entirely on the quality of those settings.

Case study. The text-only fetcher used to review webocreation.com/ strips script tags, so we could not confirm what JSON-LD the site outputs. Because Yoast is active, it very likely emits a WebSite, WebPage, Article and Person graph by default. What we can see suggests gaps: the Open Graph site name is “Opencart tutorials” rather than “Webocreation”, the author avatar is a generated placeholder, and the About page’s founding year conflicts with its “10+ years” claim. Yoast pulls names and images from the same settings, so these inconsistencies probably appear in the structured data too. Running the homepage, a post and the author page through the Rich Results Test and the Schema Markup Validator is the first verification step.

Templates you can use

The following templates are written for webocreation.com/ but can be adapted to any site. Replace placeholder values. If you use Yoast, do not paste these in addition to Yoast’s output, because duplicate and conflicting entities confuse parsers. Instead, use them as a reference for what Yoast’s settings should produce, or extend Yoast’s graph using its filters.

Organization (as ProfessionalService)

{
  "@context": "https://schema.org",
  "@type": "ProfessionalService",
  "@id": "https://webocreation.com/#organization",
  "name": "Webocreation",
  "alternateName": "webocreation.com/",
  "url": "https://webocreation.com/",
  "logo": {
    "@type": "ImageObject",
    "url": "https://webocreation.com/wp-content/uploads/logo-512.png",
    "width": 512,
    "height": 512
  },
  "description": "OpenCart, WordPress, Webflow and marketing-automation development studio and publisher of free OpenCart tutorials and extensions.",
  "founder": { "@id": "https://webocreation.com/#rupak-nepali" },
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "6015 W Camino San Xavier",
    "addressLocality": "Glendale",
    "addressRegion": "AZ",
    "postalCode": "85308",
    "addressCountry": "US"
  },
  "telephone": "+1-641-455-1295",
  "areaServed": "Worldwide",
  "knowsAbout": ["OpenCart", "WordPress", "Webflow", "HubSpot", "Marketo",
                 "Pardot", "Cloudflare", "Technical SEO", "Generative engine optimization"],
  "sameAs": [
    "https://www.linkedin.com/in/rupaknepali/",
    "https://x.com/rupaknpl",
    "https://www.youtube.com/c/OnlineGyanNepal",
    "https://www.facebook.com/onlinegyannepal"
  ]
}

Notice that the sameAs links above are the founder’s personal profiles. Ideally an organisation should have its own LinkedIn company page and other official profiles. That is one of the improvements recommended for the case study.

Person (the author)

{
  "@context": "https://schema.org",
  "@type": "Person",
  "@id": "https://webocreation.com/#rupak-nepali",
  "name": "Rupak Nepali",
  "url": "https://webocreation.com/author/rupaknpl/",
  "image": "https://webocreation.com/wp-content/uploads/rupak-nepali-headshot.jpg",
  "jobTitle": "Founder and OpenCart developer",
  "worksFor": { "@id": "https://webocreation.com/#organization" },
  "description": "Web developer and author of four books on OpenCart, writing about eCommerce development since 2010.",
  "knowsAbout": ["OpenCart", "PHP", "WordPress", "Cloudflare", "HubSpot", "SEO"],
  "sameAs": [
    "https://www.linkedin.com/in/rupaknepali/",
    "https://x.com/rupaknpl",
    "https://www.amazon.com/author/REPLACE-WITH-AUTHOR-PAGE",
    "https://github.com/REPLACE-WITH-GITHUB"
  ]
}

BlogPosting

{
  "@context": "https://schema.org",
  "@type": "BlogPosting",
  "@id": "https://webocreation.com/opencart-4-cloudflare-turnstile-captcha/#article",
  "mainEntityOfPage": "https://webocreation.com/opencart-4-cloudflare-turnstile-captcha/",
  "headline": "Replace reCAPTCHA With Cloudflare Turnstile in OpenCart 4",
  "description": "A free Cloudflare Turnstile captcha extension for OpenCart 4, with installation, code walkthrough and troubleshooting.",
  "image": "https://webocreation.com/wp-content/uploads/2026/11/opencart-4-cloudflare-turnstile-captcha.png",
  "datePublished": "2026-11-13T10:00:00-07:00",
  "dateModified": "2026-11-13T10:00:00-07:00",
  "author": { "@id": "https://webocreation.com/#rupak-nepali" },
  "publisher": { "@id": "https://webocreation.com/#organization" },
  "about": [
    { "@type": "SoftwareApplication", "name": "OpenCart" },
    { "@type": "SoftwareApplication", "name": "Cloudflare Turnstile" }
  ],
  "articleSection": "OpenCart"
}

SoftwareApplication for a free extension

The site gives away more than 80 OpenCart extensions. Each download page can describe the extension as software:

{
  "@context": "https://schema.org",
  "@type": "SoftwareApplication",
  "name": "Cloudflare Turnstile for OpenCart 4",
  "applicationCategory": "BusinessApplication",
  "applicationSubCategory": "OpenCart extension",
  "operatingSystem": "OpenCart 4.0+ (PHP 8.0+)",
  "softwareVersion": "1.0.0",
  "offers": { "@type": "Offer", "price": "0", "priceCurrency": "USD" },
  "downloadUrl": "https://github.com/REPLACE/turnstile.ocmod.zip",
  "author": { "@id": "https://webocreation.com/#rupak-nepali" }
}

Note that Google’s software app rich result requires either a rating or review data. Add aggregateRating only if you collect genuine ratings on the page.

Book

The founder’s books are strong entity signals. A books page can describe each one:

{
  "@context": "https://schema.org",
  "@type": "Book",
  "name": "OpenCart 4: Dev Guide for Themes & Extensions",
  "author": { "@id": "https://webocreation.com/#rupak-nepali" },
  "datePublished": "2024",
  "bookFormat": "https://schema.org/Paperback",
  "inLanguage": "en",
  "url": "https://webocreation.com/opencart-4-ebook/",
  "sameAs": "https://www.amazon.com/dp/REPLACE-ASIN"
}

Product for an OpenCart store

For eCommerce, Product markup is the most valuable type. OpenCart does not output complete product schema by default; an extension or theme change is usually needed.

{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Handmade Silver Ring",
  "sku": "RING-001",
  "image": ["https://store.example.com/image/catalog/ring-1.jpg"],
  "description": "Hand-forged sterling silver ring.",
  "brand": { "@type": "Brand", "name": "Example Jewellery" },
  "offers": {
    "@type": "Offer",
    "url": "https://store.example.com/silver-ring",
    "priceCurrency": "USD",
    "price": "79.00",
    "availability": "https://schema.org/InStock",
    "itemCondition": "https://schema.org/NewCondition",
    "shippingDetails": {
      "@type": "OfferShippingDetails",
      "shippingRate": { "@type": "MonetaryAmount", "value": "5.00", "currency": "USD" },
      "shippingDestination": { "@type": "DefinedRegion", "addressCountry": "US" }
    },
    "hasMerchantReturnPolicy": {
      "@type": "MerchantReturnPolicy",
      "applicableCountry": "US",
      "returnPolicyCategory": "https://schema.org/MerchantReturnFiniteReturnWindow",
      "merchantReturnDays": 30
    }
  },
  "aggregateRating": { "@type": "AggregateRating", "ratingValue": "4.8", "reviewCount": "37" }
}

FAQPage (still worth it?)

FAQ markup will not produce FAQ rich results for most sites any more. Should you still add it? Arguments for: it is accurate labelling, other engines may use it, and it encourages writing clear question-and-answer content, which helps AEO. Arguments against: it adds maintenance. A reasonable approach is to keep visible FAQ sections on pages where they genuinely help readers, mark them up if your SEO plugin does it automatically, and not spend extra effort otherwise. The visible content is what matters for AEO and GEO.

Rules that keep you out of trouble

  • Mark up only what is visible on the page. Adding ratings, prices or FAQs that users cannot see violates Google’s guidelines and can lead to a manual action.
  • Be accurate and consistent. The name, address, phone and logo should match across the site, structured data, Google Business Profile and other profiles.
  • Use one tool to generate the graph. Multiple plugins outputting overlapping schema create duplicates and conflicts.
  • Use specific types where they apply (ProfessionalService rather than plain Organization, BlogPosting rather than CreativeWork).
  • Connect entities with @id. A connected graph is clearer than a set of disconnected blocks.

Testing and monitoring

  • Rich Results Test (search.google.com/test/rich-results) shows which Google rich results a page is eligible for, and any errors or warnings. It renders JavaScript.
  • Schema Markup Validator (validator.schema.org) validates against the full Schema.org vocabulary, including types Google does not use for rich results.
  • Search Console enhancement reports (under “Enhancements” or “Shopping”) show errors and valid items across the whole site for supported types such as Breadcrumbs, Products, Videos and Review snippets.
  • URL Inspection shows the structured data Google detected on the indexed version of a page.
  • Crawlers (Screaming Frog, Sitebulb, Semrush Site Audit) can extract and validate structured data across thousands of pages.

Structured data and AI systems

How much do AI answer engines use structured data? The honest answer is that it is unclear and varies. Search engines use it to build their knowledge graphs and indexes, and AI products built on those indexes benefit indirectly. Product data from Merchant Center and product schema feeds into shopping experiences in Google’s AI Mode and other assistants. Entity data (Organization, Person, sameAs) helps disambiguate who you are.

What matters most for AEO and GEO is that the same facts are stated visibly on the page, in clear sentences, and consistently across the web. Structured data reinforces those facts; it does not replace them.

Key takeaways

  • Use JSON-LD with Schema.org types, connected through @id references.
  • The backbone for most sites is WebSite, Organization, Person, WebPage, Article and BreadcrumbList.
  • FAQ and HowTo rich results are restricted or retired, but visible Q&A and step content still helps AEO.
  • Mark up only visible, accurate information, and generate it from one source.
  • Validate with the Rich Results Test and Schema Markup Validator, and monitor with Search Console.
  • On the case study, verify Yoast’s output and fix the brand name, author image and founding-year inconsistencies that feed it.

Previous: Page Experience and Speed: Fixing Core Web Vitals
Next: Platform SEO: WordPress, OpenCart and WooCommerce
All chapters: Search Everywhere: The Practical Guide to SEO, AEO and GEO

Search Everywhere (full PDF)The complete guide in one printable PDF.PDF · 2.8 MB
Free download: unlock it in one step

Share this page

or

Mailchimp opens in a new tab to confirm. Unsubscribe any time.

Rupak Nepali
Written byRupak Nepali

Rupak Nepali is a web developer, manage Webocreation website and the author of six books:
Getting Started with OpenCart Module Development (Packt, 2013),
OpenCart Theme and Module Development (Packt, 2015),
OpenCart 4: Dev Guide for Themes & Extensions (2024),
OpenCart 4: User Manual (2025),
Cloudflare for the Enterprise Website (2026) and
The Technical Web Guide for Marketers (2026).
Rupak has built OpenCart stores and extensions since 2010, has published more than 600 tutorials on Webocreation, and shares free OpenCart extensions on GitHub.
Find Rupak on
GitHub | Amazon | LinkedIn | X | YouTube.

Leave a Reply

Your email address will not be published. Required fields are marked *