How to check when a website was last updated (6 methods that work)
PageWatch team · November 12, 2026 · 4 min read
Short answer: There's no single field that reliably says when a page was last changed. Check, in this order: a date shown on the page itself, the page's structured data or meta tags, the site's sitemap (<lastmod>), the Last-Modified HTTP header, and the Wayback Machine's captures. Each can be missing or misleading, so compare two of them. If you need to know about the next update, monitor the page instead of guessing.
Method 1: Look for a date on the page
Articles, policies and documentation often show "Last updated" or "Effective" near the top or bottom. It's the easiest signal and the one the publisher chose to show you. The catch: it's set by hand or by a template, so it can be stale, or it can update when nothing meaningful changed.
Tip: on long policy pages, search the page (Ctrl/Cmd + F) for "updated", "effective" or "revised".
Method 2: Read the page's metadata
Open the page source (right-click → View page source) and search for:
dateModifiedin JSON-LD structured data (common on articles),article:modified_timein meta tags,- dates in the page's URL or in its feed.
These are machine-readable versions of the same publisher claim, often more precise (with time) than the visible date.
Method 3: Check the sitemap
Most sites publish a sitemap at /sitemap.xml (or list it in /robots.txt). Each entry can include <lastmod>. The sitemaps protocol says this date should be "the date the linked page was last modified, not when the sitemap is generated", and that <lastmod> is optional. In practice some sites regenerate every date on every deploy, so a sitemap full of today's dates tells you little.
Method 4: Look at the Last-Modified header
Servers can send a Last-Modified response header. MDN describes it as the date and time "when the origin server believes the resource was last modified", less accurate than an ETag and usable as a fallback.
To see it, open your browser's developer tools → Network, reload, click the page request and look under Response Headers. Or from a terminal:
curl -sI https://example.com/page | grep -i last-modified
Limits: dynamic sites often don't send it, or send the current time on every request because the page is generated on the fly.
Method 5: Compare Wayback Machine captures
On web.archive.org, enter the address and open captures from different dates. If two consecutive captures differ, the page changed between those dates. It gives you a window, not an exact time, and depends on how often the page was crawled. The Archive notes a 3–10 hour lag before new crawls appear, and some pages are never captured (robots.txt exclusions, owner requests, script-heavy pages).
More on this in our guide to Wayback Machine alternatives.
Method 6: Ask the site or check its changelog
Product sites often keep a changelog or release notes; policy pages sometimes keep a version history. For anything with legal weight, ask the publisher for the dated previous version.
Which method to trust
| Method | Reliability | Precision | When it fails |
|---|---|---|---|
| Date on the page | Medium | Day | Template dates, forgotten updates |
| Structured data | Medium | Minute | Copied from the visible date |
| Sitemap lastmod | Low to medium | Day or minute | Regenerated on every deploy |
| Last-Modified header | Low on dynamic sites | Second | Sent as "now" or missing |
| Wayback captures | High for "it changed" | Between captures | Page rarely crawled |
| Your own monitoring | High | Your check interval | Only from the day you start |
The best evidence is two independent signals that agree: for example, a visible "updated" date that matches the window between two Wayback captures.
Know about the next update automatically
All six methods look backwards. If what you actually want is to know when the page changes next (a policy you depend on, a product page, a careers page), set up a monitor. PageWatch reads the page on a schedule, compares it with the previous version and emails you the lines that changed, optionally only when the change matches what you care about. You can also point it at just one part of the page with a CSS selector so date stamps elsewhere don't count.
Common mistakes
- Trusting the copyright year in the footer. It often updates automatically every January.
- Reading "updated" as "changed meaningfully". Small edits can bump the date.
- Taking the HTTP header at face value on a site that builds pages on every request.
- Checking only once. A single look tells you about the past, not about the change you're waiting for.
FAQ
Can I find the exact time a page changed? Only if the publisher records it, or if you were monitoring it when it changed.
Does Google show when a page was updated? Sometimes a date appears next to a result, but it's an estimate taken from the page; check the page itself.
How do I check many pages at once? Look at the site's sitemap, or monitor the pages that matter with a tool like PageWatch.
Sources
- MDN Web Docs: Last-Modified header (read 13 Nov 2026)
- sitemaps.org: Sitemaps XML format (read 13 Nov 2026)
- Internet Archive Help Center: Using the Wayback Machine (read 13 Nov 2026)