Skip to content
arduralab
·9 min

Schema.org and Structured Data — How to Win Rich Snippets in Google

Schema.orgstructured datarich snippetstechnical SEOJSON-LD
MG
Marcin Godula

Współzałożyciel & Head of SEO/Tech

Specjalista SEO, GEO i web development z ponad 15-letnim doświadczeniem. Pomaga firmom B2B budować widoczność w wyszukiwarkach klasycznych i AI.

Schema.org is a universal structured data standard that helps search engines and AI better understand the content of a web page.

What Is Structured Data?

Imagine Google reading your page like a robot — it sees text but does not understand context. "ARDURA Lab" — is that a company? A person? A product? "3,000 PLN" — is that a price? A salary? A fine?

Structured data is a way of telling Google (and AI) explicitly: "This is a company. This is a price. This is an FAQ. This is an article with a publication date." In the audits we run, a site with zero schema is still the norm, not the exception — and it is the cheapest fix in the entire technical audit.

Format: JSON-LD (JavaScript Object Notation for Linked Data) — a script in the <head> of the page that Google and AI parse automatically.

Result: Rich snippets — enhanced search results in Google with stars, prices, breadcrumbs, images — if Google decides to show them. Google does not guarantee that structured data will appear in search results, even when the markup is correct.


Why Schema.org Matters in 2026

1. Rich Snippets Make a Result Stand Out

A standard Google result (illustrative example):

Ergonomic Office Chair | Example Store
Adjustable lumbar support, breathable mesh back...

A result with rich snippets:

Ergonomic Office Chair | Example Store
★★★★☆ 4.6 · 128 reviews · €249 · In stock
Adjustable lumbar support, breathable mesh back...

The second result carries more information before the click. Whether that earns more clicks on your own pages is something to measure in Search Console — the markup only makes the result eligible.

2. Structured Data and AI Search

For AI Overviews and AI Mode, Google says structured data isn't required and there is no special schema.org markup to add — but it recommends continuing to use structured data as part of your overall SEO, as long as it matches the visible text on the page.

3. Knowledge Panels

Schema.org Organization + sameAs (links to social media) = a chance for a Knowledge Panel on the right side of the SERP. This is one of the signals we're using to build our own entity recognition — a process we're still actively working on, and we have no illusions that one schema type settles it.


8 Schema.org Types to Consider

1. Organization

Where: Homepage (in the layout — on every page)

What it provides: Helps Google understand your organization and tell it apart from others; it can influence which logo is shown in results and in your knowledge panel.

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "ARDURA Lab",
  "url": "https://arduralab.com",
  "logo": "https://arduralab.com/logo.png",
  "description": "Web development, SEO, and GEO agency.",
  "contactPoint": {
    "@type": "ContactPoint",
    "email": "hello@arduralab.com",
    "contactType": "customer service",
    "availableLanguage": "Polish"
  },
  "areaServed": {
    "@type": "Country",
    "name": "Poland"
  },
  "knowsAbout": ["SEO", "GEO", "Web Development"]
}

The idea is the same as on our side: we keep the full company data in one module (json-ld.ts) and render it globally from the layout — one source of truth instead of copying JSON onto every page.

2. WebSite + SearchAction

Where: Homepage

What it provides: Helps Google determine your site name. The sitelinks search box that SearchAction used to enable was retired by Google on November 21, 2024, so the potentialAction part no longer changes how your result looks.

{
  "@context": "https://schema.org",
  "@type": "WebSite",
  "name": "ARDURA Lab",
  "url": "https://arduralab.com",
  "potentialAction": {
    "@type": "SearchAction",
    "target": "https://arduralab.com/baza-wiedzy?q={search_term_string}",
    "query-input": "required name=search_term_string"
  }
}

3. BreadcrumbList

Where: Every subpage

What it provides: Breadcrumbs in desktop search results instead of the URL path. Since January 23, 2025, Google no longer shows breadcrumbs on mobile — mobile results show only the domain.

On desktop, the result looks like:

arduralab.com > Services > SEO

instead of:

https://arduralab.com/uslugi/seo
{
  "@context": "https://schema.org",
  "@type": "BreadcrumbList",
  "itemListElement": [
    { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://arduralab.com" },
    { "@type": "ListItem", "position": 2, "name": "Services", "item": "https://arduralab.com/uslugi" },
    { "@type": "ListItem", "position": 3, "name": "SEO", "item": "https://arduralab.com/uslugi/seo" }
  ]
}

4. Article

Where: Every blog post / knowledge base article

What it provides: Informs Google about the publication date, author, and topic. A chance for a rich snippet with date and thumbnail.

{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "Article Title",
  "description": "Article description",
  "datePublished": "2026-01-20",
  "dateModified": "2026-01-20",
  "author": {
    "@type": "Person",
    "name": "Author"
  },
  "publisher": {
    "@type": "Organization",
    "name": "ARDURA Lab",
    "url": "https://arduralab.com"
  }
}

The article you're reading right now carries exactly this JSON-LD — with a named author as a Person, not an anonymous "editorial team". We're not doing this for show: it's the same signal this section has been arguing for from the start.

5. FAQPage

Where: FAQ pages + articles with Q&A sections

What it provides: Marks up question-and-answer content. In August 2023 Google limited FAQ rich results to well-known government and health websites, and according to its documentation changelog the FAQ rich result no longer appears in Google Search as of May 7, 2026. This markup no longer adds expandable questions to the result.

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "How much does a website cost?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "A business card site from 3,000 PLN, a business site with a blog from 8,000 PLN."
      }
    }
  ]
}

