How to Find When a Website Was Published?

To find when a website was published, first look for a visible publication date on the page. If none appears, inspect the source code for datePublished, check the XML sitemap, search for the earliest indexed reference and review the page in the Wayback Machine.

No single method is completely reliable.

A domain registration date tells you when the domain was created, not when a specific page went live. A sitemap often shows the latest update rather than the original publication date. The first Wayback Machine capture proves that the page existed by that date, but it may have been online earlier.

The most accurate answer usually comes from comparing several signals.

What you’ll learn

• How to check a visible publication date
• How to inspect website source code
• How to find datePublished and dateModified
• How to check an XML sitemap
• How to use the Wayback Machine
• What Google search dates can and cannot prove
• How domain registration dates differ from website launch dates
• How to investigate pages that have been updated or moved
• Which methods provide the strongest evidence

Quick answer: the best ways to find a publication date

Use the methods in this order:

1. Check the article heading and footer
2. Look for an updated or published label
3. Inspect structured data for datePublished
4. Check page metadata and source code
5. Look for the URL in the XML sitemap
6. Search the exact page title or URL
7. Review its earliest Wayback Machine capture
8. Check domain registration records only as supporting evidence
9. Contact the publisher when the exact date is important

For an article, visible dates and structured data are usually the strongest starting points.

For an entire website, the earliest archived homepage, launch announcement and domain history are often more useful.

Publication date vs modification date

Before searching, decide which date you need.

A page may have several different dates:

These dates are not interchangeable.

A blog article may have been:

• Published in 2021
• Updated in 2025
• Moved to a new URL in 2026
• First captured by an archive after the move

The visible date may show the update, while the original publication date remains inside the source code or older archive.

Method 1: check the visible page date

Start with the simplest option.

Look near:

• Article title
• Author name
• Opening paragraph
• End of the article
• Share buttons
• Author biography
• Footer
• Breadcrumbs

Common labels include:

• Published
• Posted
• First published
• Last updated
• Updated
• Reviewed
• Modified

Example:

Published March 14, 2023
Updated January 9, 2026

This gives you both the original publication date and the latest revision date.

Do not confuse “updated” with “published”

A page displaying:

Updated July 2026

may have existed for several years.

Some publishers replace the original date with the latest update. Others display both.

When only one date appears, inspect the source code before treating it as the original publication date.

Check the mobile and desktop versions

Some websites hide publication details on smaller screens.

Try:

• Desktop browser
• Mobile browser
• Reader mode
• Print view
• Browser find function

Search the page for:

published

updated

modified

2026

The date may be present in visually small text.

Method 2: inspect the page source for datePublished

Many articles contain structured data that identifies publication and modification dates.

Google recommends using structured data types such as Article or BlogPosting with datePublished and dateModified fields to help search systems understand article dates.

How to view page source

In Chrome or Edge

Right-click the page and select:

View page source

You can also use:

Ctrl + U

On macOS:

Command + Option + U

Then search the source with:

Ctrl + F

or:

Command + F

Search for:

datePublished

dateModified

article:published_time

article:modified_time

Example structured data

You may find code similar to:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "How to Choose a Website Builder",
  "datePublished": "2024-03-18",
  "dateModified": "2026-06-12"
}
</script>

In this example:

• Original publication date: March 18, 2024
• Latest recorded modification: June 12, 2026

Which source-code date should you trust?

Use the following hierarchy:

1. datePublished
2. article:published_time
3. CMS-specific publication metadata
4. dateModified
5. Generic timestamps

Do not assume the first date-like value in the source is relevant.

The source may contain dates for:

• Images
• Comments
• Product prices
• Copyright
• Analytics scripts
• Events
• Reviews
• Cached assets

Structured data can still be wrong

A website owner can configure dates incorrectly.

Common problems include:

• datePublished changes whenever the article is edited
• Publication and modification dates are identical
• The current date is inserted automatically
• A migration resets every article date
• Several schema plugins output conflicting values

Treat structured data as strong evidence, not absolute proof.

Compare it with the visible date and archive history.

