Interpreting Your Report

Freshness and re-scans

Re-scan cadence should follow how volatile the business fact is, not a fixed calendar alone.

Some facts can stay valid for months. Others become wrong in hours. The re-scan schedule should reflect the risk of a stale answer.

Suggested cadence

Change	First re-scan	Follow-up
Schema or page content	24 to 72 hours	7 days if still stale
Booking, quote, or phone link	Same day	24 hours and 72 hours
Regular hours	Same day	24 hours and 72 hours
Holiday or special hours	15 minutes to 2 hours	Daily during the event window
New location or address move	Same day	24 hours, 72 hours, 7 days
Review or authority campaign	Weekly	Monthly trend review

What to record

• Change timestamp.
• Changed URL or profile.
• Source-of-truth value.
• Platform updated.
• First assistant answer observed.
• Citation or evidence used.
• Whether the fact, evidence, and action path are current.

Common propagation bottlenecks

Bottleneck	Symptom
Crawl delay	Site is correct, assistant still cites old page.
Listing lag	Website is correct, but maps or directory data is stale.
Schema mismatch	Markup is updated, visible content disagrees.
Weak source preference	Assistant uses a stale third-party source over the official page.

Turn rescans into evidence

Re-scan on a schedule tied to the change and use the results to identify which provider or page is lagging.

Run scan