G2 Reviews Scraper

Extract software reviews for any product on G2 without a login or API key. Give it one or more product slugs or product review URLs and get back structured reviews: who wrote the review, their role and company size, the star rating, what they liked best, what they disliked, the problems the product solved for them, plus a permalink and publish date.

What it does

• Reviews by product - pass a product slug (like slack) or a full product review URL and the scraper returns the product's reviews as clean structured records.
• Structured fields - each review is split into reviewer identity, role, company size, star rating, and the standard liked / disliked / problems-solved sections rather than one blob of text.
• Many products at once - pass a list of products and they are processed in parallel.
• Clean output - every field is always present, ready to load into a sheet, database, or analysis pipeline.

Input

Field	Type	Description
products	array	Product slugs or product review URLs. Example: acme-crm, or https://www.g2.com/products/acme-crm/reviews.
maxReviewsPerProduct	integer	Cap on reviews returned per product. Default 25.
concurrency	integer	Products processed in parallel. Default 5.
proxyConfig	object	Apify proxy. RESIDENTIAL is the default and recommended.

At least one entry in products is required.

How to find a product slug

The slug is the name in the product URL. For https://www.g2.com/products/acme-crm/reviews the slug is acme-crm. You can paste the full URL or just the slug.

Example input

{
  "products": ["acme-crm", "https://www.g2.com/products/example-app/reviews"],
  "maxReviewsPerProduct": 25,
  "concurrency": 3
}

Output

Each item is a single review tagged with a type of review.

{
  "type": "review",
  "id": "12345678",
  "product": "Acme CRM",
  "productSlug": "acme-crm",
  "title": "Great fit for a growing sales team",
  "reviewer": "Jane D",
  "reviewerIndustry": null,
  "reviewerRole": "Administrator",
  "companySize": "51-200 employees",
  "rating": 4.5,
  "likedBest": "The pipeline view is easy to read and the automations save a lot of time.",
  "disliked": "Reporting could be more flexible for custom fields.",
  "problemsSolved": "It keeps our whole team aligned on deal stages and follow-ups.",
  "answers": [
    { "question": "What do you like best about Acme CRM?", "answer": "The pipeline view is easy to read and the automations save a lot of time." },
    { "question": "What do you dislike about Acme CRM?", "answer": "Reporting could be more flexible for custom fields." },
    { "question": "What problems is Acme CRM solving and how is that benefiting you?", "answer": "It keeps our whole team aligned on deal stages and follow-ups." }
  ],
  "url": "https://www.g2.com/products/acme-crm/reviews/acme-crm-review-12345678",
  "publishedAt": "2026-06-15T18:04:40.000Z",
  "scrapedAt": "2026-06-17T09:00:00.000Z"
}

Every field is always present. Unknown values are null. When a reviewer chose to stay anonymous, reviewer is null and reviewerIndustry carries their industry instead.

Use cases

• Monitor what customers say about a product on a schedule.
• Build a dataset of reviews for sentiment analysis or research.
• Track the liked and disliked themes for products in your market.
• Pull recent reviews into a sheet for the team to read.

Notes

• A run uses the Apify proxy you select. RESIDENTIAL gives the most reliable results.
• If a product is temporarily unavailable, the item is returned with a generic status (upstream_unavailable, upstream_rate_limit, or not_found) so a single failure never stops the run.
• The number of reviews available per product in a single run is bounded by the most recent window the public source exposes.

Privacy

To improve our actors we collect anonymized usage telemetry (run stats and input patterns). No personal account data is collected.