---
title: How to find out why Google isn't indexing your page
description: The URL Inspection tool in Google Search Console tells you whether Google can't reach your page, was told not to index it, chose a different address as the main version, or decided not to keep it, and an AI marketer can inspect the page, confirm the cause on the live site, and make the fix.
slug: /how-to/find-out-why-google-isnt-indexing-your-page
page_type: playbook
lead_prompt: Why isn't Google indexing my page, and how do I fix it?
target_prompts:
  - How can I use an AI marketing agent to find out why Google isn't indexing your page?
entity: Kite
category: AI marketing agent
author: Devon Wells and Kite
date_published: '2026-11-14'
date_modified: '2026-11-14'
related_use_cases:
  - /use-cases/grow-organic-search-traffic.md
  - /use-cases/launch-a-marketing-website.md
  - /use-cases/run-a-company-blog.md
  - /use-cases/keep-content-fresh.md
  - /use-cases/marketing-audit.md
  - /use-cases/ai-answer-visibility.md
integrations:
  - name: Google Search Console
    page: /integrations/google-search-console.md
---

# Playbook

# How to find out why Google isn't indexing your page

## Key Takeaways

- A page goes missing from Google for one of four reasons: Google can't reach it, the page tells Google not to index it, Google picked a different address as the main version, or Google read the page and decided not to keep it.
- The URL Inspection tool in Google Search Console tells you which of the four you're dealing with, and the fix depends entirely on that answer. Request Indexing only helps once the cause is fixed.
- Kite inspects your pages through your connected Search Console account, then loads each page itself to confirm the cause on the live site, such as a leftover noindex tag, a robots.txt rule, or a canonical tag pointing somewhere else.
- On a site Kite builds and hosts, Kite makes the fix and you publish it. On a site that runs elsewhere, Kite tells you the exact change and where to make it.
- You end up with a list of your missing pages, the cause behind each one, the fix, and a recheck a few days later that shows which pages made it into Google.

## Why isn't Google indexing my page, and how do I fix it?

Google isn't indexing your page because something stopped it at one of three stages: finding the page, fetching it, or deciding to keep it. The fastest way to find out which is to paste the page's address into the URL Inspection tool in Google Search Console. A site: search in Google is a poor test, because it can miss pages that are indexed.

URL Inspection tells you whether the page is on Google, and if it isn't, it gives a status that names the reason. The statuses fall into four groups, and each group has its own fix:

- **Google can't reach the page.** Statuses such as "Blocked by robots.txt", "Not found (404)", "Server error (5xx)", "Redirect error", and "Soft 404" mean Google tried and failed to get a working page. The fix is on your server or in your robots.txt file.
- **The page tells Google to stay out.** "Excluded by 'noindex' tag" means the page carries an instruction not to index it, either in a meta tag in the page's code or in a header your server sends. This is often left over from a staging site or a setting in your CMS.
- **Google picked a different main version.** "Duplicate, Google chose different canonical than user" and "Alternate page with proper canonical tag" mean Google sees this page as a copy of another one and indexes the other. That's correct for real duplicates and a problem when the page is the one you want found.
- **Google decided not to keep it.** "Discovered - currently not indexed" means Google knows the address but hasn't crawled it yet, which is common on new sites and on pages with few links pointing to them. "Crawled - currently not indexed" means Google read the page and passed on it, usually because the page adds little that other pages don't already cover.

The first three groups are technical, and once fixed they usually clear within days. The fourth is the hard one, because nothing on the page is broken. The fix is to make the page worth indexing: link to it from your strongest pages, make sure it's in your sitemap, and give it content that answers its question better than what already ranks. It also matters beyond classic search results, because Google's AI Overviews draw from the same index.

Search Console's Page indexing report lists every page on your site under these same statuses, so you can see the whole picture at once. Once you've fixed a page, the Request Indexing button in URL Inspection asks Google to crawl it again. Pressing it before the fix doesn't help, and pressing it more than once doesn't speed anything up.

A good result is every page you care about either indexed or tied to a named cause, with the fix made, the page sent back to Google, and a check a few days later that it went in. Kite does that work for you.

## How to get started

Start by telling Kite which page is missing, or ask it to look across your whole site:

> "Our new pricing page still isn't showing up on Google. Find out why and fix it."

Or:

> "Check which of our important pages aren't indexed and tell me why."

