How to use AMP with Google Ads

Faster mobile landing pages typically reduce website abandonment and bounce rates, which can increase conversions and improve your overall ad performance. For a simple way to speed up load times, build your landing page with AMP. This article explains how to use AMP with Google Ads.

For more context, start by learning about Accelerated Mobile Pages (AMP).

Before you begin

AMP pages load fast and even faster from Google's AMP Cache. Currently, cache serving is available for text Ads on most major mobile browsers.

Follow our step-by-step guide

To create AMP versions of your landing pages (or if you want to repurpose existing AMP pages as Ads landing pages), use our Google Ads Developer Guidelines for AMP pages.

Set your new Mobile URL

Once you’ve created an AMP version of a landing page, you can treat it like you would any other mobile landing page. For your text Ads and keywords, add your AMP page URL as your mobile URL. Then, when a mobile user clicks your Ad, they’ll see the fastest version of your available page. AMP pages load from Google AMP Cache whenever possible for faster page loads. When we are unable to serve from cache, we’ll load your AMP landing page from your web server, which will still be typically faster than pages that aren’t AMP.

Add your AMP URLs to your ads with bulk edits

Once you code your AMP pages, you’ll need to change your ads’ landing pages. There are three ways to bulk edit ads:

Steps for bulk uploads feature within Google Ads:

  1. Download your editable Ads from Google Ads.

  2. Add your AMP URLs for your mobile landing pages.

  3. Upload your edited ads back into your Google Ads account.

Learn more about making changes with bulk uploads.

Note:  Make sure that your mobile URL goes to your domain (for example, https://example.com/page_amp.html) rather than to the Google AMP cache, which could be in any of the following formats:

  • https://www.google.com/amp/s/example.com
  • https://cdn.ampproject.org/c/s/example.com
  • https://example-com.cdn.ampproject.org/example.com/amp.html

Make sure your AMP pages are valid

Pages that don’t follow AMP guidelines can’t be cached, so they load more slowly than cached pages and therefore don’t perform as well. Make sure that you don't have invalid pages by using (or encouraging your web developers to use) AMP’s validation tool.  While the AMP validation tool should be used in the page development, it’s also a good idea to check for invalid AMP pages from within your Google Ads account. To do this:

  1. Select Landing pages from the blue page menu of your Google Ads account.

  2. Review the “Valid AMP click rate” column. 

Note:  Landing pages with click rates less than 100% may be invalid. If this is the case, you or your web developer should fix the coding using AMP’s validation tool.

Use tracking wisely

To make sure that visitors get to your page as quickly as possible, make sure that you use only the necessary URL parameters. Parameters that aren’t used to customise the contents of your landing page should be added after the {ignore} parameter, so your Ads are more likely served from Google’s fast AMP Cache. 

Note:  You should still use AMP landing pages in Google Ads and let Google determine when it can serve from Google AMP Cache.

AMPHTML ads

In addition to cache serving for text ads, you can apply the principles of AMP by creating AMPHTML ads. These ads allow you to deliver faster, lighter and more secure ad experiences across all platforms. You also have the ability to serve AMPHTML ads on both AMP and non-AMP pages. Benefits of using AMPHTML Ads:

  • AMPHTML ads are faster than regular ads on AMP pages, making them easier to view,  more effective and more likely to perform well.

  • The AMP framework ensures that these ads only behave as intended so users always have a positive experience with your brand.

  • AMPHTML ads are required to be validated before they’re served, which reduces the risk of malware and can help build trust in your brand as users engage with it.

Was this helpful?
How can we improve it?

Need more help?

Sign in for additional support options to quickly solve your issue