August focused on making domain reports easier to triage before you open every mobile and desktop tab, and on extending the same page-type labels from monitored sites to prospecting leads. We also shipped a public help centre, tightened how we measure outreach engagement, and published agent-readiness improvements on the marketing site so automated visitors can find contact paths and structured metadata without guessing.
Changelog #11 (1 Aug 2026) covered paid plans, the multi-organisation dashboard, newsletter preferences, and first-pass page classification on customer sites. This release builds on that classification work for leads and adds a Summary-first view on shared domain reports.
Domain report Summary tab
Shared domain reports at https://apogeewatcher.com/reports/domain/{token} now open on a Summary tab by default (#summary). Mobile, Desktop, and Tested pages remain on their own tabs when you need the full score cards or per-page tables, so you can triage from one screen before drilling into strategy-specific detail.
The Summary is built for triage. It uses three terms consistently: Pages are URLs you selected; Tests are Lighthouse runs (each page tested on mobile and desktop counts as separate tests); Metrics are the measurements inside a test (LCP, CLS, INP, category scores, and so on). We dropped vague “sample” wording so agency copy matches what you see in the report header.
The attention-free score is the percentage of completed tests that pass every lab gate we track on that report: Performance ≥90, Accessibility, Best Practices, and SEO ≥80, LCP ≤2.5s, CLS ≤0.1, and INP ≤0.2s (with Total Blocking Time as the fallback when INP is missing). 100% means no test on either strategy still needs attention. The headline states how many tests need work, for example “12 of 38 tests need attention”, beside a site status badge and the top gap label when we can infer one.
Below the headline you get a fails-only scoreboard (averages for metrics that are still failing), a short “What we found” narrative, the top five pages that need attention with a Why column that names the failing metric and value (for example Perf (88%) or LCP (3.45s)), attention grouped by page type, and merged opportunity rows that count affected pages on mobile and desktop together with links into both strategy tabs. A coverage line closes the section: how many pages were selected, how many have completed tests, and how many tests finished in total.
PDF exports follow the same order: Summary first, then stacked mobile, desktop, and tested-pages sections. For a deeper walkthrough of the score and how we use Summary links in outreach, see our companion post on attention-free scoring on domain reports, or open any recent report and jump straight to #summary.
Richer domain reports with how-to links
Grouped Lighthouse opportunities link to clearer Chrome documentation where the audit text was ambiguous, and each actionable opportunity can surface up to two related Apogee Watcher how-to posts when we have a published article that matches the audit theme. The same opportunity does not repeat the same blog link twice within a strategy block, so the sidebar stays readable on large scans.
Lead page classification
Prospecting leads in the app now classify discovered URLs with the same page-type taxonomy you already use on monitored sites: homepage, category, product, cart, checkout, content, legal, and the rest of the standard set, plus Unclassified when rules do not match. Classification runs when a lead page is created or when its URL changes. Global URL rules apply first; keyword heuristics fill gaps. Each row stores a type label, a source (global rule, heuristic, manual, or unknown), and a confidence score you can inspect on the lead page detail view. Manual overrides stick until you clear them, matching the behaviour on customer site pages from Changelog #11.
On domain reports generated from leads (including free-check funnels and prospecting runs you start from a lead record), the Tested pages tables group rows by page type so you can see whether product URLs or blog posts dominate the failures. Late August also expanded locale and home-with-query matching in the global rules so common agency prospect URLs classify more reliably on first discovery.
Faster page discovery with DataForSEO
We integrated DataForSEO into the shared page-discovery pipeline. When a sitemap is thin or the origin blocks automated crawls, Watcher can pull likely public URLs from ranking and backlink datasets instead of waiting on a long on-site crawl. That shortens the page-pick step before tests start on monitored sites and on lead prospecting runs that feed domain reports.
Lead outreach and engagement tracking
For seller outreach we added a controlled send path from curated prospect drafts: plain-text templates, reply routing to your normal inbox, and delivery through our Mailgun integration so opens can be recorded without treating internal BCC copies as prospect engagement. In the Messages area, open counts for outreach mail now ignore opens from our own monitoring addresses and campaign BCC recipients, so “opened” reflects the prospect inbox more honestly. The Leads list can filter and sort by whether a domain report exists for the lead and by how many times a shared report link was viewed, which helps you prioritise follow-up after a cold email goes out.
Public help centre at /docs
We shipped a markdown-backed help centre at apogeewatcher.com/docs with fifteen P0 guides organised into Getting started, Testing and results, Reports and sharing, Budgets and alerts, Plans and billing, and Team and access. Articles cover account setup, first organisation and site, discovery, reading lab results, mobile versus desktop strategies, lab versus field data, sharing test links, organisation PDF exports, budgets, alert digests, plan limits, roles, invitations, and what each role can do.
Agent readiness on the public site
We continued the agent-readiness work we showed in We Scored 58/100 on Agent Readiness. The marketing site now publishes llms.txt, a dedicated contact page, richer JSON-LD on home and pricing (WebSite, Service, BreadcrumbList), and recovery links on common 404 paths so automated crawlers and humans land on a useful next step instead of a dead end. Markdown error responses for missing agent-oriented paths include explicit recovery links, and pricing checkout copy aligns with the public pricing template while the footer points to the on-domain contact page. We added an honest planned API stub: a public status endpoint and JSON-shaped 404 responses for guessed API paths, labelled as forthcoming rather than pretending full API coverage already exists.
Permissions and dashboard polish
Manual Run test actions now respect organisation role: only members who can run tests in the current organisation see the control, which stops Viewers from starting quota-consuming runs by accident. Authenticated users who open the sign-up page while already logged in are redirected into the app instead of seeing an empty registration form.
What to try
Open a recent domain report from a free scan or a lead in the app and start at #summary. Note the attention-free percentage, the failing scoreboard, and whether failures cluster in one page type. Switch to Mobile or Desktop only when you need the full opportunity list.
On a lead with many discovered URLs, re-run classification from the page list and confirm product or content URLs pick up sensible types before you generate a report for outreach.
Browse apogeewatcher.com/docs for onboarding a new teammate without exporting internal wiki notes, and send a test outreach message if you run seller campaigns so opens and report views show up on the lead record.
Top comments (0)