A refill call is an extra request RankGear sends to the same search provider after the initial pull, made to recover usable result URLs that the first response did not return.
| Term | Refill Call |
|---|---|
| Category | Search and SERP Data |
| Also known as | Backfill Call, Deeper Call |
| Where it appears | Activity log and run completeness metadata |
What it means in RankGear
When RankGear collects a SERP, the provider’s first response sometimes falls short of the requested depth — a Top 20 run comes back with fewer than 20 usable URLs because some entries were ads, duplicates, or non-standard results that were filtered out. Rather than accept a short result set, RankGear issues one or more follow-up requests to the same provider to fill the gap. Each of those follow-ups is a refill call, and it is recorded in the activity log alongside the run’s completeness metadata so you can see exactly how many calls a run needed to reach full depth.
How to interpret it
Treat refill calls as a signal about how a run was assembled, not as a quality score. A run that needed several refill calls is normal for deep or heavily localized queries; it simply means the provider returned usable URLs in smaller increments. What matters is that every refill call inherits the run’s original settings — provider, country, language, device, location, and requested depth — so the recovered URLs are comparable to the ones from the first call. Before comparing two runs, confirm those settings match and that both reached their target completeness; a run still filling depth is not yet ready for a like-for-like read.
| What a refill call keeps constant | Provider, country, language, device, location, requested depth |
|---|---|
| What a refill call recovers | Missing usable result URLs needed to reach the run’s target depth |
Example
You launch a Top 20 organic run for “emergency plumber” localized to Austin, Texas on mobile. The provider’s first response yields only 14 usable URLs after ads and duplicate hosts are stripped. RankGear automatically issues a refill call — same provider, same Austin mobile localization, same depth — which returns the remaining positions. The activity log shows the run completing in two calls, and the completeness metadata marks it as full depth once all 20 usable URLs are present.
Important considerations
- The count of refill calls describes collection effort and completeness; it is a reliability indicator, not a ranking factor, and a page’s position is unaffected by how many calls it took to retrieve.
- Every refill call must retain the original run’s localization — provider, country, language, device, and location — or the recovered URLs would not be comparable to the rest of the run.
- Search results shift over time and by location, device, provider, and personalization context, so refill calls made during a run capture the SERP as it stood at that moment.
- Provider metrics are comparative indicators within that provider’s own scale, not Google scores; refill calls affect how complete a run is, not what any position means.
Related terms
Part of the RankGear glossary · how RankGear measures · the 870 factors.