How To Check When a Website was Last Updated

The fastest way to check when a website was last updated is opening your browser console and typing document.lastModified. For a more thorough check, view the page source and search for “modified” in the meta tags, or check the HTTP response headers in your browser’s developer tools.

Australian businesses change their hours or pricing all the time without touching their website. If you rely on what’s there without checking, you might drive to a shop that’s moved or quote a price that’s two years old.

Quick-Reference Comparison Table

Why It Matters to Know When a Website Was Last Updated

The older a page is, the less you should trust it. A medical article from five years ago might recommend something that’s since been revised. Tax rules in Australia shift every financial year, so a guide that hasn’t been touched could steer you toward wrong deductions or missed deadlines.

Accuracy of Business Information

Old websites love to show you phone numbers that have been disconnected or street addresses for shops that moved two suburbs over. If you’re a local customer trying to actually visit, that’s a wasted trip.

Pricing goes stale fast too. A site that hasn’t been touched in years will quote figures that have nothing to do with what things cost now.

Security and User Safety

Websites that don’t get regular updates are sitting ducks for hackers. Outdated plugins and old software versions are the first things attackers go after.

If you can see that a site hasn’t been updated in ages, there’s a fair chance nobody is watching the security side either. Expired certificates and missing encryption are common on neglected sites.

• Are their products or services still available?
• Is the business still operating?
• Can you trust the information in their articles and guides?
• Has anyone done security maintenance recently?

How to Check the Website Footer

Scroll to the bottom of most websites and you’ll find a copyright notice. It usually has a year or year range next to the business name.

If the footer shows the current year, the site owner might have logged in recently. Might. Plenty of themes update that number automatically on 1 January, so it proves nothing on its own.

The Copyright Date Limitation

A copyright date doesn’t tell you the content is fresh. It’s a rough sign of life, nothing more. If the footer says 2019, the site is almost certainly abandoned.

Manual Update Stamps

Some sites spell it out for you with a line like “Page last reviewed on 15 May 2025”. You’ll see this most often on medical or legal websites where accuracy matters.

If it’s there, great. It’s the most straightforward date you’ll find as a visitor. Just remember the site owner is self-reporting, so take it at face value.

How to Check the Page Source Code

You can look behind any webpage to find dates hidden in the code. Right-click anywhere on the page and select “View Page Source”. You can also press Ctrl+U on Windows or Command+Option+U on a Mac.

Searching for Meta Tags

Once the source code is open, press Ctrl+F (or Command+F on Mac) and type “modified” into the search bar. A lot of content management systems drop a last-modified date into the meta tags.

Look for lines that mention article:modified_time or article:published_time. These are Open Graph tags, and the date will be in ISO 8601 format (YYYY-MM-DD). Most CMS platforms put their update timestamps here.

• Open the page source code in your browser
• Search for “date” or “modified”
• Look for the ISO 8601 format (YYYY-MM-DD)
• Compare the date against the content on the page

Checking Structured Data

A lot of websites include structured data (also called schema markup) in their source code. It looks like a block of JSON-LD code, usually starting with <script type="application/ld+json">.

Search the source for dateModified or datePublished. Google reads these fields directly, so they tend to be more accurate than whatever date is visible on the page. News sites, blogs, and recipe pages almost always have them.

Checking the XML Sitemap

Most modern websites use an XML sitemap to help search engines find content. You can often access it by adding /sitemap.xml to the end of the domain name.

The sitemap lists every page with a lastmod date next to it. That date updates automatically whenever someone edits a page in the backend. Handy if you want to check a bunch of pages at once instead of inspecting them one by one.

How to Use the Browser Console

This is the fastest technical check. One line of JavaScript in your browser’s developer console and you’ve got a date. Works in Chrome, Firefox, Safari, and Edge.

What document.lastModified gives you is the date the server says the page was last changed. On static HTML pages, that’s usually accurate. On dynamic pages built with WordPress or another CMS, it often just shows the time the page was served, not when anyone actually edited the content.

How to Do This in Chrome

Open Chrome DevTools by pressing F12 or right-clicking and selecting “Inspect”. Click the Console tab, type document.lastModified, and press Enter.

Chrome shows the result in your local timezone, formatted as MM/DD/YYYY HH:MM:SS. The date actually comes from the server’s Last-Modified HTTP header. If the server doesn’t send one, the browser fills in the current date and time instead, which is misleading.

How to Check the HTTP Response Headers

Every time your browser loads a page, the server sends a bunch of HTTP headers along with the actual content. One of them, Last-Modified, tells the browser when the file on the server was last changed.

Finding Headers in Chrome DevTools

Open DevTools (F12), click the “Network” tab, then reload the page. Click on the first entry in the list (the main HTML document). Under “Response Headers”, look for the Last-Modified line.

Not every server sends this header. CDNs and dynamically generated pages often skip it. When it is there though, it’s one of the most trustworthy timestamps you’ll find.

• Open DevTools (F12) and go to the Network tab
• Reload the page
• Click the main document request
• Look for Last-Modified in the response headers
• If absent, the server doesn’t provide this information

How to Use the Wayback Machine

The Internet Archive runs a tool called the Wayback Machine. It takes snapshots of billions of pages over time, going all the way back to the mid-1990s.

Paste the URL you’re curious about into their search box. You’ll get a calendar view showing every date a snapshot was saved.

Interpreting the Calendar View

Coloured circles on the calendar mean a snapshot exists for that day. Blue means the crawler saved the page successfully.

