Google has just announced on the Google Webmaster Central Blog that as of February 1, 2018, it will require the AMP pages to have identical content to the original ones.
Starting February next year, Google will request parity between AMP and canonical URLs – “If we find that a AMP page does not contain the same critical content as the non-AMP equivalent, we will direct users to the non- AMP. ”
Launched in 2015, the AMP project has reached over 25 million websites.
In some cases, web administrators publish two versions of the content: a canonical page that is not based on AMP and a AMP page. Ideally, these two pages will have equivalent content and the user accesses the same content but faster and with a better use experience with AMP. Sometimes, however, the AMP page does not have the same content as a non-AMP page.
In few cases, AMP pages are used as an advertisement to the original content, which leads to a poor user experience because it contains only a minimal content from the canonical, non-AMP page. So users have to click twice to access the entire content.
Introduced to improve page performance, AMP delivers an experience of fast and consistent content consumption.
To preserve this level of experience, Google promises to impose the need for a parity between AMP content and the main content for pages that are eager to display as AMP in Gogle Search.
If a AMP page does not contain the same content as the main page, a redirect will be made to the non AMP page. That will not affect the position on the search engine page, promise Google.
Agile Media advices
Follow us on our Agile Media Blog, on our Facebook Page Agile Media, on our Twitter Account Agile Media and on our LinkedIn page Agile Media to receive news as well as tips on Marketing, SEO, Google Analytics, Google Adwords.
We offer the following services:
- SEO (Search Engine Optimization),
- PPC (Pay Per Click),
- SMM (Social Media Marketing),
- Link Building,
- Content Marketing,
- ORM (Online Reputation Management),
- Competition Analysis,
- Keyword Strategy,