AMP's privileged position in Google Search ended years ago, and many publishers have sunset their AMP templates. Yet AMP pages still drive meaningful traffic for some news and reference sites — and monetizing them properly remains its own discipline.
Why AMP monetization underperforms
AMP's restricted JavaScript model means no full Prebid.js in the page. Ads load through the amp-ad component, with header-bidding-style competition only via Real Time Config (RTC) — which allows a limited number of server-side bid calls (historically five) per slot. Fewer bidders, server-side match rates, and stripped-down formats generally mean AMP CPMs run 20–40% below the equivalent canonical page.
Doing it properly anyway
- Use RTC with a server-side bidding endpoint (Prebid Server or your partner's) to bring real competition to amp-ad.
- Mirror your floors: AMP inventory needs its own floor curve, not your desktop one.
- Sticky and flying-carpet AMP formats lift viewability within AMP's rules; use them where UX allows.
- Keep ads.txt consistent — AMP cache serving still resolves authorization against your domain file.
- Measure AMP separately end-to-end. Blended reporting hides AMP's true RPM and the comparison you actually need: AMP RPM vs canonical-page RPM on the same content.
The strategic question
For most publishers the decision is now traffic math: if AMP still delivers a large share of search/Discover sessions, monetize it seriously. If AMP has dwindled below ~10–15% of sessions, the engineering cost of maintaining a second template usually beats the revenue — sunset it with proper redirects and let your faster canonical pages (with full header bidding) take over. Run the numbers per site; sentiment about AMP, in either direction, is not a strategy.
See what your inventory is really worth
Get a free revenue audit — we'll benchmark your floors, demand mix and layout against your vertical.
Request Free Audit