Answer the question
In order to leave comments, you need to log in
How to correctly form h2-h3 headings to avoid overoptimization?
I will give a general example:
There is a heading h1: A selection of watches with ozone
How to correctly form headings for h2 in this case?
A selection of women's watches with ozone / a selection of men's watches with ozone? (Wouldn't it be over-optimized if we add just one word to h1 to make h2)
Or
Women's Watches / Men's Watches? (But in this case, the headings will be higher-frequency than h1. In this case, will the PS take the context from h1, that this is a selection from ozone?)
How to correctly form h2 headings in such cases?
Would it be logical to put in this situation the heading h3 in the form of the name of the product?
Answer the question
In order to leave comments, you need to log in
First of all, it is necessary to observe the correct nesting of headings.
Personally, I form headings based on the logic of the page itself (structure) and the frequency of requests, that is, the most high-frequency requests of the cluster, I try to put it higher. But this is not always the right decision, there are situations when it is necessary to understand the final conversion and the complexity of the request.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question