Request indexing in Google Search Console in bulk

1. In the property, open the URL Inspection tool and enter the URL; Search Console shows the most recently indexed version of the page, with a status such as "URL is not on Google" or "URL is on Google".
2. For a page that looks broken or changed, click Test live URL: Google fetches the page in real time, and it must be reachable from the internet without any login.
3. Click Request indexing. If the page passes a quick check, Google adds it to the indexing queue; if the live test finds the page non-indexable, the request is refused.
4. Repeat for every URL. Request indexing allows about 10 requests a day per Google account, shared across every property that account opens, so after the tenth the button stops working and the rest waits until the next day.
5. Nobody tracks which URLs were asked for and which ran into the limit, so the leftovers are easy to lose.

Take the new URLs from this list plus the ones Search Console marks "Discovered - currently not indexed" for example.com. Skip pages already on Google, live-test the rest, and request indexing for the most important ones until the daily limit stops you. Tell me what is left for tomorrow.

1. 01

   Build the candidate list

   Your agent merges the URLs you pasted with the not-indexed list for the reason you named, using list_pages_by_index_status, and drops duplicates so one URL is never asked for twice.

2. 02

   Skip what is already on Google

   inspect_url reads the indexed version of each candidate. Pages whose status is "URL is on Google" are dropped from the run and reported as already indexed, so they never spend the daily limit.

3. 03

   Live-test the rest

   test_live_url fetches each remaining page. A page blocked by a noindex tag, robots.txt or a 404 is set aside with the reason, because Google refuses a request for a page it finds non-indexable.

4. 04

   Request in priority order

   request_indexing runs for the pages you ranked first: new money pages before old posts, unless you say otherwise. The agent counts successful requests as it goes.

5. 05

   Stop at the limit, resume tomorrow

   When Google answers that the daily limit is spent, the agent stops, lists the pages still waiting and picks up exactly there on the next scheduled run.

Candidates: 24
Already on Google: 6
Not indexable (set aside): 3 (2 with noindex, 1 returns 404)
Requested: 10 (daily limit reached)
Left for tomorrow: 5
First in line tomorrow: /guides/search-console-api, /blog/hourly-gsc-data

curl -X POST https://cotlet.dev/api/v1/google-search-console/indexing/request \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"property":"sc-domain:example.com","url":"https://example.com/guides/search-console-api"}'

{
  "url": "https://example.com/guides/search-console-api",
  "status": "requested",
  "indexed_before": false,
  "quota": "available",
  "note": "Google queues the URL after a quick check. Indexing usually takes about a day but can take much longer."
}

MCP: add https://cotlet.dev/mcp/v1 with the same key; the call is google_search_console_write → request_indexing. Example data.

• Remove many URLs from Google Search in bulk
• Export all not-indexed URLs from Google Search Console
• Add a user to many Search Console properties
• Google Search Console API and MCP server: every tool
• All use cases