Most of the advice on this question says the same three things: post to the blog, freshen the copy, redesign every two or three years. That is sensible advice in its own right. What it skips is the signal Google actually reads, which is not the blog post or the redesign. It is the date inside the sitemap. That is why two of the twelve roofing company websites we checked in September had not sent Google anything new since 2025, and neither company knew it.
The blog post is the part of updating that is visible. The sitemap date is the part Google checks. Most owners have no idea what date their sitemap shows, or that the date matters at all.
What the sitemap date means
Every website has, or should have, a sitemap: a file on the server that lists the pages on the site and, next to each one, the date it last changed. Google reads those dates. Building and submitting a sitemap, Google's own documentation for site owners, describes the lastmod field as a signal it uses when the dates are accurate and consistent. The word consistent matters: a site where every date is from two years ago and never moves is sending a consistent signal, but not the one the owner intends.
Google's overview of how sitemaps help discovery puts it plainly: a sitemap is the way to tell Google which pages on the site you consider important. The dates in the file are the part of that conversation that says "something here changed, come look again."
When a sitemap has not moved in a year, Google notices. It does not penalize the site. It just stops expecting anything new from it, and visits less often.
The sitemap check reads this date in about ten seconds. Paste a URL, and the tool finds the sitemap and reports the newest date in the file.
What three of twelve Oahu sites showed
In September we ran the same checks on twelve roofing company websites on Oahu. The sitemap numbers came back like this.
| Sitemap finding | Number of sites |
|---|---|
| No sitemap at all | 1 |
| Sitemap silent since 2025 | 2 |
One site had no sitemap. Two more had one, but the most recent date in it was somewhere in 2025. Three sites out of twelve where Google, every time it visits, reads a file that has not changed.
None of those three companies had closed. From the outside, each one was operating. From inside the sitemap, the sites looked as if nobody had touched them in over a year.
The other five problems Google reads on a homepage are covered in more detail here. The sitemap issue sits quietly at the end of that list. It is not as visible as a missing title tag, but it compounds. A site that has been silent for a year will take longer to turn around than one that just went quiet last month.
What actually counts as an update
Here is where the standard advice falls short. "Update your website regularly" almost always means "write a blog post." A blog post does move the sitemap date, and writing about what customers search for is worth doing. But most businesses have reasons to update other pages far more often, and those count just as much.
What moves a page's date in the sitemap:
- A service page gets a new photo, a rewritten description, or a price change
- The homepage is corrected or a heading is adjusted
- Hours or a phone number is updated
- A broken link is fixed
- A new page is added for a service the business already offers
The CMS handles the date automatically on most platforms. Every time a meaningful change is saved to a page, the date on that page in the sitemap should update.
The right question is not "did we post something this month" but "has anything on this site changed." For a business that updates its hours, adds a seasonal offering, or fixes something a customer pointed out, the answer should be yes most weeks.
What freezes the sitemap is not inactivity in the business. It is inactivity on the site. A company that is busy and growing but has not touched the website in eighteen months has a sitemap that says eighteen months.
The routine that keeps the date moving
A Honolulu office technology dealer we have been working with since September has 123 pages on its website. A program recrawls every one of those pages every Friday, checks each change applied that week, and files anything that did not go live as a new task.
The site changes in small batches every weekday because there is a worker proposing fixes each morning and a person approving them. The Friday crawl closes the loop. Because changes go in and are verified every week, the sitemap dates move every week. Google visits more often, finds something new, and the site becomes one it expects to check regularly.
The business owner does not run the Friday crawl. That is the point: a routine that runs without anyone having to schedule it. What the owner should know is whether any routine like this exists at all. For most small business websites, no one is checking every week. The sitemap date is the most visible sign of it.
What the routine is not is a content calendar. A blog post every two weeks with nothing else changing on the site will move the date twice a month. A site where pages are actively improved, broken things are found and fixed, and the business facts stay current will move the date most days. The difference shows up over months, in how often Google decides it is worth coming back.
Run the check today
Paste your URL into the sitemap check and see when Google last got anything new from your site. If the date is from last year, the free audit covers the rest and the list is yours to keep.