Skip to content

Features
Pricing
Changelog
Status

Category: Google SEO

Google Search Console Glitch: Why Your Link Data Is Outdated

On a recent Thursday, I logged into Google Search Console expecting the usual link report, only to discover a significant issue—it had broken. For some, it displayed zero links, while others saw their reported links drop by nearly 90% from the previous week.

Google acknowledged the problem and decided to revert to older data temporarily as they worked on a fix. This means the link data you’re seeing might be weeks old.

Google’s Response: John Mueller of Google mentioned, “Thanks for the heads-up, Barry. We’ll take a look to see if there’s anything unexpected happening (given the long weekends, it might take a bit of time).”

By Saturday, the links seemed to reappear, but as Mueller explained, they had merely switched back to previous data as a temporary measure. “They’re working on resolving the actual issue and in the meantime switched back to the data from the week before.”

Old Data: If you check your link report now, it displays old information. This is crucial to keep in mind if you’re using this data for reports to clients or stakeholders.

The Bug’s Impact: Many folks noticed either zero links or a drastic drop exceeding 85%. Here’s a screenshot highlighting the problem:

OK, this takes the cake. Hahaha. Yeah, something is very off with the links reporting in GSC. pic.twitter.com/KIYmFPm1fX— Glenn Gabe (@glenngabe) May 21, 2026

Why It Matters: For those relying on this link data for generating reports, the inaccuracy can be problematic. Data pulled on that Thursday might not be reliable.

While Google is addressing the issue, be prepared to work with data that’s temporarily outdated.

Inspired by this post on Search Engine Land.

May 26, 2026
Master Google’s Generative AI Optimization: A Step-by-Step Guide

I recently came across Google’s fresh guide on optimizing for its generative AI features, highlighting key tools like AI Mode and AI Overviews. This guide compiles insights from previous Google communications into a comprehensive help document titled Optimizing your website for generative AI features on Google Search.

Inside the Guide: This document delves into multiple essential topics, which include:

– SEO’s continued relevance for AI search, adhering to Google’s SEO best practices.

– Creating valuable, non-commodity content for your audience.

– Offering a unique perspective

– Developing content that is helpful, reliable, and prioritizes users

– Organizing content effectively for reader assistance

– Incorporating high-quality images and videos

– Focusing on user needs, avoiding unnecessary complexity

– Ensuring AI tools comply with Google’s guidelines

– Maintaining a clear, technical site structure:

– Meeting technical search requirements

– Adhering to best practices for web crawling

– Emphasizing human-readable semantic HTML

– Following Google’s guidelines for JavaScript

– Providing an excellent page experience

– Reducing duplicate content

– Focusing on optimizing local business and e-commerce details.

– Dispelling myths around AI optimization:

– No need for LLMS.txt files

– Avoidance of special markup

– Refraining from ‘chunking’ content

– No content rewrites for AI systems required

– Avoid seeking inauthentic mentions

– Not overly focusing on structured data

– Exploring agentic experiences and what steps to take next.

Why It Matters to Me: This guide is a comprehensive resource that summarizes Google’s past advice across various platforms and events. It’s invaluable for understanding how to align my site with Google’s expectations for AI-powered search engines.

You can read the full guide here.

Inspired by this post on Search Engine Land.

May 15, 2026
Google Targets AI Spam in Latest Search Policy Update

Recently, I discovered that Google has updated its search spam policies, explicitly stating that these rules also apply to generative AI responses within Google Search. This update clarifies that using spammy tactics to get your site or brand featured in AI Overviews, AI Mode, or other AI-based responses now classifies as spam. Google warns that it will take action against such practices.

What changed. Google revamped a key line in their policy:

“In the context of Google Search, spam refers to techniques used to deceive users or manipulate our Search systems into featuring content prominently, such as attempting to manipulate Search systems into ranking content highly or attempting to manipulate generative Al responses in Google Search.”

Originally, it said:

“In the context of Google Search, spam refers to techniques used to deceive users or manipulate our Search systems into ranking content highly.”

