Why can a returning enhancement issue retain an old detection date?

The Citead team, updated

In short. A returning issue within 90 days can retain its original First detected date.

Definition: An enhancement issue is a structured data problem that Search Console lists for a rich result type. When Google sees the issue again within 90 days after all issues of that type were resolved, the report keeps the original First detected date, so the displayed date can predate the latest recurrence.

Key facts

  • Google's rich result report overview says the issue details page shows the initial detection date under First detected.
  • Google documents that a new instance within 90 days of resolving all issues of that type uses the original first detected date.
  • The validation guidance says an issue remains active until 90 days pass without new instances and that a recurrence after 91 days is recorded as a new issue.
  • An issue can affect structured data items on different pages or multiple items on one page.
  • The report's examples can omit instances after the last crawl or instances affecting more than 1,000 items because the table is limited to 1,000 rows.

What does First detected measure?

Search Console's rich result report is organized around a supported rich result type. Its issue details page describes the issue, its validation status when validation has started, its examples, and its crawl dates. First detected is the initial detection date of the issue. It is therefore an issue-level date, rather than a timestamp for every page or item that later appears in the report.

Google says one issue can affect structured data items on different pages and multiple structured data items on a single page. This distinction matters when a report shows a recurring problem: the same issue record can cover several affected locations. The report also counts structured data items, not pages, in its valid and invalid totals. These details appear in Google's rich result report documentation.

Why does a recurrence keep the old date?

Google's Search Console validation guidance defines an issue lifetime around the absence of new instances. A recurring issue within 90 days maintains its original detection date. The same guidance says that an issue resurfacing after 91 days is recorded as a new issue. The report can therefore show an old First detected date when the issue returns during the documented 90-day period.

This rule concerns the report's issue history. It does not turn First detected into the date of the latest crawl. Google labels Last crawled separately as the most recent date it crawled the page with the issue. A returning issue can consequently have an older First detected date and a newer Last crawled date.

How should you investigate the current occurrence?

Open the issue details page and review the examples and Last crawled field. Google says the examples list may omit rows for instances found after the last crawl or for instances affecting more than 1,000 items. The table is limited to 1,000 rows, and the URL Inspection tool provides error details plus indexed and live test results for a selected URL.

If you have corrected the structured data, Google instructs you to select Validate fix on the issue details page. Its validation process initially checks a sample of pages and then proceeds to other affected pages if that sample passes. Validation can take two weeks or more depending on crawl frequency, and Google may update issue counts during regular crawling even when you have not started validation.

FAQ

Does First detected show the date of the latest recurrence?

No. Google defines it as the initial detection date of the issue. Use Last crawled for the most recent crawl date shown for a page with the issue.

What happens when an issue returns after 91 days?

Google's validation guidance records an issue resurfacing after 91 days as a new issue. A recurrence within 90 days retains the original detection date.

Does starting validation reset First detected?

Google describes Validate fix as the control that starts its validation process, while its issue-lifetime guidance says the First detected date does not reset. Starting validation therefore does not provide a new detection date in the documented report behavior.

Sources

  1. Google Search Console Help, "Rich result report overview", undated
  2. Google Search Console Help, "Fix structured data issues in Search Console", undated

Check how a page reads to answer engines. Open the GEO score analyzer

Test a page and see what to fix first

The analysis usually takes less than 10 seconds and needs no account.

400,000+ pages scored in the public benchmark