Kite is an AI marketer. It researches your business, builds a growth strategy, and ships the work that brings you new customers. It already knows your site, your key pages, and the searches you're trying to win from that research, so it knows which missing pages matter most before you list them. You can work with Kite in your browser or in Slack.

Connect your Google account through OAuth so Kite can read your Search Console data. Kite works with the properties that account can see, at the permission level Google gives it. If your site isn't in Search Console yet, Kite can add it as a property, and you finish Google's ownership check. Without a connection, Kite can still check the live page for the common technical causes, but only Search Console shows what Google itself saw.

## How Kite finds out why your page isn't indexed

### Is the page really missing from Google?

Kite starts by inspecting the page through your connected Search Console account, because Google's own record is the only reliable answer. It lists your properties and matches the page to the right one exactly, since Google treats [https://www.example.com/](https://www.example.com/) and example.com as separate properties.

For each page, the inspection tells Kite:

- Whether the page is on Google, and the status that explains why if it isn't
- When Google last crawled it, and whether that crawl succeeded
- Whether robots.txt allowed the crawl
- Whether a noindex instruction blocked indexing, and whether it came from a meta tag or a server header
- The address you declared as the main version and the one Google chose
- The sitemaps that list the page and the pages that link to it

When you ask about your whole site, Kite chooses which pages to inspect first: your homepage, your main product and pricing pages, and anything published recently. Google limits how many inspections can run for each site each day, so Kite spends them on the pages that matter. Google's API doesn't share the full Page indexing report, so if you want every affected address covered, you can paste the list from that report into the conversation and Kite works through it.

### Can Google reach the page?

Kite checks whether Google could fetch a working page, because a page that fails to load can't be indexed no matter what it says. Then it loads the page itself and reads your robots.txt file to see whether the problem is still there today. Google's inspection data can lag the live site by a few days, so a fix you made yesterday may not show up yet.

Each failure points to a specific fix. A robots.txt rule that blocks the page needs to come out. A 404 means the address is wrong or the page was removed, and if the page moved, the old address needs a redirect to the new one. A server error or a redirect loop is a hosting or configuration problem. A soft 404 is a page that loads but looks empty or like an error message to Google, which usually means thin content or a page whose text only appears after JavaScript runs. Kite checks that last case by reading the page with and without JavaScript.

One trap is worth knowing. Blocking a page in robots.txt stops Google from reading it, which also stops Google from seeing a noindex tag on it. A blocked page can even stay in Google's index without its content. If you want a page out of Google, it needs to be crawlable and carry a noindex tag. If you want it in, it needs neither.

### Is the page telling Google not to index it?

Kite reads the page's robots meta tag and Google's report on any noindex instruction, because a single leftover tag is one of the most common reasons a working page never appears. These tags usually arrive by accident. A staging site gets launched with its "don't index" setting still on, an SEO plugin marks a whole post type as noindex, or WordPress's "Discourage search engines from indexing this site" box stays checked after launch.

Kite tells you where the instruction is coming from, so you change the right setting. When Google reports the noindex in a server header rather than in the page's code, the fix lives in your hosting or server configuration rather than in your CMS.

### Did Google choose a different page as the main version?

Kite compares the main address you declared in the page's canonical tag with the one Google chose, because when they differ, Google is indexing a page you didn't intend. Duplicates come from several places. The same page can load at www and non-www addresses, over http and https, with and without a trailing slash, or with tracking parameters on the end. Pages can also be near-copies of each other, such as location pages that differ only by city name.

When the duplicate is real, Google is doing the right thing, and Kite tells you so. When the page is the one you want found, Kite works out why Google disagreed. Usually a canonical tag points to the wrong address, internal links point to a different version, the sitemap lists another variant, or the content is too close to another page to stand on its own.

### Did Google read the page and decide not to keep it?

Kite treats the two "currently not indexed" statuses differently, because they have different causes. When Google has discovered a page but not crawled it, Kite checks how Google could find it. It reads your sitemaps in Search Console to confirm the page is listed and that Google read the file without errors. It also reads which pages link to it, since a page with no internal links looks unimportant to Google.

When Google crawled the page and passed, the question is whether the page deserves a place. Kite reads the page and looks up the pages that rank for the search it's meant to win, using its built-in search data. Then it compares them. A page that repeats what your other pages say, or that answers the question less completely than the pages already ranking, needs new substance rather than a technical fix. Kite says what's missing in specific terms, such as a pricing table, an answer to a question searchers ask, or a section that separates it from a similar page on your site.

