What shipped

Reports no longer claim more than was measured

Where a report could not measure something, it used to fill the gap with a good result. It now says what it could and could not cover, which is the difference between a report your client can trust and one that quietly flatters the month.

• A week that was only partly measured no longer reads as 100% uptime. The report states how much of the period was actually covered.
• Pages that were never compared are no longer folded into a no-visual-changes result. They are listed as not compared.
• A certificate that browsers reject no longer shows a green count of days remaining.
• An expiry date labelled as a renewal read like good news, so a certificate days from lapsing looked like one that had just been taken care of. An expiry date is now called an expiry date, in the report email, the PDF and the shared report link.

A recipient who cannot be emailed now says so

An address blocked after earlier bounces or spam reports still ended on a cheerful confirmation screen when it was added to a report, even though nothing sent to it would ever arrive. It now says the address cannot be delivered to, so you find that out before your client asks where the report went.

Reports and alerts arrive in a new layout

Every email the product sends has been redrawn: a cleaner frame, your agency colour running along the top, and no block of raw link text at the bottom for people to copy and paste.

Signing in no longer needs a second click

The sign-in link in your email now opens the dashboard directly instead of a page with a confirm button on it. If a mailbox security scanner opens the link before you get to it, the button comes back automatically for the next 90 days, with nothing to ask for or switch on.

Report history and alert history now cover every client at once

Both pages have moved out of the single-client view into the agency section of the sidebar, and list everything sent across your whole portfolio. Filter by client and by site, and the filter stays in the address bar, so a filtered view can be bookmarked or sent to someone.

Dropdowns open at full size again

On any page that loads its data first, a dropdown could open as a sliver a few pixels tall and could not be used. They open properly now. Empty lists were tidied up in the same pass, so a filter that matches nothing no longer claims nothing was ever sent for that client.

Every company that handles your data is now listed on one page

When a client's privacy review asks who else touches their data, there is now a sub-processors page to hand over, naming each company and what it does. The privacy policy, terms and cookie notice were revised alongside it.

A failed send no longer resends the whole report

If one address on a report's recipient list couldn't be reached, the send stopped there and the schedule treated the report as never sent, so it went out again the next hour to everyone who already had it. The send now continues past a failed address, that recipient is listed as not delivered, and the report goes out once.

Uptime alerts name the site in the subject line

A down alert used to arrive as "1 site is DOWN", so you had to open it to find out which one. When the alert covers a single site it now reads "example.com is DOWN", which is enough to act on from a lock screen. Batches covering several sites still show the count.

The unsubscribe link in emails goes somewhere

The unsubscribe link at the bottom of every email pointed at a page that was never built, so clicking it returned a 404. It now opens a confirmation page that removes the address for real. Links from older emails reach that page too, and where the link predates the change it explains how to get the address removed.

Visual checks stay honest when a page stays broken

Two fixes to how a page is compared against its previous capture.

• A page found broken used to become the new reference, so the next check compared broken against broken, found no difference, and went quiet about damage that was still there. Damaged captures are no longer used as the reference.
• When the reference image had aged out of storage, the page was treated as never scanned, which reads as no change. It now falls back to an older capture, and if there isn't one the page is marked unverified rather than clear.

Billing updates can't be lost in transit

A billing update from Stripe that failed to record the moment it arrived was treated as handled and never sent again, which could leave an account looking like an expired trial while it was being billed normally. Those updates are now retried until they're recorded.

Alert emails open the site they're about

Clicking through from an alert could land on whichever site you last had open, not the one the email named. Every alert now links straight to that site's overview, so an alert about one site can't show you another one's data.

One broken link is one problem, not one per page

A single broken link in a footer used to be counted once for every page it appeared on, so a small problem could read like a big one. Each broken link or image is now counted once, with the number of pages it reaches shown beside it.

Links that can't be checked aren't reported as broken

Some sites block automated checks on outbound links, and those were reported red alongside genuinely broken ones. They're now listed separately as unverified, so the broken count only holds things that are actually broken.

Long-standing problems no longer get reported as new

When a scan could only reach some of a site's pages, the next full scan compared against it and treated everything it found as brand new, including problems that had been there for weeks. Comparisons now only run against pages the previous scan actually opened.

The same domain under two clients reads as two sites

If you monitored one domain for two different clients, the portfolio built both rows from the same record, so pausing one silenced the other. Each client's row now stands on its own.

Find where a broken link or image sits on the page

Content Health findings now have a locate button. It opens that page's latest screenshot with the item outlined, so you can see whether a broken link is in the main navigation or buried in a footer nobody reads, without opening the site.

Healthy images no longer reported as broken

Images that render perfectly could show up as broken when a site serves different versions of the same image to different screens. The check now reads the version the browser actually loads, which clears a whole class of false reports on sites that have been migrated between hosts.

The overview lists every site worst-first

Your whole portfolio is now one table, sorted so the sites needing attention are the first rows you read. Paused sites sit at the bottom, and every site shows its own favicon in the overview and the pickers so you can find a client by sight.

Fewer false downtime alerts

Three separate causes of a site being reported down while it was serving visitors normally have been fixed. Incidents now also record what actually failed, so a certificate problem, a DNS problem and a timeout no longer all read the same.

