---
name: product-review
description: Write detailed product and tool reviews with hands-on testing and clear recommendations.
---

# Skill: Product Review

Reviews for tools, plugins, themes, hosting, and services on gauravtiwari.org.

## Specifications

| Attribute | Value |
|-----------|-------|
| Default length | 2500+ words |
| Tone | Honest, experienced user |
| Verdict | Required (clear recommendation) |
| Comparisons | vs main alternatives |
| FAQs | Required (5-8) |

## Review Philosophy

This is not a press release. It's an honest assessment from someone who's actually used the product.

**Include:**
- What works well
- What doesn't work
- What you DON'T use (features you've disabled)
- Who should buy it
- Who should NOT buy it
- Specific use cases from experience

**Never:**
- List every feature
- Avoid criticism
- Recommend to everyone
- Skip pricing context

## Related Resources

- See `_common-patterns.md` for: Who Should/Shouldn't, Pricing Tables, Comparison patterns
- See `_acf-blocks-for-writing.md` for: Product Review block, Pros/Cons block, CTA block
- For comprehensive reviews (3500+ words), use `software-review.md` instead

## Article Structure

```markdown
[Opening - What is it, who is it for, verdict preview]

## What [Product] Actually Does

[2-3 paragraphs explaining core function]

## My Experience with [Product]

[Personal testing context, how long, what sites]

## Key Features That Matter

### Feature 1
[Why it matters, not just what it is]

### Feature 2
[...]

## What [Product] Does Well

[Specific benefits with evidence]

## What [Product] Doesn't Do Well

[Honest limitations]

## Pricing

[Full breakdown with value context]

## [Product] vs Alternatives

### vs [Alternative 1]
### vs [Alternative 2]

## Who Should Use [Product]

[Specific reader profiles]

## Who Should NOT Use [Product]

[Be honest about bad fits]

## Verdict

[Clear recommendation with context]

## Frequently Asked Questions

[ACF Accordion - 5-8 FAQs]
```

## Opening Template

Start with:
1. What it is (one sentence)
2. Who it's for
3. One clear benefit
4. One honest limitation

**Example:**
> FlyingPress is a caching plugin that focuses on Core Web Vitals. It's best for bloggers and small business sites who want speed without complexity. The automatic critical CSS generation actually works (unlike most competitors). Downside: documentation is sparse, and support is email-only.

## Personal Experience Section

Always include:
- How long you've used it
- On how many sites
- What type of sites
- Traffic range

**Example:**
> I've used FlyingPress on 12 sites over the past 8 months. Mix of blogs, small e-commerce, and membership sites. Traffic ranging from 1,000 to 50,000 monthly visitors.

## Features Section

Don't just list features. Explain why they matter.

**Bad:**
> FlyingPress includes page caching, CSS optimization, and JavaScript deferral.

**Good:**
> Page caching is dead simple. One toggle. I tested against WP Rocket on identical staging sites. FlyingPress was 0.3 seconds faster consistently. The automatic critical CSS generation actually works, which I can't say for every plugin.

## Limitations Section

Be genuinely honest. Readers trust reviews that acknowledge problems.

**Example:**
> Documentation is sparse compared to WP Rocket. If something breaks, you're searching forums, not reading official guides. Also no phone support. Email only, usually 24-48 hour response.

## Pricing Section

Include:
- All plan tiers
- Per-site costs
- Annual vs monthly
- Renewal pricing (if different)
- Competitor comparison

**Format:**
```markdown
| Plan | Sites | Price/Year | Per Site |
|------|-------|------------|----------|
| Starter | 1 | $60 | $60 |
| Pro | 5 | $120 | $24 |
| Agency | Unlimited | $250 | varies |

**Comparison:** WP Rocket is $59 for one site, $299 for unlimited. For 3+ sites, FlyingPress is cheaper.
```

## Comparison Section

For each alternative:
1. Key difference
2. When to choose alternative
3. When to stick with reviewed product

