Skip to content

Public beta: some things may break while we finish them.

RankMeFast, public beta
Page performance

Research and tracking

Page performance

How the Pages tab chooses data, compares snapshots, and counts refreshes.

Page performance

Open a site and choose Pages to compare search performance with the latest crawl inventory. The tab reads stored data when you open it. It collects new data only when you choose Refresh or Get ranking data.

Which source appears

RankMeFast uses Google Search Console when the connected property covers the site. While it is connected, Search Console is the only source, even during its first collection or when the selected window has no rows. RankMeFast does not fill an empty Search Console source with ranking-snapshot estimates.

If Search Console is not connected, needs reconnection, was revoked, or has no matching property, the tab can use the latest stored ranked-keyword snapshot. The source label says whether this is a DataForSEO snapshot or deterministic demo data. If neither source has stored data, the tab explains what to connect or collect.

Metrics and date windows

Search Console clicks, impressions, CTR, and average position are observed metrics for the selected rolling window of 7, 28, or 90 days. Google reporting is delayed by three days. Search Console may sample or cap rows, so check the coverage note before comparing totals.

In a ranking snapshot, position, search volume, difficulty, ranking-keyword count, and estimated traffic are estimates from one point in time. A ranking snapshot has no clicks, impressions, or CTR. Those fields show Not available, including when another metric is genuinely zero. Changing the window changes the history and comparison, not the snapshot's headline numbers.

Since previous sync compares the current successful snapshot with the immediately previous eligible snapshot. It is not a previous-period comparison. Open a page to see its associated Search Console queries or fallback keywords and up to 90 stored trend points.

Opportunities and crawl context

  • Striking distance means the page is above position 3 and no lower than position 20, with enough observed impressions or estimated search volume to meet the rule.
  • Low CTR applies only to Search Console rows with enough impressions, a top-ten average position, and CTR below the rule threshold.
  • Declining and Winning compare position or observed clicks with the previous successful sync. A position gain counts as Winning only on page one or when the page earned clicks.
  • Too little data marks a Search Console page with fewer than 20 impressions and no clicks. It gets no movement label until more evidence arrives, and it sorts below pages with real opportunity.
  • Visible but not crawl-indexable means search performance exists while the latest RankMeFast crawl marked the page non-indexable.
  • Unmeasured means the latest crawl found a crawl-indexable page but the selected performance source has no row for it.

Crawl indexability describes what RankMeFast found while crawling. It does not prove whether Google indexed a URL. A provider-visible non-indexable page remains in the list so you can investigate the conflict.

The coverage note also says how many pages your last audit crawled and why the crawl stopped: it reached the audit's page limit, found no more links to follow, was stopped, or hit an error in the crawl service. Our crawler reads the HTML your server sends, so pages that are only linked after JavaScript runs are not found. Audits from before this was recorded say that no reason was recorded.

Refresh cost and stale data

Search Console refresh reuses the connected Search Console sync and does not spend a keyword lookup. Refreshing a ranking snapshot costs one keyword lookup, including a cache hit. The button only says Refresh. The cost is shown in the empty state before you get ranking data for the first time, and again in the message you see when the limit is reached. Opening detail, searching, filtering, sorting, changing page size, and moving between result pages are stored reads and do not spend usage.

If a refresh fails, the last successful snapshot stays visible and is marked stale. A ranking snapshot is also marked stale once it is older than the period ranking data stays fresh. Use the refresh button to try again when the connection is back.

Deletion and exports

Deleting a site, or completing an account-deletion request, removes its stored Pages snapshots. The current account export does not include Pages snapshots or GSC and rank time-series history, so do not treat that export as a backup of these trends.

Troubleshooting

  • For Syncing, wait for the first Search Console collection and refresh the view later.
  • For Reconnect, restore the Google connection from the Google tab.
  • For Property does not match, select a Search Console property that covers the site's exact URL prefix or domain.
  • For No stored source, connect Search Console or choose Get ranking data, which uses one keyword lookup.
  • For Limit reached, review keyword-lookup usage or your plan. Existing stored snapshots remain readable.
  • For Unavailable, retry the same source. RankMeFast does not silently switch away from usable Search Console data.

See also Connecting Google Search Console and Rank tracking.

Back to the docs index