Distribution · indexing · measurement

Distribution: making what you published get read

Most companies do not have a content problem. They have a distribution problem: the work exists, and no machine or human has been given a reason to find it.

What the distribution pass includes

Make it findable

Sitemap in shape, IndexNow ping on publish, internal links from pages that already have authority, canonical tags that point home.

Make it quotable

Structured data (Service, Offer, FAQPage), a clean answer at the top of the page, and llms.txt so assistants know what the site is about.

Make it arrive

Publish where the audience already reads, adapted to the platform instead of pasted, with canonical pointing back to the money page.

Make it measurable

One event per intent, one report per page. If a page has no event, it has no verdict.

It is running on this site right now

Everything on this page is a description of a live setup you can inspect in one click.

sitemap.xml — the page inventory, extended on every publish.
robots.txt — written to let AI crawlers in, deliberately.
llms.txt — what this site is and where the offer lives.
What shipped — the artifact list with live links, updated as work lands.
A free tool — the kind of asset that earns links instead of buying them.

Distribution is part of every package: it is line item 3 of the Engine and line item 2 of the Full build on the turnkey page.

Questions people actually ask

What is distribution as a service?

Getting the pages, articles and tools you already paid for in front of people: indexing, internal linking, submission to AI crawler feeds, publishing where your buyers already read, and repurposing into formats that platform actually rewards.

Why is publishing not enough on its own?

A page nobody links to and no crawler has been told about is a file on a server. Indexing ping, internal links, structured data and one honest distribution channel are what turn it into traffic you can measure.

How do you know it worked?

Two places: index status per URL and the analytic report by page. Both are readable, both are on my own properties — the report is visible on the what-shipped page.

The five receipts, written out

This page describes the pass; the mechanics are published in full with live numbers: Publishing is an event. Distribution is a receipt. — the canonical tag that keeps the original on your domain (40 of 75 articles on my own account point theirs here), the IndexNow ping, the internal link an orphan page never gets, the machine-readable layer, and the one measurement that surprised me: 105 UTM hits in a day of server log against 7 analytics sessions, because crawlers do not run JavaScript. The machine-readable index of everything published is in llms.txt.

Next step

Tell me what you sell and what you have already tried. I answer with a fixed scope and a price, not with a call to "explore synergies".

Message on Telegram Read the scope of work

Marketing engineer for B2B — the lead, source and reply definitions that decide whether a channel can be judged, the five things that exist before the first send, and the floor an honest test needs.

Marketing engineer job description — the four decisions and six lines to write instead of a tool list, the artifact due each week, the volume a strict test needs, and a free generator.

Marketing engineer retainer — the invoice line by line, the four decisions a retainer cannot make for you, and how many honest tests a month can actually hold at your volume.

Marketing engineer for fintech — why the readable unit sits after identity and funding, the volume a verdict needs, and the stop rule that has to exist before the spend.

Marketing engineer for devtools — why the readable unit is the first successful call rather than the signup, the volume a verdict needs, and the stop rule that has to exist before the spend.

Marketing engineer interview questions — the six questions that separate an engineer from a marketer with tools, what each answer really measures, the volume a verdict needs (13,914 contacts per arm; 27,828 in total), and the four things the interview cannot decide.

Marketing engineer for marketplaces — two funnels that must be readable at the same time, liquidity as the readable unit, why each side needs its own floor (13,914 per arm; 27,828 in total; 70 months for a 400-seller-a-month supply side) and the four decisions taken before the first contact.

Marketing engineer for agencies — an agency cannot pool its clients' traffic, so every client needs its own floor and its own read-out date: 13,914 per arm (27,828 total), 14 months for a client at 2,000 contacts a month, and 4,638 contacts a month as the smallest client readable inside 6 months.