Map the cache layers and owners
Know which system can return stale content.
Use this for: Public pages and their required resources within the sampled template or URL group.
List browser caching, CDN edge caching and any application cache that affects public pages. Ask the platform owner which rules are active rather than assuming the provider defaults apply. Record who can safely change a rule or purge a resource.
Compare the same URL and intended public state. Record a short finding only if it helps you or the person making the fix; no screenshot or evidence upload is required to complete this checklist.
Hypothetical example: A CMS update is correct at the application but an edge rule still serves the previous HTML.
- Identify the hosting and CDN provider.
- Ask which public responses are cached.
- Find the owner for rules and invalidation.
More help and optional notes
Before you begin: Permission to inspect the relevant site or diagnostic account.
If it fails: Create a short cache map with the developer or host.
Retest: Repeat the same comparison after the change, then check another URL using the same template or rule.
Not applicable: The tested feature or response variant does not exist.
Keep in mind: A passing sample does not establish that every URL behaves correctly or guarantee indexing.
Optional: URL, time, expected result, observed result and next action. Keep confidential data out of shared exports.
Changing this result updates your checkmark and progress immediately. Notes are optional.

