After num=100 Changes: Verify SEO Tool Data Against Search Console

If a rank-tracking or scraping-based SEO tool reports a sudden impression collapse after changes around the num=100 search parameter, do not read that number as a direct loss of Google Search demand. The first job is to separate three things: Google Search Console first-party metrics, third-party SERP collection methods, and the real traffic users send to your site.

What the old num=100 habit could and could not prove

The num=100 parameter was commonly used by third-party workflows to request a larger set of visible search results in one browser-like request. That habit made it convenient for rank collection beyond the first page, but convenience is not the same as an official performance reporting interface.

Google’s Custom Search JSON API documentation is a useful contrast: its num parameter is limited to values from 1 to 10, and the API will not return more than 100 results in total for a query. That product is not the same as ordinary Google web search, but it shows why unsupported browser parameters should not be treated as stable reporting contracts.

So the right conclusion is not “Google rankings improved because impressions dropped.” It is more cautious: if a tool depended on collecting many results at once, a change in collection behavior can make the tool’s visibility database smaller or noisier without proving that real users stopped searching.

Use Search Console definitions before interpreting a drop

Google Search Console defines impressions, clicks, click-through rate, and average position in a specific way. An impression generally means a user saw or potentially saw a link to your site in the current result set, with special rules for carousels, expanding elements, image results, Discover, AI Overviews, and AI Mode. Average position is also not a simple manual rank number; it is averaged across queries and uses the topmost position of your property or page when it receives impressions.

This matters because third-party tools usually do not measure the same thing. A rank tracker may collect a fixed number of results for a keyword from a location and device profile. Search Console records actual Google Search performance for your verified property under Google’s metric rules. When the two disagree, Search Console should be the baseline for Google Search performance, while third-party data can remain a directional research aid.

Before reacting to a dashboard collapse, check:

• Did Search Console clicks from Google Search fall, or only the third-party tool’s “visibility” or “impressions” estimate?
• Did Search Console impressions fall across real pages and queries, or did average position change because low-ranking impressions are no longer being sampled by a tool?
• Are changes limited to keywords where the site usually ranked outside the first page?
• Did branded traffic, conversions, or analytics sessions from Google organic search change at the same time?

Why “average ranking improvement” can be a math artifact

If a tool stops collecting deep results, the remaining dataset is biased toward pages that still appear in the collected range. That can make the average position look better even while the tool reports fewer impressions or fewer ranked keywords. This is not necessarily SEO progress; it may simply mean the tail of low positions disappeared from the sample.

Google’s own Search Console help warns that position is complex and can be misleading without context. The same position number can mean different things across desktop, mobile, image results, knowledge panels, and other search features. A third-party dashboard adds another layer of uncertainty because it may have its own collection limits, location settings, personalization controls, and result-type handling.

For reporting, replace absolute claims with a cleaner statement:

“The tool’s collected SERP sample changed. We will validate real impact with Search Console clicks, impressions, query/page breakdowns, and analytics sessions before changing strategy.”

How to audit the impact without overreacting

Use a short diagnostic workflow:

1. Check Search Console data anomalies. Google maintains a page for known reporting issues. If a known logging or aggregation issue overlaps with your date range, label it before drawing conclusions.
2. Compare equivalent periods. Use Search Console’s performance report to compare the affected period with the previous period and year-over-year where possible.
3. Segment by page and query. Identify whether the change is sitewide, template-specific, language-specific, country-specific, or limited to a keyword group.
4. Separate rankings from clicks. A position change without a click or conversion change may not justify emergency rewrites.
5. Review third-party tool notes. Check whether your tool vendor documented changes to collection depth, update frequency, or historical recalculation. Do not assume old update schedules still apply.

If only the third-party rank tracker changed, your response should be reporting hygiene: annotate dashboards, explain the methodology break, and avoid comparing pre-change and post-change visibility as if they were the same metric.

What to do with SEO operations after the change

The best operational response is not to chase a replacement parameter. It is to reduce dependency on fragile SERP scraping and improve the mix of evidence:

• Use Search Console for first-party Google Search performance.
• Use analytics data to confirm whether organic sessions and conversions changed.
• Use rank tools for directional monitoring, competitor observation, and keyword discovery, not as a substitute for verified performance.
• Keep dashboard annotations whenever a vendor changes data collection, location settings, device assumptions, or update cadence.
• Do not report unsupported percentages such as “87.7% of sites lost impressions” unless the sample, method, source, and definition are visible and trustworthy.

For most websites, the strategic checklist remains unchanged: keep pages crawlable, publish useful content that satisfies the query, improve titles and snippets where clicks are weak, and diagnose real traffic drops with Search Console rather than with a single rank-tracker metric.

For other discrepancies unrelated to num=100, compare collection settings using the rank-tracker versus real results checklist.

Primary references: Search Console: impressions, position, and clicks, Search Console data anomalies, Custom Search JSON API: cse.list, and Google guidance on third-party SEO tools.