Should Small Business Blog Posts Show Publish and Updated Dates? What Google Says (2026)
Should small business blog posts show a publish date and an updated date?
Yes, for most small business blog posts: show a clearly labelled published date, add a "last updated" date when you make a real change, and keep both consistent with your structured data and sitemap. Google's byline date documentation asks for a user-visible date "featured prominently" and labelled with words like "Published" or "Last updated". What Google warns against is changing dates to look fresh without changing the content. This guide was checked on 2026-11-10 and ends with a 4-rule date policy you can copy.
PilotaSEO is a done-for-you SEO blog service that writes SEO posts for your site and publishes them automatically. Every post needs a date policy before it goes out, which is why this question comes up early.
What does Google say about dates on blog posts?
Google asks for a visible, labelled date that matches the date in your structured data, and it doesn't guarantee showing it. The Search Central guide to byline dates lists three steps: follow its best practices, add a user-visible date featured prominently, and specify datePublished or dateModified in Article or BlogPosting structured data.
Its best practices are short and specific, and each one is a mistake small sites make:
- The date is required, the time is not. A time and timezone in the markup add precision.
- Keep visible and structured dates consistent. The date shown on the page and the date in the markup should match.
- No future dates, and no dates of the event a post describes. The date is when the page was published or updated.
- Minimise other dates on the page. If Google picks the wrong date, remove some of the other dates, such as an old date in a sidebar.
Google also says it doesn't guarantee that a byline date, visible or structured, will appear in search results. In practice that means the date is a signal you control, not a feature you can force: get it right on the page and in the markup, and let Google decide whether to display it. On a small blog the common failure is not a missing date but two conflicting ones, for example a theme that prints the original date in the header and a "related posts" widget that prints a different one beside it.
Is it bad to update the date without changing the post?
Yes. Google's guide to creating helpful, people-first content lists "changing the date of pages to make them seem fresh when the content has not substantially changed" among the warning signs of search-first content. Change the visible date only when the content really changes.
The same rule applies to your sitemap. Google's sitemap documentation says it uses lastmod only if it is "consistently and verifiably" accurate, and that lastmod should reflect the last significant update, such as a change to the main content, structured data or links. A site that bumps every date daily teaches Google to ignore its dates.
Which dates belong where?
Each date has one job, and they should agree with each other. This table maps them.
| Where | Date | Change it when |
|---|---|---|
| Visible byline | Published, plus "Last updated" if changed | The content changes meaningfully |
| Article or BlogPosting markup | datePublished, dateModified | Same moment as the visible updated date |
| XML sitemap | lastmod | A significant update to content, markup or links |
| URL | None | Never; keep dates out of slugs |
Worked example. A plumber publishes "How to stop a frozen pipe from bursting" on 2026-01-12. In November they add a section on outdoor taps and replace a dead source link, which is a real change. The byline becomes "Published 2026-01-12 · Last updated 2026-11-10", the markup gets datePublished 2026-01-12 and dateModified 2026-11-10, and the sitemap lastmod moves to 2026-11-10. In December they fix a typo: nothing changes in any of the three places.
The structured data side is covered in our guide to Article schema for small business blogs, and the sitemap side in whether a small business blog needs an XML sitemap. Keeping years and dates out of the URL lets you refresh a post without changing its address; blog post URL slugs explains why.
Should evergreen posts hide their dates?
Hiding dates doesn't make a post fresher, and without one a reader following steps can't tell whether they still apply. For a small business blog, the honest options are to show the published date on everything, or to show "last updated" on posts you actually maintain.
Some advice says to remove dates so old posts don't look stale. That treats the symptom. If a post is out of date, update it and show the new date, or decide it needs a rewrite; refresh or write new has a test for that choice. Service and pricing pages are different: they are not articles, so a byline date adds little there.
The 4-rule date policy for a small business blog
Write this down once and apply it to every post, whoever writes them. It takes the guesswork out of each update.
- Show the published date near the top of every post, labelled "Published".
- Add "Last updated" only after a real change: new facts, a new section, corrected steps or new sources. Not for a typo or a new internal link.
- Mirror both dates in datePublished and dateModified, and set the sitemap lastmod to the same update.
- Keep one date per role on the page. Remove stray dates in sidebars or "related posts" boxes if Google shows the wrong one.
A byline with a real name or team also helps readers judge the date; see whether author bios help SEO. This page follows the policy: its byline shows when it was published and last verified.
Does a done-for-you blog handle dates for you?
It should, and it is a fair question to ask any provider before you sign. Ask how they set the visible date, whether they update dateModified only for real changes, and whether the sitemap lastmod follows the same rule.
PilotaSEO's plans are Autopilot at €322 a year and Growth at €8,250 a year; the PilotaSEO plans list what each includes.
FAQ
Do dates on blog posts help SEO?
Google uses visible and structured dates to work out when a page was published or updated, and may show that date in results. It doesn't guarantee showing it, and a date doesn't replace useful content.
Should I change the date when I update a blog post?
Only when the update is meaningful, such as new facts, sections or corrections. Google lists changing dates to look fresh without substantial changes as a warning sign.
Can I show only the updated date?
Google's examples include "Last updated" labels, so showing the updated date is acceptable. Showing both dates, clearly labelled, gives readers the fullest picture.
Should the date be in the blog post URL?
Keeping dates out of URLs makes refreshing a post easier, because the address doesn't have to change when you update it. Google's byline guidance is about the visible date and markup, not the URL.
Sources
- Google Search Central: Influence your byline dates (checked 2026-11-10)
- Google Search Central: Creating helpful, reliable, people-first content (checked 2026-11-10)
- Google Search Central: Build and submit a sitemap (lastmod) (checked 2026-11-10)
- Google Search Central: Article structured data (checked 2026-11-10)