An indexability checker tells you whether search engines are allowed to index a page, and if not, which setting stops them. For a browser game page that does not show up on Google, the seogeoaeo.ai Indexing & Canonical Checker is a quick first test: paste the URL and it names the tag, header or rule in the way.
Small game sites hit this more than you would think. Game pages are often built from one template, hosted on a subdomain or a game portal, and shipped fast, and that is how a stray noindex or a bad canonical slips through.
What an indexability checker looks at
Indexability is not one setting. It is a handful of signals that all have to agree. The seogeoaeo.ai checker reads each one for Google and Bing:
- Status code. The game page has to return a 200, not a 404, a server error or a redirect.
- robots.txt. A Disallow rule for Google's or Bing's crawler on your
/games/folder stops them from fetching the page. - Meta robots and X-Robots-Tag. A
noindexin the page's HTML or in the HTTP response header tells search engines to leave it out. - Canonical tag. If every game page declares the home page as its canonical, you have asked Google to index the home page instead. The checker also tests whether the canonical's target can be indexed.
- Snippet controls. Settings like
nosnippetandmax-snippetlimit how much of the page can be quoted in results and AI answers.
The result names the blocking signal and the exact tag or header to change. One run costs 8 credits.
Common game-site traps
| What happened | What the checker shows | Fix |
|---|---|---|
| Template copied from a staging site | noindex in meta robots | Remove it from the live template |
| All game pages share one canonical | Canonical points to another URL | Make each page canonical to itself |
| Game moved to a new URL | Redirect or 404 status | Update internal links to the new URL |
| robots.txt blocks the games folder | Disallow rule for Googlebot | Remove or narrow the rule |
What it does not check
Indexable is not the same as indexed. The checker does not query Google's index, and the tool page says so plainly. To see whether Google actually holds your game page, open Google Search Console, inspect the URL and read its status. You need access to the site's property for that, and Google limits how many URLs you can inspect each day.
The checker also does not run JavaScript. Many browser games render their title, description and controls with scripts. If the page HTML is nearly empty until the game loads, add the game's name and a short description to the HTML itself so crawlers have something to read.
When to use what
If you run your own site and have Search Console set up, URL Inspection is the source of truth for whether Google indexed a page. Use the seogeoaeo.ai indexability test when you want the reason a page cannot be indexed in plain terms, when you are checking a game hosted on a portal you do not control, or when you want to test a page before you set up Search Console at all.
After a fix goes live, run the check again. Then request indexing in Search Console if you have access; Google notes that the request does not guarantee the page will be indexed.