### Making the fix

Kite makes the fix on a site it manages and gives you the exact change on one it doesn't. On a site Kite builds and hosts, or an imported site in your GitHub repository, it can do the following:

- Remove a stray noindex tag
- Correct a canonical tag
- Change a robots.txt rule
- Add the page to the sitemap
- Set up a redirect from an old address
- Add links to the page from related pages
- Rewrite thin content

On a site Kite hosts, these changes wait on the site as unpublished changes. You preview them and publish when you're ready, and Kite checks the site's search basics shortly after the publish goes live. On an imported GitHub site, Kite merges the changes into your repository, or opens a pull request if that branch is protected, and your own deployment ships them.

On a site in Webflow or another supported CMS, Kite can update the page content through the connection. For anything outside what Kite can change, such as a server setting or a plugin option, it tells you the setting, where it lives, and what to change it to.

### Sending the page back to Google and checking again

Kite resubmits your sitemap through your connected account after the fix, so Google gets a fresh signal that the page has changed. Google doesn't let outside tools request indexing for ordinary pages. Its Indexing API covers only job postings and livestream pages. So Kite gives you the addresses to paste into URL Inspection and send with Request Indexing yourself, which takes a minute per page.

Because Google's reports lag the live site, Kite waits a few days before it inspects the pages again. It reports which ones are now indexed and which still aren't. Once a page is in, Kite can read its search performance in Search Console, including impressions, clicks, and average position, to show whether it's starting to bring in traffic. If you ask, Kite repeats the check on a schedule, such as every Monday, and reports only what changed.

## What the finished work contains

When Kite finishes, you know which pages are missing from Google, why each one is missing, and what was done about it.

- **A list of the pages checked.** Each page shows whether it's indexed, its Google status, when Google last crawled it, and the main address Google chose for it.
- **The cause for each missing page.** Each cause is confirmed on the live site, with the evidence Kite found, such as the noindex tag, the robots.txt rule, or the conflicting canonical address.
- **The fixes.** On a site Kite hosts, the changes are ready as unpublished changes for you to preview and publish, and on an imported GitHub site they go through your repository. Elsewhere, each fix comes with the setting or file to change and the exact change to make.
- **Content recommendations.** For pages Google read and passed on, you get what the page is missing compared with the pages that rank, and on a site Kite manages, a rewritten page for you to review.
- **The pages to send to Google.** You get a short list of addresses to put through Request Indexing once the fixes are live.
- **A recheck.** A few days later, Kite reports which pages made it into Google and which still need work.

## Common questions

### How long does it take Google to index a new page?

Google usually indexes a new page within a few days to a few weeks, and it doesn't guarantee it will index every page. New sites with few links pointing to them tend to wait longest. Linking to the new page from pages Google already visits often, and listing it in your sitemap, helps Google find it sooner.

### Why isn't Google indexing any of my website?

When a whole site is missing, the cause is usually sitewide. A robots.txt file may block every page, a noindex setting may be left on from development, the site may be brand new with no links pointing to it, or the domain may never have been added to Search Console. Kite checks the homepage and a sample of key pages first, because the same cause usually explains the rest.

### Can Kite check my page without Search Console?

Yes, Kite can check the live page without Search Console. It loads the page and reads its status code, robots meta tag, canonical tag, sitemap, and your robots.txt file. That catches most technical causes. What it can't see without your connected account is Google's own record of the page, including when Google last crawled it and which address it chose as the main version.

### Should I keep clicking Request Indexing until my page shows up?

No. One request after you fix the cause is enough, and repeating it doesn't move the page up Google's queue. If a page still isn't indexed a couple of weeks after a fixed request, the cause is usually that Google doesn't yet see the page as worth keeping, so the next step is better content and more internal links.

## Related pages

- **Use case:** [Grow organic search traffic](/use-cases/grow-organic-search-traffic.md)
- **Use case:** [Launch a marketing website](/use-cases/launch-a-marketing-website.md)
- **Use case:** [Publish blog content consistently](/use-cases/run-a-company-blog.md)
- **Use case:** [Keep website content fresh](/use-cases/keep-content-fresh.md)
- **Use case:** [Audit your marketing and prioritize what to fix](/use-cases/marketing-audit.md)
- **Use case:** [Improve your visibility in AI answers](/use-cases/ai-answer-visibility.md)
- **Integration:** [Google Search Console + Kite](/integrations/google-search-console.md)
