# G2 Capterra review dispute: what a vendor can do

A G2 Capterra review dispute works on rule breaches, not bad ratings. See what each platform removes, how to file, how to reply, and what fails.

---


A G2 Capterra review dispute succeeds only when you can show that a review breaks the platform's written rules: the reviewer is not a real user, has a conflict of interest, or the text is fabricated, copied or abusive. A review that is negative, unfair or bad for your pipeline stays up, and both platforms say so in their own guidelines. Everything else you can do is public, professional replies and better evidence for the next review you receive.

Software buyers read patterns across many reviews, read the vendor replies, and notice when a listing carries a warning. A visible warning about your own conduct, or a heated reply, can cost more than one harsh review.

This guide covers what G2 and Capterra publish about review guidelines, authenticity checks, flag routes and vendor responses, which reviews you can legitimately dispute, how to file, how to reply, and what fails. The pages were read for this guide and each rule below names its source. Platform wording changes, so check the live page before you file. One Capterra document, its Reviews Investigation Guidelines, could not be found or read, and the text says where that limits the advice. This is information, not legal advice.

<div class="box"><b>The short version</b>
<ul><li>Both platforms remove reviews for rule breaches such as fraud, conflicts of interest, abuse and non-users. Neither removes a review because it is negative or because you disagree with the opinion.</li><li>Build a short file before you report: what rule is broken, what records you hold, and what pattern you see. G2 says a concern with a second supporting reason has better odds than a complaint about vagueness alone.</li><li>Reply in public to every review you cannot remove, briefly and without private details, rewards or threats.</li><li>Never solicit only happy customers, coach what they write, pressure a reviewer or file reports on false grounds. Both platforms list these as violations and name penalties.</li></ul></div>

<figure class="keyfacts">
<div class="keyfacts-grid">
<div><b>$100</b><span>the cap G2 sets on the value of a review incentive</span></div>
<div><b>Two years</b><span>how recent a G2 reviewer's experience must be</span></div>
<div><b>None stated</b><span>decision time on a vendor report, on the pages read for either platform</span></div>
</div>
<p class="fig-src">Sources: G2 Community Guidelines (incentive cap, experience window); G2's Report a Concern and review validity pages and Capterra's community guidelines and verification FAQ, none of which gives a response time.</p>
</figure>

## What G2 and Capterra say they will and will not remove

In <a href="https://legal.g2.com/community-guidelines">G2's community guidelines</a>, as read, the platform says reviews must pass moderation before publication, that a team member checks each one after automated filters, and that G2 does not edit or remove reviews at a seller's request. <a href="https://www.capterra.com/legal/community-guidelines/">Capterra's community guidelines</a> say that it does not remove content based on disagreements with the opinions, and does not edit content at a vendor's request or simply because content is negative.

A request that says "this review is unfair" asks to change an opinion. A request that says "this reviewer is not a customer and posted the same text under two names" asks to enforce a rule. Only the second is a dispute the platforms recognize.

The table sets out how the two routes differ on the pages read.

<div class="tablewrap"><table><thead><tr><th>Point</th><th>G2</th><th>Capterra</th></tr></thead><tbody>
<tr><td><strong>Who checks reviews</strong></td><td>Automated filters, then a person; reviews must pass moderation before publication</td><td>Manual examination by a team, plus technology that checks content quality and generative AI text</td></tr>
<tr><td><strong>Vendor report route</strong></td><td>Report a Concern on the review, or the concerns route described on its seller page</td><td>Vendor portal flag; the full process sits in a document not readable for this guide</td></tr>
<tr><td><strong>Opinions</strong></td><td>Not removed for tone; G2 never suppresses negative reviews, per its seller page</td><td>Opinions are not fact-checked; content is not edited at a vendor's request or because it is negative</td></tr>
<tr><td><strong>Appeal of a decision</strong></td><td>Guidelines mention a standard review process for vendor appeals of penalties; the seller page describes no formal appeal of a concern decision</td><td>Guidelines say decisions are at the review team's sole discretion</td></tr>
<tr><td><strong>Vendor reply</strong></td><td>Allowed on the profile</td><td>Allowed through the vendor portal; encouraged for every review</td></tr>
</tbody></table></div>

## Which reviews you can legitimately dispute

You can dispute a review when you can tie it to a named rule and show it with something other than your opinion. The grounds below come from the two sets of guidelines, not from practice or hearsay. Whether a given report is upheld is the platform's decision.

