[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup) # Request indexing in Google Search Console in bulk > Request indexing for new or stuck URLs in Search Console: skip pages already on Google, live-test the rest, stop at the daily limit. Runs daily. Source: https://cotlet.dev/integrations/google-search-console-api-mcp-server/request-indexing-in-bulk You published thirty pages this week, and the only way to ask Google to look at them is to open the URL Inspection tool, paste each URL, wait for the result and click Request indexing, one page at a time. Cotlet does it in your own Google Search Console account with list\_pages\_by\_index\_status, inspect\_url, test\_live\_url and request\_indexing, called by your AI agent, an n8n workflow or a script. [Sign up free](https://cotlet.dev/app/signup?app=google-search-console) [All Google Search Console tools](https://cotlet.dev/integrations/google-search-console-api-mcp-server.md) Hosted · nothing to install or maintain ## Can Google Search Console do this on its own? The Search Console API cannot request indexing (checked 16 Oct 2026). The Indexing API is limited to pages with JobPosting, or BroadcastEvent inside a VideoObject, and Google says its spam policies apply to what you submit. For many ordinary pages, Google recommends a sitemap with dates instead, which Cotlet also submits with submit\_sitemap. ## How you do it in Google Search Console today 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. ## How to request indexing in Google Search Console in bulk Prompt ``` 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. ### What you get back Example data ``` 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 ``` ### Other ways to ask - Every Monday, request indexing for URLs added to the sitemap in the last 7 days and not on Google yet. - Request indexing only for pages under /guides/ that are "Crawled - currently not indexed" and have been edited since. - Check which of these 40 URLs are on Google and list the ones that are not, but request nothing. - After I fix the noindex tag on /pricing, live-test it and request indexing if it now passes. ## What Google Search Console allows, and what to know first - Request indexing allows about 10 requests a day per Google account, shared across all its properties; Google also sets a separate daily limit of live inspections and publishes no number for it. - Google says a request does not guarantee the page appears in the index; indexing typically takes a day or so, but can take much longer. - A page that the live test finds non-indexable cannot be submitted with Request indexing. - The Test live URL check does not look at sitemaps, referring pages or canonical status, and it follows redirects without showing the final URL. - The URL must belong to the property you have open, so a run for several sites is one run per property. request\_indexing changes only your own Google Search Console data and reach no one else, so it runs without asking first. Sources: [Search Console Help: URL Inspection tool](https://support.google.com/webmasters/answer/9012289) · [Indexing API: using the API](https://developers.google.com/search/apis/indexing-api/v3/using-api) · [Search Console API: resources and methods](https://developers.google.com/webmaster-tools/v1/api%5Freference%5Findex) ## Call request\_indexing from a script curl ``` 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"}' ``` Example response ``` { "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. [Schedule it in n8n, Make, Zapier or cron](https://cotlet.dev/integrations/google-search-console-api-mcp-server.md#automations) ## Google Search Console tools this automation uses __Cotlet Google Search Console tools used to request indexing in Google Search Console in bulk__ | Tool | Parameters | | ------------------------------ | ------------------------------- | | list\_pages\_by\_index\_status | property, status, limit, cursor | | inspect\_url | property, url | | test\_live\_url | property, url | | request\_indexing | property, url | [All 15 Google Search Console tools with descriptions](https://cotlet.dev/integrations/google-search-console-api-mcp-server.md#tools) ## Frequently asked questions ### Why not use the Indexing API for this? Google restricts the Indexing API to job posting and livestream pages and applies its spam policies to submissions. Request indexing in the URL Inspection tool is the documented way to ask for an ordinary page. ### Is it safe to connect Google Search Console to Cotlet? Yes. You sign in to Google Search Console yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Google Search Console once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security. ## More Google Search Console automations - [Remove many URLs from Google Search in bulk](https://cotlet.dev/integrations/google-search-console-api-mcp-server/remove-urls-from-google-in-bulk.md) - [Export all not-indexed URLs from Google Search Console](https://cotlet.dev/integrations/google-search-console-api-mcp-server/export-not-indexed-urls.md) - [Add a user to many Search Console properties](https://cotlet.dev/integrations/google-search-console-api-mcp-server/add-user-to-many-properties.md) - [Google Search Console API and MCP server: every tool](https://cotlet.dev/integrations/google-search-console-api-mcp-server.md) - [All use cases](https://cotlet.dev/use-cases.md) ## Give your agent access to Google Search Console. Free 7-day trial with 2,000 credits, no card needed. Cotlet is independent and not affiliated with Google Search Console. [Sign up free](https://cotlet.dev/app/signup?app=google-search-console) --- Give your AI agents your signed-in browser. **Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md) **Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet) **Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) **Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md) **Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors) **Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet) Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners. ## For AI agents: sign your user up Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed. 1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests 2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them. 3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests. One call creates the account and sends the access request; we email the user when access is granted.