I came across a visual representation of this policy addition:

Why I care. I’ve noticed there’s a lot of advice circulating about optimizing for AI search engines. Some strategies might conflict with Google’s updated spam policies. It’s important for me, and anyone else trying to optimize their presence in AI responses, to carefully review these policies and ensure compliance, avoiding any spam techniques that could harm visibility on Google.

Inspired by this post on Search Engine Land.

May 15, 2026
Google Ends Support for FAQ Rich Results – Here’s What You Need to Know

I recently came across some important news from Google that I felt compelled to share with you. As of May 7, 2026, Google will no longer support FAQ rich results. This change means that these helpful snippets will no longer appear in Google Search results.

Additionally, Google Search Console will cease reporting on FAQ structured data, impacting how we track and analyze our content’s performance in search engines.

What Google said: Google has posted a notice on the FAQ structured data developer documentation. They state: FAQ rich results are no longer appearing in Google Search. By June 2026, Google plans to fully drop the search appearance, rich result report, and support in the Rich results test. To provide some adjustment time, support for the FAQ rich result in the Search Console API will be removed by August 2026.

Remove code: You might be wondering what to do with your existing FAQ structured data. The choice is yours—you can remove it from your code, but leaving it might still benefit you if other search engines use it for their own purposes.

Why we care: For me and many others, rich results have been instrumental in increasing web pages’ click-through rates and attracting additional traffic. The discontinuation of FAQ rich results could impact this dynamic.

To gauge the effect on your website, monitor pages with FAQ structured data closely and pay attention to any shifts in your traffic from Google.

Inspired by this post on Search Engine Land.

May 8, 2026
Explore Google’s New AI Search Link & Citation Updates

Have you noticed a change in how Google displays links and citations in its AI search features? I recently learned about five key updates that aim to enhance our experience with AI Mode and AI Overviews.

According to Hema Budaraju, VP, Product Management at Google, these upgrades are designed to help us connect with authentic voices and access valuable information across the web. She detailed these updates in a recent article.

Let’s dive into the updates rolling out:

(1) Suggested angles at the end of AI responses. Google now suggests further reading options at the end of AI responses. These link to unique articles or analyses that deepen our understanding of the topic. It’s like having a roadmap to satisfy our curiosity!

Here’s a preview of this feature:

(2) Easier access to your news subscriptions. With this update, Google displays links from our news subscriptions prominently. This means I can quickly access content I trust, maximizing the value of my subscriptions. During Google’s early tests, these subscription links significantly boosted click-through rates.

If you’re a publisher, check out the documentation to enable this feature.

Here’s what this looks like in action:

(3) Social media and online discussions now include creator details. When AI features cite social media, Google includes not only the website’s name but also the creator’s name, handle, and community name. This transparency helps me spot firsthand sources at a glance.

Here’s a glimpse of how this plays out:

(4) More links, next to relevant text. Google is increasing the number of links shown directly within AI responses, strategically placing them next to relevant text. This makes it tempting for me to explore these sources further.

Here’s what it looks like:

(5) Hover over inline links for a quick look. Now when I hover over an inline link in Google’s AI features, I get a sneak peek of the website. This could just be the nudge I need to click through and explore further. I remember seeing Google test this back in February and thought it was a brilliant idea.

Here’s an example of the feature:

Why this matters. Google is committed to ongoing testing and refinements, ensuring these features serve us better. I truly believe these changes will promote more engagement with the cited pages, presenting an exciting step forward for both users and the web ecosystem. The real question is, will they meet my expectations?

Inspired by this post on Search Engine Land.

May 6, 2026
Google’s UCP Checkout Revolutionizes Search Shopping

I find it fascinating that Google’s Universal Commerce Protocol (UCP), which was initially limited to AI Mode, is now expanding into regular search results. It’s not just a fleeting trend; some retailers have already begun integrating this technology into their listing pages, making our online shopping experience even more intuitive.