• A site that turns away checks from one location no longer counts as confirming an outage. When two locations disagree, or one is refused, a third is asked before any alert goes out.
• Sites that send unusually large response headers, common with WordPress performance plugins, are now read correctly by every check we run.
• One common shared-hosting security rule rejected the check before it reached the site. Those checks now go through.

Site cards now reflect what was actually checked

A site whose scan stopped part way used to read "Awaiting first scan" even though it had real performance, visual and uptime results. It now shows what was collected, broken assets only report "Clean" once assets have genuinely been checked, and icon addresses that some site builders serve like pages no longer take up one of your monitored page slots.

Settings now cascade from your agency down to each site

Set something once at agency level and every client and every site inherits it, including the ones you add later. Override a single client when that one needs to be different, and set alert rules and mute per site.

• Alert rules cascade across agency, client and site. Report templates are set once at agency level and cover every client and every site; who receives each one and when is set per site.
• Pause everything at once, a single client, or a single site. Scans, uptime checks, alerts and reports stop, and all your history stays.
• New outside recipients confirm their address once. Team members skip it, and you get told when a report cannot reach someone.

Billing shows your exact next charge

The billing page now reads straight from Stripe: your slot count, any discount on your plan, and the exact amount and date of the next charge. You can also type a slot count directly instead of clicking one at a time.

Scheduled report delivery fixes

Fixed an issue that could stop scheduled reports from going out, and made delivery self-healing: a missed send now goes out later the same day instead of waiting for the next period.

• "Send now" no longer delays your next scheduled report.
• The next-send time on the Reports page now follows the client's timezone.
• New clients start with weekly and monthly report schedules already set up.
• If a report has no confirmed recipients, you now get a heads-up email instead of silence.

Scans now show live progress while they run

A progress bar appears whenever a scan is running, covering the first scan after signup, a manual "Scan now", and routine scheduled scans. It fills as each page is captured and audited, and flags a scan that has stopped making progress instead of leaving you guessing.

Switching between clients and sites now happens in one place

The rows of client and site tabs across the top of the dashboard have been replaced by a single searchable picker in the sidebar. The client and site you are currently viewing are always named there, so it is clear what the page is showing.

Signup no longer stalls on slow-responding sites

Adding a site whose sitemap or domain records were slow to answer could use up the entire signup request, leaving the account without a scheduled first scan or report. Page discovery now works to a time budget, and the certificate and domain readings are filled in by the first scheduled scan instead.

Client reports now pick up your agency brand color automatically

The report builder, live preview, and branding panel now use your organization's brand color by default, so a new client's reports match your agency without any extra setup. Leave a client's color blank to inherit it, or set one to override just for that client.

A pricing guide for your care plans

New in Guides: how much to charge for website maintenance, with real published rates across five regions and a calculator to put a number on your own client list.

Shared report links now show the full report

When you share a client's report, the link opens the complete branded report in one page: Performance, uptime, visual changes, broken links, SSL, and domain. The shared page stays private and isn't indexed by search engines.

A free SSL/HTTPS checker, no signup

Check any domain's certificate in seconds: whether it's valid, who issued it, and how many days until it expires. Handy for a quick look at a client's site, or a prospect's before you pitch.

Sharper SSL certificate checks

SSL monitoring now flags more certificate problems: expired, self-signed, untrusted, or issued for the wrong domain, not just certificates nearing expiry.

Ongoing issues no longer trigger a repeat alert on every scan.

When a check crosses one of your alert thresholds, SiteLetter now alerts you once and stays quiet while it stays over that threshold, instead of re-sending the same alert each time the site is checked. No more duplicate emails or Slack messages for a problem you already know about.

Checks blocked by a site's bot protection no longer look like failures.

When a site's security or bot protection blocks a check, SiteLetter now marks it "Couldn't verify" instead of counting it as broken or sending a false expiry alert. The dashboard and the weekly email show the same neutral state, so a blocked check never reads as a real problem on a client's report.

Page discovery now follows your robots.txt rules.

SiteLetter respects the crawl rules in your robots.txt when choosing which pages to monitor, and the pages view shows how many pages those rules keep out of monitoring, with a sample of the paths. Your homepage is always kept, and discovery holds up better on large sites with sprawling sitemaps.

Alternative comparisons now use more precise data.

The /alternatives matrix and most comparison pages were re-verified on this date. Each page carries its own 'last verified' stamp.

Captures and change tracking are steadier on busy sites.

A few patterns that used to throw off a scan no longer do. Newsletter popups and cookie banners are hidden before capture, rotating banners are frozen, and lazy-loaded images are forced to load, so unchanged pages stop reading as changed.

Screenshots and visual change detection both got sharper.

Page screenshots capture more reliably on complex layouts, with fewer missing chunks and less duplicated content. And when something on a page changes, the diff highlights just the area that moved instead of marking the whole page as different.

Mixed content and insecure links now show up on content health.

Mixed content flags http:// scripts, stylesheets, iframes and images loaded by an https page (browsers block or warn on these). Insecure links lists http:// anchor URLs. Both show as separate sections on content health, distinct from broken resources.