CONTENT_FRESHNESS_UNKNOWN

Content freshness is unknown

No automatic fix — this needs a manual change on your site

What this check looks at

Whether any JSON-LD on the site declares `dateModified` or `datePublished`. Only checked once the site has some JSON-LD at all — a site with none is already flagged by JSON_LD_MISSING. Deliberately does not look at HTTP Last-Modified headers, which are an unreliable freshness signal in practice.

Why AI answer engines care

Without a dated JSON-LD signal, an AI assistant has no way to judge how current the content is and has to treat it as unknown rather than confidently recent.

Does Synviber fix it for me?

Not currently — this one needs a manual change on your own site or infrastructure; Synviber can detect it but does not publish an automatic fix for it today.

How to fix it manually

Low severity

Scanner message: "JSON-LD does not declare dateModified/datePublished, so AI assistants have no signal for how current this content is"

Add a `dateModified` (or `datePublished`) field with the real last-edited date to your JSON-LD, so AI assistants can judge content freshness instead of treating it as unknown.

← Back to all issues