Keep consistent page elements
Because you’re providing search engines with instructions for existing content versions (AMP and non-AMP, for example), you can keep code elements the same across the board. This includes hreflang, H1 tags, alt text for images, and structured data.
As we discuss structured data, it’s important to remember that when combined with AMP, you may have a better chance of getting rich results. Using effective structured data and AMP may make it more likely that you’ll be able to achieve this, resulting in a host carousel or rich results with headlines and larger images.
Although after Core Web Vitals , the gains in this area may india mobile database diminish, as both AMP and non-AMP pages may appear in page experience metrics.
Is AMP worth it?
This brings us to the final question: Is it worth using AMP pages? That depends on the availability of internal and external resources and how they might change in the future. It also depends on how much content you have and in what format.
If you already have AMP for publisher and news content, it makes sense to continue using it until you can learn more about the impact of Core Web Vitals.
At the end of the day, speed is of the essence. If you know you have enough developer time and resources to make ongoing improvements to your elements to meet the Core Web Vitals requirements, then it’s up to you to decide which route to take.