Tell it where you want to be cited. It does the rest.

They report. Attensira opens a pull request against the repository the page actually lives in — a fresh branch, an attensira label, and a body stating which page, which finding, and why the edit answers it. It never merges. The measurement is table stakes; the pull request is the product.

Teams whose site or docs live in a Git repo — technical founders, developer tools, B2B SaaS with no content hire. Attensira installs a GitHub App into your own org, scoped to the repositories you pick. If your content does not live in a repo you can still track prompts, read the stored answers and score competitors, but GitHub pull requests are the only way Attensira ships a fix today.

Setup, then review. Everything that needs a human collects in one Inbox — approvals, blockers, decisions that are yours, failed automations — split into Needs you and In flight. An approval left untouched for 7 days expires and closes the run without doing the thing, so nothing ships because you forgot to say no.

No. Attensira opens a pull request and stops: it never merges, never pushes to your default branch, and never touches CI configuration or workflow files. One caveat worth stating plainly — Attensira cannot read your branch protection settings, so if your repo auto-merges on green, an Attensira pull request will merge too unless you turn on draft mode, which opens every PR as a GitHub draft.

A first-party GitHub App you install into your own org, limited to the repositories you select, with exactly three permissions: Contents read/write, Pull requests read/write, Metadata read. No Actions permission, no Administration permission, no access to your secrets. Each pull request goes to the repo whose page it fixes, and Attensira reports back whether that PR was merged or closed and what CI said.

Every rate carries n, the number of successful runs behind it, so a rate of 33% at n=3 reads as one hit in three draws rather than a percentage floating free. Movement is gated by a two-proportion z-test at 95% significance, and below that bar Attensira reports no change it can prove instead of a number. What it will never tell you is that a mention produced a signup: there is no identity join between a model's answer and a later visitor.

Attensira re-runs your tracked prompts on a schedule — at most once per prompt, model and country per day — across the channels your plan tracks, out of five: ChatGPT, Perplexity, Google AI, Claude and Gemini. It stores the verbatim answer text from every successful run, so when a model changes how it cites, detection can be re-run over the answers already collected instead of starting from zero.

SEO optimises for a position in a ranked list of links. An AI answer has no such list — it either names you or it does not. Attensira reads each stored answer for two separate things: a mention, where your brand name or domain appears in the answer text as a case-insensitive substring, and a citation, where the model attached a URL pointing at your own domain. Then it writes the page edit meant to make the next answer do one of them.