Casino Indexation Diagnostic Workflow

The five places a URL can drop out

Once the cause is fixed, the technical SEO checklist helps stop it recurring across templates.

Every missing page has fallen out at one of five stages. Diagnosing in this order saves time, because a failure at an early stage makes later checks meaningless.

Before you start: access you need

Real diagnosis needs Search Console access to the property. A Domain property "includes all subdomains (m, www, and so on) and multiple protocols", and DNS is the only way to verify one. For a group running casino, sportsbook and poker on separate subdomains, a Domain property gives one view of all of them; URL-prefix properties per subdomain give cleaner per-product reports. Many teams keep both.

Without access, you are guessing. External tools and the site: operator cannot confirm index status. Google's own documentation says of site:: "The list of URLs returned is not always exhaustive", and it "doesn't necessarily return all the URLs that are indexed under the prefix specified in the query."

Stage 1: discovery

Look up the URL in URL Inspection. If Google reports it as unknown, it has not been discovered. Check three routes:

• Internal links. Is there at least one crawlable <a href> link to it from a page Google already crawls? Lobby tiles rendered only after a click or scroll event may not count. See our orphan pages guide.
• Sitemaps. Is it in a submitted sitemap with an absolute canonical URL?
• Logs. Has verified Googlebot ever requested it?

If the Page indexing report lists it as "Discovered - currently not indexed", Google's help text says "the page was found by Google, but not crawled yet", and "typically, Google wanted to crawl the URL but this was expected to overload the site." Large numbers of these on a big platform point toward crawl budget and server capacity.

Stage 2: crawl access

Run a live test in URL Inspection. Google describes it as fetching and examining "the URL in real time." Check:

• Not blocked by robots.txt. Test the exact path with our robots.txt rule explorer or Search Console's robots.txt report.
• HTTP 200 for the final URL, with no redirect chain.
• No geo-block, age gate interstitial, bot challenge or login wall for Googlebot. Google's locale-adaptive pages guide notes that "the default IP addresses of the Googlebot crawler appear to be based in the USA" and that it sends requests "without setting Accept-Language". A brand that blocks US traffic for licensing reasons must decide deliberately how crawlers are handled, and must not show crawlers different content from users.
• Server and CDN logs show 200 responses to verified Googlebot, not 403 or 429.

Stage 3: rendering

In the live test, open "View tested page". Google says the HTML tab "shows the rendered HTML for the page", and a screenshot is available "only in a live test with a successful test result." Confirm that the main content, the H1, the internal links and the canonical tag are present after rendering. If the game grid, event list or promotion text appears only after a user interaction, Google may not see it; our JavaScript rendering guide explains why. Our rendering test sets out a reproducible check.

Stage 4: canonical selection

URL Inspection shows the user-declared canonical and the Google-selected canonical. If they differ, the page is in a duplicate cluster and Google prefers another URL. The Page indexing report labels this "Duplicate, Google chose different canonical than user". Our canonical guide covers causes on game pages. Be patient after fixing: Google's troubleshooting guide says it "might hold pages in a duplicate cluster for up to two weeks" even after the content issue is fixed.

Stage 5: the index decision

If the page is crawled, rendered and canonical but still "Crawled - currently not indexed", Google's help text says it "may or may not be indexed in the future; no need to resubmit this URL for crawling." At this point the question is usually value: is the page substantially different from thousands of similar pages on your site and others? A game page with only the provider's stock description, or a city landing page that swaps one word, gives Google little reason to index it. Improve the page itself before asking again.

Two checks to rule out first: a noindex you did not intend (in the meta tag, an X-Robots-Tag header from the CDN, or one added by JavaScript), and a soft 404, where the page returns 200 but looks empty or like an error page.

Requesting indexing and using the API

Request indexing after a real fix, once. Google's recrawl page says "requesting a recrawl multiple times for the same URL won't get it crawled any faster" and that crawling can take "anywhere from a few days to a few weeks". There is also a daily quota. For checking many URLs, the URL Inspection API allows 2,000 queries per day and 600 per minute per site, according to Google's API limits page. That is enough to monitor a few thousand priority URLs on a rotating schedule.

Record what you find

A dated record like this lets the next person see what was tested, what was assumed and what changed, which is what makes the diagnosis repeatable.

Questions technical teams ask