Earlier this year, Google rolled out UCP for AI-agents to facilitate direct purchases from search results. It first launched exclusively within Google’s AI Mode but now, we’re seeing it implemented in Google’s main search results for retailers who support UCP.

Discovering what the UCP checkout looks like was made easier thanks to a post by Brodie Clark. He shared a screenshot showing how Wayfair’s listings on Google Search now feature a UCP-powered ‘Buy’ button. This button is a game-changer because it allows purchases directly from Google’s interface without navigating to Wayfair’s website.

The UCP protocol is paving the way for seamless transactions by establishing a common language for AI agents and commerce systems. No longer do we have to worry about bespoke integrations across different platforms.

Collaboratively developed with big names like Shopify, Etsy, Wayfair, and Target, UCP aligns with existing standards, such as Agent2Agent and Agent Payments Protocols, creating a more cohesive digital commerce space.

What really excites me is the potential for profit growth for retailers who embrace this technology. Although Wayfair might miss out on direct site traffic for specific searches, their affiliation with Google through UCP can still result in conversions.

While it’s clear that not everyone will bypass the traditional shopping journey, as many of us still prefer exploring products on the retailer’s site, the option to ‘Buy’ directly adds a layer of convenience. It’s definitely something worth monitoring as its prevalence in search results increases.

Inspired by this post on Search Engine Land.

May 5, 2026
Explore Google’s Innovative Web Bot Auth for Authentic Bot Verification
Have you ever wondered how Google is ensuring the authenticity of AI bots? I recently stumbled upon Google’s latest experimental method, Web Bot Auth, which aims to address exactly that. This project is currently in a limited testing phase, specifically for AI agents hosted on Google’s infrastructure, but it could be expanded in the future.

In Google’s new help document, they clarify that Web Bot Auth is a “new cryptographic protocol that helps websites validate that bots are authentic.” This innovative approach is designed to automate the authentication of AI Agent bots, distinguishing between genuine and fraudulent bots.

Limited test phase: Google’s team mentions they are “testing the protocol with some AI agents hosted on Google infrastructure.” It’s important to note that not all Google user agents are currently using Web Bot Auth, and the company isn’t signing every bot request with this protocol just yet.

During this gradual rollout, Google advises us to keep using IP addresses, reverse DNS, and user-agent strings alongside Web Bot Auth, as not all traffic is currently signed.

What is Web Bot Auth? Defined as “an experimental cryptographic protocol used to authenticate requests sent by bots,” this method moves away from self-reported headers and IP addresses. Instead, it allows agents to sign their requests cryptographically.

According to Google, Web Bot Auth offers several benefits:
- Future-proofing: Supporting a trusted environment where agent providers and websites can mutually verify access.
- Cryptographic certainty: Transitioning from easily falsified headers to a verified identity, separate from IP addresses.
- Better observability: Gaining clear insights into agent interactions with your content.
Why this matters to us: As AI agents continue to proliferate online, managing access to our sites becomes increasingly complex. This new authentication method could effectively distinguish credible AI agents from deceptive ones, ensuring the right entities access our data.

Since Web Bot Auth is still “experimental,” I’ll be keeping an eye on its development. It might just transform how we manage AI bot access in the future.

Inspired by this post on Search Engine Land.
May 5, 2026
Unlocking Google SEO: Master ‘Read More’ Links Best Practices
I recently discovered that back in December, Google introduced read more links for certain search result snippets on Google Search. Now, Google has shared some best practices to help us utilize these ‘Read More’ links effectively.

Digging into the Best Practices: To find these new insights, you can check out the documentation posted here. It outlines three essential tips:
- Ensure the content is instantly visible to human visitors, not tucked away behind tabs or expandable sections.
- Avoid using JavaScript that governs the user’s scroll position as the page loads. Let your users control their browsing experience.
- If you’re calling history API functions or modifying window.location.hash on page load, don’t strip away the hash fragment. This could lead to issues with deep linking.
Visualizing the Concept: Google provided an image illustrating these links. Here’s a glimpse of how they appear:

