← Issues index

26. PV AMP copies take ~46% of successful crawl — keep or retire AMP — High (PV), decision (raised 16 Nov 2026)

⚠️ Corrected below (AMP traffic, 16 Nov 2026): page-level /amp/ counts under-state AMP traffic, because Search Console usually credits AMP clicks to the canonical URL. Use the search-appearance figures. Step 1 done (16 Nov 2026): for stories published 7 Sep – 5 Nov 2026, AMP URLs earned 18,011 of 896,806 web clicks (2.0%), 8,692 of 18.6M Discover clicks (0.05%) and 153 Google News clicks (Search Console page-level, 7 Sep – 13 Nov 2026; checks/traffic_funnel/report_pv_2026-11-13.md). AMP costs ~46% of successful crawl for ~2% of new-article search clicks: retire it after #1 has been live ~4 weeks.

Added 12 Nov 2026. Not a bug: a decision to make after #1 ships.

Current AMP traffic (last 28 days, 20 Oct – 16 Nov 2026, before #1 reached Google; Search Console search appearance + GA4; checks/amp_check/amp_traffic_{pv,dh}_2026-10-20_2026-11-16.json). Clicks Google served as AMP:

PV DH
Web (AMP_TOP_STORIES + AMP_BLUE_LINK) 240,559 of 3,359,126 (7.2%) 429,995 of 1,295,268 (33.2%)
Discover (AMP_TOP_STORIES) 17,150 of 7,954,006 (0.2%) 139,534 of 7,485,188 (1.9%)
Google News none none
All three 257,709 of 11.32M (2.3%) 569,529 of 9.21M (6.2%)
GA4 sessions landing on /amp/ 162,182 of 10.70M (1.5%); 2.7% of Organic Search 521,258 of 12.42M (4.2%); 6.1% of Organic Search

Decision waits on #1 (confirmed 19 Nov 2026), and why:

  1. PV: the AMP copy is today the only copy with the full text in server HTML, and Google serves it for ~96% of mobile article web clicks. Retiring AMP before #1 would move that traffic onto pages Google reads without body text (#2: ~76% of PV articles indexed without it).
  2. Attribution: #1 and an AMP change both shift what Google crawls and serves; doing them in the same window makes neither measurable.
  3. What #1 changes for this decision: once main pages carry the body, AMP no longer adds content, so the only question left is traffic risk vs crawl cost.

What: every PV article exists twice: the main page (indexed) and an AMP copy at /amp/story/<section>%2F<slug>-<id>, announced by <link rel="amphtml"> on the main page. The AMP copy's canonical points to the main page, so it is not indexed as a duplicate, but Googlebot fetches it.

Evidence

Not part of this: PV's amphtml link uses %2F, but on PV that URL returns 200 directly (no redirect, unlike DH before its #14 fix), so changing it to plain slashes saves nothing. ⏸️ Keep it on hold; it becomes moot if AMP is retired.

Plan

  1. Now (read-only): measure traffic that still arrives through AMP: Search Console search-appearance "AMP" clicks/impressions per site (web, Discover, News), last 3 months; GA4 sessions on /amp/ pages.
  2. Ship #1, wait ~4 weeks, recheck body indexing (#2: checks/body_index_check/) and crawl (#3: Crawl stats). Don't change AMP in the same window, so effects can be attributed.
  3. Decide: keep AMP, or retire it if AMP traffic is small.
  4. If retiring: remove the amphtml link from article pages; 301 every /amp/story/… URL (encoded and plain forms) to its main page; keep the redirects permanently; check mobile speed of main pages first (#5); watch Discover/News traffic and Crawl stats for 4 weeks. Same for DH if its numbers look similar.

Verify (if retired): amphtml absent from article HTML; AMP URLs 301 to the article in one hop; Crawl stats 200 samples no longer dominated by /amp/story/; crawl of main pages per new article rises.

16 Nov 2026, DH too: in the DH "By file type → HTML" sample (12 Nov 2026, crawl_stats/2026-11-16/dh-html/Table.csv) 491 of 986 HTML fetches (50%) are /amp/story/…; PV 441 of 991 (45%). AMP copies take about half of Googlebot's HTML fetches on both sites.

Why AMP takes ~half of Googlebot's HTML fetches (code + live check, 16 Nov 2026):

Options (decide after #1 has been live ~4 weeks, as planned):

  1. Retire AMP: remove StoryAmpTags from generators on both sites; 301 /amp/story/… to the article (keep permanently).
  2. Middle ground, PV first step (after PV #1 is live): ignoreAmpHtmlStoryTemplates: ["visual-story", "syndicated-print"] in the SEO config, so print copies (79% of PV output, little traffic) lose their AMP copy while other templates keep it; 301 their AMP URLs. Roughly removes most PV AMP crawl with one config line.

AMP traffic, measured properly (16 Nov 2026; Search Console search appearance and GA4, 16 Aug – 13 Nov 2026; checks/traffic_funnel/amp_traffic_gsc_2026-11-13.json, amp_traffic_ga4_2026-11-13.json). Clicks Google served as AMP:

PV DH
Web (AMP_TOP_STORIES + AMP_BLUE_LINK) 946,321 of 12,904,219 (7.3%) 1,310,275 of 4,495,898 (29%)
Discover (AMP_TOP_STORIES) 242,252 of 28,536,333 (0.85%) 649,435 of 24,550,565 (2.6%)
Google News none none
All three ≈1.19M of 41.5M (2.9%) ≈1.97M of 30.3M (6.5%)

Why DH has more AMP traffic (16 Nov 2026; Search Console web, 16 Aug – 13 Nov 2026; checks/traffic_funnel/amp_share_context_2026-11-13.json): traffic mix, not a technical difference. Only articles have AMP copies, and Google serves AMP to mobile users. PV: 98% of web clicks are mobile but only 10% land on articles (1.53M of page clicks; the rest is home, cartoons, e-paper and listings from branded searches); DH: 85% mobile and 53% on articles (2.28M). Among mobile article clicks, AMP-served clicks are ≈87% on PV (946K of 1.08M) and ≈97% on DH (1.31M of 1.35M) (approximate: search-appearance and page-level clicks are counted slightly differently). So wherever an AMP copy exists, Google serves it for nearly every mobile article click on both sites: retiring AMP moves almost all mobile article search traffic onto the canonical pages, which is why #1 must ship first (PV) and DH must be staged.

AMP health check: no defect stops Google serving AMP (17 Nov 2026; checks/amp_check/amp_check_{pv,dh}_2026-11-17.md). Asked because other vernacular publishers report ~30% of traffic from AMP. Sample: 4 stories per template (top-2 by web clicks + 2 random), DH 62 stories / 17 templates, PV 68 / 17, live as Googlebot plus Search Console URL Inspection.

Page indexing export (18 Nov 2026; checks/index_coverage/summary_{pv,dh}_2026-11-18.md): "Alternate page with proper canonical tag" is the largest not-indexed reason on both sites and is almost all AMP: PV 1,328,617 pages (95% of a 1,000-URL sample are /amp/story/…), DH 1,255,065 (99%). Expected for AMP (canonical to the article), but it is the size of the duplicate set Google keeps re-crawling. PV's count grew by 114,586 in 85 days (≈ one AMP copy per new story); DH's is flat.