Search Central LiveDeep Dive Europe 2026

Knowledge base v2.13.0 · Community edition · data through 2 October 2026

Topic · Serving and ranking

Rich results

Day 1 only told attendees to check and focus on rich results; Day 2 supplied the detail: structured data makes pages eligible for rich results such as review stars and recipe filters, which Google says can bring more qualified visitors. Google pointed to case studies on its developer site, including a May 2018 one in which Rakuten Recipes got 2.7 times more search traffic and 1.5 times longer sessions after adding recipe markup; the speaker called it old but expects the link to hold. The Search gallery shows the supported features, from broad page-level types (breadcrumbs, article) to vertical ones (recipes, events, products), and the Rich Results Test shows which features a page triggers and whether its markup is valid. Features come and go: Google removed several little-used ones in 2025, and a structured data manual action removes rich result eligibility without affecting web ranking. Google's generative AI guide names rich result eligibility as a reason to keep using structured data, which AI features do not require. Day 3 placed rich results in serving: Google builds search features as the last step after ranking, most of them from what it extracted during indexing, while rich results rely on extra data from the site owner, usually JSON-LD structured data; AI Overviews and AI Mode are standard search features, not rich results, and need no structured data. Google highlighted review snippets (star ratings, which it called a powerful trust signal for users, said at the event; self-serving reviews of a site's own business are not eligible), product rich results, which it called essential for e-commerce, and Article markup, highly recommended though not required for Top Stories, which can also mark paywalled content. The site name is an attribution feature that owners can influence, and Google said it may never use structured data from a site it does not trust. A Day 1 community demo treated warnings in Google's structured-data test as non-critical, which matches Search Console Help: critical issues make an item invalid for rich results, while non-critical ones only limit its appearance. Google's Rich Results Test help says the tool tests either a page's full URL or a pasted code snippet, and that all page resources must be reachable by an anonymous user, so pages behind a firewall or a password need the code mode or must be exposed, for example through a tunnel; a Day 1 community demo used both modes.

What to do

  • Map each template to the Search gallery feature it can earn and implement only those types.
  • Test templates in the Rich Results Test before and after each release.
  • Re-check the Search gallery and Google's documentation updates regularly, because features are removed.
  • Keep markup relevant to what users see: a manual action costs rich results even though ranking is untouched.
  • Mark up star ratings only for reviews of other businesses or of products; reviews of your own business are not eligible.
  • Test staging or password-protected pages in the Rich Results Test's code mode, or expose them through a tunnel.

Day 1: Crawling 6

Said on stage 4

StageConsistent with docsD1-C251

A community demo treated warnings in Google's structured-data test as not critical, in an example result of 22 items with two errors and two warnings.

Speaker not identifiedIn Day 1, 13:10 · Lightning session A: Automation and AIEvidence transcript

Used byrequirement DEV-SDA-11

  • Extended by D1-C502 Day 1: In a community demo, the structured-data problems Google's Rich Results Test reported on the test page…
StageConsistent with docsD1-C501

A community demo's script used both input modes of Google's Rich Results Test: the URL mode for public pages, which Google fetches itself, and the code mode, into which the script pasted the page's HTML, for private pages and pages Google cannot fetch (best reading of a largely unintelligible recording; the second kind of page was heard as 'dead', possibly 'dev').

Speaker not identifiedIn Day 1, 13:10 · Lightning session A: Automation and AIEvidence transcript

Used byrequirement DEV-SDA-11

  • Extends D1-C249 Day 1: A community demo showed a script that opens Chrome with a saved session, pastes a URL into Google's Rich…
StageConsistent with docsD1-C502

In a community demo, the structured-data problems Google's Rich Results Test reported on the test page included an empty name, a breadcrumb problem and a price of zero, with errors shown in pink and warnings in orange (best readings of a largely unintelligible recording; each item is heard in only one of the two recordings).

Speaker not identifiedIn Day 1, 13:10 · Lightning session A: Automation and AIEvidence transcript

Used byrequirement DEV-SDA-08

  • Extends D1-C251 Day 1: A community demo treated warnings in Google's structured-data test as not critical, in an example result of…

What Google's documentation says 2

DocsSourceD1-C265

Search Console Help separates critical issues, which make a structured-data item invalid and stop it from appearing as a rich result, from non-critical issues, listed under 'Improve item appearance'; the Rich Results Test reports valid items that have warnings.