Let me show you an example of these snippets in action:

Why It Matters to Us: The introduction of read more links adds an alluring touch to search result snippets. The potential for increased website clicks can be significant. Therefore, reviewing these best practices becomes essential for attracting even more visitors to our site.

Ultimately, driving more traffic is always a win, so optimizing your site with these tips could prove beneficial.

Inspired by this post on Search Engine Land.
April 20, 2026
Google Now Uses Spam Reports for Direct Manual Actions

I’ve recently come across a noteworthy update from Google, which now enhances the potential impact of our spam reports. Interestingly, these reports are no longer just documentation—they might trigger manual actions against the reported sites. In addition, whatever I write in my report could be shared verbatim with the site owner I’ve reported.

Here’s Google’s Announcement. Google clarified in a note that they may utilize our spam report submissions to undertake manual actions against policy violations. This update makes it clear that spam reports are more critical than ever in maintaining the integrity of Google’s search results.

The updated guidelines specify:

“Ranking manipulation techniques that attempt to compromise the quality of Google’s search results violate our spam policies and can negatively impact a site’s ranking. Google may use your report to take manual action against violations. If we issue a manual action, we send whatever you write in the submission report verbatim to the site owner to help them understand the context of the manual action. We don’t include any other identifying information when we notify the site owner; as long as you avoid including personal information in the open text field, the report remains anonymous.”

Spam Reports Fuel Manual Actions. It seems that Google aims to clarify their usage of spam reports. This is quite the shift from their previous communication, where spam reports didn’t directly lead to manual actions. To me, this feels like more than just a clarification—it’s a significant development in how reports are handled.

Direct Transmission of Spam Report Text. Also, Google stated that the exact text I use in my spam report might be sent to the site owner. They advise us not to include personal details, as my submission remains anonymous unless I disclose such information.

Google emphasizes the importance of keeping sensitive information out of the report to ensure my anonymity is maintained.

Why This Matters to Us. This change could significantly alter how we approach spam reporting on Google. If you’re someone who regularly submits these reports, like I do, it’s essential to understand the new implications and modify your reporting practices accordingly.

Inspired by this post on Search Engine Land.

April 15, 2026
Google to Crack Down on Annoying Back Button Hijacking
You have until June 15, 2026, to remove the back button code before Google starts taking action.

I’ve just heard from Google about a new warning aimed at websites using back button hijacking tactics. These sites have been given a two-month deadline to remove or disable these sneaky techniques. If not, they risk facing manual spam actions or automated demotions in Google Search.

Back button hijacking. Google explained that, when we click the back button in our browser, we expect to return to the previous page. Back button hijacking disrupts this expectation. Google elaborated:
- “It occurs when a site interferes with a user’s browser navigation, making it impossible to use the back button to immediately return to the original page. Users might instead be redirected to pages they didn’t visit, shown unsolicited ads or recommendations, or otherwise prevented from browsing normally.”
While Google once claimed this had no effect on search rankings, that’s changing in just a couple of months.

June 15, 2026. From June 15, 2026, Google will start enforcing this action. Google emphasized, “We prioritize user experience. Back button hijacking interrupts the expected browsing journey and leaves users frustrated. People feel manipulated, and this makes them hesitant to visit unfamiliar sites.”

Why now? Google has observed an increase in this type of behavior. “This is why we are marking it as an explicit violation of our malicious practices policy, which states:”
- “Malicious practices create a mismatch between user expectations and the actual outcome, leading to a negative and deceptive user experience, or compromised user security or privacy.”
Google is giving us a two-month notice to implement changes. “By providing this policy now, two months ahead of the enforcement date, we are offering site owners the time needed to make adjustments before June 15, 2026,” Google stated.

Why this matters to me. If I’m using this technique, it’s crucial to remove it from my pages. I have a short window to make these changes before my website might face penalties or corrective actions.

Inspired by this post on Search Engine Land.
April 13, 2026

1 2 3