Cleaner GSC imports with overlap, gap, and retention handling
SearchTriage now explains imported date coverage, handles overlapping Search Console exports cleanly, and prunes old parsed row snapshots after 180 days.
SearchTriage now gives clearer coverage information for Google Search Console imports, especially when uploaded exports overlap or leave gaps.
This matters because manual Search Console exports are rarely tidy in the real world. Someone might upload a week of data today, then a three-month export next week. Another user might miss a week, reimport a ZIP, or upload extracted CSV files from the same report.
The app now handles that lifecycle more deliberately.
What changed
Imports now store a structured coverage summary. That summary can explain the imported date range, how many days were included, how many days were new, how many overlapped with existing data, and whether there are missing days inside the range.
Daily metrics are canonicalized by site and date. If a date is imported twice, SearchTriage updates the canonical daily history instead of double-counting it. That keeps dashboard charts and trend reporting cleaner.
Query and page rows still remain as import-level snapshots, because they are useful for source review and report evidence. But those heavier parsed rows do not need to live forever.
Parsed row retention
SearchTriage now supports 180-day parsed row retention for old query and page snapshots. The import record, reports, opportunities, and daily metrics remain. The heavy per-import query/page detail can be pruned later so the account keeps its useful history without storing unnecessary data forever.
That balance is important. SearchTriage should remember what happened, but it should not keep bulky raw analysis snapshots indefinitely if they are no longer needed.
Why this helps content teams
Good SEO planning depends on trust in the data. If overlaps are counted twice, recommendations can be distorted. If missing days are invisible, a chart can look like performance changed when the real problem is incomplete data.
The import coverage panel makes those situations easier to spot.
For example, if a user imports seven days, then imports a larger 90-day export, SearchTriage can show which days were genuinely new and which days overlapped. The dashboard still gets the best canonical daily history, while import detail remains useful for audit and explanation.
Better weekly reporting
This is especially useful for weekly search reviews. A weekly report should not be derailed by upload behavior. SearchTriage can now explain coverage and still focus the user on practical decisions: what to write, update, link, fix, or ignore.
Read more about the product workflow on SearchTriage features.