← Knowledge Notes
Global Growth / Knowledge note · English

Complete Collection of Google Search Central Case Studies (13 + landing page)

Summary of 13 official Google case studies by topic: 5 Job postings cases (Eventbrite/Jobrapido/Monster/ZipRecruiter/Saramin) + 4 Video SEO cases (Vimeo/MX/Vidio/cross-regional including Weather/Italiaonline/ABP) + 1 Recipe case (Rakuten) + 1 Discover large image case (Kirbie/Istoé) + 1 CMS integration case (Wix) + shared patterns. **These are best-case outcomes and cannot be expected to scale proportionally**, but they demonstrate the value of SD, tool combinations, iframe embedding solutions (indexifembedded), and the Wix CMS implementation path

Source collection:Google Search and SEO · Published here:2026-09-26

Overseas GrowthSEO

Important disclaimer: All sites Google selects as case studies are best-case results. Expecting proportional results is an anti-pattern — actual results depend on content quality, industry, competition, and implementation completeness. The core value of these cases lies in:Demonstrating engineering implementation paths for SD + Verifying which tool combinations are usable + Special technical patterns such as the Vimeo iframe solution and Wix CMS integration.


Part 1 — Full Case Table (aggregated by topic)

Job postings (5 cases) — JobPosting SD

Company Timeline Key metrics Tools/methods
Eventbrite Started using Event SD in 2015, benefited from Google's new events search in 2017 Traffic up 100% YoY(visible within the month) Templated SD + Search Console + Structured Data Testing Tool
Jobrapido 2018-08 (58 countries) Organic traffic +182%, new registrations +395%, bounce rate -35% Direct JobPosting SD
Monster India 2018-04 (11 cities, later expanded to Gulf/SEA) Detail page organic traffic +94%, applications +10%; after expanding to multiple countries, whole-site traffic doubled Pilot first, then scale
ZipRecruiter Started in 2012 (early adopter), benefited from Google for Jobs in 2017 Conversion rate +4.5x, bounce rate -10%, non-branded monthly traffic +35% Continuous micro-format follow-up
Saramin(South Korea) Started using SC in 2015, incremental SEO In the first year, only fixed crawl errors:+15%; peak 2019 hiring season YoY +102%, new registrations +93%, conversions +9% SC + SD(JobPosting/Breadcrumb/Estimated salary)+ Mobile-Friendly Test + AMP Test + PageSpeed Insights

Video SEO(4 + 1 multi-publisher)— VideoObject / Clip / Seek SD

Company Timeline Key metrics Key tools/technologies
Vimeo Integrated best practices in 2022 Automatically enabled customer embeds for 750M+ videos iframe + indexifembedded(noindex + indexifembedded combination); Clip markup for chapters; Seek markup for automatic Key Moments; postMessage JS wrapper for iframe key moments
MX Player(India) 2021-07, 200K hours, 12 languages Traffic +3x, session video views +100% VideoObject SD + frequent video sitemaps + Search Console video report
Vidio(Indonesia) 2024-06 impressions +3x,clicks +2x(within 1 year) VideoObject SD + stable URLs for M3U8 / HLS streams; URL Inspection Video enhancement; video indexing report + performance report
cross-regional(2023-07) — Weather.com, Italiaonline, ABP News Weather: index pages +2x;Italiaonline: clicks +841%,impressions +353%,errors -85%; ABP: traffic +30%(8 Indian languages) All used video SD + Rich Results Test + Search Console video indexing report

Recipe(1)— Recipe SD

| Rakuten Recipe (Japan) | Started using SD in 2012, collaborated with Google on expansion in 2017 | Traffic +2.7x,session duration +1.5x | Full CMS rollout within 2 weeks; Search Console + Structured Data Testing Tool |

Discover large images (1–2 publishers) — max-image-preview:large meta tag

| Kirbie's Cravings(food blog) | Added meta tag with a single line of HTML | CTR +79% | | Istoé(Brazilian news weekly) | Same | CTR +30%, clicks over 6 months +332% |

