Assess a surge of online reviews before calling it a coordinated campaign.
A rise in negative reviews may reflect genuine experience, a public event or organised activity. Useful analysis checks facts, timing, platforms and account relationships without treating every criticism as an attack.
Address verifiable facts without accusing reviewers.
Step-by-step method
A reproducible path from question to conclusion.
1
Set the period and platforms
Define the observed window, affected locations or products and normal review volume. Without a baseline, ordinary variation can look exceptional.
2
Preserve the posts
Record URL, date, rating, text, any reply and platform rules. Work from copies and collect only profile data necessary to answer the question.
3
Classify the content
Separate detailed experience, general opinion, clear error, apparent duplicate and verifiable claim. Similar wording can arise from a shared event or template.
4
Test coordination
Examine timing, unusual repetition, accounts and external relays. Compare these clues with news, service changes and legitimate campaigns.
5
Respond and monitor
Correct checkable facts, resolve valid complaints and use reporting tools for rule violations. Track the trend without amplifying marginal posts.
A timeline needs a baseline
Read a surge against prior volume, seasonality, promotions and service incidents. One spike alone cannot establish its cause.
Keep positive reviews and the organisation’s replies too, so the analysis reflects what users actually saw.
Test competing explanations
People may use the same words because an issue became public. Coordination becomes more plausible when several independent clues converge: timing, rare identical phrasing and shared relays.
State confidence and what remains unknown before distinguishing organised action, spontaneous mobilisation and real customer problems.
Reply without escalating the situation
A short public reply can acknowledge established facts, provide a resolution channel and avoid personal data. Unsupported accusations can create a new risk.
Removal requests should identify specific rule violations with URLs and evidence rather than target a merely unfavourable opinion.
Define a comparable sample
Record platform, period, selection and reviews actually examined. Separate read corpus from displayed total. Openings, promotions or controversy can change volume. Without customer data, review counts alone do not describe the frequency of negative experiences.
Support disputes with precise grounds
For each disputed review retain URL, date, passage and verifiable grounds under the applicable platform rule. Separate similarity, actual customer experience and moderation. Removal alone establishes neither author identity nor a coordinated campaign.
Worked example
A review surge follows a public controversy
Fictional teaching case, not a client investigation.
Which evidence supports coordination, and which competing explanations remain possible?
Observation, interpretation and limit
Observation
What it establishes
What remains unproven
Several reviews appear in a short period with similar wording.
A temporal and lexical cluster is visible in the sample.
Shared news can produce similar reactions without central organisation.
Some reviews describe a specific service; others repeat the controversy.
The contents do not all refer to the same kind of experience.
A service narrative alone does not establish that it occurred.
Collection covers visible reviews on one platform.
The analysis covers that platform and period.
Removed reviews, other platforms and offline audiences are excluded.
Conclusion to record
Describe the cluster and limitations without automatically attributing coordination. Separate service reviews, controversy comments and unverifiable material before selecting a response.
What would change the conclusion?
Review with a broader sample, a chronology of public calls or available moderation material, avoiding excessive personal data collection.
Check your reasoning
Are wording similarity and close dates independent sources, or two characteristics of the same reviews?
For each point, record what the material actually supports. “Supported” applies to the specific observation, not to the entire case. A contradiction needs explanation; missing material remains an open question.
Define the question
Record the source
Test the observation
State the limits
Entries stay in this page until you leave or reload it. Nothing is saved or submitted by this tool. Use neutral references instead of personal data or credentials.
How to write a useful conclusion
Editorial examples, not findings about your case
Material
Useful wording
Next check
One dated source
The consulted source stated X on the recorded date.
Check its origin and whether it still applies.
Multiple copies of one claim
Several pages repeat X; independent corroboration is missing.
Find the original and a source with independent evidence.
Conflicting sources
A states X while B states Y; the difference is unresolved.
Compare dates, scope, identifiers and definitions.
No matching result
No result was found in the recorded scope.
Describe queries, coverage and access limitations.
What to check and what to record
Use this grid to turn the method into a reviewable case file. A missing item remains an open question. The interpretation limit prevents a finding from becoming an unsupported conclusion.
Topic-specific checks
Check
Useful record
Interpretation limit
Baseline
Review volume and cadence over a comparable period.
A legitimate campaign can abruptly change volume.
Similarity
Relevant excerpts, dates and documented repetition.
Similar wording does not prove coordination.
Handling
Affected reviews, cited rule and platform ticket.
A genuine negative review must not be equated with fraud.
Comparison base
Fictional example: 18 positive reviews from 20 responses do not describe all 200 customers invited. Record received reviews, period and invited population separately.
A high rate does not describe the people who did not respond.
Common pitfalls
Four shortcuts that weaken the result.
Equating criticism with fraud
A negative review may be legitimate.
Counting copies as sources
Repetition is not independent corroboration.
Publishing profiles
Exposing authors can harm privacy and amplify the issue.
Replying in anger
A premature accusation can displace the facts.
Practical questions
Frequently asked questions.
Do same-day reviews prove coordination?
No. A real event may prompt simultaneous reactions. Look for other clues and context.
Can a false review be removed?
Use the platform’s process with precise evidence; a suspicion alone may be insufficient.
Should every review receive a reply?
Prioritise verifiable issues and resolution needs according to volume and platform rules.
Public references
These primary references support the checks described here. The sequence and working sheet are an IIS editorial method; a cited organisation does not endorse this guide. Read each reference within its stated date, jurisdiction and scope.
FTC — How to evaluate online reviews. Consumer guidance on reviewer identity, multiple sources and possible incentives. It helps frame checks; a burst of reviews or repeated wording alone does not establish a coordinated manipulation campaign.
Editorial scope
Published by Internet Intelligence Service on 23 September 2026. Last content update: 29 October 2026. This educational guide describes a lawful, defensive method. It is not legal advice, an emergency service or authority instruction.