SERP Rank Checker Depth: How Far Down Google Results Actually Go

A SERP rank checker fetches a Google results page and tells you where a URL appears on it. The free ones mostly stop at position 100, and at least one says so on its own page: "check the top 100 Google search results for multiple keywords."

That reads like a tool limitation. It is closer to a description of how much results page there is to check.

On September 11, 2026 we requested 200 results per query across six keywords, US location, English. Google returned between 83 and 128 organic results on five of the six queries, then stopped. The deepest position served anywhere in the test was 142, on "seo audit". One query produced no results past position 100 at all.

So if your plan is a "google ranking check top 1000", here is the uncomfortable part: for most queries there is no position 1000 to be in. The limit you keep hitting belongs to Google, not to your checker. What you do with that fact is the useful question, and it changes how you should spend your rank-tracking budget.

What we tested, and what came back

Method: six commercial and informational queries, one SERP request each on September 11, 2026 at a United States location in English, desktop, with a depth parameter set to 200. The API returns what Google serves, so a request for 200 results simply reveals how many exist.

Requesting 200 results does not produce 200 results. It produces however many Google is willing to serve, which ranged from 83 to 128 in this test.

Two rows deserve a second look.

The first row shows a query where the result pool ends before position 100. "How to check google rankings" returned 83 organic results and stopped at position 94. Nothing downstream of 100 exists for that query, so a rank check past 100 would return an empty set. No tool failure involved.

The last row shows the opposite problem. "Serp rank checker" reported 1,440,000 results and served 107 of them. This is the gap that makes "top 1000" promises confusing. Google is happy to report a seven-figure result count and equally happy to stop serving somewhere around position 119.

Quality check before you trust any of this: repeat one query on two different days and compare the deepest position served. If it moves, treat depth as a soft ceiling rather than a fixed number. Ours moved by a few positions between pilot runs.

The pattern past position 100 is not what you expect

The interesting finding is not the depth. It is the composition.

Past position 100, the results stopped looking like a listicle SERP and started looking like a video shelf. On "mobile rankings", every single result past position 100 was a YouTube page. On "backlink checker" it was 20 of 28. On "seo audit" it was 24 of 39.

On "backlink checker" and "seo audit", the remaining deep results belonged to a small number of strong domains repeating: ahrefs.com appeared three times past 100 on "seo audit", neilpatel.com twice. One tool site, serpstracker.com, held three deep positions on "serp rank checker".

That tells you something specific about the deep pool. It is not a second chance for your blog post. It is mostly where video and a handful of large domains absorb whatever demand remains after page one.

Where a deep pool exists, it is dominated by video and repeat domains. Your page 6 blog post is competing in a different result set than your page 1 blog post.

What free checkers get right, and what the depth limit hides

Free SERP checkers are not the problem. Several of them are genuinely well built. SerpRobot lets you pick a region and switch between desktop and mobile on the free checker. SEO Review Tools exposes both google.com and google.com (mobile). Ahrefs and Semrush both publish free SERP checkers with competitive data behind them. WhatsMySerp runs 10 checks a day at no cost.

The limit that matters is conceptual, and it survives even on paid plans. A checker answers one question: where does this URL rank right now, at this location, on this device, for this query. That is a snapshot. It is not a measurement of visibility, and Google is explicit that the snapshot is unstable. Search Console's own help documentation says: "Search results are specific to the time, place, device, and recent history of the person searching."

Three things follow from that sentence, and they are the reason rank depth gets over-sold:

• A position is not a single number. Every check is one sample from a distribution. Commercial queries reshuffle by location, device, and personalization history.
• Deep positions rarely produce sessions. A result at position 110 sends close to nothing. Tracking it is only useful when it is trending upward and you want an early signal.
• Your free tracker already tells you which deep positions matter. Search Console gives you average position for every query you appear for, including deep ones, without a depth limit and without a per-check cost.

How to check rank depth without wasting money

