Technical optimization is achieved through barrier-free templates.

The final rendering of your templates can be counterproductive for the overall optimization of your articles.

Often the complementary objects (side bars, menus, footers,…) use a series of HTML tags that disturb the weighting of the keywords of your page.

The classic example is the H2 titles used in widget headings.

They generate a semantic pollution by repeating the same group of sentences on all your pages.

In the video example, I show you how you can quickly identify these flaws to reduce their impact.

I’ll show you a classic problem that we encounter on premium themes.

And this problem is detected at several levels, actually. there’s a level we’re going to see here on the pages. I’ll show you this in detail.

First clue: variety of queries on Google Search Console

The first clue I got the other day was actually by going here to look at the logics of Google Search Console queries, in the example here we still find variations around “Community Manager”.

There are really very few different requests.

You see,”cm paper”,”community”, it’s still very limited and it surprised me a little bit considering the number of articles on the site.

Second clue: the structure of a template

Now, if I’m going to see the detail of an article, I’m going to check the main HTML Tags of my page, in the H1 Tags, which are main, I find:”login, lost password, Register, logo…”.

At the H2 level, I have a series of information. Here, I am sure:”the differences between Mooc, e-learning and distance learning”.

Since these sentences or parts of sentences are repeated all over the pages that use this template, you end up with a ball. This doesn’t help to “see” the heart of the pages better.

And if I take another article:”5 tips to make a success of your live show at an LMSM event”: I end up with the same logic.

And with all the H3 flop, I still find myself with elements that actually have nothing to do with the optimization logic of my page core.

You see:”newsletter, community management, job offers etc.”, it’s a whole series of titles which may have their reason but which reveal a big problem with the structure of the Template. They do not help to highlight the core of the article.

And so in general, what you can do, if you look here, there are a whole series of elements in the top menu. This object is with an H3.

While what matters most is the content.

The solution: change tags that repeat themselves in peripheral areas with content

At the end of the day, it will be better if the code is a span tag with a class equivalent to the layout of a level 3 title, that it keeps the layout of the element. Visually nothing changes. Only semantic weighting would be better distributed.