AMP (Accelerated Mobile Pages)
Google's open-source framework for creating fast-loading mobile web pages with restricted HTML/JS.
What is AMP?
AMP (Accelerated Mobile Pages) is an open-source HTML framework developed by Google for creating web pages that load extremely fast on mobile devices. AMP achieves this speed by restricting certain HTML, CSS, and JavaScript features, pre-rendering content through Google's AMP Cache CDN, and enforcing performance best practices at the framework level. AMP pages use custom components (amp-img, amp-ad, amp-video) instead of standard HTML elements.
AMP's importance in the publisher ecosystem has diminished significantly since 2021. Google removed the AMP requirement for the Top Stories carousel and confirmed that AMP is not a ranking factor — Core Web Vitals apply equally to AMP and non-AMP pages. Many major publishers have migrated away from AMP, finding that well-optimized standard pages achieve comparable performance without AMP's restrictions.
Why It Matters for Publishers
While AMP's strategic importance has waned, many publishers still use it, and understanding its trade-offs is relevant. AMP pages are inherently fast (typically achieving excellent Core Web Vitals scores), which can benefit publishers struggling to optimize their standard pages. However, AMP's restrictions limit ad format options, header bidding implementations, and overall monetization flexibility.
AMP pages typically earn 20-40% less ad revenue than well-optimized non-AMP pages because of limited ad formats, fewer demand sources, and restrictions on JavaScript-heavy ad technologies like header bidding. Publishers who invested heavily in AMP should evaluate whether migrating to optimized standard pages could increase revenue while maintaining performance.
Tips for Optimization
- Evaluate AMP ROI: Compare the revenue per session of AMP pages versus non-AMP equivalents. If the revenue gap is significant, consider migrating to optimized standard pages.
- Use amp-ad properly: If maintaining AMP, use the amp-ad component with Real Time Config (RTC) for header bidding-like functionality. This improves AMP ad revenue compared to single-network setups.
- Implement proper canonical tags: Ensure AMP pages use rel="canonical" pointing to the standard page version, and standard pages use rel="amphtml" pointing to the AMP version if both exist.
- Consider AMP-to-standard migration: If your standard pages can achieve comparable Core Web Vitals scores, migrating from AMP can unlock significantly more ad revenue through unrestricted header bidding and ad format options.