A Request indexing Chrome extension that works in your own Search Console
Google has no public API for Request indexing on ordinary pages. The IndexCyborg extension does what you would do by hand: it opens your property, inspects the URL, clicks Request indexing and records Google's answer, at most 10 times per property in any 24 hours.
1How it clicks in your own session
The server decides what to request and how much per day; the extension only drives Search Console and reports what it answered. Press Request indexing now in its popup, or turn on automatic runs and it works through the queue while Chrome is open.
1IndexCyborg picks the pages
Pages Google reports as “Discovered - currently not indexed”, “Crawled - currently not indexed” or otherwise not indexed go first, then pages not checked yet. Pages excluded on purpose (noindex, robots.txt, redirects, duplicates) and non-200 pages are never picked, and a page isn't picked again for 14 days.
2The extension opens your property
In a background tab of your own Chrome, signed in to the Google account that owns the property, it opens Search Console and types the URL into “Inspect any URL”.
3It reads what Search Console shows
If Search Console already shows the page as indexed, it moves on without spending a request. You can turn this off for automatic picks; URLs you queue by name are always requested.
4It clicks Request indexing
Then it waits for Google's answer in the dialog: the request was accepted, the daily quota is used up, or something failed.
5It reports back
The answer lands in IndexCyborg's activity log for that page, with the message Search Console showed. A quota answer pauses the site until midnight Pacific.
2What each answer means
A requested page is queued for crawling by Google, nothing more. These are the answers the extension reports.
- Requested
- Google added the URL to its crawl queue. Not crawled, not indexed: Google still decides both.
- Already indexed, skipped
- Search Console showed the page as indexed; no request was spent.
- Quota exceeded
- Search Console's own daily limit was reached. The site pauses until midnight Pacific.
- Failed
- No recognizable answer, a disabled button or a timeout. The page can be retried after 24 hours.
3The daily cap, enforced three times
Search Console has its own limit on how often you can request indexing. IndexCyborg adds a hard cap of its own, which a site's settings can lower but never raise.
| Parameter | Limit | Notes |
|---|---|---|
| Requests per property | 10 | Rolling 24 hours, enforced by the API, the database and the extension |
| Cooldown per page | 14 days | Automatic picks only; URLs you queue by name skip it |
| URLs queued by name | 50 per call | Through the REST API or the MCP server, requested even when indexed |
| Automatic runs | Optional | Every 3 hours while Chrome is open; queued URLs are picked up within 10 minutes |
4Privacy: what the extension can see
A Google Search Console Chrome extension needs access to your Search Console session. This one asks for as little else as it can.
Runs only on Search Console
Its content script is limited to search.google.com. It doesn't read other sites you visit.
The tabs permission
Chrome describes it as reading your browsing history. The extension uses it only to open, drive and close its own background Search Console tab.
Talks only to IndexCyborg
It fetches the next URLs to request and sends back Search Console's answer. If you point it at another server, Chrome asks you to allow that address.
Your Google session stays in Chrome
It acts as the Google account you're signed in with. What it sends to IndexCyborg is the page and Search Console's answer, nothing else from your session.
5How to load it
The extension isn't on the Chrome Web Store. It is loaded unpacked, from the instructions in the dashboard's Settings.
- 1Create an account, add your website and verify that you own it. Link your Search Console property.
- 2In the dashboard, open Settings and follow the Chrome extension steps: turn on Developer mode in chrome://extensions and choose Load unpacked.
- 3Generate an extension code there and paste it into the extension's popup. The code is an API key with the read and notify scopes, shown once.
- 4Stay signed in to Google with the account that owns your properties, then press Request indexing now, or turn on the automatic run.
Want to queue specific pages, for example right after a deploy? Send them through the REST API or let your coding agent do it through the MCP server; the extension takes them before its own picks.
New to the button itself? Read how to request indexing in Google Search Console, what the URL Inspection tool tells you, and why we built request indexing without an API.
6Frequently asked questions
- Is there an API to request indexing in Google Search Console?
- Not for ordinary pages. Google's Indexing API is documented for JobPosting and BroadcastEvent pages only, and the URL Inspection API reads a page's status without requesting anything. That is why IndexCyborg uses a Chrome extension that clicks the button in your own session.
- How many pages can the extension request per day?
- At most 10 per Search Console property per rolling 24 hours. Pages Search Console already shows as indexed are skipped without using a request, and a page isn't picked again for 14 days.
- What can the extension see?
- Its script only runs on search.google.com, and it only talks to your IndexCyborg server. Chrome describes its tabs permission as reading your browsing history: the extension uses it only to open, drive and close its own background Search Console tab, and doesn't read other sites you visit.
- Does Chrome need to stay open?
- Yes. The extension works inside your browser, signed in to Search Console. With automatic runs on, it checks for queued pages every 10 minutes while Chrome is open.
- Does requesting indexing guarantee the page gets indexed?
- No. Request indexing asks Google to crawl the URL; Google decides whether and when to crawl it and whether to index it. IndexCyborg keeps checking the page's status through the URL Inspection API and shows Google's answer verbatim.
Let the extension do the clicking
The extension comes with every plan, together with sitemap discovery, IndexNow and Google index monitoring. Starter is $5 a month for one website, Pro is $15 a month for every website you run, or pay once from 1,000 pages for $5. Every plan has the whole workflow, the REST API and the MCP server.
Billing isn't live yet. During early access nothing is charged and every account has Pro limits.