Brandon Lazovic

Pulse · July 27, 2026

Confirmed

OpenAI moves every ChatGPT Ads campaign to a seven-day average daily budget starting today

OpenAI's Ads Manager help center confirms that starting July 27, 2026, daily budgets become a seven-day rolling average rather than a fixed daily cap: spend can run up to double the budget on a given day, capped at seven times it per week, with no advertiser action required. OpenAI's advertiser email, quoted independently by Search Engine Roundtable and Search Engine Land, also details conversion-optimized (oCPC) bidding, geo-exclusion targeting, a Bulk API, and refreshed product-feed ads showing price and star ratings.

In plain termsYour daily ad-spend limit on ChatGPT is no longer a hard per-day ceiling; OpenAI now averages it out over a week, so some days can cost twice your set budget as long as the week nets out even.

Why it mattersAdvertisers who read a daily budget as a hard per-day ceiling will see individual days run up to double that amount, and the new product-feed ad format puts feed data quality on display inside the ad unit itself.

Our takeI argued in 'Conversational ads converge' that Amazon, Google, and OpenAI had all converged on one mechanic: the model writes ad copy from the merchant's feed instead of advertiser-authored creative. The refreshed product ad format here, showing price and star ratings pulled straight from the feed, is that same mechanic landing as a literal ad unit, so a thin or stale feed now caps what the ad itself can show, not just what a shopping listing says.

Observed

Google's John Mueller confirms a Search Console bug throwing errors on robots.txt recrawl requests

A practitioner reported on Bluesky that Search Console's request-a-recrawl action inside the robots.txt report was throwing an unknown error on repeated attempts across several properties. Google's John Mueller replied that the feature worked on his own site at first, then posted directly on Bluesky that he could reproduce the same error on some of his other sites and would look into it. No official incident notice or fix has been published as of this writing.

In plain termsThe button in Search Console that asks Google to immediately recheck your robots.txt file is throwing an error for some people right now, and a Google employee is seeing the same error on some of his own sites.

Why it mattersAnyone hitting this error on a robots.txt report shouldn't assume it's specific to their account or permissions, since a Google engineer has independently reproduced the same failure.

Our takeA single practitioner report is thin evidence on its own, but a Google engineer independently reproducing the same failure raises this from anecdote to a real, if unscoped, tooling bug. Until Google confirms a fix, treat a failed recrawl request as inconclusive rather than as proof a robots.txt change hasn't been picked up, and check the live file or the report's last-crawled timestamp instead.