Too many people think the job to be done of using AI to write content is a better prompt, that sounds like me, gets rid of em dashes, etc. No matter how well you prompt, often times you'll leave a pattern at some point, that pattern can damage your relationship capital. Just voice transcribe the darn thing.
Since everyone is talking Schema and AI citations, @tompeham, CEO of Otterly, shared data from adding markup on 2000+ URLs
• Google AI Overviews citations increased 1500% 📈
• ChatGPT citations dropped 📉
Honestly this whole deck presented at @brightonseo is filled with useful data from AI SEO experiments
GEO Experiments 2026: What We Tested, What Failed, and What Actually Worked
Thanks for sharing🙏
https://t.co/nC4tW0HJ1F
What a time to be alive.
I now have an agent that will review my social traffic (big query) if it is lower than I like, it goes and finds older blog posts (greater than 12 months) that drove value, then it reviews all my recent highlights on the topic and generates questions for me, then it kicks off an AI interviewer to call me and interview me to get my perspective on what's changed since that post was published.
Then it mashes it up into a set of ideas and snippets for me to write a longer fresher post and try to get my social traffic (winning with humans) back where I want it to be.
This is how I want to push my team to use AI to scale content from subject matter experts with lived experience instead of low quality scaled content with Claude's "lived experience" + some brand guidelines.
Interesting timing: Google is dropping rich results support for *all* FAQ Schema as of yesterday, and is removing FAQ structured data reporting from GSC. (Link in comments)
I wonder why they decided to do this *right now* in May 2026? Google had already deprecated FAQ rich results for most sites several years back, but had kept eligibility available for various high-authority sites, like .gov and health sites (they made this change during the pandemic).
So, why deprecate FAQ rich results now?
Putting on my tin foil hat - my theories on this:
I wonder if this has anything to do with the influx of new articles (168k in the below screenshot) claiming that "FAQ schema is critical for GEO?" This guidance is spreading like rapid fire.
Why does my mind immediately go here? Because we have already lived through this before.
When FAQ Schema was first launched in 2019, it was an *incredible* SEO opportunity. Site owners were even able to add internal links to other pages on their site within FAQ answers, which showed up directly in the SERP. One of those rare "too good to be true" opportunities in SEO.
I wrote about this on Moz in 2019 (link in comments), because our SEO team at Amsive was seeing great results using for this with our clients - especially in the form of lots of new impressions & clicks to the different links included in FAQ answers.
In this Moz article, I also included a section called "Risks involved with implementing Schema," (also linked in comments) and described some potential misuses of FAQ schema for SEO purposes. I stated: "Avoid misusing Schema, or it’s possible Google might take away these fantastic opportunities to enhance our organic listings in the future."
Unfortunately, that's exactly what Google ended up doing. (As I often say: anything that can be spammed in SEO, will be spammed.) There was so much FAQ Schema SEO spam in the search results, that we *all* lost the opportunity to continue earning rich results through FAQ Schema. I also eventually noticed that aggressively scaling FAQ questions/Schema was a common pattern among sites impacted by the Helpful Content Update.
So, this wouldn't be the first time that Google is playing the cat and mouse game when they see too many sites using the same exact techniques "for SEO/GEO."
Just an idea.
(Sidenote: I am NOT saying not to use FAQs where it makes sense to, and the associated Schema can be helpful for reasons other than rich results on Google. I'm just commenting on why they might have made this change at this time)
h/t @glenngabe@rustybrick
Had a 2 hour rant about GEO myths, schema, prompt tracking, listicles, markdown, Reddit spam and more with @edwardeachday over the weekend. Have a watch!
https://t.co/xsi5DP2Dcf
(apologies for the audio on my end, USB hub dying meant I had to use a potato mic...)
"Ensures AI engines can parse and connect your content."
That's the SaaS pitch for 'Technical GEO.' Schema. Structured data. Clean architecture.
Ensures.
LLMs were built to read unstructured language. There's nothing to ensure.
Read on The Inference: https://t.co/1SoLxa1hn0
Better late than never - I was finally able to publish the “winners and losers” list for the March 2026 Google Core Update, plus some analysis about what changed.
In some cases, reversals happened after the update, so I made a note of those too:
https://t.co/5ksX6xXqmP
Yep… takes LLMs forever to update titles, new company names after rebrands, etc.
This is where SEO/AEO gets fun though. It’s like online reputation management 2.0.
The Jan 20 Google update was the most interesting update of the year for me so far (I’m still working on March Core analysis btw 🥵)
Still finding new examples that all match the same patterns. A few things seemed to happen:
- the impact was mostly isolated to a specific subfolder, usually the blog
- the affected sites were all playing SEO/GEO games (scaled AI content, self promoting listicles, artificial updates, misusing AggregateRating schema across pages, scaled comparison/alternative pages)
- lots of SEO growth before the crash
- seems to have disproportionately hit SaaS companies
By *no* means did Google hit all the sites doing these things, but I wonder if they were testing an algorithmic change across the most obvious examples.
FWIW - I would NOT consider a site “safe” if it’s doing all the above things and hasn’t been hit yet.
(Orange chart = projected organic traffic. Blue chart = ChatGPT citations. Both from @ahrefs)
My SEO setup
- Sitemap submitted
- IndexNow configured
- Robots.txt file in place
- Meta title and description set
- Bing webmaster Tools connected
- Google search console connected
Anything I’m missing here?
Publishers have real questions about AI, but let’s be clear: @waybackmachine isn’t a backdoor for AI scraping.
For 30 years, it’s been built for people, not bulk harvesting. We actively monitor to prevent abuse. Learn more ⤵️
https://t.co/YKDkawYd5G