SearchAnalysis.io: URL Submission, Index Verification and Deindex Watch

SearchAnalysis.io accepts URLs six ways, and every route ends in the same place: a batch with its own page. Pick the route that fits how your pages get published.

• Single URL: paste one address and submit it.
• Bulk paste: drop a list of URLs into one box.
• CSV upload: upload a CSV file of the URLs you want submitted.
• Sitemap import: scan a sitemap and pick the URLs you want submitted.
• REST API: POST up to 10,000 URLs to /api/v1/submissions from your own code or CI job.
• MCP tool calls: have an AI agent call submit_urls on the remote MCP server.

Batches

Each submission becomes a batch. A batch holds up to 10,000 URLs, takes an optional name and records its source: web, API, MCP or scheduled scan. Batch pages list 100 URLs per page, so a large batch stays readable. Scheduled scan batches come from sitemap monitoring when auto-submit is turned on for a site.

Priority and the 30-Day Dedup

You set a priority per URL: High, Normal or Low. Priority sets the order of work within your own queue, so the pages you care about most go first when a quota is tight.

Before anything is sent, a 30-day dedup check runs. A URL already actively tracked on your account inside the last 30 days is skipped and reported in the batch instead of being resent. That keeps a repeated paste or a script that runs twice from spending quota on the same page again.

SearchAnalysis.io tracks every submitted URL on three separate channels, and each channel gets its own status row. The rows move independently, because each one talks to a different service with a different job.

Why Only One Row Turns Green

The Google Indexing API and IndexNow are fire-and-forget. An HTTP 2xx from Google means the notification arrived, and the product shows that as Processing with the note ping accepted. A notification does not confirm indexing, so these two rows never show Indexed. The Search Console row carries the confirmation and is the only row that turns green. The Google index checker page walks through that method in full.

Quota and Reach

Google's Indexing API quota is shared across your whole Google Cloud project. URLs over the day's quota wait for the next UTC window and keep their place in line, and the Google Indexing API submission page shows how that queue behaves.

IndexNow engines share the URLs they receive with the other engines in the protocol: Bing, Yandex, Seznam, Naver, Yep, Internet Archive and AmazonBot. Google is not on that list, which is why Google gets its own two channels.

SearchAnalysis.io confirms indexing on a fixed schedule called the ladder. Each step waits longer than the one before it, and the ladder stops early the moment a URL is confirmed Indexed. Every rung is one URL Inspection request against your verified property, and each result lands in the URL's check history.

1. First inspection about 10 minutes after submission.
2. Next check 15 minutes later if the page is not indexed yet.
3. Then 1 hour later.
4. Then 6 hours later.
5. Then every 24 hours, until the ladder reaches 6 checks.

When the ladder runs out and the URL is still unconfirmed, a daily fallback keeps inspecting it. Once a URL is Indexed it leaves the ladder and enters the deindex watch: one inspection every 7 days for as long as the site stays connected. The deindex monitoring page shows what a drop looks like.

Errors and Backoff

Transient errors (HTTP 429, 5xx responses and network failures) retry after 30 minutes. Repeated failures back off exponentially, starting at 6 hours and capped at 7 days. Every inspection counts against the 2,000 a day and 600 a minute that Google allows per property, and the schedule respects those limits without trying to get around them. The check history labels each row with its source: inspection, daily check or monitor recheck.

SearchAnalysis.io puts every URL you track on one screen, the Monitor, with each channel's status side by side. It answers the daily question for a site: which pages are confirmed, which are waiting and which need you.

Monitor

• Per-channel statuses for every URL, from Queued through Indexed.
• Filters for All, Indexed, Pending and Failed, by site and by live state.
• Live polling, so statuses update while you watch a batch move.
• CSV export of the list you filtered.
• Bulk retry for URLs that need another attempt.

URL Detail

