Forum Moderators: mack

Bing's AI generated snippets contain errors

Just annoying or defamation?

         

RonPK

2:57 pm on Oct 17, 2025 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Lately I've seen several examples of AI generated snippets with errors on Bing's result pages. Example: a web page about a dancer who is still very much alive starts with "[name here] was born in Paris in 1932". The Bing snippet starts with "[name here] was a French dancer", even though nowhere on the page does it say the dancer is dead. Not in the text, not in the meta description, not in the <title>.

To the user there is no indication that the snippet is AI generated and therefore unreliable. They see a silly snippet and move on to the next item. From a webmaster perspective it's quite annoying to see Bing making invalid summaries and pretending the site made the error. Any thoughts?

(With a slightly different query Bing falls back to using actual snippets from the page. So the erroneous snippet really is AI generated.)

Microsoft says we can add <meta name="robots" content="nocache"> to prevent the generated snippets: Announcing Generative AI Captions, [blogs.bing.com ]. Seems like an ugly hack to use a more or less deprecated tag for a different purpose.

tangor

10:48 pm on Oct 18, 2025 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



? I was born in 19--. I'm not a dancer, but I also am not dead. Not sure what the AI got wrong, but perhaps there's more than stated in OP. As described, this appears an acceptable use of TENSE and description of OCCUPATION. Is a declaration of lack of life changing any of the facts as presented?

I've used content="nocache" on every page since either Tedster or IncrediBill (been so long I've forgotten which!) back in 2006 suggested it as a way to FORCE search engines to DO THEIR JOB and FIND any changes made and keep things fresh. Appears to have had no ill-effects these many years later. HOWEVER, it is interesting to know M$ indicates they will use content="nocache" as a signal to prevent AI Captions!

That means I don't have to change ANYTHING! :)