Platform / CMS (1) — Search Console / Site Verification API integration

| Wix(250M users) | Collaborated with Google in 2022–2023 | 2 million Wix sites connected to SC and submitted sitemaps;Sites using the new features saw an average +15% traffic increase,Wix GPV +15%(ecommerce sites GPV +24%); Site Inspection users +5% traffic, +16% GPV | Search Console API + Site Verification API + URL Inspection API |


Part 2 — Shared patterns in tools/methods

Regardless of vertical,every case used some form of SD plus at least one Search Console validation tool:

2.1 SD types mapped to verticals

  • Job → JobPosting SD (+ optional Estimated salary, Breadcrumb)
  • Video → VideoObject SD (+ Clip for chapters, Seek for automatic Key Moments,contentUrl required)
  • Recipe → Recipe SD (+ optional Review, Time properties)
  • Event → Event SD
  • Discover → not SD, but <meta name="robots" content="max-image-preview:large">

2.2 Validation tool combinations (used in almost every case)

  1. Rich Results Test — test whether code/URL is eligible
  2. URL Inspection — see how Google indexes your URL and its Video enhancement section
  3. Search Console video indexing report — video-specific, for monitoring and fixes
  4. Search Console Rich Result status report — whole-site SD performance
  5. Performance report — clicks/impressions acceptance check
  6. Structured Data Testing Tool(legacy, deprecated, replaced by Rich Results Test and Schema Markup Validator)

2.3 Engineering implementation path

  1. Find templates: most cases used a base template and modified a small number of fields
  2. CMS pilot on a small subset → validate → scale to the whole site
  3. AMP compatibility requires separate verification (used by Rakuten / Saramin)
  4. Wait weeks to months after implementation to see results

2.4 Time window expectations

  • Eventbrite: after implementation,2–3 weeks visual SERP differences were visible
  • Saramin:Only fixed crawl errors in the first year and saw +15%; after 4 years of continuous investment, hiring season YoY reached +102%
  • ZipRecruiter:The day after implementation conversion increases were seen
  • Vidio:1 year to see 3x impressions

Part 3 — Special technical patterns (referenceable)

3.1 Vimeo's iframe + indexifembedded solution

Embedded video player developers who want embedded videos on customer sites to be indexed by Google:

Step 1: Add VideoObject SD Step 2 to the source player page (the page users embed); add robots meta to the source player page:

<meta name="robots" content="noindex, indexifembedded" />

Why this works:

  • Without noindex → the source player page itself is indexed independently (undesired)
  • With only noindex → the embedded version also loses SD (undesired)
  • noindex + indexifembedded = markup is passed through the embed attribute only when embedded via iframe on a customer page, and the source page is not independently indexed

Step 3: Wait for Googlebot to recrawl

3.2 postMessage cross-origin communication for Vimeo Key Moments

iframe embeds need to communicate the starting time parameter to the source video player:

  • Use postMessage JavaScript wrapper(Window.postMessage)
  • JS embeds (non-iframe) do not need a wrapper; player controls are on the same URL and same page

3.3 Vidio's M3U8/HLS stream handling

HLS / M3U8 video streams:

  • M3U8 is a segment map that slices the video into segments
  • ⚠️ Googlebot crawl/parse may fail on one segment → the entire byte-fetch fails
  • Solution: Use stable URL for each video file + ensure it is accessible to Googlebot
  • Verify using Video enhancement section in URL Inspection

3.4 Wix CMS integration — for developers

Wix uses Google's APIs to simplify SC for ordinary users:

  • Site Verification API + Search Console API + URL Inspection API
  • Inside the Wix Dashboard: automatic ownership verification → automatic sitemap submission → display indexing status and errors
  • The Search Console API's reporting functionality is used to build 4 integrated SEO reports
  • A model for CMS developers: integrate Google APIs so users do not need to leave your UI to complete the full SEO workflow
  • If you are a CMS wanting to collaborate with Google:forms.gle/taGyhNnAczn3VgGDA or @googlesearchc

