Tools · Chrome extension

SEO & GEO Inspector

See any URL the way Googlebot and AI bots see it: what blocks it and on which robots.txt line, what JavaScript changes and why it isn’t indexable.

Add to Chrome, it’s free

Free · No sign-up · The extension has no analytics · English and Spanish

Interactive demo: click any tab

Real captures of the extension on elmundo.es, nachomascort.com and claude.ai.

No voiceover, real captures of the extension.

Everything it does

Indexing and crawling

Indexability lights Status, meta robots, X-Robots-Tag and canonical.
Redirects hop by hop JavaScript, meta refresh and HSTS too.
robots.txt with Google’s parser With the line that decides each bot.
Two-half icon Indexing and crawling as you browse.

Bots and AI

AI bots GPTBot, ClaudeBot, PerplexityBot and the rest.
Browse as a bot With its user agent or your own.
AI fan-out The searches ChatGPT, Claude and Perplexity run.
With and without JavaScript Side by side and with the full diff.

Content and performance

Core Web Vitals With the culprit element marked.
Readable schema Every entity as a tree, ready to copy.
Metadata and headings Title, description, Open Graph and H1 to H6.
Links Full table, rel and CSV.
Boilerplate by page type What repeats and what % is unique content.

International and SERPs

Hreflang with reciprocity Codes, x-default and links back.
Entities in SERPs The Knowledge Graph kgmids.
Top 10 entities What the top 10 results cover.
Volumes in Google and Trends With your DataForSEO account.

Four things you won’t find together in another extension

robots.txt read with Google’s parser, line by line

The extension reads robots.txt with the parser Google publishes as open source, Googlebot’s production code, compiled to WebAssembly. For each bot it tells you whether it can crawl the URL and which line decides it.

It does this for Googlebot and for the AI search and assistant bots: GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, PerplexityBot and the rest. Google-Extended doesn’t crawl: it is a token that decides whether Gemini can train on your site, and it is listed so you can see if you block it.

You can also browse a tab as any of those bots, or with your own user agent. It changes the user agent, not the IP: it shows whether the site serves something different depending on who asks, not how it treats the real bot.

elmundo.es blocks OpenAI’s three bots and PerplexityBot (with the line of each block) and lets Anthropic’s through.

The page with and without JavaScript, side by side

Many AI bots don’t run JavaScript: they see the HTML the server sends. One button opens a tab with both versions of the page side by side, and another view with the full diff of the server HTML against the rendered DOM.

The summary tells you which links, headings and text blocks only exist with JavaScript, which is what a bot that doesn’t render misses.

elmundo.es with JavaScript on the left and without JavaScript on the right — Without JavaScript, elmundo.es loses its games and paywall: that is what a bot that doesn’t render sees.

Summary and code diff for elmundo.es: links and headings that only exist with JavaScript — The diff marks what JavaScript adds in green and what it removes in red, with links and headings summarized on top.

The searches AI runs before it answers

While you use Claude or Perplexity, the extension collects the web searches the model runs to answer you (the query fan-out), grouped by question, to copy or export to CSV. With ChatGPT it works when you are signed in.

They are read from the responses your browser already receives: nothing is sent anywhere. Gemini and Google AI Mode don’t show their searches, so they can’t be captured.

An icon that splits indexing from crawling

The toolbar icon has two halves. The left one is indexing: red if there is a noindex (in the meta tag or the X-Robots-Tag header) or an error, amber if the canonical points to another URL. The right one is crawling: red if robots.txt blocks Googlebot.

You see what’s wrong as you browse. The number only shows up when there is a redirect or an error.

Indexable and crawlable All good.
noindex or error Meta robots, X-Robots-Tag or 4xx/5xx.
Blocked in robots.txt Googlebot can’t crawl it.
Canonical to another URL The number shows the redirect.

Two greens, all good. When a half changes color, you know whether the problem is indexing or crawling.

Everything I check on a page, in one click

A warning when JavaScript changes what matters

Compares title, description, canonical, robots, H1, headings, links and word count between the server HTML and the rendered page, and flags what changes.

See it in the demo

Schema you can read

Every JSON-LD entity as a tree, with its type highlighted and a button to copy it. It flags broken JSON and schema that only shows up with JavaScript, and opens the Rich Results Test with the URL filled in.

