Capterra Reviews Scraper — Ratings, Pros & Cons

Capterra Reviews Scraper is an Apify Actor for Capterra software review data. It accepts either a canonical Capterra product reviews URL or a free-text search query, and it returns one dataset record per review, plus product summary rows in search mode. Each review row can include star rating, review title, review body, pros, cons, reviewer firmographics, review date, review URL, helpful count, vendor response, and scrape timestamp. This Actor is usable through Apify MCP.

Best fit and connected workflows

This Actor fits workflows that need Capterra review content together with product context:

• Product research workflows can collect review text, star ratings, and reviewer firmographics for a named product.
• Competitive intelligence workflows can start from a product URL and build a review dataset for analysis.
• Search-based discovery workflows can identify matching products first, then scrape reviews for selected results.
• AI agent workflows can call the Actor through Apify MCP and process returned rows one by one.
• Data pipelines can separate review rows from product rows using recordType.

Focused standalone workflow

This Actor is designed as a focused standalone workflow.

Practical scenario

A product manager wants recent feedback on Slack from Capterra. They paste the product reviews URL and set a review cap. The Actor returns rating, reviewTitle, reviewBody, pros, cons, reviewer, reviewDate, and reviewUrl, along with product context such as productRating and productReviewCount. The product manager uses those fields to summarize recurring praise and objections, then shares the dataset with the sales team for call preparation.

Input

Provide either startUrls or searchQuery.

Field	Type	Default	Purpose
startUrls	array of objects	-	Capterra product or reviews URLs to scrape. Use canonical product review URLs such as https://www.capterra.com/p/135003/Slack/reviews/. The /reviews/ suffix is optional and added automatically.
searchQuery	string	-	Product name or keyword to search on Capterra, then scrape matching products' reviews. Example: project management software.
maxReviewsPerProduct	integer	50	Upper bound on reviews extracted for each product. Accepts 1-5000.
maxProductsPerSearch	integer	5	In search mode, how many matching products to take from search results. Accepts 1-100.
includeReviews	boolean	true	In search mode, scrape reviews for each matched product when true. When false, return only product summary cards.
sortReviewsBy	string	newest	Review order before the per-product cap is applied. Values: newest, helpful.
proxyConfiguration	object	Residential US	Proxy settings for reaching Capterra. Residential proxies are the default configuration.
debug	boolean	false	Writes diagnostic extraction data to the key-value store for troubleshooting.

Focused JSON example

{
  "startUrls": [
    {
      "url": "https://www.capterra.com/p/135003/Slack/reviews/"
    }
  ],
  "maxReviewsPerProduct": 25,
  "sortReviewsBy": "newest",
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ],
    "apifyProxyCountry": "US"
  },
  "debug": false
}

Output

The dataset can contain both review rows and product summary rows. Use recordType to separate them.

Field	Type	Description
platform	string	Always capterra.
recordType	string	review for a review row, product for a product summary row.
productName	string	Software product name on Capterra.
productSlug	string	Capterra product slug in {id}/{name} format.
productUrl	string	Canonical Capterra reviews URL for the product.
productRating	number	Aggregate product star rating, from 0 to 5.
productReviewCount	integer	Total number of reviews Capterra reports for the product.
vendor	string	Vendor or brand that publishes the product.
category	string	Capterra application category.
rating	number	This review's star rating, from 0 to 5.
reviewTitle	string	Review headline.
reviewBody	string	Full review text.
pros	array of strings	Reviewer-listed pros.
cons	array of strings	Reviewer-listed cons.
subRatings	object	Per-aspect ratings such as ease of use, support, value, features, and likelihood to recommend.
reviewer	object	Reviewer firmographics: name, title, companyName, companySize, industry, verified.
reviewDate	string	Review publish date in ISO 8601 UTC.
reviewUrl	string	Direct URL to the review when available.
helpfulCount	integer	Number of users who marked the review helpful.
vendorResponse	string	Vendor's public reply to the review, if any.
scrapedAt	string	When this row was scraped, in ISO 8601 UTC.

Illustrative output record

{
  "platform": "capterra",
  "recordType": "review",
  "productName": "Slack",
  "productSlug": "135003/Slack",
  "productUrl": "https://www.capterra.com/p/135003/Slack/reviews/",
  "productRating": 4.7,
  "productReviewCount": 1000,
  "vendor": "Salesforce",
  "category": "Team Communication",
  "rating": 5,
  "reviewTitle": "Strong fit for team communication",
  "reviewBody": "Example review text from a Capterra review page.",
  "pros": [
    "Easy to onboard",
    "Useful integrations"
  ],
  "cons": [
    "Notifications can add noise"
  ],
  "subRatings": {
    "easeOfUse": 5,
    "support": 4,
    "valueForMoney": 4,
    "features": 5,
    "likelihoodToRecommend": 5
  },
  "reviewer": {
    "name": "Reviewer name",
    "title": "Operations Manager",
    "companyName": "Example Co",
    "companySize": "11-50 employees",
    "industry": "Marketing",
    "verified": true
  },
  "reviewDate": "2026-01-15T00:00:00.000Z",
  "reviewUrl": "https://www.capterra.com/p/135003/Slack/reviews/",
  "helpfulCount": 12,
  "vendorResponse": "Vendor reply text when available.",
  "scrapedAt": "2026-01-15T12:00:00.000Z"
}

