By Mehdi HassanYou published a page, it's in your sitemap and it still doesn't show up when you search for it. That's one of the most common questions founders bring to a technical SEO review, and the answer is almost always sitting in Google Search Console. Google tells you why each URL isn't indexed; the work is reading the status correctly and applying the right fix.
This guide walks through how to diagnose a missing page and what each Search Console status means, with fixes for the causes most typical on startup sites. It's part of our technical SEO guide for marketing websites.
Why are my pages not indexed by Google?
Pages aren't indexed by Google because they're blocked, marked noindex, treated as duplicates, broken, or not yet judged worth indexing. On small marketing sites, the last two causes, duplicates and perceived low value, are behind most of the missing pages.
- Blocked: robots.txt disallows the URL, or it sits behind a login or a firewall rule that blocks Googlebot.
- Excluded on purpose: a noindex tag or header, often left over from staging or a template default.
- Duplicate: Google picked a different URL as the canonical version, such as a parameter or trailing-slash variant.
- Broken: the URL returns a 404, a 5xx error, a redirect or a page Google reads as a soft 404.
- Not valuable enough yet: Google crawled or discovered it but chose not to index it, often because it's thin, similar to other pages or poorly linked.
How do you find out why a page isn't indexed?
Find the reason by inspecting the exact URL in Search Console, then checking the Pages report for patterns across the site. URL Inspection gives the status for one page; the Pages report shows whether the problem affects a whole template.
Inspect the URL
Paste the full URL into Search Console's URL Inspection. Note the indexing status, the user-declared canonical and the Google-selected canonical.
Test the live URL
Run the live test and view the rendered HTML and screenshot. Confirm your main content and links appear, which rules out rendering problems.
Check the Pages report
Open Indexing, then Pages, and look at the reasons listed under why pages aren't indexed. Click a reason to see example URLs and spot template-wide issues.
Check robots.txt and meta robots
Confirm the path isn't disallowed and the page source has no noindex in a meta tag or X-Robots-Tag header.
Check internal links
Count how many pages link to the URL, and from where. A page linked only from the sitemap is a weak candidate for indexing.
Fix, then request indexing once
Apply the fix for the status, then use Request Indexing a single time. Validate the fix from the Pages report for template-wide issues.
What do Search Console's indexing statuses mean?
Each Search Console status points to a specific cause. The table below covers the statuses you'll meet most on a marketing site and the usual fix for each. Some of them, such as page with redirect, are normal and need no action.
Status | What it means | Usual fix |
|---|---|---|
Crawled, currently not indexed | Google fetched it and chose not to index | Improve uniqueness and depth; add internal links |
Discovered, currently not indexed | Google knows the URL but hasn't crawled it | Add internal links from strong pages; check site quality |
Excluded by noindex tag | The page tells Google not to index it | Remove noindex if the page should rank |
Blocked by robots.txt | Crawling is disallowed | Remove the rule if the page should rank |
Duplicate without user-selected canonical | Google sees duplicates and you declared no canonical | Add a self-referencing canonical on the preferred URL |
Duplicate, Google chose different canonical than user | Google disagrees with your canonical | Make signals consistent: links, sitemap, redirects |
Alternate page with proper canonical tag | Duplicate that correctly points elsewhere | Usually no action |
Soft 404 | Page returns 200 but looks empty or missing | Add real content, or return a proper 404 or 410 |
Not found (404) | The URL doesn't exist | Redirect if it moved; otherwise leave it |
Page with redirect | The URL redirects elsewhere | No action; remove it from the sitemap |
How do you fix crawled, currently not indexed?
Fix crawled, currently not indexed by making the page clearly worth indexing: unique content that answers a specific question, strong internal links and no near-duplicates on your own site. Google has seen the page and decided it adds too little, so technical tweaks alone rarely change the outcome.
On startup sites this status clusters around a few page types. Programmatic pages, such as a page per integration, city or competitor generated from a template with only a name swapped, are the classic case. Thin feature pages and short blog posts that repeat each other are close behind. The fix is often counterintuitive: publish fewer pages and make each one substantially different. Our guide to SaaS feature pages shows how to give each page a real job, and answer-first page structure covers how to write pages that answer a question directly.
Hypothetical example: 80 integration pages, 12 indexed
For example, suppose a SaaS startup generates 80 integration pages from a template. Each has the partner's logo, one sentence and the same feature list. Search Console shows 12 indexed and the rest as crawled, currently not indexed.
The team picks the 20 integrations customers actually use and writes each page properly: what the integration does, setup steps, common use cases and limits. The other 60 are combined into a single directory page that lists them with short descriptions. The thin URLs are redirected to the directory, and each detailed page gets links from the relevant feature page.
The point isn't a guaranteed outcome. It's that Google now sees 21 distinct pages instead of 80 near-identical ones, which is a much stronger case for indexing.
How do you fix discovered, currently not indexed?
Fix discovered, currently not indexed by giving Google stronger reasons to crawl the URL: links from pages that are already indexed and visited, a clean sitemap and a site that isn't diluted by many low-value URLs. The status means Google knows the page exists but hasn't prioritized fetching it.
It's common on new domains and on sites that publish many pages at once. Link each new page from at least one relevant hub or navigation page and from two or three related articles, using descriptive anchors. Our internal linking strategy for small marketing sites explains how to build that into the site structure. Also check the sitemap lists only canonical 200 URLs; our guide to robots.txt and XML sitemaps covers what belongs there.
How do you fix duplicate and canonical statuses?
Fix duplicate statuses by declaring one canonical URL for each piece of content and making every other signal agree with it. Internal links, the sitemap, redirects and hreflang should all point to the same URL you put in the canonical tag.
On marketing sites, duplicates usually come from UTM-tagged URLs, trailing-slash and non-slash variants, http and https versions, near-identical landing pages for paid campaigns and solution pages that overlap with product pages. For overlapping pages, decide which one owns the topic; our guide to solutions pages vs product pages helps with that call. When Google keeps choosing a different canonical than yours, it's usually because your own internal links point to the other version.
Which pages should stay out of the index?
Some pages should never be indexed, and seeing them as excluded is a sign your setup is working. Thank-you and confirmation pages, internal search results, login pages, paid-campaign variants and canonicalized duplicates all belong out of Google's index.
Paid landing pages are a common example. Variants built for ad traffic often duplicate a main page with small copy changes, so they should carry noindex or a canonical to the main version. Our guide to landing pages for paid ads covers how to set them up. Excluded counts in Search Console only matter when the excluded URLs include pages you want to rank.
When should you get help with indexing problems?
Get help when the Pages report shows a template-wide problem you can't trace, when indexed pages drop sharply after a site change or when important pages stay excluded for weeks after you've fixed the obvious causes. Those situations usually point to rendering, canonical logic or a migration issue that needs code changes.
If the drop followed a migration or redesign, start with redirects and canonicals; a redirect map built from your old URLs shows what was missed. If the site is a client-rendered app, read our guide to JavaScript SEO first.
