How to Verify an SEO Consultant's Claims and Case Studies

Why does verification matter in SEO more than in most services?

Hire a plumber and you can see whether the tap stops dripping. Hire an SEO consultant and the evidence is slower, fuzzier and easier to dress up. Results arrive months later, depend on a search engine nobody controls and are measured in charts that can be made to say almost anything. That's why claims deserve checking, and why most people don't check them.

The good news is that verification is easier than it looks. You don't need technical skill. You need a handful of well-aimed questions, a willingness to look at the evidence and the patience to notice what's missing.

What does Google's guidance say?

Google's hiring guidance, Do you need an SEO? Tips for hiring an SEO, last updated on 5 June 2026, lists questions to ask a potential SEO. The first is whether they can show past work and share success stories. It also advises checking references with past clients, asking whether the SEO was helpful, easy to work with and produced results.

Those two suggestions, examples and references, are the backbone of verification. The rest of this guide shows how to make them work.

Evidence has layers

Claims come first, then examples, then independent checks. The more layers a claim survives, the more you can trust it.

What counts as a claim worth checking?

Anything that affects your decision: "we've ranked clients on page one", "we increased traffic by x", "we've worked in your sector", "we're experts in local SEO", "we have a special process", "we're certified". Each can be tested to some degree, and the way a consultant responds to testing is informative in itself.

You're not trying to catch anyone out. You're trying to understand what's real, what's exaggerated and what's unprovable, so that you can weigh it sensibly.

What does a credible case study look like?

Not all case studies are equal. Some are marketing posters. Others are honest accounts. The difference lies in the details.

Learn the anatomy and you'll spot the weak ones immediately.

Which elements should every case study contain?

A starting position: where the site was, with numbers and dates. The problem: what held it back, in plain terms. The intervention: what was actually done, specifically enough that you could picture it. The timeline: when each action happened. The outcome: what changed, measured from a named source. And the limits: what else may have influenced the result, and what can't be attributed to SEO.

If any of those are missing, ask for them. A consultant who has the evidence will provide it. One who doesn't will start to hedge.

Look for specifics a stranger couldn't invent

Details such as "fourteen service pages were excluded from the index because of a template canonical error" sound like someone who did the work.

Why do honest case studies mention limits?

Because SEO doesn't happen in isolation. Seasonality, brand campaigns, site redesigns, pricing changes and Google updates can all move organic numbers. An honest consultant will say so, and explain how they separated their effect from the noise, or admit they couldn't completely.

A case study that credits everything to SEO should raise an eyebrow. A case study that says "we can't be certain how much of this was our work, but here's the evidence we have" is far more trustworthy. How honest case studies document the problem, the intervention, the timeframe and the limits is shown on the SEO case studies page.

The attribution question

Ask: "What else changed during that period, and how do you know it wasn't responsible?" The answer reveals depth of thinking.

How do you check the claims yourself?

Some verification takes a few minutes and requires no one's cooperation. Start there.

Treat each check as a way of testing the story, not of proving a verdict.

What can you see on the client's live site?

If the case study names the client, visit the site. Does it look like a site that has had sound SEO work? Look at the structure, titles, headings and content quality. Check whether the changes described are visible: a restructured service section, new guides, cleaner navigation. Use your browser to view the source for titles, canonicals and structured data.

You don't need to audit it. You're checking that the story matches the evidence, and that the site isn't obviously a mess. If the described improvements are nowhere to be seen, that's a red flag.

Check the dates

Compare the changes with the dates in the case study. A page that's visibly older than the claimed work doesn't support the story.

What can public tools tell you?

Visibility estimates from commercial tools can show whether a domain's search presence grew over a period. Treat them with caution: Google's guidance notes that third-party tools don't have access to its internal ranking data, so their figures are estimates from their own models. They're useful for rough trends, not proof.

Search for the client's main services yourself. Does the site appear where the case study says it does? Remember that results vary by location and device, so a single check proves little. Several checks from different places give a better picture.

The Wayback Machine

The Internet Archive's snapshots can show how a site looked before and after the claimed work, which is a neat way to check the story.

What can you check on the consultant's own site?

Does the consultant's site show competence? Is it well structured, fast, clear and honest? Does it rank for sensible terms, or at least show evidence of care? You wouldn't expect perfection, but obvious basic mistakes, such as broken pages, missing titles or confusing structure, are worth noting.

Read their content. Do they explain things clearly and admit uncertainty, or do they make sweeping promises? The tone of the writing says a lot about how they'd treat your project.