<div class="tablewrap"><table><thead><tr><th>Ground</th><th>What the pages say</th><th>Evidence that helps</th><th>Odds</th></tr></thead><tbody>
<tr><td><strong>Reviewer works for a competitor or for you</strong></td><td>G2 excludes employees of the product's company and of a direct competitor; Capterra rejects competitor and conflict-of-interest reviews</td><td>Public job history you already hold as an employer or former colleague; never private data gathered by pressure</td><td>Good if documented</td></tr>
<tr><td><strong>Not a user at all</strong></td><td>G2 requires actual users; Capterra requires the actual user to write the review</td><td>No account, license, seat or invoice matching the name or company in your system</td><td>Good if records are accurate</td></tr>
<tr><td><strong>Fabricated or copied text</strong></td><td>G2 bans fabricated experiences; Capterra lists reviews written without real use, copied reviews and generative AI text</td><td>Side-by-side text, dates, matching phrasing across accounts</td><td>Fair to good</td></tr>
<tr><td><strong>Abuse, personal data, unproven accusations</strong></td><td>Capterra bars abusive language, personal details and unproven accusations of illegal conduct</td><td>The exact lines that break the rule, quoted</td><td>Good for the lines, not the review</td></tr>
<tr><td><strong>Vague or anonymous with no detail</strong></td><td>G2 says vagueness alone is not proof of inauthenticity</td><td>A second reason, such as no matching customer</td><td>Weak alone</td></tr>
<tr><td><strong>Factually wrong claim by a real user</strong></td><td>Capterra does not fact-check opinions; G2 says it cannot verify information in reviews</td><td>None that changes the outcome</td><td>Reply instead</td></tr>
</tbody></table></div>

The last two rows are where most vendor reports die. A real customer describing a real outage in strong language has a review the platform will keep. Reply, do not report.

## How G2 checks reviews and what that means for your evidence

G2 says every review is looked at by a member of its moderation team, that reviewers sign in with a work email, LinkedIn or a personal Gmail account, and that reviewers can upload screenshots, which are never made public. Published reviews carry labels. G2's pages list Validated Reviewer on published reviews, Verified Current User where screenshots were validated, and Business Partner where there may be a conflict of interest, and the guidelines page lists others such as Incentivized.

Two details matter to a vendor. First, reviewers with a business tie to a vendor or its competitor, such as a reseller, can share insight, but G2 says those reviews do not count toward scoring. Second, G2 limits reviews to experience within the past two years, so a very old experience is a possible ground, not a certain one.

The G2 pages read did not describe detection methods or flagging criteria.

## How Capterra checks reviews and where its process differs

<a href="https://www.capterra.com/reviews/faqs-verification">Capterra's verification FAQ</a> says reviews are manually examined by its team, which verifies the reviewer's identity, checks for conflicts of interest, and evaluates the review against the guidelines. Technology checks content quality and flags generative AI and plagiarized content. Proof of use may be requested during an investigation but is not required, and Capterra treats it as one factor among many.

Three Capterra points change how you plan a dispute.

- **It does not fact-check opinions.** The FAQ says the quality team must not fact check the opinions reviewers submit. A claim you can prove false still stays if it is the reviewer's stated experience.
- **It audits after publication.** The FAQ says flagged published reviews are periodically audited and may be removed. That is an outcome, not a service you can order.
- **Edits are narrow.** The FAQ says Capterra may fix typos, remove non-standard characters and hide sensitive data such as personal information, without changing the review's intent. A review that exposes personal information is a legitimate point to raise.

The FAQ says vendors can flag suspicious reviews in the vendor portal and refers to the Reviews Investigation Guidelines for the full process. That document could not be located or read for this guide, so the exact fields, evidence rules and timing of the Capterra flag are not described here. Read the guidance in the portal itself before you write your report.

## Filing a G2 concern that gets read

G2 gives the route plainly: open the three dots at the top right of the review, choose Report a Concern, explain why you believe the review is invalid, and submit. G2's <a href="https://sell.g2.com/review-validity">review validity page for sellers</a> says concerns can also go by email and that supporting material can be attached by replying to the confirmation email.

<figure class="fig">
<figcaption><b>Preparing a G2 concern</b></figcaption>
<ol class="fig-steps">
<li><b>Name the rule</b>Write one sentence stating which guideline you believe the review breaks, for example a reviewer who is not an actual user or a competitor's employee.</li>
<li><b>Gather your own records</b>Pull account lists, license or seat records, support tickets and the dates involved. Use only information you hold in the normal course of business.</li>
<li><b>Add a second reason</b>G2 says a vagueness dispute is more likely to succeed when supported by another reason. Pair it with the missing customer match or the repeated phrasing.</li>
<li><b>Keep it factual</b>State what you checked and found. No adjectives, no claims about motive.</li>
<li><b>Submit once and attach material</b>File the concern, then reply to the confirmation with documents if you have them. Do not file again unless asked.</li>
</ol>
</figure>

