Skip to content

Guides

Competitor monitoring: sitemap ledger, key pages, tracked terms

Add a competitor target, read the sitemap change ledger, mark up to five key pages, run on-demand tracked-term SERP snapshots — and the red lines.

Guide · competitors

Open in ChatGPTAsk questions about this pageOpen in ClaudeAsk questions about this page

Competitor monitoring reads public signals only: sitemaps, page snapshots and the SERP snapshots you run on your own tracked terms. It sits beside your page work — same console, same parent site, separate rows that never merge into your own numbers.

Add a competitor target

  1. Add the target under the site it belongs to

    A competitor is a comparison target, not a second billing entity. It hangs under a verified owned site, does not consume a paid site slot, and inherits that site as its parent. Pick the parent first; a target cannot be promoted into an owned site later.

    Console → Competitors → Add competitor

  2. Let the first poll build a silent baseline

    Enter the public domain. The first successful poll records existing URLs without reporting them as new — otherwise every launch would look like a competitor publishing your whole backlog at once. Changes start with the second snapshot.

    Console → Competitors → Add competitor → domain

  3. Know the caps before you plan around it

    Free holds one target per owned site and polls it weekly; Pro holds three and polls daily. A competitor audit covers up to 10 pages per round and draws on the same account audit pool as your own sites, so it is not free capacity. Targets carry no ownership features: no Search Console, GA4, telemetry, IndexNow, share links or schedules.

    Console → Competitors → Overview

  4. Refresh manually between polls

    Manual refresh queues a poll for the targets you select. Targets already checked in the last hour are skipped, so repeated clicks do not hammer the same site. Rename or remove a target from its overview; removing it also clears its snapshots.

    Console → Competitors → Refresh

The sitemap change ledger

The ledger is a dated list of what moved between public snapshots: URLs added, URLs removed, and lastmod changes on pages that already existed. Key pages add content changes on top. Each row names the competitor, the date, the change, the URL and its triage state, so a change can be marked Pending, Saved or Ignored without leaving the list.

Polls run weekly on Free and daily on Pro, and the feed is a digest — not a real-time alert stream. A response carries up to 50 events (100 maximum) and events are kept for 90 days. A site that rebuilds every lastmod at once is detected as a whole-sitemap refresh, and those lastmod events are suppressed rather than reported as hundreds of changes.

Read a missing entry correctly: the ledger observes public sitemaps and readable pages only. A URL absent from a sitemap, a page behind a login, a robots.txt block or a client-rendered body can all hide a real change. Absence of an event is not proof that nothing changed. The competitor feature page lists the exact source and limit per row.

Mark up to five key pages

Mark up to five pages per competitor — pricing, the main product page, the blog index — and the console re-checks them daily with conditional requests. A change means the title, meta description, word count or content hash differs from the last snapshot, and it lands in the ledger as a content_changed event with the page attached. The first fetch is a baseline, like the sitemap poll.

Choose pages whose movement would change a decision, not every URL: five is the cap per competitor, and a broad template change is better caught by the sitemap ledger. Pages behind a login or built client-side may be missed, and robots.txt is respected — a blocked page is skipped, not recorded as changed. Open the target from Competitors and use its watched-pages section; the daily check is separate from the sitemap poll.

Tracked-term SERP snapshots

The comparison runs on your own tracked terms, not on terms discovered from the competitor. Start from the tracked keyword list, choose the terms and up to three competitors, and run the check. One request per term returns the top 10 and positions your domain and every selected competitor against each other.

The run is capped at 50 tracked terms, and a successful result is reused for 24 hours — running the same terms again inside that window does not buy a second SERP read. Snapshot runs use the DataForSEO credential stored in console settings, so the vendor bills your account, not the site; snapshots are kept for 90 days. Because one request serves every competitor, three competitors cost the same as one.

Scope is the point: this is a snapshot over the terms you already track, not a daily rank history and not a picture of either site's keyword landscape. A competitor absent from the top 10 is not shown, and an unmeasured term is excluded rather than counted as zero.

Red lines

  • No traffic estimates. No competitor sessions, pageviews, conversions or revenue, modelled or otherwise.
  • No keyword mining. The SERP view only uses terms you already track; it does not discover new terms, build a keyword gap or describe the competitor's keyword landscape.
  • No backlink profile. No link counts, anchor text or referring-domain analysis for any target.
  • No competitor AI citations. AI Overview citations and crawler activity are measured for your own domain only; competitor AIO and crawler comparisons are out of scope.
  • No guessing from absence. A missing sitemap entry, a blocked page or a client-rendered body is a blind spot, not a change.

Caps and cadence by plan are on pricing; the report side is described on page decisions.

Was this page helpful?