If you are implementing AMP on your news or blog pages, you have probably implemented it with a www.example.com/directory/amp/ method, where all AMP pages are within a subdirectory. The official WordPress AMP plugin uses this method, so it is fairly common.
But what isn’t common is that websites can choose to serve their AMP pages from a different subdomain or domain.
During the SMX session yesterday, Dave Besbris from Google said that sites do not need to stick to their original domain and structure for their AMP pages. Instead, webmasters can utilize subdomains or even different domains.
Besbris brought up the example of The Guardian. Instead of keeping AMP in a subdirectory, they decided to use amp.theguardian.com. They also said that anyone can just remove the www and add amp from any www.theguardian.com/example/ URL to find the AMP version easily.
So if you are planning to implement AMP, feel free to use subdomains or a different domain completely, if you have other reasons for not wanting to include it within the pages of the usual page structure.
Latest posts by Jennifer Slegg (see all)
- JSON-LD Google’s Preferred Structured Data Markup - October 21, 2016
- How Google Handles Site Moves When Old Domain Cannot Be Redirected - October 20, 2016
- Exit Page Interstitials Not Impacted by Google’s Mobile Interstitial Change - October 19, 2016
- Google: Leave 301 Redirects in Place at Least a Year, Preferably Longer - October 19, 2016
- Site Wide & Blogroll Links Are Not Automatically Bad Links for Google - October 19, 2016