01
Agencies needing execution
White-label delivery under your brand. No named account in the record; /for-agencies has the terms.
Not in the record
How white-label delivery runsService 08Delivery and record-keeping
Every item is logged against seven fields as it moves, so the campaign can be read at any point without anybody having to reconstruct it.
7 of 18 rows are live — the other 11 are not reportable yet
Client, month, target page, anchor, source and final live URL — the record the portfolio figures are read off.
Somebody reconstructs the last four weeks from memory and an inbox, and the number is different every time.
A placement counted when it was commissioned, which is how a report claims things that are still drafts.
You can see that links were built and not which of your pages they were built for.
The distribution becomes whatever it became, and nobody can tell you what it is today.
A piece is pulled or edited months later and the report still counts it, because nothing was ever checked twice.
The relationship ends and so does any account of what was done, which makes the next campaign start from zero.
Drag the divider — or use the arrow keys
01
White-label delivery under your brand. No named account in the record; /for-agencies has the terms.
Not in the record
How white-label delivery runs02
Service-area pages that each need their own authority, not one campaign stretched thin.
In the record
03
Products whose buyers search the problem long before they search the category.
In the record
04
One chain per market: the service, the city, a topic that belongs to both.
In the record
05
Category pages competing against directories and every other agency in the city.
In the record
06
Community and development pages, where the market name is the search.
In the record
Client, month and target page recorded when the item is ordered — not when it lands, by which point the intent has been forgotten.
Taken from the campaign's planned distribution and stored beside the destination, so the plan and the profile stay the same document.
The publication section the placement is going to, which is what makes duplicate approaches visible before they happen.
Ordered, drafted, placed, live. Four states rather than a tick, because "delivered" covers three very different situations.
The published page opened, the anchor read, the destination followed. The final URL goes in and the row closes.
Cut by market, by target page, by anchor type or by month — which is where an uneven campaign becomes visible while it is still fixable.
ResultA verified live URL, logged against the campaign.
Every row is an artefact — something you are holding at the end of a week. None of them is an outcome, because an outcome is not something a supplier can hand over.
One row per placement, seven fields, maintained as it moves. Everything else on this page is a view of it.
Which of your pages each placement was built for. Without it a campaign cannot be judged, only counted.
The exact phrase used, stored at placement time. Reconstructing a distribution afterwards is guesswork with a spreadsheet around it.
The publication section approached, so the same one is never worked twice for the same client by accident.
Ordered, drafted, placed, live — so a monthly figure means one specific thing rather than whichever of the four is convenient.
The verified page. Nothing without one is counted, which is the single rule that makes the totals defensible.
Orders and live placements per client per month, which is the cut that shows cadence rather than accumulation.
541
14
8
190
This is the record itself: ten campaigns, summed at render time from the same sheet every figure on this site is read off. It holds delivery data — no rankings, no traffic, no revenue.
34
Tracked placements
Markets tracked in a single month
Garage-door repair and local service discovery. One product, opened into the questions its buyers were already asking somebody else.
See the delivery ledgerClient, month, target page, anchor text, source section and final live URL, plus the status the item is at. Those fields are what let a campaign be read months later by somebody who was not there.
When it is live and has been opened. Ordered, drafted and placed are tracked as separate states precisely so that a monthly number cannot quietly include work that has not been published.
Yes. It is the reporting, rather than the source of a report — the same sheet, not a formatted summary of it. It stays yours if the engagement ends, which is the point of keeping it this way.
As items move, not on a monthly cycle. A record updated in a batch at month end is reconstructed from memory, which is the failure this whole discipline exists to prevent.
It is recorded as what it now is. A publication can edit or remove a piece at any time and no supplier controls that — what a record can do is stop counting something that is no longer there.
Yes, and that is the main reason for the field structure. Cut by target page it shows which of your pages have been supported; cut by market it shows the city that has been ignored for four months.
No. The record is a delivery record. Ranking and analytics data live in your own tools and would need a separate evidence layer — presenting delivery data as performance data is the most common dishonesty in this industry.
No. What this service guarantees is that you can see exactly what was done, where it went live, and which of your pages it was for. That is accountability, which is a different thing from a promise.
Still something here unanswered?
Send the question with the domain and the page it is about. It is read the same day, by me — there is no auto-responder.
Start here
Send the campaign you are currently running and whatever record exists for it. The reply says what can be reconstructed, what cannot, and what to start recording from this month.