Use when auditing content pages for freshness signals, setting up HTTP Last-Modified headers in a web server config, or ensuring Article JSON-LD dateModified is updated when CMS content changes.
70
86%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Medium
Suggest reviewing before use
Google's Query Deserves Freshness (QDF) algorithm boosts recent or recently updated content for time-sensitive queries. Missing or stale freshness signals mean your updated content competes without the freshness advantage it deserves.
Last-Modified HTTP response header and include dateModified in Article JSON-LD on all content pagesdateModified only when content substantively changes — trivial edits should not alter the dateFor each article or blog page: (1) Check the HTTP response Last-Modified header — is it set and recent? (2) Check the JSON-LD for a dateModified property in ISO 8601 format. (3) Is a visible 'Last updated' date shown to users? (4) Is the dateModified in JSON-LD consistent with the visible date and the Last-Modified header?
Last-Modified headers based on the file modification time:
add_header Last-Modified $date_gmt;mod_headers is enabled; static files serve Last-Modified automatically.dateModified:
{ "@type": "Article", "dateModified": "2024-11-20T14:30:00Z" }dateModified only when content is substantively changed (not on metadata-only saves).updatedAt field through to the JSON-LD and <time> elements.Google's freshness algorithm (QDF — Query Deserves Freshness) actively boosts recently published or updated content for searches where recency matters. If your dateModified is stale or absent, Google may not credit your content with the freshness it deserves, ranking older competitors above you even after you have updated the article.
Check that the Last-Modified response header is present on article pages. Verify Article JSON-LD includes dateModified in ISO 8601 format. Confirm that the build or deployment system updates dateModified only for content files that actually changed — not a blanket timestamp update on all pages during deploy.
For full implementation details, code examples, and framework-specific guidance,
see references/rule.md.
Rule page: https://frontendchecklist.io/en/rules/seo/freshness
48405aa
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.