Free tool
Automate URL Submission to Google for Indexing with MCP and a Chrome Extension
Paste your URLs or sitemap.xml. We group them by Search Console property, keep each one under Google’s daily limit and give you a list. The free Search Console Auto Indexer extension then submits it in your own Chrome, every day.
Free. Build today’s Request indexing list from your URLs or sitemap, then let a Chrome extension submit it in Search Console every morning. Agents can build the list over MCP.
- URLs, sitemap.xml or JSON
- Search Console properties
- Max URLs per property per day
Build my indexing list
Example
Sitemap → list → Request indexing
10 / day
URLs per property
Runs in Your Chrome
How it works
-
1
Paste your URLs or sitemap
Paste URLs, a sitemap.xml or JSON, and your Search Console properties. Or skip the page and ask Claude, Cursor or any MCP client to run this Mini App through the Launch Llama MCP server.
-
2
Build my indexing list
We group URLs by property, drop files and tracking links, and keep each property under Google’s daily limit. Copy or download the JSON.
-
3
Let the Chrome extension run it
Load the free Search Console Auto Indexer, paste the list or point it at a list URL your agent rewrites daily. Each morning it clicks Request indexing for every URL and stops on quota, a CAPTCHA or the wrong account.
Why automate Request indexing at all
New pages on a young site can sit in “Discovered – currently not indexed” for weeks. Search Console’s URL inspection tool has a Request indexing button that asks Google to crawl a page now, but it takes one URL at a time, five clicks each, and about ten a day per property. Programmatic sites, blogs and directories publish more than that, so the job either gets skipped or eats half an hour every morning.
The Google Indexing API is not an alternative for most sites: Google limits it to job posting and livestream pages. Request indexing in Search Console is the supported way for everything else, so this setup automates that, in your own browser and your own account.
How the MCP part works
The list is the part an AI agent is good at. Connect the Launch Llama MCP server to Claude, Cursor or ChatGPT and ask it to run the automate-google-indexing Mini App with your new URLs: it returns the same grouped, capped JSON this page builds. Pair it with a Search Console MCP server or your sitemap so the agent picks pages that are not indexed yet, then have it save the JSON where the extension reads it each morning.
- MCP server: https://tools.launchllama.co/mcp (no sign-in needed for Mini Apps).
- Tool: run_mini_app with slug automate-google-indexing and inputs urls, properties, cap.
- Output: list.sites[] with property and urls, plus what was skipped and what is left for tomorrow.
- REST: POST /mini-apps/automate-google-indexing on the Launch Llama API, same body.
How the Chrome extension works
The Search Console Auto Indexer is a small Manifest V3 extension. It opens each property’s overview page, types the URL into the “Inspect any URL” box, waits for the result, skips pages that are already on Google, clicks Request indexing and waits for “Indexing requested”. Between URLs it pauses 6 to 15 seconds, like a person would.
- Runs on a daily alarm, and catches up when Chrome opens if the time was missed.
- Reads a pasted list, or fetches a list URL at each run (JSON, sitemap, markdown or plain URLs).
- Skips URLs it requested in the last few days, and stops a property when Google says the quota is exceeded.
- Settings and history stay in Chrome storage on your computer. No server, no API key, no account with us.
What this does not do
- Google allows about 10 Request indexing submissions per property per day. The list builder caps each property for you and keeps the rest for later.
- Requesting indexing asks Google to recrawl a page. It does not guarantee the page gets indexed: thin or duplicate pages can still be left out.
- The extension drives the Search Console page in your own signed-in Chrome. Chrome must be open at the run time, and a Google page change can need an extension update.
- It never solves CAPTCHAs or signs in for you. When Google asks for either, the run stops and leaves the window open.