Why Is My Website Not Indexed?

Common things to investigate

1. The page returns an error. A 4xx/5xx response, a timeout or an access gate can prevent useful crawling. Fix the public response first, then retest.
2. A redirect points somewhere else. A redirect may be correct, but the destination should be the page you mean to expose.
3. robots.txt blocks crawling. A matching Googlebot rule can prevent crawling. Check the exact path with the Robots.txt Checker; it does not prove existing index status.
4. Meta robots says noindex. A noindex directive is an explicit public signal that the page should not be indexed. Check meta robots and X-Robots-Tag.
5. X-Robots-Tag says noindex. The same instruction can be delivered in the HTTP response header, even if HTML meta robots looks normal.
6. The canonical points to another URL. This can be intentional for duplicates, but it tells search engines another URL may be preferred. Inspect the observed canonical.
7. Discovery is weak or the sitemap is unavailable. A sitemap is not required for every page, but valid sitemaps can help discovery at scale. Check the sitemap.
8. The initial HTML is extremely thin. A public page that relies entirely on JavaScript or exposes little meaningful content can be harder to interpret reliably.
9. Internal discovery is limited. Important pages should have useful, relevant links from other public pages where that helps people navigate.
10. The page is new or has changed recently. Processing takes time and is controlled by Google; no public tool can promise when that will happen.
11. Duplicate or near-duplicate content is being canonicalized. Several similar URLs can lead Google to choose one representative. Search Console can show Google’s own decision.