What to Expect in the First 30 Days With an SEO Consultant

Why does the first month look so quiet?

Let's be honest about something most proposals gloss over. The first month with an SEO consultant rarely looks like much from the outside. There's no dramatic chart, no sudden flood of enquiries, and (if the consultant is any good) no loud claims about what's coming. That can feel underwhelming when you've just signed a contract.

It shouldn't. The quiet is the work. Before anyone changes a page, somebody needs to find out what's already there, what's broken, what's working by accident and what you actually want from search. Skip that and you end up fixing the wrong things quickly.

What does Google say about timing?

Google's SEO Starter Guide, last updated on 10 December 2025, includes a section titled "How long until I see impact in search results?" The short version is that it varies. Changes to a site can take time to be crawled, processed and reflected, and in some cases the effect is gradual.

That's not a dodge. It's how the system works. Google has to revisit your pages, reassess them, and weigh them against everything else it knows. A good consultant explains this on day one instead of pretending the delay doesn't exist.

The difference between activity and impact

Activity is what the consultant does: crawls, audits, briefs, tickets. Impact is what changes for your customers and your enquiries. In month one you'll see plenty of the first and very little of the second. Both are normal.

What are you actually paying for in month one?

Mostly judgement. Anyone can run a crawl. The value is in knowing which of the four hundred issues it flags actually matter for your business, and which are noise. You're paying for someone to say "fix these six, ignore those forty, and here's why."

You're also paying for risk reduction. A consultant who spots an accidental noindex tag in week one has already earned part of their fee, even though nothing visible has changed yet.

Why a documented start protects you

Notes, baselines and a change log feel dull. They're also what lets you prove, three months later, what moved and what didn't. Insist on them.

What happens in week one?

Week one is mostly conversation and access. You'll talk more than you expect, and you'll be asked questions that seem unrelated to SEO. They're not.

A good consultant is trying to learn how your business makes money, because that decides which searches deserve attention.

How does the discovery call work?

Expect a call of roughly an hour, sometimes split in two. The consultant will want to know which services bring in the most profit, who your best customers are, where you operate, who you compete with and what you've tried before. They'll ask what a good year looks like in numbers: enquiries, bookings, sales.

You'll also be asked about the practical stuff. Who approves changes? Who can edit the site? How quickly can developers act? How are enquiries handled once they arrive? Answers to those questions shape the plan as much as any keyword list.

Questions you should be ready for

What are your three most valuable services? Which areas do you want more work from? Which enquiries are a waste of your time? What's your average job or order worth? Rough answers are fine. Guesses are better than blanks.

What access will you be asked to set up?

Typically read-only access to Google Search Console and Google Analytics 4, a list of any other tools in use, and a way to contact whoever manages the website. A consultant can crawl your public site without any login at all.

Resist the urge to hand over admin keys on day one. Google's hiring guidance suggests limiting access and starting with read-only Search Console access for an initial audit. Add more only when the work needs it, and write down who has what. The options are laid out in detail under what access an SEO consultant should have.

Accounts that should always stay in your name

Your domain, hosting, analytics, Search Console and Google Business Profile belong to you. If any of them sit under someone else's login, fix that now.

What does the diagnosis phase involve?

Once access is sorted, the consultant starts looking properly. This is the part most people picture when they think of an audit, and it usually runs through weeks one and two.

It's less glamorous than it sounds. It's mostly reading data and asking "why is that happening?" over and over.

What do they look at in Search Console and analytics?

In Search Console they'll look at which queries bring impressions and clicks, which pages get them, which pages are indexed and which aren't, and whether Google reports any problems. The page indexing report is often the first stop, because it shows quickly whether Google can actually see the pages that matter.

In analytics they'll check that tracking works. This one catches people out more than you'd think. If form submissions or phone calls aren't recorded, nobody can say whether SEO is helping, so fixing measurement often comes before fixing anything else. That's why measuring organic leads in GA4 comes first in most plans.

A common week-one discovery

It's not unusual to find that a site's contact form has never been tracked, or that the same lead is counted twice. Neither is an SEO problem as such, but both make SEO impossible to judge.

What does the crawl show?

A crawl tool like Screaming Frog or Sitebulb visits your pages the way a search engine would, following links and recording what it finds: status codes, titles, headings, canonicals, redirects, internal links and more. It's a map of how your site is built, as opposed to how you think it's built.

The crawl usually produces a long list. The skill is in sorting it. Most items are minor. A handful will matter a lot, such as important pages that return errors, canonical tags pointing the wrong way, or whole sections that nobody links to.

