How to Fix Content Freshness: Dates, Updates & Last-Modified
A content freshness warning means crawlers found no sign your pages were recently updated. Your pages either mention no recent years or your server sends no Last-Modified header. By the end of this guide you will have refreshed your most important pages, added a visible updated date and dateModified markup, and configured a valid Last-Modified header.

Why it matters
Search engines and AI answer engines prefer sources that look current for time-sensitive queries such as pricing, statistics, how-tos and comparisons. A page with 2021 data and no updated date is less likely to rank or be cited by ChatGPT, Perplexity or Google AI Overviews. Visitors also bounce from pages that look abandoned.
A valid Last-Modified header lets crawlers send conditional requests and recrawl efficiently, and dateModified gives machines an explicit freshness signal they can trust.
What you need
Step-by-step fix
Check headers and dates on your key pages
Run curl against your homepage and 5–10 important URLs to see whether a Last-Modified header comes back. Then open each page and search (Ctrl/Cmd+F) for last year and this year. If you find neither a header nor a recent year, the page reads as stale to crawlers.
for u in https://example.com/ https://example.com/blog/pricing-guide https://example.com/services; do echo "$u"; curl -sI "$u" | grep -i '^last-modified'; done
Pick the pages worth refreshing first
In Google Search Console go to Performance > Search results > Pages, set the date range to the last 12 months and sort by Clicks. Export the top 20. Prioritise pages whose clicks are declining (use Compare mode) and pages with time-sensitive topics such as prices, statistics, tools or regulations.
Update the content itself, not just the date
Make changes a reader would notice:
- Replace old statistics with 2025 or 2026 figures and cite the source and year.
- Swap outdated screenshots for current UI.
- Add a recent example or case study.
- Remove dead links and discontinued products.
- Update the title or H1 year only if the content genuinely covers that year.
<p>According to the Example Co 2026 Benchmark Report, median checkout conversion rose to 3.1% in 2025 (source: example.com/report-2026).</p>
Show a visible 'Updated' date on the page
Add a published and updated date near the H1 in your article or page template. Wrap it in a <time> element with a machine-readable datetime attribute. Show the updated date only when it differs meaningfully from the publish date.
<p class="post-meta">Published <time datetime="2023-05-04">May 4, 2023</time> · Updated <time datetime="2026-03-12">March 12, 2026</time></p>
Add datePublished and dateModified to JSON-LD
Put dateModified in your Article, BlogPosting or WebPage structured data, using ISO 8601 format. It must match the visible updated date. Ideally, generate it from the CMS's last-modified field so it changes automatically.
<script type="application/ld+json">{"@context":"https://schema.org","@type":"Article","headline":"Pricing Guide for Small Businesses","datePublished":"2023-05-04T08:00:00+00:00","dateModified":"2026-03-12T09:00:00+00:00","author":{"@type":"Organization","name":"Example Co"}}</script>Send a valid Last-Modified response header
Static files served by Nginx or Apache get Last-Modified automatically. Dynamic pages (PHP, Node, most CMSs) usually do not, so set the header from the content's real modification time. Format it as an RFC 7231 HTTP date in GMT.
On Nginx, sub_filter and SSI drop the header unless you enable it explicitly.
<?php
// $post_modified_ts = Unix timestamp of the page's last real edit
header('Last-Modified: ' . gmdate('D, d M Y H:i:s', $post_modified_ts) . ' GMT');
# Nginx: keep the header when using sub_filter / SSI
# location / { sub_filter_last_modified on; ssi_last_modified on; }Update the sitemap lastmod and request recrawl
Make sure each refreshed URL's <lastmod> in sitemap.xml matches the new modification date. Then resubmit the sitemap in Search Console under Indexing > Sitemaps. For your most important pages, use URL Inspection > Request indexing.
<url><loc>https://example.com/blog/pricing-guide</loc><lastmod>2026-03-12</lastmod></url>
Verify the fix
Re-run curl and confirm a Last-Modified header with a recent date. View the page source and confirm the page text contains last year or the current year, and that dateModified appears in the JSON-LD. Test one URL in Google's Rich Results Test, then re-run the site audit.
curl -sI https://example.com/blog/pricing-guide | grep -i last-modified # Expected: Last-Modified: Thu, 12 Mar 2026 09:00:00 GMT
Platform-specific notes
WordPress
Most themes can show the modified date through the_modified_date(). Yoast SEO and Rank Math add dateModified to their schema and lastmod to sitemaps automatically. WordPress does not send a Last-Modified header for pages by default. Add it with a small plugin that hooks the 'wp' action and calls header() with get_post_modified_time('U', true). Some caching plugins, such as WP Rocket and LiteSpeed Cache, can also preserve it. Check after purging the cache.
Shopify
You cannot set custom response headers on storefront pages. Rely on visible dates and markup instead. In blog templates (main-article.liquid), output {{ article.updated_at | date: '%B %-d, %Y' }} and add dateModified using {{ article.updated_at | date: '%Y-%m-%dT%H:%M:%S%z' }}. Product and collection pages need recent-year references in their content, such as '2026 collection' or current reviews.
Next.js
In the App Router, set Last-Modified from a Route Handler or middleware via the headers on NextResponse. Static paths can also use the headers() option in next.config.js, though that value is fixed. Hosting on Vercel serves cached ISR pages with its own headers, so confirm Last-Modified survives with curl. Use generateMetadata or a JSON-LD script tag for dateModified.
Cloudflare
Cloudflare normally passes through the origin's Last-Modified header. Features that rewrite HTML, such as Email Obfuscation or some Workers transforms, can strip it or weaken validators. Test with curl against the public URL, not just the origin. After a refresh, purge the cache for that URL under Caching > Configuration > Purge Cache > Custom Purge.
Wix / Squarespace / Webflow
These hosted platforms control response headers, so focus on content signals. Enable the blog post 'last updated' or date display in the post template. In Webflow, bind a CMS Date field (e.g. 'Updated on') to a text element and to dateModified in a custom code embed. Make sure refreshed pages mention current-year data.
Check that it worked
✅ How to verify
- Run curl -sI on several key URLs and confirm a parseable Last-Modified header in GMT format.
- Search the rendered page text for the current or previous year and confirm it appears in genuine updated content.
- Paste a refreshed URL into Google's Rich Results Test and confirm dateModified is detected with the correct value.
- Re-run the site audit and confirm the content freshness check passes, with pages referencing last year or later.
⚠️ Common mistakes
- Bumping the visible date or the year in the title without changing the content. Google may ignore it, and readers notice.
- Setting Last-Modified or dateModified to the current server time on every request, which makes the signal meaningless and breaks caching.
- Adding the header at the origin but having it stripped by Nginx sub_filter, a CDN or a caching plugin. Always test the public URL.
- Letting sitemap lastmod, the visible date and dateModified disagree. Keep all three in sync from one source field.
Is this still an issue on your site? Run a free audit — ZORO checks this and 294 other SEO, AI-visibility, accessibility and security signals, with fixes for your platform.
Check my site freeFAQ
How often should I update old blog posts?
Review high-traffic and time-sensitive pages every 6–12 months, and evergreen reference pages at least yearly. Update immediately when prices, laws, product UIs or key statistics change.
Does changing the date on a post help SEO?
Only when it reflects real changes. Google compares visible dates, structured data and content changes. A new date on unchanged content gives little benefit and can reduce trust.
Should I show the published date or the updated date?
Show both if you can. Many sites show only the updated date for evergreen guides. Whichever you show must match datePublished and dateModified in your structured data.
What is the Last-Modified header and do I need it?
It is an HTTP response header giving the time a resource last changed, e.g. 'Last-Modified: Thu, 12 Mar 2026 09:00:00 GMT'. Crawlers use it with If-Modified-Since to recrawl efficiently. It is not required to rank, but it is a reliable machine-readable freshness signal.
How to Fix a Low Readability Score (Flesch Reading Ease)
How to Fix Duplicate Content Across Pages on Your Website
How to Fix Long Paragraphs So Your Pages Are Easy to Scan
How to Fix Thin Content: Expand or Merge Pages Under 300 Words
How to Fix Spelling and Grammar Errors on Your Website
How to Fix Missing Video Entries in Your XML Sitemap