Google Search's time filters have long been one of the most dependable tools for finding the latest information on any topic. Whether you are looking for breaking news, software updates, or recent discussions, these filters let you narrow results to a specific period, such as the past hour, past 24 hours, past week, past month, past year, or a custom range. For years, they have worked quietly in the background, helping billions of users cut through older content and focus on what is current. That is why it comes as such a shock that these essential tools are now completely broken.

A reader first tipped us off to the issue after noticing that Google Search's time filters, which were working correctly just a couple of days ago, were no longer returning results from the selected time period. We were able to reproduce the problem across multiple Google accounts, multiple devices, and a wide variety of search queries. This suggests that the issue is not tied to a specific user setting, browser, or search term, but is instead a systemic problem affecting Google Search as a whole.

The core problem: random dates ignoring your filter

Instead of limiting results to the selected time period, Google Search is returning a mix of pages from random dates, including both older and newer content that does not match the chosen filter at all. For example, selecting "Past week" might yield articles from three months ago, while choosing "Past year" could return results from yesterday. The inconsistency is jarring and makes the filters effectively useless for anyone who relies on them for timely information.

The issue appears to be global. Reports on Reddit suggest that the problem has persisted for at least a few days, with users from different countries and time zones sharing similar experiences. While Google has not yet acknowledged the problem, the widespread nature of the reports points to a bug on Google's side rather than user error or localised interference. The fact that the problem spans multiple accounts and devices further strengthens the case for a server-side issue.

Why time filters are so important

Time filters are not just a convenience; they are a critical part of how many people use Google Search. Journalists rely on them to find recent developments, researchers use them to track updates on specific topics, and everyday users depend on them to ensure they are not reading outdated information. For example, when searching for a programming error, a developer wants the most recent fixes and discussions, not a decade-old forum thread. Similarly, when looking for a product review, a shopper wants the latest model's feedback, not a page from five years ago.

The feature has been part of Google Search for more than a decade, evolving from simple date tools to more granular options like custom date ranges. Under the hood, these filters use a combination of search operators and JavaScript to refine results. The intention is straightforward: tell Google to focus on pages published within a specific window, and Google will do the rest. When that system breaks, it throws the entire search experience into disarray.

What might be causing the breakage?

According to one Reddit user, the issue may lie with the JavaScript powering Google's time filter dropdown. The dropdown itself still appears and allows you to select a time frame, but the underlying logic that sends the request to Google's servers might be malfunctioning. If the JavaScript is not properly converting the selected time frame into the correct query parameter, Google would receive no date constraint and simply return the default set of results, which would naturally include pages from all dates.

However, the fact that the underlying search operator continues to function correctly is a strong hint. When users manually type something like after:2026-07-01 into the search bar, Google respects that operand and limits results to pages published after July 2026. This suggests that the backend of Google Search is still capable of filtering by date, but the front-end interface is failing to trigger that capability properly. In other words, the machinery is intact, but the control panel is broken.

A workaround: using the after and before operators

Thankfully, there is still a way to get the timed search results you need. Instead of relying on the time filter dropdown, you can add date operators directly to your search query. The two most useful are after: and before:. These operators tell Google to include only pages published after or before a specific date. For instance, searching for after:2026-07-01 will limit results to pages published after July 1, 2026. You can also combine both operators to create a custom range. For example, after:2026-06-01 before:2026-07-01 will return results from June 2026 only.

The operators are not new. They have existed for years as an alternative to the dropdown, and many power users prefer them because they allow for more precise date filtering. The syntax is straightforward: after:YYYY-MM-DD and before:YYYY-MM-DD. You can insert them anywhere in the query, though placing them near the end often works best. You can also use them alongside other search operators, such as site: to restrict results to a specific domain, or intitle: to look for words in the title.

Examples of using date operators effectively

Let's say you want to find recent news about a new smartphone release. A search for smartphone launch after:2026-07-01 should give you pages from the past month, even with the time filter dropdown broken. If you want to narrow it further to a specific week, you could use smartphone launch after:2026-07-25 before:2026-08-01. For researchers tracking a topic over the past year, the operator is equally helpful: climate policy after:2025-08-01 will pull up pages from the last year.