See it in the demo

Hreflang with reciprocity

Validates the codes, flags a missing self-reference or x-default and checks that every version links back to the others.

See it in the demo

Core Web Vitals with the culprit marked

LCP, CLS, INP, FCP and TTFB for your visit, with the LCP phases so you know whether the problem is the server, the resource load or the paint. One button boxes the LCP element, the shifting elements and the slowest interaction on the page.

This is data from your visit in your browser, not from real users (CrUX).

See it in the demo

elmundo.es with the LCP element and the block causing CLS boxed — The LCP element and the block causing CLS, boxed on the page.

Every link, where it points and its rel

A table with every link on the page, filterable by internal or external and by rel (nofollow, sponsored, ugc), and exportable to CSV. On the page itself, a colored dot on each link by its rel.

Links table for elmundo.es with text, URL, type and rel — The 465 links on the elmundo.es homepage, filterable and exportable.

Entities and volumes in Google and Trends

On every Google search, a box with the Knowledge Graph entities that show up in the SERP, with their kgmid and a link to Wikidata. With your DataForSEO account it adds the monthly volume, CPC and 12-month trend of the search and its related searches. On Google Trends, the volume of the terms you compare and, when you hover over the chart, the real searches for each month.

You pay DataForSEO only for what you look up, and each volume is cached for 30 days. With a Google Natural Language API key, it also extracts the entities the top 10 results cover.

Google search for softonic with the extension box: the Softonic entity with its kgmid and the volume of the search and its related searches — softonic: 14,800 searches a month in Spain, plus the volume of every related search.

Google Trends comparing softonic and uptodown: the tooltip for the week of February 22–28 adds 14,800 and 12,100 searches in February 2026, and the extension box shows each term’s monthly volume — Trends shows interest from 0 to 100; the extension adds how many searches that is, month by month, right in the tooltip.

Who built it

Built by Nacho Mascort

SEO, AI & growth consultant · Barcelona, working remotely

It is what I check on every page when I run an audit, now in one click. I have worked in technical SEO since 2014: I led SEO at Softonic, with over 1 billion users a year, and at word.tips.

Version 0.2.0 · Updated on October 22, 2026

0.2.0: Boilerplate by page type: which zones repeat as template and what % of each page is unique content.
0.1.0: First version.

Nothing leaves your browser

The extension has no server and collects no usage data: everything is computed in your browser. The only exception is your choice: if you add your DataForSEO account, volume lookups go from your browser to DataForSEO.

It never makes requests to your local network (routers, private IPs), not even when a site redirects to them.

Extension privacy policy

If you’d rather not install anything, several checks are available as web tools: the robots.txt tester, the bot access checker and the redirect checker.

FAQ

Frequently asked questions

Can't find your question? Email me at [email protected] and I'll reply within 24 hours.

Is it free?

Yes, all of it, with no sign-up. The only thing that can cost money is search volume, because it comes from your own DataForSEO account: you pay DataForSEO only for what you look up, and the extension caches each volume for 30 days to avoid repeat lookups.

How is it different from other SEO extensions?

Other extensions tell you whether a URL is blocked. This one uses Google’s official parser and tells you which robots.txt line decides it, for Googlebot and for every AI bot. It also shows the page with and without JavaScript side by side, with the full diff, and its icon tells you at a glance whether the problem is indexing or crawling.

What data does it collect?

None. No accounts, no analytics, no server of its own: everything runs in your browser. If you add your DataForSEO credentials, they stay in your browser and the calls go straight from your computer to DataForSEO.

Why does it ask for access to all sites?

To record the redirects and headers of each page you visit, download its robots.txt and unrendered HTML, and check the hreflang of the other versions. Those requests leave your browser and their results are not sent anywhere. Each permission is explained in the privacy policy.

When will it be on the Chrome Web Store?

It’s already submitted for review on the Chrome Web Store. Once Google approves it, the button above will link to the listing. In the meantime, the robots.txt tester, the bot access checker and the redirect checker work as web tools.

Let's talk

Would you rather have someone look at it for you?

Tell me what you want to achieve and I'll tell you honestly whether I can help.

What happens next

Reply within 24 business hours.
30-minute call.
Fixed proposal with scope and price.

Prefer to talk? Book a 30-min call
Or email me at [email protected]