Part 4 — Lessons from industry cases

4.1 Job industry (5 cases)

  • iceberg under SD: Core JobPosting markup + Breadcrumb / Estimated salary enhancements; Saramin added Breadcrumb and saw statuses turn from red to green
  • Migration effect: Monster piloted in India → expansion to Gulf/SEA all benefited (component reuse)
  • Conversion gains are far higher than traffic gains: ZipRecruiter saw 4.5x conversions, Jobrapido saw a 35% bounce rate reduction — users attracted by SD are more targeted
  • Freshness is critical: ZipRecruiter updates "almost in real time" — Google for Jobs updates faster than traditional SERPs

4.2 Video industry (4 cases)

  • Two-pronged approach: video sitemap + video SD(MX emphasized frequent submission)
  • video must be main content + within the viewport, above the fold (implied in multiple cases)
  • Video files must allow fetching(otherwise no video preview) — see separate note in Complete Guide to Rich Features / Discover / Images / Video / Page Experience / Web Stories / SXG / Paywall Video SEO
  • iframe embedding pattern(Vimeo solution) is essential for platform video companies
  • For HLS/DASH streams, ensure a single stable URL is provided for complete fetching

4.3 Recipe industry (1)

  • CMS implementation took only 2 weeks
  • Collaborated with Google to expand fields (Rakuten 2017 collab) — early adoption of fields is an advantage
  • AMP + Recipe SD = a long-standing combination; the Structured Data Testing Tool is required for validation

4.4 Discover large images (2)

4.5 CMS platform-level integration

  • The trio of Search Console API + Site Verification API + URL Inspection API
  • Users complete SEO verification + sitemap submission + health monitoring without leaving your UI
  • Delivering +24% GPV for ecommerce sites represents significant business value, not just traffic

Part 5 — Common failures / risks

Risks implied but not explicitly stated in every case:

  • best-case bias: All cases Google selects to publish are successes — failed cases are never written about
  • Multiple variables: Eventbrite itself stated "Multiple ongoing SEO projects can make it difficult to determine exactly what results in increased traffic" — results cannot be fully attributed to SD
  • SD ≠ ranking: SD makes you eligible to appear in rich results, but it does not guarantee appearance and does not directly affect ranking signals
  • Ongoing update and maintenance costs: Vimeo customer chapters/clips, Vidio's stable URL, ZipRecruiter continuously tracking new fields — these represent long-term costs
  • Decline of AMP: The Rakuten case used AMP, but Complete Guide to Googlebot Crawling Mechanisms and Indexing Control (URL/Links/Mobile-first/Meta/Testing/AMP) notes the overall decline of AMP — implementing AMP for SEO is not recommended at present

Part 6 — Timeline

Year Key cases
2010 Rakuten Recipe platform launched
2012 Rakuten began using Recipe SD; ZipRecruiter began using JobPosting SD
2014 Vidio launched
2015 Saramin registered for SC; Eventbrite began using Event SD
2017-05 Google launched events search → Eventbrite benefited
2017-06 Google launched Jobs search → ZipRecruiter / Jobrapido / Monster / Saramin benefited (all followed up afterward)
2017 Rakuten collaborated with Google to expand Recipe SD fields
2018-05 Eventbrite case published; ZipRecruiter case published; Rakuten case published
2018-08 Jobrapido case published
2019-06 Monster India case published
2020 Google launched max-image-preview:large for Discover
2020-04 Saramin case published
2021-07 MX Player case published
2021-08 Large images Discover case published (Kirbie / Istoé)
2022 Google launched indexifembedded rule; Vimeo and various publishers began using it
2023-01 Vimeo case published
2023-07 Cross-regional video case (Weather/Italiaonline/ABP) published
2024-02 Wix case published
2024-06 Vidio case published

Cross-references

Sources and related materials