[IMPORTANT] Make beaver W3C compatible to improve SEO

Hello,

We have seen beaver is not W3C compatible. It prevents us to improve SEO’s websites.

Can you correct the mistakes on yours modules and theme ?

Example : Call out : You should replace <span class=“fl-cta-text-content”> by a div for the content (wordpress text editor add automatically p tags and a p mustn’t be into a span)

<div class="fl-module fl-module-cta fl-node-55a2eafe41a5b" data-node="55a2eafe41a5b" data-animation-delay="0.0">
	<div class="fl-module-content fl-node-content">
		<div class="fl-cta-wrap fl-cta-inline">
	<div class="fl-cta-text">
		<h3 class="fl-cta-title">Ready to find out more?</h3>
		<span class="fl-cta-text-content"><p style="">Drop us a line today for a free quote!</p>
</span>
	</div>
	<div class="fl-cta-button">
		<div class="fl-button-wrap fl-button-width-full">
	<a href="" target="_self" class="fl-button" role="button">
				<span class="fl-button-text">Click Here</span>
			</a>
</div>	</div>
</div>	</div>
</div>

An other example : https://validator.w3.org/nu/?doc=https%3A%2F%2Fwww.wpbeaverbuilder.com%2F

Thank in advance

Hey Novfr,

I’ve already assigned another member of the team to check on this.

Ben

Hi novfr,

Thanks for bringing that to our attention. It looks like W3C is flagging callout modules because they have nested inline elements. I don’t think there will be an issue with getting that changed to a div and have made a note to do so in the next release.

Regarding SEO, I’m not entirely sure that will affect it. We’re using callout modules on our homepage and currently rank on the first page of Google for a number of competitive keywords. You’ll see that even Google itself doesn’t validate…

https://validator.w3.org/nu/?doc=https%3A%2F%2Fwww.google.com%2F

Thanks,
Justin

Hello,

Our SEO analysis tools alert us to this issue and drop our scores. Google does not need to meet its own criteria for its own services as it has a monopoly on the market.

We know that Wordpress Editor adds inline styles and that is problematic (we will try to solve this problem). But without the inline styles the problem is this: block-level tags (p, h1, h2, …) are introduced into the content of the callout and are placed in a span. This is one example among many.

Apart from SEO criteria, respect the W3C standards means quality for our customers and helps improve the web and rendering graphical equivalent, and that whatever browsers. You will agree with us.

Thank you for your answers, we use regularly Beaver and we love it!

Hi novfr,

Our SEO analysis tools alert us to this issue and drop our scores.

I understand that, but just because an SEO analysis tool shows a lower score doesn’t mean that your ranking will go down. No one nows the exact formula for ranking a website.

Google does not need to meet its own criteria for its own services as it has a monopoly on the market.

That’s actually untrue. Some of Google’s properties have been falling in the SERPs, so they are looking at hire an SEO manager to help with that… http://searchengineland.com/google-is-hiring-an-seo-to-improve-their-ranking-in-google-225320

We’ll look into getting the block elements nested in inline elements fixed. Thanks!

Justin