RTINGS Scraper

Scrape RTINGS.com — the lab-tested electronics review site that buys its own units, tests them under identical conditions, and publishes detailed score breakdowns for TVs, headphones, monitors, soundbars, keyboards, mice, vacuums, laptops, mattresses, printers, projectors, and more.

The actor returns clean JSON records with the overall score, per-usage scores (e.g. Mixed Usage, Gaming, Home Theater), featured spec test results (resolution, refresh rate, panel type, etc.), editor pros / cons / mixed-notes summaries, the verdict text, product imagery, and size/colour variants — all extracted from the page's embedded structured JSON, so the output schema is stable and field-complete.

What this scraper does

For each product review on RTINGS, the actor pulls:

• Identity — product name, brand, RTINGS product ID, review ID, model slug, category
• Overall score — RTINGS' headline 0-10 rating
• Per-usage suitability — Mixed Usage, Home Theater, Bright Room, Sports, Gaming (TVs); Neutral Sound, Commute/Travel, Sports/Fitness, Office, Wireless Gaming (headphones); Mixed Usage, Office, Gaming, Media Creation, HDR Gaming (monitors) — each with the suitable flag and editorial description
• Featured test results — the top 5-8 technical specs RTINGS highlights per product (e.g. Resolution: 4k @ 10/10, Native Refresh Rate: 144Hz @ 9.5/10, Sub-Type: WOLED)
• Summaries — pros, cons, and mixed-priority bullet points written by the editorial team
• Verdict text — the multi-paragraph introduction explaining what the product is good for
• Recommended / not recommended for — derived from the per-usage suitable flag
• Imagery — main product image URL (rehosted on i.rtings.com CDN)
• Variants — size variants (e.g. 55", 65", 77", 83", 97" for TVs), SKU IDs
• Provenance — review publish date, methodology version (test bench), authors, community comment count, scrape timestamp

Modes

Mode	What it does	Typical input
search	Match a free-text query against product slugs in RTINGS' sitemap, then fetch each	searchQuery=lg c4, category=tv
byCategory	Pull the curated picks from /{category} then enrich with sitemap-listed reviews	category=headphones, maxItems=20
byUrls	Fetch specific review URLs you paste in	reviewUrls=[ "https://www.rtings.com/tv/reviews/lg/g4-oled" ]
byBrand	Pull every reviewed model for a brand in a category	category=tv, brands=["lg","sony"]

Filters

• category — 25-option dropdown (TV, Headphones, Monitor, Soundbar, Keyboard, Mouse, Vacuum, Laptop, Mattress, Printer, Projector, Blender, Lawn Mower, Snowblower, Graphics Card, Speaker, Router, SSD, Webcam, Phone, Tablet, Air Purifier, Robot Vacuum, Gaming Headset, Earbuds)
• minScore / maxScore — drop products outside this 0-10 range
• suitableUsages — keep products marked suitable for any of these usages (case-insensitive substring)
• containsKeyword — substring search across name, brand, verdict, tagline
• yearMin / yearMax — drop reviews published outside this year range
• sortBy — score-desc / score-asc / newest / oldest / alphabetical
• includeVerdict — turn the multi-paragraph verdict on/off to keep records compact
• includeSummaries — turn pros / cons / mixed notes on/off

Example input

{
  "mode": "byCategory",
  "category": "tv",
  "sortBy": "score-desc",
  "maxItems": 15
}

{
  "mode": "search",
  "category": "headphones",
  "searchQuery": "sony wh-1000xm5",
  "maxItems": 5
}

{
  "mode": "byUrls",
  "reviewUrls": [
    "https://www.rtings.com/tv/reviews/lg/g4-oled",
    "https://www.rtings.com/monitor/reviews/lg/27gp850-b-27gp83b-b"
  ]
}

{
  "mode": "byBrand",
  "category": "tv",
  "brands": ["lg", "samsung"],
  "minScore": 8,
  "sortBy": "score-desc",
  "maxItems": 20
}

Example output (excerpt)

{
  "productId": "84591",
  "reviewId": "192473",
  "name": "LG G4 OLED",
  "brand": "LG",
  "category": "tv",
  "brandSlug": "lg",
  "modelSlug": "g4-oled",
  "overallScore": 8.6,
  "reviewedVariation": "65\"",
  "publishedAt": "2024-04-15 09:30:00 -0400",
  "publishedYear": 2024,
  "reviewUrl": "https://www.rtings.com/tv/reviews/lg/g4-oled",
  "productUrl": "https://www.rtings.com/tv/reviews/lg/g4-oled",
  "mainImageUrl": "https://i.rtings.com/assets/products/.../lg-g4-oled/design-medium.jpg",
  "skuIds": ["10492", "10493", "10494", "10495", "10496"],
  "variantCount": 5,
  "authors": ["Jacob Falato Rodrigues", "Ben Trudeau"],
  "testBenchName": "2.2",
  "testBenchId": "227",
  "verdict": "The LG G4 OLED is one of the best TVs we've tested...",
  "recommendedFor": ["Mixed Usage", "Home Theater", "Gaming"],
  "usageRatings": [
    {"usage": "Mixed Usage", "suitable": true, "description": "Excellent for mixed usage..."},
    {"usage": "Gaming", "suitable": true, "description": "The G4 is exceptional for gaming..."}
  ],
  "featuredTests": [
    {"name": "Resolution", "value": "4k", "score": 10.0},
    {"name": "Native Refresh Rate", "value": "144Hz", "score": 9.5},
    {"name": "Panel Type", "value": "OLED", "score": 10.0}
  ],
  "testScoresFlat": {
    "Resolution": "4k",
    "Native Refresh Rate": "144Hz",
    "Panel Type": "OLED"
  },
  "pros": [
    "Near-infinite contrast ratio for perfect blacks with no blooming.",
    "Native 144Hz support with HDMI 2.1 on all four ports."
  ],
  "cons": [
    "Reflections can be intense in very bright rooms."
  ],
  "commentCount": 1247,
  "recordType": "review",
  "scrapedAt": "2026-05-21T10:30:00+00:00"
}

FAQ

How fresh is the data?

RTINGS keeps published_at and first_published_at on every review and re-tests products periodically. The actor reports both fields and the methodology version (testBenchName, e.g. 2.2).

Do I need cookies or an API key?

No. Everything the actor extracts is publicly visible on rtings.com — the scraper simply parses the structured Vue component data already embedded in each page.

Why are some score values missing from usageRatings?

RTINGS hides the per-usage numeric scores behind their Insider membership paywall on some pages. The suitable boolean and the editorial description are still extracted (they're public), and the headline overallScore is always populated.

What's the difference between byCategory and byBrand?

byCategory starts from the category landing page (e.g. /tv) and pulls the editor-curated "best of" picks plus all reviews listed in the sitemap. byBrand enumerates every model RTINGS has reviewed for a specific brand × category (e.g. all LG TVs).

Why doesn't search work like Google?

RTINGS' live search UI is JavaScript-rendered with no public API. To keep the actor cookie-free and fast, the scraper instead loads the full sitemap (~5,600 review URLs) and matches your query tokens against brand + model slugs. So lg c4 matches /tv/reviews/lg/c4-oled reliably.

Which categories are supported?

The 25-option category dropdown covers everything RTINGS reviews regularly — TVs, headphones, monitors, soundbars, keyboards, mice, vacuums, laptops, mattresses, printers, projectors, blenders, lawn mowers, snowblowers, graphics cards, speakers, routers, SSDs, webcams, phones, tablets, air purifiers, robot vacuums, gaming headsets, and earbuds. New categories RTINGS adds in the future can be reached via byUrls.

How does pagination work?

Each request fetches one review page. Set maxItems to control the hard cap. The actor automatically de-duplicates and sorts before emitting.

Are all output fields always present?

No — the scraper omits empty fields so your records stay lean. Always-present fields: name, brand, reviewUrl, category, productId, recordType, scrapedAt. Other fields depend on what RTINGS publishes for each product.

Data Source

This actor scrapes publicly accessible review pages on www.rtings.com. RTINGS publishes hands-on lab test results purchased independently — no manufacturer-sent units, no sponsored placements. The scraper reads the same structured Vue component data the website itself uses to render each page.