What a consultant ignores on purpose

Warnings that don't affect indexing, rankings or conversions. Audit tools love to flag things like missing meta keywords or slightly long descriptions. A consultant who sends you a 200-item list without ranking it hasn't finished the job.

How do they review the search results themselves?

They search for your main services the way a customer would and read what Google shows. Who ranks? What kind of pages? Are there maps, videos, forums, people-also-ask boxes? That tells the consultant what Google thinks searchers want, which is often different from what the business assumes.

It's also where gaps appear. Maybe the top results are all comparison pages and you only have a sales page. Or they're all local listings and you've got no profile. That kind of insight shapes the plan more than any tool score.

What should you have by the end of week two?

By the middle of the month you should be hearing real findings, not just questions. If the consultant is still "gathering information" in week three, ask what's holding things up.

The deliverables at this stage are usually a baseline and a short diagnosis.

What goes into a baseline?

A baseline is a snapshot of where you are before anything changes. It's the thing that lets you say later, "we started at X and now we're at Y." It normally includes organic traffic and conversions from analytics, impressions and clicks from Search Console, the number of indexed pages, rankings for a defined set of important searches, and the state of your local profile if relevant.

Why you should keep your own copy

Ask for the baseline in a shared document, and save a copy yourself. If the relationship ends, the starting point shouldn't leave with the consultant.

What does a good diagnosis read like?

Short and specific. Something like: "Fourteen service pages aren't indexed because of a canonical template error. Your contact form isn't tracked. Three pages compete for the same search. Your Business Profile has the wrong primary category." Each item has evidence, a likely impact and a rough effort estimate.

It shouldn't read like a sales pitch or a wall of jargon. If you need a glossary to follow it, say so. A diagnosis is only useful if the people who must act on it can understand it.

What honesty looks like here

Good diagnoses include things like "we're not sure yet" and "this will take developer time." Over-confident ones usually haven't looked hard enough.

What are the first fixes, and which ones are safe?

Somewhere between week two and week three, most consultants make a few changes, or ask you to. These are the quick wins. They exist because some problems are obvious, cheap to fix and costly to leave.

The key word is safe. Early changes should be reversible, documented and approved by you.

Which quick wins are normal?

Removing an accidental noindex tag from an important page. Fixing a robots.txt rule that blocks a key section. Repairing broken form or call tracking. Correcting a wrong canonical. Fixing redirect chains on high-traffic URLs. Rewriting title tags on a handful of key pages that are clearly weak. Adding the right primary category to a Business Profile.

None of those is dramatic, and any of them can make a visible difference. They also demonstrate whether the consultant can spot real problems instead of recycling a template.

The "do no harm" rule

If a change could affect many pages at once, such as a template edit, it should be tested on staging, signed off and logged. Speed is never a good enough reason to skip that.

Which changes should wait?

Anything big and structural: new site architecture, mass title rewrites, changes to URLs, merging or deleting lots of pages, or a platform change. These need the full diagnosis, a plan and often developer time. Doing them in week two, before the data is in, is a gamble.

It's perfectly fine for a consultant to say "that's a month-three job." It's a good sign, in fact. It means they've sequenced the work.

What does the plan look like at the end of the month?

By week four the consultant should hand you something you can act on. Not a 90-page report that sits in a folder. A short, ranked plan.

The format varies, but the contents shouldn't.

What belongs in a first roadmap?

A list of actions, grouped into things to fix, things to create and things to measure, with a priority, an owner and a target date for each. Some will be for the consultant, some for your developer, some for your writers and some for you. A good plan makes those owners explicit.

It should also say what's not on the list and why. "We're not recommending a new blog programme yet because the service pages need fixing first" is the sort of sentence that shows real thinking. For the formal version of this, see how we structure an SEO roadmap.

A simple way to score priorities

Give each action a score for impact, effort and risk, then work from high impact, low effort, low risk downwards. It's not scientific, but it stops the loudest idea winning by default.

How should you review it?

Read it with a pen. Ask what each item is for, what evidence supports it and how you'll know whether it worked. Check the plan against your goals. If you want more enquiries for your top service and nothing in the plan touches that service, say so.

Then ask about dependencies. What needs developer time? What needs content approval? What could block a step? Plans fail at the handoff between people far more often than at the idea itself.

What to do if you disagree

Say so early, in writing. A consultant should welcome the challenge and either explain the reasoning or change the plan. Resentful silence helps nobody.

How should communication feel in month one?

