Why this signal matters for Google
A long-term review is a dated record of prolonged use: day 1, day 10, day 30, with what changed between each entry. On a website it is a single page you keep adding to over weeks: "March 3, first application", "March 18, skin feels less tight", "April 2, bottle empty, here is what I would do differently". Some people call it a logbook or a usage log. It differs from a lived testimonial, which tells an experience once it is over. Here the reader watches time pass. Take an article about invoicing software for freelancers. A test written after two hours says whether the interface is pleasant. A log kept for three months says whether tax filing went smoothly, how many times support answered, and whether the author renewed. The second text answers the only question the reader really has: does it hold up over time?
Google scores first-hand experience, and a long-term review is its most legible form. The people Google pays to judge its search results work from a long manual, the Quality Rater Guidelines (QRG). Its section 3.4 asks them to weigh whether the content creator has the first-hand experience the topic calls for: did they use the product, visit the place, live the situation? Section 3.4.1 adds that even on sensitive topics, lived experience can be the most valuable thing on the page: a forum where patients describe daily life with a condition does not need to be written by a doctor to be worth reading. A "day 45" entry with a photo of the worn item is exactly what the rater is looking for. In the audits I have run since 2010, this is the experience signal I meet least often: on most sites the test article goes up once and is never touched again.
The "E" for Experience is only a few years old, and it was added for precisely this kind of content. On December 15, 2022, Google announced on its Search Central blog that Experience was joining E-A-T: content should show real use of a product, a real visit to a place, or personal lived experience (Google announcement, 2022). A long-term review leaves traces a program can read without understanding the prose: dates that spread out, original photos whose EXIF metadata (the date and camera stored inside the file) follow one another, a page modified several times, vocabulary that shifts between the first entry and the last. A review typed in one sitting leaves none of that. You can invent a feeling. You cannot easily invent four photos of the same treadmill taken a month apart, with the belt wearing down a little more each time.
AI tools cite what they cannot produce themselves, and a record kept over time is one of those things. Ask Claude or Perplexity "does this mattress sag after a year?". The answer can only come from a page where someone slept on it for a year and wrote it down, with dates. Product listings do not say, and the model does not own a mattress. This matters even more on topics where a mistake costs the reader dearly, the subjects Google classes as YMYL: a six-month log under a new acne treatment, kept by a patient and reviewed by a named dermatologist, is a page that neither a rushed writer nor a text generator can produce. It takes a long time to make. That is exactly why almost nobody makes it.
The NeuroEEAT scoring grid (0-10)
Score your page the way a wary reader would, wondering whether you really kept the product longer than a week.
| Score | Description | Concrete indicators |
|---|---|---|
| 0-2 | No duration visible | A test or review written in one go, with no usage dates and no photo taken by the author. Nothing shows how long the product or service was used. |
| 3-4 | Duration claimed, not shown | The text says "after a month of use", but everything was written at the same time, with a single photo. No dated entries, no shift in judgment. |
| 5-6 | A real log, but thin | Three or four dated entries over several weeks, one or two photos by the author, an opinion that moves. No final verdict, no measurements, page never updated afterwards. |
| 7-8 | A documented log | Regular entries, progressive photos with EXIF intact, figures recorded over time (price paid, failures, hours of use), an honest verdict including what disappointed, a named and identifiable author. |
| 9-10 | A log that keeps going | All of the above, plus a six-month or one-year update, a short video at each milestone, a measured before-and-after comparison, and a review by a qualified person whenever the topic touches health, money or safety. |
How to audit it on your site
Open the page that claims to describe prolonged use and run these five checks in order. Each one takes under two minutes.
- 01
Find the dates, then check their order
A long-term review has dated entries, oldest to newest. If the only date is the publication date at the top, it is not a log, it is an article. Compare the first and last dates too: a "30-day test" whose entries fit inside three days gives itself away at once.
- 02
Count the entries against the duration
Thirty days of use with two entries is thin. A short note every three or four days beats a long text at the start and another at the end. The rater is not looking for length, they are looking for proof that someone came back.
- 03
Check whether the photos follow one another
Open the images. Were they taken by the author, in the same setting, at different times? Check the EXIF metadata with a free tool such as ExifTool: the capture dates should line up with the entries. One stock photo and the log loses all its value as evidence.
- 04
Underline what changed the author's mind
Read the first entry, then the last. Did the judgment move? A log where the author loves the product on day 1 and loves it exactly as much on day 30, with no nuance, reads like a text written in one sitting. Real use almost always brings a disappointment or a surprise.
- 05
Check the verdict and the update date
Does the page end with a dated conclusion: what the author would do again, what they would not, whether they still use the product? And is the page's last-modified date later than the first entry? A page never edited after publication was not kept as a log.
How to activate or improve it
Here is how I set up a long-term review for a client, from the simplest notebook to a record Google can verify line by line.
Keep the notebook
- Pick a product, service or method you genuinely use, and set a realistic span: 30 days for an everyday object, 90 days for software or a subscription.
- Publish the first entry the day you start using it, with the date, the price paid and what you expect.
- Add a short entry every three to five days: what happened, what surprised you, one photo taken with your phone.
- End with a dated verdict that says plainly whether you are keeping it, and why.
- Sign the page with your full name and a link to your bio.
Make the record verifiable
- Keep the EXIF metadata on your photos: export them without passing through an app that strips it.
- Record one or two numbers at every entry: hours of use, consumption, number of failures, support response time, weight, price.
- Shoot the same angle every time, so wear or change is visible from one image to the next.
- Show the last-updated date at the top of the page and keep the entry history visible, without deleting older ones.
- Write down what disappointed you as well: a log with no complaint convinces no one.
Extend it and have it reviewed
- Return to the page at six months and one year with a new entry and a new photo, even if nothing changed: "still in service" is information.
- Add a short video at each major milestone, shot by you, with the date on screen or in the file name.
- Mark the page up with schema.org Review (author, datePublished, dateModified, itemReviewed) and link the author to their personal page.
- For a health, money or safety topic, have the log reviewed by a qualified person and name them on the page with their credential.
- Group your long-term reviews in a dedicated section: the collection shows a habit, not a one-off stunt.
5 common mistakes to avoid
Sector specifics
The patient's log, reviewed by a clinician
A six-month record under a new treatment, kept by the person taking it, is a valuable page for Google and for readers. But it touches health: name the qualified person who reviewed it, date that review, and remind readers that one person's experience is not medical advice. The figures recorded (weight, pain out of 10, side effects) stay the author's own, with no generalization.
The job-site log
A roofer who publishes the follow-up on a roof they installed, with a photo at installation, at one year and at three years, proves two things: that they do the work and that they stand behind it afterwards. A restaurant owner can log a new oven or a new supplier. Mention the season and the weather: that is what makes wear readable.
The test that continues after the commission
On a site that earns a commission on sales, the long-term review is what separates a recommendation from an advertisement. Publish the proof of purchase, keep the log until the warranty runs out, and leave in the entry where the product let you down. A reader who sees one disappointment will believe your praise.
90 days with the tool
For software, duration matters more than first impressions: data migration, the first billing cycle, the first outage, the first support ticket. Keep the log for a quarter, note response times and the updates you received, and close on one plain question: did you renew?
Signals to activate in parallel
A long-term review draws on these neighbouring signals, and strengthens them in return:
FAQ
How do you write a long-term review of a product?
Start the day you begin using it: date, price, what you expect, one photo. Then add a short entry every three to five days with what happened, what changed and a new photo, and record one or two numbers each time (hours of use, failures, support response time). Close with a dated verdict that says whether you are keeping it. All of it lives on one page that you edit at each entry, with the last-updated date visible. The method is not the hard part. Coming back is.
How long should a long-term review last?
Long enough for something to go wrong, or to prove that nothing did. Car magazines keep test vehicles for a year and tens of thousands of miles because that is when repairs show up. For an everyday object, 30 days is a fair minimum; for software or a subscription, 90 days covers the first billing cycle and the first support request. What matters more than the total is the spread: entries spaced across the whole period, not two notes written a day apart. And the best logs never quite end: a one-line update at six months is worth more than a longer initial review.
What is the most legitimate review site?
The one that goes back to the product after publishing. Legitimacy does not come from the size of the site but from what a reader can check: a named author, a proof of purchase, dated entries spread over weeks, photos taken by that author, and a verdict that includes at least one disappointment. A large site that publishes one-day reviews with manufacturer photos is less credible on durability than a small blog that logs the same kettle for a year. Apply the same test to your own pages before judging anyone else's.
Is a long-term review the same as a usage log?
Almost. A usage log is the raw record: dates, numbers, what happened, with no conclusion. A long-term review is that log plus a verdict a reader can act on. On a website you want both on the same page: the entries provide the evidence, the verdict provides the answer. Publishing only the verdict gives Google nothing to verify; publishing only the log leaves the reader to do the work. In software circles "usage log" also means a file recording how a program was used, which is a different thing entirely.
Does a long-term review only work for cars and phones?
No, those are just the products with the biggest audiences. The format works for anything that has to hold up over time: a mattress, a pair of work boots, accounting software, a roof, a diet, a physiotherapy program, a bank account with monthly fees. The rule is the same everywhere: dated entries, evidence that follows one another, an opinion that is allowed to change. On health or money topics, add a qualified reviewer named on the page. If you can use something for a month and take a photo of it, you can log it.
Case study
Before · a test published once, never revisited
After · a long-term review kept over 90 days
Scenario built for educational purposes. The values illustrate what the log changes on the page, not a guaranteed ranking outcome · every situation is different.