AMP stands for "Accelerated Mobile Pages" in SEO context. These pages are quite easy to create and they are indexed in a separate index in Google. In other contexts, the abbreviation for amplifier or amps stands.
Because many websites take too long to load, Google has developed a way to encode with special customization of various AMP fuctions retrieved by Google's own libraries. Basically, it's like working back to how to create web pages before 2000.
You can use canonical to direct the AMP page to the original page. The original page links to the AMP page. But you might as well be able to build a website just in AMP and report the pages to Google. Then you can follow data on the pages of Search Console during accelerated mobile pages. Here you can read about guidelines .
Now indexing of AMP pages has really started in Sweden. It will be interesting to see how it will develop. More exciting pages with code examples to create AMP pages with a little more features.
- >> https://ampbyexample.com/components/amp-iframe/
- >> https://www.ampproject.org/docs/guides/iframes
- >> https://www.ampproject.org/docs/guides/iframes
Through this, Google gets a great opportunity to lift the web into its own index as they have full control themselves 100%. In the long term, one can think about what it will mean. But even twitter has its own index where you will be warned if you want to read an article outside.
So the consequence of starting to create AMP pages is a bit double-bottomed. One might think that speed would be of greater interest to web developers and claimants in recent years. But most assume that the majority of Internet users have fast connection today. Nevertheless, many websites are heavy to load.
I myself wonder if you can compete with AMP pages by creating your own quick pages in classical HTML5.
No comments:
Post a Comment