Rebuild the workflow around the question, not the tool. Four questions, four sources.

Two practical rules keep this cheap.

Rule one: only track depth for queries that have earned it. A query qualifies when Search Console shows it already receiving impressions at a deep average position and the query has commercial intent. Everything else gets tracked at page-one depth only. If you are running this inside an agent workflow, that qualification step is a filter, not a judgement call. Our SEO agent guide covers the task-fit side of that split, including why agent work should stay on the same-shaped task every week.

Rule two: store the raw pull, not the summary. If you only save "position 34", you cannot later ask whether the SERP got longer, whether video took over, or whether a competitor entered. Saving the raw top-200 payload costs nothing extra and answers questions you have not thought of yet. This is the same discipline behind a weekly ranking report you can actually re-read.

Where the deep pool changes your content decisions

Once you know what lives past position 100 on your target queries, two decisions get easier.

Decide between a page and a video. On four of the five queries in this test that had a deep pool, video held between 40% and 100% of results past position 100. If your target query behaves that way and you have no video asset, a written page is competing in a slot that is mostly not written content. That does not make the page wrong. It makes a video the cheaper route to the deep pool.

Decide which page on your site deserves the link. Because repeat domains absorb the deep pool, a second or third URL from your own site can sit there without cannibalizing anything. That is a legitimate placement for a supporting page, and it is one of the few ways to hold more than one position on a query. Our notes on how AI SEO platforms track ranking performance over time cover the reporting side of that pattern.

Auspia view: depth limits are a data-model problem, not a tooling problem. Google caps what it serves, your checker caps what it asks for, and neither number is the one your business cares about. Track the queries where a deep position is moving, and let the rest go.

When a deep rank check is the wrong move

Skip the deep pull when any of these is true:

• The query has fewer than a few hundred monthly searches. A position 60 ranking on a 90-search term produces nothing worth a monthly check.
• Your impressions on that query come from a single country you do not sell in.
• You are mid-migration or mid-consolidation. Comparing deep positions across a moving URL structure produces noise, and you will chase your own redirects.
• The query is branded. Brand queries behave differently, and deep positions there usually mean something other than an SEO problem.

If you already have a monitoring loop running, the deep-pull data belongs in the weekly review rather than in the alert path, which is the split we describe in this ranking monitor design.

Takeaways for your team

• Request more than Google serves and you learn the ceiling, not your ranking. 83 to 128 organic results was the real range across six queries.
• "Top 1000" is a marketing frame, not a data source. Deep pools exist mainly on high-volume commercial queries.
• Past position 100, the results page stops being a listicle and becomes video plus repeat domains.
• Search Console is the only free source that covers every query you appear for, at any depth, with no per-check cost.
• Track depth on a shortlist, store the raw pull, and let the rest of your keywords live at page-one depth.

FAQ

Why does a free rank checker stop at 100 if Google has more results? Because requesting deeper costs more to serve and, on most queries, returns nothing useful. WhatsMySerp states its free checker covers the top 100. Others stop at 10 or 20. The cap is a product decision built on the fact that almost nobody needs the rest.

Is checking positions past 100 ever worth it? Yes, for a shortlist: queries with real impressions, commercial intent, and a deep position that is improving. That combination produces an early warning. Outside it, deep positions are trivia.

Does Search Console have a depth limit? Search Console reports the queries you appeared for, including deep ones. Its table is capped at 1,000 rows per view, which is a display limit rather than a depth limit. If you need every row, export or use the API.

Why did one query report 1.4 million results and serve 107? Result counts and served results are different things. Google reports an estimated index size for the query and serves a much smaller set. The count is not a promise of availability.

Should I check mobile and desktop separately? Yes, and that is a bigger effect than most teams expect. We measured up to 11 positions of difference on the same query in our own data. That test is here.

Author: Olivia Stone, SERP Intelligence Researcher Across 25k+ Queries at Auspia. Olivia writes about ranking patterns, result-page composition, and what SERP data can and cannot tell you.