Troubleshooting

Symptom, cause, and a way to tell which cause it is

The loader is built never to break the page it sits on, which means it fails quietly on purpose. That is right for a live site and unhelpful when you are the one debugging it, so these pages exist to make the quiet failures legible. Every cause on them is a real branch in the product, and every one carries something you can observe before you change anything.

It will not appear

It answers wrongly, or not at all

What was indexed, what was not, and why a refusal is sometimes correct.

It is running but something is off

Two things that solve most of these

Open the browser console before anything else. The loader says nothing on the page and quite a lot in the console, and three of the failures above name themselves outright there.

Then wait a minute. The configuration that carries the appearance, the status and the allowed sites is cached for that long, so a change made seconds ago has genuinely not taken effect yet, and chasing that is how an afternoon disappears.

24 failure modes documented.