The last retainer closed with eighteen open tickets, a Drive folder nobody owned, and a monthly deck still ranking last quarter’s keywords as if they had shipped.
That is the usual wreckage when a founder picks the wrong delivery model. An seo agency vs consultant decision is not a brand preference. It is a decision about scope, access, implementation, and reporting - and who is actually allowed to change the live site when Search Console starts screaming.
We work this split every week out of the Philippines, British-led, on technical work, on-page, content, local, audits, migrations, white-label, development, and AI search. Pricing stays private because the work is scoped, not packaged. What follows is how we size the choice with the founder who has to live with it.
What the wrong model actually costs you
A consultant who cannot publish leaves strategy sitting in Notion. An agency that cannot decide leaves strategy sitting in a Slack thread with four people tagged and nobody owning the CMS.
The cost is not the invoice. The cost is the six-week lag between a finding and a live template change. Crawl budget wasted on parameter URLs. A migration that went live on a Friday because the account manager was on leave. Local pages that still cannibalise each other because keyword mapping never left the slide.
If the last engagement produced decks and not diffs, the model was wrong. If the last engagement produced diffs and no one could explain why those URLs existed, the model was also wrong. Both failures show up in the same place: organic that will not move, and a founder who now has to choose again.
Scope before anyone logs in
Scope is the first filter. Write it down before anyone asks for Search Console.
A consultant engagement is usually one senior person, a defined set of properties, and a list of decisions that person is allowed to make. Technical audit. Information architecture. On-page templates. A content brief system. A migration checklist. The edges are sharp because one person cannot hide behind a bench.
An agency engagement is usually a roster: technical, content, outreach or digital PR, local, sometimes paid sitting next to organic. Scope has to name which of those seats are in, which are out, and who signs off when two seats disagree. If scope says “SEO” and nothing else, you have bought a meeting, not a programme.
We refuse vague retainers. The document has to say which domains, which locales, which CMS, which languages, and whether implementation sits with us or with your developers. If that paragraph cannot be written in one sitting, neither model will save the quarter.
White-label work has its own scope trap. An agency reselling our technical layer still needs a named owner on their side who can grant access and ship. Without that owner, the white-label layer becomes another ticket queue.
Access, CMS, and who can ship a change
Access is where most consultant-versus-agency fights are actually lost.
A consultant with read-only Search Console and a staging login they cannot deploy is an expensive auditor. An agency with five logins spread across a PM, a tech lead, and a freelancer who left in March is a security incident waiting for a password reset.
We ask for the same stack every time: Search Console, GA4 (or the current analytics property), CMS with a role that can publish or at least open a pull request, Google Tag Manager, hosting or CDN where robots and redirects live, and the repo if the site is headless. Local work also needs Business Profile access, not a screenshot of the listing.
If your security policy will not grant that to one named person, a consultant is a poor fit. You need an agency that can work through a named technical contact on your side, with a written access register, and a revoke process when the contract ends.
If your security policy will grant it, do not hide the consultant behind an account manager. Direct access is the point of hiring one person.
Migrations make this non-negotiable. Redirect maps, canonicals, hreflang, and XML sitemaps cannot be “recommended” from outside the repo. Someone has to commit. Decide who that someone is before the DNS cut.
Implementation is the real split
Advice without implementation is a PDF. Implementation without judgement is a backlog of random tickets.
A consultant model works when your developers, or your in-house content lead, will take a spec and ship it inside a sprint. The consultant writes the change, sits in the review, and checks the live HTML. That is a clean loop. It dies the moment the developer’s priority is a product launch and SEO tickets sit in “nice to have”.
An agency model works when the agency can actually implement: template edits, internal linking, schema, content production, local landing pages, and the grunt work of cleaning parameter URLs. That only works if implementation is in the scope paragraph, not implied. Plenty of agencies sell “full service” and still file tickets into your Jira.
We treat implementation as a named line, not a vibe. Technical changes we can ship, we ship. Content we can brief and produce, we produce. What we will not do is pretend a recommendation is a result. If your stack is custom and only two people in the company understand it, say so. That pushes the model toward a consultant sitting with those two people, not a roster sending weekly status.
AI search work sits in the same split. Someone has to change how entities, FAQs, and extractable answers are marked up and written. A consultant can design that. A bench can produce it at volume. Mixing the two without saying who writes and who publishes is how you get seventeen near-duplicate passages and a thin-content problem.
Reporting that a founder can act on
Reporting is not a Looker Studio theme. Reporting is the answer to: what changed, what did we ship, what is blocked, and what decision do you need from me this week.
Agency reporting often arrives as a 30-page pack: rankings, traffic, a few competitor charts, and a slide called “next steps” that restates the retainer. Consultant reporting often arrives as a Loom and a punch list. Neither is automatically better. The test is whether you can make a decision without a follow-up call.
We keep the operating view in our seo command centre so tickets, indexation, content status, and the work that actually shipped sit in one place rather than a deck that dies in email. That is reporting as an operating system, not a performance.
Vanity rankings on keywords you do not rank for on purpose are not a KPI. Pipeline pages, non-brand clicks on money templates, index coverage, and the age of open technical debt are. If the person presenting cannot explain a movement without opening six tabs, the reporting layer is theatre.
A founder should be able to read the week’s report in ten minutes and know whether to unblock access, approve a content cluster, or kill a tactic that is about to get the domain in trouble.
When a consultant is the cleaner hire
Hire a consultant when the bottleneck is judgement, not headcount.
Typical fit: one or two domains, a CMS your team already ships on, a technical mess that needs a senior pair of eyes, a migration with a hard cutover, or a founder who wants one throat to choke and will actually read the notes.
A philippines-based seo consultant philippines search often starts here. Timezone overlap with UK mornings and AU afternoons, English as the working language, and a single senior who has done the audit, the IA, and the template work themselves. You are not buying a logo wall. You are buying the person who will argue with your developer about canonicals.
Also hire a consultant when the last agency drowned you in process. If you spent more time in status calls than reviewing diffs, you do not need more seats. You need one person with access and a written scope.
A consultant is a poor fit when you need 40 location pages a month, a link programme with actual digital PR, or three brands in three CMSs. One person will nod, then drown. That is not humility. That is maths.
When an agency bench is worth the overhead
Hire an agency when the work has volume and the volume has a calendar.
Typical fit: multi-location, multi-language, a content engine that has to publish every week, a migration that needs QA on staging plus a rollback plan, or white-label delivery for a partner who cannot staff technical SEO.
The overhead is real. You will have a PM. You will have handoffs. You will wait for the specialist who “owns schema”. That tax is worth paying only if the bench actually ships. Ask to see a recent implementation log, not a case-study slide. Who changed the robots file. Who wrote the hreflang. Who rejected a guest-post farm.
Agency structure also helps when you need cover. Consultants get sick, take leave, and sometimes get hired by a client. A bench can keep crawl fixes moving. That only matters if the bench shares a single source of truth. If every specialist has a private sheet, you have bought five consultants and called it an agency.
Watch for the model that is an agency on the invoice and a junior on the account. If the senior who sold the work never touches Search Console after week two, you are in the worst of both: agency price, consultant depth, neither’s accountability.
A philippines consultant versus a remote agency stack
Geography is not the strategy, but it is not nothing.
A consultant in the Philippines sitting UK hours can join the stand-up, write the ticket, and still be in the CMS when your European developer is online. An agency stacked across three timezones can give you 24-hour ticket movement, or it can give you a game of telephone. The difference is whether implementation is follow-the-sun or follow-the-handoff.
Language matters more than people admit. Briefs, meta, and on-page copy for PH, AU, UK, and US English are not the same job. A team that writes in the market’s English, and has a British editorial pass on the commercial pages, will produce fewer embarrassing titles than a roster treating English as a single locale.
Local SEO in the Philippines is its own product: NAP consistency, category choices, Filipino and English queries, map pack realities that do not match a US playbook. An imported agency process that ignores that will burn a quarter on the wrong landing pages.
None of that decides consultant versus agency on its own. It decides whether the people you hire can do the work in the language and hours your site actually lives in.
Keyword work sits under both models
Neither model works if the demand map is fiction.
Before we argue about consultant or agency, we run keyword research services against the live templates, the sales pipeline, and the queries Search Console already sees. That map decides whether you need one senior rewriting hub pages or a bench producing supporting articles every week.
If the research says twenty commercial templates and a thin blog, a consultant plus your writer is enough. If it says two hundred location modifiers, a comparison cluster, and a migration of old URLs that still earn links, you need production capacity. The research is the staffing plan. Treat it that way.
Do not let either model start with a keyword list scraped from a competitor. That list is not scope. It is a wish. Intent, cannibalisation, and which URL is allowed to rank for which term have to be written down, or implementation will create duplicates and reporting will celebrate the wrong page.
Tactics that get the domain in trouble
The model also has to survive a policy read, not just a pitch.
Link schemes, scaled doorway pages, expired-domain tricks, and AI content spun without supervision are how retainers turn into manual actions. We will not run them. If a prospective agency or consultant cannot sit with the Google spam policies and show where their playbook stays inside the line, they are selling you a cleanup job with a delay on it.
That document is not academic. It is the difference between a content engine and a site that disappears from the money queries overnight. A consultant who shrugs at it is a risk. An agency that hides the outreach vendor from you is a larger one.
Ask who owns disavow decisions. Ask who is allowed to buy a link. Ask what happens when a writer pastes unedited model output into a commercial URL. If those answers are fuzzy, the reporting will stay pretty until the day it is not.
How we decide fit before a scoped audit
We do not start with a roster. We start with the site condition.
Index bloat, a CMS that cannot ship, a migration date, a founder who has already burned a retainer - those facts pick the model. Then we write scope, name access, name who implements, and name the reporting cadence. Only after that do we talk about whether the work sits with one senior or a bench.
If the fit is a consultant, you get one person, direct Slack or email, and a punch list that maps to live URLs. If the fit is an agency-shaped programme, you still get a named lead, not a rotating junior, and implementation stays in the same operating view as the findings.
The next useful step is not a chemistry call with six people. It is a scoped audit on the properties that are actually in play: crawl, templates, cannibalisation, local if it matters, and a written recommendation on consultant versus bench for the next ninety days of work. If that audit says your developers can ship and the mess is judgement, we staff it that way. If it says volume and cover, we staff it the other way.
Bring the last report, the open tickets, and the CMS reality. We will tell you which model stops the wreckage, and we will not pretend a deck is a deploy.
