Dynamic and user‑specific endpoints should not be cached by the browser or at CDN edges in a way that
serves one user’s content to another. Common examples include login pages, cart and checkout flows,
account dashboards, and administrative interfaces. In WordPress, ensure wp-login.php,
/wp-admin/, and AJAX endpoints such as admin-ajax.php are excluded. Some
themes or plugins expose custom endpoints or REST routes that return personalized data; these must be
kept fresh and uncached as well.
Sitemaps and feeds may be updated frequently as content changes, so consider excluding
sitemap.xml, sitemap_index.xml, and /feed/ from long‑term
caching. During development or when using cache‑busting techniques that rely on query strings, avoid
caching raw HTML too aggressively to prevent confusion when templates update. The plugin’s “Prevent
cache” feature allows you to specify filenames or patterns that should always bypass browser caching.
When in doubt, identify pages where immediate consistency matters more than speed—checkout, forms that
change based on user state, dashboards—and prioritize correctness. Safe, targeted exclusions ensure that
performance gains never come at the cost of broken flows or privacy issues.