Method 3: inspect meta tags

Some websites store publication information in Open Graph or article metadata.

Search the source for:

<meta property="article:published_time" content="2024-03-18">

or:

<meta property="article:modified_time" content="2026-06-12">

You may also find:

<meta name="date" content="2024-03-18">

<meta name="pubdate" content="2024-03-18">

<meta name="last-modified" content="2026-06-12">

These fields vary across platforms.

article:published_time is commonly associated with article metadata used for social sharing and content interpretation.

Method 4: inspect the HTML <time> element

The visible date may be generated through a semantic HTML element.

Search for:

<time datetime="2024-03-18">

A page may display:

March 18

while the code contains the complete date:

<time datetime="2024-03-18T09:30:00-04:00">
  March 18
</time>

The datetime value can be more precise than the visible text.

Check the surrounding class names.

Useful examples include:

published

entry-date

post-date

updated

Method 5: check the XML sitemap

An XML sitemap may contain a <lastmod> date for the URL.

Common sitemap addresses include:

example.com/sitemap.xml

example.com/sitemap_index.xml

example.com/post-sitemap.xml

The exact structure depends on the platform.

Example sitemap entry

<url>
  <loc>https://example.com/article/</loc>
  <lastmod>2026-05-14T10:22:00+00:00</lastmod>
</url>

This tells you that the site reports a significant modification on May 14, 2026.

Google’s sitemap guidance says <lastmod> should reflect the date of the last significant page update, not a small change such as updating the copyright year. Google may use the value when it is consistently accurate and verifiable.

Why sitemap dates do not prove publication

The <lastmod> field normally represents modification, not original publication.

It may also be:

• Missing
• Generated incorrectly
• Updated after every site rebuild
• Reset during migration
• Identical across thousands of pages
• Based on template changes rather than article changes

Use it to confirm recent updates, not as your only publication-date source.

How to find a URL inside a large sitemap

A sitemap index may link to several files.

For example:

post-sitemap1.xml
post-sitemap2.xml
page-sitemap.xml
product-sitemap.xml

Open the likely sitemap and search for:

• Full URL
• URL slug
• Article title fragment

When the website has thousands of pages, a tool or script may be faster than checking manually.

See how to find all pages on a website for broader URL-discovery methods.

Method 6: search Google for the page

Search the exact title inside quotation marks.

Example:

"How to Choose a Website Builder"

You can also search the full URL:

"https://example.com/how-to-choose-a-website-builder/"

or combine the site and title:

site:example.com "How to Choose a Website Builder"

Google may display a date beside the result.

Can you trust the date shown in Google?

Treat it as a clue.

Google chooses dates using several signals. It recommends giving users a clear visible date and supporting it with structured data because one signal alone may be insufficient.

The displayed date may represent:

• Publication
• Significant update
• Date inferred from page content
• Date supplied in structured data

It is not necessarily the first day the page existed.

What happened to Google’s date-range tricks?

Search operators and custom date ranges can help locate older references, but they do not provide a guaranteed original publication date.

A result appearing within a date range may reflect:

• Crawl timing
• Indexing timing
• Update timing
• A date Google associated with the page

Use search dates alongside stronger signals.

Search for the title without the current domain

A page may have moved.

Search the exact title without using site:.

You may find:

• Old domain version
• Syndicated copy
• Social post
• Newsletter archive
• Press release
• Forum discussion
• Citation from another website

An external page dated earlier than the current page can help establish that the content existed at that time.

Method 7: use the Wayback Machine

The Wayback Machine allows visitors to view archived versions of websites by entering a URL and browsing captured dates.

How to check a page

1. Copy the complete page URL
2. Open the Wayback Machine
3. Paste the URL
4. Select Browse History
5. Find the earliest available capture
6. Open the snapshot
7. Confirm that the actual page content appears

The earliest capture proves:

The page was publicly accessible no later than this date.

It does not prove:

The page was first published on this exact date.

The archive may have discovered it days, months or years later.

Check several URL variations

The original page may have used a different address.

Try:

http://example.com/article

