See Which of Your URLs Google Actually Indexed

You publish a page, submit it to Google's Indexing API, and get a clean 200 back. So it's indexed, right? You don't actually know. The API confirms your request was accepted — nothing more. Whether Google ever crawled the page, decided it was worth keeping, or quietly filed it under "discovered but not indexed" is a separate question the submission never answers.

To find out the old way, you open Search Console, paste in a URL, wait for the inspection to run, read the verdict, and repeat — one page at a time, often days after you submitted. For a site with more than a handful of pages, nobody does this consistently. So you submit into a void and hope, and your sense of "how much of my site is actually indexed" stays a guess.

What changed

The Google Request Index history now shows each submitted URL's real Google verdict, right next to the submission status. Every row tells you whether the page is indexed, discovered but currently not indexed, or unknown — read straight from URL Inspection — so the list you already have of "URLs I sent to Google" becomes a list of "URLs Google actually kept."

How it works in practice

Every submitted URL carries its real verdict

Open the History tab in Google Request Index and you see every URL sent through the Indexing API for the current project — including the skipped and failed ones. The new Index Status column sits next to each row: a green Indexed when Google has the page, an amber Discovered · currently not indexed when it doesn't yet, or unknown when there's no verdict to read. A running summary at the top tells you how many of your submissions are confirmed indexed, so "is my site getting picked up?" has an actual number instead of a feeling.

It reads from a cache, so it doesn't burn your quota

URL Inspection has a daily quota, and re-checking hundreds of URLs every time you open the page would blow through it fast. So statuses are read from a local cache first: a URL Google already confirmed indexed is never re-inspected, and a URL it's never seen is checked once, automatically. When you do want a fresh reading on a specific page — you fixed something and want to know if it took — every row has a manual re-check. You spend inspection calls deliberately, not by accident.

Submit your whole site at once

Knowing what's indexed is only half the loop; the other half is getting more of it submitted without hand-typing URLs. Both Google Request Index and IndexNow can now load a whole batch at once. Point the importer at a file — one URL per line, or CSV/TSV cells, with quotes, a header row, blank lines, and comments all tolerated — or paste your sitemap URLs and it pulls every same-host page they list, following one level of sitemap index. Everything is merged, deduplicated, and dropped into the queue for review before a single request goes out.

Before vs after

Knowing what Google indexed	The old way	With Live Index Status
Confirmation you get on submit	A 200 that means "request accepted"	The same, plus the page's real index verdict over time
Checking a verdict	One URL at a time in Search Console	Every submitted URL, in one history list
Cost of re-checking	Manual, and it eats inspection quota	Cached — known URLs are never re-inspected
Submitting a whole site	Copy-paste URLs a few at a time	Import a file or sitemap, deduplicated, in bulk
"How much of my site is indexed?"	A guess	A running count of confirmed-indexed URLs

Who benefits most

Indie marketers running their own SEO. You don't have an SEO team watching Search Console daily. A single history that reconciles what you submitted against what got indexed gives you the one number that matters without a monitoring habit.

Anyone shipping pages in volume. Programmatic pages, a docs site, a wave of comparison or alternative pages — when you publish dozens at a time, bulk import gets them submitted and the index column tells you which ones stuck, so you can chase the stragglers instead of assuming.

Freelancers and agencies reporting to clients. "142 URLs submitted, this many confirmed indexed" is a screenshot you can put in a report, backed by Google's own verdict rather than your word.

Also in this release

Version 0.11.0 lands more than the indexing loop:

• Cross-post a piece to another channel. A new Post to other channel action opens Post Now with nothing preselected, so a piece you wrote for one channel — say Discord — can go to a different connected channel like X, reusing its text and attached media as-is.

  

• Download generated media. Campaign pieces with an attached image or video get a Download button in the detail preview, and the asset library adds Download to any locally stored file — each saving through a standard Save dialog.

  

• One-click YouTube connection. YouTube now connects through 1MarketingTool's verified Google app, so uploading videos no longer requires registering your own OAuth credentials — with an Advanced option for power users who want to run through their own Google project.

Try it

Update to 0.11.0, open Google Request Index, and switch to the History tab. You'll see the index verdict on every URL you've submitted — and with file and sitemap import a click away, getting the rest of your site into the queue takes about as long as this paragraph did to read.