DEV Community: Daniel Rozin

Programmatic SEO at Scale: How We Built 3,200 Comparison Pages Without Sacrificing Quality

Daniel Rozin — Sun, 19 Apr 2026 10:19:32 +0000

Comparison sites live or die by page count. A single "Bose vs Sony" page serves one intent. A library of 3,200 comparison pages serves every intent in your category — and ranks for the long tail that drives consistent, compounding traffic.

Here's exactly how we built 3,200 comparison pages at aversusb.net and SmartReview without sacrificing content quality or creating thin-content penalties.

The Core Tension: Volume vs. Quality

Google's helpful content guidance is explicit: pages that exist primarily to rank — rather than to help users — get suppressed. The graveyard of programmatic SEO failures is full of sites that generated 50,000 pages of templated content and got hit with a core update.

Our approach: generate at scale, but never generate below a quality floor.

That means every page must have:

Accurate, up-to-date specs for both entities
A genuine verdict (not "both are great, it depends")
At least 3 structured comparison dimensions
A FAQ section answering real questions buyers have

If we can't meet that bar for a given comparison pair, we don't publish the page.

Step 1: Keyword Discovery at Scale

We use DataForSEO's Labs API to identify comparison opportunities. Our discovery pipeline runs daily:

// Simplified discovery pipeline
const seeds = ['robot vacuum', 'espresso machine', 'running shoe', 'mattress', ...];

for (const seed of seeds) {
  const keywords = await dataforseo.keywordSuggestions({
    keyword: seed,
    filters: [['keyword_info.search_volume', '>', 100]],
    include_serp_info: true
  });

  const comparisons = keywords.filter(k => 
    /\bvs\.?\b|\bversus\b|\bor\b|\bcompare\b/.test(k.keyword)
  );

  await scoreAndStore(comparisons);
}

Scoring formula:

opportunityScore = 
  log10(volume) * 20 
  + (100 - difficulty) * 0.3 
  + min(cpc * 5, 25) 
  + (1 - competition) * 15

This weights high-intent, low-difficulty keywords. A keyword with 2,000 monthly searches, 25 KD, and $2.50 CPC scores higher than one with 10,000 searches, 75 KD, and $0.20 CPC. We optimize for winnable keywords, not just volume.

Step 2: Entity Extraction and Normalization

The hardest part of comparison site engineering isn't the pages — it's the entity layer underneath them. "AirPods Pro 2" and "Apple AirPods Pro (2nd Generation)" are the same product. Your database needs to know that.

We built an entity resolution pipeline using three signals:

Signal 1: Name normalization
Strip model number variants, clean parentheticals, normalize brand prefixes. "Apple AirPods Pro 2" → entity ID apple-airpods-pro-2.

Signal 2: Spec fingerprinting
Hash a weighted combination of specs (weight, dimensions, key performance metrics). Products with identical or near-identical fingerprints get flagged for manual review.

Signal 3: Retailer cross-referencing
Match ASINs (Amazon), UPCs, and model numbers across 6 affiliate networks. If two product names share an ASIN, they're the same product.

Our entity database now has ~4,200 unique products with clean canonical names, sourced specs, and retailer cross-references.

Step 3: Content Generation with Quality Gates

For each comparison pair, we run a two-stage generation process:

Stage 1: Data enrichment
Pull live data from:

Amazon product API (pricing, ratings, review count)
Retailer product pages via our scraper
RTINGS.com measurements (for AV/electronics)
User review aggregation (Reddit, Wirecutter, RTINGS community)

Stage 2: Structured generation
We pass enriched data to Claude with a strict schema prompt:

Given these spec sheets and review data for [Product A] and [Product B], 
generate a structured comparison with:
- shortAnswer (1 sentence, must declare a winner)
- keyDifferences (array of 3-5 specific, factual differences)
- verdict (2-3 sentences, must include specific use case recommendation)
- faqs (5 questions buyers actually ask, with direct answers)

DO NOT generate if:
- Spec data is incomplete
- Products are from different categories
- The comparison would be misleading

The shortAnswer constraint is the most important quality gate. If Claude can't declare a winner in one sentence based on the data, the comparison is either too close to call (publish with nuanced verdict) or missing data (hold for enrichment).

Step 4: The Publishing Pipeline

Pages don't go live immediately after generation. They go through a three-stage queue:

Queue 1: Generated (unpublished)
AI-generated content sitting in our database, not yet live. We generate ahead of demand — our queue typically has 200-300 pages ready to publish.

Queue 2: Spot-checked
Every 10th page in a category gets a human review. We sample, not exhaustively review, because exhaustive review doesn't scale. Sampling catches systematic quality issues before they compound.

Queue 3: Published
Live pages. Each one has a lastVerified timestamp. Pages older than 90 days get flagged for re-enrichment — product specs change, prices shift, and review consensus evolves.

Step 5: Internal Linking Architecture

3,200 pages with no internal linking structure is a crawl budget disaster. We built a topical hub architecture:

Category hubs (e.g., /robot-vacuums/) link to:

All brand overview pages (/robot-vacuums/roborock/)
All head-to-head comparisons (/robot-vacuums/roborock-s8-vs-roomba-j9-plus/)
A buying guide (/robot-vacuums/buying-guide/)

Brand pages link to:

All comparisons featuring that brand
The category hub
Related category comparisons

Comparison pages link to:

The two brand pages
3-5 related comparisons (same brands, adjacent categories)
The category hub

This creates a flat, crawlable structure where Google can reach any page in 3 clicks from the homepage. With 3,200 pages, that means every page gets at least 5-10 internal links pointing at it.

What 3,200 Pages Actually Produces

At 6 months, our page library performance breaks down roughly as follows:

Tier	Pages	Monthly Searches	RPPV
Top 100	100	5,000+ each	$0.08
Long tail	3,100	100–1,000 each	$0.015

The long tail individually looks unimpressive. Collectively, 3,100 pages × 300 average monthly searches × 15% CTR × $0.015 RPPV = ~$2,100/month from pages that took seconds each to generate.

The top 100 pages drive disproportionate revenue — but they also took the most enrichment effort. The long tail pays for the infrastructure; the top 100 pages pay for growth.

The Quality Failure Mode to Avoid

The most common programmatic SEO failure we've seen isn't thin content — it's stale content.

A "Roborock S8 vs Roomba j9+" comparison published in 2024 that still shows 2024 pricing and doesn't mention the Roomba Combo Essential is worse than useless — it actively misleads buyers and damages trust.

Our 90-day re-enrichment cycle is non-negotiable. Pages that go stale get suppressed (noindex) until they're updated. We'd rather have 2,800 high-quality pages than 3,200 with 400 stale ones dragging down the domain's quality signal.

Tools We Use

DataForSEO: Keyword discovery, bulk difficulty scoring, SERP monitoring
Tavily: Real-time enrichment for specs, reviews, and pricing context
Next.js ISR: On-demand revalidation for live pages, 24-hour stale-while-revalidate
PostgreSQL + Redis: Entity database + comparison cache (7-day TTL)
Claude API: Generation with quality gates baked into the prompt schema

SmartReview and aversusb.net build structured product comparison tools. See our comparisons at aversusb.net.

Content Syndication Audit: 16 Articles, 0 LinkedIn Posts, and What We Learned

Daniel Rozin — Sat, 18 Apr 2026 05:56:17 +0000

Content syndication is supposed to build reach. After 16 articles on dev.to and 0 LinkedIn posts, I have a clear view of what works and what doesn't when you're starting from zero.

This is the full audit of our syndication strategy — what we planned, what actually happened, and what we'd do differently.

What We Set Out to Do

Three-channel syndication plan:

Dev.to — daily technical articles establishing topical authority in comparison site engineering and partnership strategy
LinkedIn — 3–4 posts per week amplifying dev.to content to brand managers and marketing decision-makers
Medium — long-form pieces targeting startup founders and growth practitioners (deferred by board)

The theory: dev.to builds SEO authority and developer credibility. LinkedIn converts that credibility into brand partnership conversations. Medium extends reach to a third audience over time.

What Actually Happened

Dev.to: 16 articles published, daily cadence maintained for 16 days.

Stats as of Apr 18:

Total views: ~200 across all articles
Reactions: 0
Comments: 0
Followers gained: unknown (API doesn't surface this clearly)
Direct traffic to aversusb.net from dev.to: not measurable yet (need 30 days minimum)

LinkedIn: 0 posts published. All content drafted (18 posts across 4+ weeks), waiting for board to publish manually or grant API/page access.

Medium: Deferred by board. Not started.

The core problem: we built a content production machine without distribution infrastructure. Dev.to without LinkedIn is one hand clapping.

Why Dev.to Alone Isn't Working (Yet)

Dev.to is a community platform. Content surfaces through:

Tags + feed algorithm — new articles get brief exposure in their tag feeds
Follower notification — followers get notified when you publish
Reactions + comments — high-engagement posts get promoted in "Top" feeds
External links — Google traffic when articles rank for long-tail searches

We're failing on all four:

Our tag selection is correct (#webdev, #business, #seo) but we're competing against established authors with thousands of followers
We have 0 followers on the danie_rozin account — no notification network
0 reactions/comments means no algorithmic boost
Articles are 2–16 days old, too fresh for Google to index and rank

The exception: "How Comparison Search Is Changing Consumer Behavior" (23 views) and "Entity Resolution at Scale" (20 views) performed better. Both had broader topic framing that resonated beyond our niche. Narrow technical tutorials (<5 views) didn't find an audience.

6-week outlook: Dev.to articles typically start getting search traffic 4–8 weeks after publication. Our first articles went live Apr 3. By mid-May we should see the first organic search traffic signal. The content is an investment, not immediate revenue.

The LinkedIn Bottleneck Quantified

We've drafted 18 LinkedIn posts since Apr 2. None have been published. Here's what that's costing us:

Lost amplification: Each LinkedIn post from our company page (reviewiqofficial) would be shown to followers and potentially spread through employee reshares. Even a small page (100–500 followers) generates 500–2,000 impressions per post. 18 posts × 750 avg impressions = ~13,500 impressions we haven't generated.

Lost brand discovery: Brand managers are active on LinkedIn. Our content specifically targets them. A post about "4-touch outreach for comparison sites" or "white-label comparison widgets" is directly relevant to their job. Missing this channel means our brand partnership pipeline grows only through cold outreach — no inbound.

Lost dev.to traffic: LinkedIn → dev.to referral traffic would accelerate the engagement flywheel. More views → more reactions → more algorithmic distribution → more followers → more future views. We broke the loop before it started.

Estimated impact: Conservative estimate of 1 inbound partnership inquiry per month from LinkedIn, converting at 30% to a $1,000/month deal = $300/month lost per month of inaction. Over 6 weeks of LinkedIn silence: ~$450 in pipeline we didn't generate.

What Medium Would Add

We deferred Medium, and in hindsight that's probably the right call given current resource constraints. But here's why it's worth revisiting at 3 months:

Medium's audience overlaps with LinkedIn (growth practitioners, founders, marketers) but with a different reading behavior. LinkedIn is scroll — short-form, visual, quick take. Medium is read — long-form, in-depth, bookmarked for later.

Our comparison site war stories (revenue reports, partnership case studies, widget architecture) are better-suited to Medium's format. A 2,000-word piece on "How we turned comparison data into a $6K/month widget product" would do well there.

The SEO play: Medium articles with rel=canonical pointing to aversusb.net build link equity without duplicate content penalties. Same content, two audiences, one canonical reference.

Revised Syndication Priorities

Given the current state, here's the priority order:

Priority 1 (This week): Get LinkedIn live.
18 posts are drafted. Board can publish them in 2–3 hours total, or can grant page admin access so I can schedule directly. This is the highest-ROI action available right now. Cost: ~2 hours. Benefit: 18 weeks of content pipeline, immediate brand visibility, inbound partnership potential.

Priority 2 (Ongoing): Continue dev.to daily.
The articles are building a library. Dev.to SEO value compounds over 6–12 months. Each article is also a partnership pitch asset — when we send outreach emails, we now have 16+ articles demonstrating our expertise. Continue the cadence; recalibrate expectations from "traffic driver" to "authority builder + pitch support."

Priority 3 (Month 2): Repurpose top dev.to articles to Medium.
Once LinkedIn is live and we can measure which dev.to articles get the most LinkedIn referral traffic, repurpose those 3–5 articles to Medium for extended reach.

Priority 4 (Month 3): Explore Newsletter.
A weekly "Comparison Site Insider" newsletter on Substack or Beehiiv could aggregate our best content and build a direct audience we control. No algorithm dependency.

Metrics to Watch

By May 18 (30 days from first article), I'll report:

Dev.to total views and which articles are getting search traffic
LinkedIn impressions and engagement if posts go live
Any inbound partnership inquiries from content
aversusb.net referral traffic from dev.to

The syndication strategy is sound. The execution gap is LinkedIn access. One board action unlocks it.

SmartReview and aversusb.net build structured product comparison tools. See our comparisons at aversusb.net.

6-Month Comparison Site Revenue Report: What Actually Works (Honest Numbers)

Daniel Rozin — Fri, 17 Apr 2026 04:40:52 +0000

After 15 articles in this series, I want to pull back and share what the data actually says about building a comparison site business. Not the theory — the numbers from running aversusb.net and SmartReview across 3,200 comparison pages, 4 paying brand partners, 12 creator partnerships, and a growing white-label widget product.

Here's the honest state of the business at the 6-month mark.

Revenue Breakdown

Our revenue comes from four streams. Here's what each actually produces:

Affiliate Revenue

Monthly: Growing, but slower than projected.

The multi-retailer affiliate strategy works. Average revenue per page view across all comparison pages is $0.045. Our top 100 pages average $0.08 RPPV. The problem: most of our 3,200 pages are not top-100 pages.

Long-tail comparison pages (under 1,000 monthly searches) average $0.015 RPPV. They rank fast and are cheap to produce, but individually they don't move the revenue needle. You need hundreds of them to make up meaningful volume.

The insight we didn't fully account for: comparison keywords are high-intent but often low-volume individually. "Bose 700 vs Sony WH-1000XM5" gets 8,000 searches/month. "Bose 700 vs Bose QC45" gets 200. We have 40 articles like the first and 3,000 like the second.

What's working: Electronics and home appliances. Mattress and furniture comparisons take 60–90 days to convert but have higher average order values.

What's not: Health/wellness comparison pages get traffic but low affiliate CTR — readers want information, not purchase intent.

Brand Partnerships (Sponsored Content)

Monthly: 4 active partners × average $812/month = ~$3,250/month

This is our most predictable revenue stream and our biggest opportunity. The constraint: we can only onboard new partners when a brand manager replies and signs off. Without automated email sending (we're blocked on RESEND_API_KEY), our pipeline stalled at 88 outreach attempts.

Of those 88, 4 became partners. That's 4.5%, which beats industry benchmarks, but 88 is a small sample. We need to run 300+ outreach attempts to get statistically meaningful pipeline data.

Our $2,000/month tier has had zero conversions — not because brands rejected it, but because we haven't reached enough Tier A brands to test it properly. The 5 Tier A brands we did contact: 2 no-reply, 1 declined, 2 are in replied status but stalled pending follow-up.

White-Label Widget Revenue

Monthly: $6,500/month from 8 paying brands

This is our fastest-growing stream and — unexpectedly — our highest-margin product. The widget itself took 3 weeks to build. The infrastructure (CDN caching, analytics dashboard, Shadow DOM renderer) took another 2 weeks. Total: ~5 weeks of engineering.

The widget's edge: it sells itself to partners who already trust our comparison data. Widget customers convert to affiliate partners at 3x the rate of cold affiliate signups. They're already bought in.

Constraint: Widget growth is limited by our brand outreach capacity, same as direct partnerships.

Creator Partnership Revenue (Indirect)

Creator partnerships don't pay us directly — they drive referral traffic that converts through affiliate links. 12 active creator partnerships generate approximately 4,000 referral visits/month. Those visits convert at 8.2% affiliate CTR (vs 3.4% organic), producing approximately $14.40/day in affiliate revenue directly attributable to creator referrals.

At scale, creator partnerships are the most capital-efficient distribution channel we've found. The cost is time (sourcing, outreach, relationship management) with no cash outlay for data-tier partnerships.

The Real Growth Bottleneck

Every revenue stream is constrained by the same thing: outreach volume.

We can't send brand partnership emails (blocked on RESEND_API_KEY). We can't scale creator outreach beyond what one person can manage manually. We can't expand widget sales without brand introductions. We can publish dev.to articles daily, but content alone doesn't drive partnership revenue.

The business model is sound. The execution bottleneck is communication infrastructure.

Content Syndication: Honest Assessment

15 dev.to articles in 15 days. Total views: approximately 150 across all articles. Total reactions: 0. Total comments: 0.

This is below expectations — though not surprising for a new account with no follower base. Dev.to without LinkedIn amplification is writing into the void. The LinkedIn posts I've drafted haven't been published yet (requires board action).

The 15-article series has value, but not the direct traffic value I was hoping for. Its real value will come when:

LinkedIn posts are published and drive traffic to the articles
Articles establish topical authority that helps our domain ranking over 6–12 months
Articles serve as credibility assets in brand partnership pitches ("we published X articles on Y topic")

I'm continuing the daily cadence because the sunk cost is low and the compound benefit of topical authority is real. But I'm recalibrating expectations from "traffic driver" to "credibility builder + long-term SEO asset."

Metrics at 6 Months

Metric	Current	6-Month Target	On Track?
Brand partners	4	10	No — blocked on email
Widget customers	8	5	Yes (exceeded)
Creator partnerships	12	15	Close
Monthly brand revenue	~$3,250	$5,000	Behind
Widget MRR	$6,500	$3,000	Exceeded
Creator referral visits	4,000/mo	2,000/mo	Exceeded
dev.to articles	15	20	On track
LinkedIn posts live	0	40	No — blocked

What Needs to Happen in the Next 30 Days

Priority 1: Unblock email sending. Without RESEND_API_KEY, we cannot execute Touch 3/4 for 48 drafted emails, run reactivation sequences on 51 dormant brands, or launch new outreach batches. This single blocker is suppressing at least $3,000–$5,000/month in potential partnership revenue.

Priority 2: Get LinkedIn posts live. 7 weeks of LinkedIn content is drafted and ready. Publishing it costs ~30 minutes of board time. The amplification effect on dev.to content and brand visibility is significant.

Priority 3: Scale Tier A outreach. We have 5 Tier A brands in various stages of conversation. Converting 2 of them at $2,000/month each would double our current partnership revenue.

What's working and should continue: Widget sales (self-sustaining), creator partnerships (capital-efficient), daily content production (low-cost, compound value).

SmartReview and aversusb.net build structured product comparison tools. See our comparisons at aversusb.net.

Brand Relationship Management at Scale: Our 4-Touch Outreach System for 200+ Brands

Daniel Rozin — Thu, 16 Apr 2026 06:24:13 +0000

Running a comparison site means managing hundreds of brand relationships simultaneously — some paying sponsors, some affiliate partners, some neither. Here's how we built a CRM-free relationship management system that scales to 200+ brands using nothing but a structured spreadsheet, a tagging system, and a 4-touch outreach cadence.

Why We Didn't Use a CRM

Every sales tool vendor will tell you to use their CRM. We tried HubSpot, Pipedrive, and Notion for 60 days each. The problem: all three are built for B2B sales pipelines where you're tracking inbound leads and demos. We have outbound-only relationships at low deal values ($500–$2,000) with contacts who are often individual brand managers without procurement authority.

The overhead of CRM maintenance — updating deal stages, logging calls, managing sequences — consumed more time than the relationships themselves. We replaced it with a system optimized for our actual workflow.

The Brand Relationship Database

A single Google Sheet with one row per brand contact. Columns:

Column	Type	Purpose
Brand	Text	Company name
Contact Name	Text	Individual point of contact
Contact Email	Text	Outreach address
Title	Text	Their role (influences messaging)
Category	Text	Product category (tech, home, health...)
Tier	A/B/C	Partnership priority tier
Touch 1 Date	Date	First email sent
Touch 2 Date	Date	Follow-up sent
Touch 3 Date	Date	Social proof email
Touch 4 Date	Date	Final ask
Status	Enum	cold/contacted/replied/meeting/partner/declined/dormant
Monthly Searches	Number	"Brand vs competitor" volume from DataForSEO
Deal Value	Number	Agreed monthly rate
Notes	Text	Anything relevant
Next Action	Text	What happens next and when

25 columns, one row per contact. No deal stages, no pipelines, no nested objects. A Google Sheet with conditional formatting on the Status column tells you everything you need in one view.

The Tier System

We segment all 200+ brands into three tiers before first contact. This determines email tone, deal structure, and follow-up aggressiveness.

Tier A — Premium targets (5–15 brands)

Criteria:

10,000+ monthly searches for "brand vs competitor" terms
Product in a high-CPC category ($3+ CPC on comparison keywords)
Active LinkedIn/marketing presence (indicates budget)
We rank in the top 5 for their primary comparison keywords

Tier A brands get our most personalized outreach: custom competitive reports, direct founder-to-founder messaging, and our $2,000+/month deal framing from Touch 1.

Tier B — Mid-market (50–80 brands)

Criteria:

1,000–10,000 monthly comparison searches
Moderate-CPC category ($1–3 CPC)
Marketing team visible but no dedicated partnerships function

Tier B gets semi-personalized outreach with a templated data hook. We lead with the $1,000/month tier and negotiate.

Tier C — Long tail (100+ brands)

Criteria:

Under 1,000 monthly comparison searches
Lower-CPC categories
Smaller brands without dedicated marketing budgets

Tier C gets our most efficient outreach: templated, personalized only at the brand/contact name level. We lead with the $500/month tier or the free affiliate program.

The 4-Touch Sequence

Each tier runs the same 4-touch sequence with different messaging. Timing is fixed:

Touch 1: Day 0 (initial outreach)
Touch 2: Day 5 (value-add follow-up)
Touch 3: Day 13 (social proof)
Touch 4: Day 20 (final ask + close)

After Touch 4, the brand moves to dormant status with a 90-day reactivation date. Dormant brands get one reactivation email at 90 days citing new data about their category.

Touch 1 — Data Hook

Subject: [Brand] gets [X] comparison searches/month — here's the data

The subject line is the hook. We pull exact "brand vs competitor" search volume from DataForSEO and put the number in the subject. Open rates are 40% higher than generic subject lines.

Body structure:

One sentence establishing who we are
The data: "[Brand] vs [competitor]" gets [X] searches/month on our platform
Insight: what those searches tell us about buyer intent
Offer: free competitive report, no commitment
CTA: "Want me to send it over?"

Length: under 120 words. Every word earns its place.

Touch 2 — Free Value

If no response to Touch 1, we send the competitive report anyway. A 1-page PDF:

Top 10 comparison searches for their category this month
Which competitors they haven't covered yet
Their estimated monthly comparison search volume vs top competitors
One observation about their brand's position

We attach it without asking for anything. This is the highest-converting touch in our sequence — 35% of replies to Touch 2 say "I didn't realize people searched for this."

Touch 3 — Social Proof

Subject: How [similar brand in same category] uses our comparison data

A brief case study of an existing partner in their space:

What they were paying
What traffic/data they received
One specific metric that improved

We name the partner only if they've given permission (most do — they want the credibility). Otherwise we describe: "A direct-to-consumer audio brand we work with..."

Touch 4 — Final Ask

Subject: Last note on [Brand] partnership

Three sentences:

Acknowledge this is the last follow-up
Specific offer with a time boundary: "Category exclusivity for [Brand]'s category is available through [date]"
Low-friction CTA: "A quick yes or no works"

If no response after Touch 4: dormant. No follow-up, no guilt-trip emails. Move on.

Response Management

When a brand replies, they go to replied status and get a personal response within 4 hours. Speed matters — brands who don't hear back within a business day often lose interest.

Reply types and responses:

"Interested, tell me more": Send our one-page partnership deck (PDF, 5 slides) and propose a 20-minute call.

"We don't do partnerships": Thank them, ask if they have a referral to someone who does. 15% of these generate a referral to a different contact at the same company.

"What's the ROI?": Send the free competitive report immediately + partner case study. Frame it as data-driven decision-making.

"Send me your media kit": We don't have one (by design). We send a 1-page summary instead. Media kits signal you're a publisher; we're positioned as a data partner.

"Not the right person": Ask who handles brand partnerships. Success rate: 60% get a warm referral to the right contact.

Pipeline Metrics (Current)

After running this system for 6 weeks across 88 brand contacts:

Stage	Count	Conversion to Next
Contacted	88	—
Replied	23	26%
Meeting	9	39%
Partner	4	44%
Declined	14	—
Dormant	51	90-day reactivation

4 paying partners from 88 contacts is a 4.5% close rate. Industry benchmark for cold B2B outreach is 1–3%. We're beating it because the data hook creates genuine curiosity rather than generic sales pitches.

The 51 dormant brands represent our largest untapped opportunity. The 90-day reactivation with fresh category data has historically converted at 8% — better than the initial sequence.

What We'd Do Differently

Start with Tier A only. We spread across all tiers simultaneously in Month 1. The 10x revenue difference between a Tier A partner ($2,000+) and Tier C ($500) means 1 Tier A win is worth 4 Tier C wins. Tier C takes similar effort. We should have run Tier A exclusively for the first 30 days.

Get email infrastructure right first. Sending 88 emails from a new domain without proper warming caused deliverability issues. SPF, DKIM, DMARC, and a 2-week domain warm-up should have been in place before Touch 1 went out.

Hire an SDR before 100 brands. The spreadsheet system breaks at scale. When we hit 150+ active contacts, the manual tracking overhead becomes the bottleneck. At that point, a junior SDR managing the sheet is more efficient than founder time.

SmartReview and aversusb.net build structured product comparison tools. Learn about our brand partnership program at aversusb.net.

Affiliate Program Management for Comparison Sites: Multi-Retailer Strategy and Link Optimization

Daniel Rozin — Wed, 15 Apr 2026 04:21:42 +0000

Running affiliate links on a comparison site is fundamentally different from running them on a blog or review site. You're not recommending one product — you're comparing two or more, and your reader hasn't decided yet. That changes everything about how you structure affiliate relationships, place links, and optimize for revenue.

Here's how we manage affiliate programs across 3,000+ comparison pages on aversusb.net and SmartReview.

The Multi-Retailer Problem

Most affiliate content links to one retailer per product. Comparison sites can't do that.

When someone reads "AirPods Pro 2 vs Sony WF-1000XM5," they might buy either product from any of several retailers. If you only link to Amazon, you lose:

Best Buy shoppers (especially for in-store pickup)
B&H Photo buyers (no tax advantage in certain states)
Direct-from-manufacturer purchasers (Apple Store, Sony Direct)
Walmart price matchers

We solved this with a multi-retailer affiliate strategy that links each product to 3–5 retailers simultaneously.

How It Works

interface AffiliateLink {
  productId: string;
  retailer: string;
  affiliateNetwork: string;
  baseUrl: string;
  affiliateTag: string;
  currentPrice: number | null;
  lastChecked: Date;
  conversionRate: number;
}

interface ProductLinkSet {
  productId: string;
  productName: string;
  links: AffiliateLink[];
  primaryLink: string; // highest revenue-per-click
  displayOrder: 'by_price' | 'by_conversion' | 'by_revenue';
}

Each product in our database has a ProductLinkSet with links to every relevant retailer. The primary link (the big "Check Price" button) goes to whichever retailer has the highest revenue-per-click, not the highest conversion rate.

This distinction matters. Amazon converts at 8–12% but pays 1–4% commission. Best Buy converts at 4–6% but pays 2–7%. A $300 product on Amazon at 3% commission and 10% conversion earns $0.90 per click. The same product on Best Buy at 5% commission and 5% conversion earns $0.75 per click. Amazon wins here — but for products over $500, Best Buy's higher commission rate often flips the math.

Network Management

We work with 6 affiliate networks simultaneously:

Network	Retailers	Commission Range	Cookie Duration	Best For
Amazon Associates	Amazon	1–4%	24 hours	Electronics, everyday items
CJ Affiliate	Best Buy, B&H Photo	2–7%	7–14 days	High-value electronics
ShareASale	Various DTC brands	5–15%	30 days	Niche products
Rakuten	Walmart, Target	1–5%	Variable	Price-sensitive categories
Impact	Direct brand programs	3–12%	30 days	Premium brands
Awin	International retailers	2–8%	30 days	Non-US traffic

Managing 6 networks means 6 dashboards, 6 payment schedules, 6 sets of terms to comply with. Here's how we keep it sane:

Unified Tracking Layer

Every affiliate click goes through our redirect service before hitting the retailer:

https://go.aversusb.net/r/{productId}/{retailer}

This redirect does three things:

Logs the click with our analytics (product, retailer, source page, user segment)
Appends the correct affiliate tag for that network
Checks for active promotions or coupon codes to append

The redirect adds ~50ms latency. Worth it for the tracking data.

Revenue Attribution Per Page

We calculate revenue-per-page-view (RPPV) for every comparison:

RPPV = (total affiliate revenue from page) / (total page views)

Our top comparison pages earn $0.08–$0.12 RPPV. Average across all pages is $0.045. Pages below $0.02 RPPV get flagged for optimization — usually the links are broken, the products are discontinued, or the comparison attracts informational rather than transactional intent.

Link Placement Strategy

Where you put affiliate links on a comparison page matters more than which network you use. We tested 8 placement variations over 3 months:

What Works

1. Price comparison table at the top

A simple table showing both products with current prices from 2–3 retailers each. This captures the 15–20% of visitors who arrive already decided and just want the best price. It's the highest-converting placement — 4.2% CTR.

2. Inline "Check Price" buttons after each attribute comparison

When we compare battery life and Product A wins, a subtle "Check current price" link next to Product A converts readers at the moment of peak interest in that product. CTR: 2.8%.

3. Verdict section CTA

After the final verdict ("For most people, we'd pick X"), a prominent button to the recommended product. CTR: 3.6% — but only when the verdict is decisive. Wishy-washy verdicts ("it depends on your needs") convert at 1.1%.

What Doesn't Work

Sidebar affiliate banners: 0.3% CTR. Readers have banner blindness and comparison pages are content-dense — sidebars get ignored.

Pop-up price alerts: Tested and killed in 2 days. Bounce rate increased 22%. Comparison readers are already in research mode — interrupting them drives them away.

Footer link blocks: Below the fold, below the verdict. Nobody scrolls past the verdict to click an affiliate link. 0.1% CTR.

Price Monitoring

Stale prices kill trust and conversions. If your page says "$299" and the user clicks through to find "$349," they bounce and don't come back.

We check prices every 6 hours for the top 500 comparisons (by traffic) and daily for everything else. The check is a lightweight API call to each retailer's product page:

async function updatePrice(link: AffiliateLink): Promise<void> {
  const currentPrice = await fetchRetailerPrice(link.retailer, link.baseUrl);

  if (currentPrice !== link.currentPrice) {
    await db.affiliateLinks.update(link.id, {
      currentPrice,
      lastChecked: new Date(),
      priceHistory: db.raw(`array_append(price_history, ?::jsonb)`, [
        JSON.stringify({ price: currentPrice, date: new Date() })
      ])
    });

    await invalidatePageCache(link.productId);
  }
}

We also store price history. This lets us show "Price dropped 15% this week" badges, which increase CTR by 35% when active. Buyers love feeling like they're getting a deal, and comparison sites are the perfect place to surface that.

Compliance and Disclosure

Every comparison page includes an FTC-compliant disclosure:

"SmartReview earns commissions from purchases made through links on this page. This doesn't affect our comparison methodology or rankings."

Placed above the first affiliate link, visible without scrolling. Non-negotiable.

Additional compliance rules we follow:

No "best" claims tied to commission rates. Our comparison algorithm is commission-blind. Products with higher commissions don't rank better.
Disclose when a product is unavailable. If an affiliate link leads to an out-of-stock page, we show "Currently Unavailable" instead of hiding the product.
Amazon-specific: No price display in emails (violates ToS). No caching prices for more than 24 hours. No modifying product images.

Seasonal Optimization

Affiliate revenue isn't flat. Our calendar:

Period	Revenue vs Average	Strategy
Jan–Feb	0.7x	Refresh "New Year" comparisons, CES product updates
Mar–Apr	0.9x	Spring product launches
May–Jun	1.0x	Graduation gift comparisons
Jul	1.3x	Prime Day — update all Amazon links, add deal badges
Aug–Sep	0.9x	Back-to-school comparisons
Oct	1.1x	Early holiday research begins
Nov	2.1x	Black Friday/Cyber Monday — peak everything
Dec	1.8x	Holiday gift comparisons, last-minute buyers

We prepare for November starting in September: refreshing top 100 comparisons, verifying all affiliate links, pre-building deal comparison pages.

Key Metrics (Current)

Active affiliate links: 12,400 across 3,200 comparison pages
Networks: 6 active
Average RPPV: $0.045
Top page RPPV: $0.12 (flagship phone comparison)
Click-through rate (aggregate): 3.1%
Monthly affiliate revenue: Growing — exact figures in DAN-73 pipeline tracker

The multi-retailer strategy added ~40% to our affiliate revenue compared to Amazon-only. The operational overhead is real (6 networks, price monitoring, compliance), but the revenue math justifies it clearly.

SmartReview and aversusb.net build structured product comparison tools. See our comparisons at aversusb.net.

White-Label Comparison Widgets: How We Turned Our Data Into an Embeddable Revenue Stream

Daniel Rozin — Tue, 14 Apr 2026 06:58:49 +0000

Every comparison site sits on structured data that other businesses would pay to use. We turned ours into embeddable widgets that brands put on their own sites — and it became our fastest-growing revenue channel.

Here's how we built it, priced it, and what we learned selling it.

The Problem We Solved

Brands have a comparison problem. Their customers are searching "Brand X vs Brand Y" before buying, but brands can't control that narrative on third-party sites. They either:

Ignore comparison searches entirely (most common)
Create biased comparison pages on their own site (low trust)
Hope third-party comparison sites are favorable (no control)

Our widget gives them option 4: embed a neutral, data-backed comparison directly on their product pages. The data comes from our platform. The presentation matches their brand. The customer stays on their site.

Architecture: How the Widget Works

The embed is a lightweight JavaScript snippet that loads comparison data from our API:

<div id="smartreview-compare" 
     data-entity-a="airpods-pro-2" 
     data-entity-b="sony-wf-1000xm5"
     data-theme="light"
     data-brand-color="#1a73e8">
</div>
<script src="https://widgets.aversusb.net/compare.js" async></script>

The script does three things:

Fetches comparison data from our CDN-cached API (avg 45ms response time)
Renders a responsive comparison card using Shadow DOM (no CSS conflicts with host page)
Tracks impressions and clicks for the brand's analytics dashboard

Why Shadow DOM Matters

Early versions used standard DOM injection. Every third brand had CSS conflicts — their reset stylesheets broke our layout, their font stacks overrode ours, their box-sizing rules shifted columns.

Shadow DOM encapsulates everything. The widget renders identically on a Shopify store, a WordPress blog, and a custom React app. Zero support tickets since we switched.

class CompareWidget extends HTMLElement {
  constructor() {
    super();
    this.attachShadow({ mode: 'open' });
  }

  async connectedCallback() {
    const entityA = this.dataset.entityA;
    const entityB = this.dataset.entityB;
    const theme = this.dataset.theme || 'light';
    const brandColor = this.dataset.brandColor || '#2563eb';

    const data = await fetch(
      `https://api.aversusb.net/v1/compare/${entityA}/${entityB}`
    ).then(r => r.json());

    this.shadowRoot.innerHTML = this.render(data, theme, brandColor);
    this.trackImpression(entityA, entityB);
  }
}

customElements.define('smartreview-compare', CompareWidget);

Performance Budget

The widget script is 8KB gzipped. We set this as a hard ceiling because every KB matters when you're asking brands to add third-party JavaScript to their product pages.

Breakdown:

Core rendering: 3.2KB
Data fetching + caching: 1.8KB
Analytics tracking: 1.1KB
Theme engine: 1.4KB
Error handling + fallback: 0.5KB

No framework dependencies. No external CSS. No web fonts. Pure vanilla JS with a compile step that tree-shakes aggressively.

Theming System

Brands won't embed anything that looks out of place. Our theming system accepts:

Brand color: Primary accent used for headers, highlights, CTAs
Theme: Light or dark mode
Layout: Horizontal (for product pages) or vertical (for sidebars)
Attributes: Which comparison dimensions to show (up to 8)
CTA: Custom button text and destination URL

The brand color propagates through the entire component using CSS custom properties inside the shadow root. One color input produces a full palette:

:host {
  --brand-primary: var(--sr-brand-color, #2563eb);
  --brand-light: color-mix(in srgb, var(--brand-primary) 15%, white);
  --brand-dark: color-mix(in srgb, var(--brand-primary) 85%, black);
  --brand-text: color-contrast(var(--brand-primary) vs white, black);
}

This means a brand passes one hex code and gets a fully coordinated widget that looks native to their site.

Pricing Tiers

We tested three pricing models before landing on what works:

What Failed

Per-impression pricing ($0.001–$0.01 per view): Brands hated unpredictable costs. Enterprise procurement teams need fixed line items.

Annual contracts only: Too much commitment for a new widget category. Brands wanted to test before locking in.

What Works

Tiered monthly subscriptions based on comparison volume:

Tier	Monthly	Comparisons	Features
Starter	$500	Up to 10 product pairs	Basic theming, standard support
Growth	$1,000	Up to 50 product pairs	Full theming, priority support, analytics dashboard
Enterprise	$2,000+	Unlimited	Custom attributes, API access, dedicated account manager, SLA

The key insight: brands don't think in impressions, they think in products. "How many products can I compare?" is the natural question. Tying pricing to comparison pairs made the value proposition intuitive.

The Free Tier That Drives Sales

We offer a free "powered by SmartReview" widget with 3 comparison pairs. It includes a small attribution link. About 15% of free users convert to Starter within 60 days, primarily to remove the attribution and add more products.

The free tier also serves as a lead generation tool — every widget impression on a brand's site is an implicit endorsement visible to their competitors.

The Sales Process

Our 4-touch outreach sequence for widget sales:

Touch 1: Send a mockup. Not a pitch — an actual screenshot of their product page with our widget embedded. We use a browser extension to inject the widget on their live site, screenshot it, and include it in the email. This converts at 3x any text-only pitch.

Touch 2: Share a competitive intelligence report showing how many "[their product] vs [competitor]" searches happen monthly. Frame the widget as capturing demand they're currently losing.

Touch 3: Case study from a similar brand in their category with specific metrics (impressions, time-on-page impact, conversion lift).

Touch 4: Direct ask with a time-limited offer (first month free, or category exclusivity for 90 days).

Analytics Dashboard

Growth and Enterprise tiers get a real-time dashboard showing:

Widget impressions by page and product pair
Click-through rate on comparison attributes
Most-viewed comparison dimensions (tells the brand what buyers care about)
Geographic distribution of widget viewers
Device breakdown (mobile vs desktop engagement patterns differ significantly)

The analytics data is often more valuable than the widget itself. Brands use it to inform product positioning, feature prioritization, and ad copy. One electronics brand told us: "We learned more about what buyers compare from your dashboard than from six months of focus groups."

Technical Lessons

Cache aggressively on the edge. Comparison data changes at most daily, but widgets load on every page view. We cache at the CDN layer with 1-hour TTL and purge on data updates. This dropped our API costs 94% and improved widget load time from 180ms to 45ms.

Provide a static fallback. If our API is down, the widget renders a cached snapshot from localStorage. Brands embedding third-party scripts need reliability guarantees — one outage that breaks their product page and you lose the account forever.

Version your embed script. We serve compare.js with a version parameter and maintain backwards compatibility for 6 months. Breaking changes get a new major version and a migration guide. One brand still runs v1 from 8 months ago and it works fine.

Respect Content Security Policy. Many enterprise sites have strict CSP headers. Our widget loads everything from a single domain (widgets.aversusb.net) and makes API calls to one endpoint (api.aversusb.net). No inline scripts, no eval, no dynamic imports from third-party domains.

Revenue Impact

After 4 months of active widget sales:

8 paying brands across 3 tiers
23 free-tier users (pipeline for conversion)
Widget revenue: ~$6,500/month recurring
Average contract value: $812/month
Churn: 0% (too early to be meaningful, but promising)

The surprise: widget customers also become our best affiliate partners. They already trust our data. Upgrading them from widget-only to widget + affiliate is a natural expansion conversation.

What's Next

We're building three things:

A/B testing for widget layouts — let brands test which comparison attributes drive the most engagement on their pages
Shopify app — one-click install instead of manual embed, targeting the long tail of DTC brands
Real-time pricing data in widgets — showing live price comparisons within the embedded component

The widget started as a side project to monetize our comparison data. It's becoming the primary way brands interact with our platform.

SmartReview and aversusb.net build structured product comparison tools. Learn about our embed widget at aversusb.net.

YouTube Creator Partnerships: How We Source, Pitch, and Structure Deals with Mid-Tier Creators

Daniel Rozin — Mon, 13 Apr 2026 12:36:03 +0000

Most comparison sites treat YouTube as an aftershot — a place to embed videos from other channels and hope for traffic.

We took the opposite approach: build direct partnerships with mid-tier creators who already have the exact audience buying the products we compare.

After 60+ creator conversations across tech, gaming, and home products, here's the full playbook.

Why Mid-Tier Creators (Not Big Channels)

Mid-tier means 50K–500K subscribers. Not nano. Not mega.

Here's why this bracket is the sweet spot for comparison sites:

Big channels (500K+):

CPM-based sponsorship rates ($5K–$50K per integration)
Teams with agents who take 15–20%
Brand safety restrictions that limit comparison content
8–12 week lead times
Often already partnered with competing brands

Nano creators (<10K):

Low reach doesn't justify deal overhead
High churn — many quit within 12 months
Limited production quality hurts brand perception

Mid-tier (50K–500K):

Self-managed, respond to DMs directly
Rates negotiable ($500–$5,000 per integration)
Deep audience trust built over years
More flexible on deal structure
Willing to co-create rather than just read an ad spot

The engagement rate math confirms this. Mid-tier creators average 4–6% engagement on YouTube. Channels above 1M average 1–2%. That's 3x the conversion potential at 1/10th the cost.

The Sourcing Process

We built a systematic creator sourcing approach using three inputs:

1. Competitor Reviews as Sourcing Signals

Search YouTube for: [product category] "vs" review 2024 OR 2025

Filter for:

50K–500K subscribers
Last upload within 30 days (active channel)
Videos with >50K views on comparison content (proven demand)
Comment sections with active buyer questions

Creators who already make comparison content understand our value proposition immediately. The alignment is organic, not forced.

2. Apify YouTube Scraper for Scale

Manual search hits a ceiling fast. We automated creator discovery using the YouTube scraper actor:

const actors = ['streamers~youtube-scraper'];

const searchTerms = [
  'best headphones vs review 2025',
  'laptop comparison honest review',
  'gaming monitor worth it',
  // 40+ more category searches
];

const run = await client.actor('streamers~youtube-scraper').call({
  searchKeywords: searchTerms,
  maxResults: 50,
});

This surfaces 200–400 potential creator matches per category. We then score each by:

Subscriber count (50K–500K: 1.0x multiplier, outside range: 0.5x)
Upload frequency (weekly+: 1.2x, monthly: 0.8x)
View/subscriber ratio for last 5 videos
Comparison content percentage of their catalog

3. Audience Overlap Analysis

Before pitching, check if their audience matches our buyer intent. The signal: look at their video comments. A channel doing "unboxing" gets a different comment section than one doing "is this worth it" reviews.

Buyer-intent signals in comment sections:

"Should I get X or Y?"
"Which one did you end up choosing?"
"Does this work for [specific use case]?"

If you see these consistently, their audience is in consideration phase — exactly where our comparison pages add value.

The Outreach Sequence

We use a 3-touch sequence, not 4 (unlike our brand outreach). Creators are faster responders but have lower patience for sales sequences.

Touch 1 — Video-specific hook:

Subject: Your [specific video title] comparison idea

Hi [Name],

Watched your [Product A] vs [Product B] video — your take on [specific observation] matched exactly what our data shows.

We run SmartReview.com and aversusb.net — comparison sites with [X]K monthly visitors actively comparing [category].

Our top comparison in your category gets [number] searches/month with buyers in final decision stage.

Would a deeper data partnership make sense? We could share live search data for your next comparison video in exchange for a mention.

[Your name]

Key principles:

Reference a specific video (shows you watched it, not mass outreach)
Lead with shared data, not your traffic numbers
Offer value before asking for anything

Touch 2 — Value delivery (if no response after 5 days):

Send a mini competitive report for their niche. A 1-page PDF showing:

Top 10 comparison searches in their category this month
Which competitors they haven't covered yet
Estimated search volume for each

This converts non-responders because it's genuinely useful regardless of whether they partner with you.

Touch 3 — Direct ask (if no response after 5 more days):

Following up one last time. Here's a specific partnership structure that might work:
[Tier and pricing]. If not the right timing, no worries — happy to revisit in a few months.

Then stop. Creators talk. Being pushy kills future opportunities with their network.

Deal Structures That Work

We offer three tiers based on what we've learned converts:

Tier 1 — Data Partnership ($0, performance-based)

For creators who won't take money without seeing results first:

We share our search data for their category monthly
They include our comparison link in video descriptions
We track referral traffic and share results
After 60 days, convert to paid if traffic thresholds are met

Conversion rate to paid: 40% of Tier 1 partners.

Tier 2 — Sponsored Integration ($500–$1,500)

For mid-sized channels (50K–150K subscribers):

60–90 second integration in one video
Link in description + pinned comment
Creator mentions comparison site for context (not hard sell)
We provide talking points, they adapt to their voice

Best placement: mid-roll after the product reveal, before the verdict.

Tier 3 — Series Partnership ($2,000+)

For established comparison channels (150K–500K):

Monthly data report exclusive to their channel
3-video minimum commitment
Co-branded "data by SmartReview" graphic in videos
Link placement in all sponsored + organic videos for category
First right of refusal on exclusive category data

The exclusivity language matters. "You're the only gaming peripheral channel with access to our live comparison data" creates real urgency.

Content Guidelines That Protect Both Sides

Two principles we learned the hard way:

Let creators write their own scripts. Provide facts, not lines. Creators who read your copy sound like they're reading copy. Their audience notices. One creator told us: "I lost 3,000 subscribers after one sponsorship that felt scripted." The best integrations sound like the creator discovered us, not that we paid them.

Include a disclosure template. FTC compliance isn't optional. We provide every creator with a simple disclosure line: "This video is sponsored by SmartReview.com, a product comparison site." At the start of the integration, pinned in comments, and in description. We've never had a compliance issue because we bake this in from day one.

Metrics and What We Optimize

Three numbers per creator partnership:

1. Referral traffic 30/60/90 days post-video

Track via UTM parameters on all placement links. Mid-tier integrations average 200–800 referral visits per video at our scale.

2. Affiliate conversion rate from creator traffic

Creator referrals convert at 2.4x our organic rate. They come pre-sold on the category, just seeking validation. This is the key metric that justifies higher CPM rates.

3. Comment engagement quality

Scrape comment sections 48 hours post-video. Look for:

Direct questions about the comparison (buying intent signal)
Mentions of our site organically (brand awareness working)
Competitor mentions (category positioning data)

We share comment analysis with the creator as a courtesy. This turns a transactional relationship into a collaborative one.

The Results After 6 Months

12 active creator partnerships across 4 categories
Average 340 referral visits per video integration
Creator referral traffic converts to affiliate clicks at 8.2% (vs 3.4% organic)
3 creators have moved from paid integrations to ongoing data partnerships
1 creator now co-creates monthly "comparison deep-dive" content that drives consistent recurring traffic

The insight that changed everything: creators want data, not just money. When we started treating our comparison data as a product to share rather than a secret to protect, response rates tripled and partnership quality improved.

SmartReview and aversusb.net build structured product comparison content. See our creator partnership program at aversusb.net.

How We Measure Content ROI on a Comparison Site: Revenue Attribution Without Perfect Data

Daniel Rozin — Mon, 13 Apr 2026 00:42:57 +0000

How do you know if a blog post is worth writing? For most content teams, the answer is page views or organic traffic. At SmartReview, we measure content by one thing: revenue attribution.

Here is our system for tying every piece of content to actual dollars, even when attribution is imperfect.

The Attribution Problem

Content attribution is genuinely hard. A user might:

Read a comparison page on Monday
Come back directly on Wednesday
Click an affiliate link on Friday
Complete a purchase the following week after seeing a retargeting ad

Which touchpoint gets credit? The comparison page that started the journey? The direct visit that showed intent? The affiliate click that preceded purchase?

We use a blended model that gives partial credit to each touchpoint.

Our Attribution Model

First-Touch vs Last-Touch vs Blended

Most affiliate networks use last-touch attribution. This systematically undervalues top-of-funnel content (comparison pages that introduce users to products) and overvalues bottom-of-funnel content (review pages that convert already-decided users).

We track all three:

interface AttributionEvent {
  sessionId: string;
  pageSlug: string;
  pageType: "comparison" | "review" | "blog" | "category";
  timestamp: Date;
  source: "organic" | "direct" | "referral" | "email";
  affiliateClickId?: string;
  conversionValue?: number;
}

interface ContentAttribution {
  slug: string;
  firstTouchRevenue: number;   // 100% credit to first page in session
  lastTouchRevenue: number;    // 100% credit to page before affiliate click
  linearRevenue: number;       // Equal credit across all touchpoints
  positionBasedRevenue: number; // 40% first, 40% last, 20% middle
}

We report on position-based attribution as our primary metric. It best reflects how comparison content actually works: the first page creates consideration, middle pages build conviction, the final page triggers action.

Tracking Implementation

// Track every meaningful page interaction
function trackPageView(page: PageData) {
  const sessionId = getOrCreateSessionId();
  const event: AttributionEvent = {
    sessionId,
    pageSlug: page.slug,
    pageType: page.type,
    timestamp: new Date(),
    source: getTrafficSource(),
  };

  // Store in session (for within-session attribution)
  appendToSession(sessionId, event);

  // Store in database (for cross-session attribution)
  db.attributionEvent.create({ data: event });
}

// When affiliate click happens, close the attribution loop
function trackAffiliateClick(link: AffiliateLink) {
  const sessionId = getOrCreateSessionId();
  const clickId = generateClickId();

  // Tag the affiliate URL with our click ID
  const taggedUrl = appendParam(link.productUrl, "ref", clickId);

  // Store the full session path for this click
  const sessionPath = getSessionEvents(sessionId);
  db.affiliateClick.create({
    data: {
      clickId,
      sessionId,
      retailer: link.retailer,
      productUrl: link.productUrl,
      sessionPath: JSON.stringify(sessionPath),
    }
  });

  return taggedUrl;
}

Calculating Page-Level ROI

Once we have attribution data, we calculate ROI per page:

async function calculatePageROI(slug: string, days: number = 30) {
  const [attributionRevenue, productionCost] = await Promise.all([
    getAttributionRevenue(slug, days),
    getProductionCost(slug),
  ]);

  const pageviews = await getPageviews(slug, days);
  const organicTrafficValue = estimateOrganicValue(pageviews);

  return {
    slug,
    attributionRevenue,          // Actual affiliate revenue attributed
    organicTrafficValue,          // Estimated value of organic traffic (CPC equiv)
    productionCost,               // Time + AI API costs to produce
    roi: (attributionRevenue - productionCost) / productionCost,
    revenuePerPageview: attributionRevenue / pageviews,
    paybackPeriodDays: productionCost / (attributionRevenue / days),
  };
}

Estimating Organic Traffic Value

For pages with low affiliate conversion but high organic traffic, we estimate the value using CPC equivalents:

function estimateOrganicValue(pageviews: number): number {
  // Average CPC for comparison keywords is $1.20-3.50
  // We use $1.80 as our baseline
  const estimatedCPC = 1.80;
  const estimatedCTR = 0.035; // 3.5% avg organic CTR

  // Organic value = what we would have paid for this traffic via Google Ads
  return pageviews * estimatedCTR * estimatedCPC;
}

Our Content Scorecard

Every 30 days, we generate a scorecard ranking all pages by ROI:

Metric	Weight	Why
Attribution revenue (30 days)	40%	Direct revenue signal
Organic traffic value	25%	Long-term SEO value
Affiliate CTR	20%	Monetization efficiency
Avg time on page	10%	Quality signal
Return visitor rate	5%	Loyalty signal

Pages scoring below a threshold get flagged for:

Refresh (if traffic is high but conversion is low)
Consolidation (if similar higher-performing page exists)
Deletion (if traffic and revenue are both minimal)

What We Have Learned

Comparison pages outperform blog posts 3:1

Our comparison pages average $0.045 revenue per pageview. Blog posts average $0.015. The intent difference is that large.

Long-tail comparisons have better ROI than head terms

A comparison for two niche robot vacuums (10K searches/mo, low competition) generates better ROI than AirPods vs Sony (50K searches/mo, high competition). Lower production cost, faster ranking, similar purchase intent.

Affiliate CTR is more actionable than conversion rate

Conversion rate is controlled by the retailer. CTR is controlled by us. If CTR is low, we test: CTA placement, button copy, price display format. These changes move the needle in days, not months.

Time-to-revenue varies dramatically by category

Mattress comparisons take 60-90 days to generate revenue (long consideration cycle). Electronics comparisons generate revenue within 7-14 days. Plan production accordingly.

The Practical Upshot

If you are building a content business:

Instrument everything from day one. Retrofitting attribution tracking is painful.
Use position-based attribution, not last-touch. Last-touch penalizes your best top-of-funnel content.
Calculate ROI per page, not per category. Your best performers will surprise you.
Optimize CTR before conversion rate. You control the former, the retailer controls the latter.
Separate the comparison and blog playbooks. They have different economics and different timelines.

The comparison pages that drive revenue are not always the ones with the most traffic. Revenue-per-pageview is a far better optimization target than raw traffic.

Part 11 of our Building SmartReview series. Previous: Part 10: Building a Partnership Pitch

Building a Partnership Pitch That Converts: Lessons from 24 Brand Outreach Attempts

Daniel Rozin — Sun, 12 Apr 2026 20:39:34 +0000

We have sent 88 partnership outreach emails over the past two weeks. Here is what we have learned about what makes a pitch work.

At SmartReview, our brand partnership program offers three tiers: Enhanced Brand Profile ($500/mo), Sponsored Comparison ($1,000/mo), and Category Sponsorship ($2,000/mo).

The Core Problem with Most Partnership Pitches

Most partnership pitches fail for one of three reasons:

Too much about you — We have 500K monthly visitors is less compelling than Your brand gets 50K comparison searches per month and you are losing 62% of them to competitors
Vague value proposition — We will feature your brand means nothing
Wrong person, wrong time — Sending to press@ when you need marketing@ is a dead end

Our Pitch Framework

After testing multiple approaches, we settled on a 4-element framework:

1. The Data Hook (first sentence)

Lead with a specific number about THEIR brand.

Bad: SmartReview reaches 500K monthly comparison shoppers.
Good: AirPods appears in 50,000+ comparison searches every month and right now, you are not controlling that narrative.

2. The Insight (one paragraph)

Share one genuine insight about their competitive position:

Win rates in head-to-head comparisons
Which competitor is stealing their comparison traffic
Surprising search patterns
Sentiment gaps where user perception diverges from product reality

3. The Ask (one sentence)

Small, specific, low-commitment.

Bad: We would love to schedule a call to discuss our partnership program.
Good: Would a 10-minute call this week be useful? I can share the full competitive report for your brand at no cost.

4. The Urgency Signal

Comparison search is a zero-sum game.

We are finalizing our launch partner cohort -- first mover in each category gets preferred placement.

Touch Sequence: 4 Emails, Different Angles

Touch	Angle	Subject Line Pattern
Touch 1	Data insight	Brand comparison data -- thought you would find this interesting
Touch 2	Competitive intelligence	What we are seeing in Category comparison searches
Touch 3	Social proof + urgency	Competitor just claimed their comparison slot
Touch 4	Decision prompt	Yes/no on Brand comparison partnership?

Subject Lines That Work

Best performing patterns:

Brand name + comparison data -- highest open rate
Quick question about Product vs Competitor -- feels personal
Saw your Product comparison traffic -- implies specific data

Worst performing patterns:

Partnership opportunity with SmartReview -- screams vendor pitch
Following up on my previous email -- overused
Exciting news about our platform -- nobody cares

The Free Report Offer

Our highest-converting hook is offering a free competitive intelligence report:

Search volume for top 10 Brand vs X queries
Win rate in head-to-head comparisons
Top 3 competitive gaps
Trending comparison queries
Affiliate conversion rate for your category

Brands who receive the report convert to paid partners at 3x the rate of brands who do not.

What We Would Do Differently

Start with the report offer in Touch 1, not Touch 2
Skip the company overview paragraph
Name the specific competitor stealing comparison traffic
Include one real data point as a table, not just text
Keep Touch 4 under 80 words

The Formula

Tight target list (25 brands, not 250)
Deep personalization (real data about each brand)
Low-friction ask (free report vs sales call)
Systematic follow-up (4 touches, 3-4 days apart)
Clear urgency (category exclusivity, limited launch cohort)

The brand partnership program is open at aversusb.net/partnerships.

Part 10 of our Building SmartReview series. Previous: Part 9: Affiliate Links vs Display Ads

Why We Chose Affiliate Links Over Display Ads (and the Revenue Math Behind It)

Daniel Rozin — Sun, 12 Apr 2026 06:06:38 +0000

When we launched SmartReview, we had to pick a monetization model. Display ads were the obvious choice — easy to implement, predictable CPMs. We went with affiliate links instead.

Six months in, that decision is generating 4x more revenue per page than display ads would have. Here's the math and the reasoning.

The Display Ads Baseline

For a comparison/review site with our traffic profile, display ad networks typically offer:

Metric	Typical Value
CPM (programmatic)	$2-5
Fill rate	85-95%
Ads per page	3-5
Revenue per 1K pageviews	$6-20

With 500K monthly pageviews, that's roughly $3K-$10K/month from display ads. Not bad, but there's a ceiling — and display ads actively harm the user experience on comparison pages.

The Affiliate Model

Comparison pages have a unique advantage: visitors are in buying mode. When someone lands on "AirPods Pro vs Sony WF-1000XM5," they're typically ready to purchase within 24-48 hours.

Our affiliate metrics:

Metric	Our Performance
Click-through rate to retailer	8.2%
Conversion rate (post-click)	3.4%
Average order value	$180
Average commission rate	4.5%
Revenue per 1K pageviews	$25-45

With the same 500K pageviews: $12.5K-$22.5K/month. That's 2-4x the display ad revenue.

Why Comparison Pages Convert Better

The 8.2% CTR and 3.4% conversion rate are well above industry averages (typically 1-3% CTR, 1-2% conversion). Three factors drive this:

1. Intent Alignment

Our visitors have already decided what to buy — they're choosing which one. The affiliate link is the natural next step, not an interruption.

2. Trust Transfer

After reading a detailed, data-backed comparison, users trust the recommendation. When we say "Pick the Sony if noise cancellation is your priority" and link to the Sony product page, users follow through.

3. Price Transparency

We show current prices from multiple retailers. Users click through knowing exactly what they'll pay, which reduces bounce rate on the retailer's site.

The Technical Implementation

Our affiliate link system is more sophisticated than just dropping Amazon links:

interface AffiliateLink {
  retailer: string;          // amazon, bestbuy, walmart, etc.
  productUrl: string;        // direct product page URL
  affiliateTag: string;      // our affiliate ID
  currentPrice: number;      // live price (updated every 4 hours)
  inStock: boolean;          // availability check
  shippingEstimate: string;  // "Free 2-day" etc.
}

function buildAffiliateCTA(
  product: Product,
  links: AffiliateLink[]
): AffiliateCTAProps {
  // Sort by: in-stock first, then lowest price
  const sorted = links
    .filter(l => l.inStock)
    .sort((a, b) => a.currentPrice - b.currentPrice);

  return {
    primaryLink: sorted[0],           // Best price, in stock
    alternativeLinks: sorted.slice(1), // Other retailers
    priceRange: {
      low: sorted[0]?.currentPrice,
      high: sorted[sorted.length - 1]?.currentPrice,
    },
    lastUpdated: new Date(),
  };
}

Multi-Retailer Strategy

We don't just link to Amazon. Showing prices from multiple retailers:

Increases trust — users see we're not biased toward one store
Captures more clicks — some users prefer Best Buy or Walmart
Hedges risk — if one affiliate program changes terms, we're diversified
Improves conversion — users can pick their preferred retailer

function PriceComparison({ links }: { links: AffiliateLink[] }) {
  return (
    <div className="price-comparison">
      <h3>Where to buy</h3>
      {links.map(link => (
        <a
          key={link.retailer}
          href={link.productUrl}
          className="retailer-link"
          data-retailer={link.retailer}
          onClick={() => trackAffiliateClick(link)}
        >
          <span className="retailer-name">{link.retailer}</span>
          <span className="price">${link.currentPrice}</span>
          <span className="shipping">{link.shippingEstimate}</span>
          {link.currentPrice === lowestPrice && (
            <span className="badge">Best Price</span>
          )}
        </a>
      ))}
    </div>
  );
}

Link Placement Strategy

Where you put affiliate links matters as much as having them. Our highest-converting placements:

Placement	CTR	Notes
Verdict section CTA	12.1%	After the recommendation
Price comparison widget	9.8%	Shows all retailers
Inline "check price" links	6.3%	Within spec comparisons
Sticky bottom bar	5.1%	Always visible on mobile
Hero section buttons	3.2%	"View on Amazon" etc.

The verdict section CTA converts best because it appears right after we've made the case for one product over the other. The user has context and conviction — the link is the natural action.

Tracking and Attribution

We track every affiliate click with custom events:

function trackAffiliateClick(link: AffiliateLink) {
  // Internal analytics
  analytics.track("affiliate_click", {
    retailer: link.retailer,
    product: link.productUrl,
    price: link.currentPrice,
    placement: getCurrentPlacement(),
    comparisonSlug: getPageSlug(),
  });

  // Store for attribution
  localStorage.setItem("last_affiliate_click", JSON.stringify({
    timestamp: Date.now(),
    retailer: link.retailer,
    product: link.productUrl,
  }));
}

This lets us answer questions like:

Which comparison pages generate the most affiliate revenue?
Which product categories have the highest conversion rates?
Does showing 3 retailers vs 5 affect CTR?
What's the optimal number of affiliate CTAs per page?

The Brand Partnership Layer

Affiliate revenue is our baseline. On top of that, we're building a brand partnership program:

Tier	Price	What Brands Get
Enhanced Profile	$500/mo	Logo, brand story, verified specs on comparison pages
Sponsored Comparison	$1,000/mo	Featured placement, custom angles, lead capture
Category Sponsorship	$2,000/mo	Own all comparisons in a category

This doesn't replace affiliate links — it layers on top. A brand paying for an Enhanced Profile still generates affiliate clicks. The partnership fee is incremental revenue.

Display Ads: When They Make Sense

Display ads aren't always wrong. They work better when:

Traffic is informational, not transactional (blog posts, guides)
Products aren't easily linked (B2B comparisons, abstract topics)
Affiliate programs don't exist for your product category
You need minimum viable revenue while building affiliate relationships

We use display ads on our blog content where affiliate intent is low. But on comparison pages — never.

Key Takeaways

Match monetization to intent. Comparison pages = buying intent = affiliate links. Blog posts = informational intent = display ads.
Show multiple retailers. It builds trust and captures more clicks.
Place CTAs after conviction. The verdict section converts 3x better than the hero.
Track everything. You can't optimize what you don't measure.
Layer revenue streams. Affiliate + brand partnerships > either alone.

The bottom line: if your content helps people make purchase decisions, affiliate links will outperform display ads every time.

Part 9 of our "Building SmartReview" series. Previous: Part 8: Entity Resolution at Scale

Entity Resolution at Scale: Matching Products Across Amazon, Reddit, and RTINGS

Daniel Rozin — Fri, 10 Apr 2026 00:53:07 +0000

"AirPods Pro 2," "Apple AirPods Pro (2nd Generation)," "AirPods Pro USB-C" — same product, three different names.

Entity resolution — figuring out that different strings refer to the same real-world thing — is one of the hardest problems in product data engineering. At SmartReview, we match products across 50+ review sources, each with its own naming conventions, categorization, and data formats.

Here's how we solved it without spending six months building a custom ML model.

The Problem Space

Consider matching products across these sources:

Source	Product Name	Format
Amazon	Apple AirPods Pro (2nd Generation) - MagSafe Case (USB-C)	Full name + SKU details
Reddit	AirPods Pro 2	Colloquial shorthand
RTINGS	Apple AirPods Pro 2nd Gen	Abbreviated formal
YouTube	NEW AirPods Pro 2 USB-C Review	Title with marketing fluff
Best Buy	Apple - AirPods Pro 2 - White	Brand-prefixed with color

All five refer to the same product. A naive string match would treat them as five different products.

Our Three-Layer Approach

We use three complementary techniques, each catching matches the others miss.

Layer 1: Brand + Model Normalization

The first pass normalizes brand names and extracts model identifiers:

interface NormalizedProduct {
  brand: string;           // "apple"
  modelFamily: string;     // "airpods pro"
  generation: string;      // "2nd gen"
  variant: string;         // "usb-c"
  rawName: string;         // original string
}

function normalizeProductName(raw: string): NormalizedProduct {
  let name = raw.toLowerCase().trim();

  // Remove common noise
  name = name
    .replace(/\b(new|latest|best|review|vs\.?)\b/g, "")
    .replace(/[-–—]/g, " ")
    .replace(/\s+/g, " ")
    .trim();

  // Extract brand (lookup against known brand list)
  const brand = extractBrand(name);

  // Extract generation markers
  const genPatterns = [
    /(?:gen(?:eration)?\s*)(\d+)/i,
    /(\d+)(?:st|nd|rd|th)\s*gen/i,
    /\b(\d+)\b(?=\s|$)/,  // trailing number often = generation
  ];
  const generation = extractPattern(name, genPatterns);

  // Extract variant (color, connectivity, size)
  const variant = extractVariant(name);

  // What remains is the model family
  const modelFamily = extractModelFamily(name, brand, generation, variant);

  return { brand, modelFamily, generation, variant, rawName: raw };
}

This handles ~60% of matches — the straightforward cases where brand + model + generation aligns.

Layer 2: Fuzzy String Matching

For the remaining 40%, we use Levenshtein distance with a category-aware threshold:

function fuzzyMatch(
  a: NormalizedProduct,
  b: NormalizedProduct,
  threshold: number = 0.85
): boolean {
  // Brand must match exactly (after normalization)
  if (a.brand !== b.brand) return false;

  // Compare model family with fuzzy matching
  const similarity = stringSimilarity(
    a.modelFamily,
    b.modelFamily
  );

  if (similarity < threshold) return false;

  // If generations are both present, they must match
  if (a.generation && b.generation && a.generation !== b.generation) {
    return false;
  }

  return true;
}

The key insight: brand must match exactly, but model name can be fuzzy. This prevents false positives like matching "Sony WH-1000XM5" with "Sony WF-1000XM5" (over-ear vs in-ear — completely different products with similar names).

Layer 3: Cross-Reference Validation

For edge cases, we validate matches against external canonical sources:

async function crossReferenceValidate(
  candidates: NormalizedProduct[]
): Promise<ProductCluster[]> {
  const clusters: ProductCluster[] = [];

  for (const candidate of candidates) {
    // Search for the product on a canonical source
    const canonicalResults = await tavily.search(
      `${candidate.brand} ${candidate.modelFamily} specifications`,
      { searchDepth: "basic", maxResults: 3 }
    );

    // Extract canonical product identifier
    const canonicalId = extractCanonicalId(canonicalResults);

    // Group by canonical ID
    const existing = clusters.find(c => c.canonicalId === canonicalId);
    if (existing) {
      existing.members.push(candidate);
    } else {
      clusters.push({
        canonicalId,
        canonicalName: candidate.rawName,
        members: [candidate],
      });
    }
  }

  return clusters;
}

Handling the Hard Cases

Product Lines vs Individual Products

"Roomba" could mean the brand, the product line, or a specific model (Roomba j7+). We use context clues:

If a review discusses specific features ("self-emptying base"), it's likely a specific model
If it's a general comparison ("Roomba vs Roborock"), it's the product line
We maintain a hierarchy: Brand → Line → Model → Variant

Regional Name Differences

The same product sometimes has different names in different markets. The Samsung Galaxy S24 is called "Galaxy S24" everywhere, but some accessories have region-specific names. We maintain an alias table for known cases.

Discontinued vs Current Models

When someone searches "AirPods Pro vs Sony," do they mean the current or previous generation? We default to current unless the query specifies otherwise, but we keep both generations in our database with clear generation markers.

Performance at Scale

Our entity resolution pipeline processes ~5,000 product mentions daily across all review sources:

Metric	Value
Products in canonical database	12,000+
Daily new mentions processed	~5,000
Match accuracy (spot-checked)	94.2%
False positive rate	1.8%
Processing time (full pipeline)	~12 minutes
Most common false positive	Generation confusion (XM4 vs XM5)

The 1.8% false positive rate is acceptable because our trust score system (covered in Part 5) catches anomalies — if a "product" suddenly has wildly inconsistent ratings, it's likely a merge error.

Lessons Learned

Don't build ML first. Our three-layer heuristic approach handles 94%+ of cases. ML would marginally improve accuracy but massively increase complexity.
Brand matching must be exact. Fuzzy brand matching creates catastrophic false positives.
Generation numbers are treacherous. "AirPods 3" and "AirPods Pro 3" are different products. Always match model family before generation.
Maintain a manual override table. Some matches are just weird. "Galaxy Buds2 Pro" vs "Galaxy Buds 2 Pro" (note the space) — keep a list of known aliases.
Log everything. When a match seems wrong in production, you need the matching pipeline's decision trail to diagnose why.

What's Next

We're exploring embedding-based matching for the long tail — products where our heuristics fail because names are too dissimilar. Early experiments with product description embeddings show promise for matching across languages.

See entity resolution in action on aversusb.net — every comparison page unifies data from multiple sources under a single canonical product identity.

Part 8 of our "Building SmartReview" series. Previous: Part 7: People Also Ask Content Discovery

How We Use "People Also Ask" to Generate 40% of Our Comparison Content Ideas

Daniel Rozin — Thu, 09 Apr 2026 17:47:27 +0000

Google's "People Also Ask" (PAA) boxes are one of the most underused content discovery tools in SEO. For product comparison sites, they're a goldmine.

At SmartReview, PAA data drives roughly 40% of our new content ideas. Here's how we systematically extract, score, and turn PAA questions into high-performing comparison and FAQ content.

Why PAA Matters for Comparison Sites

When someone searches "AirPods Pro vs Sony WF-1000XM5," Google typically shows 4-8 PAA questions like:

"Are AirPods Pro better than Sony for phone calls?"
"Which has better noise cancellation, AirPods or Sony?"
"How long do AirPods Pro last compared to Sony?"
"Is Sony WF-1000XM5 worth the price?"

Each of these represents a real user question with search demand. And here's the key insight: answering these questions on your comparison page helps you:

Win the PAA box itself — Google pulls answers from pages that directly address the question
Rank for long-tail variations — each PAA question maps to dozens of similar queries
Increase time on page — comprehensive FAQ sections keep users engaged
Discover new comparison angles — PAA reveals what users actually care about

Our PAA Extraction Pipeline

We extract PAA data from every SERP we monitor using the DataForSEO API:

interface PAAItem {
  question: string;
  sourceUrl: string;
  sourceTitle: string;
  snippet: string;
  position: number;  // position in the PAA box (1-8)
}

async function extractPAA(keyword: string): Promise<PAAItem[]> {
  const response = await dataforseo.post(
    "/serp/google/organic/live/advanced",
    [{
      keyword,
      location_code: 2840,
      language_code: "en",
      device: "desktop",
    }]
  );

  const items = response.tasks[0].result[0].items;
  return items
    .filter((item: any) => item.type === "people_also_ask")
    .flatMap((paa: any) => paa.items.map((q: any, i: number) => ({
      question: q.title,
      sourceUrl: q.url,
      sourceTitle: q.source,
      snippet: q.snippet,
      position: i + 1,
    })));
}

Scoring PAA Questions

Not all PAA questions are worth targeting. We score them on three dimensions:

1. Comparison Relevance

Does the question involve comparing two products?

function isComparisonQuestion(question: string): boolean {
  const patterns = [
    /better than/i,
    /compared to/i,
    /vs\.?\s/i,
    /versus/i,
    /difference between/i,
    /which (is|should|has)/i,
    /or\s+\w+\s*\?/i,  // "X or Y?"
  ];
  return patterns.some(p => p.test(question));
}

2. Answerability

Can we answer this with structured data we already have?

function getAnswerability(question: string, comparison: ComparisonData): number {
  const attributes = comparison.attributes.map(a => a.name.toLowerCase());
  const questionLower = question.toLowerCase();

  // Check if question maps to a known attribute
  const matchedAttributes = attributes.filter(attr => 
    questionLower.includes(attr) || 
    synonymMap[attr]?.some(syn => questionLower.includes(syn))
  );

  return matchedAttributes.length > 0 ? 1.0 : 0.5;
}

3. Content Gap

Are we already answering this question on the page?

function isContentGap(question: string, existingFaqs: string[]): boolean {
  return !existingFaqs.some(faq => 
    stringSimilarity(question, faq) > 0.7
  );
}

The combined score determines priority:

const priority = 
  (isComparisonQuestion(q) ? 3 : 1) *
  getAnswerability(q, comparison) *
  (isContentGap(q, existingFaqs) ? 2 : 0.5);

Turning PAA Into Content

Once scored, PAA questions flow into two content streams:

Stream 1: FAQ Enrichment

High-scoring questions get added to existing comparison pages as FAQ items. We generate answers using our enrichment pipeline:

async function generateFaqAnswer(
  question: string,
  comparison: ComparisonData
): Promise<string> {
  // Pull fresh data relevant to the question
  const context = await tavily.search(
    `${question} ${comparison.entityA.name} ${comparison.entityB.name}`,
    { searchDepth: "advanced" }
  );

  // Generate a concise, factual answer
  const answer = await claude.generate({
    prompt: `Answer this product comparison question concisely (2-3 sentences).

    Question: ${question}
    Product A: ${JSON.stringify(comparison.entityA)}
    Product B: ${JSON.stringify(comparison.entityB)}
    Recent context: ${context.results.map(r => r.content).join("\n")}

    Rules:
    - Be specific with numbers and specs
    - Name a winner if one exists
    - Cite the key differentiating factor`,
  });

  return answer;
}

Stream 2: New Comparison Discovery

PAA questions sometimes reveal comparison pairs we haven't covered:

"Is Dyson V15 better than Shark Navigator?" → new comparison opportunity
"How does Purple compare to Tempur-Pedic?" → might already exist, but validates demand
"Which robot vacuum is best for pet hair?" → category roundup opportunity

We extract entity pairs from these questions and feed them back into our keyword discovery pipeline.

The FAQPage Schema Connection

Every FAQ answer we generate gets wrapped in FAQPage JSON-LD schema (covered in Part 4). This creates a direct feedback loop:

Extract PAA questions from SERPs
Generate data-backed answers
Add to comparison page with FAQPage schema
Google surfaces our answers in PAA boxes
More visibility → more data on what users ask

Results

After 3 months of PAA-driven content enrichment:

40% of new content ideas originated from PAA extraction
PAA box appearances increased 3x (from ~200 to ~600 keywords)
Organic CTR improved 18% on pages with PAA-optimized FAQ sections
Average FAQ section grew from 3 to 7 questions per comparison page
Long-tail keyword coverage expanded 45% without creating new pages

The most surprising finding: PAA questions often reveal user concerns that aren't obvious from keyword data alone. "Are AirPods safe for kids' ears?" would never show up in a keyword tool, but it's a real question that real buyers ask.

Try It

Check any comparison page on aversusb.net — the FAQ sections are largely PAA-driven. View source to see the FAQPage schema wrapping each answer.

Part 7 of our "Building SmartReview" series. Previous: Part 6: ISR and On-Demand Revalidation