https://example.com/article

https://www.example.com/article

https://example.com/article/

Also try:

• Old slug
• Category path
• AMP URL
• Print URL
• Previous domain
• Translated URL

Review the archived page carefully

An archived URL may show:

• Redirect
• Error page
• Homepage
• Domain parking page
• Login page
• Incomplete capture

Confirm that the snapshot contains the article or page you are investigating.

Why a page may be missing from the Wayback Machine

Possible reasons include:

• The page was never captured
• Crawlers could not reach it
• The site blocked archiving
• The page required login
• The page relied heavily on scripts
• The archive excluded it
• The URL changed
• The content was removed

A missing archive does not prove the page never existed.

Method 8: check domain registration records

ICANN’s Registration Data Lookup Tool provides current public registration data for domain names using RDAP and, where needed, WHOIS services. Results can include the domain creation date.

What the domain creation date tells you

It tells you when the current domain registration record was created.

Example:

Domain created: August 12, 2018

The website cannot have existed on that domain before that registration date.

However, the website may have:

• Launched years later
• Used another domain first
• Changed owners
• Been deleted and re-registered
• Hosted unrelated content
• Remained parked for years

Domain age is supporting evidence, not a page publication date.

Domain creation date vs website launch date

Suppose:

• Domain registered: 2018
• First archived homepage: 2020
• Article published: 2023

All three dates can be correct.

The domain existed before the website launched, while the article appeared later.

Can a domain registration date reset?

Yes, in some situations.

A domain may expire and later be registered again. The visible creation date may reflect the newer registration rather than the domain’s earliest historical use.

Archive history and historical registration services may reveal older activity.

Method 9: inspect HTTP headers

Some servers return a Last-Modified header.

You can inspect headers through:

• Browser developer tools
• Command-line tools
• Online header checkers

Example command:

curl -I https://example.com/page/

Possible response:

Last-Modified: Tue, 16 Jun 2026 11:40:22 GMT

Why Last-Modified is weak evidence

The value may refer to:

• File update
• Page generation
• Cache refresh
• Deployment
• Server configuration
• Template change

Dynamic websites often omit it or return the current response time.

Use it only as a supporting signal.

Method 10: inspect JavaScript and API data

Modern websites may load article data through JavaScript or an API.

Open browser developer tools and check:

• Network requests
• JSON responses
• GraphQL data
• Embedded page-state objects
• CMS API responses

Search returned data for:

publishedAt

createdAt

updatedAt

firstPublishedAt

publicationDate

These fields may provide dates not displayed in the page HTML.

Created date is not always publication date

A CMS entry may be created as a draft weeks before publication.

Possible fields include:

• createdAt: draft record created
• publishedAt: first made public
• updatedAt: latest edit
• firstPublishedAt: original public release

Choose the field that matches your question.

Method 11: check RSS or Atom feeds

Blogs and news sites may publish article dates in feeds.

Common feed addresses include:

example.com/feed/

example.com/rss.xml

example.com/atom.xml

A feed entry may contain:

<pubDate>Mon, 18 Mar 2024 09:30:00 GMT</pubDate>

or:

<published>2024-03-18T09:30:00Z</published>

Feeds often retain only recent items, so older pages may be missing.

A feed can also be regenerated during migration.

Method 12: inspect comments

The oldest comment can establish a latest possible publication date.

If the first comment appeared on May 4, 2022, the article must have been public on or before that date.

Comments can help when:

• Publication date is hidden
• Structured data is missing
• Archive history is incomplete

But comments may be:

• Imported
• Moderated later
• Backdated
• Migrated from another URL
• Added through another platform

Treat them as supporting evidence.

Method 13: check social media posts

Publishers often share new pages through:

• LinkedIn
• X
• Facebook
• Pinterest
• Reddit
• YouTube descriptions

Search for:

• Exact title
• Full URL
• Shortened URL
• Domain and key phrase

The earliest social post may indicate when the page launched.

It could also be:

• A later resharing
• An update announcement
• A migrated URL
• A scheduled promotion

Look for wording such as:

