SEO Freelancer, Agency or In-House: Which Should You Hire?

Define the gap before comparing proposals

If a developer is waiting for a clear technical brief, buying a package of monthly articles will not resolve the delay. If you have a sound strategy but nobody to implement it, a purely advisory engagement may also leave you stuck.

I ask a prospective client what is already available: developer time, writers, product knowledge, analytics access and someone who can approve changes. Then I separate the missing decisions from the missing production capacity. This often changes the type of support the business should buy.

Write a one-page brief covering the commercial objective, current evidence, constraints and available team. Include what you do not need. That makes proposals easier to compare and reduces the chance of being sold a familiar package that does not fit the problem.

Compare the four working models

These are not rankings. An agency can provide excellent senior access; a freelancer can outsource heavily; an internal specialist may still need outside technical help. Look at the proposed arrangement rather than assuming a business model determines quality.

A hybrid can work well too. Your internal lead may own priorities while a consultant reviews difficult decisions and an agency handles production. It only works if responsibilities are explicit and the same work is not being commissioned twice.

Separate advice from implementation

For a consultancy engagement, I would make the output concrete: diagnosis, priorities, a decision on what not to do, implementation briefs and an agreed review point. A document alone is not enough if the team cannot translate it into work.

Ask whether recommendations include acceptance criteria. “Improve internal links” is vague. Naming the affected page group, intended destination, template change and verification method gives a developer something testable.

My DAAOMI framework means Discover, Analyze, Audit, Optimize, Monitor and Improve. In a consultancy brief, that translates into understanding the business, examining demand and the site, setting priorities, guiding changes and reviewing what happened. Your team can own implementation while I support those decisions.

If you need someone to write, edit, configure tools or deploy changes, put that in scope. Do not assume it is included because a proposal says “SEO management”. Equally, an advisory service should not be judged as a failed production service when implementation was never commissioned.

What I would agree before an SEO engagement starts

Ask who will do the analysis, who can change the website and which decisions need your approval. Agree the first deliverable, reporting format, communication schedule and access arrangements. An activity list without ownership can leave both the consultant and your internal team waiting for the other to act.

When evaluating a proposal, ask to see relevant completed work and how its outcomes were measured. Ask what happens when development capacity is limited or evidence changes the initial plan. I would make commitments about the work, communication and review process rather than promise a fixed search position.

• Keep business accounts and access under your ownership.
• Agree implementation responsibilities and approval limits.
• Define useful reporting and the next review point.
• Clarify handover, documentation and what is outside scope.

Ask questions that reveal how the work will run

• Who reviews my website personally? Ask for the named lead and the people doing the work.
• What do you need from my team? Developer access, approvals and expert input should be discussed early.
• What happens in the first stage? Look for a diagnostic process tied to your situation, not a predetermined list of fixes.
• How do you prioritise? Ask how commercial value, risk and implementation effort affect the order.
• What remains owned by my business? Clarify accounts, data, content and access when the engagement ends.
• How will we review progress? Agree the business measures, reporting context and next decisions.

Ask for a sample of a redacted brief or report where confidentiality permits. You are looking for clarity, not the length of the document. A short set of precise decisions can be more useful than a large automated audit with no owner attached to the findings.

Read case studies carefully

Relevant evidence includes the starting situation, work completed, timeframe and measurement definition. A traffic increase is useful context, but it does not tell you profit, lead quality or which other changes happened at the same time.

Use my published case studies in that way: as examples of completed work to discuss, not a forecast for your site. Ask what resembles your situation and what does not. A small local service business and a large product catalogue need different operational capabilities.

I have worked in search marketing since 2008. That experience informs my judgement, but it should not replace questions about the actual scope you are buying. You can read more about my background on the about page.

Compare total delivery cost, not only the retainer

A lower retainer can still require substantial internal writing and development time. A higher proposal may include production you already have. Put the costs beside the responsibilities before deciding which is better value.

Clarify meetings, implementation, revisions, tools, reporting, contract length and handover. Ask how out-of-scope work is approved. For an internal hire, allow for recruitment, management and any specialist support the role will need.

I prefer a scope that the client can explain back in plain language: what I will do, what their team will do and how we will decide the next step. If that remains unclear after the proposal discussion, the engagement needs more definition.

Ask how AI is used and checked

AI use is not a separate hiring model. Ask which tasks use it, who verifies the output and how confidential information is handled. A provider should be able to explain the difference between a research aid and a source of verified facts.

For content, request the review process for product claims, experience and subject-matter accuracy. For analysis, ask how recommendations are traced back to your actual data. The useful outcome is better decisions and reliable delivery, not a larger number of machine-produced pages.

What I would agree before an SEO engagement starts

Ask who will do the analysis, who can change the website and which decisions need your approval. Agree the first deliverable, reporting format, communication schedule and access arrangements. An activity list without ownership can leave both the consultant and your internal team waiting for the other to act.

When evaluating a proposal, ask to see relevant completed work and how its outcomes were measured. Ask what happens when development capacity is limited or evidence changes the initial plan. I would make commitments about the work, communication and review process rather than promise a fixed search position.

• Keep business accounts and access under your ownership.
• Agree implementation responsibilities and approval limits.
• Define useful reporting and the next review point.
• Clarify handover, documentation and what is outside scope.

Common questions