Skip to content

No freshness signal (no published/updated date, schema date, or Last-Modified)

A freshness signal is any way a page tells crawlers or AI systems when it was published or last updated, whether that's a visible date on the page, a datePublished/dateModified field in schema, or a Last-Modified value in the server's HTTP response headers. This check found none of those three signals present on a page that otherwise reads as content, so its age is genuinely unknowable from the outside. AI engines deprioritise content they can't date, since they have no way to judge whether it's still accurate, especially for anything time-sensitive like pricing, statistics or industry news. Even genuinely fresh, well-maintained content gets treated as suspect simply because there's no evidence of when it was written or last checked. Your content team needs about 30 minutes per page. Show a visible 'Last updated' date on the page itself, add datePublished and dateModified to the page's schema, and confirm your server sends a Last-Modified HTTP header, ideally reflecting the actual last edit rather than a build timestamp.

Why this matters

AI engines deprioritise content they can't date, since they have no way to judge whether it's still accurate, especially for anything time-sensitive like pricing, statistics or industry news. Even genuinely fresh, well-maintained content gets treated as suspect simply because there's no evidence of when it was written or last checked.

How to fix it

Your content team needs about 30 minutes per page. Show a visible 'Last updated' date on the page itself, add datePublished and dateModified to the page's schema, and confirm your server sends a Last-Modified HTTP header, ideally reflecting the actual last edit rather than a build timestamp.