Communication is one of the clearest early signals. It's also easy to judge, because you don't need any technical knowledge to see whether you're being kept in the loop.

You're looking for regular, plain-English updates and quick answers.

What cadence works?

A short written update every week or two, and one call at the end of the month, is plenty for most small businesses. The updates should say what was done, what was found, what's next and what's needed from you. Anything longer than a page is probably padding.

If you're not hearing anything for two weeks at a stretch, ask. Silence is rarely a sign of deep work. It's usually a sign of drift.

What a good update sounds like

"This week we found that 14 service pages are excluded from the index because of a canonical error. Fix is a one-line template change. Ticket sent to your developer. Expect recrawl within a few weeks. Nothing needed from you." That's it. Short, specific, calm.

How do you spot trouble early?

Watch for vague reports, missing dates, rankings with no business context, excuses that change from week to week and requests for access that don't match the work. More of these appear among the SEO consultant red flags worth knowing.

Also watch for the opposite problem: you're the one who's slow. If a recommendation has sat with your team for three weeks, the consultant can't move on. Month one goes better when you treat it like a project with deadlines on both sides.

The simplest early-warning question

At the end of any call, ask yourself: do I know what happens next, who's doing it and by when? If not, you've found something to raise.

What won't change in the first 30 days?

It helps to be blunt about this, because disappointment usually comes from mismatched expectations, not from actual failure.

Some things take longer than a month, however good the consultant is.

Which results should you not expect yet?

Big ranking gains for competitive terms. A steady stream of new enquiries from new content. Recovery from a long-running problem. Authority built through earned links and mentions. These all depend on Google recrawling, reassessing and trusting what you've done, and on competitors standing still, which they won't.

Technical fixes can show effects sooner than content or authority work, since a blocked page that becomes crawlable can start appearing quickly. Even then, "quickly" can mean weeks. Which indicators move first is covered under how long SEO takes to show results.

Early indicators worth watching

More pages indexed, more impressions for target queries, better click-through on rewritten titles, and cleaner crawl reports. Those are signs the groundwork is landing, even if enquiries haven't budged.

What if there's a drop?

It happens. A site might dip after a fix, because of seasonality, because of a Google update, or for reasons unrelated to the work. Don't panic and don't blame by reflex. Check the change log, check Search Console, compare against the same period last year and ask the consultant for their read.

A drop in month one doesn't automatically mean something went wrong, and a rise doesn't automatically mean it went right. Cause and effect in search is slow, noisy and shared with a hundred other things. A consultant who says so honestly is worth more than one who takes credit for every upswing.

When to be genuinely concerned

If changes were made without approval or documentation, if important pages vanished from the index, or if the consultant can't explain what happened, escalate. Those are process problems, not just bad luck.

How do you tell if month one went well?

At the end of thirty days, step back and run a simple test. It doesn't need data. It needs honesty.

You're checking whether the engagement is set up to succeed, not whether it has succeeded.

What's the month-one checklist?

Run through these questions. Do you have baselines saved somewhere you control? Do you have a written diagnosis you understand? Is there a prioritised plan with owners and dates? Is tracking working? Has every change been logged? Do you know what's happening in month two? Do you feel you can ask questions without being brushed off?

Six or seven yeses, and you're in good shape. Three or four, and you should have a frank conversation. Fewer than that, and it's worth reviewing the contract. If doubts creep in, the questions to ask an SEO consultant before hiring are a useful reference.

How to run the review conversation

Book thirty minutes. Bring the checklist. Ask for what's missing, agree dates and write the outcome down. It's not confrontational. It's just housekeeping.

What should month two look like?

More delivery, less discovery. Fixes ship. Briefs go to writers. Local profiles get tidied. Redirects get tested. The consultant starts to measure what the earlier changes did and adjusts the plan.

You'll probably be asked to make more decisions: approve content, release developer time, sign off on structural changes. That's a good sign. It means the plan is turning into work.

One last thing to remember

You're not looking for fireworks in month one. You're looking for a clear head, a plan you believe and a partner who tells you the truth. If you get those, the rest tends to follow. That kind of start is exactly what an SEO audit is built around.

What does your own team need to do in the first month?

Here's the part nobody puts on the proposal. SEO is a two-sided job. The consultant can diagnose, plan and brief, but somebody inside your business has to approve, publish and release. If that side of the table is slow, the whole engagement stalls, and it's rarely the consultant's fault.

Think of it as a small project with two project managers. One of them is you.

Who should own SEO on your side?

