AdSense and content readiness checklist
This public-safe operational page summarizes the core checks oeeco should pass before AdSense review or major promotion. It intentionally avoids secrets, private analytics, database credentials, and user data.
Current snapshot
19 blog posts
Target baseline: 18 or more original, topic-focused articles.
pub-5608004759418063
Google AdSense publisher id configured in the site shell.
4 topic hubs
Topic pages organize articles into creator, game, tool, and trust clusters.
6/6 checks
High-level readiness signals for policies, content, topics, discovery, ads, and product routes.
AdSense basics
- `ads.txt` should return the Google seller line for publisher id `pub-5608004759418063`.
- Blog pages should provide original explanatory content, visible author context, and internal links.
- Policy and trust pages should be reachable from the footer without requiring login.
- Ads should not be placed close to game controls, deceptive navigation, or primary interaction buttons.
Policy and trust pages
About
FAQ
Contact
Editorial Team
Editorial Policy
Submission Guidelines
Privacy
Terms
Discovery endpoints
Blog topic hubs
Creator submissions
Browser games
Interactive tools
Review and trust
Public product routes
Latest blog article
Latest article: What Are AI-Made Web Works?. Keep publishing focused articles as the platform adds new demos, review rules, and creator workflows.
Command-line check
Run `npm run check:site` to verify the live public routes, `ads.txt`, RSS, sitemap, and key page content signals. Run `npm run check:quality` to crawl sitemap URLs for title, description, canonical, noindex, thin-content, and login-wall issues before requesting or retrying AdSense review.