Checks / Links, canonical and speed
Public page cannot be cached
The page is open to everyone but is sent with Cache-Control private or no-store (or sets a cookie), so a CDN cannot serve it from cache. Every visit, and every crawler request, hits your server, and cold pages answer slowly.
public_not_cacheable · Links, canonical and speed · Notice
What triggers it
A page's Cache-Control header says no-store or private, or the page sets a cookie of its own (cookies set by a CDN or load balancer in front of it do not count).
What to change
Send Cache-Control: public with a max-age (and s-maxage for a CDN) on pages that are the same for everyone, and keep cookies off them.
Example
Response headers to add on your server or CDN:
Cache-Control: public, max-age=300, s-maxage=3600How to confirm the fix
- Run curl -sI <url> | grep -i -E 'cache-control|set-cookie': public with a max-age, and no cookie
- Press 'Re-check 1 page'
How common it is
In the audits of our own sites on 26 Oct 2026 (4 sites): finding judged right on citedby.eu, resaleiq.dev.
Source: finding audit 2026-10-26 (English).
About this check
| Check ID | public_not_cacheable |
|---|---|
| Report section | Links, canonical and speed |
| Severity | Notice |
| How it is decided | Measured: read directly from the page or the server's response. |
| Added | Version 9, 24 October 2026 |
| Status | Measured in every report |
| Report gives the code | No, the fix is described in words |
Related checks
- Indexable page missing from the sitemap
- Links to addresses that have moved
- Render-blocking scripts and styles
- Security headers missing
See whether it applies to your site
Paste your address and we crawl up to 10 pages and show every issue we find, with its fix. No account, no card.
Every plan crawls up to its page limit and lists these checks with the fix: plans.
How an audit works: method