Thanks.

I’ve disabled sucuri.

Regarding the other link – this appears to refer to a plugin called contentviews pro that I don’t have? Will it actually make any difference as the code appears to be specific to the plugin?
https://docs.contentviewspro.com/fix-issue-element-style-not-allowed-child-element-div-context/

Hi,

To answer your questions:

– I have made no changes to the theme files.
– I do not have a child theme
– Plugins (9 in total) are the ones that came with newspaper (4 tagdiv ones) + yoast + google console + quantcast choice + akismet + sucuri

Thanks!

Hi,

From what I am told this will not resolve this issue with the code on the page.

This is the impact I have been informed of:

A substantial number/critical type of HTML errors can lead to certain parts of offending pages not being correctly indexed by Google as their crawlers simply are unable to read the code if it does not conform to HTML standards. It’s quite easy to make HTML errors and without a tool to carefully scan through your code. Your SEO rankings can quickly evaporate after making content changes to your pages, and realizing far too late that Google can no longer read these new changes as you’ve incorrectly placed an attribute.

Google’s spokesman John Mueller elaborated on this saying that:

While HTML validity is not a direct ranking factor, critical HTML errors get in the way of Google achieving the following:

successful crawling of a site and indexation of SEO relevant pages;
crawling, reading, and understanding of structured markup on a page;
rendering your site’s pages correctly on mobile devices and displaying different versions of your site correctly based on cross-browser compatibility.