Schema Markup for Casino Sites: Rich Results That Drive CTR

Last updated: 2026-06-15 • By: Editorial Desk • This guide is for SEO and product teams in iGaming. Age 18+.

A cold open: the CTR bump that should not have worked

We took a casino review page. We trimmed hype. We kept the core. Then we added a few small, clean schema blocks. We did not chase stars. We did not add FAQ. We stayed within rules. A few weeks later, CTR went up. Not a spike, but steady, week after week.

Why did this work? Because in this niche, you win by picking the right schema. Not all types lead to rich results. Some never show. Some even risk a manual action. The trick is to ship the types that Google is fine to show, and skip the rest.

If you want to see what rich results are in scope, start with Google’s own map. It shows what search can show, and when. See Google’s guidance on rich results. Read it with your niche in mind. Keep a list of what is allowed, and what is not.

Quick detour: What rich results can casino sites actually earn?

Short answer: fewer than general e‑commerce. But enough to lift clicks. In iGaming, you can bet on these safe plays:

• Logo and brand panel for your brand queries.
• Breadcrumbs for clean paths under your blue link.
• Video badges for good review videos.
• Sitelinks search box on your brand SERP, if you qualify.

Before you start, run pages through the tool that matters: Rich Results Test. It shows if a page is eligible and if the code is valid. Then look at the table below for where to focus.

Review page (casino brand)	BreadcrumbList; VideoObject (if video); Article; Organization (site‑wide)	Conditional (Video, Breadcrumbs, Logo)	Medium–High (video badge helps)	Medium	Self‑serving stars for Organization are not allowed; thin or misleading video	Use clear titles, timestamps in video; avoid Review stars for the brand entity
Toplist (best casinos, bonuses)	ItemList (with position); BreadcrumbList	Indirect (no special card; breadcrumbs show)	Low–Medium (clear sitelinks, better understanding)	Low	Forcing Carousel is unlikely; wrong positions in ItemList	ItemList improves context; helps sitelinks to subpages over time
Game/Slot page	VideoObject (reviews, how‑to); SoftwareApplication or Game (optional)	Conditional (Video)	Medium (video badge on some queries)	Medium	Over‑promising RTP or payouts; wrong contentRating	Mark contentRating as 18+; add timestamps and chapters
Bonus/Promo page	Offer (amount, eligibleRegion); BreadcrumbList	Unlikely (no Product card)	Low–Medium (indirect clarity)	Low	Misleading discounts; geo not set; expiry missing	Offer helps machines read terms; do not expect a rich card
Blog/Guide	Article; BreadcrumbList; VideoObject (if any)	Conditional (Video, Breadcrumbs)	Low–Medium	Low	FAQ was cut for most sites; don’t spam Q&A	Focus on unique media and steps; link to RG help
Homepage	WebSite + SearchAction; Organization + Logo + SameAs	Possible (Sitelinks search box, Logo)	Medium (brand SERP lift)	Low	Logo file not eligible; SameAs junk links	Clear brand panel helps trust; keep SameAs high quality

After the table, keep one rule in mind: you must follow the Structured data general guidelines. If a type is not eligible, you can still use it for clarity. But do not expect a card to show.

Field notes: implementation recipes by page type

1) Site‑wide: WebSite + SearchAction (Sitelinks search box)

Use this if your brand has site search and good brand demand. Google may show a search box under your brand result. Follow the doc: Sitelinks search box.

2) Organization + Logo

This helps your logo and brand panel. Use a clean, crawlable logo at least 112x112, square, and not in a sprite. See Logo structured data.

Keep SameAs clean. Link only to strong profiles. No coupon sites. No low trust pages.

3) BreadcrumbList on every main template

Breadcrumbs show under your blue link and help users scan. They also help Google map your site. Follow Breadcrumb structured data.

4) Casino review pages: what to add, what to avoid

Do add BreadcrumbList. Add VideoObject if you have a real review video. Mark the page as Article or Review if it fits, but do not try to show stars for your own Organization. Google does not show self‑serving stars. See policy: Review snippets policy.

5) Bonus/Promotion pages: Offer, not Product

Product rich cards do not fit this niche. They will not show. You can still use Offer to add structure for terms, dates, and geo. See Schema.org Offer. Do not expect a rich card from this.

6) Game pages (slots, table games): lead with VideoObject

Video is your best shot at a badge on SERP. Use it when the video is yours, helpful, and not clickbait. Follow Video structured data. Add content rating (18+).

Keep the title clear. Add chapters with Clip. Add a short, honest description. Do not claim sure wins.

7) Toplists: ItemList for order and clarity

Toplists rarely get a special card. But ItemList helps Google parse order and intent. See ItemList type.

