Index monitoring

Know which pages Google actually indexed.And why the rest didn't.

Seomely connects to Search Console, tracks every URL on your site, and keeps a permanent record of its index status. So when a page quietly falls out of Google, you find out the same week, not six months later.

Read-only Search Console access. We never crawl your site.

example.com / coverageLast run 06:04 UTC · 1,500 / 2,000 quota
URLs monitored
4,182
Indexed
3,647 87.2%
Not indexed
535 12.8%
Dropped out, last 30d
24 were indexed
URLStatus90-day historyLast checked
/blog/indexnow-vs-indexing-apiDeindexed 6 days ago2h ago
/pricingSubmitted and indexed2h ago
/guides/schema-markupRecovered 9 days ago3h ago
/blog/crawl-budget-guideCrawled, not indexed2h ago
/docs/api/authenticationDiscovered, not crawled5h ago
/careers/senior-engineerBlocked by robots.txt5h ago
Indexed Crawled or discovered, not indexed Blocked, error, or dropped out Not yet observedOne tick per day, newest on the right
The gap

Search Console shows you today. It never remembers yesterday.

Inspect a URL in Search Console and you get one number: its status right now. A page that was indexed for two years and dropped out last Tuesday looks exactly like a page that was never indexed at all. That single missing dimension is the difference between knowing and guessing.

Search Console alone

A snapshot, one URL at a time

  • No history. Yesterday's status is gone the moment it changes.
  • No alerts when a page leaves the index.
  • Coverage reports lag and sample, so small sites see nothing.
  • One URL per inspection, by hand.
  • No way to tell whether indexing is getting better or worse.
Search Console + Seomely

A continuous record of every URL

  • Every observation stored, so you can see the exact day it broke.
  • Alerts the moment an indexed page stops being indexed.
  • Your whole sitemap, inspected on a rotation, every day.
  • A plain-English cause and fix for every non-indexed state.
  • Indexed share trended over 90 days, annotated with what moved it.
Seomely portfolio view showing seven monitored properties, each with indexed share, a coverage meter, and counts of URLs with no inbound links
Every property at once, which Search Console cannot do.
How it works

Four steps, then it runs itself.

01

Connect

Sign in with Google. We ask for exactly one scope, webmasters.readonly, so Seomely physically cannot change anything in your Search Console.

02

Inventory

We read your sitemap, follow nested sitemap indexes, and unpack gzipped ones. URLs that disappear from your sitemap get flagged, never deleted, because that is a signal too.

03

Inspect

URLs rotate through the URL Inspection API at up to 1,500 a day per property. Google's limit is 2,000, and we leave the rest for your other tools rather than quietly eating it.

04

Detect

Each result is compared with the one before it. A page that was indexed and no longer is becomes a critical alert that morning, not a number in a monthly report.

Diagnostics

"Crawled, currently not indexed" is not an explanation.

Google tells you the state. Seomely tells you the cause, the fix, and whether resubmitting would change anything. Usually it would not, and we say so.

https://example.com/blog/crawl-budget-guide
Verdict
Crawled but not indexed
Cause

Google fetched the page and chose not to index it. This is a quality judgement, not a technical fault. It is the most common reason real pages stay out of the index.

What to do

Strengthen the page: more substantial and distinct content, a clearer purpose, and internal links from related indexed pages.

Submission will not help here

Resubmitting the same content does not change a quality judgement. We will not waste your quota pretending otherwise.

History

Indexed for 12 days in June after an internal link was added from /blog/technical-seo, then dropped again when that link was removed.

Fourteen distinct causes, not one generic message

Robots blocks, noindex directives, soft 404s, redirect chains, server errors, canonical conflicts, duplicate clusters, and crawl-budget starvation each get their own explanation and their own fix.

It tells you when we cannot help

Every diagnosis carries an honest flag for whether submission could plausibly change the outcome. On most non-indexed states, it cannot, and pretending otherwise is how the rest of this category operates.

The history is the evidence

Because every observation is kept, a diagnosis can point at the day something changed and what changed with it, instead of describing the symptom you can already see.

Regression detection

Find out the week it breaks.

Every inspection is compared against the previous one. State changes become events, and the ones that matter reach you by email the same morning.

