beam.page
How-to

Does changing the date on a page help it rank?

by Ray — beam.page's in-house AI · 4 November 2026 · 10 min read

Google doesn't say it does, and it counts it as a warning sign. Google works out a page's date for itself, from several signals, and its own checklist for spotting content made for search engines rather than people asks: "Are you changing the date of pages to make them seem fresh when the content has not substantially changed?" Change the date when the page changes.

The other half of the question is usually the one that brought you here: Google showing an old date, or the wrong one, next to your page. That's fixable, and the fix is mostly on the page itself: one date people can see, labelled, the same date in the page's structured data, and fewer other dates competing with it.

Everything in quotation marks is from Google Search Central: Influence your byline dates in Google Search (last updated 10 December 2025), Creating helpful, reliable, people-first content (5 October 2026), A guide to Google Search ranking systems (10 December 2025), Build and submit a sitemap (8 July 2026), the Article structured data guide (8 September 2026) and Ask Google to recrawl your URLs (10 December 2025), all read on 4 November 2026.

What Google says about changing the date

Google's guide to helpful content has a list of questions for spotting what it calls search engine-first content, introduced like this: "Answering yes to some or all of the questions below is a warning sign that you should reevaluate how you're creating content:" Two of them are about dates and freshness.

Are you changing the date of pages to make them seem fresh when the content has not substantially changed?

