AE AutoEmbedGames

Quality assurance

Iframe Embed Validation Guide

Before you publish an HTML5 game page, confirm every iframe really tracks back to a playable document. This guide outlines the checks embedded inside AutoEmbedGames and the manual diagnostics teams can run in seconds.

Mobile-first review CORS-safe workflows Automation ready

Need a quick verdict?

Drop URLs into the Game Extractor and ensure the embed passes both iframe and document tests before it reaches your production CMS.

Iframe validation tool - Engineer testing HTML5 game embed code for CORS errors, security issues and mobile compatibility on dual monitors

Instant iframe validation

Paste an embed URL to see whether it delivers a playable document. The checker mirrors the logic in our automated extractor—only iframes backed by HTML or executable JavaScript will pass.

We recommend testing canonical iframe sources such as GameDistribution, CrazyGames, Poki, or your own hosted HTML5 bundles.

Validation runs through the AutoEmbedGames proxy with caching to avoid repeat fetches.
Enter a URL above to see the verdict.

Recent successful embeds

We keep the last five passes so you can copy verified snippets into your CMS.

    Core checks before approving an iframe

    Confirm structural requirements

    The iframe must be present in markup, and its src should point to a playable document rather than a static image. If the attribute is empty, check for alternate data attributes and normalise them to a real URL.

    AutoEmbedGames parses src, data-src, data-game, and similar fields. When a valid match is found, the system rebuilds the iframe tag and rejects image-only endpoints.

    Validate document responses

    We fetch each candidate URL, inspecting the payload for <html>, canvas elements, or executable scripts. Any response returning 4xx/5xx or a pure binary object is flagged and removed from the list of approved embeds.

    When you need extra assurance, open the URL in a separate tab and use DevTools network logs to confirm that the document successfully loads required JavaScript, WebGL, or Unity assets.

    Step-by-step iframe validation workflow

    Follow this checklist whenever you onboard a new publisher, build a bulk import script, or troubleshoot a suspect embed.

    1. Inspect source attributes

    • View page source and copy the iframe element. Ensure the src is absolute or resolve it against the page origin.
    • Look for hidden parameters such as gd_sdk or referrer values that signal third-party platforms like GameDistribution.
    • If the iframe uses a loader script, verify the manifest URL still resolves to a published build.

    2. Fetch the document safely

    • Use the AutoEmbedGames proxy or your own Cloudflare Worker to bypass CORS walls during validation.
    • Confirm the response contains HTML or executable JavaScript. Reject plain images, PDF files, or empty shells.
    • Record HTTP status codes. Anything outside 2xx/3xx should be escalated to your content ops team.

    3. Review runtime behaviour

    • Launch the iframe in an isolated window. Verify keyboard focus, pointer lock, and audio permissions work as expected.
    • Check console logs for blocked resources or mixed-content warnings.
    • Document whether the game requests fullscreen or additional scripts so you can pre-approve permissions.

    4. Archive validation evidence

    • Save screenshots or HAR files as proof of compliance for your QA repository.
    • Update the master entry in your Game Discovery & Filtering Tool dataset so teammates reuse verified embeds.
    • Schedule periodic rechecks for URLs hosted on external CDNs or partner domains.

    Automating validation with AutoEmbedGames

    Our latest extractor release pairs iframe detection with document-level heuristics, ensuring that only secure, playable embeds surface for your publishing pipeline.

    Smart candidate screening

    We exclude static assets, 4xx/5xx responses, and malformed URLs before they pollute your project backlog.

    Playable document detection

    Validation checks look for HTML shells, loader scripts, or JSON manifests so Unity and WebGL builds get the green light.

    Audit-ready exports

    Export validated embeds to JSON, then plug them into the Tutorials hub SOPs for production rollout.