Review standards
Review standards
Read beyond the praise. Understand the experience behind it. Reviews can help you ask better questions about an SEO provider when you know who is speaking, what work they experienced and what the evidence supports. These standards explain how to interpret agency information, testimonials, case studies and editorial comparisons without confusing a personal account with a verified commercial outcome.
Begin with the kind of information in front of you
An agency service page, a testimonial, a project case study and an editorial comparison do different jobs. A service page describes an offer. A testimonial presents a client’s account. A case study explains a selected project and reported results. An editorial comparison applies a particular perspective to a group of candidates. Reading all four as though they were independent performance measurements creates certainty the material may not support.
First identify the speaker and the claim. Is the statement about how communication felt, which services were purchased, how implementation worked or what happened to a business metric? A reviewer can credibly describe an experience without possessing the information needed to attribute every result. An agency can explain its work while remaining an interested source for the performance claims it publishes.
The practical aim is to keep useful evidence in its proper scope. You do not need to discard a review because it is subjective, or accept a numerical case study because it looks objective. Ask what the material lets you understand and which questions still need another source. That distinction supports better conversations with providers and a more defensible shortlist.
Agency information: confirm the present offer
Agency descriptions can help establish stated services, locations, credentials and the kind of work a provider says it performs. Confirm information that matters to an agreement directly with the provider. A service offered when a page was written may have changed, and a location mentioned in a market comparison does not by itself establish a staffed office there.
Look for precise language. Serving ecommerce businesses is different from naming a relevant platform project. Offering technical SEO is different from taking responsibility for development. A credential can be relevant without establishing expertise in every part of a proposed engagement. Ask how the description maps to the deliverables, team and responsibilities in the actual proposal.
Treat unresolved information as a question rather than silently completing the profile yourself. If the public material does not explain who implements recommendations, ask. If pricing is described in a different unit from another proposal, request a comparable scope. A careful reading identifies what is missing without turning a lack of public detail into proof of poor capability.
Testimonials: useful experience, selected perspective
A testimonial is an attributed account of a client’s experience. It can illuminate communication, responsiveness, working relationships and the kind of engagement involved. It is also a selected account. A positive statement does not describe every client relationship, and a negative experience does not necessarily predict what will happen under a different scope or set of circumstances.
Ask whether the account identifies the work and its timing. A client discussing a website migration may offer relevant insight for another migration, while saying little about ongoing local profile management. A short endorsement with no service context has narrower usefulness. The objective is not to demand that every client write a technical report, but to understand the limits of the account you have.
Keep satisfaction and performance separate. A client may value clear communication even if commercial results are uncertain. A project may achieve a reported visibility improvement while being difficult to manage. Both dimensions can matter to a buying decision. Reducing the entire experience to a single positive or negative label can hide a practical issue you should discuss before hiring.
Case studies: inspect the claim, not just the chart
A useful case study makes the project understandable. Look for the business context, baseline, period, work delivered, measurement method and the party publishing the result. Those details let you judge relevance and identify assumptions. A chart without a starting point or a claim without a period may be visually impressive while providing little basis for a comparison.
Ask what the metric measures. Traffic, qualified enquiries, transactions, revenue and profit are different outcomes. An increase in visits does not establish an increase in suitable customers. An increase in all-channel revenue does not establish an organic search result. Brand demand, paid activity, seasonality and other changes can affect what happened during an SEO engagement.
For a hypothetical illustration, a fifty percent increase could describe twenty qualified enquiries becoming thirty, or two thousand becoming three thousand. The percentage is the same, but the scale is different. Neither example is an actual agency result. It shows why a baseline and a clear definition of the metric are necessary before you compare two growth claims.
Selected projects are not forecasts. A case can show that a provider reports delivering particular work under particular conditions. It cannot promise the same outcome for another site. If the project is central to your decision, ask for relevant supporting material or a reference that can clarify the scope. Confirm which part of the result is agency-reported and which part is independently supported.
Third-party reviews: understand the platform's role
Third-party platforms can provide client perspectives beyond an agency’s own site. Read the review in the context of the platform, its date, sample size, service category and stated verification process. A platform’s verified label should be interpreted according to what that platform checks. It should not be expanded into a claim that SEOS.co interviewed the client or independently measured the result.
Identity, relationship and performance are distinct. A platform might establish that a person is connected to a company or that a commercial engagement occurred. That does not automatically establish the cause of a traffic change or the accuracy of a revenue attribution. Read the label and the result separately, then ask whether the platform’s process supports the specific conclusion you want to draw.
The distribution of experiences can be useful, but avoid treating a small sample as a complete account of a provider. Consider how recent and relevant the reviews are, what services the reviewers purchased and whether the described circumstances resemble yours. A large collection of brief praise may answer different questions from a detailed account of a comparable project.
Authenticity signals are questions, not verdicts
A useful review explains the relationship, the work, the timing and an inspectable source where one is available. Specific context makes an account easier to assess. Generic repeated praise, unexplained clusters or statements with no engagement detail can justify follow-up questions. They do not, by themselves, prove that a review is false.
Avoid replacing one unsupported inference with another. A polished review is not necessarily fabricated, and an awkwardly written review is not necessarily authentic. Similar language can have more than one explanation. If authenticity materially affects your decision, ask for evidence of the relationship or a relevant reference rather than making a definitive accusation from appearance alone.
Pay attention to the difference between a concern and a demonstrated fact when sharing your own notes. Write that a review lacks context if that is what you observed. Do not rewrite that observation as a claim that the reviewer was not a client. Careful wording protects the usefulness of your assessment and makes it easier to update when more information becomes available.
Compare the relevance of experiences
Relevance depends on the work and the business context. An agency may receive praise for content production while you need a complex platform migration. A review from a very different budget or operating model may still be informative, but it should not carry the same implications as a comparable engagement. Look for the connection rather than relying on a familiar industry label alone.
Implementation is particularly important. A client with an internal development team may describe an advisory engagement that would not work for a business needing hands-on delivery. A company with established analytics may measure outcomes differently from a company building its reporting for the first time. Ask what resources were present in the reviewed project and which your own team can provide.
Consider timing without assuming that newer always means better. A recent account may reflect the current team or offer, while an older detailed project may provide useful context about a specific capability. Confirm material present-day facts directly. The point is to understand what the experience describes, not to manufacture a universal rule from the age of a review.
Turn review reading into useful due diligence
Prepare a few questions that connect the evidence with your brief. Ask for references relevant to your sector, budget and intended work. Ask which people would perform the engagement and how deliverables are defined. Clarify the role of your own team, especially where approvals, development or access could determine whether recommendations are implemented.
Ask how performance will be measured and which accounts you can inspect. Discuss how reporting separates organic search from other channels, brand demand from broader discovery where relevant, and qualified enquiries from every form submission. These questions do not require a provider to predict the future. They require the proposal to explain how observations will be interpreted.
Ownership and access belong in the same conversation. Confirm who owns accounts, content and reports, how you will receive the work and what happens at the end of the engagement. A positive review about a relationship does not settle the terms of your own contract. Use what you learn from reviews to make those terms clearer rather than assuming they are identical across clients.
Keep editorial comparisons in their proper scope
SEOS.co agency comparisons are editorial recommendations with page-specific context and limits. RankScore is an editorial comparison score, not a customer star rating or a probability of success. Read the ranking methodology for the distinctions between editorial placement, reported claims, third-party perspectives and measured outcomes. Do not treat a small numerical difference as a scientifically established difference in quality.
An editorial description is also different from a directly submitted review. Attribution matters because it tells the reader whose judgment or experience is being presented. A description can summarize relevant information without claiming that every statement has been independently audited. The useful question is whether the account makes its basis and limitations understandable.
Use comparisons to find candidates and organize questions. Then compare current proposals against the same business brief and evidence requirements. A ranking cannot decide how much implementation responsibility your team can carry, how a provider’s process fits your approvals or which commercial terms are acceptable. Those are decisions that need your context and direct confirmation.
Report a factual problem precisely
If information appears incorrect, provide the affected page URL, the exact statement and a source supporting the proposed correction. Include the date of a known change where relevant. A report about an outdated service differs from disagreement with an editorial recommendation. Naming the issue precisely helps separate a factual claim from a preference about placement or presentation.
Use the corrections policy and contact route for an existing factual issue. Do not send private client records, passwords or confidential contracts. If evidence is sensitive, describe the concern and identify a public alternative where possible. For agency consideration or inclusion, use Agency Connect with relevant context rather than treating a correction request as a guarantee of a particular editorial outcome.
Keep a short evidence notebook
When a review influences your shortlist, record its source, date, service and the specific point that mattered. Note any unresolved question beside it. This prevents a useful but narrow observation from becoming a broad claim as it moves between colleagues. It also gives a provider a concrete question to answer rather than asking it to respond to an impression assembled from several unrelated accounts.
Questions readers often need to resolve
Can a positive review prove an agency will work for me?
No. It describes an experience under particular circumstances. Use it to understand the engagement and formulate questions, then compare those circumstances with your own brief. Relevant scope, implementation capacity, people and terms still need direct discussion before you commit.
Should I ignore a review without performance numbers?
Not necessarily. A review can provide useful information about communication, responsibilities and delivery without claiming a measured business result. Judge it against the question it can answer. Do not dismiss an experiential account for lacking a metric, or invent a performance conclusion that the account never makes.
What is the safest way to summarize uncertain evidence?
State the observation and its limit together. For example, say that a published case reports organic traffic growth but does not identify qualified lead outcomes. That preserves the useful information without upgrading it into a broader result. Your notes should become more precise as evidence improves, not more certain simply through repetition.