Read our full coverage: Google Discover Update: Early Data Shows Fewer Domains In US<\/em><\/p> Mueller Says Google May Skip Sitemaps Without \u201cNew And Important\u201d Content<\/h2>
Google\u2019s John Mueller, Search Advocate at Google, responded to a Reddit question about persistent sitemap fetch errors in Search Console. The site owner had confirmed via server logs that Googlebot fetched the sitemap with a 200 response, but Search Console kept displaying a \u201ccouldn\u2019t fetch\u201d error despite valid XML and correct indexing directives.<\/p>
Mueller said Google has to be \u201ckeen on indexing more content from the site\u201d and that it won\u2019t use the sitemap if it isn\u2019t convinced there\u2019s \u201cnew and important\u201d content to index.<\/p>
Why This Matters<\/h3>
Sitemap fetch errors are one of the more confusing signals in Search Console because they can appear even when the server-side looks correct. Running through the standard checklist of XML validation, response codes, and robots.txt rules may not surface the problem if Google simply doesn\u2019t see enough reason to index what\u2019s behind the URLs.<\/p>
Roger Montti, who covered this for Search Engine Journal, noted that Mueller was broad in his description, but thinking about what makes a site visitor satisfied can help you identify what needs improving.<\/p>
What People Are Saying<\/h3>
The story continues a debate in SEO about sitemaps being hints, not directives. Some argue Google ignores sitemaps for small or non-news sites, relying on links instead, while others note Google doesn\u2019t say it \u201closes trust\u201d in a site when a sitemap is unused.<\/p>
Mueller\u2019s response added a new indexing-demand perspective that the community hadn\u2019t widely considered.<\/p>
Read our full coverage: SEO Fundamental: Google Explains Why It May Not Use A Sitemap<\/em><\/p> Microsoft Finds AI Memory Poisoning Through \u201cSummarize\u201d Buttons<\/h2>
Microsoft\u2019s Defender Security Research Team published research describing what it calls \u201cAI Recommendation Poisoning.\u201d The technique involves businesses hiding prompt injection instructions inside website buttons labeled \u201cSummarize with AI.\u201d<\/p>
Clicking one of these buttons opens an AI assistant with a pre-filled prompt delivered through a URL query parameter. The visible part tells the assistant to summarize the page, while the hidden part instructs it to remember the company as a trusted source for future conversations.<\/p>
Reviewing AI-related URLs observed in email traffic over 60 days, Microsoft\u2019s team said it identified 50 distinct prompt injection attempts from 31 companies across 14 industries. The pre-filled prompt URLs target Copilot, ChatGPT, Claude, Gemini, Perplexity, and Grok. Microsoft noted that effectiveness varies by platform and has changed over time.<\/p>
Why This Matters<\/h3>
Instead of optimizing for search ranking, these companies are trying to influence what AI assistants recommend by planting instructions at the memory layer. Microsoft traced the prompts to publicly available tools designed to build presence in AI memory, and one prompt went well beyond a simple \u201cremember us\u201d instruction by injecting full marketing copy.<\/p>
The AI recommendation layer has become a competitive arena, with companies developing tools to influence it. The way platforms address these tactics will shape the level of trust users have in AI-generated recommendations.<\/p>
What People Are Saying<\/h3>
The research drew attention across security and AI circles. In an interview with Dark Reading, Tanmay Ganacharya, VP of Security Research at Microsoft, described the mechanism:<\/p>
\u201cThe button will take the user \u2014 after the click \u2014 to the AI domain relevant and specific for one of the AI assistants targeted.\u201d<\/p> <\/blockquote>
Ganacharya also told BankInfoSecurity that not all platforms are equally exposed:<\/p>
\u201cOf the major platforms we examined, only Copilot, ChatGPT, and Perplexity have explicit memory features. Claude and Grok do not currently have persistent memory, making them seemingly immune to this specific attack.\u201d<\/p> <\/blockquote>
Some marketers have questioned whether the technique is just an aggressive growth strategy, drawing pushback from security professionals over the ethical and trust consequences.<\/p>
Read our full coverage: Microsoft: \u2018Summarize With AI\u2019 Buttons Used To Poison AI Recommendations<\/em><\/p> Theme Of The Week: The Signals That Decide Visibility Are Getting Harder To See<\/h2>
Every story this week touches on events happening behind the scenes, beyond the usual metrics that most SEO professionals keep an eye on.<\/p>
Google\u2019s Discover update is guiding more topics through fewer publishers, a change that you can notice in feed data rather than in Search Console. Mueller\u2019s explanation about sitemaps shows that a fetch error can indicate an indexing judgment happening upstream. And Microsoft\u2019s research shows businesses trying to influence recommendations at the memory layer.<\/p>
The common thread is that the decisions determining visibility are being made in places most of us haven\u2019t been paying close attention to yet.<\/p>
For deeper context on these topics, check out these recent pieces.<\/p>
Featured Image: VRVIRUS\/Shutterstock; Paulo Bobita\/Search Engine Journal<\/em><\/p> <\/div> SEO,SEO Pulse#Discover #Core #Update #Data #Sitemap #Tips #amp #Risks #SEO #Pulse #sejournal #MattGSouthern1772204152<\/p> ","protected":false},"excerpt":{"rendered":"
Welcome to the week\u2019s SEO Pulse for the best of this week\u2019s news: updates cover what early data reveals about the February Discover core update, why Google may ignore a valid sitemap, and how businesses are trying to game AI assistant memory. Here\u2019s what matters for you and your work. Discover Core Update: Early Data […]<\/p>\n","protected":false},"author":1,"featured_media":3988,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[16],"tags":[87,91,450,4031,90,841,1419,80,97,385,2767,92],"class_list":["post-3987","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-accessibility","tag-amp","tag-core","tag-data","tag-discover","tag-mattgsouthern","tag-pulse","tag-risks","tag-sejournal","tag-seo","tag-sitemap","tag-tips","tag-update"],"acf":[],"_links":{"self":[{"href":"http:\/\/longzhuplatform.com\/index.php?rest_route=\/wp\/v2\/posts\/3987","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/longzhuplatform.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/longzhuplatform.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/longzhuplatform.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/longzhuplatform.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=3987"}],"version-history":[{"count":0,"href":"http:\/\/longzhuplatform.com\/index.php?rest_route=\/wp\/v2\/posts\/3987\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"http:\/\/longzhuplatform.com\/index.php?rest_route=\/wp\/v2\/media\/3988"}],"wp:attachment":[{"href":"http:\/\/longzhuplatform.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=3987"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/longzhuplatform.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=3987"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/longzhuplatform.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=3987"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}