Shopify App Store reviews

Shopify App Store Review Scraper Apify — apps.shopify.com ratings, pricing hints, and themes

Shopify App Store Review Scraper (Store id taroyamada/shopify-app-store-review-intelligence) reads public Shopify App Store listing and paginated review pages you supply. The live Store description is: extracts and normalizes Shopify App Store app metadata, ratings, pricing hints, review samples, and keyword-based theme/feature-request rollups. Required input is appUrls. It is not a G2 or Capterra review-page tool and not an Apple Podcasts review RSS tool — those jobs belong on G2 & Capterra Review Scraper and Apple Podcasts Reviews Scraper.

$30.00 / 1,000 shopify app review and pricing reports ($0.03 per delivered app-level report titled Shopify app review and pricing report)

Open Shopify App Store Review Scraper on Apify

Shopify App Store merchant listings, not G2/Capterra pages or podcasts

Use this page when the job is merchant feedback on a Shopify app listing: praise patterns, complaint clusters, pricing posture, and onboarding friction from public App Store pages. Use G2 & Capterra Review Scraper when the source is a public G2 or Capterra product review page. Use Apple Podcasts Reviews Scraper when the source is Apple/iTunes Customer Reviews RSS for podcast collection IDs.

This Actor G2 & Capterra Review Scraper Apple Podcasts Reviews Scraper
Source Public apps.shopify.com/{slug} listing and review pages Public G2 and Capterra review-page HTML Official iTunes Customer Reviews RSS JSON
Primary input appUrls (listing URLs or slugs) reviewPageUrls (G2 or Capterra review URLs) podcastIds, countries, maxPagesPerPair
Reviewer fields Merchant storeName, location, usage duration, developer replies Normalized author, pros, cons, verified Podcast reviewerName, rating, title, content, storefront
Deliverable One app-level report: rating, pricing hints, AI summary, samples, theme rollups Per-product row: ratings, breakdown, review samples, status Raw podcast_review rows or one podcast_review_report
Published price $30.00 / 1,000 shopify app review and pricing reports ($0.03 per app-level report) from $10.00 / 1,000 results ($0.01 per result; Actor Start $0.001) from $3.00 / 1,000 apify-default-dataset-items; $1.50 per review report

This Actor does not accept reviewPageUrls, podcastIds, Apple show URLs, or episode feeds. It does not search Apple Podcasts, snapshot Top Podcasts ranks, or read iTunes review RSS. None of these Actors is affiliated with or endorsed by Shopify, G2, Capterra, or Apple. Review text is public source material for reputation and market research. Do not use the output to target individual merchants or reviewers.

Use cases

What it does

For each app URL or slug you provide, the Actor:

  1. Fetches the public listing page at apps.shopify.com/{slug}.
  2. Extracts structured metadata from JSON-LD and HTML (name, developer, description, icon, category).
  3. Parses the rating summary — overall score, total review count, per-star distribution, and star counts.
  4. Extracts pricing plan details — plan names, pricing hints, free-trial indicators, and feature-list snippets.
  5. Collects the AI-generated review summary that Shopify surfaces on listing pages.
  6. Samples individual reviews from listing and paginated review pages (stars, date, store name, location, usage duration, body text, developer replies).
  7. Builds keyword-based rollups — top themes (support, ease of use, bugs, billing, onboarding, and similar) and feature-request excerpts.

How does Shopify App Store Review Scraper differ from G2/Capterra product pages and Apple/iTunes review RSS?

This Actor fetches public Shopify App Store merchant listings at apps.shopify.com/{slug}. Required input is appUrls (full listing URLs or bare slugs). Each delivered app-level report covers listing metadata, rating summary, pricing hints, Shopify’s listing AI review summary, sampled merchant reviews, and keyword theme rollups. G2 & Capterra Review Scraper reads public G2 and Capterra review-page HTML (reviewPageUrls) and normalizes product ratings with nested reviews[] that include pros and cons. Apple Podcasts Reviews Scraper reads Apple/iTunes Customer Reviews RSS JSON for podcast collection IDs and storefronts. This Actor does not accept reviewPageUrls, podcastIds, Apple show URLs, or episode feeds.

Which appUrls formats does the published Shopify App Store schema accept?

appUrls is required. The published schema accepts Shopify App Store URLs or bare slugs. Other published fields:

