URL indexer or Search Console: how SemChat checks what Google indexed

Know which pages Google kept, and why the others were not. Illustration by Zéro Corvée.

You published a page, and nobody finds it on Google. Before you reach for a URL indexer, ask a simpler question: did Google keep the page in its index at all? And if not, why?

This page is part of our guide to automated SEO: what an assistant like SemChat can do for you, and what you should still check yourself. Google quotes come from its official pages, read on October 30, 2026. The SemChat buttons on this page are affiliate links.

What a URL indexer promises

About 260 people a month search for “url indexer” in the United States (DataForSEO Labs, October 29, 2026). Most of the results they get sell speed. On October 29, 2026, the top 10 included titles like “Fast Google Indexer,” “Index Websites in Google” and “Bulk Google Indexing” (DataForSEO, United States). Several also mention backlinks.

We tested none of these services, and this site recommends none. Here’s what Google itself says, so you can judge any promise.

Why indexing matters for your pages

Google works in three stages, according to its guide to how Search works:

• crawling: its robots download the pages they find;
• indexing: Google analyzes the text, images and videos, then stores the page in the Google index, “a large database”;
• serving: it shows indexed pages that match a search.

A page outside the index can’t show up in results. And Google is blunt: “Indexing isn’t guaranteed; not every page that Google processes will be indexed.” Our guide to indexing in SEO explains each stage in more depth.

Indexers and backlink indexers: what Google’s own rules say

On October 29, 2026, Google’s AI Overview for this search cited rapidurlindexer.com, urlindexingtool.com, searchatlas.com, apexindexer.com, freeindexer.com and instanturlindexer.com (DataForSEO, United States). We didn’t test them, and we attribute no result to them.

Three lines from Google are enough to set your expectations:

• “Google doesn’t accept payment to crawl a site more frequently, or rank it higher.”
• Its own indexing request has a limit: “You can’t request indexing for URLs that you don’t manage.” A backlink sits on someone else’s site.
• Even your own request “does not guarantee that inclusion in search results will happen instantly or even at all.”

First, find out why a page isn’t indexed

Google already gives you a free tool for this. Search Console is “a free service offered by Google.” Its Page indexing report sorts your URLs into indexed and not indexed, with a reason for each. For one page, use the URL Inspection tool, which “provides information about Google’s indexed version of a specific page.”

Three statuses come up often. Here’s how Google defines them:

• “Crawled - currently not indexed”: “The page was crawled by Google but not indexed. It may or may not be indexed in the future; no need to resubmit this URL for crawling.”
• “Discovered - currently not indexed”: “The page was found by Google, but not crawled yet.”
• “URL is unknown to Google”, in URL Inspection: “Google hasn’t seen this URL before.” Here, Google says you should request indexing.

Not every gap is a problem. Google writes: “It’s fine for a URL not to be indexed for the right reasons.” Its examples: a robots.txt rule you meant to set, a noindex tag, a duplicate URL, or a 404 for a page you removed.

Blocked by you, seen but not kept, too new: the three cases

	Blocked by you	Seen, not kept	Too new
What happens	noindex, robots.txt, redirect or error	Google saw it and didn't keep it	Google hasn't processed it yet
What you do	check that it's intended	improve the page and link to it	wait, then inspect it

Two settings block Google, and they’re easy to mix up. A robots.txt file “tells search engine crawlers which URLs the crawler can access on your site.” Google adds that “it is not a mechanism for keeping a web page out of Google.” For that, there’s noindex, a rule “used to prevent indexing content by search engines that support the noindex rule, such as Google.”

The trap: a page blocked by robots.txt never shows Google its noindex tag. For noindex to work, Google says the page “must not be blocked by a robots.txt file.”

Normal discovery vs indexing tools

Google finds pages through links and sitemaps. On WordPress or another hosted platform, “in most cases, the platform submits your new content to search engines automatically.” A sitemap helps, but “submitting a sitemap is merely a hint.”

For a few pages, URL Inspection has a Request indexing button, with a daily limit. And “requesting a recrawl multiple times for the same URL won’t get it crawled any faster.” New sites need patience: “It can take a week or so for Google to start crawling and indexing a new page or site.”

Step 1: ask SemChat which pages Google hasn’t indexed

On October 29, 2026, I tested SemChat on plugkit-avis.com, my own site, on the Starter plan. The site was new: Search Console had data only since October 24, 2026.

What our French-language request asked for

I typed the request in French, on a French-language site, with the interface in French. The path: Nouveau chat (New chat), the “+” button, Compétences (Skills), Audit Technique (Technical audit). The exact sentence:

“Fais un audit technique SEO de plugkit-avis.com, centré sur l’indexation. Liste les pages que Google n’a pas indexées, en t’appuyant sur ma Search Console. Pour chacune, dis si elle est bloquée (noindex, robots.txt, erreur, redirection, canonique) ou si Google l’a vue sans la retenir. Range-les par cause, de celle qui touche le plus de pages à la moins fréquente, et dis-moi par quoi commencer.”

