Google MapsGoogle MapsGoogle Maps reviews are some of the most useful review data there is, and some of the most awkward to get out. There is no download button, copy-paste barely works, and the reviews are not really sitting in the page where you would expect them. This guide explains why, and what actually gets you a clean spreadsheet.
Open a Google Maps place, view the page source, and search for a review you can clearly see on screen. It is not there. This surprises people, and it is the key to understanding the whole problem.
Google Maps does not put the reviews in the initial HTML. It loads them in batches through background requests as you scroll the review panel. The first few might arrive with the page; the rest stream in, a page at a time, each time you reach the bottom of the list. This is why the obvious approaches fail:
To export Google reviews you need something that reads them the way you do: by scrolling the panel and collecting each batch as it loads.
Google Business Profile, if the place is yours. If you own or manage the listing, Google’s own tools are the sanctioned path to your reviews. This is the cleanest option for your own business and should be your first choice when it applies. It does not help with any place you do not manage.
The Places API, for developers. Google’s Places API returns place data including a limited set of reviews, but it deliberately caps how many reviews it will return per place, so it is not a route to a complete export of a busy listing. It also needs code and a billing account. Useful inside an application, not for getting a spreadsheet.
A browser exporter, for everything else. For a place you do not own, or when you just want the file, a browser extension that reads the review panel is the practical answer. It scrolls the panel, collects each batch, and writes a spreadsheet locally.
For each review, the data worth having:
That local-guide detail is more useful than it looks. A one-star review from an account with 400 reviews carries different weight from one that is the account’s only post, and having that in a column lets you sort accordingly.
Relative dates. Google almost never shows a calendar date; it shows “a month ago”. A careless exporter either drops the date entirely or, worse, invents a precise one. The honest approach keeps the exact wording Google gave and adds a clearly-labelled estimate beside it. There is a whole article on why this matters: how Google Maps relative dates work.
Knowing when to stop. Because the panel loads endlessly, a tool has to tell the difference between “the next batch is still loading” and “there are genuinely no more reviews”. Stop too early and you get a partial file that looks complete. A good exporter watches whether new reviews are actually appearing before it decides the list has ended.
ExportReviews’s Google Maps exporter is built for exactly this, including the relative-date handling and the end-of-list detection described above.
Local reputation work is the obvious use, and reading the one and two-star reviews in order is still the highest-value first pass. But Google Maps reviews earn their keep in a second way that Trustpilot data does not: they are tied to physical locations. If you run several sites, exporting each location’s reviews and comparing complaint themes side by side surfaces which branch has a problem the others do not, which is exactly the thing that is invisible from a single blended star average.
There is more on the local-SEO angle in using Google reviews for local SEO.
The reviews are public, but they are written by real people, so the same habits apply as anywhere: do not republish reviewer names, do not build profiles of individual reviewers, and scroll at a human pace rather than trying to rip through thousands of reviews as fast as possible. A tool that keeps the data on your device, and paces itself, is doing right by both you and the platform.
Because they are not really on the page in the usual sense. Google Maps loads reviews in batches as you scroll, through background requests, rather than putting them all in the initial HTML. Copy-paste gets you the handful currently on screen, and view-source gets you almost none, which is why exporting Google reviews needs a tool that reads them as they load rather than one that reads the page once.
You can export what any visitor can see, because the reviews are public. What you cannot do through Google's own tools is pull another business's reviews in bulk: the official routes are built for owners managing their own listing. A browser exporter reads the public review panel the same way a person scrolling it would.
Google displays relative dates like 'a month ago' rather than calendar dates. A good exporter keeps that exact wording in one column and adds a best-effort calendar estimate in another, clearly marked as approximate. It never invents a precise date it does not have, because a fabricated 2026-06-14 is worse than an honest 'about a month ago'.
Yes, where the business has replied. The owner's response and its relative date sit alongside the review in the panel, so both can be captured into their own columns. For reputation work this is often the most useful part, because response rate and tone say a lot about how a place is run.
As many as the panel will scroll through, which for a busy place can be thousands. The real constraints are time and pacing: reading several thousand reviews means scrolling the panel that many times, and doing it at a reasonable rate rather than hammering Google.
Ready to export Google Maps reviews?
Export the reviews of any Google Maps place to CSV, Excel or JSON, straight from your browser. Ratings, text, dates, owner replies and more, in one click.
See the Google Maps exporter