The last two weeks, in dated plain English — new pages, new toggles, new monitoring checks, and the small operator fixes that keep the watchlist honest. Big things and small things, both on the list.
The top five questions every site owner asks before handing over the keys now have a plain-English answer page — trust, safe auto-fix scope, platforms covered, rollback on a bad fix, and how to pause or cancel. Linked from the top nav so visitors reach it before the subscribe button.
Open SiteIssues now have a one-click "Mark resolved" button on each row. It writes the resolution back through the audit log, so the weekly digest and the issue counts stay in lockstep with what the operator actually closed.
The Friday digest now leads with a one-glance status row — green / auto-fixed / needs you — and the subject line names the single most important item so filtered inboxes still tell the story. Everything else in the email stays the same.
A new /pricing page lists the three flat monthly plans — Solo for one site, Shop for up to three sites, Scale for unlimited sites with priority delivery — with a hosted Stripe checkout for each. Cancel any time; no setup fee.
Owners can now hold auto-applied safe fixes on a single site without affecting the rest of the watchlist. One toggle in the operator console pauses the small stuff — sitemap pings, broken-link redirects — until they flip it back. Held fixes still get logged, just not applied.
The day a watchlist URL is added, removed, or redirected, the operator now regenerates the sitemap and pings the search engines the same morning. No more waiting a week for a stale sitemap to settle.
Every site Hearthkeep watches now ships with a defense-in-depth header set: Content-Security-Policy, Strict-Transport-Security, Referrer-Policy, and the standard hygiene trio. Owners can tighten or relax any of them from the operator console.
The daily HTTPS probe now reads the certificate expiry and surfaces a 30-day warning in the digest — well ahead of any browser padlock turning red. Repeated checks (every six hours) kick in once we are inside that warning window.
A ranking-relevant diff — a missing H1, a changed canonical, a stripped meta description — now shows up in the digest with a before/after line so you can spot a regression the same week it lands, not the next time a customer complains about search traffic.