Which evidence should you ask the consultant to provide?

When you can't verify something yourself, ask for the underlying evidence. A good consultant expects it.

Request it politely and specifically.

What documents and data are reasonable to ask for?

Anonymised screenshots from Search Console or analytics with dates and axes visible. A short summary of the work done, with a timeline. A sample audit or roadmap, redacted for confidentiality. A sample monthly report. Details of the tools used for measurement. And a description of how attribution was handled.

Be reasonable about confidentiality. Clients often prohibit sharing data. Anonymised, redacted examples are usually fine, and a consultant who refuses to share anything at all deserves more questions. The guide to the questions to ask an SEO consultant before hiring covers the wider set.

Ask for a worked example of reasoning

"Take me through one problem you diagnosed: what you suspected, what evidence changed your mind and what you did." Real work has dead ends.

How do you read a sample report or audit?

Look for clarity, specifics and prioritisation. Does it identify real problems with evidence? Does it rank the fixes by impact and effort? Does it explain why each matters? Are the recommendations tied to business goals? Or is it a generic list of tool warnings with a logo on the front?

Check that the claims in the sample match what you can see. Ask how the consultant decided what to leave out, because good audits are as much about what to ignore as what to fix.

How do you use references properly?

References are the closest thing to independent testimony. Used well, they're gold. Used carelessly, they're a formality.

Choose and question them with care.

How many references should you ask for, and which?

Ask for two or three, ideally including one from a similar sector or size of business, and one from an engagement that has ended. Ongoing clients are likely to be happy. Past clients reveal how the relationship ended. If the consultant offers only a single, handpicked reference, ask for another.

If confidentiality prevents naming clients, ask whether a past client would speak to you privately. A consultant with a long record can almost always arrange it.

Make the call or email short and respectful

Introduce yourself, explain why you're asking and say how long it will take. Most people are glad to help if asked politely.

What should you ask a reference?

Open questions that invite detail. What problem were they trying to solve? What did the consultant actually do? How did they communicate? Were deadlines met? What results did they see, and how were they measured? What went wrong, and how was it handled? Would they hire the consultant again? Is there anything you'd advise me to watch for?

Google's guidance suggests asking whether the SEO was helpful, easy to work with and produced results. Add questions about problems, because every engagement has some. A reference who can describe a difficulty and how it was resolved is more credible than one who only offers praise.

Listen for specifics

Vague praise is weak evidence. Concrete stories, with dates and details, are strong.

How do you spot weak or misleading evidence?

Some "proof" looks impressive and isn't. Knowing the common types helps you discount them.

Here are the usual suspects.

Which kinds of evidence are weak?

Unnamed screenshots with no dates or axes. Charts of a single metric, such as impressions or "authority", with no link to enquiries. Claims about ranking for terms nobody searches. Before-and-after pictures with no description of the work. Vanity numbers such as "we've delivered a million impressions". Testimonials with no names or details. Awards and badges that don't relate to organic search.

None of them proves the consultant is bad. Together they show a pattern of evidence that can't be tested, and you should weigh the claims accordingly. The wider warning signs are in the guide to SEO consultant red flags.

Rising lines are easy to make

A selection of dates, a particular metric and a friendly scale can turn flat results into a success story.

What about guarantees and special-access claims?

Google's guidance says no one can guarantee a number one ranking, and lists claims of a special relationship with Google among its red flags. Any consultant who offers such guarantees or claims is, at best, misunderstanding how search works. Treat the claims themselves as disqualifying, whatever case studies accompany them.

The same goes for claims that a method is secret. A consultant who won't explain what they do, even in outline, makes verification impossible, and verification is the whole point.

Ask how the claim could be proven wrong

If a claim can't be tested, it isn't evidence. Good consultants welcome testable claims.

How do you verify credentials, tools and experience?

Beyond case studies, consultants make claims about who they are: years of experience, qualifications, tools, sector knowledge. These can be checked too.

Keep proportion. Credentials matter less than demonstrated judgement, but they shouldn't be false.

What should you check about identity and business?

That the business exists on Companies House, if it's a company. That the website, address and contact details are consistent and real. That named people exist and have a verifiable professional history, such as a professional profile that matches the story. That reviews on independent platforms look genuine: varied, specific and spread over time.

If the consultant claims a partnership or certification, check with the issuer. Remember that advertising partner badges relate to paid search, not organic ranking ability, and Google's guidance cautions against claims of special relationships.

