Skip to main content

​
Why off-site at all

When an answer engine names a product, it is usually quoting somebody else’s page — a roundup, a comparison, a README, a docs page. Fixing your own site matters and is table stakes. The rest of the work is on the sources that decide the answer, and none of those are yours. The agent works those sources in one order, and it never skips a rung to reach a lower one:
1

Proven

A source an engine already cites for your questions, that names a competitor and not you. The engine has decided it trusts this page; the only missing thing is you on it.
2

Better

A source that outranks where you are today but has not been read citing you yet.
3

New

Nothing worth joining exists. Then the move is to publish the page that would be cited — see Original pages below.

​
The rules that bind every off-site channel

These hold on every channel — email, directories, repositories — and they are enforced in code, not by instruction.
  • Nothing is ever sent from an Attensira domain on your behalf. Mail goes from your own connected Gmail or Outlook, or it does not go.
  • The first sends on any channel are yours. Until ten pitches have gone out from your mailbox by hand, no pitch sends on its own; until you have approved one directory listing, no listing is filed on its own. Approving one channel does not unlock another, and one workspace never unlocks another.
  • A daily cap per channel, per workspace. Two pitches a day, three directory listings a day. It applies to you as well as to automations, and rolls over at midnight UTC.
  • A listing always waits for you. A directory listing publishes claims about your product under your name, and claims are never published unattended in any mode, including act mode.
  • Community posting is never unattended. Reddit, forums and Q&A answers are drafted for you to post, always.
  • Replies land in your mailbox, because that is where the conversation is. We never answer one for you.

​
Directory listings

When the deciding-sources map shows that a directory decided answers to your tracked questions, Attensira prefills that site’s submission form from your brand profile — name, tagline, category, pricing, logo, website — attaches the citation counts that make the case, and puts it in your Inbox. It knows the forms for G2, Capterra, GetApp, Product Hunt, AlternativeTo, Clutch and Slashdot. Anything the brand profile cannot answer is left blank and named as blank. We do not guess a logo URL or invent a category. Fill those in on the Knowledge page and the next listing carries them. On your approval, we submit through a connected integration where one exists. Where none does — which is every directory today — you file it and mark it sent, and we take it from there.

​
How a placement is verified

A placement is verified only when both of these are true:
  1. The page shows you. We fetch the page and look for your brand name in its text or a link to your domain. We record which one we found.
  2. An answer cited it. The page’s URL turns up in a reading’s citations, on a day after we did the work.
If the page shows you and nothing has cited it yet, the placement is placed — dated, honest, and re-checked daily for sixty days. It becomes verified when, and only when, an answer cites it. If the page does not show you, nothing changes, however often an engine cites that page. An engine citing a page you do not appear on tells you the engine likes the page, not that the placement exists — a directory that quietly rejected a submission still gets cited every day. The same rule applies to code: a merged pull request is not a deployed page, so we read the live URL before anything counts. Verification only moves forward. A page that returns an error today does not undo a placement confirmed yesterday. When a placement is verified, we schedule a re-read of your answers so we can tell you honestly whether it moved anything.

​
Pitches

When a source an engine cites names a competitor and not you, the agent reads the page, finds who runs it from the page itself, and writes the pitch. What the pitch carries is evidence, not adjectives: the verbatim answer passage that cited the page, the URL of the source, and the one page of yours that answers what its readers came for. The draft is under 150 words, makes one ask, and is signed by a real person from your profile. Where the draft goes. It lands on an Inbox row you can read and edit. From there, press Save as Gmail draft or Save as Outlook draft and it appears in your own Drafts folder. You send it. Sending it for you. With the workspace in act mode, and after the first ten have gone out by hand, and while there is room in the day’s two, the agent can send the drafted pitch from your own connected mailbox. Anything else refuses and says which of those it was. Sending cannot be undone, so it is the one capability that is off unless you turn it on — see Approval and modes. What happens next. Once a day the agent checks your mailbox for a reply to each pitch it sent. When one arrives, the row moves to replied and a line appears in Needs you. It reads that a reply exists, who from and when — never the reply itself, and it never writes back. Who we never write to. Anyone who has opted out, any address on a domain that has declined, and any market where prior consent is required and we do not have it. One email per site, one follow-up at most, never a third.

​
Entries in other people’s repositories

Some of the pages engines read are files in repositories: a curated awesome- list, another product’s README, an ecosystem or integrations page in somebody’s docs. A merged one-line entry there is a citation with no editor to persuade. The agent reads the file, reads its CONTRIBUTING.md, checks the list’s own stated criteria against your profile, and writes the single row in the file’s own format. Then one of two things happens, and the Inbox row says plainly which:
  • Your connected GitHub account opens it. If the account you connected has permission to open a pull request on that repository, the pull request is opened from your account, under your name.
  • You open it in one click. Otherwise — and this is the usual case — the row carries the exact one-line diff plus a prefilled GitHub edit link. We are not installed on somebody else’s repository and cannot open a pull request there for you, so we do not pretend to.
This is draft-only in every mode. Act is a standing permission over your own site; a stranger’s repository is not that, and no standing yes covers it.
We change one line. We never reorder or reformat a file, never remove somebody else’s row, never open a second pull request while one of ours is open there, and never chase a maintainer with an issue or a comment. Whether it merges is theirs to decide.

​
Original pages worth citing

When nothing third-party is cited for a question at all, there is nothing to join. The move is to publish the page that would be cited — and to build it out of something nobody else has: what we have actually read for you. Two shapes, and only two:
  • A data page, answering a question with counts from your own readings — what four answer engines said about something, across a window, with the sample size.
  • A reference page, defining and organising something the category argues about, with each definition attributable.
Every claim carries its source — a reading id from your own history, or a public URL read while writing it. A sentence with no source is deleted rather than softened, and a draft with fewer than three sourced claims is not written at all. The method comes before the numbers: what was asked, of which engines, over what window, how many samples. Every count carries its sample size in the sentence itself, not in a footnote. How it ships. Through the same path as any other change: a pull request against your repository, with your documentation site treated as a first-class target rather than a fallback, because engines cite docs. With no repository connected, the full draft lands in your Inbox with the path it wants. How it gets found. Once the page is live, it becomes the thing the pitches point at. Never before — a pitch pointing at a page that is not there yet costs you the contact.

​
Where to see it

Every off-site act is on your private receipt: what was drafted, what was sent, who replied, what was placed, and what a later reading verified. A placement counts as verified only when the page itself shows you and the URL later turns up in a reading’s citations. A merged pull request is not a live page, and we check the live page.