← Issues index

40. Premium stories are fully readable on their AMP copies; no paywall, schema says paywalled — Medium (PV, DH)

Added 17 Nov 2026. AMP health check (checks/amp_check/, live 17 Nov 2026) + source audit (PV tpml 70d7bebf, DH tpml-dh 22f4c0f0; @quintype/amp PV 2.22.8, DH 2.17.13).

What: subscription stories (access: subscription) are paywalled on the main article page, but their AMP copy shows the whole story to anyone, with no paywall component. Google serves the AMP copy for most mobile article clicks (#26), so mobile readers from Google Search can read premium stories in full, free, including via Google's AMP cache. The structured data on the same AMP page says isAccessibleForFree: false, with no hasPart / cssSelector showing which part is paywalled.

Evidence (all 8 premium stories in the 17 Nov sample, Googlebot UA; words inside <p> in server HTML; checks/amp_check/amp_check_{pv,dh}_2026-11-17.json, HTML in amp_html_{pv,dh}_2026-11-17/):

Site Template Main page <p> words AMP <p> words AMP paywall script
DH dh-exclusive (2) 0, 0 823, 765 none
DH interview (3) 6–13 1,109–1,178 none
DH syndicated-print (1) 7 534 none
PV pv-exclusive (2) 15, 15 412, 432 none

Cause: @quintype/amp renders its paywall (amp-subscriptions) only when the AMP route options include featureConfig.subscriptions (with the AccessType authorisation URL); otherwise it renders the full body. Neither site passes it: ampRoutes options at PV app/server/app.js:364 and DH app/server/app.js:485. (Library read from the minified dist/index.js by grep; the switch is in the story-body renderer.) Also, PV writes "@productID" instead of productID in isPartOf (PV seo-hard-gate.js:278), which Google will ignore.

Search side: not cloaking (users and Google see the same full AMP text), and the AMP copy is what Google serves for mobile clicks. The issues are (a) premium text given away on AMP, and (b) inconsistent paywall signals: main page near-empty for Google (#9, #1), AMP complete, and schema saying "not free" without marking the paywalled section.

Fix (decide with #26):

  1. If AMP stays: configure featureConfig.subscriptions for AMP (AccessType authorisation / pingback URLs, as Quintype documents for amp-subscriptions) so AMP shows the same preview as the main page, and add hasPart: {"@type": "WebPageElement", "isAccessibleForFree": false, "cssSelector": "<paywalled container>"} on both page types. Ask Quintype for the supported config for each library version.
  2. Quicker alternative: no AMP for premium stories. Omit amphtml when access === "subscription" (custom check around StoryAmpTags, or set the story attribute disable-amp-for-single-story, which makes the AMP route 301 to the main page). ignoreAmpHtmlStoryTemplates alone won't do it, because premium isn't a template.
  3. If AMP is retired (#26), this goes away.
  4. PV: "@productID" → productID.

Verify: AMP copy of a premium story shows only the preview without login (AMP cache URL too); Rich Results Test shows isAccessibleForFree: false with a hasPart selector that matches an element on the page; re-run python -X utf8 checks/amp_check/amp_check.py --site dh and compare AMP <p> words for premium stories.