One named person, ideally. Not a committee. This person needn't know any SEO. They need to be able to say yes, to chase developers, to find a writer and to answer questions without a three-week delay. In a small business that's often the owner or a marketing manager. In a bigger one it's usually whoever owns the website.

Without an owner, recommendations pile up. Three months in, the consultant has delivered forty suggestions and the business has shipped four, and everyone feels vaguely disappointed. Name the owner in week one and put it in writing.

What the owner actually does

Approves changes, books developer time, supplies business knowledge, reviews content briefs, and attends the monthly check-in. That's maybe two to four hours a week at busy moments, and less at others.

How much developer and writer time should you book?

More than you'd guess. Technical recommendations need a developer, even if each one is small. Content recommendations need a writer or a subject expert, and subject experts are notoriously hard to pin down. Ask your consultant for a rough estimate in hours, then add a buffer.

If you don't have in-house developers, find out how to reach whoever built the site, and what they charge. A fix that takes ten minutes still needs a person with access and a process for releasing it.

A realistic example

Imagine a small London firm whose consultant finds that fourteen service pages carry a wrong canonical tag. The fix is a single template change, perhaps an hour of developer time. But if the developer works two days a month and the release cycle is monthly, that "one-hour fix" takes six weeks. Knowing that early changes the plan.

What should you gather before the consultant asks?

Save yourself a few days by collecting the basics up front: your service list with rough margins, your best customers and why, your service areas, your main competitors, past SEO or agency reports, a list of every website and social profile you own, and logins or contacts for hosting, domain and website platform. The consultant will ask for all of it anyway.

It also helps to write down what you've already tried and what happened. "We paid for links in 2023 and our rankings dropped" is the kind of sentence that saves weeks of detective work.

Don't hide the embarrassing bits

Old agencies, past penalties, abandoned sites, bought links. The consultant has seen worse. Hiding it only slows the diagnosis.

How do you keep the first month on track?

A lot of month-one success comes from habits rather than tactics. Small, boring habits.

None of them require any SEO knowledge.

What does a good check-in rhythm look like?

Keep it light. A weekly or fortnightly written update, a short call at the end of week two to review findings, and a longer review at day thirty. Put the dates in your diary at the start so they don't slip.

At each check-in, ask the same three questions. What have you done? What did you find? What do you need from me? It sounds simple, and it keeps both sides honest. If the answers start to blur into jargon, ask for an example.

Keep a shared decision log

A shared document listing every decision, who made it and when is worth its weight in gold three months later. It stops arguments about who agreed to what.

What documents should exist by day 30?

Five things. A baseline report. A diagnosis. A prioritised roadmap. A change log. And an access list showing who can touch what. None needs to be long. All of them should live somewhere you control.

If you're missing any of them, ask. It's not rude. It's simply how you stay in charge of an asset that's worth real money to your business.

Why paperwork is protection

If the consultant is hit by a bus, or you switch providers, those five documents let someone else pick up the work in days rather than months.

How do you handle surprises?

You'll get them. A problem will turn up that nobody expected, such as a hosting issue, a plugin conflict or a page that mysteriously vanished from the index. Good consultants flag it quickly, explain what they know and what they don't, and propose a next step.

Treat surprises as normal. What matters is how they're handled: fast notice, honest explanation and a clear plan. A calm response to a sudden problem looks like the steps for diagnosing an organic traffic drop.

Is a 30-day start different for different kinds of business?

Yes, and it's worth knowing which version you're in. The skeleton stays the same, but the emphasis shifts with the size of the site and the way you win customers.

Three common cases show the difference.

What about a small local service business?

Expect more time on your Google Business Profile, your service pages and your reviews. The site is small, so the crawl is quick, and the interesting questions are about local visibility: which areas you actually want, which categories fit and whether your details agree everywhere online. Quick wins here are often profile fixes and tracking calls.

What about an online shop?

The crawl is bigger and messier. Faceted navigation, duplicate product URLs and category structure take up much of the diagnosis, and the plan leans toward template-level fixes that need developer time. Month one may end with a long technical backlog and only a few shipped changes, which is normal for a store with thousands of URLs.

What about a site that's just been redesigned or migrated?

Everything starts with damage control. The consultant checks redirects, indexing, canonicals and tracking against the old site, and compares traffic with the pre-launch baseline if one exists. This is the one situation where "fix first, plan second" is right, because every day of lost visibility has a cost. An SEO traffic recovery consultant handles exactly this scenario.

Whatever your case, ask for the sequence

In the first call, ask what the consultant expects to do in weeks one to four for a business like yours. A clear answer shows they've done it before. A vague one shows they haven't.