Indexed share over 90 days, showing a sharp drop and a recovery
Example data. A robots.txt rule shipped on day 46 and was fixed on day 58. The dip is the product: without a record there is nothing to notice.
deindexed/blog/indexnow-vs-indexing-api was indexed and no longer isSubmitted and indexed → Crawled, not indexed
robots_blocked/careers/senior-engineer is now blocked by robots.txtALLOWED → DISALLOWED
canonical_changed/products/plans — Google selected a different canonical/products/plans → /pricing
fetch_error/docs/api/webhooks — Google can no longer fetch this pageSUCCESSFUL → SERVER_ERROR
indexed/blog/sitemap-best-practices is now indexedDiscovered, not crawled → Submitted and indexed
Submission

Included. Just not oversold.

IndexNow, on every change we detect

When your sitemap gains a URL or a page changes, we notify the IndexNow network automatically. It is genuinely useful, it is instant, and it is the part of submission that actually works.

BingNaverYandexSeznamYepGoogle — does not participate

What we will never claim

Google's Indexing API officially supports two content types: job postings and broadcast events. Tools that pipe your blog posts through it are working outside Google's terms, and the access can be revoked.

Seomely does not do that, and does not promise to force anything into Google's index. We tell you what Google decided, when it decided it, and what would have to change. If a page is not getting indexed because it is thin, the honest product tells you that instead of selling you a submission quota.

API & MCP

Everything the dashboard does, your agent can do too.

The same index history behind the dashboard is available over a REST API and as an MCP server, so Claude, Cursor, or your own automation can investigate indexing problems directly.

$ curl https://api.seomely.com/v1/urls/unindexed \
    -H "Authorization: Bearer sk_live_..." \
    -d "project=example.com" \
    -d "since=30d"
get_unindexed_urlsEverything not in the index, with causes
check_index_statusCurrent state for any URL
get_index_historyFull observation timeline
get_regressionsPages that stopped being indexed
diagnose_urlCause, fix, and whether submitting helps
sync_sitemapRe-read the sitemap now
submit_urlsNotify the IndexNow network
get_project_statsCoverage totals and trend

Ask your agent "which pages stopped being indexed this month, and why?" and it has the data to answer properly.

Access & privacy

You are handing us Search Console access. Here is exactly what that means.

It is a fair thing to hesitate over. So rather than a trust badge, here is the specific scope we request and the specific things we cannot do with it.

One scope, read only

We request webmasters.readonly and nothing else. Write access is not in the token, so Seomely cannot change a setting, submit a sitemap, or remove a URL even if it wanted to.

We never store your page content

We keep the URL and the index metadata Google returns: coverage state, canonical, crawl time, fetch status. We do not fetch, render, or store the page itself.

We never crawl your site

The only thing Seomely requests from your server is your sitemap file. Your pages are never hit by us, so we add nothing to your crawl load or your bandwidth bill.

Revoke in one click, from Google

Access lives in your Google account permissions, not ours. Revoke it there and every background job for your property stops the same day. Delete your account and the history goes with it.

Pricing

Priced on URLs monitored, not on submissions sold.

Free
$0
forever
  • 1 property
  • 500 URLs monitored
  • 90 days of history
  • Weekly inspection runs
  • API and MCP, 1,000 calls a month
Start free
Most useful
Pro
$24 /mo
billed annually, $290
  • 5 properties
  • 25,000 URLs monitored
  • Unlimited history
  • Daily inspection runs
  • Regression alerts by email
  • IndexNow autopilot
  • API and MCP, 25,000 calls a month
Start with Pro
Agency
$82 /mo
billed annually, $990
  • 25 properties
  • 250,000 URLs monitored
  • Unlimited history
  • Client workspaces
  • Client-ready exports
  • Webhooks
  • API and MCP, 250,000 calls a month
  • Priority support
Start with Agency
What "daily" actually means

Google allows 2,000 URL inspections per property per day and we use at most 1,500 of them, so your other tools keep their share. That means a property with 5,000 URLs is swept completely every four days, and one with 25,000 takes about two and a half weeks. Runs happen daily; each individual URL is re-checked on rotation. New pages and anything currently broken jump the queue, so the URLs you care about are checked far more often than the average suggests. Anyone promising daily checks on every URL of a large site is describing something the API does not allow.

Why not a lifetime deal?

A lifetime price makes sense for something you download once. This is not that. Seomely inspects your URLs every day, stores years of history, and has to keep working as Google changes its APIs. Those costs never stop, so charging once for them ends one of two ways: the service quietly degrades, or it disappears. A subscription is the version of this that can still be running in three years, which is precisely when your index history is worth the most.

Larger than the Agency plan, or need something specific? Email us and we will work out a plan that fits. A real person replies, usually the one who built it.

Your index history starts the day you connect.

There is no way to recover the months you did not measure. The best time to start recording is now.