G2's seller page gives a strong example, a concern that a review intentionally portrays the product negatively, and a weak one, a complaint that the review is negative and low quality and should come down. It says contesting minor issues such as spelling is generally negligible, and that challenges to G2's branding or image because a review was accepted will be rejected.

## Flagging on Capterra without breaking its vendor rules

Capterra's community guidelines say content can be reported with a product link and supporting detail, and that a report triggers an investigation but does not guarantee removal. Reported content may stay visible meanwhile. Reports are handled in the order received and all decisions are at Capterra's sole discretion. It also says it does not mediate disputes between vendors and users and does not share users' contact details.

The same guidelines draw lines around your conduct, where vendors most often end up worse off. They say vendors must not contact reviewers directly in a way that could reasonably be seen as harassment, must not coach customers on what to write, must not threaten reviewers or the site, including threatening legal action over honest feedback, and must not submit reports under false pretenses or to manipulate ratings. They also say solicitation must be fair and not target users by expected sentiment.

So a Capterra flag is a narrow, factual document: the rule, what you checked, what you found. If your sales team thinks it knows who the reviewer is, that guess does not belong in a report, and acting on it can turn a weak review into your own violation.

## Replying in public to reviews you cannot remove

Capterra's FAQ encourages vendors to respond to all reviews, regardless of rating, and its guidelines say vendors can respond through site tools such as the vendor portal, that responses are the vendor's own, and that they should be respectful and professional. G2's profile allows seller replies too, and its response guide for vendors sets a simple order for a justified criticism: apology, explanation, then what you are doing to prevent it.

G2's guide also says not to reply to vague, unactionable or rude reviews. Apply that to your own tone too: a reply written to win the argument reads as the vendor's behavior, not the reviewer's.

A workable reply has four parts: thanks, a specific acknowledgment, one fact if a fact corrects the record, and an offer to continue elsewhere. It does not name the customer's account, quote private tickets or contracts, offer a gift for a changed rating, or hint at consequences. The <a href="https://www.ftc.gov/business-guidance/resources/consumer-reviews-testimonials-rule-questions-answers">FTC's staff questions and answers</a> on its reviews rule say you can respond publicly to a review and that you should watch what you say. The same document says the rule prohibits making a false accusation about the reviewer if you know it is false, and it does not prohibit contacting customers to resolve issues or asking satisfied customers to update their reviews. Both platforms add their own limits on contact, so follow their rules.

## What fails, and what turns a dispute into your own problem

The table sorts the common failures by what the vendor does and what follows.

<div class="tablewrap"><table><thead><tr><th>Tactic</th><th>What the sources say</th><th>Likely result</th></tr></thead><tbody>
<tr><td><strong>Report because the review is negative</strong></td><td>Both platforms say tone and disagreement are not grounds</td><td>No action; wasted credibility</td></tr>
<tr><td><strong>Report with no evidence</strong></td><td>G2 describes a bare "take it down" complaint as weak</td><td>Declined</td></tr>
<tr><td><strong>Ask happy customers only</strong></td><td>G2 bans collecting reviews by methods that segment out potentially negative ones and says it removes reviews it finds solicited that way</td><td>Positive reviews removed, possible penalties</td></tr>
<tr><td><strong>Offer a reward for a better rating</strong></td><td>Capterra: incentives must not depend on a positive review; FTC staff say offering incentives to remove reviews could be an unfair practice</td><td>Penalty risk, legal exposure</td></tr>
<tr><td><strong>Contact the reviewer to push</strong></td><td>Capterra bars contact that could reasonably be seen as harassment</td><td>Warning, Buyer Alert or suspension risk</td></tr>
<tr><td><strong>Threaten a lawsuit</strong></td><td>Capterra bars threats; the FTC rule bars unfounded legal threats to suppress reviews</td><td>Penalties and a worse public record</td></tr>
<tr><td><strong>Post reviews yourself or via staff</strong></td><td>Both bar vendor reviews of their own or competitors' products</td><td>Listing penalties</td></tr>
</tbody></table></div>

<aside class="callout">
<span class="callout-label">Warning</span>
<h4>Enforcement lands on the vendor listing</h4>
<p>G2's guidelines list restrictions on new reviews or listings, warning banners, removal of existing reviews or report inclusions and bans. Capterra's list includes profile comments, suspension and a Buyer Alert on the listing. One heavy-handed campaign can cost more than any single review.</p>
</aside>

On the law, the FTC's Consumer Reviews and Testimonials Rule, which the staff page says went into effect on October 21, 2024, prohibits suppressing reviews through intimidation, unfounded legal threats or false accusations about reviewers. It also covers buying reviews with a required sentiment and insider reviews without clear disclosure. The staff page says courts can impose civil penalties for knowing violations, does not address software reviews specifically, and says it provides no safe harbor. Treat it as a floor for conduct, not as a route to remove anything. Your own counsel decides how it applies to you.

