Choosing an SEO agency is a decision about fit, evidence, and risk - not just a list of services. Start with the business problem you need to solve, then test each proposal against the same questions: what work will happen, what evidence supports the approach, who owns the inputs, and how will progress be reviewed? No agency can guarantee a specific search outcome.
What decision are you hiring an SEO agency to improve?
An SEO agency is a provider that plans or performs agreed work to help a site earn relevant visibility in organic search. Before comparing providers, define the decision behind the hire: for example, whether to improve qualified nonbrand demand, fix crawl and indexing constraints, or build content for a known set of buyer questions.
Separate the business outcome from the indicator used to monitor it. Search impressions, rankings, and visits can help explain performance, but they do not by themselves show qualified pipeline or revenue. Agree on the starting point, target audience, conversion event, reporting window, and what the agency can reasonably influence.
Write down constraints too: engineering availability, subject-matter review, legal approvals, data access, and existing commitments. A proposal that ignores these dependencies may look attractive while leaving the delivery path unclear.
How should you inspect an agency's evidence?
Ask the agency to show relevant work and explain its role. A case study is useful when it states the client context, starting condition, dates, work performed, measurement method, and limits. A chart without those details is not enough to establish what caused a change.
Google's guidance for hiring an SEO advises businesses to research potential SEOs, check references and examples, ask about proposed changes and expected outcomes, and understand the risks. That guidance supports due diligence; it does not certify any vendor or make a result transferable to your site.
Use these questions in a reference call or proposal review:
What was the business and site context, and how close is it to ours?
What did your team personally deliver, and what did the client or another vendor do?
Which baseline and time period are shown? Were there migrations, seasonality, or other major changes?
Which metric changed, how was it measured, and what does it leave out?
Can we speak with a client whose project had similar constraints?
Treat a relevant example as evidence to investigate, not a forecast. Strong answers explain uncertainty and what the agency would need to learn before making a recommendation.
What questions reveal strategy and fit?
A proposal should connect the work to a specific diagnosis. Ask the agency to explain how it would decide what to do first, what it would defer, and what evidence could change its plan. The answer should make dependencies visible rather than present a fixed package as equally suitable for every site.
Ask each provider:
Which business and search questions would you investigate first, and why?
How would you distinguish technical constraints from content or demand problems?
What work will your team perform directly, and what will you ask our team to do?
What would you need from engineering, product, sales, and subject-matter experts?
What would the first review point deliver, and what decision should it help us make?
What finding would cause you to change or stop the proposed work?
For a SaaS or B2B company, ask for examples that show how the provider handled long buying journeys, product nuance, and collaboration with internal experts. Industry labels alone are weak evidence. The provider should explain which parts of the example transfer and which do not.
Who owns the work, data, and access?
Clarify ownership before granting accounts or signing. Your company should know who controls analytics, Search Console, the website, content, and any work product. Confirm the access level required, who approves changes, how recommendations are documented, and what happens to accounts and files if the relationship ends.
The contract or statement of work should make these points findable:
Deliverables, scope boundaries, and what is excluded.
Client inputs and dependencies, including response times or technical resources.
Approval steps for publishing, site changes, and external outreach.
Reporting definitions, meeting cadence, and escalation path.
Fees, renewal or termination terms, and transfer of access and work product.
A missing detail is a prompt for clarification, not proof of misconduct. But unresolved ownership or access terms can create avoidable operational risk.
How do you compare proposals fairly?
Use an evidence-to-contract matrix so the same claim is tested in each proposal. The example below is hypothetical; it illustrates a review method, not a typical agency result.
Proposal claim | Evidence to request | Follow-up question | What to document |
|---|---|---|---|
“We will grow qualified organic demand” | Comparable case context, baseline, definitions, and reporting | How will you identify qualified visits or leads? | Metric definitions, exclusions, reporting window |
“We will fix technical issues” | Sample finding with affected URLs and validation method | How will you separate a critical block from a warning? | Prioritization rules, owner, acceptance test |
“We will create content” | Example brief or published work and its review process | Who supplies expertise, fact-checks, and approves it? | Deliverables, review rounds, rights, dependencies |
“We will improve performance” | Baseline and evidence connecting work to outcome | What else could explain a change? | Assumptions and limits, not only a target |
Then compare the proposals on scope, staff access, dependencies, measurement, and risk. A lower fee may exclude implementation or research; a higher fee is not automatically better. Pricing should be assessed alongside the work and responsibilities actually included.
What are the warning signs?
Be cautious when a provider guarantees a ranking or revenue outcome, will not explain methods, relies on a polished dashboard without definitions, or asks for broad access before describing why it is needed. Also investigate undisclosed paid links, copied content, and unclear ownership of accounts or deliverables.
A warning sign is a reason to ask for evidence and safeguards. It is not enough, by itself, to conclude that a provider has acted improperly. Google specifically cautions that unethical SEO practices can harm a site, so ask how proposed changes will be reviewed and reversed if they create problems.
Frequently Asked Questions
How do you pick an SEO agency?
Pick an SEO agency by defining the business problem, comparing proposals against the same evidence and scope criteria, checking relevant references, and clarifying ownership and reporting in writing. Do not choose on rankings promises or price alone.
What makes a good SEO agency?
A good SEO agency explains its diagnosis, shows relevant evidence with limitations, names the work and dependencies, and makes reporting understandable. The fit depends on your goals and internal capacity; no single service mix suits every company.
How do you choose an SEO company for a SaaS business?
For a SaaS business, ask how the provider will understand the product, buying committee, sales cycle, and conversion events. Ask which parts of similar work transfer to your context and which do not. A specialty label alone does not establish fit or guarantee results.
How Nortav Can Help
Choosing a provider is easier when the current search position, business priorities, and evidence gaps are clear. Nortav's approach starts with understanding your current search visibility, identifying gaps against competitors, and developing a strategy focused on qualified traffic, lead generation, and measurable business value. Book a Discovery Call →
Sources
Google Search Central, Do you need an SEO?
Grow and Convert, How to Choose an SEO Agency That Actually Drives Growth
Reddit, How to Choose the Right SEO Company for Your Business (question-provenance only; not factual evidence)
