stillindexedStart monitoringOpen the app

Know before Google does.

We re-check your client's pages as often as every 15 minutes and tell you the moment one stops being indexable.

Status200
Redirectsnone
Meta robotsnoindex, nofollow
X-Robots-Tagnone
Canonicalself
TitlePricing plans | Example

Blockedmeta robots

An example page, exposed. Put any URL in the leader to run your own.

GET https://example.com/pricing
HTTP/1.1 200 OK
214 ms
01h01h, pass
02h02h, pass
03h03h, pass
04h04h, pass
05h05h, pass
06h06h, pass
07h07h, pass
08h08h, pass
09h09h, pass
10h10h, pass
11h11h, pass
12h12h, pass
13h13h, pass
14h14h, pass
15h15h, pass
16h16h, pass
17h17h, pass
18h18h, blocked
19h19h, needs a check
20h20h, pass
21h21h, pass
22h22h, pass
23h23h, pass
00h00h, pass
Last 24 hours · one monitored URLSample strip · yours fills in from your first check

A deploy ships noindex.
Nobody notices for days.

The page still loads, so every uptime check stays green. The indexing failure is silent until the traffic drops.

  1. 09:12

    Deploy

    Staging directives reach production.

    the change
  2. 09:12

    The page

    Still returns HTTP 200, so uptime checks stay green.

    looks fine
  3. 11:40

    Googlebot

    Reads the blocking directive and stops indexing.

    damage
  4. 3 days

    The client

    Asks why the traffic went.

    damage

What we watch

Headers, HTML, routing and site-level checks. Everything that decides whether a page can be in the index at all.

Indexing directives

The signals that remove a URL from search while the page still looks normal.

  • meta robots
  • X-Robots-Tag
  • robots.txt per URL

Responses and routing

The route Googlebot actually receives, including every hop before the page.

  • HTTP status
  • redirect chain
  • canonical target

Site integrity

Slower failures that undermine a migration or take a client site out of service.

  • title and H1
  • sitemap health
  • SSL and domain expiry

Every check comes from published egress IPs. No Google account, no snippet on the client's site, no ownership verification.

Telegram first.
Email every time.

An alert you cannot trust is worse than no alert, so a critical change is checked twice before it reaches you.

  1. On the cycle

    A scheduled check finds a change

    Every 30 minutes on Starter, every 15 on Agency.

  2. 60 seconds later

    Critical changes get a second fetch

    A re-check suppresses one-off failures and flapping. Nothing that reverted is ever sent.

  3. Then

    Telegram takes the fast path

    Email is always sent too, so the incident has a durable record you can forward.

Two plans. No free tier.

The public tools stay free and ungated forever. Continuous monitoring starts at $29 a month, and every purchase has a 30-day refund.

Starter

For independent consultants

$29/month

$290 a year

  • 10 Sites, up to 25 URLs each
  • Checked every 30 minutes
  • Telegram alerts, email always sent
  • Weekly monitoring report
  • 90 days of change history
Choose Starter

Agency

For teams running client portfolios

$79/month

$790 a year

  • 50 Sites, up to 25 URLs each
  • Checked every 15 minutes
  • Telegram alerts, email always sent
  • White-label weekly client reports
  • 365 days of change history
  • Migration Watch (planned)
Choose Agency

No free plan and no trial: checkout comes before setup. Every purchase has a 30-day no-questions refund, and payments are handled by Polar as merchant of record.

Find the change before the client does.

Add the client sites that matter, pick your alert channel, and let every confirmed incident come to you.

Start monitoring from $29