Google Quietly Removes 100 Results Per Page Option, Why?

In a quiet yet impactful change, Google has recently stopped honoring the long-standing URL parameter &num=100, which allowed users and tools to view 100 search results per page. This move has stirred concern within the SEO and digital marketing communities, especially those who rely heavily on scraping, SERP tracking, and comprehensive competitor analysis.

This article dives into what exactly changed, why it matters, how it could affect different SEO workflows, and most importantly, how you can adapt to stay ahead.

What Changed?

Google has effectively deprecated support for the &num=100 parameter in its search URL. This feature traditionally allowed users to modify the default number of results (10 per page) to view up to 100 results in a single query.

• Old behavior: https://www.google.com/search?q=your+query&num=100 would return 100 results.
• New behavior: Google now defaults back to showing just 10 results, even with the &num=100 parameter included.

Google’s stance; The company confirmed that this parameter is not supported and “was never officially documented.”

Why Does This Matter?

At first glance, this may seem like a minor user interface tweak, but for SEOs, developers, and data analysts, the implications are significant.

1. Disruption to Rank Tracking Tools

Many rank tracking platforms and custom SEO scripts relied on the ability to fetch 100 results in a single query. Removing this option means these tools must now make more requests, increasing the risk of rate-limiting and IP blocks.

For instance, tools like Ahrefs’ Rank Tracker allow users to monitor keyword positions across the top 100 results. With Google no longer supporting the &num=100 parameter, platforms like Ahrefs may face challenges in consistently accessing deeper SERP data without relying on alternative scraping infrastructure or paid APIs.

Impact:

• Increased API costs and latency
• Potential rate-limit issues
• Inaccurate rank data if not adapted

2. Reduced Efficiency in SERP Scraping

Scraping tools often use &num=100 to minimize requests and extract complete SERP datasets. The change forces a shift to paginated scraping, more requests, more complexity.

Impact:

• Higher operational load on scraping infrastructure
• Potential data loss or incomplete snapshots

3. Misleading Data in Google Search Console

Some SEOs report seeing noticeable drops in impressions and clicks in GSC. If bots/tools now fetch fewer results, it could artificially deflate these metrics.

Impact:

• Confusion in reporting
• Inaccurate performance attribution

4. Harder Competitor Research and Market Analysis

Finding long-tail competitors or niche SERP placements required deeper result sets. Limiting users to 10 results per page restricts visibility into this long tail.

Impact:

• Missed competitor signals
• Shallow competitive landscape views

How to Adapt to the Change

1. Update Rank Tracking Configuration

To maintain reliable data despite Google’s change, start by adjusting how your tools fetch and process search results.

• Break larger queries into multiple paginated requests (page 1, 2, 3…)
• Ensure your tools handle pagination correctly
• Watch for rate limits and implement rotating proxies or delays

2. Use Google APIs Where Possible

When direct scraping becomes less efficient, alternative data access methods can offer more stability and scale.

Google Custom Search API can still retrieve more results (within limits). For example, a query like:

https://www.googleapis.com/customsearch/v1?key=YOUR_API_KEY&cx=YOUR_SEARCH_ENGINE_ID&q=best+seo+tools

…will return structured JSON results, including titles, URLs, and snippets — perfect for building lightweight rank checkers or search monitors.

For large-scale needs, consider DataForSEO, SERP API, or other commercial SERP data providers that support deep result sets, rich SERP features (like featured snippets, ads, or PAA), and 100-result depths in a single request, ideal for high-volume rank tracking or competitor analysis.

3. Recalibrate Search Console Expectations

With reporting fluctuations now more likely, it’s important to interpret your Search Console data in context.

• Don’t panic if you see sudden drops in impressions
• Correlate with the timing of this change
• Look at alternative indicators like click-through rates and position trends

When Google stopped supporting &num=100, google search console that previously scanned and recorded impressions across the top 100 positions could only access the default 10 results per query, causing a sudden drop in recorded impressions.

It’s important to note:

• Your actual rankings or traffic may not have dropped.
• Instead, what’s dropped is the visibility of those impressions in tools like Google Search Console, especially for pages ranking beyond the top 10.

4. Refocus on Quality Over Quantity

Since deep result sets are no longer easily accessible, a more strategic focus on high-impact positions is essential.

• Instead of pulling all 100 results, zero in on the top 10–20 for meaningful competition
• Use clustering tools to group similar pages and identify SERP intent patterns

5. Monitor Further Google UI & Parameter Changes

Given Google’s evolving approach to SERP delivery, staying informed is your best defense against future disruptions.

• This change may be part of broader efforts to restrict bot activity and simplify UX
• Stay connected with communities like r/SEO, SEO Twitter, and Google Search Central

Conclusion

Google’s removal of the &num=100 parameter is a seemingly small update with wide-reaching implications for SEO workflows. Whether you’re running enterprise rank tracking systems or solo scraping scripts, adapting quickly is critical.

By understanding the impacts and proactively adjusting your strategies and tools, you can stay ahead of the curve, and continue to dominate the SERPs, 10 results at a time.