Partners that don't use WordPress as a CMS and want to serve AMP pages over HTTPS with a custom URL must first create and register a CNAME, set up a reverse proxy configuration, and then insert a specific code in the HTML of every article they want activated as a Google AMP page.
Using a CNAME to serve AMP pages under custom domains requires specific steps to be performed in order to serve them under HTTPS. Publishers also have to distribute the content using a reverse proxy configuration. The reason a reverse proxy is needed is because HTTPS requires the certificate in the domain where it will be served (the publisher's domain).
Best practices dictate that the publisher manages their security certificates on their end and sets up a reverse proxy.
While setting up AMP pages over HTTP requires less manual effort, it's also important to note that serving AMP pages over HTTPS does not provide significant benefits as a publisher's AMP content is served by Google's servers.
To complete the entire procedure, perform the following steps:
Google recommends that a publisher's AMP pages be served under their specific domain which means they must create a CNAME in their DNS provider according to the following naming convention:
The CNAME publishers register depends on the Marfeel domain they are on.
- Create a reverse proxy configuration. For more information, see the Set Up a Reverse Proxy Configuration article.
- Aggregate Google AMP events to Webmaster Tools. This step ensures that partners can track their Google AMP events by linking their Google AMP domain to their current Search Console account. It involves creating and grouping the property into a property set in Webmaster Tools. For a complete overview and the steps necessary, see the Group your properties into sets article in Google's Search Console Help.
Insert a code resembling the following example with a link element pointing to the AMP pages, for every article you want activated as a Google AMP page.