Comprobador de indexabilidad: ¿puede Google indexar esta página?

Search Console says "Excluded by noindex" but the live page looks fine in your browser. Or the URL ranks nowhere and you are not sure whether the problem is crawl, index, or content. Indexability is whether a page can be indexed from technical signals. Indexed is whether Google chose to keep it. Crawlable is whether Googlebot is allowed to fetch it. Three different questions. This guide walks the order a crawler meets signals, the robots.txt versus noindex trap, canonical mistakes, and how to combine URL Inspection with the Indexability Checker . The checker answers can it be indexed from two server fetches. It does not replace the Google Index Checker or the Page indexing report for what Google already did. ! Three steps: fetch page and robots.txt, read indexing signals, output verdict conflicts and fixes Crawlability vs indexability vs indexed Crawlability is governed first by HTTP reachability and robots.txt . If Googlebot is disallowed for the path, it may never download HTML to read meta tags. Indexability adds on-page and header directives: noindex , none , X-Robots-Tag , and status codes like 404/410. A page can be crawlable but carry noindex . Indexed is Google's decision after crawl. Quality, duplication, and manual actions still matter. A clean indexability report is necessary but not sufficient. Signals in crawl order 1. Status and redirects Check the first response and the final URL after redirects. Longer redirect chains can add hops before Google sees the final URL. Final 404/410 tells crawlers the URL is gone. 401/403/429 may be WAF or login walls; automated checks may differ from Googlebot. Illustrative check: 2. robots.txt on the origin Fetch https://your-host/robots.txt and see whether Googlebot (or * if no Googlebot group) allows the path. Google's robots.txt intro explains that disallow blocks crawling, not necessarily every appearance in…