The main downside is that the operators are less intuitive than a dropdown menu. Average users may not know they exist, and they require manual typing. But for anyone who is aware of them, they offer a reliable workaround during this outage. If you are using a search term that repeatedly returns outdated content, simply add after: followed by an appropriate cutoff date. This approach has been verified by users on Reddit and in our own testing, and it works on both desktop and mobile browsers.

How this affects different types of searches

The impact of the broken time filters varies depending on what you are searching for. For news-related queries, the issue is especially problematic because recency is paramount. If you search for a breaking event and select "Past day," you would normally expect the latest articles. Instead, you might get a mix of older analysis and new updates, making it difficult to understand the current state of events. For stock market queries, outdated financial results could mislead investors who are seeking the latest data. For health-related searches, old recommendations could be dangerous if medical guidelines have changed.

Even casual searches, such as looking for a restaurant's opening hours or a movie's release date, can be affected when the filter is ignored. The entire purpose of the filter is to provide signals about freshness, and without it, Google's relevance algorithms may prioritise older, more established pages over newer but smaller sources. This can create a bias toward previously popular content and suppress emerging voices. In a time when misinformation and outdated content are widespread, having a reliable date filter is not just a convenience—it is a safety mechanism.

Google's history of search feature glitches

Google Search is generally reliable, but it is not immune to bugs. Over the years, there have been several instances where core features temporarily stopped working. In 2021, a bug caused Google Search to display blank results for certain queries. In 2022, the featured snippets sometimes displayed incorrect information from low-quality pages. In 2023, some users reported that the "verbatim" mode did not actually match the exact words they typed. Each time, Google eventually identified the issue and rolled out a fix, but the outages highlighted how dependent we are on these tiny functions.

The current time filter bug appears to be more widespread than previous glitches, and it has persisted for several days without an official response. This is concerning because it suggests that the problem may be deeply rooted in how Google handles date information at scale. Alternatively, it could be the result of a recent update that accidentally changed the behaviour of the dropdown menu. Either way, the longer it persists, the more damaging it becomes to user trust and productivity.

What can users do in the meantime?

In the absence of a fix from Google, there are a few strategies you can adopt to mitigate the issue. First, memorise the date operators mentioned above and incorporate them into your daily searches. If you often search for news, setting a habit of adding after:YYYY-MM-DD will ensure you always get fresh results. Second, consider using Google News rather than general search for breaking stories, as News has its own set of date filters that may still work. Third, you can try using third-party search engines that offer date filtering, though they may not have the same index breadth as Google. Finally, you can report the issue to Google using the "Send feedback" link at the bottom of the search results page, which can help raise awareness and pressure the company to act.

It is also worth checking whether the issue affects all your browsers and devices, as we found it does. This confirms that clearing cookies or switching to incognito mode will not solve the problem. The bug is server-side, so no amount of local troubleshooting will restore the functionality. The only effective workaround, for now, is the manual date operator.

The road ahead for Google Search

Google has not yet provided a timeline for a fix, but history suggests that once a bug this visible is confirmed and reported widely, the company typically responds quickly. Search is Google's flagship product, and these sorts of reliability issues undermine confidence in the entire platform. The fact that the underlying date operators still work is a good sign that the fix may be relatively simple—perhaps just a matter of correcting the JavaScript code that sends the date parameter to the backend. Until that happens, users will have to rely on the workaround, and many are likely to become more familiar with the search operators than they ever expected.

While the broken time filter is an inconvenience, it also serves as a reminder of how much we depend on subtle features in search engines. A simple dropdown often goes unnoticed until it fails. When it does fail, it disrupts workflows, spreads outdated information, and forces users to improvise. The current situation is a textbook example of how a seemingly small feature can have outsized importance. For now, the best course of action is to use the after: and before: operators, stay tuned for an official update from Google, and remember that even the most fundamental features can sometimes break.

Source: Android Authority News