**Example:**
> **FlyingPress vs WP Rocket**
>
> WP Rocket is easier to set up. FlyingPress is faster once configured. If you want to install and forget, get WP Rocket. If you're willing to spend an hour tweaking settings, FlyingPress gives better results. I use FlyingPress on my own sites.

## Recommendation Matrix

Use this structure:

**Get [Product] if:**
- [Specific condition]
- [Specific use case]
- [Specific user type]

**Skip [Product] if:**
- [Specific condition]
- [Better alternative scenario]
- [Poor fit situation]

## Verdict Section

Clear, actionable, specific.

**Template:**
> [Product] is best for [specific audience] who want [specific outcome]. The [key benefit] is worth the [price/tradeoff]. [One honest caveat]. If [alternative condition], consider [alternative] instead.

**Example:**
> FlyingPress is best for performance-focused bloggers who want fast sites without complexity. The automatic optimization is worth the $60/year. Documentation could be better. If you need extensive hand-holding and phone support, WP Rocket is the safer choice.

## Affiliate Disclosure

If affiliate link present, include:
```markdown
*Disclosure: Some links in this review are affiliate links. I only recommend tools I actually use.*
```

## Review Tone Calibration

### Positive Review
Still include 2-3 genuine criticisms. Perfect reviews aren't trusted.

### Negative Review
Acknowledge what it does well. Explain who might still benefit.

### Mixed Review
Be clear about the conditions for each verdict.

## Specific Numbers

Always include:
- Load time benchmarks
- Uptime percentages
- Support response times
- Price per unit
- Time to implement

**Example:**
> Support responded in 4 hours on a weekend. Load time dropped from 2.8s to 0.9s. Setup took 20 minutes including testing.

## FAQ Section

Include these question types:
1. Is it worth the price?
2. Free alternatives?
3. Comparison to [main competitor]?
4. Refund policy?
5. Support quality?
6. Specific use case questions

## Image Placement

Include screenshots and visual proof throughout reviews.

### Required Images

| Section | Image Type |
|---------|------------|
| Features | Screenshot of interface/dashboard |
| Performance | Before/after benchmarks, PageSpeed scores |
| Pricing | Pricing table screenshot (optional) |
| Verdict | Product logo or hero image |

### Syntax

```markdown
[IMAGE: Screenshot of FlyingPress settings panel showing caching options]
Alt: FlyingPress plugin settings interface with recommended configuration
```

---

## ACF Blocks for Reviews

### Mid-Article Pros/Cons (after features section)

```html
<!-- wp:acf/pros-cons {"name":"acf/pros-cons","data":{"pc_show_first":"positive","pc_pros_title":"What I Like","pc_pros_list":"<ul>\n<li>Pro 1</li>\n<li>Pro 2</li>\n</ul>","pc_cons_title":"What Could Be Better","pc_cons_list":"<ul>\n<li>Con 1</li>\n<li>Con 2</li>\n</ul>"}} /-->
```

### CTA Block (after verdict)

```html
<!-- wp:acf/cta {"name":"acf/cta","data":{"acf_cta_heading":"Ready to Try [Product]?","acf_cta_description":"<p>Brief value prop.</p>","acf_cta_button_text":"Get [Product]","acf_cta_button_url":"https://gauravtiwari.org/go/product/"}} /-->
```

See `_acf-blocks-for-writing.md` for Product Review block syntax.

---

## Output Checklist

- [ ] Clear verdict in opening
- [ ] Personal experience context (how long, how many sites)
- [ ] Features explained (not listed)
- [ ] Features you DON'T use (shows expertise)
- [ ] Honest limitations
- [ ] Full pricing breakdown with comparison table
- [ ] Alternative comparisons (2-3)
- [ ] Who should buy (specific user types)
- [ ] Who should NOT buy (with alternatives)
- [ ] Specific numbers/benchmarks
- [ ] Image placeholders included
- [ ] Pros/Cons block mid-article
- [ ] 3-5 internal links
- [ ] FAQs (5-8) in ACF Accordion
- [ ] CTA block after verdict
- [ ] Affiliate disclosure if applicable
- [ ] 2500+ words
- [ ] No banned phrases
