Skip to content

Google's num=100 Removal: What It Means for Rank Trackers and Search Console

Appending &num=100 to a Google search URL no longer yields a hundred organic results. At the time of writing Google had not said whether this was a fault or a deliberate change, but the practical effects are already visible in Search Console dashboards and in rank-tracking tools that reach past the first page. This guide separates a data-collection effect from a genuine shift in position, shows which result bands remain dependable, and gives you a short checklist for reading your own reports.

What actually changed

The num=100 parameter was a shortcut: one request, one hundred organic listings. That shortcut no longer works. A search for 'coffee near me' with the filter applied returns fewer entries than the number requested, which is the clearest public sign of the change.

For a casual searcher the loss is trivial. For measurement systems it is structural. Search Console impressions can fall sharply because impressions were partly built from positions that the result set no longer exposes. Rank trackers that report beyond the first ten positions face the same wall: assembling a hundred results now takes roughly ten separate requests rather than one. Some tools have absorbed that cost; others have cut the depth they report. Either way, the number on the dashboard is describing a smaller slice of the results page than it used to.

Reporting artefact or real ranking change?

The distinction that matters most is between a change in what gets collected and a change in where a page actually sits. The removal of num=100 did not move any page up or down the results. What it altered is how much of the result set a dashboard or tracker can see, and therefore what it can report.

Work through these questions before you react to a sudden shift:

  • Did the movement appear only in Search Console impressions, or also in a tracker's position column?
  • Does the tool report positions beyond the top ten, or only within it?
  • Could average rank have risen because deep positions dropped out of the dataset rather than because the site climbed?
  • Is the Local Pack still showing the same position it showed before?

A fall in impressions alongside steady top-ten positions points to the collection change, not a ranking loss. Likewise, when a tool narrows its reporting depth, average rank can drift upward simply because low-ranked entries are no longer part of the calculation. The metric moved; the ranking did not.

Which result bands still matter

The first ten positions remain the most valuable to report on, and most tools still return them. The top twenty are generally available too, and that band is often where realistic opportunities sit. Below the top twenty, clicks and impressions thin out and positions swing widely, so losing sight of those depths is rarely a serious problem for a local business.

Local Pack tracking sits outside this problem entirely, because it reads a different surface. That makes Local Pack position a useful fixed reference point while organic deep-position data settles into its new shape.

Worked example: the 'coffee near me' query

Take a search for 'coffee near me' with num=100 applied. It no longer returns a hundred results. A tracker that once captured positions one to one hundred in a single request must now chain several requests to reach the same depth, and some tools have chosen to cap their reporting instead of paying that cost.

Imagine a business that previously sat at position 47 for that query. Once deep results stop being collected, the tracker may stop reporting the position altogether. The business has not climbed to 47 from somewhere lower, and it has not lost the ranking; the data point has simply fallen outside the collected set. Because the low position is no longer averaged in, the keyword's average rank can appear to improve. That is a reporting effect, not a gain in visibility.

Checking whether your tracker is affected

Use this field map to interpret what a tool is showing you:

  • Reported depth: does the tool state a maximum position, such as top ten, top twenty or top fifty?
  • Request model: does it fetch deep results in one request or several?
  • Average rank basis: is the average calculated over all collected positions, or only over those the tool can still see?
  • Surface: is the figure for organic results or for the Local Pack?
  • Comparison window: are you comparing against a period before the collection change?

A tool that reports only the top ten or top twenty is not necessarily broken; it may have adjusted its depth deliberately. A tool that still claims deep coverage is worth checking for whether it makes multiple requests to reach that depth.

Reported product statements from the source publisher

The original article was published by a third-party source and described how two of its own tools responded. Those statements are reported here as that publisher's account, not as commitments made by this page.

According to that account, Local Search Grid, a geo-grid rank tracker, was not affected by the change, while Local Rank Tracker, which provided the top fifty results, was affected. To reach fifty results, the publisher said it needed five requests instead of one, and it rolled out a temporary fix to keep supplying the data it had previously offered. In an update dated October 15, 2025, it described moving to a more permanent solution intended to keep providing the top fifty results, said most customers on old and new plans would be unaffected and need take no action, and said a small proportion on old and custom plans might be affected by significant cost increases for fetching data. It said those customers would be contacted individually, that tracking for those accounts would change automatically to the top twenty results, and that the top fifty would remain available on request to discuss pricing. It also said it would monitor the situation and inform customers of any effect on its API and Local Rank Tracker.

Treat these as dated, first-party statements about another company's products. They are not a description of any service offered here, and the product names, plan behaviour and pricing conversations belong to that publisher.

What to do next

Start by treating the change as a data-collection event. Check whether your Search Console impressions and your tracker's positions moved together or separately. If only impressions fell, revisit how your reporting defines a valuable position. If a tracker reduced its depth, ask whether the lost bands were driving meaningful clicks; for most local businesses, positions beyond the top twenty were not.

Keep Local Pack tracking in place as a stable signal. Where a tool now reports a shallower set, note the change in your reporting records so that future comparisons are made on a like-for-like basis rather than against a deeper dataset that no longer exists.

Frequently asked questions

Did my actual Google rankings change because of this?

No. The removal of num=100 did not move any page in the results. What changed is how many results a tool or Search Console can collect and display. A drop in impressions or a jump in average rank can come from the collection change rather than from a real movement in position.

Why did my Search Console impressions drop so sharply?

Impressions can fall because positions that were previously counted are no longer surfaced in the result set. The change affects data collection above the top ten results, so impressions tied to deeper positions may disappear from the dashboard.

Are Local Pack rankings affected?

Local Pack rank tracking has not been affected by the num=100 change. It reads a different surface, so it remains a useful stable reference while organic deep-position data settles.

My tracker now only shows the top 20. Is that a problem?

Not necessarily. The top twenty are generally still available and are where many opportunities sit. Positions beyond the top twenty tend to attract minimal clicks and impressions and fluctuate significantly, so a shallower reporting depth is rarely a serious loss for local reporting.

How can I tell a reporting artefact from a real ranking change?

Compare surfaces. If Search Console impressions fell but tracked top-ten positions held steady, the likely cause is the collection change. If a tool reduced its reporting depth, average rank can rise because low-ranked entries are no longer included. Check whether the Local Pack position also moved; if it did not, the organic change is more likely a data effect.