Infrastructure and security
Most sitemaps lie, so Google stopped believing them
Nothing had changed. The build had changed. Those are not the same event, and only one of them is any of the crawler's business.
A sitemap can tell a search engine when each page last changed. Almost every automatically generated one gets this wrong in the same way, and the penalty is not a lower ranking. The penalty is that the field stops counting at all.
What the field claims
A sitemap is a list of the addresses on a site, handed to a search engine so it does not have to discover them by following links. Next to each address you may put one optional thing: the date that page last meaningfully changed.
It is there so a crawler can be efficient. Thirty six pages, two of which changed this week, means a crawler can look at two instead of thirty six. Everybody wins, including the people who pay for the bandwidth.
That is the deal. The field is useful exactly as far as it is true.
How almost every site breaks it
A modern site is built by a program. The program runs, writes every page, and writes the sitemap at the same moment. So the easiest possible implementation, and therefore the most common one, is to stamp the date of the build onto every address in the list.
Our own site rebuilds every morning, on a schedule, so that a post dated in the future can arrive on its day without anybody pressing anything. Which means the easy implementation would have us announcing, every single morning, that all thirty six of our pages had just changed.
Thirty six lies a day, told with perfect sincerity by a shell script, to the one party whose job is to notice patterns.
Nothing had changed. The build had changed. Those are not the same event, and only one of them is any of the crawler's business.
What the search engine does about it
This is the part worth knowing, because it is harsher than people expect and it is not a ranking penalty.
Google has said plainly that its treatment of this field is binary. In Gary Illyes' words, we either trust it or we don't.
There is no partial credit. There is no building up a reputation over months. If the dates do not survive contact with reality, the signal is disregarded, and it can be disregarded across the whole site rather than on the pages that got it wrong.
So the cost of filling the field in badly is not that it works less well. It is that you lose the field, and with it the only cheap way you had of telling a crawler which two pages out of thirty six were worth its time.
What we do instead
The rule is one line long and it is not clever.
Which means our sitemap is incomplete, on purpose, and that is the whole point. An incomplete honest signal is worth more than a complete invented one, because the first can be trusted where it speaks and the second cannot be trusted anywhere.
<url>
<loc>https://example.com/blog/a-real-article</loc>
<lastmod>2026-10-14</lastmod>
</url>
<url>
<loc>https://example.com/contact</loc>
</url>
The second entry below is not broken. It is the honest version of a page whose last meaningful change nobody recorded.
- <b>A page whose real date we know carries that date.</b> An article has a publication date. That date is real, it does not move, and it goes in.
- <b>A page whose real date we do not know carries nothing.</b> The field is simply absent. Not a guess, not the build time, not today.
The general principle, which is not about sitemaps
Every system you connect to offers you optional fields, and every one of them is a chance to say something you cannot stand behind.
The instinct is to fill them all in, because an empty field looks like something missing and a full one looks thorough. That instinct is wrong in any system that is paying attention, and the more sophisticated the reader, the more expensive it is.
A field you cannot fill truthfully should be left empty. Not because honesty is a virtue, although it is, but because the alternative does not fail quietly. It fails by discrediting everything next to it.
On Wednesday we wrote about measuring a site without tracking the people on it, which is the same discipline pointed inwards: do not collect what you cannot justify. This is that discipline pointed outwards. Do not claim what you cannot stand behind.
An optional field is not an invitation. It is a question, and a wrong answer costs more than no answer, because silence is never held against you and a lie is.
MK!
Maria Catalina Kovacs
There is no tracking on this site. No analytics, no cookies, nothing recording where you went or how long you stayed.
But I would like to know if something here was worth your time. If it was, press the heart. It tells me nothing about you. It is a number going up, and it is what tells me to keep writing.
If you want more of this, I am on X. @Queendemetriak