针对 Google Ads 着陆页使用 AMP
使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
着陆页加载速度越快，转化次数往往就越多。AMP 是制作加载速度更快且富有吸引力的 Google Ads 着陆页的绝佳方式。amp.dev 为 Web 开发者提供了制作富有吸引力且效果出色的网页所需的资源。本分步指南介绍了如何在 AMP 网页中使用 Google Ads 和其他广告技术。
第 1 步：创建和验证 AMP 网页
创建 AMP 网页
如需了解如何制作基本 AMP 网页，请先参阅 AMP 项目的创建您的首个 AMP 网页教程。如需获取更多实操性分步指导，请完成将 HTML 转换为 AMP 和添加高级 AMP 功能教程。您可以在 AMP 网站示例和 AMP 模板中找到 AMP 组件的示例代码和模板。
下列列表介绍了 AMP 网页上使用的部分组件。如需参考，请参阅组件的完整列表。
验证 AMP 网页
在开发过程中，您需要确保您的 AMP 网页有效。AMP 提供了多种不同的方法来验证您的文档。验证 AMP 网页的最常用方法是使用网页验证工具或 Google 网站站长工具验证工具。您还可以使用 Chrome 浏览器插件和开发者控制台，或在 build 中集成 amphtml-validator npm 模块。
您还可以使用 AMPBench，这是一个开源 Web 应用和服务，可用于验证和调试与 AMP 网页部署相关的问题。
如需有关 AMP 测试的支持，请访问 AMP 项目的获取支持页面。
第 2 步：为转化跟踪和分析设置 AMP
Google Ads 转化跟踪
使用 amp-analytics 组件跟踪 Google Ads 转化。如需了解如何进行此设置，请按照为 AMP 着陆页设置 Google Ads 转化衡量中的步骤操作。
Google Analytics
Google Analytics 是 amp-analytics 支持的分析解决方案之一。如需跨 AMP 和非 AMP 网页统一会话，请按照为 AMP 网页设置 Google Analytics 会话统一中的步骤操作。
Google 跟踪代码管理器
amp-analytics 组件内置了对 Google 跟踪代码管理器的支持。除了 Google Ads 转化之外，您还可以使用 Google 跟踪代码管理器添加再营销、DoubleClick Floodlight、Google Universal Analytics 和类似的衡量产品。请参阅兼容代码的完整列表。
Adobe Analytics 提供了两种使用 amp-analytics 组件实现其网站效果跟踪解决方案的方法：iframe (adobeanalytics_nativeConfig) 和非 iframe (adobeanalytics) 实现。不妨了解每种方法的优缺点和实现细节。
您可以使用 amp-analytics 组件跟踪用户操作和事件。AMP Analytics 提供 40 多家分析服务供应商的原生支持。该框架非常灵活，可让您使用自定义配置衡量和触发网址，以便将分析信息发送到您自己的服务器或不支持原生 AMP 的供应商。如果您使用的技术目前不受支持，请要求供应商添加支持。
AMP 分析还支持灵活的变量替换；如需了解详情，请参阅变量替换文档。
第 3 步：在 Google Ads 界面中启用 AMP 广告投放
虽然 Google 搜索中的 AMP 网页会通过网页中的链接自动发现，但广告客户必须在 Google Ads 中明确输入 AMP 网页网址。如需详细了解如何在 Google Ads 界面中设置 AMP 网址，请参阅如何在 Google Ads 中使用 AMP。
目前，在大多数主流浏览器（包括 Android Chrome、Android Google 搜索应用和移动 Safari）上投放的 Google 搜索结果页上的文字广告均支持缓存加载。我们在未来几个月中将扩大缓存支持范围。
如果您想测试 AMP 网页在 Google 搜索查看工具中通过 Google AMP Cache 提供时的显示效果，请在 Google 搜索 AMP 测试工具中输入您的 AMP 文章，然后点击预览链接。
此外，如果您希望将 Google Ads 流量引导至 AMP 着陆页，但不希望这些网页显示在自然搜索结果中，请像对待任何常规网页一样，向 robots.txt 添加相关 AMP 网页的禁止指令。
更新着陆页上的 AMP 内容
当用户从 Google AMP Cache 请求 AMP 文档时，缓存会自动请求更新，以便在缓存内容后为下一位用户提供新内容。采用这种模式后，AMP 文档的更新会自动快速传播；在您更新后，很少有用户会注意到未更新的版本。此外，如有需要，您还可以使用 update-cache API 更新或移除 AMP 缓存中的内容。
AMP 项目每天都在添加新功能和组件。如果您发现缺少某项功能，可以贡献该功能，也可以通过创建 GitHub 问题来请求添加该功能。
AMP 网页处理方式无效
当网页失效时，AMP Cache 会在几次请求内发现这一点，并开始重定向到提供 AMP 网页的来源。系统可能需要 1 到 2 天才能恢复使用 AMP 缓存服务。
如未另行说明，那么本页面中的内容已根据知识共享署名 4.0 许可获得了许可，并且代码示例已根据 Apache 2.0 许可获得了许可。有关详情，请参阅 Google 开发者网站政策。Java 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC)：2025-08-21。
[null,null,["最后更新时间 (UTC)：2025-08-21。"],[[["\u003cp\u003eFaster landing pages typically lead to more conversions and AMP is a great way to create attractive, fast-loading Google Ads landing pages.\u003c/p\u003e\n"],["\u003cp\u003eThis guide provides step-by-step instructions on how to create, validate, and implement AMP pages for advertising purposes, including conversion tracking and analytics.\u003c/p\u003e\n"],["\u003cp\u003eSeveral AMP components are highlighted, such as amp-bind, amp-form, amp-list, and amp-carousel, offering interactive and dynamic features for landing pages.\u003c/p\u003e\n"],["\u003cp\u003eAMP analytics supports various platforms including Google Ads, Google Analytics, and Google Tag Manager, allowing for comprehensive tracking and measurement of user interactions.\u003c/p\u003e\n"],["\u003cp\u003eGoogle Ads requires explicit input of the AMP page URL for ad serving, and the AMP project encourages contributions and feedback for ongoing improvement.\u003c/p\u003e\n"]]],[],null,["# Using AMP for your Google Ads landing pages\n\n[Faster landing pages](//support.google.com/google-ads/answer/7496737) typically\nlead to more conversions and AMP is a great way to create attractive Google Ads\nlanding pages that load more quickly. [amp.dev](//amp.dev/) provides web\ndevelopers with resources they need to create attractive, high performing pages.\nThis step-by-step guide describes how to use Google Ads and other advertising\ntechnology in your AMP pages.\n\nStep 1: Create and validate AMP pages\n-------------------------------------\n\n### Create AMP pages\n\nTo learn how to create a basic AMP page, start with the AMP Project's [Create\nyour first AMP page](//amp.dev/documentation/guides-and-tutorials/start/create/)\ntutorial. For more hands-on, step-by-step guidance, complete the [Convert HTML\nto AMP](//amp.dev/documentation/guides-and-tutorials/start/converting/) and [Add\nadvanced AMP\nfeatures](//amp.dev/documentation/guides-and-tutorials/start/add_advanced/)\ntutorials. You can find sample code and templates of AMP components at [AMP\nWebsites Examples](//amp.dev/documentation/examples/) and [AMP\nTemplates](//amp.dev/documentation/templates/).\n\nThe list below describes some components used on AMP pages---refer to the\n[complete list](//amp.dev/documentation/components/) of components for\nreference.\n\n- [amp-bind](//amp.dev/documentation/components/amp-bind): Add custom stateful interactivity based on JavaScript-like events.\n- [amp-form](//amp.dev/documentation/components/amp-form): Create landing pages that require input from the user.\n- [amp-list](//amp.dev/documentation/components/amp-list): Fetch content dynamically from a CORS JSON endpoint.\n- [amp-carousel](//amp.dev/documentation/components/amp-carousel): Image carousel for scrolling an image gallery.\n- [amp-lightbox](//amp.dev/documentation/components/amp-lightbox): Display full-screen view of a component when it's been interacted with.\n- [amp-call-tracking](//amp.dev/documentation/components/amp-call-tracking) Dynamically replaces a phone number in a hyperlink for call tracking.\n- [amp-mustache](//amp.dev/documentation/components/amp-mustache): Allows rendering with [Mustache.js](//mustache.github.io/).\n- [amp-date-picker](//amp.dev/documentation/components/amp-date-picker): Provides a widget to select dates. The date picker can render as an overlay relative to input fields, or as a static calendar widget.\n\n### Validate AMP pages\n\nDuring development you'll want to make sure your AMP pages are valid. AMP offers\n[several different\nmethods](//amp.dev/documentation/guides-and-tutorials/learn/validation-workflow/validate_amp)\nto validate your documents. The most common way to validate an AMP page is by\nusing the [web validator](//validator.ampproject.org/) or the [Google Webmaster\nTools Validator](//search.google.com/test/amp). You can also use the [Chrome\nbrowser\nplugin](//chrome.google.com/webstore/detail/amp-validator/nmoffdblmcmgeicmolmhobpoocbbmknc)\nand developer console, or integrate the [amphtml-validator npm\nmodule](//www.npmjs.com/package/amphtml-validator) in your build.\n\nYou can also use [AMPBench](https://github.com/ampproject/ampbench), which is an open\nsource web application and service to validate as well as debug issues around\ndeployment of AMP pages.\n\nFor support with AMP testing, visit the AMP Project's [Getting\nSupport](//www.ampproject.org/support/developer/get_support) page.\n\nStep 2: Set up AMP for conversion tracking and analytics\n--------------------------------------------------------\n\n### Google Ads conversion tracking\n\nUse the\n[amp-analytics](//amp.dev/documentation/guides-and-tutorials/optimize-and-measure/configure-analytics/)\ncomponent to track Google Ads conversions. Follow the steps in [Set up Google Ads\nconversion measurement for AMP landing\npages](/google-ads/amp/conversion-measurement) to learn how to set this up.\n\n### Google Analytics\n\n[Google Analytics](/analytics/devguides/collection/amp-analytics) is one of the\nsupported analytics solutions by\n[amp-analytics](//amp.dev/documentation/components/amp-analytics). To enable\nsessions to be unified across AMP and non-AMP pages, follow the steps in [Set up\nGoogle Analytics session unification for\nAMP](//support.google.com/analytics/answer/7486764).\n\n### Google Tag Manager\n\nThe [amp-analytics](/analytics/devguides/collection/amp-analytics)\ncomponent has built-in support for [Google Tag\nManager](//support.google.com/tagmanager/answer/6103696). In addition to Google\nAds conversions, you can use Google Tag Manager to add remarketing,\nDoubleClick Floodlight, Google Universal Analytics, and similar measurement\nproducts. Refer to the [full list of compatible\ntags](//support.google.com/tagmanager/answer/6106924).\n\n### Adobe Analytics (formerly known as Omniture)\n\nAdobe Analytics offers two methods for implementing their website performance\ntracking solution with\n[amp-analytics](//amp.dev/documentation/guides-and-tutorials/optimize-and-measure/configure-analytics/)\ncomponent: iframe (`adobeanalytics_nativeConfig`) and non-iframe\n(`adobeanalytics`) implementation. Read about the pros/cons and implementation\ndetails of each\n[approach](//marketing.adobe.com/resources/help/en_US/sc/implement/accelerated-mobile-pages.html).\n\n### Integrating other common Google Ads-related technologies\n\nYou can use the\n[amp-analytics](//amp.dev/documentation/guides-and-tutorials/optimize-and-measure/configure-analytics/)\ncomponent to track user actions and events. AMP analytics comes with native\nsupport from over 40 analytics vendors. The framework is flexible and allows you\nto measure and trigger URLs using [custom\nconfigurations](//amp.dev/documentation/components/amp-analytics#specifying-configuration-data)\nto send analytics information to your own servers or to vendors where native AMP\nsupport isn't available. If you're using a technology that isn't currently\nsupported, [ask your vendor to add\nsupport](//amp.dev/documentation/guides-and-tutorials/contribute/integrate-your-analytics-tools).\n\nAMP analytics also allows for flexible variable substitution; for details, refer\nto the [variable\nsubstitution](//amp.dev/documentation/guides-and-tutorials/optimize-and-measure/configure-analytics/analytics_basics)\ndocumentation.\n\nStep 3: Enable AMP serving in the Google Ads UI\n-----------------------------------------------\n\nWhile AMP pages in Google Search are\n[auto-discovered](//support.google.com/webmasters/answer/6340290) via the [link\nfrom your\npages](//amp.dev/documentation/guides-and-tutorials/optimize-and-measure/discovery),\nadvertisers must\nexplicitly input the AMP page URL in Google Ads. Read [How to Use AMP with Google\nAds](//support.google.com/google-ads/answer/7495018) for details on\nsetting up AMP URLs in Google Ads UI.\n\n[Cache\nserving](//amp.dev/documentation/guides-and-tutorials/learn/amp-caches-and-cors/how_amp_pages_are_cached)\nis currently available for text ads on Google search results pages served on\nmost major browsers including Android Chrome, Android Google Search App, and\nMobile Safari. We are rolling out more coverage throughout the coming months.\n\nIf you'd like to test how an AMP page appears when delivered from the Google AMP\ncache inside the Google Search Viewer, input your AMP article in the [Search AMP\ntest tool](//search.google.com/test/amp) and click **Preview link**.\n\nAlso, if you'd like to drive Google Ads traffic to your AMP landing page but\ndon't want them to appear in organic search results, add Disallow directives for\nthe relevant AMP pages to your `robots.txt` as you would for any regular web\npage.\n\n### Updating AMP content on landing pages\n\nWhen a user requests an AMP document from the Google AMP Cache, the cache\nautomatically requests updates in order to be able to serve fresh content for\nthe next user once the content has been cached. With this model, updates to AMP\ndocuments propagate automatically and quickly; few users will notice the\nnon-updated version after your update. Additionally, if needed, the\n[update-cache API](/amp/cache/update-cache) can be used to update or remove\ncontent from the AMP cache.\n\nThe AMP project is adding new functionality and components every day. If you\nfind functionality that's missing, you can\n[contribute](https://github.com/ampproject/amphtml/blob/master/README.md) or request\nit to be added by opening a [GitHub\nissue](//amp.dev/documentation/guides-and-tutorials/contribute/).\n\n### Invalid AMP page handling\n\nWhen a page turns invalid, the AMP Cache would discover that within the span of\na few requests and start redirecting to the AMP page served origin. It can take\n1 to 2 days to revert to AMP cache serving."]]
