Why your page count changed
Your page count dropped and nothing was deleted — here's why the new number is the accurate one.
If your project used to show 5,192 pages and now shows 2,273, nothing was deleted. The old number was wrong.
Until recently, TaskGlaze kept every page it had ever seen on your site, across every crawl, and showed you the total. Crawl a site four times over three months and the count only ever went up, even for pages that no longer existed. It looked stable. It wasn't measuring anything.
The number you see now is what the most recent crawl actually found. That makes it smaller, and it makes it real: crawl the same site twice without changing anything and you'll get the same number twice. It also means the number can go down when your site genuinely loses pages, which is exactly what you want a page count to do.
Two related fixes landed at the same time. We used to count http://example.com/page, https://example.com/page, https://www.example.com/page and the trailing-slash versions of all three as separate pages. One page could appear eight times. Now they fold into one. And redirects that pointed at a page we'd already crawled were being counted twice: once as the redirect, once as the destination. Now just once.
So your count dropped for three reasons at once: stale pages from old crawls are gone, duplicate URL variants are collapsed, and double-counted redirects are fixed.
Your score may have moved too. The health score is an average across the pages in the crawl. If the old count included hundreds of stale, low-scoring pages, dropping them raises the average. A score that moved several points the first time you re-crawled after this change is expected, and the new one is the honest number.
What to do: re-crawl each project once. Until you do, a project still shows its old figures. After that, compare like with like — this crawl against the next one, not against anything from before the change.