We draft the issue, you publish it
A newsletter issue built from your own scan, published under your name
Your scan produces numbers nobody else in your category has. On Dominate we draft a newsletter issue from them, and you publish it under your name.
Every plan queries all 5. See how each engine picks who it names
LinkedIn
The buyer behind the reader
of B2B buyers now use AI somewhere in their buying process (Forrester, 2026). An issue that sits at a public, indexed URL is one more place those systems can find your argument.
The gap this closes
- Most B2B newsletters die at issue four because writing one takes a morning nobody has.
- The ones that survive are opinion with nothing measured inside them.
- A brand account accumulates posts. A named person accumulates authority.
- Most founders cannot tell whether the engines read newsletters in their category.
What you end up with
- An issue drafted from your own scan findings, on Dominate.
- Numbers your readers cannot get anywhere else, which is what keeps a list subscribed.
- The issue published by you, on your platform, under your name.
- The Sources pane telling you whether newsletter domains get cited in your category.
How it works
We draft. You edit and publish.
The scan produces the finding
Each scan stores every answer word for word and computes your Tofu Index and, on paid plans, your Bofu Index. What moved since last time, and the answer that explains it, is the subject of the issue.
The Content Engine drafts the issue
On Dominate the issue is drafted from that finding. It carries a subject line phrased the way a buyer asks, one concrete example, and one link back to the page on your site that answers the query in full. It sits in the Content Engine as a draft.
You publish it where your readers are
Copy it into your LinkedIn newsletter, Substack or Beehiiv and send it. We do not run your list, and we never post for you. The next scan re-asks the same queries on all five engines, so the following issue has its own finding to report.
What you get on each plan
Newsletters are one of the three things the Content Engine drafts, beside blog posts and video scripts. The monthly issue count below is read live from the plan configuration.
Track
Free- No drafting on this tier
- The buying queries where a rival was named instead of you
- The verbatim answers, which are an issue's raw material
- Your Tofu Index across every engine, the number an issue reports
- The Sources pane, including any newsletter domains the engines cited
Fix
$99/mo- Still no newsletter drafts: Fix drafts blog, FAQ and comparison pages
- Weekly scans give you a fresh finding every week
- The Bofu Index joins the Tofu Index, from head-to-head comparisons
- The pages an issue links back to get drafted here
Dominate
$499/mo- Newsletter issues drafted from each scan's own findings
- What moved, which queries you started winning, which rival gained
- Subject line phrased the way a buyer would ask
- One link back to the page on your site that answers in full
- You publish on LinkedIn, Substack or Beehiiv, under your name
Rule
$1999/mo- Dominate's numbers, with our team doing the work
- We prepare each issue for your review
- You still publish it from your own account
Rule carries Dominate's numbers with our team doing the work, and is sales-assisted.
Which engine actually leans on this
Your row is Newsletters. The rest of the grid is on the engines page.
| Channel | ChatGPT | Claude | Perplexity | Gemini | Google AI Mode |
|---|---|---|---|---|---|
| Your own site Schema, answer pages, llms.txt, crawlability | Heavy Vendor | Heavy Vendor | Heavy Measured | Heavy Our read | Heavy Vendor |
| Reviews and directories G2, Clutch, Capterra, Trustpilot, Google Business | Moderate Our read | Light Measured | Heavy Our read | Moderate Our read | Moderate Measured |
| Reddit and forums Unpaid opinion, where buyers go for the unvarnished view | Light Our read | Light Measured | Heavy Our read | Moderate Our read | Heavy Measured |
| Video YouTube. Only counts once there is a transcript | Moderate Our read | Light Our read | Moderate Our read | Heavy Our read | Heavy Measured |
| Newsletters LinkedIn, Substack, Beehiiv. Published under a named person | Moderate Our read | Light Our read | Moderate Our read | Heavy Our read | Heavy Measured |
| News and PR Earned coverage, wire pickup, journalist mentions | Heavy Vendor | Heavy Vendor | Heavy Our read | Moderate Our read | Moderate Our read |
Your own site. Your own site counts most for ChatGPT, Claude, Perplexity, Gemini, Google AI Mode.
Reviews and directories. Reviews and directories counts most for Perplexity. It is a light signal for Claude.
Reddit and forums. Reddit and forums counts most for Perplexity, Google AI Mode. It is a light signal for ChatGPT, Claude.
Video. Video counts most for Gemini, Google AI Mode. It is a light signal for Claude.
Newsletters. Newsletters counts most for Gemini, Google AI Mode. It is a light signal for Claude.
News and PR. News and PR counts most for ChatGPT, Claude, Perplexity.
Where this comes from
- OpenAI: publishers and developers FAQ States that a site must allow OAI-SearchBot to be eligible for ChatGPT search at all.
- OpenAI: introducing ChatGPT search The named publisher partnerships behind the news and PR row.
- Anthropic: web search tool documentation Citations are always enabled. Left to itself Claude decides when to search; our scans force the search on every query.
- Google Search Central: AI features and your website AI Overviews and AI Mode report inside the ordinary Search Console Performance report.
- Search Console Help: impressions, position and clicks How AI Mode counts a click, and why a follow-up question is treated as a new query.
- Dan Petrovic: citation mining of OpenAI grounding metadata Reddit retrieved in 76 percent of OpenAI searches and selected 0.61 percent of the time.
- Our production scan database, read 12 August 2026 46 completed reports, 34 brands, 419 buying queries, 2,421 answered buying cells. Where the per-engine mention rates come from.
- Our 15-region managed services study 743 records, 566 named by an engine, and the per-engine corroboration rates.
- What our crawler finds on real sites 39 readable crawls: 38 with no llms.txt, 26 with no FAQ schema, 16 with no Organization schema.
- How we check an AI visibility report The method behind every first-party number on this page, including what it cannot show.
Engine behaviour moves month to month. This table is maintained, not published once.
The proof, including the parts that flatter nobody
We publish our own scan numbers, so here is the starting line an issue reports from.
Across the 46 completed reports behind this page, Perplexity named the brand in 7.4% of the buying queries we put to it, on firms that arrived already suspecting they were missing.
Every other engine sat between 0.4% and 4.0%, on the same firms that suspected they were missing.
What we cannot show you is a controlled result for newsletter publishing. We do not instrument LinkedIn, Substack or Beehiiv, and we will not invent an attribution model to fill that gap.
What the product does show is narrower and real: whether a newsletter domain was among the cited sources for your queries, and the same queries re-asked on all five engines, scan after scan.
Read the MSP AI Visibility Report 2026 →A worked example: an issue drafted from a scan
The shape of an issue drafted for a founder whose scan showed a rival named on most engines for a compliance query. The brand, the rival and the numbers are illustrative. The structure is what a real draft carries.
Subject and opening
- Subject: Why the compliance query decides your shortlist before anyone calls you
- Opening: This week we asked every major AI engine which provider a 40-person accounting firm should hire for SOC 2 readiness. Most of them answered. None named us. Three named the same national provider, and one of those answers said exactly why.
- Turn: The answer told buyers to look for prior work in professional services and a named compliance lead. We have both. We had never written either of them down anywhere a machine could read.
Body
- The criterion the engine stated, quoted in full, because it is the buyer's criterion and not ours.
- What we do about it, with the evidence named: the audit pack, six years of log retention, one named lead per client.
- The admission: this was true for two years and invisible for two years, which is a publishing failure rather than a service failure.
- One link to the page on our site that answers the query in full.
- Next issue: whether the page moved the answer, from the next scan.
The issue works because it reports something that happened. It has a date, a method, a quote and an admission. Those four properties make a passage safe for an engine to quote, and worth a reader's two minutes. The last line sets up the next issue, which the next scan will write the evidence for.
How it actually works
The mechanism, for anyone who wants it. Open a card to read the detail.
What a published issue does for an engine
An issue on LinkedIn, Substack or Beehiiv lives at a public URL, on a domain whose reputation you did not have to build. When an engine searches the web for your topic, that page is a candidate in a way a three-month-old company blog may not be.
Read the detail
Every engine we query searches the live web before it answers, so a public page is something it can actually find.
The honest limit sits right beside it:
- These platforms restrict automated reading in different ways.
- How much of a given issue an engine sees varies by platform.
- So treat an issue as a second home for your argument. The first home is the page on your own domain that answers the query in full, which is why every draft links back to one.
You do not have to guess whether newsletters matter in your category. The Sources pane on every scan lists the ten domains the engines cited most for your queries, with the cited URLs under each.
- If substack.com or a LinkedIn article shows up there, the format is being read for your buyers' queries.
- If it stays absent, the issue is distribution to people, which is still worth something. The citation work belongs on your site.
Why the byline has to be a person
A logo has no history of being right, and nothing that carries from one issue to the next. A founder publishing on one topic, month after month, under their own name, builds an association between that person, that topic and the firm behind them.
Read the detail
That association is what any reader, human or machine, leans on when deciding whom to believe.
It is also why we draft and you publish:
- The draft saves the morning.
- The decision to put your name on it, and the edits that make it sound like you, are the part that compounds.
- Handing that to a vendor would hand away the one asset the format builds.
Consistency beats volume by a wide margin. An issue after every scan for a year builds a recognisable body of work. Eleven issues in March and silence after that builds an archive, not a reputation.
An issue reports, a blog post answers
The Content Engine drafts three kinds of thing, and each has a different job:
Read the detail
- A blog post, FAQ page or comparison page answers one buying query completely, on your domain, so an engine can lift the answer.
- A video script puts the same answer into a transcript on a platform Google owns.
- A newsletter issue reports what changed, to people who chose to hear from you.
Keeping those jobs separate stops a newsletter turning into a link roundup. The issue argues one point from one finding and sends the reader to the page that does the answering.
The page is the asset an engine cites. The issue is how your market hears about it, and occasionally a second place the engines find the same argument.
All of it is written to get you cited rather than liked. An issue engineered for opens and shares delays its point to hold attention. An issue built from a scan finding states it in the first paragraph, because that finding is the reason anyone opened it.
See where you stand first
Run a free scan and find out which of these gaps you actually have.
Get your free auditFrequently asked questions
Do you run my newsletter?
No. On Dominate we draft each issue from your scan findings, and you publish it on your own LinkedIn newsletter, Substack or Beehiiv. We never hold your subscriber list and never send on your behalf.
Which plan drafts newsletter issues?
Dominate, and Rule, which carries the same numbers with our team doing the work. Fix drafts blog posts, FAQ pages and comparison pages but no newsletter issues. The plan cards above read the live configuration, so the counts there are current.
Do the engines read newsletters?
Some issues, on some platforms, some of the time. Each platform restricts automated reading differently. The Sources pane on your scan settles it for your category: if a newsletter domain is among the ten domains the engines cited most for your queries, it lists the cited URLs.
LinkedIn, Substack or Beehiiv?
LinkedIn for most B2B founders, because your buyers already read there. Substack or Beehiiv if you want a list you own outright, with the email addresses in your hands. The draft works on all three.
Why publish under my name and not the company's?
Because a logo accumulates nothing. A named person publishing on one topic over time builds the association a reader leans on when deciding whom to believe. That association transfers to the firm.
I barely have any subscribers. Is it worth it?
The issue is worth writing for the finding alone, and a public issue is readable by a search engine whatever your subscriber count. The audience compounds later; the habit starts with the first one.
Sources and further reading
- Forrester B2B Buying Study 2026: 94% of B2B buyers use AI in the buying process; 2x now cite AI as a top information source.
- Kevin Indig, 30k-citation study (via G2): 10% more reviews correlates with roughly 2% more AI citations, an association rather than a mechanism.
Related solutions