Open any URL to see its per-channel status, its full inspection history and the latest verdict fields from Google. Each inspection stores Google's health snapshot: verdict, coverageState, robotsTxtState, the indexing state, the Google-selected canonical and the last crawl time. Field names follow Google's own, so you can look any of them up in Google's URL Inspection documentation.

Check History

Every inspection adds one row, so you can see when a page first turned green and when a recheck found it gone. If the coverage state reads Crawled, currently not indexed, the guide to Crawled, currently not indexed explains what Google means by it.

SearchAnalysis.io gives each site a Google index card, a summary of what its inspections have verified.

Two Independent Signals

Coverage counts only what URL Inspection verified, divided by the pages you track. The card always prints the denominator next to it, so you see how many pages the figure covers. Because coverage divides by tracked pages, a large new batch lowers it until inspections catch up, and the awaiting-check count shows how many pages are still pending.

Appearing in search comes from a separate source. Search Console Search Analytics reports which pages earned impressions over the last 7 days across the whole site, whether or not you submitted them. Coverage tells you which tracked pages Google confirmed. Appearing in search tells you which pages searchers are seeing.

Queries, clicks, positions and rank tracking are PLANNED and will arrive later. The Google index checker page explains how each inspection feeds this card.

SearchAnalysis.io reads the HTML of each submitted page and looks for JobPosting or BroadcastEvent structured data. Those are the two types Google names in its Indexing API documentation: "The Indexing API can only be used to crawl pages with either JobPosting or BroadcastEvent embedded in a VideoObject."

What a Best-effort Badge Means for You

A Best-effort badge is normal for most content sites. The Indexing API notification still goes out, and confirmation still comes from the Search Console channel, which inspects every submitted URL whatever badge it carries. A blog post with Best-effort can reach Indexed the same way a job listing does: through a PASS verdict or an indexed coverage state.

Quota Context

Google's default is 200 publish requests a day for the whole Google Cloud project, and Google writes that "The quota may increase or decrease based on the document quality." SearchAnalysis.io queues anything over the day's quota for the next UTC window. The Google Indexing API submission page covers the queue in detail.

To test one public page before you sign up, run it through the free indexability checker. It checks page load, redirects, robots.txt, indexing directives, canonical and thin content.

SearchAnalysis.io watches the sitemaps you add to each site and keeps a page inventory of every URL it finds in them. Scans run on a schedule, and Scan now runs one right away when you have just published.

1. Add one or more sitemap URLs to a site.
2. A scan reads each sitemap and follows sitemap index files to their child sitemaps.
3. Every URL found enters the page inventory with a first seen date.
4. Later scans update the last seen date, and a URL that leaves the sitemap is marked Removed.

Inventory States

Each inventory row moves Discovered → Submitted → Indexed, or ends at Removed when it disappears from the sitemap. Indexed here means what it means everywhere in the product: URL Inspection confirmed it.

Auto-submit

Turn on auto-submit for a site and newly discovered URLs are submitted on their own, as a batch with the source scheduled scan. Those batches go through the same three channels and the same inspection ladder as anything you submit by hand.

How Sitemaps Reach Google

Google announced in June 2023 that its sitemap ping endpoint was going away. Sitemaps reach Google through Search Console, the Search Console API or a reference in robots.txt. A single sitemap is limited to 50MB uncompressed or 50,000 URLs, and Google uses <lastmod> when it is consistently and verifiably accurate. The sitemap monitoring page covers scans in more depth.

SearchAnalysis.io organizes everything by site. A site is one website matched to one Search Console property, and setup takes four steps.

1. Add the site. Enter the website you want tracked.
2. Connect Google with OAuth. Sign in with the Google account that holds your Search Console access.
3. Pick the property. Choose the matching Search Console property: a domain property (sc-domain:) or a URL-prefix property.
4. Verify the IndexNow key. SearchAnalysis.io generates a 32-character hex key. You host it at the address below, and the product fetches the file and checks that the contents match before it sends any IndexNow notification.

