Google Search Console Last 28 Days vs Last Month for SEO Reporting

For data analysis and trend comparison in Google Search Console, "last 28 days" provides a more consistent and comparable dataset than "last month." Because it always spans exactly four complete weeks, it eliminates the day-of-week imbalance that makes calendar month comparisons unreliable.

Search traffic is not evenly distributed across the week. Most websites see meaningful differences in traffic on certain days, weekdays or weekends. The balance of those days within a given month varies.

February contains 28 days (or 29 in a leap year). March contains 31. Compare those two months side by side and you are not comparing like for like. A reported increase in March clicks over February might simply reflect the fact that March contains three additional days, not any genuine improvement in performance.

This is a well-documented problem in SEO reporting. As one analysis puts it, the error of comparing a 31-day month to a 28-day month and concluding there has been a 10% traffic increase is common. The increase may simply reflect the additional days, not real growth.

Why 'Last 28 Days' is More Accurate

Consistent Weekly Structure

A 28-day window contains exactly four complete weeks, meaning every analysis period includes the same number of Mondays, Tuesdays, Saturdays and so on. This removes the day-of-week skew that distorts calendar month comparisons. Traffic patterns that are tied to weekly behaviour such as B2B spikes on Tuesday or retail peaks at weekends are represented equally in every period.

Fairer Period-over-Period Comparisons

When you compare the last 28 days against the preceding 28 days, you are working with two structurally identical windows. The comparison is clean. When you compare last month against the month before, you may be comparing periods of different lengths, with different weekend distributions and different numbers of working days.

Alignment with Other SEO Reports

Google's own reporting infrastructure reflects the importance of rolling windows. Core Web Vitals data in Search Console uses a rolling 28-day aggregation to smooth out fluctuations in field data collected from real users. This is not coincidental, the consistent rolling window reduces noise and produces more stable trend lines.

Google significantly expanded Search Console's reporting capabilities in December 2025, introducing weekly and monthly aggregation views alongside the existing daily default. This update is worth understanding in the context of the 28-day question.

Previously, the Performance report displayed data on a daily basis only. The December 2025 update introduced a granularity selector directly within the chart interface, allowing users to switch between daily, weekly and monthly views. Google's stated rationale was that daily fluctuations can make it harder to see whether a site is genuinely growing or declining over time.

The new monthly view aggregates data into standard calendar months from the 1st to the last day. Critically, Google confirmed that the system does not normalise monthly data to account for varying month lengths. A monthly view of February and a monthly view of March are aggregating different volumes of days without adjustment.

The weekly view, by contrast, runs from Sunday to Saturday and offers cleaner period-over-period comparisons, precisely because each unit is a consistent seven-day block. For SEO analysis, weekly aggregation in the native interface and 28-day custom ranges for broader comparison are now complementary tools.

AI-Powered Configuration

Also introduced in December 2025, Google added an experimental AI-powered configuration feature to the Performance report. Users can describe the analysis they want in plain language and Search Console assembles the relevant filters and settings automatically. Example prompts include requests such as "show average CTR and average position for queries in the last 28 days" or "find pages that dropped in clicks last 28 days compared to the previous 28." The 28-day window is baked into Google's own example use cases for this feature, further reflecting its status as the default unit for meaningful comparison.

There are legitimate situations where calendar month reporting is the correct approach. Understanding the distinction helps you choose the right tool for the right purpose.

If your business operates on strict calendar-month reporting cycles, whether for finance, client contracts or internal dashboards, then calendar month data is necessary for consistency with those other systems. A January report that does not align with January financial data creates more confusion than it solves.

In these cases, the more robust approach is to export your Search Console data and process it in a separate tool such as Google Sheets or Looker Studio, where you can apply normalisation, annotate anomalies and align search data with other channel data on your own terms. This gives you the accuracy of the 28-day methodology alongside the calendar-month framing that stakeholders expect.

