Last Updated Dates on Guide Pages, Done Honestly
Our wiki had a raid guide that was genuinely current. Someone had checked every ability timer against the live build three weeks earlier.

Our wiki had a raid guide that was genuinely current. Someone had checked every ability timer against the live build three weeks earlier. The page still said March 2022, because that was the only date the theme printed, and the Discord reaction to it was always the same: is this still good? We answered that question in chat maybe forty times before I accepted it was a template problem and not a reader problem.
So I did what most admins do first and ran a bulk date update across 600 pages. Traffic did not move. Two readers noticed every guide on the site had been edited on the same Tuesday and said so publicly, which was worse than the original complaint. Dates are useful, and they are only useful if they describe something that actually happened.
What a date is doing on the page
A reader looking at a guide wants to know one thing: has this been checked since the last patch that mattered. That is a different question from when the article was written. On a site covering a game that ships balance changes every six to eight weeks, a publish date from 2022 is not evidence of anything except that the page is old.
Search engines read dates too, and the behaviour is worth separating from the folklore. Google will show a date in a result when it can work one out confidently, drawing on visible text on the page, structured data, the URL, and the sitemap lastmod value. It picks one. If your visible text says one thing and your schema says another, you have handed it a reason to pick the wrong one or to show nothing. The date is a display decision, not a ranking lever, and treating it as a lever is where people get into trouble.
There is a second audience nobody designs for: your own volunteers. On a team of eight part time editors, a reliable modified date is how the next person knows whether a page has been through the current patch or is still waiting. Ours became the de facto work queue.
Two dates, and keeping them from arguing
Show both. The published date gives the page a history, and the updated date answers the question readers actually have. One line under the title, something like published January 2022, checked 14 November 2026, reads better than either date alone and takes about four minutes to add to a child theme template.
In WordPress the functions you want are get_the_date() and get_the_modified_date(). The second one has a trap: WordPress treats any save as a modification, so fixing a typo, changing a tag, or re-saving a draft moves the modified date. If you print it unconditionally your guides will look like they are revised weekly when nobody has touched the content. The rule I settled on is to print the modified date only when it is at least 30 days later than the published date, and only when the edit was logged as a content check rather than housekeeping.
Then make the markup agree. Article schema has datePublished and dateModified, both in ISO 8601 with a timezone offset, and most SEO plugins fill them from the same post fields your template reads. Check with the rich results test rather than assuming. The two cases I keep seeing on fan sites are a theme that hardcodes the publish date into schema while the visible line shows the modified date, and a caching layer serving a schema block generated before the last edit.
Sitemap lastmod is the third place. It should match dateModified, and it is the one most likely to be lying, because plenty of sitemap plugins write today's date for every URL on every regeneration. If your sitemap claims 600 pages changed last night, the crawler learns to ignore the field entirely, and you have lost a genuinely useful signal for the pages you really did fix. Keeping that file honest matters as much as the rest of what goes into an XML sitemap for a fan site.
The freshness myth, and what the bulk bump really costs
The advice circulating in admin groups is that search engines reward recency, so you should keep dates moving. I believed it for about a year. Here is what happened on our site, which gets roughly 40,000 sessions a month, so the numbers are small but not noise.
The bulk re-save in 2024 touched 600 pages. Over the following ten weeks, impressions on those pages moved less than 3 percent against the site trend, and clicks did not move at all. Meanwhile 38 pages that had real content work done on them, new timers, rewritten sections, corrected item names, gained measurably, and several of them were pages we had not re-dated at the time.
The mechanism is not mysterious. A crawler can compare the content it stored against the content it fetches. Changing a timestamp while the words stay identical tells it nothing it cannot check directly. What a changed date buys you is a recrawl, slightly sooner, which is valuable exactly when the page has changed and worthless when it has not. Spend it on the 38, not the 600.
The reader cost is the part people skip. A guide dated three days ago that still references a removed mechanic is worse than one honestly dated 2022, because now the date is evidence that someone looked and missed it. Trust on a community site is slow to build and very easy to spend.
A policy a volunteer team will actually follow
Ours fits on an index card, which was the design constraint. Anything longer than that gets ignored by week three.
- Define what counts as a check: someone opened the page, compared it against the current build, and either changed something or confirmed nothing needed changing.
- Add a custom field, we called it last_verified, and set it by hand during a check. Print that in the visible line, not the WordPress modified date.
- Map
dateModifiedin schema to the same field so the markup and the page agree. - Leave the sitemap to real file changes and turn off any setting that rewrites lastmod on every build.
- Set a review cadence by page value rather than by calendar: top 50 pages within two weeks of a major patch, the next 200 within two months, the long tail when someone reports a problem.
- Record the patch version alongside the date, since checked against patch 7.2 is more useful to a reader than a bare date.
- Never bulk edit dates. If a batch of pages genuinely needs checking, that is scheduling work, not a database update.
Point six turned out to matter more than the rest combined. Our older pages that carry a patch number get the is this current question almost never, even when the date is eight months old, because the reader can decide for themselves whether that patch is close enough. Pages with the date alone still get asked.
One thing I cannot tell you is how much of our later growth came from any of this. We changed the review cadence in the same quarter we fixed a pile of dead internal links, and I never separated the two, which is poor measurement on my part. If you are auditing old pages anyway, the piece on how broken internal links pile up on long running wikis covers the other half of that cleanup, and renaming pages during a review has its own hazards, set out in the guide to renaming a wiki page without losing traffic.
FAQ
Should I remove dates from guide pages entirely?
Only for pages that genuinely do not age, like a glossary or a site rules page. On patch dependent guides, hiding the date does not make the page feel current, it makes readers assume you are hiding something. Search engines will also often work a date out anyway and show it, so you lose control of which one appears.
Does changing the modified date trigger a recrawl?
It can, mainly through sitemap lastmod, but the effect is a scheduling nudge rather than a promise. Pages that change often get crawled often because the crawler has learned that from history. A single date change on a page that has not moved in two years will usually not jump the queue.
What timezone and format should the date use?
Use ISO 8601 with an explicit offset in structured data, so a value like 2026-11-14T09:30:00+01:00. For the visible line, write it the way your readers write it and include the year. A date of 14 November with no year ages badly on a site that keeps pages for a decade.
Can I show a date without touching the theme files?
Yes, if you are happy typing it into the post. A short line at the top of the body text works and survives theme changes, which is how we ran it for the first six months. The downside is that nothing keeps it in sync with your schema, so you end up checking two places by hand.
More in Web Tips
Web Tips
How to Stop Layout Shift on Ad Heavy Game Guide Pages
The complaint that finally made me fix this arrived in our wiki Discord as a seven second clip.
Web Tips
How to Fix Discord Link Previews for a Game Site
Someone in our clan Discord posted a link to a raid guide I had spent a weekend writing, and the embed came out as the site...
Web Tips
How to Lazy Load YouTube Embeds on Game Guide Pages
A boss guide with six embedded YouTube clips feels helpful to write.