(Run a technical SEO audit of plugkit-avis.com, focused on indexing. List the pages Google hasn’t indexed, based on my Search Console. For each one, say whether it’s blocked (noindex, robots.txt, error, redirect, canonical) or whether Google saw it without keeping it. Sort them by cause, from the one affecting the most pages to the least frequent, and tell me where to start.)

The same request in English hasn’t been tested yet: missing data (planned source: an English-language test session).

SemChat offered to link the chat to my site. I picked “Non, lancer indépendamment” (No, run it independently). In an earlier test, a chat linked to the site couldn’t see Search Console; run on its own, it could.

Started as a technical audit, it switched to indexing on its own

I launched it as a technical audit. Its first reply already showed the badge of its Indexing skill: SemChat had switched skills on its own.

Its tools show up in the chat: reading the Search Console properties, crawling the whole site, then URL inspections. You see what it reads, and where its numbers come from.

Step 2: read what it found on a real site

Pages inspected, consistent with Search Console

It inspected 5 pages; all 5 were indexed. That was right. My own inspections the same day showed 10 pages “Submitted and indexed.” It found no page blocked by mistake: also right.

Two details on its summary card were off, though. It showed 170 pages in the sitemaps; my sitemap index listed 194 URLs that day. And it dated its data “juillet-octobre 2026” (July to October 2026), for a site tracked since October 24.

A follow-up that made it admit three mistakes

Its first diagnosis was wrong on three points:

• it saw about 70 English pages with zero impressions and considered noindexing them; yet the manychat-pricing page had about 27 to 30 impressions in my Search Console;
• it missed that the site was new, with data only since October 24, 2026;
• it called 104 duplicate main headings (H1) generic content; they were 52 pairs of US and UK English pages.

I pushed back with those three facts and asked: “Reprends le diagnostic en séparant trois cas : page bloquée par moi, page connue mais pas retenue par Google, page trop récente pour juger. Inspecte aussi les pages de contact.” (Redo the diagnosis by separating three cases: page blocked by me, page known but not kept by Google, page too recent to judge. Also inspect the contact pages.)

Its answer opened with “J’avais tort sur trois points” (I was wrong on three points). It then sorted pages into “Bloquées par toi” (blocked by you: URLs without a language prefix, returning 404, for which it wrote “Rien : c’est voulu,” nothing to do, it’s intended), “Connues mais pas retenues” (known but not kept) and “Trop récentes” (too recent).

It also counted 4 pages Google didn’t know. My inspections confirmed two: /fr/contact/ and /pt-br/contato/ showed “URL is unknown to Google,” even though both were in my sitemaps. Good catch.

Step 3: don’t follow its final actions without checking

The corrected answer ended with three actions for the week. I checked them the same day, against the sitemaps and with HTTP requests. Three claims were wrong.

A page to add to the sitemap that was already there

First action: add /fr/contact/ to the sitemap. Wrong: it was already in the French sitemap. The real issue was elsewhere. Google didn’t know the page, even though the footer links to it. For a page like that, Google’s fix is to inspect the URL, then request indexing.

Dead URLs to add, and a sitemap to create that already existed

The same action added /fr/plugkit-vs-circleboom/ and /fr/plugkit-vs-manychat/. Wrong again: both returned a 404, with a noindex tag. Adding them would have sent Google to dead pages. It also listed /es/contacto/: missing data, I didn’t check that one.

Third action: “Crée et soumets sitemap-en-gb.xml” (Create and submit sitemap-en-gb.xml). That file already existed: it returned a 200, with 51 URLs. The second action, giving US and UK pages different H1s, isn’t an indexing question; I don’t judge it here.

Cost: missing data for this test alone. The Starter plan quota moved 22.4 points across this test and the next one (a keyword clustering), with no reading in between.

My verdict: a good sorter of leads, which reads Search Console and accepts correction. A poor executor: even corrected, its action list was wrong. Ask it where to look; check before you act. The full test is in our SemChat review, and the plans are on our SemChat pricing page.

Free URL indexing tools or Search Console: what to use first

Here’s the order I’d follow, all of it free:

1. Inspect the page in Search Console’s URL Inspection tool.
2. Blocked by you? Decide if that’s intended.
3. Unknown to Google? Link to it from a known page, check your sitemap, then request indexing.
4. Seen but not kept? Improve the page rather than resubmitting it.
5. Too new? Wait, then inspect again.

Only once you know the cause does any indexing service even enter the question. We haven’t tested one.

How to get your site indexed on Google

The full method, step by step, is on our page on how to index your website on Google. Google’s own page on recrawling sums up the limits: “Crawling can take anywhere from a few days to a few weeks.” And “there’s a quota for submitting individual URLs.”

And once your pages are indexed? Opening a site? See our page on SEO for a new website. Deciding which pages to write? Read how to create an SEO strategy. Checking where rivals beat you? Compare competitor analysis SEO tools. Running a local shop? Look at our local SEO tool page.

Bottom line: before any URL indexer, use the free one Google built. SemChat can read Search Console for you and sort your pages into three cases, as long as you push back when it’s wrong and check each action before you follow it.