TL;DR
Every white label arrangement has a line in it, and where exactly it sits is usually never discussed. The default is right: the agency owns the client completely and invisibility is the product. The cost is two hops per question, with detail lost at each. Negotiate three exceptions before starting.
Every white label arrangement has a line in it. On one side the agency owns the relationship; on the other the specialist does the work. Where exactly that line sits is usually never discussed, and it is the thing that determines whether the arrangement lasts.
I have worked on both sides of it. Here is what actually goes wrong.
The default, and why it is right
The agency owns the client. Completely. All communication, all reporting, all commercial conversations, all bad news.
That is what the agency is paying for. If the specialist appears, the agency’s value is visibly diminished. The client starts wondering what the middle layer does, and the honest answer becomes harder to give.
So the default is total invisibility, and I hold to it hard. The client never knowing I exist is the product, not an inconvenience.
Where the default costs something
Being honest about the trade, because it is not free.
Every question takes two hops. Client asks the agency, agency asks me, I answer, agency relays. A question that would take ninety seconds takes two days, and detail is lost at each transfer.
Technical questions get garbled. Not through incompetence. Through translation. “Why isn’t the page indexed” becomes “the client wants to know why Google hates them”, and the answer comes back through the same filter.
That particular question is a good example of why the translation matters. “Not indexed” covers several genuinely different states, and Google’s own documentation distinguishes them: discovered but not crawled is a queue problem; crawled and not indexed is a quality judgement. Those have different answers and different timelines, and the distinction does not survive being relayed by somebody who does not know it exists.
Speed suffers, and speed matters. MIT’s study of 15,000 leads and 100,000 call attempts found the odds of qualifying a prospect dropping twenty-one-fold between a five and a thirty minute response. That is about sales rather than support, and the principle transfers: a relay adds delay, and delay costs something real when the question is urgent.
The exceptions worth negotiating up front
Three, and agreeing them at the start prevents the awkward version later.
Talking to the developer. Not the client, but the client’s developer. This is the one I ask for most and it is the one that saves the most time. A technical instruction relayed twice arrives wrong, gets implemented wrong, and then somebody has to work out why the fix did not work.
The compromise that usually works: I join a call as a member of the agency’s team, or I write the ticket and the agency sends it. Both keep the boundary and remove the translation layer.
Access. Search Console, analytics, the CMS. This should not be negotiated per request. Agree at the start that the specialist has read access, or accept that everything takes an extra day.
The awkward finding. Occasionally the honest diagnosis is that the previous work, sometimes the agency’s own work, caused the problem. Agree in advance how that gets handled, because discovering it mid-engagement with no protocol is where relationships break.
What I will not do
- Pretend to be an employee to the client’s face. Invisible is fine. Actively claiming to be staff is a lie I would have to maintain, and I will not.
- Undercut the agency. If a client works out I exist and approaches me directly, the answer is no, and I tell the agency it happened.
- Present work I disagree with. If the agency has promised something I do not think is achievable, I say so before it goes to the client, not after.
The failure I see most
Not a breach of the boundary. It is the agency using the boundary to avoid learning anything.
An agency that relays questions without understanding them cannot evaluate the work, cannot defend the recommendations, and eventually cannot justify its margin. The boundary is supposed to protect the relationship, not replace the agency’s judgement with a forwarding address.
The arrangements that last are the ones where the agency gets better at SEO over time. The ones that end are the ones where the agency stays a relay and gradually notices it is paying for something it could buy direct.
The short version
- Default: the agency owns the client completely. Invisibility is the product.
- The cost is two hops per question, and detail is lost at each.
- Negotiate three exceptions up front: the developer, access, and the awkward finding.
- Joining a call as the agency’s team keeps the boundary and removes the translation.
- Never claim to be staff. Invisible is not the same as lying.
- Never undercut, and say so if approached.
- The boundary must not replace the agency’s judgement. That is how these arrangements die.
This is how I work with agencies. White label SEO covers the arrangement, the boundary and what each side owns.