Our practice: every post on our blog closes with an FAQ section carrying its own JSON-LD, generated from the post's frontmatter, because it describes the Q&A content explicitly. We don't count on it for rich results, which Google now limits to government and health sites.

6. Service

Where: Service pages

What it provides: Informs Google about your services — name, description, provider, location.

{
  "@context": "https://schema.org",
  "@type": "Service",
  "name": "SEO Positioning",
  "description": "Strategic SEO — audit, content, link building.",
  "url": "https://arduralab.com/uslugi/seo",
  "provider": {
    "@type": "Organization",
    "name": "ARDURA Lab"
  },
  "areaServed": {
    "@type": "Country",
    "name": "Poland"
  }
}

7. LocalBusiness (for businesses with an office)

Where: Homepage or contact page

What it provides: Tells Google about business details such as address and opening hours. The Google Maps listing itself comes from your Business Profile, not from the markup.

8. HowTo

Where: "How-to" articles

What it provides: Describes step-by-step instructions. Since September 2023, Google no longer shows HowTo rich results, so treat it as an optional description, not a SERP feature.


How to Implement Schema.org

Option 1: JSON-LD in Code (recommended)

Add <script type="application/ld+json"> in the <head> or before </body>.

In Next.js:

<script
  type="application/ld+json"
  dangerouslySetInnerHTML={{
    __html: JSON.stringify(organizationJsonLd()),
  }}
/>

Advantages: Full control, easy to maintain, does not affect rendering. This is the exact function, organizationJsonLd(), that we call from this site's own layout — one type, one function, zero duplicated JSON across pages.

Option 2: WordPress Plugin

  • Yoast SEO — basic schema (Organization, Article, BreadcrumbList)
  • Rank Math — more advanced schema
  • Schema Pro — dedicated plugin

Downside: Limited control, dependency on the plugin.

Option 3: Google Tag Manager

Injecting JSON-LD through GTM. The "no developer" option.

Downside: Google officially supports this method, but JavaScript rendering can delay indexing.


How to Test Schema.org

1. Rich Results Test (Google)

URL: search.google.com/test/rich-results

Paste the URL -> Google shows detected schema and whether you qualify for rich snippets.

2. Schema Markup Validator

URL: validator.schema.org

More technical — shows all errors and warnings in your schema.

3. Google Search Console

Reports -> the rich result reports for the types Google detects on your site (e.g., Breadcrumbs).

Shows how many pages have valid schema and what errors Google has detected.


Most Common Schema.org Mistakes

1. Schema Does Not Match Content

FAQ schema on a page without questions and answers. Google will detect this and ignore it.

2. Missing Required Fields

Every schema type has required fields. An Article without headline or datePublished is invalid.

3. Spammy Schema

Fake reviews (5 stars, 100 reviews on a new site). Google penalizes spammy structured data.

4. Duplicates

Two identical Organization schemas on the same page. One instance per type.

5. Outdated Data

Opening hours from before the pandemic. Prices from 2 years ago. Update schema alongside content.


Schema.org's Impact on Rankings

Direct impact on rankings: Google's documentation presents structured data as a way to understand content and qualify for rich results, not as a ranking factor.

Indirect impact: possible, not guaranteed.

  • Better content understanding -> more accurate SERP display
  • Eligibility for rich results -> a more noticeable result, if Google shows it

To check the effect on your own site, Google recommends a before-and-after test on a few pages, recorded for a few months in the Performance report of Search Console.


Schema.org and GEO (AI)

In the context of GEO (Generative Engine Optimization), it is worth separating what is documented from what is assumed. For AI Overviews and AI Mode, Google says there is no special schema.org markup to add, though it recommends structured data as part of overall SEO. What Schema.org does reliably is describe your organization, services, and content explicitly and consistently with the visible page:

  • Organization schema states who you are and links your official profiles
  • Service schema states what you offer, where, and who provides it
  • Article schema states who wrote a piece and when it was updated

This site follows the same approach: our robots.ts explicitly lets in GPTBot, ClaudeBot, PerplexityBot, and Google-Extended, and we separately publish llms.txt and llms-full.txt (Google says Google Search doesn't use such files).


Schema.org Implementation Checklist

Minimum (every site):

  • Organization (layout/global)
  • WebSite (homepage)
  • BreadcrumbList (every subpage)

Content:

  • Article (every blog post)
  • FAQPage (FAQ page + articles with Q&A)

Services:

  • Service (every service page)

Optional (but recommended):

  • LocalBusiness (if you have an office)
  • Review/AggregateRating (for products you sell — Google doesn't show self-serving review stars for your own business)

Verification:

  • Rich Results Test — zero errors
  • Schema Markup Validator — zero warnings
  • Google Search Console — monitor reports

Want to implement Schema.org on your site? Request a structural audit — we will determine which schemas to implement and how to measure their effect in Search Console.

Need help with this topic?

Get a free audit and find out how we can help your business grow online.

Get a free quote