• New article
• Just published
• Now live
• Launching today
• We updated

Method 14: check newsletters and email archives

A newsletter may announce the original page.

Search:

• Publisher name and article title
• Newsletter archive
• Email subject
• Campaign landing pages

A dated newsletter saying:

We published our new guide today

is stronger evidence than a generic social share.

Method 15: search external citations

Another website may have linked to or quoted the page.

Search for:

"Exact Article Title"

"example.com/article-slug"

"Distinct sentence from the article"

The earliest dated reference establishes that the page or its content existed by that date.

Check the citing page’s own date carefully.

Method 16: inspect images and file metadata

Images sometimes contain clues.

Possible sources include:

• Upload path with year and month
• Image filename
• EXIF metadata
• CDN URL
• Attachment page
• Media library ID

Example:

example.com/uploads/2024/03/website-launch.jpg

This suggests the image entered the system around March 2024.

It does not prove the article was published then.

The image may have been:

• Reused
• Uploaded before publication
• Migrated
• Renamed
• Stored in a date-based folder automatically

Method 17: inspect the URL

Some websites include publication dates inside URLs.

Example:

example.com/2024/03/18/article-title/

This strongly suggests a March 18, 2024 publication path.

It can still be misleading because:

• The URL may have been preserved after an update
• The date may represent a scheduled publication
• A migrated article may retain its old path
• Editors can manually change URLs

Use it as one signal.

Method 18: contact the website owner

When the exact date has legal, academic or commercial importance, ask the publisher.

Possible contacts include:

• Author
• Editor
• Webmaster
• Communications team
• Support
• Domain owner
• Agency that built the site

Ask a specific question:

Could you confirm the original publication date of [page title and URL]? The page currently shows an updated date, but I need the first public publication date.

The publisher may be able to check:

• CMS revision history
• Database record
• Editorial calendar
• Deployment logs
• Archived newsletter
• Analytics

How to find when an entire website was first published

Finding the launch date of a whole website is different from finding an article date.

Use this sequence:

1. Check the About page
2. Search for company launch announcements
3. Search the company name with “website launch”
4. Check the earliest homepage capture
5. Review domain registration records
6. Search old social accounts
7. Check press releases
8. Look for old sitemaps or archived navigation
9. Ask the owner

Website launch evidence table

The strongest answer may be a range:

The domain was registered in January 2021, the first archived homepage appears in March 2021 and the company announced the site publicly on March 12, 2021.

How to find the original publication date after an update

An updated article may hide its original date.

Try:

1. Search source code for datePublished
2. Compare it with dateModified
3. Open the earliest archive capture
4. Search the old title
5. Check RSS feeds
6. Search external citations
7. Check social shares
8. Inspect URL date folders
9. Contact the publisher

What if the article title changed?

Search using:

• Current URL
• Current title
• Distinct sentences
• Author name
• Topic and domain
• Archived versions

The old title may appear in:

• Search snippets
• Social posts
• Link previews
• Archive captures
• External citations

What if the page moved to a new URL?

Check for:

• Redirect from old URL
• Canonical tag
• Internal links
• Archived sitemap
• Search results with old slug
• Backlinks
• CMS redirect plugin

A redirect can preserve the relationship between the old and new addresses.

The current URL’s first archive date may be much later than the content’s original publication.

How to find the date on a WordPress page

WordPress pages may expose dates through:

• Visible post metadata
• datePublished structured data
• article:published_time
• <time> element
• REST API
• XML sitemap
• RSS feed
• URL structure

A WordPress REST API request may look similar to:

example.com/wp-json/wp/v2/posts?slug=article-slug

When public API access is enabled, the response may contain:

{
  "date": "2024-03-18T09:30:00",
  "modified": "2026-06-12T11:00:00"
}

The API can be disabled or restricted.

Pages and custom post types may use different endpoints.

How to find the date on a Shopify page

Shopify pages, products and articles may expose different timestamps.

Possible signals include:

• Visible blog date
• Structured data
• Product JSON
• Theme metadata
• Sitemap <lastmod>
• API data
• Earliest archive capture

