Honeypot text showing in SERP

Hi Torsten,

Do you use any SEO plugins like Yoast or Rank Math? If yes, you can set the meta description that will be displayed on the SERP and social media shares. By using a custom meta description, you can easily prevent irrelevant text from appearing on SERP and social media shares.

You can follow the article below to setup the meta description: https://rankmath.com/kb/seo-meta-tags/.

Hi @faisalahammad

there is a meta description set. Google can decide to ignore this value and show the text found on the page. And in this case it happened with the honeypot text, which is confusing for the visitor.

All the best
Torsten

Hi Torsten,

It seems that the text “If you are a human seeing this field, please leave it empty.” is sourced from two different script files. One has a CSS ID of “nf-front-end-js-extra“, which can be activated using jQuery to append the “data-nosnippet” attribute.

However, it is uncertain whether Google crawls from this script file. Let’s start with this approach and inform me of the results.

jQuery(document).ready(function($){
    $('#nf-front-end-js-extra').attr('data-nosnippet', '');
});

You can use this jQuery code in your child theme JS file or use the “Simple Custom CSS and JS” plugin. The Google SERP can take a few days to update.

???? https://www.ads-software.com/plugins/custom-css-js/

Please keep me posted about the outcome. Thank you ??

Hey @faisalahammad

this is not the output of the text, but the JavaScript for the translation (i18n). The text itself is in the form. So adding the attribute to the line loading the JS does not make sense at all.

I could modify your idea to use .nf-form-hp, which seems to be the generic class for the honeypot. But I am wondering if Google executes JS before indexing.

I don’t think this approach will be successful (although at least Google and Bing render JS). It would be much easier, if Ninja Forms would just add the mentioned attribute to their honeypot.

All the best
Torsten

Hello Torsten,

Thank you for reaching out and highlighting this issue with the honeypot field appearing in search engine results. Your suggestion to use the data-nosnippet attribute is a great one and could certainly help prevent this content from being displayed in search results without revealing the nature of the honeypot.

I will forward this suggestion to our development team to let them know that we can consider implementing it in the future. Adding this attribute should maintain the honeypot’s functionality and its purpose of deterring spam, as it only affects how search engines display the data.

In the meantime, if there’s anything more I can assist you with, or if you’d like to provide further input, please don’t hesitate to reach out. Your feedback is invaluable in helping us improve.

I am getting the same issue with pages that DO have a meta description set.