kursor.live: SEO, GEO and analytics for an odds comparison site, connected to its team by API
kursor.live puts the odds of 13 licensed bookmakers for the same bet on one page and adds tools for serious bettors: a value-bet scanner, surebets, AKO coupons and odds-drift alerts, sold by subscription. We run its SEO, GEO and analytics in Firecrux Digital Intelligence, and our systems talk to each other: technical issues and content changes reach the kursor.live team by API.
addresses in the sitemap, now only the pages worth indexing
requests from AI bots and from Googlebot in one week
requests from fake Googlebots in five days, caught in the logs
improvements to three guides in the Academy
The challenge
A new site with tens of thousands of pages: matches, leagues, teams and players. Most of them reached Googlebot as empty JavaScript shells, 27 to 36 words and no H1, so when we started Google had indexed 2 of them.
82% of the sitemap were player pages, the football hub changed its address every day, and the site shared its Google Analytics property with a mobile game, so nobody could say which visits led to a subscription.
What we built
- An audit of rendering and structure: server-side rendering for the pages that earn, leagues as permanent hubs, dates as a filter, and a sitemap of only the pages worth indexing.
- Measurement from scratch: a GA4 property of its own and a Tag Manager container fed by the product’s funnel, from the scanner to the paywall, with purchases sent from the backend and a cookieless beacon that counts consent.
- Weekly technical reports: match pages that grow to 1.8 MB on match day, soft 404s, structured data for sports events, and the fake Googlebots that probe the site for config files.
- Content for the Academy: three guides, on surebets, expected value and AKO coupons, were stronger than anything in Google’s top results, the only ones counting odds after the 12% tax, but did not use the words people search for. 73 suggestions fixed that.
How it works
- AI bots read the site far more than Google: in one week ClaudeBot and Amazonbot made 6,053 requests, Googlebot 58. Server logs show which bot reads which page and which bots are fakes. We explain why it matters in how AI answers pick their sources.
- Pages are built to be quoted: a direct answer near the top, the evidence in the text, and structured data on every match.
- Our systems are connected through the Firecrux API: each technical issue lands in the kursor.live team’s tools and its status comes back, content changes are approved from there, and reports arrive with them.
Results
- The sitemap went from 31,287 addresses to 988, split into five maps.
- The football hub has a permanent address, and visits to broken team links fell from 94 a day to 7.
- Subscriptions, the paywall and the product’s funnel are measured in GA4, with consent counted separately.
What comes next
Rendering the match and league pages for bots, then tracking how often AI assistants name kursor.live when people ask about comparing odds, surebets and value bets.