Publisher Google Search Console HelpAnnotates Day 1, 13:10 · Lightning session A: Automation and AI

Used byrequirement DEV-SDA-11

DocsSourceD1-C506

Google's Rich Results Test help says the tool tests either a page's full URL or a pasted code snippet (Code instead of URL); all page resources must be reachable by an anonymous user on the internet, so resources behind a firewall or a password are not available to the test unless exposed, for example through a tunnel.

Publisher Google Search Console HelpAnnotates Day 1, 13:10 · Lightning session A: Automation and AI

Used byrequirement DEV-SDA-11glossary term Rich Results Test

  • Extends D1-C249 Day 1: A community demo showed a script that opens Chrome with a saved session, pastes a URL into Google's Rich…

Day 2: Indexing 10

Shown on screen 3

SlideConfirmed by docsD2-C482

A Google case study shown on stage (published May 2018) reported that Rakuten Recipes got 2.7 times more traffic from search engines and a 1.5 times increase in session duration after implementing recipe structured data.

Speaker Ryan LeveringIn Day 2, 13:35 · What is Structured Data and why we need it on the internet.Evidence slide photo, transcript

SlideConfirmed by docsD2-C490

Google recommends using the Search gallery in its developer documentation to find the structured data features that suit a site; the gallery shows each feature and how Google uses the markup.

Speaker Ryan LeveringIn Day 2, 13:35 · What is Structured Data and why we need it on the internet.Evidence slide photo, transcript

Used byrequirement DEV-SDA-03

  • Repeated by D3-C329 Day 3: Google's structured data feature guide lists the kinds of structured data Google supports with a search…
SlideConfirmed by docsD2-C498

Google recommends testing and previewing structured data in the Rich Results Test, which shows the rich result features it detected and whether the markup is valid.

Speaker Ryan LeveringIn Day 2, 13:35 · What is Structured Data and why we need it on the internet.Evidence slide photo, transcript

Used byrequirement DEV-SDA-11glossary term Rich Results Test

Said on stage 6

StageConfirmed by docsD2-C454

Structured data turns the loosely structured web into structured information that powers visual search features such as review stars and recipe filters (for example by preparation time).

Speaker Ryan LeveringIn Day 2, 13:35 · What is Structured Data and why we need it on the internet.Evidence transcript

Used byglossary term Rich results

  • Extended by D3-C337 Day 3: Review structured data lets a site specify how its users rated something; the review snippet shows an average…
StageConsistent with docsD2-C521

Structured data makes pages eligible to appear as rich results, Google's structured data talk said in its recap.

Speaker Ryan LeveringIn Day 2, 13:35 · What is Structured Data and why we need it on the internet.Evidence transcript

Used byglossary terms Rich results, Structured data

  • Extends D1-C122 Day 1: Check and focus on rich results for Google.
  • Extended by D3-C324 Day 3: Rich results differ from other search features because Google builds them from extra data that site owners…
StageConfirmed by docsD2-C522

Google keeps adding structured data features and recommendations but also removes them: in the previous year (2025) it removed several features that brought little benefit and were little used.

Speaker Ryan LeveringIn Day 2, 13:35 · What is Structured Data and why we need it on the internet.Evidence transcript

Used byrequirement DEV-SDA-03

What Google's documentation says 1

Day 3: Serving: Ranking, Search Console, and Performance 19

Shown on screen 2

SlideConsistent with docsD3-C331

Google's rich results slide said Article structured data is not required to appear in Top Stories but is highly recommended for all articles.

“Not required for "Top Stories," but highly recommended for all articles.”

Wording checked against the slide or recording

Speaker Gary IllyesIn Day 3, 13:25 · How Search results are bornEvidence slide photo, transcript

Used byrequirement DEV-SDA-13

SlideConfirmed by docsD3-C333

Google's Article rich results slide said structured data can be used to indicate that content is behind a paywall.

Speaker Gary IllyesIn Day 3, 13:25 · How Search results are bornEvidence slide photo

Used byrequirement DEV-SDA-13

Said on stage 14

StageConsistent with docsD3-C323

Most of Google's search features need nothing extra from the site owner; Google generates them from what it extracted from the page during indexing.

Speaker Gary IllyesIn Day 3, 13:25 · How Search results are bornEvidence transcript

