When a Search Query Becomes a Standing Instruction

Most of us view search as a transaction. You ask a question, the engine provides an answer, and the session ends. But we are moving toward a model where the request doesn't die when you close the tab. Instead, the query remains active in the background, waiting for the world to change so it can notify you.

I call this a standing instruction. It is the shift from "find this for me now" to "keep looking for this until it happens." For anyone running a website or a local business, this is a fundamental change in how users discover information. Your content is no longer just competing for a click in a moment of active curiosity, but for a spot in a persistent monitoring task.

The Precedent for Persistent Requests

This isn't entirely new territory, though the execution is evolving. Google Alerts has existed for years, essentially turning a specific topic into a recurring search that emails you when new matches appear. You set the frequency, the region, and the language, and Google handles the polling.

OpenAI has followed a similar path with scheduled tasks in ChatGPT, which appeared around January 2025. By July 2026, the introduction of ChatGPT Work expanded this to include tasks that can run once, repeat on a schedule, or specifically monitor for changes. These monitoring tasks are designed to send notifications when a relevant update occurs, often leveraging data from previous runs to determine what constitutes a "change." A useful companion note is AI Is Merging Paid and Organic Visibility, because it looks at a nearby part of the same system. The same pattern also shows up in Follow up Query, where the practical question is how the signal becomes visible.

The critical distinction here is the move from simple keyword alerts to intelligent monitoring. The tradeoff is between precision and noise. While a keyword alert is binary, an AI driven standing instruction attempts to understand the intent of the request, which means the system decides what is "relevant" rather than just what matches a string of text.

How Google Transforms Search Into Monitoring

Google's approach is deeply integrated into the search experience. During Google I/O in May, the company introduced information agents capable of scanning blogs, news sites, social posts, and real time data like sports and finance. The idea is to allow a user to "brain dump" a complex set of requirements, such as specific criteria for an apartment hunt, and have the agent continuously scan the web for a match.

Practically, this is triggered by adding phrases like "keep me updated" to a search. While early documentation mentioned providing helpful links for further exploration, more recent updates from September focus on "info monitoring capabilities." The system continuously checks changing information and suggests tasks during the search process.

From a technical perspective, this means Google is moving toward a "push" model for search. Instead of the user initiating the query, the system pushes the result when the criteria are met. The decision point for a site owner is whether their content is structured to be "discoverable" by an agent that is looking for a specific state of being (e.g., "an apartment with a balcony under $2000") rather than a general topic.

OpenAI and the Concept of Ongoing Work

OpenAI takes a different route with "dots." These are described as always on agents that possess their own cloud computing environment, a browser, and access to connected apps. Unlike a search query, a dot can take on ongoing responsibility and make progress between separate conversations.

This manifests as "assigned work." A dot can decide when to pause and when to wake up to continue a task. Users can specify the timing, the trigger event, and where the results should be delivered. For example, a user might tell a dot to monitor a specific source for a change and then notify them via a connected service like Slack.

The key difference here is agency. While Google's monitoring is an extension of Search, OpenAI's dots are general purpose agents. They manage their own notes and memory. The tradeoff for the user is privacy and permission; for a dot to monitor a private source, the user must grant explicit access to connected accounts.

The Common Thread: Persistent Intent

Despite the different architectures, both systems are built on the foundation of persistent intent. The user defines a goal, and the AI continuously evaluates new information against that goal. It is no longer about matching keywords, but about satisfying a requirement.

In Google's case, you get a notification when a listing meets your specific needs. In OpenAI's case, the user defines which changes are significant enough to warrant a notification. In both scenarios, the system applies a set of criteria to information that arrives after the initial request was made.

This shifts the value of content from "timeliness" to "utility." If a user has a standing instruction for a specific product or service, the first site that publishes a page meeting those exact criteria wins, regardless of when the site was first indexed. The decision for creators is to move away from generic "best of" lists and toward highly specific, attribute rich data that an agent can easily validate against a user's goal.

Distinguishing Search Tools from Agents

It is important to recognize where the comparison between Google and OpenAI ends. Google's monitoring is an embedded feature of Search. It returns updates derived from web content and real time data. It is, essentially, a highly evolved notification system for the web.

Dots, conversely, are agents. They can execute actions, prepare drafts, and manage a browser. They are not just searching for information; they are performing work. While Google provides an update, OpenAI provides a result, which could be an analysis or a suggested action.

The distinction matters because it changes the "conversion" event. For Google, the success metric is likely a click to a source link. For an OpenAI dot, the success metric might be the completion of a task within the agent's own environment, potentially reducing the need for the user to ever visit the source website.

Implications for Website Visibility

The most significant consequence of standing instructions is that they can surface content that did not exist when the user first made the request. If an agent is scanning for news or specific listings, an article published today could trigger a notification for a request made three weeks ago.

For publishers, this creates a new window of visibility. However, the mechanics of how a page is fetched or selected for these updates remain opaque. Google's AI Mode is included in Search Console reporting under the Web search type, but there is currently no way to distinguish a standard search visit from a "monitoring update" visit. This connects with We Earned 1 when the same signal needs a clearer operating decision.

This creates a measurement gap. If you see a spike in traffic, you cannot currently tell if it came from a user actively searching or from an AI agent fulfilling a standing instruction. The risk here is over optimizing for the "active" searcher while ignoring the "passive" agent that is filtering the web for a specific set of criteria.

The Unanswered Questions

There are still several gaps in the public documentation from both companies. Google has not clarified exactly how it selects sources for monitoring updates or whether every update will consistently include outbound links. There is also a lack of detail regarding the user agents involved in these background fetches.

OpenAI is similarly quiet about the specific browser or fetch identity used by dots when they access the public web. Site owners cannot currently distinguish between a standard ChatGPT bot visit and a dot performing proactive research. it is unclear if updates based on public web content will always include citations or if the agent will simply synthesize the answer.

The primary tension here is between transparency and competitive advantage. Both companies are deploying these features rapidly, but the lack of a specific "Agent Bot" identifier makes it difficult for site owners to analyze how their content is being consumed by these persistent tasks.

The Path Forward

As these features roll out more widely, we should expect more clarity in the tooling. For Google, this would mean a dedicated section in Search Console for monitoring updates, allowing us to see which queries are becoming standing instructions for our target audience.

For OpenAI, a dot specific public web identifier would be the first step in allowing site owners to recognize these requests. Citation guidance is also necessary to ensure that the "work" performed by an agent still leads back to the original source of the data.

The shift toward standing instructions means we are moving from a world of "queries" to a world of "goals." The websites that thrive in this environment will be those that provide the most concrete, verifiable data, making it easy for an AI agent to check a box and notify the user that their goal has been met.