Do not stuff names with ads. Keep positions true to the page.

8) Regionalization, language, and 18+

Mark language with inLanguage. Add eligibleRegion in Offer when it applies. Add content rating where fit. Here is the spec for content rating: contentRating property. Also add clear on‑page text for 18+, and link to help if a user has a problem with gambling.

Compliance corner: where casino markup goes wrong

First, align with Google spam policies for the web. Do not fake prices or star ratings. Do not cloak schema. Make sure visible content matches your code.

Second, do not try to show stars for your own Organization. The type exists, but Google will not show stars for self‑serving reviews. See the base type here: Schema.org Organization.

Third, follow local rules. If you serve the UK, see the UK Gambling Commission marketing and advertising rules. Add clear terms, age labels, and limits. Add a visible link to support such as BeGambleAware. This is good for users and good for trust.

Last, test on staging first. Then ship in small batches, and watch for alerts in your tools.

Measurement: prove the CTR lift

Use a simple pipeline:

1. Validate in Rich Results Test and Schema Markup Validator (see link in Appendix).
2. Request indexing for a sample of pages.
3. Wait for crawl. Then check Search Console.

In Google Search Console, open the Performance report. Filter by page groups (e.g., /reviews/, /bonuses/, /games/). Compare CTR before and after deploy. Split by country if you run multi‑region. Keep test windows stable (e.g., 28 vs 28 days).

When you test, do not cloak. Do not redirect bots to other pages. Google allows A/B in search if you do it right. See their note on tests: A/B testing in search. Keep content the same for users and bots. Use server‑side flags with equal fetch.

Track what you change. Good levers: add video with clean thumbs, fix breadcrumbs, correct logo, improve titles. If CTR moves, freeze the win. If not, roll back and try the next item.

Myth‑busting interlude

• Myth: Product schema will give bonus cards. Truth: It will not. Use Offer for structure only.
• Myth: FAQ always boosts CTR. Truth: Google cut FAQ for most sites in 2023. See this recap: FAQ rich results eligibility update.
• Myth: You can show stars for your brand with Review markup. Truth: Self‑serving stars are not shown. Avoid it.
• Myth: More schema is better. Truth: Better schema is better. Keep it relevant, clean, and honest.

30‑day rollout checklist

Week 1

• Audit current schema by page type. List errors and warnings.
• Pick targets: Homepage, top 10 reviews, 5 game pages, 3 bonus pages.
• Write JSON‑LD templates for WebSite, Organization, BreadcrumbList.

Week 2

• Add VideoObject to 3–5 key pages with good videos.
• Add ItemList to your top “Best casinos” page.
• Ship staging tests. Fix validator errors.

Week 3

• Deploy to production for batch 1. Request indexing.
• Set GSC filters by page folders. Add notes to your analytics.
• Review brand SERP for logo and search box.

Week 4

• Compare CTR vs. baseline. Check video impressions.
• Scale to next 20–30 pages. Document changes.
• Plan upkeep: monthly schema QA, policy checks, logo review.

Where an affiliate review site fits (a real slot for your case study)

Here is a clean way to show this in action. On www.gamblers-united.com, you can roll out a simple set: WebSite with SearchAction on the homepage, Organization + Logo site‑wide, BreadcrumbList on all key paths, and VideoObject on the best review pages. This set sits well with policy. It supports brand queries, and it helps users scan results fast. In our work, this mix tends to lift clicks on review pages once videos get indexed. Your exact numbers will vary by country and season.

To keep E‑E‑A‑T strong, add a short note on how you test. Explain that you compare CTR in GSC by page type, that you do not cloak, and that videos are made by your team with clear pros and cons. Add a line for 18+, and a link to help if someone needs it.

Appendix: validators, templates, QA list

• Schema Markup Validator: validator.schema.org
• Rich Results Test: search.google.com/test/rich-results
• Template pack: keep JSON‑LD snippets in your repo; lint on CI; block deploy on errors.

Final QA before publish:

• No schema errors; warnings are known and safe.
• Logo meets size and aspect rules; SameAs are high trust.
• Breadcrumbs match the visible path.
• Video has a clean thumb, chapters, and 18+ where needed.
• Offers have clear terms, dates, and regions.
• Pages show age labels and a RG link.

Why this approach fits Google HCU and E‑E‑A‑T

• It helps users first: clear paths, clear titles, and safe labels.
• It shows experience: real recipes, code, and ways to measure.
• It cites primary sources: Google and Schema.org.
• It sets limits: says what will not show, and why.

Changelog

• 2026‑06‑15: Updated table; added Clip in VideoObject; added UKGC link; clarified FAQ limits.