Normal view

Before yesterdayMain stream

Google to no longer support FAQ rich results

8 May 2026 at 19:03

Google will no longer support FAQ rich results as of May 7, 2026. This means you will no longer see FAQ rich results in the Google Search results going forward.

Plus, Google Search Console will stop reporting on FAQ structured data.

What Google said. Google posted a note at the top of the FAQ structured data developer documentation saying:

FAQ rich results are no longer appearing in Google Search. We will be dropping the FAQ search appearance, rich result report, and support in the Rich results test in June 2026. To allow time for adjusting your API calls, support for the FAQ rich result in the Search Console API will be removed in August 2026.

Remove code. You can remove the FAQ structured data from your code, if you want but you can also leave it. Other search engines may be able to continue to process it and use it for their own purposes.

Why we care. Rich results have helped web pages with click-through rates and get more traffic. FAQ rich results may have helped as well. But that is now no longer supported.

Keep an eye on your pages with FAQ structured data to see if your traffic from Google is impacted or not.

Google AdSense removes browser back button trigger for vignette ads

7 May 2026 at 19:39

Google is dropping the back button trigger for AdSense vignette ads on June 15, 2026 due to the new Google search penalty for back button hijacking. Google wrote, “Starting June 15, 2026, the browser back button will no longer trigger a vignette ad.”

What is changing. Google explained that the back button trigger will no longer work after June 15th. The “change will apply automatically for all publishers who have opted in to “Allow additional triggers for vignette ads” and will take effect across all supported browsers (including Chrome, Edge, and Opera).” Google added.

A Google spokesperson told me these same updates will apply to Ad Manager as well.

Why the change. Google explained that the Google Search team “recently introduced a new policy against “back button hijacking” — a practice where websites or scripts interfere with a user’s ability to navigate back to their previous page. To ensure our publishers remain compliant with these latest user experience and search quality guidelines, we are removing the trigger that shows a vignette ad when the user navigates backward from the suite of vignette ad triggers.”

This comes after the search community called this out to Google and Google is making the right change here. Of course, some publishers will not be happy because that trigger may have earned them a lot of money.

Why we care. If you currently have the allow additional triggers for vignette ads setting on with AdSense, keep in mind, one of the triggers, the back button trigger, will be disabled on June 15th. It may impact your earnings, but it will ensure that your site does not get penalized by the back button hijacking penalty.

❌
❌