Skip to content
Marc Nashaat Consulting Start a conversation

What an SEO consultant does & when you should (or shouldn’t) hire one

An SEO consultant diagnoses why a site underperforms in search and works with your teams until the fixes ship. The useful question isn't what they do. It's whether you have the capacity to use one.

Whether hiring an SEO consultant is worth the money comes down to one thing; it isn’t seniority or the day rate. It’s whether the person produces findings or produces changes. Findings are cheap and plentiful. Changes are neither.

The work of an SEO consultant is advisory and hands-on in roughly equal measure. Diagnose why a site underperforms in organic search, decide what to do about it and in what order, then stay alongside the marketing and engineering teams until those changes are live. What it isn’t is production (a consultant doesn’t replace the people who write, build and ship).

Consultant versus agency versus in-house hire

These three solve different problems and get bought as though they were substitutes.

An agency sells capacity. Several people, a process, ongoing execution across content production, link acquisition, reporting and campaign management. The right answer when you need volume of work delivered and have the budget to match. The structural weakness is that the senior person who won the account is rarely the person doing the work six months later.

A consultant sells judgment. One senior person, engaged directly, on a narrower set of problems. The right answer when the questions are architectural or strategic: a replatform, a stalled program, an estate nobody understands end to end. The structural weakness is finite hours, because a consultant can’t also be your content team.

An in-house hire sells presence. Somebody in your standups, your planning and your Slack, accumulating context no external party can match. The right answer once search is a permanent function rather than a project. The weakness is that a good senior hire is hard to find and takes months to land, and a junior one gets outranked by everybody whose roadmap they need to influence.

The combination that works is a consultant to set direction and get the first difficult changes through, an in-house owner to hold it, and agency capacity for the production. The pattern that doesn’t work is hiring an agency to answer an architectural question, because the answer might be that six months of their retained production was the wrong thing to buy.

Getting that sequence wrong costs more than it used to. Gartner’s 2025 CMO Spend Survey found 59% of the 402 marketing leaders surveyed reporting insufficient budget to execute their strategy, with roughly two in five planning to reduce agency spending. There is no slack to absorb a wasted retainer.

What a fractional SEO engagement looks like week to week

Stripped of the proposal language, an embedded engagement is mostly meetings and tickets. A typical sprint looks like this.

A standing session with engineering. Reviewing what’s in flight, checking that acceptance criteria still say what they need to say, and answering the questions that would otherwise stall a ticket for a sprint.

Writing and refining tickets. Not recommendations, tickets, in your tracker, with acceptance criteria a developer can test against and a rollback note. Most of the value gets created here and none of it shows up in a report.

Reviewing what’s about to ship. Staging crawls, rendered-output diffs, and catching the template change that quietly dropped the canonical tags before it reaches production (which is three weeks before anybody notices).

One piece of deeper analysis a fortnight. Logs, a query-level cut, an internal link audit. This is the work that generates next quarter’s priorities.

A monthly session with whoever holds the budget. What shipped, what it did, what’s blocked and who needs to unblock it. Half the job is making a blockage legible to somebody with the authority to clear it, and I spend more time on that than on analysis.

Two to four days a month is a normal shape once the initial diagnostic is done. That band describes the engagements I’ve run rather than a market rate, and it won’t hold for every scope. A migration month is heavier and a maintenance month lighter.

How to tell a good SEO consultant from a bad one

Most of the signals show up in the first conversation.

A good one asks about your release process and your org chart before asking for analytics access, because they know the constraint usually lives there. They’ll decline work, or tell you the thing you want isn’t the thing you need. They give you a position, meaning a clear recommendation with the trade-off named, rather than a list of options weighted by your apparent preferences. They talk about something they got wrong, unprompted. And they’re specific about mechanism: not that rankings improved, but what changed, why it worked, and what they expected that never happened.

The warning signs are equally consistent, and Google publishes most of them. Its guidance on hiring an SEO states that nobody can guarantee a number one ranking, and tells you to be wary of anyone claiming guaranteed rankings, a special relationship with Google, or a priority submit. Add the rest from experience. A deliverable described as a number of issues or a report length. Reluctance to talk to your developers directly. An audit tool’s output presented as analysis. And the deck where every finding is critical, which tells you nothing got prioritized, when prioritization is the job.

That same page tells you to ask for examples of previous work, to check business references with past clients, and to grant only read access to Search Console while you’re still evaluating somebody. All three are sensible. The reference check gets skipped most often, and it’s the cheapest.

Then ask what they wouldn’t do. Anybody who has run this work has a list, and anybody who doesn’t has been selling rather than doing.

What an SEO consultant cannot do for you

They can’t create engineering capacity. If your teams are committed for two quarters, a consultant produces a well-argued backlog of things that won’t happen, and you’ve bought a document. This is the most common way these engagements waste money, and it’s knowable before anybody signs, which is why I ask about release capacity in the first call.

They can’t supply authority. If the person who has to approve a change reports into a function that doesn’t care about search, a consultant can make the argument and can’t make the decision. Sponsorship comes from inside or it doesn’t come.

They can’t manufacture subject-matter expertise either. Google’s content guidance asks whether a page clearly demonstrates first-hand expertise and depth of knowledge, the kind that comes from having actually used a product or service. Only your practitioners have that, and nobody external invents it credibly.

And they can’t compress time. Google’s site move documentation is blunt about the waiting: a small to medium website can take a few weeks for most pages to move, larger sites take longer, and you keep the redirects for at least a year. A good consultant shortens the path. Nobody shortens the wait.

When not to hire an SEO consultant

Three cases where the honest answer is no.

If organic search is a small share of your revenue with no plausible route to it being larger, the money belongs somewhere else. Think of a business driven by outbound sales into a market of a few hundred named accounts (you know all their names). Any consultant worth hiring will say so on the first call.

If nothing about your site can change for the next six months because of a freeze, a funding round or a platform decision nobody has made yet, wait. Diagnosis ages, and a recommendation written against an architecture you’re about to replace is worth very little.

And if the known problems are basic and unaddressed, meaning no title tags, no sitemap, a blocked robots.txt, fix those problems first or buy a one-off audit and act on it. You don’t need ongoing senior advice to do the things you already know you haven’t done.

How to brief an SEO consultant before you contact one

Write down the decision you need help making. Not the symptom, the decision. “Consolidate five ccTLDs onto one domain, or keep them separate” is a brief. “Traffic is down” is a feeling, and it’ll get you a proposal for whatever the vendor happens to sell.

Then check honestly whether you have the engineering time to act on the answer this quarter. If you don’t, the first engagement worth buying is the one that helps you make the case for that time. If you do, describe the decision in a paragraph and see who replies with a question rather than a package.

Written by

Marc Nashaat

Toronto-based Enterprise SEO & Growth consultant with 15+ years working with Fortune 50–500 brands including FedEx, Toyota, Adobe and Public Storage. Google Partner; featured in Forbes, CBC News and CIO.