Year-over-year comparisons using the new monthly view can also be valuable for seasonal businesses, where comparing December 2024 to December 2025 in a consistent calendar format helps strip out within-year variation. The key is to use the same month length in both periods, which the calendar month view naturally provides when comparing the same month across years.

Whichever date range you use, it is important to understand that Search Console data is not real-time. There is always a processing delay between when a user performs a search and when that data appears in your reports.

Under normal conditions, the Performance report has a lag of around two to six hours for the most recent data, with a typical practical delay of two to four days before data is considered stable. The most recent days in any report, whether using "last month" or "last 28 days," may still contain preliminary figures that can shift slightly as processing completes.

This lag is worth bearing in mind when drawing conclusions from very recent data. A dip in the last two or three days of your reporting window is not necessarily meaningful until those data points have fully settled.

When Delays Become Outages

Google's Search Console reporting infrastructure has experienced several notable disruptions. In late 2025, the platform suffered two significant incidents in close succession: a Performance report lag that stretched to over 70 hours before being resolved in December 2025, and a Page Indexing report delay that left data frozen for nearly a month from mid-November to 18th December 2025. Google confirmed throughout both incidents that the issues were reporting-only and had no effect on actual crawling, indexing or rankings.

These events are a useful reminder that Search Console should not be your sole source of performance data. Cross-referencing with Google Analytics, server logs or third-party rank tracking tools provides a more resilient view of organic performance, particularly during periods of reporting instability.

The choice between date ranges is not simply a technical preference. It affects the quality of conclusions you draw and the decisions you make based on them.

Recommended Approach by Use Case:

• Trend analysis and SEO performance monitoring: Use "last 28 days" as your default. It provides a structurally consistent window with four complete weeks.
• Period-over-period comparison: Compare last 28 days against the preceding 28 days for clean, like-for-like analysis. Avoid comparing calendar months of different lengths without normalisation.
• Client and stakeholder reporting on a calendar cycle: Export data and process in Looker Studio or Google Sheets, where you can align with calendar months while applying your own normalisation or annotations.
• Year-over-year seasonal analysis: The new monthly aggregation view is useful here. Comparing the same calendar month across two years controls for seasonal patterns while keeping the time unit consistent.
• Diagnosing sudden drops or spikes: Switch to daily view. Rolling windows and aggregated views smooth out the anomalies you need to identify when investigating a specific incident.
• Core Web Vitals monitoring: This report already uses a 28-day rolling window natively. No adjustment is needed, and the methodology is consistent with best practice.

Key Takeaways

• 28 days equals four full weeks: This makes it a structurally consistent unit for analysis, free from the day-of-week imbalance that affects calendar months.
• Calendar months vary in length: Comparing a 31-day month against a 28-day month without normalisation introduces error into your reporting.
• Google uses 28 day windows natively: Core Web Vitals and several AI-powered reporting examples reflect this as the preferred unit for stable performance data.
• New weekly and monthly views are useful but not equivalent: The December 2025 weekly view offers clean period comparison; the monthly view does not normalise for varying month lengths.
• Data lag is normal: Expect two to four days of delay under normal conditions. Do not over-interpret the most recent two or three data points in any window.
• Diversify your data sources: Search Console alone is not sufficient. Cross-reference with Analytics and other tools, particularly during periods of reporting instability.
• Match the tool to the task: Use 28-day windows for analysis, export to Sheets or Looker Studio for calendar-aligned client reporting.

The 28-day window is not a workaround. It is simply a more statistically sound unit for the kind of rolling performance analysis that SEO requires. Used consistently, it produces cleaner comparisons, more reliable trend data and fewer false conclusions driven by calendar arithmetic.

Helpful Resources

• Google: Search Console Performance Report documentation
• Google Search Central: Introducing weekly and monthly views in Search Console (December 2025)
• Google Search Central: AI-powered configuration in Search Console (December 2025)
• Google: Core Web Vitals and the 28-day field data window

If you need help structuring your Search Console reporting or interpreting performance trends across channels, we can help. Get in touch to discuss how to build a reporting framework that gives you clean, reliable data to work from.