Product Review Updates reward in-depth, expert reviews while punishing thin affiliate content that regurgitates manufacturer copy. If your affiliate or review content dropped after a Review Update, the recovery pattern is specific: original testing, named reviewers with credentials, original photos/video, balanced pros and cons, and demonstrable use. This is a stricter cousin of Helpful Content Update recovery, focused on review content.
For each review page, check: - Did someone actually use the product? - Are there original photos of the actual unit (not stock)? - Is the reviewer named with relevant expertise? - Are pros AND cons covered (not just pros)? - Are alternatives mentioned with honest comparison? - Is methodology disclosed? - Are claims backed by testing data or just opinion? If most are "no", the page is review-update vulnerable.
The difference between recoverable and not: did you actually test?
Reviewer bio (visible on each review):
- Real name (not "Editorial Team")
- Credentials relevant to the category
(chef reviewing kitchen tools, photographer reviewing cameras)
- Use history with the category (years of experience)
- Link to fuller bio page
- sameAs to LinkedIn / professional profile
Use Person schema as covered in how-to-fix-author-trust-signals
to make these signals machine-readable.
Reviews with only pros read as affiliate hype. Reviews with honest cons read as actual reviews:
For each product reviewed:
- 3-5 specific pros with examples ("X works because Y")
- 2-4 specific cons (real friction points, not "nothing")
- Honest verdict on who SHOULDN'T buy this
- Better alternatives for the people who shouldn't buy this
Even paid-for-review content can be honest about cons.
Google rewards balance even with affiliate links present.
Disclose affiliate relationships — concealment hurts more.
Single-product reviews lose to comparison content. For each product, build a comparison section: - vs direct competitor 1 - vs direct competitor 2 - vs cheaper alternative - vs more expensive alternative This signals you tested in context, not in isolation. Comparison tables (per how-to-fix-content-extractability) extract well into AI engine answers AND rich-result snippets.
Either per-review OR site-wide "How we test": - What products are evaluated - Selection criteria - Testing duration and conditions - Specific tests run (battery, durability, accuracy) - Scoring rubric (if used) - Conflicts of interest policy - Update cadence Methodology pages signal serious review operation. Google's Search Quality Rater Guidelines specifically cite methodology as a quality indicator for reviews.
Review updates run several times per year, smaller than core. Recovery typically faster than core/HCU: Month 0: Update hits review content Month 0-2: Rebuild affected reviews with testing + bios Month 2-4: Next review update — partial recovery Month 4-8: Following updates — fuller recovery The condition: actually do the testing. Sites that fake it (using AI to generate "test results") stay flagged or drop further on next update.