https://yourdomain/{key}.txt

How Google Tokens Are Stored

Google OAuth tokens are encrypted at rest with AES-256-GCM. They are decrypted only in memory, at the moment a call to Google needs them, and never sit decrypted in storage. The deindex watch runs only while a site is connected, so disconnecting a site stops its weekly rechecks.

Limits Counted per Property

Two budgets are counted per property: 2,000 URL Inspection requests a day and 600 a minute from Google, and the 10,000 IndexNow URLs a day that SearchAnalysis.io sets for each property.

The IndexNow protocol accepts keys of 8 to 128 characters, so the 32-character hex key sits well inside that range. The IndexNow submission page explains the key file and every response code, and the SearchAnalysis.io privacy policy covers how account data is handled.

SearchAnalysis.io separates errors that clear on their own from errors that need you, and it emails you about the second kind.

Failed, Dropped and Cancelled

• Failed: an error that needs a person. The error text is shown on the URL so you know what to change.
• Dropped: filtered out before sending. Typical causes are a URL outside the site's domain, a duplicate or an invalid format. Dropped URLs never reach a channel, so they spend no quota.
• Cancelled: the label a URL carries when its submission is cancelled.

Automatic Retries

Transient problems retry without your help. HTTP 429, 5xx and network errors try again after 30 minutes, and repeated failures back off exponentially from 6 hours up to a 7-day cap. Once you fix the cause, filter the Monitor to Failed and one site, then retry the whole list with bulk retry.

Emails You Receive

All three are transactional. A failure email names the URL and carries the same error text the URL detail page shows. Deindex alerts by email and Slack, along with weekly digest reports, are PLANNED. Until they ship, a dropped page appears as amber Not indexed in the Monitor, which the deindex monitoring page describes.

SearchAnalysis.io exposes submission and status through REST API v1 and a remote MCP server, so scripts, CI jobs and AI agents work with the same account you use in the browser. Create a bearer API key in Settings; every endpoint and every MCP tool authenticates with it.

Send an Idempotency-Key header with each POST. If your job retries after a network error, the API returns the original batch instead of creating a duplicate. The OpenAPI 3.1 document is public. A job can call GET /api/v1/quota first to see how much engine quota remains before it sends a large batch.

MCP Server

The remote MCP server at https://searchanalysis.io/mcp offers six tools: list_properties, submit_urls, list_submissions, check_submission, check_url_index_status and get_quota. Install it in Claude Code with one command and your bearer API key:

claude mcp add --transport http searchanalysis https://searchanalysis.io/mcp

AI agents find the public pages and machine endpoints in llms.txt for AI agents, and the SearchAnalysis.io developer documentation covers each request and response.

SearchAnalysis.io labels every item in this panel PLANNED. None of them is available today, and each one is written here as future work. Shipped features carry a SHIPPED badge in the panels above; this panel holds only items that do not exist in the product yet.

• Deindex alerts by email and Slack (PLANNED): will notify you when the deindex watch finds a page that dropped out, with weekly digest reports alongside.
• Merchant Center title module (PLANNED): will connect Google Merchant Center, fix flagged product titles through a supplemental data source and track each product until it is approved.
• Drip-feed submission (PLANNED): will pace a submission over a number of days you choose.
• Search performance intelligence (PLANNED): will go past appearing in search to queries, clicks and positions, with rank tracking.
• Workspaces for agencies (PLANNED): will group sites into workspaces or projects, with shareable status pages for clients.
• Resubmission on lastmod (PLANNED): will resubmit a URL automatically when its sitemap lastmod changes.
• Sitemap checker (PLANNED): will join the free indexability checker as a second free tool.

Merchant Center Today

Product titles already have a free fix in the browser. Case Changer Pro is a free tool from SearchAnalysis.io, and its Product Title Fixer corrects product titles in a Shopify product CSV, first 50 products free. The Merchant Center waitlist is open, and its members get a say in the fix rules.