Correct invalid or conflicting dates

What does this finding mean?

The report identifies this check as date-contradictions in Freshness and hygiene. The category carries up to 10 of the 100 rubric points. This is a category weight, not an automatic deduction for this finding. Read the scan detail for the measured state, overlapping signals and any score cap.

Use the real document history to correct metadata and visible dates together.

Why does this matter for AI retrieval?

Canonical URLs and valid dates describe which document this is and when it changed. HTTPS protects delivery. These are observable document signals, not a measurement of how often ChatGPT, Claude, Perplexity or Gemini visits.

How do I check and resolve it?

1. Read the document history to establish the original publication and last substantive update dates. Do not use today merely because the template rebuilt.
2. Use valid ISO 8601 dates in markup and a matching visible time element. Updates must not precede publication or lie in the future.
3. Apply dates to articles and documentation where they help a reader. Evergreen homepages do not need a fabricated publication date.

Adapt the example to the reported issue and the actual route. Placeholder names, URLs and dates must be replaced with facts from your site.

Copy code

<time datetime="2026-10-18">18 October 2026</time>
<script type="application/ld+json">
{"@context":"https://schema.org","@type":"TechArticle",
 "headline":"Actual article headline",
 "datePublished":"2026-10-18","dateModified":"2026-10-18"}
</script>
<!-- Replace both example dates with the real dates. -->

Verify the result

Compare the visible date, JSON-LD and sitemap lastmod against the actual update. Rescan the article route, not just the homepage.

Open the related tool or technical guide, then run a new scan of the affected URL. Keep unknown checks marked unknown until you have a complete response.

Copy a prompt for your coding agent

Paste this into Codex, Claude Code or Cursor from your own repository. Include the scan's exact URL and detail so the agent can verify the observation.

Copy prompt for coding agent

Investigate the scanner finding "Correct invalid or conflicting dates" (date-contradictions) in this repository.
Observation: The scanner found invalid calendar values, future dates or inconsistent publication and update ordering.
Required change: Use the real document history to correct metadata and visible dates together.
Inspect the existing route, shared layouts and configuration first. Confirm the finding against the actual response before editing. Preserve intentional access restrictions, existing content and unrelated changes. Use only factual identity and date values. Make the smallest appropriate fix, verify the deployed HTML or resource response and run the relevant project checks. Explain any measurement that remains unknown. Do not promise search rankings or AI citations.
Reference: https://letthebots.in/fixes/date-contradictions/