## A worked scenario and a realistic timeline

Invented scenario, generic parties: a scheduling-software vendor sees four new reviews on one listing in a week. Three one-star reviews name roles at companies the vendor cannot match to any account, license or support ticket, and two of them share unusual phrasing. The fourth is from a real customer whose integration broke after an update.

The vendor reports the first three, and replies to the fourth. The timings below are our working planning assumptions, not platform commitments, because the pages read give no deadlines.

<div class="tablewrap"><table><thead><tr><th>When</th><th>Action</th><th>Output</th></tr></thead><tbody>
<tr><td><strong>Day 1</strong></td><td>Check every name and company against accounts, seats, tickets and invoices. Save screenshots of the reviews and of your findings.</td><td>A one-page record per review</td></tr>
<tr><td><strong>Day 2</strong></td><td>File G2 concerns, each stating a rule and a second reason. Use the Capterra vendor portal flag after reading its on-screen guidance.</td><td>Three reports, no duplicates</td></tr>
<tr><td><strong>Day 2 to 3</strong></td><td>Reply to the real customer with thanks, an acknowledgment, the fix status and a route to support.</td><td>A public reply that a buyer can read</td></tr>
<tr><td><strong>Week 1 to 3</strong></td><td>Wait. G2 says moderators email if they need more documentation or have an update; neither platform states a timeline, so allow weeks.</td><td>Upheld, partly upheld or declined</td></tr>
<tr><td><strong>After a decision</strong></td><td>If upheld, no action. If declined, add a short factual public comment where the platform allows and move on.</td><td>A closed file</td></tr>
</tbody></table></div>

If two of the three reports are declined, those reviews stay. That is a normal outcome. The reply, the fixed integration and the next genuine reviews do more for the rating than another round of reports.

## Where this stops: other review systems and getting more reviews

Marketplace seller feedback works differently: it is tied to order records and the marketplace's own seller policies, not the user-identity checks G2 and Capterra apply. This guide does not cover it.

Asking customers for reviews is covered by both platforms' solicitation rules, and the safe line is the one the guidelines draw: ask everyone, do not filter by expected sentiment, do not script what they write, disclose any incentive, and offer it regardless of rating. A tactic that raises your average by selecting who is asked is the one both platforms name as a violation.

## The next step: prepare the file before the next review lands

Prepare before a suspicious review arrives. Decide who checks accounts against reviews, where records are kept and who writes replies. A one-page internal rule, "no outreach to reviewers, no incentives tied to ratings, replies only through the portal", prevents the mistakes the platforms punish.

<div class="box hot"><b>If this is happening to you now</b>
<p>If a wave of reviews looks coordinated, or a review exposes private information and the platform route has stalled, we can look at the evidence and the options with you. Reputation Partners starts with a private audit of what the reviews, search results and AI answers say about your company. <a href="/audit">Request a private audit</a>.</p></div>

A weekly look at new entries on your listings also helps: a dated record of when each review appeared supports any later report and shows which complaints repeat.

## Questions people ask

### Can a vendor have a review removed from G2 or Capterra just because it is negative?

No. G2 says it does not edit or remove reviews at a seller's request, and its seller page says it will never suppress negative reviews. Capterra says it does not remove content based on disagreements with opinions or because content is negative. Removal depends on a rule breach such as a conflict of interest, fraud or abuse.

### Does a G2 concern guarantee a review will be removed?

No. G2's pages describe how to file and say the moderation team will reconsider the review's validity based on context and depth of the concern. They do not promise removal or give a timeframe. Capterra says in its guidelines that a report triggers an investigation but does not guarantee removal, and the content may stay visible meanwhile.

### Can I contact the reviewer to ask them to change or delete a review?

Be very careful. Capterra's guidelines bar contact with reviewers that could reasonably be perceived as harassment, and pressure or threats are listed as violations. The FTC staff page says offering incentives to remove reviews could be an unfair practice. If a platform offers a comment or reply tool, use that instead of private outreach.

### Can I reply to a review that I have reported?

Yes. Reporting and replying are separate. Capterra encourages replies to all reviews, and G2 lets sellers reply publicly on their profile. Keep the reply factual and free of accusations. If the review is vague, unactionable or rude, G2's vendor guidance says a reply probably will not help.

### What if a competitor's employee wrote a review of my product?

Both platforms treat this as a conflict. G2 excludes employees of a direct competitor from reviewing, and Capterra rejects competitor and conflict-of-interest reviews. Report it with factual evidence you already hold, and do not investigate the person through private channels. Whether the report is upheld is the platform's decision.