Start a project

Tool 01 of 194 · Indexing

Indexability Checker

Find out whether a page can be indexed and, if not, which signal stops it, with every signal checked in the order search engines apply them.

Use the tool All developer tools Live · free
Indexability Checker at a glanceIllustration: 1, A URL or pasted page; 2, processed in your browser; 3, Google vs Bing verdict.Indexability Checker1A URL or pasted page3Google vs Bing verdict2In yourbrowser
1 A URL or pasted page 2 processed on your device 3 Google vs Bing verdict

Indexability Checker

Page to check

Fetch sends this address to leej.uk, which reads the page once as LeejTools/1.0 and keeps only a count. Or paste below: pasted text never leaves your device.

What the check reads (filled by Fetch, or paste your own)

Verdict

    Signal (in the order they apply)GooglebotBingbotDetail

    What to fix

      Redirect hops

      #URLStatusLocation
      Report (JSON)

      Want the AI crawler view of your whole site? Run PingAI, which scores how well ChatGPT, Claude, Perplexity, Gemini and Copilot can reach and read it.

      01

      What it does

      Combines status, redirects, robots.txt, meta robots, X-Robots-Tag, canonicals, sitemap and hreflang into one verdict for Googlebot and Bingbot.

      • One verdict each for Googlebot and Bingbot
      • robots.txt, status, X-Robots-Tag and meta robots in precedence order
      • Canonical conflicts: several, in body, header vs HTML
      • Sitemap listing and hreflang self-reference

      02

      Private by design

      Everything you paste or upload stays in your browser. Only when you press Fetch does leej.uk read the address you give, once, as LeejTools/1.0, keeping nothing but a daily count.

      03

      What you get

      A verdict per crawler and a JSON report, with a Copy and a Download button on every result.

      • Indexing
      • noindex
      • Canonical
      • robots.txt

      Why it matters

      'Discovered, currently not indexed' and 'Excluded by noindex' usually come from signals fighting each other: a canonical pointing somewhere else, a noindex set by a CDN header, a sitemap listing a URL that redirects. Developers check them one at a time in DevTools, curl and a robots tester, and miss how they interact.

      This checker reads them all at once and applies them in the order crawlers do. A page blocked by robots.txt can't have its noindex seen; a page with two different canonicals has both ignored. It tells you whether the page can be indexed, and which signal to fix first. Whether it actually is indexed depends on quality and links, which no outside tool can promise.

      How it works

      1. InputA URL, or headers, HTML, robots.txt and sitemap
      2. In your browser16 signals applied in the order search engines use
      3. OutputA verdict per engine and the signal that decides it

      Where it fits in a designer's workflow

      1. Plan
      2. Design
      3. Build
      4. Test
      5. Launch
      Finding out why a page isn't indexed.

      By the numbers

      Verdicts on the sample page's indexing signalsok (Googlebot): 4 of 10; note (Googlebot): 1 of 10; mixed (Googlebot): 4 of 10; not reached (Googlebot): 1 of 10; blocks (Bingbot): 1 of 10ok (Googlebot)4 of 10note (Googlebot)1 of 10mixed (Googlebot)4 of 10not reached (Googlebot)1 of 10blocks (Bingbot)1 of 10
      Read from this tool's output on its sample page: 10 signals checked in the order search engines apply them. One header blocks Bing but not Google, and four canonical, sitemap and hreflang signals point at a different URL, so Google may index the page under another address. Source: Google: block indexing with noindex; Google: consolidate duplicate URLs.
      Show the numbers as a table
      SignalGooglebotBingbot
      2. Blocked by robots.txtokok
      3. HTTP statusokok
      4. Redirectsnotenote
      6. X-Robots-Tag noindexokblocks
      7. Meta robots noindexokok
      11. Header and HTML canonicals disagreemixedmixed
      12. Canonical points elsewheremixedmixed
      13. noindex and canonical togethernot reachedmixed
      14. Sitemap listingmixedmixed
      15. hreflang self-referencemixedmixed

      How to use it

      1. Enter the page address and press Fetch, or paste its response headers and HTML.
      2. Read the verdict for Googlebot and Bingbot.
      3. Work down the signal table: earlier rows win over later ones.
      4. Fix what's listed, then check again and download the report.

      FAQ

      Why do Googlebot and Bingbot get different verdicts?

      Robots meta tags and X-Robots-Tag headers can name one crawler (googlebot: noindex), and robots.txt can have a group for each. The tool applies each crawler's own rules.

      Does 'Indexable' mean the page is in Google?

      No. It means nothing technical stops it. Use Search Console's URL Inspection to see whether Google has indexed it.

      Why is noindex 'not reached'?

      When robots.txt blocks crawling, the crawler never downloads the page, so a noindex on it is never seen. Unblock it in robots.txt if you want the noindex to work.

      What does it send to leej.uk?

      Only when you press Fetch: the address, which leej.uk reads with the LeejTools crawler, plus robots.txt and up to three sitemap files on the same site. Nothing is stored except a daily count. Pasted text never leaves your device.

      Work with me

      Want a site that gets these right?

      I build fast, accessible websites and web apps that pass these checks from day one. Tell me about your project and I'll reply personally with honest next steps.

      Start a project What I do

      All developer tools · Back to leej.uk