Every change to your pages, matched and measured
Attensira reads your pages on a schedule and records every change it sees: one it shipped, one you made from its advice, or one nobody suggested. It matches the change to the suggestion behind it, then re-reads the same prompts at +7, +14 and +30 days and reports moved, too early, or nothing it can prove yet.
7 days free · card required
- 30 Sep 2026 · first capturedHTTP 200 · JSON-LD present
- 1,657 words
- 2 Oct · changedJSON-LD absent: the server returned a near-empty page
- 36 words
- 4 Oct · changedBody and JSON-LD back
- 1,693 words
New wording · waitingFiled 30 Sep for “Attensira vs Profound”, where this page is already the top source ChatGPT cites. Once someone pastes it and marks it shipped, that prompt is re-read at +7, +14 and +30 days.
Re-reads booked: none. Two changes were seen, but no suggestion for this page has shipped, so nothing is measured and nothing is claimed.
Attensira.com's own Profound alternatives page on 5 Oct 2026. Attribution records every version it sees, including a broken deploy, and books no verdict until a suggestion ships.
Analystattensira.com workspace, read over the Attensira MCP ·
Analyst · Matches each change to the work behind it and reads the verdict, with its n.
How does attribution work?
Seeing a change, matching it and measuring it are three separate steps, and none of them claims the change caused anything.
See the change
Your pages are read weekly, and daily while a suggestion for them is open. A new version is recorded when the title, description, headings, structured data, status or body text changes past the noise.
Match it to the work
The change is compared with every suggestion and delivery on file for that page: shipped by us, applied suggestion, close to suggestion, field flagged, draft published, or unattributed.
Re-read the prompts
The prompts it targets, or else the prompts whose answers cited the page, are re-read at +7, +14 and +30 days. Each compares a week before the change with a week around the date.
Decide once
At +30 days the answers are pooled into one before and one after, the significance test runs once, and the label is stored: moved, too early, or nothing we can prove yet.
What does a page's baseline look like before a change ships?
Attribution compares each page against its own before. These are the answers that linked four of our own pages in the last 30 days; a change to any of them is judged against this count at +7, +14 and +30 days.
- answers that linked / (www)
- 72 of 4,518
- n=4,518 answers
- answers that linked /compare
- 61 of 4,518
- n=4,518 answers
- answers that linked /alternatives/profound
- 58 of 4,518
- n=4,518 answers
- answers that linked /compare/attensira-vs-profound
- 47 of 4,518
- n=4,518 answers
Analyst · Holds the baseline per pageattensira.com workspace, read over the Attensira MCP on 4 Oct 2026 · ChatGPT and Perplexity · 24 of 31 days sampled · to Where else does the before-and-after show up?
The same verdicts feed every place that reports on work, so no page can claim more than the re-reads proved.
| Goals | One number from a fixed catalog, a target and a date. Its start is measured, never typed, and it reads ahead, on pace, behind or unmeasured every morning. Shipped changes sit beside it as markers, never as its cause. |
|---|---|
| Receipt | Every act with its status: shipped, waiting, failed or cancelled. It says no change is proven until a re-read comes back moved, and shares on a private link that lasts 30 days. |
| Morning brief | Up to three lines under “Changes we saw on your pages”, moved first. |
| Client reports | Up to ten changes matched to our work in the period, worded as their evidence card words them. |
What does attribution not claim?
A re-read shows that two windows differ. It cannot rule out a model update or a competitor's new page in the same weeks.
- It never says “because”, “thanks to” or “drove”. The change and its measurement are always two sentences.
- Seeing a change never marks a work item shipped or approves anything. A person confirms that.
- Pages are read as the HTML your server returns. Text that appears only after JavaScript runs is not seen.
- Below 30 answers in a window, the card shows the counts and no percentage.
- Page changes are in the dashboard only, not yet on the REST API or the MCP server.
What is the change being measured?
The one that shipped: here, an answer moved to the first sentence of a page. From the day it merged, the same prompts are re-read at +7, +14 and +30 days, and the verdict says moved, too early, or nothing proven yet.
Answer “Does Ledgerly send VAT-compliant invoices?” first
attensira2 checks passed
content/features/vat-invoices.mdx
- removed: Invoicing that keeps up with you.
- added: Yes. Ledgerly adds the VAT number, rate and reverse-charge note that EU invoices need.
Web engineer · Opened the changeExample · Ledgerly, a fictional brandWhat else do people ask about attribution?
Does Attensira take credit for changes it did not make?
What does “moved” mean on a page change?
How do goals fit in?
What if I make the change myself?
What is the Attensira receipt?
See what changed, and what the answers did after.
7 days free · card required