Read reviews critically

A cluster of near-identical five-star reviews posted in one week is a warning. Detailed, varied reviews are more convincing.

How do you test experience and judgement?

Ask scenario questions relevant to your situation. "Our traffic fell after a redesign. What would you check first?" "We have thousands of filter URLs. How would you decide which to index?" "We've had a Business Profile suspended. What's your approach?" The answers show how they think, and whether they've seen similar problems.

Listen for structure, caution and specifics. Good answers start with diagnosis, not solutions, and acknowledge uncertainty. Weak answers reach for a favourite tactic immediately. A short paid audit is the most reliable test of judgement, and an SEO audit is designed to show how a consultant thinks before you commit further.

Test with a small, paid task

A fixed-fee diagnostic gives you something concrete to judge, and limits your risk.

How do you score what you find?

Evidence needs weighing. A simple scoring method keeps you from being swayed by charm or fatigue.

It takes a page.

What does a verification scorecard look like?

List the key claims the consultant made. For each, note the evidence offered, whether you could check it, what you found and a score from zero to three: zero for no evidence or contradicted, one for weak, two for plausible and partly verified, three for strong and verified. Add a note on how they responded to questions.

Total the scores and look at the pattern. A consultant with several threes and a couple of twos is credible. One with mostly ones and zeros is selling.

Be consistent across candidates

Use the same scorecard for each consultant so you compare like with like.

How should the score affect your decision?

Use it as one input. Combine it with the quality of the conversation, the clarity of the proposal, the fit with your needs and your instinct. If the scorecard and your instinct disagree, ask why. Sometimes the numbers reveal what you were ignoring. Sometimes your instinct picks up something the scorecard misses.

If a promising candidate scores low on verification, give them a chance to fill the gaps. A strong consultant will rise to the challenge. If they get defensive, you've learned something.

How do you verify claims after you've hired?

Verification doesn't stop at the contract. Checking continues in lighter form as the work proceeds, and it protects you from drift.

Build the habit early.

What should you keep checking?

That the work described in reports matches the live site. That the change log is current and honest. That reports tie to your own Search Console and analytics, which you should own. That tracked outcomes are real and counted properly. That the consultant's advice cites official documentation where it exists. And that promises about timing are met or explained.

Google's guidance, updated in 2026, adds that you should verify third-party recommendations against official documentation before making major changes. Make that a standing practice: for any major recommendation, ask where it comes from.

Own the data

Keep Search Console and analytics under your control. You can't verify anything if the data lives in someone else's account.

How do you handle discrepancies?

Raise them promptly and politely, in writing, with evidence. "The report says rankings improved for these terms, but Search Console shows impressions flat. Can you explain?" Good consultants will check, explain and correct. They may be right, and there may be a reason. Either way, you'll learn something.

If discrepancies keep arising and explanations don't convince, take it seriously. The framework in the guide to when to fire your SEO consultant explains how to review and decide.

What does a worked example look like?

A story shows the process. This one is hypothetical, built from typical patterns, with illustrative details.

It follows a business owner choosing between two consultants.

What did the owner do?

A small London firm shortlisted two consultants. Both sent glossy case studies. The owner asked each for a baseline, a timeline, the actions taken and the limits of attribution, plus a reference who'd ended the engagement. Consultant A replied with an anonymised summary: starting position, a diagnosis of canonical and indexing problems, dates of fixes, a Search Console chart with axes and a candid note that a seasonal peak had overlapped the improvement. A reference was arranged.

Consultant B sent more screenshots of rising lines, said the methods were proprietary and declined to name or connect a reference, citing confidentiality.

The contrast

One consultant's evidence could be tested. The other's couldn't.

What happened next?

The owner spoke to Consultant A's reference, who described the problem, the fixes and a delay caused by the client's own developer, and said they'd hire the consultant again. The owner then commissioned a small paid audit from Consultant A, which was specific, ranked and clear. They also checked the consultant's own site, which was clean and well structured.

They chose Consultant A, set a ninety-day review and kept ownership of all accounts. The process took about a week and cost a small audit fee. It didn't guarantee success, but it replaced guesswork with evidence, which is what verification is for. Whatever you decide, the same habits apply: ask for specifics, check what you can, speak to references and weigh the answers honestly.

The takeaway

Ask for baselines, dates, methods and limits. Check the live evidence, speak to references, test with a small paid task and score what you find.

How do you verify claims about specific kinds of SEO work?

