Google Indexing Request: When It Helps

You make a Google indexing request in Search Console with the URL Inspection tool: enter the full address in the search bar at the top, run "Test live URL" if needed, then click "Request indexing". After a quick check, the page goes into Google's queue. Only owners and full users of the property can do this. Requests have a daily limit that Google doesn't publish; for many addresses, a sitemap is the intended route. And a request is not a command: according to Google, crawling can take a few days to a few weeks, and a request "does not guarantee that inclusion in search results will happen instantly or even at all". For regular pages there is no API for the request itself (as of November 2026).

That raised a question I asked myself: how do I teach my AI agent to use Search Console, through the API but also in the browser, the way we do it? Setup itself is covered in Setting Up Google Search Console.

How to make a Google indexing request, step by step

1. Inspect the URL. Open the property and enter the full address including https:// in the top search bar. The first result comes from the Google index, not your live page.
2. Read the result. "URL is on Google": it's indexed; a request only makes sense after a substantial change. "URL is unknown to Google": exactly the case Google recommends a request for.
3. Test the live URL. It checks whether Google can fetch the current version without credentials and whether robots.txt or noindex is in the way. A positive result only means the page can be crawled, not that it will appear.
4. Click "Request indexing". After a quick check, the URL is queued. If the live test finds the page non-indexable, you can't request it.

Restricted users get "Fetch only" in URL Inspection, per Google's permissions table.

What a request can and can't do

A request fits a few important pages, such as a new post or a page with a fixed noindex mistake. For a hundred new posts it's the wrong tool.

The quota: how many requests per day?

Google only says: "There is a daily limit to how many index requests you can submit." No number (as of November 2026).

What I observed, not documented by Google: on November 3, 2026, 11 requests went through; on November 4, it was 10. Then Search Console reported "Quota exceeded", also for a second property in the same Google account. A morning attempt on November 4 was rejected immediately; in the afternoon it worked again. That points to a per-account limit over a rolling 24 hours. It isn't confirmed; Google's help mentions a daily limit of inspection requests per property.

Separate from that, the URL Inspection API allows 2,000 read queries per day per property.

Many pages: a sitemap instead of single requests

Google uses the <lastmod> field in your sitemap when it's consistently and verifiably accurate: real content changes, not a new copyright year. Submit the sitemap in the Sitemaps report or with a line in robots.txt. Google retired the old sitemap "ping" in 2023; calls now return a 404 error. A sitemap, too, is only a hint.

Google has to find a page via a known page or the sitemap, so links matter as much. For a brand new site, Google suggests requesting the home page first.

Crawled or discovered, currently not indexed: the statuses

The Pages report and URL Inspection tell you why a URL is missing:

What I observed: of 220 new post URLs (110 each in German and English) published since October 20, 2026, the URL Inspection API showed 83 indexed on November 3, 2026. Google didn't know 95 of the rest, and 41 were "Discovered". No technical errors; the pages simply hadn't been crawled. My reading, as a hypothesis: Google crawls by priority, not by volume.

AI agent and Search Console: read via the API, request in the browser

What about the Indexing API? Google says it "can only be used to crawl pages with either JobPosting or BroadcastEvent embedded in a VideoObject", so job postings and livestreams, with rigorous spam detection on every submission. For URL Inspection, the Search Console API has a single method, inspect, and it reads.

Reading via the API

1. Create a project in the Google Cloud console and enable the Search Console API.
2. Create a service account; save its JSON key outside any repository.
3. In Search Console, under "Settings", "Users and permissions", add the service account's address as a restricted user.
4. Request only the webmasters.readonly scope.

An example in Python; path and addresses are placeholders:

# Read-only: check the index status of a URL (Search Console API, URL Inspection)
from google.oauth2 import service_account
from googleapiclient.discovery import build

KEY_FILE = "/safe/place/service-account.json"  # placeholder, never in the repo
creds = service_account.Credentials.from_service_account_file(
    KEY_FILE, scopes=["https://www.googleapis.com/auth/webmasters.readonly"])
gsc = build("searchconsole", "v1", credentials=creds)

result = gsc.urlInspection().index().inspect(body={
    "inspectionUrl": "https://example.com/blog/new-post",
    "siteUrl": "sc-domain:example.com",  # URL-prefix property: "https://example.com/"
    "languageCode": "en-US",
}).execute()

s = result["inspectionResult"]["indexStatusResult"]
print(s["verdict"], s.get("coverageState"), s.get("lastCrawlTime"))

The API only shows the indexed version, not the live page. With a restricted role and read-only scope, the agent can't submit anything this way.

Requesting in the browser

For the request, the interface is what's left. An agent drives a browser through Playwright; this is how it runs for us:

1. The agent opens a visible browser with a fixed profile folder (a Playwright "persistent context"), so the sign-in sticks.
2. The human signs in. The agent never types or sees a password.
3. Via the API, the agent checks which addresses are still missing; only those go on the list.
4. Per address: enter the URL, wait, click "Request indexing", read the message, log time and result.
5. On "Quota exceeded" or two errors in a row, it stops. No second account, no workaround.

The profile folder holds session cookies; Playwright strongly discourages checking such files into a repository. The agent works at human pace and only in your own account. Google's terms prohibit automated access that violates machine-readable instructions such as robots.txt; a script that drives the interface remains a grey area you're responsible for. And the interface isn't an API: when Google changes a label, the script breaks. Instead of Playwright, Claude in Chrome: How to Use the Extension works too.

How to write it into CLAUDE.md

Claude Code reads CLAUDE.md at the start of every session. A Search Console section can look like this:

## Google Search Console
- Read only via the Search Console API with the service account (restricted
  user, scope webmasters.readonly). Key lives outside the repo; never print it.
- Request indexing only in the browser session I signed in to myself.
  Never enter a password, never work around a sign-in.
- Requests only on my explicit instruction; log my wording and the time.
- Check with URL Inspection first; only request URLs that aren't indexed.
- On "Quota exceeded", stop. No second account.

Anthropic says Claude treats these files "as context, not enforced configuration". The file is a request; the limit comes from role and scope. Whatever an employee must not do, I block technically. How that works in Claude Code is in Claude Code Security: Permissions and Sandbox.

For me, Sebastian, my AI employee for SEO and GEO, does this. He reads Google Search Console and Bing Webmaster Tools but can't submit anything through his access. Every URL submission goes through my explicit approval case by case, and he only clicks requests in the session I signed in to myself. Why that approval is part of the design and not mistrust is in Human in the Loop: Meaning and Examples.

Frequently asked questions

How long does indexing take after a request?

Google gives two ranges: the Search Console help says usually about a day, the developer docs say a few days to a few weeks. No guarantee.

How many indexing requests can I make per day?

Google mentions a daily limit but no number. For me, it was 10 to 11 requests on November 3 and 4, 2026.

Is there an API to request indexing from Google?

Not for regular pages. The Indexing API is only for job postings and livestreams, and the URL Inspection API only reads.

Why is my page "Discovered - currently not indexed"?

Google rescheduled the crawl, usually so as not to overload the site. Internal links from strong pages, a clean sitemap and patience help.

What to do next

Today, inspect your five most important pages. Request indexing for anything "unknown". Improve anything crawled but not indexed first. For the rest, rely on your sitemap and internal links. If an agent helps: read-only first, browser requests once the routine works. On Bing, you can notify via an API; that's covered in Submit Your Site to Bing: Setup and IndexNow.

Sebastian's own course is in the Premium tier of my community AI Employee Framework: twelve lessons from the first audit through setting up Search Console and Bing to the GEO baseline and the follow-up measurement.