Used byglossary term Search features

  • Extends D2-C446 Day 2: The 'gold nuggets' that Google's feature extraction step pulls out of a page's HTML are structured data (such…
StageConfirmed by docsD3-C324

Rich results differ from other search features because Google builds them from extra data that site owners provide, usually structured data and usually in JSON-LD format.

“The magic behind rich results is usually structured data. Emphasis on "usually".”

Speaker Gary IllyesIn Day 3, 13:25 · How Search results are bornEvidence transcript

Used byglossary terms Rich results, Search features

  • Extends D2-C521 Day 2: Structured data makes pages eligible to appear as rich results, Google's structured data talk said in its…
StageConfirmed by docsD3-C325

AI Mode and AI Overviews are not rich results but standard search features: they need no structured data to function and work with the normal text results from Google's index.

“AI Mode and AI Overviews are not rich results.”

Speaker Gary IllyesIn Day 3, 13:25 · How Search results are bornEvidence transcript

Used byrequirement DEV-AIF-02glossary terms Rich results, Search features

  • Extends D2-C726 Day 2: AI Overviews and AI Mode use the same index structures and token-based snippets as classic web results, a…
StageConfirmed by docsD3-C329

Google's structured data feature guide lists the kinds of structured data Google supports with a search feature and what each can do to a site's search results.

Speaker Gary IllyesIn Day 3, 13:25 · How Search results are bornEvidence transcript

  • Repeats D2-C490 Day 2: Google recommends using the Search gallery in its developer documentation to find the structured data…
StageConfirmed by docsD3-C335

Google described the site name as an attribution feature rather than a rich result, and said site owners can influence which site name Google shows for their site in search results.

Speaker Gary IllyesIn Day 3, 13:25 · How Search results are bornEvidence transcript

Used byrequirement DEV-SDA-15glossary term Site name

StageConfirmed by docsD3-C337

Review structured data lets a site specify how its users rated something; the review snippet shows an average star rating and often the number of reviews of a product, service or piece of content.

Speaker Gary IllyesIn Day 3, 13:25 · How Search results are bornEvidence transcript

Used byrequirement DEV-SDA-14glossary term Review snippet

  • Extends D2-C454 Day 2: Structured data turns the loosely structured web into structured information that powers visual search…
StageNot in docsD3-C338

Google said users rely quite a bit on review stars, calling them a powerful signal of quality and trust for users and a way for sites to use social proof to increase clicks.

“Those little yellow stars are a powerful signal of quality and trust for our users.”

Speaker Gary IllyesIn Day 3, 13:25 · How Search results are bornEvidence transcript

StageConsistent with docsD3-C647

Google may never use structured data from a site it does not trust: once it sees markup it does not trust, it does not touch it.

Speaker Gary IllyesIn Day 3, 15:45 · How long does it take to..?Evidence transcript

Used byrequirement DEV-SDA-02

  • Extends D2-C500 Day 2: Structured data that is not relevant to the page's content can be treated as abusive: Google's filters make…

What Google's documentation says 3

DocsSourceD3-C315

Google's Visual Elements gallery describes a text result as based on the page's textual content, with attribution, title link and snippet; attribution can include the site name, favicon and visible URL, and a rich result typically relies on structured data.

Publisher Google Search CentralAnnotates Day 3, 13:25 · How Search results are born

DocsSourceD3-C332

Google's Article documentation says there is no markup requirement to be eligible for Google News features like Top stories, and that Article markup can tell Google more explicitly that content is a news article, who the author is and what the title is.

Publisher Google Search CentralAnnotates Day 3, 13:25 · How Search results are born

Used byrequirement DEV-SDA-13

DocsSourceD3-C340

Google's review snippet documentation supports ratings for local businesses and organizations only on sites that capture reviews about other businesses; self-serving reviews of a site's own business are not eligible.

Publisher Google Search CentralAnnotates Day 3, 13:25 · How Search results are born

Used byrequirement DEV-SDA-14glossary term Review snippet

Across days and sessions 11

  1. Stage D1-C501 Day 1 · Lightning session A: Automation and AI

    A community demo's script used both input modes of Google's Rich Results Test: the URL mode for public pages, which Google fetches itself, and the code mode, into which the script pasted the page's HTML, for private pages and pages Google cannot fetch (best reading of a largely unintelligible recording; the second kind of page was heard as 'dead', possibly 'dev').

    extends
    Stage D1-C249 Day 1 · Lightning session A: Automation and AI

    A community demo showed a script that opens Chrome with a saved session, pastes a URL into Google's Rich Results Test, waits about 15 seconds, then screenshots and saves the result and retries on failure (the demo's recording is largely unintelligible; the tool name is a best reading).

  2. Stage D1-C502 Day 1 · Lightning session A: Automation and AI

    In a community demo, the structured-data problems Google's Rich Results Test reported on the test page included an empty name, a breadcrumb problem and a price of zero, with errors shown in pink and warnings in orange (best readings of a largely unintelligible recording; each item is heard in only one of the two recordings).

    extends
    Stage D1-C251 Day 1 · Lightning session A: Automation and AI

    A community demo treated warnings in Google's structured-data test as not critical, in an example result of 22 items with two errors and two warnings.

  3. Docs D1-C506 Day 1 · Lightning session A: Automation and AI

    Google's Rich Results Test help says the tool tests either a page's full URL or a pasted code snippet (Code instead of URL); all page resources must be reachable by an anonymous user on the internet, so resources behind a firewall or a password are not available to the test unless exposed, for example through a tunnel.

    extends
    Stage D1-C249 Day 1 · Lightning session A: Automation and AI

    A community demo showed a script that opens Chrome with a saved session, pastes a URL into Google's Rich Results Test, waits about 15 seconds, then screenshots and saves the result and retries on failure (the demo's recording is largely unintelligible; the tool name is a best reading).

  4. Stage D2-C521 Day 2 · What is Structured Data and why we need it on the internet.

    Structured data makes pages eligible to appear as rich results, Google's structured data talk said in its recap.

    extends
    Stage D1-C122 Day 1 · session not recorded

    Check and focus on rich results for Google.

  5. Stage D3-C323 Day 3 · How Search results are born

    Most of Google's search features need nothing extra from the site owner; Google generates them from what it extracted from the page during indexing.

    extends
    Stage D2-C446 Day 2 · Finding the gold nuggets: structured data, media, and more!

    The 'gold nuggets' that Google's feature extraction step pulls out of a page's HTML are structured data (such as JSON-LD), images and videos.

  6. Stage D3-C324 Day 3 · How Search results are born

    Rich results differ from other search features because Google builds them from extra data that site owners provide, usually structured data and usually in JSON-LD format.

    extends
    Stage D2-C521 Day 2 · What is Structured Data and why we need it on the internet.

    Structured data makes pages eligible to appear as rich results, Google's structured data talk said in its recap.

  7. Stage D3-C325 Day 3 · How Search results are born

    AI Mode and AI Overviews are not rich results but standard search features: they need no structured data to function and work with the normal text results from Google's index.

    extends
    Stage D2-C726 Day 2 · How does the index look like?

    AI Overviews and AI Mode use the same index structures and token-based snippets as classic web results, a point Google called important but not obvious.

  8. Stage D3-C337 Day 3 · How Search results are born

    Review structured data lets a site specify how its users rated something; the review snippet shows an average star rating and often the number of reviews of a product, service or piece of content.

    extends
    Stage D2-C454 Day 2 · What is Structured Data and why we need it on the internet.

    Structured data turns the loosely structured web into structured information that powers visual search features such as review stars and recipe filters (for example by preparation time).

  9. Stage D3-C341 Day 3 · How Search results are born

    Some countries rely a lot on social proof such as reviews, Google's speaker said, recalling a point from Google's Day 2 internationalisation talk.

    extends
    Stage D2-C614 Day 2 · Focusing on Internationalisation and Localisation

    According to consumer data shown on a slide in the talk (source not captured), US consumers judge product quality more by user feedback and reviews, while European shoppers seem to look more at brand reputation.

  10. Stage D3-C647 Day 3 · How long does it take to..?

    Google may never use structured data from a site it does not trust: once it sees markup it does not trust, it does not touch it.

    extends
    Stage D2-C500 Day 2 · What is Structured Data and why we need it on the internet.

    Structured data that is not relevant to the page's content can be treated as abusive: Google's filters make it ineffective, and egregious cases can lead to a manual action.

  11. Stage D3-C329 Day 3 · How Search results are born

    Google's structured data feature guide lists the kinds of structured data Google supports with a search feature and what each can do to a site's search results.

    repeats
    Slide D2-C490 Day 2 · What is Structured Data and why we need it on the internet.

    Google recommends using the Search gallery in its developer documentation to find the structured data features that suit a site; the gallery shows each feature and how Google uses the markup.

Built on these claims 8

Developer requirements 8

Sources 16