SERP feature tracking

Every rank check RankMeFast already runs for you also records which search-result features appeared for that keyword. There is no separate unit to buy and no extra depth requested.

<!-- docs-truth: metric=none; unit=byproduct-of-serp_checks; cache-hits=count; refund=not-applicable; cadence=follows-rank-check; estimates=provider-observation -->

What is recorded

For each check RankMeFast stores whether a featured snippet, People Also Ask block, local pack, video, image, shopping, or knowledge-graph result was present, together with the organic result set up to a ceiling of 100 rows.

Ownership is decided by exact normalized-host match against your site domain. If the host of a feature result equals your site host, the feature is marked as yours; otherwise it is recorded as present but not owned.

History and retention

Each tracked keyword keeps a per-check history you can read as a dot matrix or, for screen readers and exports, as an equivalent table. Both views show the same stored observations.

Observations are retained for 90 days, and the newest 30 checks per keyword are kept. Older rows fall out of the window and are not reconstructed.

Honest limits

Capture is a byproduct of the rank check you already pay for. Because no extra depth is requested, a live check can store fewer than 100 organic rows.

RankMeFast can only tell you that a feature was observed or not observed on a stored check. It never claims a feature is absent from Google, and it never fills a gap by estimating.

Plans and availability

This capture has no separate allowance of its own — it rides along with the rank checks your plan already includes.

The surface is gated by the SERP_FEATURE_TRACKING_ENABLED rollout flag: when an operator turns it off, new runs are refused with a localized message while stored results stay readable.

For units and plan limits, see Pricing.

Before acting, compare this guide with the stored evidence and status shown in RankMeFast.

Back to the docs index