CrawlCheck
Glossary · Delivery and rendering

edge cache pinning

A cached response continuing to be served after the origin has changed.

What edge cache pinning does not show

A purge API returning 200 is a statement about the API call, not evidence that anything was evicted.

How CrawlCheck measures edge cache pinning

2 finding codes measure it. Each one’s share of all scans is computed from the live corpus when this page is served, not typed into it.

Finding codeShare of scansGuide
CHALLENGE_PINNED_AT_EDGE0.4%Is Cloudflare blocking AI crawlers on your site? What changes on 15 September 2026
MACHINE_FILE_CACHE_SPLIT0.1%Does llms.txt actually do anything?

Every code, its rule and its current rate: the dataset page. Scan a site to see which apply to it.

Where edge cache pinning comes up on this site

Related terms in Delivery and rendering

What arrives on the wire, and what only exists after something else runs.

payload ratio · render dependence · render dependence gap · TTFB · Core Web Vitals · CrUX · field data · prompt injection · Hydration mismatch · Dynamic rendering · DOM depth · Edge transformation · 202 interstitial · rate limiting · bot management platform

Questions about edge cache pinning

What is edge cache pinning?

A cached response continuing to be served after the origin has changed.

What does edge cache pinning not show or guarantee?

A purge API returning 200 is a statement about the API call, not evidence that anything was evicted.

How does CrawlCheck measure edge cache pinning?

Through the finding codes CHALLENGE_PINNED_AT_EDGE, MACHINE_FILE_CACHE_SPLIT, each with a stated rule, evidence bytes and a live share of scans on the dataset page.

Which area of the glossary does edge cache pinning belong to?

Delivery and rendering: What arrives on the wire, and what only exists after something else runs.

← render dependence gap  ·  TTFB →

See it in the full glossary · 731 terms across 19 areas.