A programmatic casino-list fleet: from zero to about 3,000 domains in 26 GEOs
We built and run a fleet of casino-comparison sites generated from a page plan per GEO and language, researched and checked by AI agents, deployed on Cloudflare's edge, and grown on a Google Search Console feedback loop.
Under NDA: no domains, brands, casinos, partner links or account details are shown. GEOs are labelled by country only.
≈3,000
domains built since March 2026
2,962 registered · 2,880 live today
≈1,500
first-time deposits (FTDs) in the last 2 months
from partner reports, not from GSC
organic clicks per month, May → October
Google impressions, May – mid-November
26 GEOs · 20 languages
Starting point and challenge
In March 2026 the fleet did not exist. The goal was organic first-time depositors across many casino markets at once, including Tier-1 GEOs, without a content team per country.
The hard parts: one site per keyword and market does not scale by hand; casino facts (licences, bonuses, payment methods) change and differ by country; gambling advertising law differs by GEO; and thousands of new domains have to be indexed and earn links from nothing.
What we built, and why
A page plan per GEO and language. Each market gets a keyword root, a set of page types and semantic blocks (reviews, bonuses, payment methods, games, safety, FAQ) in the local language, with hreflang across language versions. One plan drives hundreds of domains, so a change to the plan improves the whole market at once.
Research by AI agents, into a shared fact store. Small, cheap research agents collect casino and bonus facts per market and write them to one database, so the same casino is not researched twice and every page reads the same source.
A legal check per market. A dedicated compliance agent reviews claims and wording against each GEO's gambling-advertising rules; restricted phrases are rejected before anything is published.
Generation with quality gates. Pages are generated as schema-validated structured output, then pass fact checks against the store, SEO and technical audits (canonicals, hreflang, structured data, sitemaps), and a review agent before release.
Edge deployment. Sites are served by Cloudflare Workers with content in Workers KV: no servers per site, staged releases, and a canary before a change reaches the full fleet.
A cross-site link campaign. Contextual link blocks, written per page and language, are placed on donor pages inside the fleet, so each new site starts with relevant internal-network links in its own market.
A GSC growth loop. Every domain is verified in Google Search Console automatically; clicks, impressions, queries and URL-inspection results are pulled daily and decide what we build next: which GEOs get more domains, which pages get expanded, which sites get links.
Why this way: the cost of a site is close to zero once the plan, the fact store and the gates exist, so the fleet can test many markets and keywords and then put money where Search Console shows demand. The quality gates are what make that safe at this volume.
Results
All charts below come from the Search Console data of every live domain, grouped by the GEO each site targets. Data through 14 November 2026; November is a partial month.
Organic clicks per month, whole fleet
Google Search Console clicks · Nov = 1–14 Nov
Impressions per month
Google Search Console impressions
Domains deployed per month
New sites going live, March – November
By GEO, monthly
Sorted by clicks. Each row's line shows that GEO's monthly clicks, May to November.
Links
Key insights
Breadth first, then depth. Many GEOs were opened cheaply; Search Console then showed where demand turns into clicks. Five markets (Brazil, Poland, Romania, the UAE, Spain) now bring 85% of the clicks, and they get the next domains and links.
Impressions lead clicks by about two months. Impressions climbed from June to August; clicks followed from September as pages moved up. New sites need patience, and the loop has to measure both.
Indexing is the first gate at scale. Of the pages we inspected through the URL Inspection API, 83% are indexed (12,391 of 14,910). Automated verification, sitemaps and internal links matter more than any single page.
Facts in one store, checked before release, keep thousands of pages consistent and let one correction reach every site that mentions a casino.
Our part
We designed the architecture and wrote the tooling ourselves: the page plans and semantic blocks per market, the agent pipeline and its gates, the Cloudflare deployment, the link campaign and the Search Console sync and dashboards. We set the GEO priorities from the data and run the fleet day to day.
Data and method notes
Sources. Link counts: the pipeline's link-building log; placement confirmed by the operator. Clicks and impressions: Google Search Console, synced daily for every live domain, May 1 – Nov 14, 2026, grouped by each site's target GEO. Domains, deployments, indexing: the fleet's own pipeline database. FTDs: affiliate partner reports, as given by the operator; they are not in Search Console and are not split by GEO here.
Withheld under NDA. Domain names, brands, casino names, partner and tracking links, and account identifiers. Small GEOs are shown as they are, with no rounding.