An agent fetches the CDN edge response, not the origin's latest page. Long-term caching of whole HTML pages containing prices, or a landing page reached only through a chain of 301/302s, makes agents read stale content or give up when redirect following is limited.
Set cache policy by content type: short cache with validation for HTML carrying price and stock, long cache with content fingerprints for static assets. Keep redirect chains to a single hop and point canonical at the final address. After changes, spot-check status codes and headers with script-disabled requests to confirm the edge serves the intended version.
Caching and redirects are config-layer changes — cheap and often edited. Log each with its date in the definition changelog. This article covers crawlability and response semantics only, endorses no CDN provider and issues no verdict on any single edge hit.