General credibility is useful, but your project is specific. A consultant who's brilliant at local SEO may know little about migrations, and the reverse. Verification should match the work you actually need.

Here's how to test the common specialisms.

How do you verify technical SEO claims?

Ask for a worked example of a technical diagnosis: the symptom, the evidence, the cause, the fix and the verification. Good answers mention specific tools and reports, such as Search Console's page indexing report, a crawl export or server logs, and describe how the fix was confirmed. Ask how they'd handle a case similar to yours, such as thousands of filter URLs or a JavaScript-rendered site.

Then test their explanation against official documentation. Google's guidance says to check third-party advice against its own documentation before making major changes, and a technical consultant should be able to point to the relevant page. If their advice contradicts official guidance, ask for the evidence.

Ask for the verification step

Every technical fix should end with a check. "How did you confirm it worked?" separates practitioners from theorists.

How do you verify local SEO claims?

Ask about Business Profile work: categories, services, verification problems, suspensions, review processes and citation clean-ups. Ask how they measure local results, for instance calls and direction requests from the profile alongside enquiries from your own records. Check whether they understand the guidelines on names, addresses and service areas, and whether they refuse tactics such as fake reviews or keyword-stuffed names.

Look at examples of profiles they've managed, if the client allows. Check that the details are clean and consistent, the reviews look genuine and the profile is complete. The behaviours that suggest competence are covered in the guides to a suspended Business Profile and getting more Google reviews.

How do you verify content and strategy claims?

Ask how they choose topics, map search intent to pages and measure content success. Request a sample brief or content plan, and look for clarity about audience, intent, structure and links to business goals. Ask how they handle existing content: refreshing, merging and removing. And ask how they separate content impact from other influences.

A strong answer explains the reasoning, not just the output. Weak answers focus on volume, such as "we'll publish thirty articles a month," without saying why those articles, for whom and with what expected result.

What should you do if a claim can't be verified?

Sometimes you can't check something, whatever you try. Confidentiality, timing or the nature of the claim gets in the way. The question then is how much weight to give it.

Be proportionate and consistent.

How much weight should unverified claims carry?

Little, on their own. Treat them as hypotheses rather than facts. If a consultant says they achieved a spectacular result and nothing supports it, don't let it drive your decision. Weigh the claims you can check more heavily, and look for patterns: does the verifiable evidence suggest competence, caution and honesty?

If a claim is central to your decision, such as experience in your sector, ask for another form of proof: a reference, a work sample or a short trial. Don't accept "trust me" for anything important.

Ask what would convince you

Tell the consultant what evidence would satisfy you, and see how they respond. Their reaction is information.

How do you protect yourself if you proceed anyway?

Limit risk. Start with a short paid diagnostic. Use a short initial term with a review point. Keep ownership of all accounts. Insist on a change log. Define success measures in writing. And agree a clear exit. These measures turn an uncertain bet into a managed experiment.

If the early work confirms the claims, you can extend with confidence. If it doesn't, you've limited the cost and gathered evidence, using the steps in the guide to switching SEO providers without losing rankings if you need to move on.

How can you share the verification work with your team?

Hiring decisions often involve several people. A shared, simple record keeps everyone on the same page and prevents the loudest voice winning.

It takes minutes.

What should the record include?

The list of claims, the evidence offered, what was checked and by whom, the scorecard, notes from reference calls and the open questions. Store it in a shared document. Ask each decision maker to read it before the final discussion.

A shared record also helps later. If the engagement runs into difficulty, you can see exactly what was promised and what evidence supported it, and you can judge the work against the original claims.

Keep the tone fair

The record is for decision-making, not for gotchas. Note strengths as well as concerns.

How do you make the final call?

Review the scorecards, the references and the sample work together. Discuss the biggest risks and how to manage them. Decide on the engagement structure: a paid audit first, a project, a short retainer. Write down the decision and the reasoning, so that you can revisit it at the first review.

Whichever consultant you choose, tell the others politely and promptly. The industry is small, and good manners cost nothing. And if you'd like an independent second opinion on a proposal or a track record, a short SEO audit is a cheap way to see how a provider thinks.

One last reminder about proportion

Verification should be thorough, not paranoid. You're looking for enough evidence to make a confident decision, not a perfect one. A handful of well-chosen checks, a couple of honest reference conversations and a small paid test will tell you most of what you need. If a consultant passes those, relax and let them do the work, while keeping the reporting and ownership habits that protect you either way.