How it works

The Actor opens Capterra pages in a browser-rendered workflow, then extracts review and product data from the page content. The live contract describes JSON-LD as the primary extraction source, with HTML enrichment for the final dataset. In URL mode, it scrapes the product pages you provide. In search mode, it finds matching products first and, when enabled, visits each product to scrape reviews. The sortReviewsBy field controls whether reviews are taken in newest-first or helpful-first order before the per-product cap is applied. The debug flag writes per-product diagnostic data to the key-value store, including JSON-LD nodes, selector hits, and HTML head details.

Pricing

This Actor uses Pay per event pricing on the Apify platform, plus Apify platform usage. The live contract defines these events:

• Actor start
• Review scraped
• Product found

For current pricing details, open the live Pricing tab on the Actor page.

As a simple event-count example, a run that starts once and scrapes ten reviews for one product is charged for one actor start event and ten review events. In search mode, each returned product summary card also adds a product-found event.

Use with AI agents (MCP)

This Actor is an Apify Actor usable through Apify MCP. The exact Actor identity is khadinakbar/capterra-reviews-scraper.

Tool description: given a Capterra product URL or a search query, it returns structured review rows and product summary rows in the Apify dataset.

Find Capterra reviews for Slack. Return the review rows with rating, title, body, pros, cons, reviewer firmographics, and review date. If search mode returns product cards, include those too.

Output interpretation:

• Use recordType to separate review rows from product rows.
• Use productRating and productReviewCount for product-level context.
• Use reviewer fields when you need firmographic context.
• Use reviewUrl and productUrl as provenance links back to Capterra.

Provenance, scope, pagination, and cost guidance:

• The dataset reflects public Capterra pages.
• URL mode always scrapes reviews for the provided product pages.
• Search mode can return product summary cards when includeReviews is false.
• Increase maxReviewsPerProduct when you want more review rows per product.
• In search mode, maxProductsPerSearch controls how many matching products are processed.
• Review and product counts affect event usage, so larger runs create more billed events.

Apify API example

from apify_client import ApifyClient

APIFY_TOKEN = "YOUR_APIFY_TOKEN"

client = ApifyClient(APIFY_TOKEN)

run = client.actor("khadinakbar/capterra-reviews-scraper").call(run_input={
    "startUrls": [
        {"url": "https://www.capterra.com/p/135003/Slack/reviews/"}
    ],
    "maxReviewsPerProduct": 10,
    "sortReviewsBy": "newest"
})

dataset_id = run["defaultDatasetId"]

for item in client.dataset(dataset_id).iterate_items():
    print(item.get("recordType"), item.get("productName"), item.get("rating"), item.get("reviewTitle"))

Best results and outcome guidance

Start with a canonical Capterra product reviews URL when you already know the product. Use searchQuery when you want Capterra search results to surface matching products first. Set sortReviewsBy to newest when recent feedback matters, or helpful when you want the most-upvoted reviews first. Use maxReviewsPerProduct to control how many review rows are returned for each product. In search mode, setting includeReviews to false returns product summary cards first, which is useful for discovery before a deeper scrape.

Design note

I found that the dataset contract uses one shared stream for both review and product rows, and recordType is the visible separator for downstream processing.

FAQ

When should I use startUrls instead of searchQuery?
Use startUrls when you already know the exact Capterra product page. Use searchQuery when you want Capterra search results to identify matching products first.

What changes when includeReviews is false?
In search mode, the Actor returns product summary cards with fields such as productName, productRating, productReviewCount, and productUrl.

How can I separate product cards from reviews in my pipeline?
Filter the dataset by recordType. Review rows carry review-level fields such as rating, reviewTitle, and reviewBody.

Can I sort by helpful reviews first?
Yes. Set sortReviewsBy to helpful to fetch the most-upvoted reviews before the per-product cap is applied.

Which proxy setup is intended for Capterra pages?
The live contract defines residential proxy usage as the default configuration, with the option to set the proxy country for regional Capterra domains.

Responsible use

This Actor collects publicly available information from Capterra. Use the data in ways that respect applicable laws, Capterra's terms, and reviewer privacy. Review content can include personal and firmographic information, so handle it carefully and keep your use aligned with your intended purpose.