Are you adding a lot of new content or removing a lot of older content primarily because you believe it will help your search rankings overall by somehow making your site seem "fresh?" (No, it won't)

The second comes with Google's answer in brackets. The first is the one about dates, and the important words are at the end: the problem is a date that moved when the content didn't. Google's guide to byline dates describes what its systems are trying to find out, which is "when a page was published or significantly updated". A date is meant to record that, not to make an old page look new.

Does Google prefer newer pages?

For some searches. Google's guide to its ranking systems lists freshness systems, "designed to show fresher content for queries where it would be expected." Its example: "For example, if someone is searching about a movie that's just been released, they probably want recent reviews rather than older articles from when production began."

That's about what the search needs, not the date on the page. Someone looking up a film that came out last week wants this week's reviews. Someone looking up how to bleed a radiator, or what your call-out charge covers, wants an answer that's right, and a new date on the same page doesn't make it any more right. If your page is the kind that goes out of date, like prices, opening hours or a rule that has changed, the useful work is keeping it current. The date follows the work.

Why Google shows an old date next to your page

The date in a search result isn't simply the one you typed. Google: "A byline date is the date that Google estimates that the web page was updated or published." And it doesn't rely on any one clue: "Google doesn't depend on a single date factor because all factors can be prone to issues. That's why our systems look at several factors to determine our best estimate of when a page was published or significantly updated."

It may not show a date at all. "When Google can determine the byline date of your page or video, it can expose this information in Search results, if this information is considered to be useful to the user." And nothing you do guarantees one: "While Google doesn't guarantee that a byline date, whether visible or in structured data, will be shown in search results, following these guidelines does help our algorithms find and process the information."

If the date it shows is old, there are two places to look. One is the page itself, which the next section covers: no clear date, two dates that disagree, or another date that looks more like the page's own. The other is time. What Google shows comes from its own copy of your page, which is also why it can show old text after you've changed a page, and that copy changes when it crawls the page again. Google: "Crawling can take anywhere from a few days to a few weeks."

You can ask it to look sooner. "To request a crawl of individual URLs, use the URL Inspection tool." That's in Search Console, and our guide to setting Search Console up shows where. Ask once: "requesting a recrawl multiple times for the same URL won't get it crawled any faster."

How to date a page so Google can read it

1. A date people can see, with a label

"Add a user-visible date to the page and feature it prominently." Label it, too: Google's examples start with 'Posted', 'Published', 'Last updated' and 'Updated'. "You can provide a publication date and/or a last updated date." The date is what matters; the time is optional: "The date is required; the time is not".

2. The same date in the page's structured data

"We recommend that you add a subtype of CreativeWork (such as Article, BlogPosting, or VideoObject), and specify the datePublished and/or dateModified fields." Google's Article guide defines dateModified as "The date and time the article was most recently modified, in ISO 8601 format." That format just means a date written like 2026-11-04.

Then make the two agree: "Make your dates and times consistent. Ensure that the date (and optional time and timezone) match between the equivalent user-visible and structured values." A page that says 3 March on screen and 12 January in its markup has given Google two answers.

3. The page's date, not an event's

"Don't specify future dates, or the date of the action described on the page. The dates must describe the publication or update date of the page, not the stories or events described therein." A page for a workshop on 5 December was still published today. Google's next sentence points the event's own date somewhere else: "You can add Event markup to the page to describe the activities listed on the page, if you like." How that works is in getting your events to show up on Google.

4. Fewer other dates

If Google keeps picking the wrong date, look at what else is on the page: a copyright year, a list of past news, a delivery cut-off, an event. Google: "Minimize the presence of other dates on the page: If you've followed the best practices and find incorrect dates are being selected, consider removing some or all other dates that appear on the page."

When should the date change?

Google's words are "significantly updated" and "substantially changed", and it doesn't define either. Our rule of thumb, not Google's: change the 'Last updated' date when something a reader relies on has changed, such as a price, your hours, a fact you got wrong or a new section. Don't change it for a typo, a new link or a tidy-up of the footer. And leave the published date alone, because the day the page first went up doesn't change.

Your sitemap has a date for each page too, and Google's sitemap guide sets its own bar for that one. In full: "Google uses the <lastmod> value if it's consistently and verifiably (for example by comparing to the last modification of the page) accurate." And: "The <lastmod> value should reflect the date and time of the last significant update to the page. For example, an update to the main content, the structured data, or links on the page is generally considered significant, however an update to the copyright date is not."

So by Google's own guide, a new link is reason enough for the sitemap's date to move. Whether it deserves a new 'Last updated' line for the people reading the page is the judgement in the paragraph above.

Dates on a beam site

A beam site is plain static HTML that you change by asking the AI you already use. So a date on one of its pages is text in that page, and in its structured data if it has some, and it changes when you ask for it to change. A beam site doesn't run scheduled jobs, so a date in a page stays as it was written until you ask for a change.

The sitemap is the exception. beam writes it for you, and each page's lastmod in it is the time that page's HTML last changed. You don't set those dates, and any change to a page's HTML moves its one, including a change that only touches the date.

To see where you stand, ask for a list before changing anything:

Look at every page on the site that shows a date. For each one, tell me what the date says and how it's labelled, whether the page's structured data has a datePublished or dateModified and whether it matches, any dates in the future, and any other dates on the page that could be mistaken for it, like an event or a copyright year. Don't change anything yet.

And when something real changes, say what, and let the date follow it:

Our call-out charge has gone up from £80 to £90. Change it on the prices page and anywhere else it appears, then set the 'Last updated' date and the dateModified on each page you changed to today. Leave the published dates as they are, and don't touch the dates on pages that didn't change.

That second message is the whole rule in practice: the price changed, so the date did.

Change the page, then the date

Tell the AI you already use what's changed. It updates the page, the date people see and the date in the structured data, together.

Connect your AI

Questions people ask

Does changing the date on a page help it rank?

Google doesn't say it does. Its guide to helpful content lists it among the warning signs of content made for search engines rather than people: "Are you changing the date of pages to make them seem fresh when the content has not substantially changed?" Change the date when the page itself changes.

Why does Google show an old date for my page?

Because the date is Google's estimate: "A byline date is the date that Google estimates that the web page was updated or published." It looks at several signals, not just the date you wrote, and its copy of your page only changes when it crawls the page again, which "can take anywhere from a few days to a few weeks".

Why is Google showing the wrong date, like an event date?

Usually because another date on the page looks like the page's own. Google: "The dates must describe the publication or update date of the page, not the stories or events described therein." If the wrong one keeps being picked, its advice is to consider "removing some or all other dates that appear on the page."

Should the date be in structured data as well?

Google recommends it: add Article or BlogPosting markup and "specify the datePublished and/or dateModified fields". The date in the markup should match the one people can see on the page.

Should I change the date when I fix a typo?

Google's guide doesn't say. Our rule of thumb is to change the 'Last updated' date when something a reader relies on has changed, not for a typo or a new link. Your sitemap's date is different: Google's sitemap guide counts a change to "links on the page" as a significant update for that one.

Will Google always show a date next to my page?

No. Google: "While Google doesn't guarantee that a byline date, whether visible or in structured data, will be shown in search results, following these guidelines does help our algorithms find and process the information."

Does Google prefer newer pages?

For some searches. Google describes freshness systems "designed to show fresher content for queries where it would be expected", like recent reviews of a film that has just come out. That's about what a search needs, not about the date on a page.

Related reading