Troubleshooting

Browser pages are closed to every extension: chrome:// addresses, the Chrome Web Store and the pages of other extensions. The panel still opens on them and says so, because failing silently would leave you wondering whether the click landed. Open an ordinary http or https page and click the icon again.

There are two ceilings and they are different on purpose. On the automatic path, where the panel follows a navigation with no click from you, a page over 1,000,000 characters is not read, because an analysis nobody asked for may not cost whatever it costs. Your own click has no such ceiling: it runs up to the reader's own refusal at 20 million characters. So when this band appears, click the icon.

The browser grants access to a tab at your click, and it takes the grant away when that tab goes to another site. Coming back does not bring it back. Click the icon again on the new page. If you walk that site often, press the opt-in under the identity card: it asks for that one site by name, and after that every navigation there is read with no click at all.

A network failure and a lapsed tab grant are reported by the browser in exactly the same way, so we cannot tell them apart and do not pretend to. One sentence names both possibilities and gives the remedy, which is to click the icon again. When robots.txt is the one that failed, the indexability verdict also declares itself incomplete rather than assuming the page is open.

Some servers refuse HEAD requests. The panel then falls back to the headers of the request it made for the source HTML. If that one did not arrive either, the X-Robots-Tag counts as not read, and the verdict says so instead of treating the header as absent.

If the file answers 4xx, missing is the real answer: no file means no block, and nothing is wrong. The same goes for llms.txt, which gets no red badge when it is absent, because that file is not even a standard yet. A 5xx or a network failure is a different case and gets its own sentence.

INP measures how long the page takes to respond to an interaction, so until you click something there is genuinely nothing to measure. The row says that instead of showing a zero, which would read as a perfect score. Click a few things on the page, then click the toolbar icon again.

The panel writes out how long the tab has been open, and past two minutes it adds that sentence. The numbers have not gone wrong; they belong to a load that happened a while ago. Reload the page, then click the icon again to measure the fresh one.

It cannot: there is no API that reports the theme chosen inside DevTools. The panel carries its own setting instead, at the right of the title row, with the same three values: Auto, Light and Dark. It opens dark. Auto follows the browser and the operating system, not DevTools, so if you run DevTools forced to one theme, pick that same value here.

That state is what the overlay is built never to reach. If the page navigated away or the injected reader is gone, the panel says the page could not be reached and drops its own button back at the same moment. When the panel follows a navigation it also turns the overlay off rather than redrawing it, because the elements a mode framed may not exist on the new page. Press the button again there.

A side panel gets no reliable event when it closes, and a message sent to a document that is being torn down does not arrive either. So the marks stay until the page is reloaded or navigated away from, or until you click the toolbar icon again, which clears the page before reading it. Faking a clean exit with a timer would be worse than saying this out loud.

Only a Googlebot block earns a badge. Blocking GPTBot, CCBot or any of the others is a legitimate choice that many sites make deliberately, so the table reports the state and the rail stays quiet. The note under the table says the same thing.

The reader takes Disallow lines into account and ignores Allow lines. It over-obeys, which is the safe direction for a crawler, so a path that a Disallow closes and an Allow reopens shows as blocked. The section says this in two places rather than letting you find out later. It is a known limit, not a misreading of your file.

The browser wants the panel document focused before anything is written to the clipboard, and it can refuse. When it refuses, the label on the button does not change, so nothing ever claims a copy that did not happen. Click somewhere inside the panel and press the button again. The report is also selectable text under the disclosure, so you can copy it by hand.

The request for the source HTML was redirected to a different address. The two sides would not be the same document, so no comparison is made at all. Reporting no difference there would be wrong, and reporting a difference would be worse.

The panel follows the tab. A route change, a hash change, a same-site navigation or a reload is re-analyzed with no click. A neutral band then names the new address and says the results below belong to it, and it clears itself after six seconds. The identity card at the top of Summary always names the page the numbers belong to, so nothing on screen is ever unattributed.

No, that is the intended state. The four permissions it declares raise no install warning between them, and the optional entry adds nothing to the card or to the details page until you grant a site yourself. When you do, that site appears under site access, and pressing the same control again removes it.

The side panel needs Chrome or Edge 116 or newer. If your browser is older the panel cannot open, and there is no fallback. If the version is fine and the icon does nothing, open the extensions page and check that the extension is enabled and that its card carries no error badge.