Trustpilot Scraper - reputation, status and contact in one row
A review platform profile compresses a lot of judgement into a small amount of data: a rating, how many people contributed to it, whether the business bothers to manage the page, and whether it is still trading. The Trustpilot Scraper collects that at scale. Submit up to 1,000 queries per run in any of three forms - a plain domain, a direct Trustpilot page link, or a category URL - and each business comes back as a single row carrying seventeen fields: name, rating, review count, the categories it is listed under, claimed, closed and temporarily-closed flags, its website, the profile URL, a logo image, plus email, phone and a split address of street, city, postal code and country.
The most useful thing to understand first is what this is not. It returns the summary view of a business, not its reviews. You get a rating and a count, not the review text, reviewer names or dates - reading what customers actually wrote is a separate service in the catalogue. That boundary matters for cost as much as for content: one row per business makes this cheap enough to run across an entire market, whereas pulling every review for the same set is a different order of magnitude. The three input forms also differ in that respect. A domain or a page link resolves to one row, making a run exact to budget, while a category URL expands into every company listed in that category - which is the fastest way to map a market and the one case where row count cannot be predicted from query count. The estimator prices a job before it runs, and spending a few free-tier rows on a single category is a sensible way to learn how large one typically is.
Four details in the documented response deserve attention before anyone writes an importer. The logo URL is protocol-relative, beginning with a double slash rather than a scheme, which works inside a web page and fails in a spreadsheet or a server-side fetch - prepend https and it resolves. Missing values arrive in two different shapes: the documented record shows the profile URL as null and the phone as an empty string in the same row, so a check for only one of them will let blanks slip through. The three status flags are genuine booleans rather than the strings some services return, which is a small mercy worth knowing so nobody writes string comparisons against them. And the categories field holds an array, since a business can be listed under more than one, so flatten it deliberately when exporting to CSV rather than letting a writer stringify it arbitrarily.
Three workflows account for most of the use. Research teams submit a category and sort the results by rating to see who leads a market on customer sentiment rather than on marketing budget, using the review count to judge which scores carry weight. Agencies and sales teams look for the combination of a low rating and an unclaimed profile, which identifies a business with a reputation problem nobody is managing - and because email and phone arrive in the same row, qualifying the lead and being able to contact it are the same job. Operations teams run existing lists through for the closed and temporarily-closed flags, which catch companies that have shut and that no amount of contact enrichment would flag. On the legal side this sits at the lighter end of the catalogue: a business profile is published precisely so customers can find it, there is no personal data in the seventeen fields, and because the service returns a review count rather than the reviews, no reviewer is named or quoted anywhere in the output. The platform's terms restrict automated access as they do everywhere, nothing behind a login is touched, and exports auto-delete after 30 days. Start free: your first 500 rows cost nothing and need no credit card.