Verify --prod on Cloudflare (Measurement D)

This proof note records one production path on rendershield.dev/docs/quickstart.

It is an infrastructure verification log, not a ranking or traffic case study.

Before (earlier measurement state)

Earlier production checks had two blockers:

  1. Human canonical request handling still normalized through redirects.
  2. Published verifier defaults did not yet include HowTo in the allowlist.

Representative request evidence from the trail:

curl -sS -D - -o /tmp/quickstart-bot.html \
  -A 'Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)' \
  'https://rendershield.dev/docs/quickstart' \
  | rg -i 'HTTP/|x-rendershield:'

Observed in the trail:

HTTP/2 200
x-rendershield: bot-hit

The routing header was correct, but full production verification still failed until the published package behavior matched the page contract.

After Measurement D

After publishing @lownoise-studio/[email protected], production verification passed with the same live route:

rendershield verify --prod https://rendershield.dev/docs/quickstart

Observed outcome in Measurement D:

One lesson learned

Treat route behavior and validator defaults as a single contract.

If the live HTML shape (for example HowTo JSON-LD) and the published verifier allowlist diverge, production checks can fail even when bot routing is correct.

Related pages