Why it matters
After a site update, the hard part of getting pages recrawled is knowing exactly which URLs changed, and remembering what you already submitted last week. Search Console doesn't keep that history in a form you can diff, and spreadsheets go stale.
This tracker saves a snapshot of your sitemap each time you check, compares any two snapshots by URL and lastmod, and keeps a timeline of submissions with the response you got. It all lives in your browser's own storage, nothing on a server, so export a backup if you clear your browser data.
How it works
- InputSitemap snapshots saved over time
- In your browserCompared by URL and lastmod
- OutputAdded, changed and removed URLs, ready for IndexNow
Where it fits in a designer's workflow
- Plan
- Design
- Build
- Test
- Launch
By the numbers
Show the numbers as a table
| Change | URLs |
|---|---|
| Added | https://www.example.co.uk/guides/walnut |
| Changed | https://www.example.co.uk/tables, https://www.example.co.uk/guides/oak-care |
| Removed | https://www.example.co.uk/sale |
How to use it
- Enter your host and fetch or paste your sitemap, then Save snapshot.
- Next time, save another snapshot and pick the two to compare.
- Send the changed URLs to the IndexNow builder, or submit them in Search Console.
- Log what you sent and the response, and export a backup now and then.
FAQ
Where is my data stored?
In this browser's IndexedDB on this device. It isn't uploaded. Another browser or device won't see it unless you import a backup.
What if my sitemap has no lastmod?
Then only added and removed URLs can be found. Changed pages look the same. Adding accurate lastmod dates fixes that.
Does it check whether pages are indexed?
No outside tool can see Google's index reliably. Use URL Inspection in Search Console for that; this tracks what changed and what you submitted.
How often should I snapshot?
After each release or content update. The page reminds you when your last snapshot is over a week old.
