Structured data research entity SEO semantic visibility iGaming knowledge systems
Independent technical publication Sources checked Oct 26, 2026
Entity registry & intelligence desk
Research on JSON-LD, Schema.org implementation, entity relationships and validation patterns for casino and sportsbook websites, checked against Google's own documentation.
| # | Entity name | Type | Status |
|---|---|---|---|
| 1 | Verdant Crown Casino | Organization | Valid |
| 2 | Verdant Crown | WebSite | Valid |
| 3 | Verdant Crown player support | ContactPoint | Valid |
| 4 | Slots lobby | CollectionPage | Valid |
| 5 | Slots breadcrumb | BreadcrumbList | Valid |
| Primary type | Organization |
|---|---|
| Linked by @id | contactPoint |
| Key properties | name, legalName, url, logo |
| Status | Valid |
A practical guide to describing casino and sportsbook brands as consistent entities, with entity maps, identity rules and what changed in Google Search from 2023 to 2026.
Read the guideBrand, operator and parent group in casino Organization markup.
Read moreWhich reviews can carry markup, and why self-serving stars fail.
Read moreWhat FAQPage markup still does after FAQ rich results ended.
Read moreBreadcrumb trails for lobbies, games, fixtures and help centers.
Read moreKeeping brand facts aligned across domains and market editions.
Read moreKey Schema.org types and entity categories for iGaming websites.
A layered approach to structured data, entity SEO and how search systems read a site.
Correct implementation and adherence to Schema.org definitions.
Aligned entity facts across pages, sections and external profiles.
How entities connect across brands, content and external data sources.
Reusable markup patterns for large casino and sportsbook sites.
Common errors, warnings and how to fix them.
What Google says AI features need from a page, and what they do not.
Hierarchy, trails and navigation markup.
Bylines, dates and author entities that match the page.
Browse and search entity records, markup types and checklist results. All data is illustrative: fictional brands on reserved .example domains.
| # | Entity name | Type | Industry focus | Status |
|---|---|---|---|---|
| 1 | Verdant Crown Casino | Organization | Casino | Valid |
| 2 | Verdant Crown | WebSite | Casino | Valid |
| 3 | Verdant Crown player support | ContactPoint | Casino | Valid |
| 4 | Slots lobby | CollectionPage | Casino | Valid |
| 5 | Slots breadcrumb | BreadcrumbList | Casino | Valid |
| 6 | Payments questions | FAQPage | Casino | Valid |
| 7 | Verdant Crown on its own reviews | Organization | Casino | Review |
| 8 | Safer gambling page | WebPage | Casino | Valid |
| 9 | Northwake Sportsbook | Organization | Sportsbook | Review |
| 10 | Northwake | WebSite | Sportsbook | Valid |
Verdant Crown Casino
Organization · Casino
Primary brand entity for a fictional online casino brand licensed in Great Britain and registered in Ontario.
| name | Verdant Crown Casino |
|---|---|
| legalName | Verdant Crown Gaming Ltd (fictional) |
| url | https://verdantcrown.example/ |
| logo | https://verdantcrown.example/media/logo-512.png |
| sameAs | 2 values |
| contactPoint | Reference: https://verdantcrown.example/#support |
| @type | Organization |
|---|---|
| @id | https://verdantcrown.example/#org |
| name | Verdant Crown Casino |
| legalName | Verdant Crown Gaming Ltd (fictional) |
| url | https://verdantcrown.example/ |
| logo | https://verdantcrown.example/media/logo-512.png |
| sameAs | 2 values |
| contactPoint | Reference: https://verdantcrown.example/#support |
{
"@context": "https://schema.org",
"@type": "Organization",
"@id": "https://verdantcrown.example/#org",
"name": "Verdant Crown Casino",
"legalName": "Verdant Crown Gaming Ltd (fictional)",
"url": "https://verdantcrown.example/",
"logo": "https://verdantcrown.example/media/logo-512.png",
"sameAs": [
"https://social.example/verdantcrown",
"https://video.example/@verdantcrown"
],
"contactPoint": {
"@id": "https://verdantcrown.example/#support"
}
}A complete brand node: name, url, logo, sameAs and a contact point that matches the contact page.
Illustrative data. Status comes from SchemaReel's local checklist, not from Google.
A place to practice reading structured data. Results come from a local checklist, not from Google's tools.
Example loaded. Edit it or paste your own JSON-LD, then check.
| Type | Google Search feature | What the checklist does |
|---|---|---|
| Organization | Logo and administrative details; no required properties | Asks for name, url and logo; notes sameAs; warns on self-serving ratings |
| WebSite | Site names (home page only). Sitelinks search box retired in November 2024 | Requires name and url; notes SearchAction is unused |
| Article | Article understanding; no required properties | Asks for headline, author, datePublished; notes time zones and images |
| BreadcrumbList | Breadcrumb trail, desktop results only | Requires two or more ListItems with position, name and item |
| FAQPage | No longer shown since May 7, 2026 | Adds a note; checks Question and Answer structure |
| Review, AggregateRating | Review snippets for supported item types; self-serving reviews excluded | Asks for author, rating and item; counts for aggregates |
| Person, ContactPoint | Used inside other markup, such as article authors and organization contacts | Asks for name and a link; a contact channel |
| SiteNavigationElement | No documented Google feature | Adds a note |
Sources: Google Search Central structured data documentation and the Search Central documentation updates log, both read on October 26, 2026. See Google structured data changes, 2023 to 2026.
| Type | Name | @id | Path |
|---|---|---|---|
| Organization | Verdant Crown Casino | https://verdantcrown.example/#org | (top level) |
| ContactPoint | contactPoint |
Draw these links as a diagram in the entity map.
<script type="application/ld+json">.Organisation is not a Schema.org type; Organization is.More detail in structured data validation errors.
Sample: Organization (casino brand)
0 errors, 0 warnings, 0 notes
Our approach to iGaming entity research and analysis.
Identify the template: home page, game page, article, help page.
Define the primary and related entities with Schema.org types.
Read the existing structured data and note gaps or conflicts.
Check syntax, then Google requirements, then the visible page.
Follow @id links and sameAs to see how entities connect.
Write dated, sourced guidance with its limits stated.
Implementation guides, checklists and research notes.
A complete guide to JSON-LD on casino and sportsbook templates, with examples, validation tips and common issues.
Read more
How to describe games, software providers and game collections with Schema.org, without inventing facts.
Read more
Key entities, content structure and validation patterns for sportsbook brands.
Read more
A checklist for auditing entities and markup on casino and sportsbook sites, step by step.
Read more
Send the editors a correction, a source or a question. A person reads every message.