YouTube Review Script Template 2026: The Format That Earns Affiliate Commissions

This template works for any physical product, software, or service review. Replace bracketed text with your specific product details.

[OPENING — 0–45s]
"I've been using [Product Name] for [X weeks/months], so this is a real review, not a first-impressions take. I've [specific usage: used it for X tasks / compared it against Y competitors / tested the specific features most reviewers skip]. By the end of this video you'll know exactly whether [Product Name] is right for you — and if it's not, I'll tell you what is.

Quick disclosure: some links in my description are affiliate links, which means I earn a small commission if you purchase through them at no additional cost to you. This doesn't influence my review — I'll cover both what works and what doesn't, and I'll tell you if I think this product is not worth buying."

[PRODUCT OVERVIEW — 45s–2:30]
"[Product Name] is [one-sentence description of what it is and who makes it]. It's designed for [target user], and it competes primarily with [2–3 main alternatives]. The price point is [$X] for [what you get — one-time purchase / monthly subscription / what's included].

Before I get into my testing results, here's who this review is and isn't for. This review is useful if you are [specific use case 1] or [specific use case 2]. If you need [different use case], this review may not apply to your situation — I'll mention an alternative at the end that's better suited for that."

[TESTING METHODOLOGY — 2:30–3:30]
"Here's exactly how I tested [Product Name] so you understand what my conclusions are based on.

I used it for [X weeks/months]. During that time I [specific tasks: edited 14 videos with it / used it to manage 3 client accounts / ran it against [competitor] on the same dataset]. I specifically tested [feature 1], [feature 2], and [feature 3] — these are the three features that determine whether this product is worth it for the use case most of you have.

I did not test [limitation of test — e.g., enterprise features / performance at very high volume / use on [specific operating system]]. If those are important to your situation, I'll flag where my results might not apply."

[5 PROS WITH EVIDENCE — 3:30–6:30]
"Let me go through what I found works well, in order of importance.

Pro number one: [Feature/Benefit]. Here's the evidence: [specific result — not 'it was fast' but 'it processed a 4GB file in 3 minutes vs. 12 minutes for [competitor]']. This matters for [specific use case].

Pro number two: [Feature/Benefit]. [Specific evidence]. What this means in practice: [concrete application].

Pro number three: [Feature/Benefit]. I want to specifically call this out because most reviews don't mention it: [specific detail that demonstrates you actually used the product].

Pro number four: [Feature/Benefit]. Compared to [alternative], [Product Name] does [specific thing] better in [specific way].

Pro number five: [Feature/Benefit]. This one surprised me. I expected [one thing] and got [better outcome]. Specifically: [detail]."

[3 CONS — HONEST, NOT SOFTENED — 6:30–7:45]
"Now for what doesn't work well. I'm going to be direct here — softening cons doesn't help you make a decision.

Con number one: [Specific problem]. This is a real limitation, not a nitpick. [Explain specifically what goes wrong, when, and how often]. If [this use case] applies to you, this could be a dealbreaker.

Con number two: [Specific problem]. [Specific evidence — not 'the interface is confusing' but 'it took me 3 hours to find the setting for X, which most users will need in the first week']. This is something the developers could fix, but as of [date of review], it hasn't been addressed.

Con number three: [Specific problem]. I want to be fair here — [competitor] handles this better. [Specific comparison]. Whether this matters depends on [your specific situation]."

[COMPARISON VS. ALTERNATIVES — 7:45–9:00]
"Before I give my verdict, let me compare [Product Name] against the two most common alternatives.

Vs. [Competitor 1]: [Product Name] wins on [specific dimension] but loses on [specific dimension]. If [use case], choose [Product Name]. If [different use case], choose [Competitor 1].

Vs. [Competitor 2]: This is closer. Both do [X] well. The difference comes down to [specific factor — price, specific feature, target use case]. My recommendation: if [condition], [Product Name]. If [other condition], [Competitor 2].

Links to all three are in the description — I've tested all of them, and the descriptions note which use case each is best for."

[VERDICT AND RECOMMENDATION — 9:00–9:45]
"My verdict: [Product Name] is [strong recommendation / conditional recommendation / not recommended] for [specific audience].

Buy it if: you are [specific user type], you need [specific capability], and [condition that makes it worth the price].

Don't buy it if: you need [capability it lacks], you're on a tight budget (because [cheaper alternative] does [X% of what this does] for [Y% of the price]), or you're [specific use case where it underperforms].

At [$price], I think it [is / is not] fair value for [target user] because [specific reason]."

[CTA — 9:45–10:00]
"If you decide to buy, the link in my description will give you [any deal / bonus / affiliate discount if applicable]. Drop any questions in the comments — I've been using this for [time period] and I'll answer from actual experience. Subscribe if you want more reviews like this — I only cover products I've actually tested."

