Fix SEO errors with cache and CDN rules

Example: The CMS is corrected, the audit still sees the old error

The editorial team removes a noindex, but visitors without registration will still receive the old HTML version. Often, logged-in editors will see an uncached preview, while public retrieval comes from a page or CDN cache. This makes the change in the backend more successful than it is public.

Finding the triggering point

Compare a fresh public call with the preview and control cache hit, age, or manufacturer-specific headers. Check the same URL, language, and device configuration. Different parameters can hit a different cache entry and thus simulate an apparent correction.

Checking a limited fix

Empty the affected page and, if necessary, the associated CDN variant. Then correct the disability when publishing if changes regularly become visible too late. For language-dependent or personalized responses, the cache key must take into account the actual relevant distinction.

Check the output after the first call and after another cache hit. Both must provide the same desired meta-data. If only the first call remains correct, the cause lies in the stored object or cache key rather than in the page content.