Product2 min read

See every fix on a real build, then see who arrives

Fix it is now one sheet. Each fix previews on a real build of your site, waits for your OK, then shows the first AI crawler and the first visitors to reach it.

Fix it as one sheet: who AI picks instead of you, then rows for fixes waiting for your OK, connections a fix waits on, a listing our team does, and pages to write, each with one action and its stage.
Every fix, task and missing connection is one row with one action. Shown on a demo account with sample data.

Since October, every fix could be published and checked. Now you see it on a real build of your site first, and after it goes live, you see who comes to read it.

1 sheet
every fix, task and connection
Hourly
reads of a new fix page for its first 48 hours
Ask me first
Autopilot's default

A real build, not a mockup

Diagram: the fix, a change on a branch, is previewed by your host when it builds previews; otherwise Proofsource builds it on proofsource.site. Either way you see the real page in your site's layout, then give your OK.
Your host's own preview comes first. Only when it has none does Proofsource build the branch itself.
  1. The fix

    A change on its own branch.

  2. A real build

    Your host's preview, or a Proofsource build on proofsource.site.

  3. The real page

    Framed inside your live site's own layout.

  4. Your OK

    Only then does it go live.

Then see who arrives

A fix's Timeline after it went live: OAI-SearchBot and PerplexityBot read the changed page, then the first visit by a person from Google search and the first from ChatGPT, with visit counts.
The Timeline: first AI crawlers, then the first people from search and ChatGPT. Shown on a demo account with sample data.

With Cloudflare connected, a new fix page is read every hour for two days, then daily. Crawlers, people and AI referrals each get their first line.

You stay in charge

Settings, Autopilot: a dial from Ask me first to Fully handle it, set to Ask me first; reading and drafting always run, every change to your site asks you, and holds by place for site builders, GitHub and Cloudflare.
Autopilot starts at Ask me first. Hold any place or step; the strictest rule wins. Shown on a demo account with sample data.
  • One sheet. Fixes, person tasks and connections, sorted by where AI already looks.
  • One page per fix. The change, Improve this page and the Timeline side by side.
  • Improve a live fix. Say what to change, see the new preview, then approve.

Availability

Live for every brand on Fix it. Hourly reads and visits need Cloudflare connected; Autopilot lives in Settings.

See Autopilot

Further reading

Published · Questions or feedback? Write to us

Questions

Where does the preview come from?

From your host's own preview when it builds one. When it does not, Proofsource builds the fix's branch the way your site ships and serves it on proofsource.site.

Can Autopilot publish without asking?

Only if you turn the dial up. It starts at Ask me first, and any place or step you hold always asks.

How do I see visitors to a fix?

Connect Cloudflare. Proofsource then reads a new fix page every hour for two days and adds the first crawler, person and AI referral to the fix's Timeline.

Find where AI leaves you out. And fix it.