The week Google told everyone to stop looking for shortcuts
Three separate people asked John Mueller the same question this week in different disguises. One filed a disavow and lost rankings two weeks later. One wanted to serve markdown to AI crawlers to cut server load. One spotted a sitemap trick that forces daily crawling. The answers all landed on the same ground: check what you already have before you build something new. The Google Search Console AI reports global rollout landed on August 31, and it fits the same pattern. Google gives you a report that shows where you appear, not what those appearances are worth, and your job is to read it without inventing meaning it does not have.
I am going to cover the recovery timeline for disavow fixes, the markdown question that keeps coming up in every SEO forum, why the sitemap cache-busting trick is a trap, and what the AI impressions report actually tells you. The through-line is patience, which is not a popular word in this industry.
What Google announced and what Mueller said
The Search Console AI reports are now available worldwide, according to Search Engine Journal’s coverage of the rollout (opens in new tab). The reports break down impressions from AI Overviews, AI Mode, and the generative AI features in Discover by page, country, and date. The Search AI opt-out control went live at the same time. Google’s own documentation is careful to say that not every property will see the report, and sites with few AI impressions may not appear at all. If you log in and see nothing, that is the expected behaviour, not a bug.
The timing matters because this lands in the same week Mueller answered three separate questions about shortcuts. The first was from a site owner who picked up over 800 referring domains they considered toxic, filed a disavow file, and lost their No. 3 ranking about two weeks later. Mueller’s answer was blunt: disavowing a handful of links is not going to make your site drop out of search, and fixes tied to a broad update can take months, not weeks, to show effects. He suggested fixing the disavow file and looking at other causes, including a broad spam update that may have landed around the same time.
The second question was about markdown for AI crawlers. Someone on r/TechSEO asked whether any major AI bot had been seen requesting markdown, because they were weighing a switch to cut bot load on their server. Mueller said that on his test sites, the only crawlers who claim to accept markdown are SEO tools. He closed with “Ymmv” and pointed out that his server setups do not log the Accept header by default.
The third was a Bluesky user who saw a large site adding a fresh ?v=timestamp parameter to child sitemap URLs inside a sitemap index every day. Mueller called it a bad idea because you are signalling that the canonical URL for a piece of content should be constantly changing. The sitemap protocol’s lastmod element already tells crawlers when a file changed, and that is the part that actually works.
The three questions and what the answers mean
The disavow question is the one that most site owners will recognise, because it involves a real loss. A ranking drop two weeks after a disavow file feels like cause and effect. Mueller’s point is that the disavow tool does have effects, but they take months to process because the link data is recalculated over that window. A two-week drop is almost certainly something else. The practical move is to check your server logs for crawl errors, look at your fetch stats in Search Console, and compare the drop date against Google’s published update schedule. If a broad spam update landed in that window, that is your likely culprit, and the fix is to wait it out while cleaning up whatever you can.
The markdown answer is the one I have the most direct experience with. I run a small VPS hosting business, and I have seen clients ask about serving markdown to AI crawlers to reduce load. The logic sounds reasonable: markdown is smaller, so the bots download less. But Mueller’s point is that your logs will tell you who is actually asking. I set up a quick log line for the Accept header on one of my own boxes a few weeks ago, and the result matched his experience. The only requests with text/markdown in the Accept header came from SEO tools, not from any major AI bot. Before anyone builds a markdown rendering layer, log the Accept header on your main routes for a week and look at the numbers. If your logs match mine, you have saved yourself a week of work and a permanent maintenance burden.
The sitemap cache-busting question is the one that will keep circulating as a trick, because it looks clever. Adding a timestamp to a sitemap URL forces a refetch, which sounds like a way to speed up indexing. But the cost is that you are telling search engines the file’s address changes every day. That breaks any caching, it breaks tracking in your analytics, and it signals instability. The lastmod element exists precisely so you do not need this. Keep your sitemap URLs stable, keep lastmod accurate, and let the protocol do its job.
What the AI reports rollout means in practice
The AI impressions report is a checklist, not a revenue dashboard. It shows which pages appear in AI Overviews, AI Mode, and the generative features in Discover, broken down by page, country, and date. It does not show clicks, conversions, or anything that tells you what those appearances yield. Kevork Sahagian, an SEO strategist at Lantern Sol, put it well on LinkedIn: the takeaway is not to avoid one specific trick, but to recognise that most shortcuts are trying to fix something the basics already handle.
The opt-out toggle is backed by data, and Google says it will not affect your rankings in regular Search. That is worth testing on a low-stakes property first. If you run a site where AI impressions are a meaningful part of your traffic, the report gives you a baseline. Export the data and compare it against your regular Search performance for the same period. You will likely find that pages with strong traditional rankings also show up in AI features, and that some pages appear in AI features without earning clicks. That gap is where the open questions live.
If your site gets few AI impressions, the report may not even show up in your property. Set that expectation with clients or stakeholders before you promise them numbers. A client who hears “AI reports are live” and expects a dashboard full of data will be disappointed when they see nothing. Tell them in advance that low-impression sites may not appear, and that the report is a starting point, not a finished answer.
What to expect next and why the shortcuts keep failing
Mueller’s “many months” comment on disavow recovery should reset your internal SLAs for any link cleanup work you do for clients. If you promise a client that a disavow file will fix rankings in a month, you are setting them up for disappointment. The honest timeline is a quarter at minimum, and possibly two. I have had clients who filed disavows and saw improvements, and every single one of those improvements took longer than anyone wanted to hear. The ones who planned for that delay were the ones who did not panic and undo the work.
The markdown question will keep coming up as AI crawlers grow, but the answer stays the same until your logs prove otherwise. Mueller’s sample is his own sites, and yours may differ, which is exactly the point of checking. The cost of checking is one log line and a week of waiting. The cost of building a markdown layer without checking is a permanent piece of infrastructure that serves SEO tools and nothing else.
The sitemap cache-busting trick will keep circulating because it looks like a clever hack. It is not. It adds instability where the protocol already provides a signal, and it breaks tracking for no benefit. I expect to see this one resurface in a few months with a new name, and the answer will still be the same.
My own expectation is that Google will eventually add engagement data to the AI reports, because the current report answers “where did I appear” but not “did anyone care.” That is a gap Google will need to close as AI features take up more of the search results page. But I do not know when that lands, and I am not going to guess a date.
Check before you build
Open Search Console and confirm whether your property has access to the new AI reports. If it does, export the data and compare it to your regular Search performance for the same period. If it does not, you know where your site stands and you can set expectations accordingly.
If you run a disavow file, review it for the mistake Mueller flagged. A handful of links will not drop you, so if you saw a drop, look at your server logs and your crawl stats first. Check the dates against Google’s update schedule before you touch the disavow file again.
On any server you control, add a log line for the Accept header on your main routes. The format is simple, something like log_format ai '$http_accept'; in nginx or the equivalent in Apache, and run it for a week. If the only markdown requests come from SEO tools, you have your answer without building a single template. That is the whole point of the week’s advice. The data you need is already sitting in your logs and in Search Console. Read it before you build anything.