Why 48 blog posts miss last-modified signals

We tracked a 54-post blog through a technical SEO audit and found 48 posts with no last-modified signal anywhere on the page. No dateModified in frontmatter, none in JSON-LD schema, no visible updated label for readers to check. Missing last-modified dates cost blogs ranking authority and reader trust simultaneously, and the fix is simpler than most people expect.

Quick answer: A last-modified signal is the machine-readable and reader-visible date that tells both search engines and readers when a page was last edited. Without it, Google has no reliable re-crawl trigger and readers have no way to confirm advice is current. Adding dateModified to frontmatter, JSON-LD schema, and a visible label on each post resolves both problems at once.

<script type="application/ld+json">

{

"@context": "https://schema.org",

"@graph": [

{

"@type": "Article",

"headline": "Why 48 blog posts miss last-modified signals",

"datePublished": "2026-09-14",

"dateModified": "2026-09-14",

"author": { "@id": "https://patchment.app/#author" },

"publisher": { "@id": "https://patchment.app/#org" },

"mainEntityOfPage": "https://patchment.app/blog/why-48-blog-posts-miss-last-modified-signals"

},

{

"@type": "Person",

"@id": "https://patchment.app/#author",

"name": "Kien Quoc Ngo",

"jobTitle": "Founder",

"url": "https://patchment.app/"

},

{

"@type": "Organization",

"@id": "https://patchment.app/#org",

"name": "Patchment",

"url": "https://patchment.app/",

"logo": "https://patchment.app/logo.png"

},

{

"@type": "WebSite",

"@id": "https://patchment.app/#website",

"name": "Patchment",

"url": "https://patchment.app/",

"potentialAction": {

"@type": "SearchAction",

"target": "https://patchment.app/?s={search_term_string}",

"query-input": "required name=search_term_string"

}

},

{

"@type": "FAQPage",

"mainEntity": [

{

"@type": "Question",

"name": "Is last-modified different from publish date?",

"acceptedAnswer": {

"@type": "Answer",

"text": "Yes. Publish date is when content first went live. Last-modified is when it was last edited. Search engines use last-modified to decide whether to re-crawl and re-rank. Readers use it to judge whether advice is current."

}

},

{

"@type": "Question",

"name": "Do I need to update every old post to rank better?",

"acceptedAnswer": {

"@type": "Answer",

"text": "No. Updating a post's last-modified date without actual changes is dishonest and search engines penalize it. Update only posts where the information genuinely changed or became outdated. Honest updates signal authority; fake ones signal spam."

}

},

{

"@type": "Question",

"name": "What's the difference between schema markup and visible dates?",

"acceptedAnswer": {

"@type": "Answer",

"text": "Schema markup (dateModified in JSON-LD) tells search engines the date. Visible dates on the page tell readers. Both matter. Schema alone doesn't build reader trust if the page shows no date at all."

}

},

{

"@type": "Question",

"name": "Can I bulk-add last-modified dates to old posts?",

"acceptedAnswer": {

"@type": "Answer",

"text": "Yes, if your CMS tracks edit history. WordPress plugins like WP Last Modified Info pull the actual last-edit timestamp from your database. Don't manually set dates to today if the post hasn't changed since 2021."

}

},

{

"@type": "Question",

"name": "Does last-modified help with E-E-A-T scoring?",

"acceptedAnswer": {

"@type": "Answer",

"text": "Indirectly. Freshness is part of Google's topical authority assessment. A blog that shows current dates and honest update history signals that the author stays current with their field, which feeds into expertise and trustworthiness signals."

}

}

]

}

]

}

</script>

What does a last-modified signal actually do?

A last-modified signal is the date stamp that records when a page was last substantively edited. It is separate from the publish date, which marks when content first went live.

Two things consume this signal. Search engines use it to decide whether to re-crawl a URL. A page with a dateModified value in JSON-LD schema or a fresh Last-Modified HTTP header tells Google's crawler there is new content to index. A page without it gives the crawler no signal, so re-crawl frequency falls. Readers use the visible date to judge whether advice still applies. A post with no date on a fast-moving topic reads as potentially stale within seconds of loading.

The signal lives in three places at once: the HTTP response header, the JSON-LD schema block, and a visible label on the page. Missing any one of them leaves a gap for either the machine or the reader.

