Instant Google Indexing — batch URL submit via Indexing API
Submitting URLs to Google one at a time through the "Inspect URL" tool in Search Console works fine for a handful of pages. The moment you publish a content series, push a large technical fix, or re-price hundreds of product pages, that manual flow breaks down completely. SEO Scanner solves this by integrating Google's official Indexing API into a visual batch interface: select URLs from your scan table, click Submit, and SEO Scanner notifies Google for each one — showing you live progress and per-URL results as they come back.
Start batch submission →Why batch indexing beats manual GSC submission
Visual URL selection
Every URL on your site appears in an interactive table after a scan. Use single checkboxes, shift-click ranges, or select all — then submit exactly what you need.
200 URLs submitted in under a minute
What takes 30 minutes of clicking through GSC manually takes seconds here. Google's daily quota of 200 requests is saturated in one efficient batch, not one URL at a time.
Per-URL outcome tracking
See exactly whether Google accepted each request or returned an error. Common issues like 'URL not in property' or 'quota exceeded' are shown with actionable messages.
Persistent request history
Every batch is logged with timestamps, URLs, request type, and outcome. Filter by date, status, or URL text. Export as CSV for client reporting or internal audits.
Live quota counter
A real-time counter shows how many of the 200 daily requests you've used and how many remain. Resets automatically at midnight UTC per Google's policy.
Cancel mid-batch anytime
Started a 150-URL batch but changed your mind? Click Cancel — the batch stops cleanly with no pending requests left in flight.
When batch indexing makes a measurable difference
- Publishing a content series — launched 50 blog posts or guide pages in one week? Select them all in the table and submit in a single batch instead of visiting GSC individually.
- Post-deploy technical fixes — updated canonical tags, fixed duplicate meta descriptions, or corrected hreflang across 80 pages? Signal those changes to Google immediately rather than waiting for the next crawl cycle.
- E-commerce price updates — re-priced 400 products ahead of a promotional weekend? Submit all affected URLs so Google renders updated prices in rich snippets before the campaign begins.
- Recovering non-indexed pages — GSC's Coverage report shows 25 URLs as "Discovered – currently not indexed"? Submit the entire group to push them back into the crawl queue with urgency.
How the Indexing API connection works
Connection happens through Google's official OAuth flow. Click "Connect Google Search Console", grant the required scopes (GSC property read + Indexing API write), and SEO Scanner receives a refresh token stored securely. From that point every submission uses your own GSC credentials — Google sees you as the sender, not SEO Scanner as an intermediary.
This means requests are attributed to your GSC property, they count against your own Google Cloud quota (200/day), and they respect your property permissions. If you manage multiple properties in GSC, choose the correct one before submitting.
Indexing API vs. sitemap.xml — understanding the difference
Your sitemap.xml remains the primary mechanism for telling Google which URLs exist on your site — keep it accurate and submitted in Search Console. The Indexing API does not replace the sitemap; it complements it. The sitemap says "these URLs exist"; the API says "this specific URL just changed — please recrawl it now".
In practice you use both: sitemap for comprehensive URL coverage, Indexing API for priority re-crawl signals on high-value or recently changed pages. SEO Scanner handles the API; use the Sitemap tab to validate and inspect your sitemap structure.