If the snapshots stop appearing after a certain date, the site has likely been taken down or moved to a different URL. Regular snapshots suggest the site is popular or updated frequently.

Comparing Site Versions

Pick two different dates from the calendar to see how the site changed between them. You can spot when new products were added, when the design got an overhaul, or when contact details changed.

Some sites block the Wayback Machine’s crawlers using a robots.txt file. If no results appear, the site owner has opted out of archiving.

• Did the branding or layout change?
• Were service pages added or removed?
• Did the contact details or pricing change?
• Did they rebuild the whole site on a new platform?

Other Tools Worth Trying

A few specialised tools can tell you things the browser can’t. They pull data from domain registries and server configurations.

Whois Lookups

A Whois search shows you the registration history of a domain name, including when it was first created and when it was last renewed.

Renewing a domain doesn’t mean the website content changed. It does tell you the business still wants that web address, though.

Using BuiltWith

BuiltWith tells you what technology a website runs on. It also tracks when a site switches platforms, which is handy if you’re researching how a website was built.

If BuiltWith shows a recent change in tracking pixels or CMS, the site is probably being looked after. You can see a history of plugin updates and platform changes through their interface.

Methods That No Longer Work

Google Cache was retired in September 2024. Before that, you could click the three dots next to any Google search result and view Google’s cached copy of the page, which showed the date Google last visited. This feature no longer exists, and the cache: search operator no longer works either.

If you find guides that still recommend checking Google Cache, that’s a sign the guide itself hasn’t been updated. The Wayback Machine is the best remaining alternative for viewing historical page snapshots.

What to Do If You Can’t Find the Date

Sometimes none of the technical methods turn anything up. When that happens, look at the content itself for clues.

Examining Social Media Links

Most businesses link to their Facebook, Instagram, or LinkedIn profiles somewhere on the site. Jump over and check the date of their latest post.

If a company hasn’t posted on social media in over a year, their website is probably outdated too. Businesses that stay active on social media tend to keep their website maintained as well.

Checking for Broken Links

Click around. Try a few links in the navigation menu and within the body text. Broken links and “404 Error” pages are dead giveaways that nobody’s minding the shop.

A site full of dead links has probably been abandoned, and that means the information on it is probably no good either.

Reviewing the Design

Web design trends shift every few years. A site with a narrow layout, low-resolution images, or no mobile responsiveness was almost certainly built years ago and never touched since.

A professionally designed site today uses full-width layouts and adapts to any screen size. If a site looks broken on your phone, that tells you more than any timestamp could.

Why Different Methods Sometimes Show Different Dates

If you check the same page with multiple methods, you’ll probably get different dates. That’s normal. Each method measures something slightly different.

• Meta tags show when the content author last saved the page in their CMS
• HTTP headers show when the file on the server was last modified (which could be a code change, not a content update)
• document.lastModified reflects what the server reports, which on dynamic sites may just be the time the page was generated
• Sitemap dates update when any change is made in the backend, including edits to metadata or tags that don’t affect what visitors actually see
• Wayback Machine snapshots show when the crawler visited, not necessarily when the site was actually changed

Your best bet is to cross-check two or three methods. If the page source meta tags and the sitemap both show dates from years ago, the content is almost certainly stale. If only one method shows a recent date, the change was probably cosmetic, like a plugin update or a footer tweak.

Frequently Asked Questions

How do I check when a website was last updated in Chrome?

Press F12 to open DevTools, click the Console tab, and type document.lastModified. For a more thorough check, go to the Network tab, reload the page, click the main document request, and look for the Last-Modified response header. You can also right-click the page, select “View Page Source”, and search for article:modified_time in the HTML.

Can you inspect a page to see when it was last updated?

Yes. Right-click anywhere on the page and select “View Page Source” or “Inspect”. In the page source, search for “modified” to find timestamps in the meta tags or structured data.

In the Inspector’s Network tab, check the HTTP response headers for a Last-Modified value. Both methods work without installing anything.

How accurate is the last-modified date on a website?

It depends on the method. CMS meta tags are generally reliable because they update when an author saves the page.

HTTP Last-Modified headers are accurate for static files but can be missing on dynamic pages. document.lastModified is the least reliable of the three because some servers just report the current time instead of the real modification date.

What happened to Google Cache?

Google retired its cache feature in September 2024. You used to be able to view a cached copy of any indexed page by clicking the three dots next to a search result, or by using the cache: search operator.

Neither works any more. The Wayback Machine at web.archive.org is the best alternative for viewing historical snapshots of a page.

Why does the same page show different update dates in different tools?

Each tool measures something different. Meta tags track content saves, HTTP headers track file changes on the server, and sitemaps update whenever anything in the backend changes (including invisible edits like plugin updates).

Different dates don’t mean a tool is broken. Cross-checking two or three methods gives you the most complete picture.

How do I find when a webpage was first created, not just last updated?

Look for article:published_time or datePublished in the page source. These meta tags store the original publication date separately from the modification date.

If those aren’t present, the Wayback Machine’s earliest snapshot is a good proxy. A Whois lookup shows when the domain was registered, but that only tells you about the domain, not specific pages on it.

Keep Your Own Website Updated

If you ended up here because your own site is looking a bit tired, that’s worth sorting out. People expect a site that looks current and works properly. An outdated one makes your business look the same way. Have a look at what makes a good website and see how yours stacks up.

To discuss your project, get in touch with our team. We help Australian businesses keep their websites working as hard as they do.