Know about a breakage before your client does

From problem to fix

1. Dozens of client sites in dozens of tabs

   All sites in one list, with tags and groups.

2. A client gets alerts about sites that are not theirs

   Each client’s channel gets only their own sites, with quiet hours.

3. You need to show what was done this month

   A “what we did” report with a letter and milestones, on a schedule, under your brand.

4. Handing a fix to a developer and checking it later

   “Hand over the fix” sends it by email; “Check the fix” confirms it worked.

Checks that spare your server and your attention

How we scan, plainly.

• Gentle on your server: at most 2 requests per second, no daily crawl of thousands of pages.
• Key pages every hour, a sample of every page type each day, every page at least every 8 days and a full crawl every 30 days — and right away when the sitemap, the catalog or the site build changes.
• After a release we check the key pages and one page of each template, without waiting for the schedule.
• An error in a template: you see at once roughly how many pages it touches, in one line per template.
• New pages from the sitemap and from a WooCommerce or Shopify catalog are checked straight away.
• Once you connect Google, we listen to it: Search Console errors, 404 pages with visitors from Google Analytics, speed for real users.
• A site that looks down is re-checked before we wake you.
• A link counts as broken only if it failed to open twice, four hours apart.

Questions