Field Type Default Notes
appUrls string[] required Listing URLs or slugs (for example https://apps.shopify.com/omnisend or omnisend)
reviewLimit integer 100 Max reviews per app. README documents 1–500
timeoutMs integer 20000 HTTP timeout per page in milliseconds
delivery string dataset dataset or webhook
webhookUrl string — POST target when delivery is webhook
dryRun boolean false Skip dataset and webhook writes

The schema sets additionalProperties to false. Use appUrls, not unpublished aliases. The published input schema does not include appSlugs, maxReviewsPerApp, sinceDays, sortBy, reviewPageUrls, podcastIds, or countries.

Published input example (matches the schema):

{
  "appUrls": [
    "https://apps.shopify.com/omnisend",
    "klaviyo-email-marketing"
  ],
  "reviewLimit": 50,
  "delivery": "dataset",
  "dryRun": false
}

Single-listing Store example:

{
  "appUrls": ["https://apps.shopify.com/omnisend"],
  "reviewLimit": 100,
  "timeoutMs": 20000,
  "delivery": "dataset",
  "dryRun": false
}

Start with a Quickstart Baseline on 1–2 listings in dataset mode. Keep reviewLimit modest for a Recurring Baseline; raise it only when deeper theme clustering changes decisions. Use dryRun: true before recurring runs or larger watchlists.

Run a listing report on Apify

Why do Store README input examples use appSlugs, maxReviewsPerApp, sinceDays, and sortBy?

Those names appear in README Input Examples (Single app reviews, Competitor portfolio, Recent only). They are not live schema fields. The published input schema requires appUrls, sets additionalProperties to false, and does not include appSlugs, maxReviewsPerApp, sinceDays, or sortBy. Use the Store Quickstart appUrls sample, not those README aliases.

What fields are on an apps[] listing report versus nested reviewSamples[]?

A good first run gives you apps[] (one merchant-review row with rating, pricing hints, AI summary text, and recurring themes), nested reviewSamples[] plus rollups (raw evidence and grouped complaints), and warnings / endpointStatuses when review pages are thin or a listing surface degrades.

Published README sample shape:

{
  "meta": {
    "generatedAt": "2026-04-10T17:06:42.111Z",
    "implementationStatus": "live",
    "totalSources": 1,
    "totals": {
      "apps": 1,
      "ok": 1,
      "errors": 0,
      "warningCount": 0,
      "totalReviewsSampled": 10
    },
    "notes": ["..."]
  },
  "apps": [
    {
      "slug": "omnisend",
      "url": "https://apps.shopify.com/omnisend",
      "status": "ok",
      "app": {
        "name": "...",
        "developer": "...",
        "description": "...",
        "icon": "...",
        "category": "..."
      },
      "rating": {
        "overall": 4.8,
        "totalReviews": 2939,
        "distribution": { "5": 90 },
        "starCounts": { "5": 2632 }
      },
      "pricing": {
        "hasFreeOption": true,
        "hasFreeTrial": false,
        "pricingHint": "Free to install",
        "plans": ["..."]
      },
      "reviewSummary": "Merchants praise this app for ...",
      "reviewSamples": [
        {
          "id": "2090002",
          "stars": 5,
          "date": "February 21, 2026",
          "storeName": "...",
          "body": "..."
        }
      ],
      "rollups": {
        "themes": [{ "theme": "customer support", "count": 5 }],
        "featureRequests": ["..."]
      },
      "warnings": [],
      "endpointStatuses": { "listing": "ok", "reviews": "ok" },
      "error": null
    }
  ]
}

That sample is the published README illustration, not a live coverage guarantee. Nested reviewSamples[] in the sample show id, stars, date, storeName, and body. There is no separate published dataset/output JSON schema on the Store page.

Does the published reviewSamples[] list include location, usage duration, and developer replies?

README What it does prose lists sampled reviews as stars, date, store name, location, usage duration, body text, and developer replies. The published README JSON sample for reviewSamples[] shows id, stars, date, storeName, and body. Location, usage duration, and developer replies are README prose, not names in that sample object. Do not treat intro prose as extra guaranteed output fields.

How do JSON-LD listing pages and paginated merchant reviews become one app-level report?

For each app URL or slug, the Actor fetches the public listing page at apps.shopify.com/{slug}, extracts structured metadata from JSON-LD and HTML, parses the rating summary, extracts pricing plan details, collects the AI-generated review summary Shopify surfaces on listing pages, samples individual reviews from listing and paginated review pages, and builds keyword-based rollups (themes such as support, ease of use, bugs, billing, onboarding, and feature-request excerpts). The billed deliverable is one app-level report, not one event per nested review sample.

What do warnings and endpointStatuses report when a Shopify listing or review page is thin?

If certain surfaces are unavailable (for example no reviews or a changed HTML structure), the Actor returns explicit warnings instead of failing silently. A good first run also exposes endpointStatuses for the listing and reviews surfaces so thin review pages or a degraded listing are visible. Use those fields instead of treating a thin listing as a silent empty success.

How do reviewLimit and timeoutMs bound a Shopify App Store listing run?

reviewLimit is the maximum reviews to collect per app (integer, default 100). The README documents the range 1–500. timeoutMs is the HTTP request timeout per page in milliseconds (integer, default 20000). Start with a Quickstart Baseline on 1–2 listings in dataset mode. Keep reviewLimit modest for a Recurring Baseline; raise it only when deeper theme clustering changes decisions. Use dryRun: true before recurring runs or larger watchlists.

How is a billed Shopify app review and pricing report different from one nested review sample?

The live billed event title is Shopify app review and pricing report at $0.03, charged once for each delivered app-level report containing public rating, pricing, sampled-review, and feedback-theme evidence. The published README output is one apps[] item with nested reviewSamples[] and rollups. There is no separate published per-review billing event. README cost control says total cost mainly follows how many app listings you analyze and how many review pages you sample.

What is the live PPE event for a Shopify app review and pricing report?

Billing is pay-per-event. The live Store card is $30.00 / 1,000 shopify app review and pricing reports. The published event is Shopify app review and pricing report at $0.03, charged once for each delivered app-level report containing public rating, pricing, sampled-review, and feedback-theme evidence. Platform usage is free. You are not charged for Apify platform usage, only the fixed event price. There is no Actor Start event on this Actor’s Store pricing table.

Total cost mainly follows how many app listings you analyze and how many review pages you sample. Keep reviewLimit modest while validating the schema. Use dataset delivery first. Check the Store pricing card for the current per-event rates.

$30.00 / 1,000 shopify app review and pricing reports ($0.03 per delivered app-level report titled Shopify app review and pricing report)

See Shopify App Store Review Scraper pricing on Apify

When does webhookUrl POST a Shopify listing report, and what does dryRun skip?

delivery defaults to dataset. Set delivery to webhook and provide webhookUrl to POST results after the payload shape is useful. dryRun true runs without saving results to the dataset or webhook. The published enum is dataset or webhook. The Store quickstart starts with a single-listing dataset run (Quickstart Baseline), then a multi-app Recurring Baseline, then Webhook Routed Alerts once the schema is stable.

Open Shopify App Store Review Scraper on Apify

Does Shopify App Store Review Scraper accept reviewPageUrls, podcastIds, or Apple show URLs?

No. Required input is appUrls. additionalProperties is false, so unpublished fields such as reviewPageUrls, podcastIds, countries, Apple show URLs, episode feeds, appSlugs, maxReviewsPerApp, sinceDays, and sortBy are not accepted. G2 and Capterra product review pages belong on G2 & Capterra Review Scraper. Apple/iTunes podcast review RSS belongs on Apple Podcasts Reviews Scraper. Use the Review Intelligence pack to choose among those three sources.

Does Shopify App Store Review Scraper accept a Partner login, cookie, or private App Store API field?

No. The published input schema is appUrls, reviewLimit, timeoutMs, delivery, webhookUrl, and dryRun. There is no login, cookie, API key, Partner token, or private-endpoint field. The Actor fetches public apps.shopify.com listing and paginated review pages. This independent Actor is not affiliated with or endorsed by Shopify. Review text is public source material for reputation and market research. Do not use the output to target individual merchants.

Are the $9 release_review_snapshot_report and $29 release_regression_report events on this Actor's PPE card?

No. Those prices belong to the follow-on Actor App Release Review Regression Report (release_review_snapshot_report at $9 and release_regression_report at $29). They are README After this run / Related paid report workflow prices, not events on this Actor’s live Store PPE table. This landing’s live card is $30.00 / 1,000 shopify app review and pricing reports ($0.03 per delivered Shopify app review and pricing report).

How to start a run

  1. Open this page, then the Actor on the Apify Store.
  2. Pass 1–2 public appUrls (listing URLs or slugs). Keep reviewLimit modest on the first run.
  3. Leave delivery on dataset. Raise reviewLimit only when deeper theme clustering changes decisions.
  4. Use dryRun: true before a recurring watch. Switch to webhook only after the payload shape is useful.

Open Shopify App Store Review Scraper on Apify

Related actors

Related pages