Extra H1 header causing potential Accessibility and SEO issue

  • Resolved davidginzberg

    (@davidginzberg)


    1 year ago

    Hello,
    I see that there are two existing support questions about the h1 tag added by this plugin. Those both have an answer stating that search engines are suppressed from loading the script. However, when looking at the robots.txt for translate.google.com, I see the following line:

    Allow: /translate_a

    It appears that the script loaded by this plugin ( translate_a/element.js) is not actually suppressed, leading to issues with the duplicate h1 tag. Can you please address this issue?

    Either way, the presence of a second H1 tag on a rendered page is still producing issues on SEO and Accessibility reports (whether they are false- or true-positives). If it’s not absolutely necessary for that element to be an h1 (could it perhaps be a different semantic HTML element?) please consider adding an option to hide or modify this element (for example, this commit on GitHub seems to do this) so that this issue is not present anymore and is future-proofed in case of further changes to the robots.txt for the script’s source domain.

Viewing 1 replies (of 1 total)
  • Plugin Author edo888

    (@edo888)

    11 months, 4 weeks ago

    Hi,

    The translate_a/element.js is not the script which adds the hidden h1, it is a different one which is loaded by translate_a/element.js. Recently Google has made lots of changes for the translator widget and we have not received any complaints yet about the hidden h1 tag.

    If you are concerned, you can write additional javascript code to remove it. Something like this should do the trick for you:

    <script>
jQuery(document).ready(function() {
    jQuery('.skiptranslate h1').remove();
});
</script>

    Thanks! 🙂

Viewing 1 replies (of 1 total)
  • The topic ‘Extra H1 header causing potential Accessibility and SEO issue’ is closed to new replies.