Potly.Win's entire business model runs on advertising revenue. 80% of what the platform earns from ads goes directly into prize pools. So when the biggest ad network in the world keeps telling you "no," it's not just an inconvenience — it's a direct hit on how much your players can win.
This is the story of our ongoing effort to get approved for Google AdSense, what we've tried, what we've learned, and how we're keeping the platform funded while we figure it out. If you're building an ad-funded project of your own, hopefully this saves you some headaches.
The Timeline So Far
ads.txt file in place, meta tags configured. We submit for review.robots.txt. We wait for Google to index the new pages.Why AdSense Keeps Saying No
The "low value content" rejection is Google's most common and most frustrating. It's vague by design — they don't tell you exactly what to fix. But after researching extensively and analyzing our situation, the root issue is clear: AdSense is built for content sites, and Potly.Win is primarily an application.
When Google's crawler visits our game pages, it sees HTML canvases, JavaScript, and minimal text. The actual "content" — the games themselves — is interactive and visual, not indexable text. From AdSense's perspective, these pages look thin even though they're the core product that players come for and engage with deeply.
Google's review criteria emphasize text-heavy, article-style content. They want to see expertise, authority, trustworthiness (what the industry calls E-E-A-T), and pages that provide informational value to visitors. A gaming platform provides entertainment value and competitive value, which is different from what their review team is trained to evaluate.
The irony: AdSense approval requires content that exists primarily to satisfy their reviewers, not our actual users. Our players come for the games and the leaderboards — they don't need 15 blog posts to find value in the platform. But Google does, so we write them.
What We've Done to Fix It
Built a real blog. Not filler content — genuinely useful articles about game strategy, platform mechanics, and the skill gaming space. Each post is 800+ words of original content written from direct experience building and running the platform. Google wants expertise? We're literally the people who built these games.
Added structured data. Every blog post has schema.org JSON-LD markup identifying it as a BlogPosting with author, publisher, and date information. The blog index has structured data for the full collection. This helps Google understand the content structure.
Set up proper SEO infrastructure. Sitemap.xml with all pages listed, robots.txt pointing to the sitemap, canonical URLs on every page, meta descriptions, Open Graph tags. We're making it as easy as possible for Google to crawl, index, and understand the site.
Internal linking. Blog posts cross-reference each other and link to game pages. Game pages link to their strategy guides. The homepage links to the blog. This creates a content web that demonstrates the site has depth beyond the game canvases.
The Alternative Ad Networks
While working on AdSense, we haven't waited around with empty ad slots. We've pursued several alternative networks to keep revenue flowing to prize pools.
AdSterra was the first network we integrated. The approval process was fast, but the experience was mixed. Their ad serving required significant Content Security Policy adjustments on our end — their scripts load from rotating CDN domains and use eval(), which meant opening up our CSP in ways we weren't initially comfortable with. We also discovered they were injecting pop-under ads that opened new tabs with dead landing pages, which is a dealbreaker for a platform that needs user trust. We disabled the aggressive formats but the creative quality for our traffic level has been inconsistent.
Media.net (the Yahoo/Bing contextual network) and CPMStar (a gaming-focused network) both have pending applications. CPMStar is particularly interesting because they specialize in gaming audiences and understand the context of browser-based games.
HilltopAds referral banners are currently running on the homepage as a bridge while we wait for other approvals. They're not high-CPM display ads, but they keep the ad slots active and generate some baseline revenue.
What This Means for Prize Pools
In practical terms, the AdSense situation means our prize pools are smaller than they should be right now. AdSense typically pays the highest CPMs for US traffic, and without it, we're leaving money on the table — money that would go directly to player prizes.
The March prize pools reflect this reality. They were funded by the ad networks we've been able to integrate so far, which don't have the same demand and CPM rates as Google's network. Once AdSense (or a comparable premium network) is live, the pools will jump significantly — even with the same player base.
This is also why growing the player base matters so much right now. More players means more ad impressions, which means more revenue per ad network, which means bigger pools. The ad network mix will improve over time, but player growth drives everything.
Lessons for Other Builders
If you're building an ad-funded platform that isn't a traditional content site, here's what we'd tell you:
Apply for AdSense later, not at launch. Have 15+ pages of substantial text content indexed before you submit. We applied too early and the rejections create a cycle of waiting, reapplying, and waiting again.
Don't rely on a single ad network. Apply to multiple networks simultaneously. Approval timelines vary wildly, and having revenue from any source is better than having empty ad slots while you wait for the ideal one.
Budget for the CSP headaches. Ad networks load scripts from unpredictable domains, use inline JavaScript, and sometimes require unsafe-eval. If you have a strict Content Security Policy (and you should), expect to spend time adjusting it for each network. Document every CSP change so you can roll them back if a network doesn't work out.
Check for aggressive ad formats. Some networks bundle pop-unders, redirect ads, or auto-play video with their display units. Test in multiple browsers and with ad blockers disabled. Your users will notice before you do, and the trust damage is real.
Where We Stand Now
As of early April, we have 13 blog posts, 6 content pages, a proper sitemap, structured data, and internal linking throughout the site. We're confident the next AdSense application has a strong chance of clearing their content threshold. In parallel, we're waiting on CPMStar and Media.net approvals.
We'll update this post when there's a resolution — approved or rejected again. Either way, the platform keeps running, the games keep paying out, and the prize pools keep growing. AdSense approval would accelerate everything, but it's not a blocker. The model works regardless. It just works better with premium ad partners.
If you're a player, the best thing you can do is keep playing with ads visible. Every impression counts, literally — it adds to the pool you're competing for. If you're a builder going through the same process, feel free to reach out. We're happy to share what we've learned.