Google MapsGoogle MapsIf you have ever exported Google Maps reviews and tried to sort them by date, you have met the problem: the dates are not dates. They are phrases like “a month ago”, “2 weeks ago”, “a year ago”. A spreadsheet cannot sort those, a chart cannot plot them, and a naive tool will either drop them or make one up.
The good news, and it is not widely understood: the exact date is not lost. It is right there in what the page loads.
Google Maps does not display a calendar date on a review. It displays a relative, rounded phrase, expressed in the largest convenient unit: “Yesterday”, “3 days ago”, “2 weeks ago”, “a month ago”, “a year ago”.
That is a display decision. When the reviews panel loads, the page receives, for each review, a precise timestamp alongside the text, the rating, the language and the owner’s reply. The interface then renders “a month ago” because that is what reads well on a map. The precision was there the whole time; it simply never reaches the screen.
This distinction matters more than it sounds, because it splits review exporters into two categories that produce visibly different files.
Relative wording fails the moment you want to do anything time-based:
That last point is the subtle one. A column of relative phrases is not merely hard to sort; it becomes actively misleading over time, because its meaning depends on a “now” that has moved on.
The tempting shortcut is to convert “a month ago” into a real date and be done with it. Take the capture date, subtract a month, write 2026-06-24, move on.
This launders a rough guess into false precision. “A month ago” might be anywhere from three to six weeks. Writing an exact day implies knowledge you do not have, and anyone downstream who sees a clean calendar date will treat it as accurate. When they later correlate reviews against a product launch or an incident, they are correlating against fiction.
There is a quick way to spot a file built this way. Sort it by date and look at the distribution: estimated dates pile up on round intervals counted back from the day of the export, and you will see suspicious clusters exactly one month, three months and one year before it. Real timestamps scatter.
An exporter that reads the data the page loaded, rather than only the text painted on screen, gets the timestamp itself. No arithmetic, no rounding, no drift. A review posted at a specific moment lands in your file with that moment, and it will still be correct when you reopen the file a year from now.
Keep two columns anyway:
The exact date. This is what you sort, group and chart on. It is a real timestamp, not a reconstruction.
Google’s own wording. Keep “a month ago” beside it. It costs one column and it is what a colleague will see if they open the same place page, so nobody has to take your conversion on trust. It is also the honest thing to do: never silently discard what the source actually displayed.
When you evaluate a Google Maps exporter, this is a fast and revealing test. Export a place and look at the date columns.
ExportReviews’s Google Maps exporter writes both: the precise timestamp Google sent, and the wording Google showed. Beyond dates, the same applies to the owner’s reply, which also carries its own date, so you can measure how long a one-star review waited for an answer instead of guessing.
“A month ago” is a rounding made for readers, not a limit on what is knowable. An exporter that only reads the screen is stuck estimating; one that reads what the page loaded is not. When you are about to build a trend, a monthly average or a correlation with an incident, the difference between an exact date and a plausible one is the difference between a finding and a coincidence. For the rest of the export workflow, see the step-by-step guide.
Yes, and it is closer to the surface than most people assume. The review panel displays a rounded phrase, but the data the page loads to draw that panel carries a precise timestamp for every review. The rounding is a display choice, not a limit of what the page has.
Yes, if it reads the data the page loaded rather than only the text on screen. An exporter that scrapes the visible wording can only estimate; one that reads the underlying response gets the exact date. That difference shows up immediately in a file: estimated dates cluster on round intervals from the day you exported, real ones do not.
In two columns. The exact date is what you sort, group and chart on. Keep Google's own wording beside it, because it is what a colleague will see if they open the same page, and having both means nobody has to take the conversion on trust.
Because it reads better. 'A month ago' tells a visitor what they need to know in three words, and an exact timestamp on a consumer page is noise. The rounding serves the reader; it just happens to be useless the moment you want to analyse hundreds of reviews at once.
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.