A complete guide to Google Search Console hourly reporting — how the Search Analytics API delivers hourly GSC data, how to set it up without code, and how to automate hourly exports beyond the 10-day window.
Google Search Console is the definitive source of truth for organic search performance — but for years, it had a major blind spot: no hourly data. If a Google algorithm update rolled out on a Tuesday afternoon, you'd have to wait until the next day (at minimum) to see the impact in your performance report.
That changed in April 2025, when Google officially announced that the Search Analytics API now supports hourly data. This guide explains exactly what GSC hourly reporting is, how to set it up via the Search Analytics API, and how to use hourly GSC data to make faster, smarter SEO decisions.
GSC hourly reporting refers to the ability to retrieve Google Search Console performance data (clicks, impressions, CTR, position) broken down by hour rather than by day.
Before April 2025, the finest granularity available in GSC was daily data. Now, via the Search Analytics API, you can pull data at an hourly level — giving you a near-real-time view of how your site is performing in Google Search.
Key facts about GSC hourly data:
"The API will return data for up to 10 days with an hourly breakdown. This will allow developers to create solutions to show not only hourly data for the latest period but also to compare hourly data across different days." — Google Search Central Blog, April 2025
When Google rolls out a core update, the impact often hits within hours — not days. With daily data, you might not notice a significant traffic drop until 24–48 hours after it starts. With hourly data, you can see exactly when the update landed and how your site responded hour by hour.
SEO consultant Glenn Gabe, who was among the first to document hourly GSC data workflows, noted that hourly data lets you "see when the update actually lands and the stark difference in traffic when that happens" — a capability previously only available through Google Analytics, not GSC itself.
Pushed a major site update? Launched a new content section? Hourly data lets you watch the impact unfold in near real time, rather than waiting a full day to see if something went wrong.
Some sites have strong intraday patterns — news sites, e-commerce sites, or anything with time-sensitive content. Hourly GSC data lets you understand when your audience is searching and clicking, which can inform publishing schedules and content strategy.
If your clicks suddenly drop at 2pm on a Wednesday, hourly data lets you catch it immediately. With daily data, that anomaly gets averaged out and might not be obvious until you're doing a weekly review.
The hourly data is available through the standard Search Analytics API endpoint. You simply add "dataState": "hourly" (or use the hourly dimension type) to your API request.
Example API request (Python):
request = {
'startDate': '2026-05-18',
'endDate': '2026-05-28',
'dimensions': ['date', 'page'],
'dataState': 'hourly',
'rowLimit': 25000
}
response = service.searchanalytics().query(
siteUrl='https://yoursite.com/',
body=request
).execute()
This returns rows with timestamps at the hour level (e.g., 2026-05-28T14:00:00Z), giving you a full 10-day hourly dataset.
For SEOs who prefer working in spreadsheets rather than writing code, Analytics Edge is a popular add-in for Excel and Google Sheets that connects to the GSC API. It added support for hourly data within 24 hours of Google's announcement in April 2025.
Basic workflow:
The Analytics Edge core add-in costs $99/year and the GSC connector is $50/year — a cost-effective option for professionals who run regular GSC exports.
If you want hourly GSC data without writing code or managing spreadsheet macros, dedicated tools like GSC Saver handle the API connection for you. You connect your GSC property once, and the tool automatically collects and stores your hourly data — so you always have a clean, queryable history available, even beyond the 10-day API window.
This is the most practical option for site owners and SEO teams who want the insights without the infrastructure overhead. You can install GSC Saver from the Chrome Web Store and be up and running in minutes.
One important nuance: even with hourly reporting, GSC data is not truly "live." There is always some delay between when a user performs a search and when that data appears in GSC.
On a normal day, the delay is typically 1–5 hours. However, GSC has historically experienced extended delays during periods of high load or internal issues. In late 2025, for example, the GSC performance report experienced delays of 50+ hours for several weeks — a prolonged outage that frustrated SEOs who rely on fresh data for monitoring.
This is one reason why saving your own copy of GSC data is so valuable. If GSC's own reporting is delayed or disrupted, having an independent export means you're not flying blind.
1. Set up automated hourly exports for your key properties
2. When Google announces (or you suspect) an update:
→ Pull hourly clicks + impressions for the past 5 days
→ Chart by hour
→ Look for sharp inflection points
3. Cross-reference with your GA4 hourly data for confirmation
4. Drill down by page or query to identify what's affected
1. Note the exact time of your site deployment
2. Pull hourly GSC data for 24 hours before and after
3. Check for any drop in clicks or impressions
4. If a drop is detected: compare affected pages to pre-deploy versions
1. Export hourly data for your top content pages over 10 days
2. Identify peak traffic hours (e.g., 8–10am, 12–1pm)
3. Schedule new content publishing to align with peak discovery windows
4. Monitor hourly performance of new content in the first 24 hours post-publish
| Limitation | Detail | |------------|--------| | 10-day window only | Hourly data is only available for the past 10 days via the API | | API access required | Not available in the GSC web UI — you must use the API or a tool | | Data delay | Even hourly data has a 1–5 hour lag under normal conditions | | No historical hourly data | You can't retroactively get hourly data from before the feature launched | | Row limits apply | Standard API row limits (25,000 per request) still apply |
The 10-day window is the most significant limitation. If you want to compare "this Monday at 9am" to "last Monday at 9am," you need to have already saved last Monday's hourly data before it aged out of the window. This makes automated daily exports essential for anyone who wants to use hourly data for longitudinal analysis.
Is hourly GSC data available in the Search Console UI?
No. As of 2026, hourly data is only accessible via the Search Analytics API. The GSC web interface still shows daily granularity at its finest.
How far back does hourly GSC data go?
Only 10 days. After 10 days, hourly data is no longer available via the API. To retain it longer, you must export and store it yourself.
Is hourly GSC data accurate?
It's as accurate as daily GSC data — the same sampling and aggregation rules apply. For high-traffic sites, hourly data is highly reliable. For very low-traffic pages, small numbers can create noisy-looking charts.
Can I get hourly data for Google Discover or Google News?
Yes. The hourly data endpoint supports all search types available in the standard API, including Web, Image, Video, News, and Discover.
Why does my hourly data sometimes show gaps?
Gaps in hourly data are usually caused by GSC's normal data processing delays. Hours with very low traffic may also appear as zero due to sampling thresholds.
GSC hourly reporting is one of the most significant additions to Google Search Console's data capabilities in recent years. The ability to see clicks and impressions at an hourly granularity — especially during algorithm updates or major site changes — gives SEOs a level of situational awareness that simply wasn't possible before April 2025.
The catch is that hourly data only covers a 10-day window, and it requires API access. If you want to make hourly reporting a sustainable part of your SEO workflow, the key is automating your exports so you're always capturing data before it ages out.
Tools like GSC Saver make this straightforward — connecting to the GSC API, collecting your hourly data automatically, and storing it so you can analyze trends over weeks and months, not just 10 days.
Start monitoring your site at the hour level. When the next algorithm update rolls out, you'll be glad you did.
→ Visit gscsaver.com · Install on Chrome
Sources: