Sightline for agencies and web studios

Catch what's broken on a client site before the client does.

For the sites you build and run for clients. Sightline reads a client's public pages across three lenses: the interface (broken links and forms, unclear claims, pages that fail on a phone), search visibility and the technical setup. It runs on the domains you manage, verified by DNS with your client's say-so.

Example High Interface footer, every page

The newsletter sign-up in the footer has nowhere to send.

Evidence
On all 14 pages read, the footer form has no action and no script listening to it, so pressing Subscribe only reloads the page.
Why it matters
Visitors think they've subscribed and the client's list never grows. Nobody notices until the client asks why.
Fix
Connect the form to the client's mailing-list service, then test one sign-up.

Evidence

footer form: <form class="newsletter"> (no action attribute)scripts on the page: no submit listener on form.newsletter

Fix for your developer

set the form action to the list provider's endpoint, or bind its embed script
Example finding.

What Sightline checks

Three lenses, one report.

Each finding lands on a to-do list for the page it belongs to.

Interface

UX, forms, accessibility

Links that lead nowhere and forms a visitor can't get through; a price on one page and a different one on another; layouts that scroll sideways or controls too small to tap on a phone. Each one is pinned to the page and the element where it happens.

Search visibility

SEO, metadata, structured data

Page titles and descriptions that are missing, too long or the same on every page; headings out of order; structured data search engines can't read; pages a crawler can't reach. Each one names the page and the tag where it happens.

Technical

headers, cookies, HTTPS

Missing security headers, sign-in cookies without the protections browsers look for, certificate and HTTPS gaps and responses that give away more than they should. All read from what the site already returns to any visitor.

How it works

From a client domain to a fix list, then a re-check.

  1. Add a client's domain

    Only a site you build or run for a client who has agreed to the check. The domain is verified with one DNS record, added by whoever manages the client's DNS with the client's say-so.

  2. Run Sightline

    It reads the public pages across the site, and you can watch it work through them page by page while it runs.

  3. Work the per-page to-do list

    Each page closes with its own list of fixes in rank order, with the severity and a rough effort for each, ready to drop into your tracker.

  4. Re-check after changes

    Run it again when the fixes ship, or turn on the weekly re-scan for that domain, so the next report shows what's still open.

How it runs

Reads public pages the way a visitor does, on domains verified by their owner. It never changes anything on the site.

Verification: whoever manages the domain's DNS adds one record we give them. It shows the site's owner agreed, and Sightline reads nothing until the record is in place.

Pricing

Sightline is a subscription for each client domain, billed monthly. Prices aren't published yet: ask us and we'll tell you.