Finding Out When a Page Was Last Updated
Enter a URL and this tool reads what the page reports about its own age: the Last-Modified HTTP header, the article:modified_time and article:published_time meta tags, itemprop dateModified and datePublished, and the first <time> element on the page. It shows each signal it finds, picks the most authoritative one, and works out how many days ago that was.
If a page sends no date signal at all, the tool says so. A missing date is not the same as a stale page — it just means the page does not tell anyone.
How to Use This Tool
Enter the page URL
Articles and blog posts carry the most date information; homepages often carry none.
Read each signal
The HTTP header, the modified and published meta tags, and any visible <time> element are listed separately.
Check the best-known date
The tool prefers the Last-Modified header, then the modified tag, then the published tag, and shows which it used.
Sanity-check it
If the date is today on a page you know is old, the server is generating it on every request — see below.
Where a Page's Dates Come From
- Last-Modified header — sent by the server with the response. Accurate for static files; often meaningless for dynamic pages.
- article:modified_time and article:published_time — Open Graph meta tags that many CMSs and SEO plugins add to posts.
- itemprop="dateModified" and "datePublished" — schema.org Microdata. The same fields in JSON-LD Article markup are not read here; the Schema Markup Validator shows those.
- A <time datetime> element — the machine-readable version of a date shown on the page, such as a byline.
- The XML sitemap's <lastmod> — not read by this tool, but checked by search engines alongside the page itself.
Why the Date Is Sometimes Today
Many sites build each page when it is requested — WordPress, most CMSs, and server-rendered apps. Some of them send a Last-Modified header set to the moment the response was generated, which makes every page look brand new every time you check.
When the header says today and the meta tags say something older, trust the meta tags. When there are no tags and only a today's-date header, the honest answer is that the page does not say when it was changed.
Other Ways to Check When a Page Was Updated
- Look for a visible “updated” or “published” date near the headline or at the end of the article.
- View the page source and search for dateModified, datePublished or modified_time.
- Check the Wayback Machine at archive.org to compare snapshots of the page over time.
- Search Google for the URL; results sometimes show a date next to the snippet.
- Check the site's XML sitemap for the page's <lastmod> value.
Does Google Use Content Freshness as a Ranking Factor?
For some queries, yes. Google has described a “query deserves freshness” approach for searches where recent information matters — news, events, fast-changing topics and annual “best of” lists. For those, a recently updated page has an advantage.
For evergreen reference content, an accurate old page is not penalised for its age. A page quietly kept accurate does not need a new timestamp to rank.
What does hurt is the opposite: a visibly recent date on content that was not meaningfully changed. Google has said it tries to detect this, and readers notice too.
If Your Page Sends No Freshness Signal
- Add dateModified and datePublished to your Article structured data, and article:modified_time to your meta tags, when you genuinely update a page.
- Show the updated date visibly on the page as well, so readers and search engines see the same thing.
- Make sure your server or CMS sends a Last-Modified header that reflects real content changes, not the time of the request.
- Keep the sitemap's <lastmod> in step with real updates — the Sitemap Generator can read lastmod values from your live pages.
When to Refresh Old Content
Prioritise pages that used to earn traffic and are slipping, and pages on topics where facts, prices, laws or products change. The GSC Quick-Win Analyzer finds pages ranking just off the top positions, which are often the best candidates for an update.
A real refresh means checking every fact, updating examples and screenshots, adding what is now missing and removing what is no longer true. Then update the date — not before.
Frequently Asked Questions
How can I tell when a web page was last updated?
Check for a visible updated date first, then the page's metadata: the Last-Modified header, article:modified_time tags and dateModified in structured data. This tool reads all of those at once. The Wayback Machine shows historical snapshots if the page has none.
Should I fake a recent modified date to look fresh?
No. Changing the date without meaningfully changing the content goes against Google's guidance, is easy to detect, and can undermine trust in all of your dates once noticed.
Why does the Last-Modified header show today's date?
The server is generating the page on every request and stamping the header with the current time. It tells you nothing about when the content changed; use the meta tags or structured data instead.
Why does Cache-Control matter here?
Aggressive caching can mean a stale copy is served for a while after the content changes, so the reported Last-Modified header can lag behind the real update.
Does updating the date improve rankings?
Not on its own. For freshness-sensitive queries, genuinely updated content can help. Changing only the date does not, and may backfire.
Related Tools
Sitemap Generator
Keep lastmod dates consistent with your page's real update history.
HTTP Header Checker
Full review of a page's caching and response headers.
GSC Quick-Win Analyzer
Find older pages worth refreshing based on real Search Console data.
Schema Markup Validator
Validate dateModified and datePublished structured data.