How We Curate the Catalog

Last updated: May 2026

This page describes how a game enters the Game Hub Arena catalog, what review applies, how content ratings are assigned, and how the catalog is maintained over time. The five-stage workflow:

Stage 1: Source feed identification

Games enter the catalog from several channels:

CloudArcade-compatible game feeds. The CloudArcade CMS supports importing from established HTML5 game-distribution networks via XML/JSON feeds. New game additions to these feeds are reviewed for catalog inclusion.
GameDistribution.com — one of the largest HTML5 game distribution networks; provides a feed with thousands of legitimately-distributable games with developer attribution preserved.
GameMonetize — another major HTML5 game distribution network with similar feed integration.
Itch.io public-API content — where Itch.io developers have configured their HTML5 games as portal-distributable.
Direct developer submissions — HTML5 game developers submitting their games for inclusion via info [at] gamehubarena [punto] fun with subject line Game submission.

The full source-feed list and licensing context is on Game Sources & Licensing.

Stage 2: Game review for catalog fitness

For each game candidate, the review evaluates:

Technical fitness. The game runs reliably in modern browsers; no broken functionality, no broken links to game assets, no dependencies on deprecated browser features.
Family-friendly fit. The game's content is appropriate for the catalog's family-friendly default, OR is appropriate at a higher content-rating tier with proper flagging.
Content-standards compliance. The game does not contain real-money gambling, sexual content, content sexualizing minors, or other categorical exclusions per Content Standards.
AdSense-policy compatibility. The game does not push the catalog into AdSense-restricted territory (no real-money gambling, no adult content, no malware-adjacent behavior).
Developer attribution. The developer / studio credit is preserved and identifiable.
License clarity. The game is being legitimately distributed through the source channel, with the original developer's permission.

Games failing any criterion are not added to the catalog.

Stage 3: Content rating application

Each cataloged game gets a content rating per Content Ratings:

All Ages — suitable for the youngest players including ages 4+. No violence, no scary themes, no language concerns.
General Audience — mainstream casual games appropriate for general audiences including school-age children.
Teen — cartoon violence, mild combat, age-appropriate competitive themes for 13+.
Older Teen — substantial violence, more intense combat, dark themes; for 16+.
Adult — very limited; reserved for genuinely-adult-content games that we may carry only with strong filtering. Most "Adult" games are excluded entirely.

The rating is applied conservatively — when in doubt, we apply the higher tier.

Stage 4: AdSense compliance check

Each cataloged game is checked against AdSense's content-policy framework:

No gambling content. Casino games, slot games, betting interfaces, real-money games are categorical exclusions.
No adult content. Sexual content, suggestive imagery beyond mainstream-game-art conventions, dating-simulation with explicit content.
No malware-adjacent behavior. Games that prompt unexpected downloads, phishing-pattern overlays, deceptive UI patterns are excluded.
No content sexualizing minors. Categorically and unequivocally excluded.
No content promoting real-world hatred against protected groups.

The check protects the AdSense publisher account and the family-friendly portal positioning. Full framework on AdSense Compliance.

Stage 5: Publication and ongoing maintenance

Publication includes:

Game-page generation through CloudArcade with title, developer credit, source-feed identification, content rating, genre tags, embedded gameplay frame.
Category assignment (action, puzzle, sports, etc.) for discovery.
Sitemap inclusion (the Site's sitemap-games.xml).
Internal-linking integration with related-games suggestions.

Post-publication maintenance:

Reader feedback may surface technical issues (game broken in current browsers), content concerns (rating dispute), or attribution issues. The corrections framework is on Corrections & Removal Policy.
Periodic catalog audits identify games that have stopped working (developer-removed assets, source-feed changes) and either restore working state or remove the entry.
Takedown response per DMCA — rights-holder takedowns processed within 3 business days of valid notice.
Source-feed changes — where a source feed adds or removes games at scale, the changes are reviewed and the catalog adjusted.

What this workflow does not promise

It does not promise zero errors. 10,000+ games at scale will contain edge cases that pass review and need post-publication correction.
It does not promise comprehensive coverage of every HTML5 game ever made. The catalog focuses on legitimately-distributable games through the source channels we use.
It does not promise that game functionality will be maintained. Games depend on developer-side asset hosting; where assets become unavailable, games may stop working.
It does not promise defense against rights-holder takedowns. Where rights are claimed, we honor takedowns and apply counter-notice mechanisms for disputes.

Reader feedback on catalog quality

Reader feedback is the primary mechanism for catching catalog issues. Email info [at] gamehubarena [punto] fun with:

Game-page metadata corrections (wrong developer credit, wrong genre, wrong content rating).
Catalog requests (games not yet included).
Content-rating disputes (rating you believe is too lenient or too strict).
Technical issues (game broken in current browsers).
Inappropriate-content reports (use abuse [at] gamehubarena [punto] fun).
DMCA / rights-holder takedown requests (use dmca [at] gamehubarena [punto] fun).