Why search engines care about freshness signals?

Search engines weight freshness as a ranking input when query intent carries a time dimension. A search for "best answering service pricing" implies the searcher wants current options, not two-year-old pricing tables.

The practical mechanism is re-crawl scheduling. Googlebot doesn't crawl every URL daily. It uses signals to decide which pages are likely to have changed. A page that has never sent a last-modified signal gets crawled less frequently than one that has. Less frequent crawling means a genuine content update may not appear in search results for days or weeks after the edit is live on the server.

There is a second effect that is less discussed. When Google's quality raters assess topical authority, they look at whether a blog maintains its content over time. A site where most posts carry no update history looks less authoritative than one with an honest maintenance record. That signal is softer than crawl frequency, but it accumulates across an entire domain.

How do you audit your blog for missing dates?

The audit takes three steps.

First, crawl your blog directory with Screaming Frog, Sitebulb, or a simple custom script. Collect the URL, the Last-Modified HTTP response header, the dateModified value from any JSON-LD blocks, and the visible date text from rendered HTML. Export to a spreadsheet. Any row where two or more of those three columns are blank is a gap to fix.

Second, check your CMS's own edit log. WordPress tracks the last edit timestamp in the wp_posts table's post_modified column. Most Markdown-based systems, including Hugo and Astro, expose the file's mtime if you configure the build to use it. That log is the source of truth for honest dates. Don't set dates manually unless you can verify them against actual edits.

Third, prioritize. Posts on time-sensitive topics (pricing, product comparisons, compliance rules) lose reader trust faster when their date is missing. Fix those in the first pass and batch the evergreen ones afterward. A realistic audit of a 50-post blog takes two hours to document and a single session to fix if your CMS supports bulk frontmatter edits.

What happens when readers can't verify when content was written?

Readers apply a fast heuristic on pages with no date: they assume the content is old. That assumption isn't always wrong, but it is always costly.

The reader who can't verify recency either leaves and searches for a dated source, or stays and trusts the content less. Neither outcome serves content you spent time producing.

According to the WP Last Modified Info plugin page on WordPress.org, the plugin has accumulated 40,000 plus active installations. That is evidence of a real behavior: publishers who care about reader trust install dedicated tooling to surface these dates. The installs exist because the problem is common and the cost is visible.

The cost compounds on high-stakes content. A field-service business reading advice about call answering, compliance, or pricing comparisons is making decisions that affect real revenue. If the page carries no date, the reader has no way to know whether the guidance is current. The absence of a date transfers the verification burden entirely to the reader, and most readers won't carry it.

Which WordPress plugins actually solve this at scale?

Three plugins handle last-modified dates for WordPress blogs, and they are not equivalent.

WP Last Modified Info is the most targeted option. It pulls the actual last-edit timestamp from the WordPress database rather than requiring manual date entry. According to a YouTube tutorial on the plugin, "this plugin has uh five star uh ratings and 40,000 plus active installations", which makes it one of the more widely-adopted single-purpose tools in this category.

Rank Math handles it as part of a broader schema package. If you already run Rank Math, you may have dateModified in your Article schema without realizing it. Check the Schema tab before installing a second plugin.

The honest warning: neither plugin retroactively corrects old post dates. They display whatever your database has for post_modified. If a post was created in 2021 and never edited since, the date displayed is 2021. That is correct behavior. Do not use these tools to manufacture recent dates on posts you haven't actually updated.

Does your CMS expose last-modified by default?

Most content management systems track last-modified internally but don't surface it by default.

WordPress stores the value in post_modified from the first edit. Default themes don't display it visibly and don't include it in schema output. A plugin or theme customization is required.

Hugo and Astro can use file mtime as the lastmod value for sitemaps. Astro requires a dateModified field in the content collection schema, populated in frontmatter. Hugo respects a lastmod frontmatter key and can fall back to git commit timestamps with enableGitInfo: true.

Ghost CMS surfaces updated_at natively and includes it in Article schema by default.

Patchment runs its blog on a Markdown system where dateModified is now set in frontmatter on every post. If you're building a content operation for a field-service business, book a demo and we'll walk through the setup as part of onboarding.