A product’s modification date may change after:

• Price update
• Inventory change
• Image update
• Description edit
• Theme processing

Do not treat every product sitemap date as the original product launch.

How to find the date on Wix or Squarespace

Hosted builders may expose dates through:

• Visible blog metadata
• Structured data
• Sitemap
• RSS feed
• Archive captures
• Search snippets

Static pages such as Home or About may not have public publication dates.

In that case, archive history and launch announcements are often more useful.

Which method is most reliable?

Use this ranking as a general guide.

No method is perfect when the publisher has changed platforms or reset dates.

Use several signals for important research

For casual research, one or two signals may be enough.

For academic, legal or investigative work, record:

• URL
• Visible date
• datePublished
• dateModified
• Earliest archive
• Domain creation date
• Earliest external reference
• Access date

Then explain the uncertainty.

Example:

The page lists March 18, 2024 as its publication date and June 12, 2026 as its modification date. The earliest available Wayback Machine capture is March 21, 2024.

This is stronger than writing:

The website was published in 2024.

Common mistakes when checking publication dates

Using the copyright year

A footer saying:

© 2026 Company Name

usually means the footer was updated for 2026.

It does not prove the page was created in 2026.

Using the domain age as the article age

A domain registered in 2010 can publish a new article today.

Treating <lastmod> as datePublished

A sitemap modification date is not normally the original publication date.

Trusting the first Google date

Google may show an update or inferred date.

Assuming the first archive is the launch date

The archive may have discovered the page later.

Ignoring redirects

The current URL may be newer than the content.

Using image upload dates as proof

Images can be reused or uploaded before publication.

Believing every structured-data field

Plugins and migrations can produce incorrect dates.

Looking only at the homepage

An article, product or landing page has its own history.

Publication-date investigation checklist

Page review

• Visible published date checked
• Visible updated date checked
• Footer reviewed
• Author metadata reviewed
• Mobile and desktop versions checked

Source review

• datePublished checked
• dateModified checked
• article:published_time checked
• <time datetime> checked
• CMS metadata checked

Website files

• Sitemap checked
• RSS feed checked
• URL path checked
• HTTP headers checked
• API data checked where available

Historical research

• Exact title searched
• Full URL searched
• Old URL variants checked
• Earliest archive opened
• External citations searched
• Social posts checked
• Launch announcements checked

Domain research

• Domain creation date checked
• Previous domains considered
• Ownership or re-registration changes considered

Final conclusion

• Publication and update dates separated
• Evidence recorded
• Uncertainty stated
• Publisher contacted when needed

Build a timeline instead of trusting one date

When the exact publication date is unclear, create a timeline.

Example:

• January 8, 2022: domain registered
• February 10, 2022: first homepage archive
• March 18, 2022: company announces website launch
• August 4, 2023: article first published
• June 12, 2026: article updated

This separates the domain, website and article histories.

Start with visible page information. Then check structured data, sitemap records and archived versions. Use domain records only as supporting context.

When several independent signals agree, you can report the date with greater confidence.

WebsiteInABoxPro provides the planning structure behind a website, including publishing fields, page ownership and update responsibilities that make future content histories easier to verify.

Turn this idea into a website box

Start with homepage, pricing, proof, FAQ and blog-ready sections in one editable system.

Start building →

Article by John Fondant

John Fondant is the creator of Website in a Box Pro. He writes about practical website systems, template strategy, SEO-friendly page structure and launch-ready small business websites.

Related posts

Keep reading

Jul 13, 2026

200+ Website Design Statistics You Need to Know [2026]

Looking for some website design statistics to get inspired by? Read our blog post and find out more!

Jul 12, 2026

7 Best Vacation Rental Website Builder Options in 2026

Compare 7 vacation rental website builder solutions, see the real OTA fee math and learn how direct bookings and calendar sync work.

Jul 12, 2026

7 Low-Cost Website Builders for Nonprofits in 2026

Compare the best website builders for nonprofits based on donations, events, volunteer forms, accessibility, pricing and ease of use.