Skip to main content
sus.botdocs
  • SEO
  • AI
  • QA
  • Privacy
  • Accessibility
  • Security
  1. Docs
  2. QA
  3. Content freshness
  4. The text names a recent past year as if it were current

QA finding

The text names a recent past year as if it were current

QA Info Severity: Low

Part of the audit Content freshness. Finding id: qa.outdatedYearInText.

What it costs you

'Our rates for' a past year tells the visitor the page was left behind, and they doubt the figures next to it.

What to do

Read the sentence. Update the year together with what it refers to, or reword it so it does not age.

What it checks

  • Past year mentioned as current

How to fix it

Update the year or reword the sentence

  1. Find the sentence on the page with the selector and the context in the evidence.
  2. If it refers to something that changes every year (rates, opening days, a programme), update the content and the year together.
  3. If it is history, leave it and dismiss the finding.
  4. If past years are normal in this section, set the archive_like parameter to its address pattern.

How to check: After the next crawl the page is no longer listed, or its finding is dismissed with a reason.

Thresholds

Thresholds for The text names a recent past year as if it were current
NameDefaultMeaning
min_years_ago1A year is returned when it lies at least this many years back.
max_years_ago3A year further back than this is not returned. Old years are usually history ('founded in 1987'), not something that was meant to be updated.
archive_like%/archive/%SQL LIKE pattern for URLs where past years are expected. Pages that match are not returned.
  • All audits
  • About sus.bot
  • Open the app
  • Contact support