Tech product reviews require additional sections that general product reviews do not: a specs overview, a performance benchmarks section, and a longevity assessment (how will this hold up in 12 months).

Tech Review Additional Sections:

[SPECS OVERVIEW — insert after Product Overview]
"Let me run through the key specs quickly — I'll link the full spec sheet below if you want to compare. The specs that actually matter for real-world use are: [Spec 1 and why it matters], [Spec 2 and why it matters], and [Spec 3 and why it matters]. The specs that manufacturers highlight but rarely affect daily use include [spec the manufacturer pushes but which doesn't matter much in practice — and why]."

[BENCHMARKS — insert before Pros section]
"I ran [Product] through [specific benchmarks or real-world tests]. Results: [specific numbers]. For context, [Competitor] scored [their numbers] on the same tests. What this means in real use: [translation from benchmark to actual experience — because benchmark scores often don't map directly to the tasks most users actually perform]."

[LONGEVITY ASSESSMENT — insert after Cons]
"One question tech reviews usually don't answer is: how will this hold up? Based on [X weeks/months of use], here's my assessment: [specific observations about build quality, software update frequency, company support track record]. I'd [recommend / not recommend] this as a long-term purchase because [specific reason]."

Tone guidance for tech reviews: Tech audiences respond to specificity and skepticism. Avoid superlatives ('best ever,' 'revolutionary') — they read as sponsored language. Use comparisons constantly. The phrase 'for most users' appears frequently in trusted tech reviews because it acknowledges that edge cases exist. Say what the product is bad at in the same direct language you use for what it's good at — tech audiences value intellectual honesty above brand loyalty.

Software reviews have unique requirements: the product updates frequently (note your version in the script), pricing changes (always show current pricing on screen, not in the script itself), and free trials usually exist (always mention if a free trial is available).

Software Review Specific Language:

[Version Disclosure — add to opening]
"I'm reviewing version [X.X] of [Software Name] as of [month/year]. If you're watching this more than 6 months after upload, check the description — I'll update it with any major changes to features or pricing."

[Pricing Section — add after Product Overview]
"[Software Name] has [X] pricing tiers. The tier that makes sense for most viewers watching this: [tier name] at [$X per month / year]. Here's what you actually get at that tier: [specific features]. The features that require upgrading to a higher tier that most people think they need but probably don't: [list]. The features at the higher tier worth paying for if [specific condition applies to you]: [list]. A free trial is [available / not available — if available: it's X days and requires / doesn't require a credit card]."

[Workflow Integration — add after Testing Methodology]
"Before getting into what works and what doesn't, I want to explain how I integrated this into my actual workflow. I use it for [specific task] as part of a workflow that also includes [other tools]. This matters for the review because software rarely exists in isolation — how it connects with the other tools you use is as important as what it does on its own."

Tone guidance for software reviews: Software audiences are problem-focused. They arrived at your video because they're trying to solve a specific problem. Constantly tie features back to outcomes: not 'the automation features are robust' but 'the automation saved me 2 hours per week on [specific task].' Mention free alternatives where they exist — software reviewers who pretend free alternatives don't exist lose credibility quickly with their audience.

YouTube review videos with affiliate links are regulated by the FTC in the United States and by similar consumer protection laws in most other jurisdictions. Non-disclosure of affiliate relationships is illegal, not just bad practice.

Required Verbal Disclosure (within first 60 seconds of any video with affiliate links):
"I want to be upfront: some links in my video description are affiliate links. If you click one and make a purchase, I earn a small commission at no extra cost to you. This helps support the channel. My reviews are not influenced by affiliate relationships — I'll tell you if I think a product isn't worth buying, even if I have an affiliate link for it."

Required Written Disclosure (in video description):
"DISCLOSURE: This video contains affiliate links. I may earn a commission if you make a purchase through these links at no additional cost to you. I only recommend products I have personally tested."

FTC Compliance Notes:
- The disclosure must be in a place viewers will see it before clicking links — a disclosure buried at the end of a long description does not meet FTC standards
- Verbal disclosure in the video itself, in addition to description disclosure, is the safest practice
- 'Gifted' or 'sponsored' products must be disclosed even if there is no affiliate commission — receiving a product for free creates a material connection that must be disclosed
- The disclosure language must be clear and unambiguous — 'contains affiliate links' is clear; '#ad' buried in hashtags is not

Commission Ethics — What High-Trust Review Channels Do:
High-trust review channels operate by one rule: recommend what you would recommend if you had no affiliate relationship. This is not just ethical — it is strategically correct. An audience that trusts your recommendations converts at 3–5x the rate of an audience that suspects your recommendations are financially motivated. A single dishonest recommendation that is later discovered by your audience permanently damages the trust that makes affiliate reviews profitable. The math always favors honesty.