🌐 Responsive Visual QA Matrix

Runs a headless-Chromium responsive QA pass on each URL across a desktop/tablet/mobile matrix and returns ONE verdict per URL: per-viewport layout metrics, a horizontal-overflow flag per viewport, missing-resource evidence, and a cross-viewport perceptual diff. Billed once per completed matrix — never per screenshot.

Output is one responsive_matrix row per result; billing is pay-per-event, the value event being one responsive visual qa matrix verdict (a $0.02 start fee per run, then $0.05 per responsive visual qa matrix verdict).

No login, no API key and no CAPTCHA solving are involved: the source is read logged-out with an identified contact User-Agent.

📊 Sample Output

Real rows from run QiyjlkUTN2f0vwIua on build 0.1.4 (2026-09-17), the same input as the Quick start below — every value is as the source published it (emails masked, long text shortened):

target_url	final_url	browser	browser_version	capture_timestamp	input
https://example.com/	https://example.com/	chromium	153.0.8010.12	2026-09-17T18:26:10.703258+00:00	https://example.com/

The run finished with the status message: 1 URL(s): 1 completed matrix(es) charged, 0 unbilled (blocked/unreachable/unparseable) | responsive_page_check charged=1

✅ What you get

Each row is flat JSON with these fields (from the dataset schema and the sample run; a field the source does not publish for a given row is null):

• target_url (string/null) — e.g. https://example.com/
• final_url (string/null) — e.g. https://example.com/
• http_status (integer/string/null) — e.g. 200
• matrix_complete (boolean/null) — e.g. True
• desktop_metrics (string/null) — e.g. {"scrollWidth":1280,"clientWidth":1280,"scrollHeight":800,"innerWidth":1280,"inn
• tablet_metrics (string/null) — e.g. {"scrollWidth":768,"clientWidth":768,"scrollHeight":1024,"innerWidth":768,"inner
• mobile_metrics (string/null) — e.g. {"scrollWidth":390,"clientWidth":390,"scrollHeight":844,"innerWidth":390,"innerH
• horizontal_overflow_viewports (string/null) — null in every sample row
• missing_resources (string/null) — null in every sample row
• missing_resource_count (integer/string/null) — e.g. 0
• perceptual_diff_desktop_mobile (string/null) — e.g. 0.0245
• perceptual_diff_desktop_tablet (string/null) — e.g. 0.0116
• browser (string/null) — e.g. chromium
• browser_version (string/null) — e.g. 153.0.8010.12
• image_keys (string/null) — e.g. {"desktop":"qa-0-desktop-example.com","tablet":"qa-0-tablet-example.com","mobile
• capture_timestamp (string/null) — e.g. 2026-09-17T18:26:10.703258+00:00
• render_warnings (string/null) — null in every sample row
• faults (string/null) — null in every sample row
• record_type (string) — e.g. responsive_matrix
• source (string/null) — e.g. buyer-submitted page URLs
• outcome (string/null) — e.g. answer
• input (string/null) — e.g. https://example.com/
• outcome_reason (string/null) — null in every sample row
• observed_at (string/null) — null in every sample row
• terminal (string/null) — null in every sample row

Output & billing

One row per URL. A completed matrix (all three viewports captured) carries outcome: answer and bills once — never once per screenshot. A URL blocked (robots / SSRF / 403 / 429 / 5xx) or unreachable is delivered as an unbilled status row, never a broken-site verdict. Push-then-charge: every row is delivered before its charge, so a billing hiccup can only ever undercharge.

⚙️ Sample inputs

1. Quick start — the Store example (this is what the sample above came from)

{
  "urls": [
    "https://example.com/"
  ],
  "maxUrls": 10
}

The sample run charged exactly: 2 × $0.02 apify-actor-start + 1 × $0.05 responsive_page_check = $0.09 on the Free tier — every delivered row was billed.

2. A smaller, narrowed run

{
  "urls": [
    "https://example.com/"
  ],
  "maxUrls": 10,
  "userAgent": "Mozilla/5.0 (compatible; NexGenWatchBot/1.0; +https://apify.com/nexgenwatch)"
}

A bounded run for checking the field shape before scheduling. userAgent narrows what the source is asked for.

3. A full-size run

{
  "urls": [
    "https://example.com/"
  ],
  "maxUrls": 10
}

The same input run on a schedule; each run is billed only for what it delivers.

🧾 JSON sample record

One real record from run QiyjlkUTN2f0vwIua, exactly as it lands in the dataset (emails masked, long text shortened):

{
  "target_url": "https://example.com/",
  "final_url": "https://example.com/",
  "http_status": 200,
  "matrix_complete": true,
  "desktop_metrics": "{\"scrollWidth\":1280,\"clientWidth\":1280,\"scrollHeight\":800,\"innerWidth\":1280,\"innerHeight\":800,\"docReady\":\"complete\",\"horizontal_overflow\":false}",
  "tablet_metrics": "{\"scrollWidth\":768,\"clientWidth\":768,\"scrollHeight\":1024,\"innerWidth\":768,\"innerHeight\":1024,\"docReady\":\"complete\",\"horizontal_overflow\":false}",
  "mobile_metrics": "{\"scrollWidth\":390,\"clientWidth\":390,\"scrollHeight\":844,\"innerWidth\":390,\"innerHeight\":844,\"docReady\":\"complete\",\"horizontal_overflow\":false}",
  "horizontal_overflow_viewports": null,
  "missing_resources": null,
  "missing_resource_count": 0,
  "perceptual_diff_desktop_mobile": "0.0245",
  "perceptual_diff_desktop_tablet": "0.0116",
  "browser": "chromium",
  "browser_version": "153.0.8010.12",
  "image_keys": "{\"desktop\":\"qa-0-desktop-example.com\",\"tablet\":\"qa-0-tablet-example.com\",\"mobile\":\"qa-0-mobile-example.com\"}",
  "capture_timestamp": "2026-09-17T18:26:10.703258+00:00",
  "render_warnings": null,
  "faults": null,
  "record_type": "responsive_matrix",
  "source": "buyer-submitted page URLs",
  "outcome": "answer",
  "input": "https://example.com/",
  "outcome_reason": null
}

🔧 How it works

Transport. Plain HTTPS from the Apify platform, no proxy. A headless browser renders the page. robots.txt is read first and a disallowed path is never fetched. Every request carries an identified contact User-Agent.

Terminal states. A run ends NORMAL, CAPPED (your cap was reached), PARTIAL (something was withheld and the message says what), GENUINE_EMPTY (the source was read and truly had nothing in scope) or BLOCKED (the source refused or changed shape — the run FAILS loud and bills nothing). A zero-row run is never reported as a silent success.

Charging. Each responsive visual qa matrix verdict is charged at the moment it is pushed (responsive_page_check); a row that fails to charge is not delivered, so the dataset count always equals the charged count.

What you submit

urls — page urls. Page URLs to QA across a viewport matrix. Per URL ONE record covering three bounded captures (desktop 1280x800, tablet 768x1024, mobile 390x844): per-viewport layout metrics, a horizontal-overflow flag per viewport, missing-resource evidence, and a cross-viewport perceptual diff. Billed once per completed matrix (never per screenshot). A URL blocked (robots/SSRF/403/429/5xx) or unreachable is an unbilled status, never a broken-site verdict.

The runtime source gate (per submitted target)

You choose the targets, so the source contract is enforced at run time — for every submitted URL — per origin, before any page is read:

• robots.txt fetched once per origin and honored; no robots / 404 = permitted, a disallowed path or an unavailable/forbidden robots file = BLOCKED.
• SSRF guard — every host is resolved and must be public; private, loopback, link-local, reserved and cloud-metadata addresses are refused before a socket opens.
• HTTP — 403 / 429 / 5xx = BLOCKED; DNS / timeout / connection faults = UNREACHABLE.

A BLOCKED or UNREACHABLE target is delivered as an unbilled status row — never a broken-site verdict, and never charged.

Why this and not the obvious alternative

one responsive layout verdict per URL across a desktop/tablet/mobile matrix — overflow, missing resources, and a cross-viewport perceptual diff in a single billed record — not fleet-1's interactive browser MCP and not a per-screenshot capture API.

What is not done. No login, no cookie or CAPTCHA bypass, no private or personal-account data.

💰 Pricing example

Event	Free	Bronze	Silver	Gold
Actor Start (apify-actor-start)	$0.02	$0.02	$0.02	$0.02
Responsive Visual QA Matrix verdict (responsive_page_check)	$0.05	$0.04	$0.04	$0.03

Worked at the live Free-tier price:

• 1 responsive visual qa matrix verdicts: $0.02 start + 1 × $0.05 = $0.07
• 25 responsive visual qa matrix verdicts: $0.02 start + 25 × $0.05 = $1.27
• 100 responsive visual qa matrix verdicts: $0.02 start + 100 × $0.05 = $5.02

A run that delivers zero rows charges the $0.02 start fee only. A BLOCKED run (source refused) fails loud and charges no value event. The start fee is charged once per GB of run memory; the default run memory is 2048 MB.

Yield on the sample run: 1 URL(s): 1 completed matrix(es) charged, 0 unbilled (blocked/unreachable/unparseable) | responsive_page_check charged=1.

⚖️ Legal & ToS

This actor reads public data only. It collects only what the source publishes to any visitor, keeps to the source's robots rules (checked on every run), identifies itself with a contact User-Agent, and does not access accounts, private data or anything behind authentication. Use the output in line with the source's terms and your local law; the intended use is B2B research and monitoring.

❓ FAQ

Q: Do I need an API key or a login?
A: No. the input schema has no key field and the actor carries no secrets.

Q: Why did my run return 0 rows?
A: Read the run's status message. GENUINE_EMPTY means the source was read and had nothing in scope for your input; BLOCKED means the source refused and the run failed without billing a value event — retry later or narrow the input. A zero-row run bills the start fee only.

Q: How fresh is the data?
A: Every run reads the source live at run time; nothing is cached between runs. Put it on a schedule for a continuous feed.

Q: What formats can I export?
A: The dataset downloads as JSON, CSV, Excel, XML or RSS from the run's Dataset tab or the Apify API, and any run can push to a webhook or integration.

Q: How is this different from the other web QA and enrichment tools actors?
A: Same output shape and billing model; this one covers Responsive Visual QA Matrix. The siblings under Related Actors cover the other sources or slices — run several on one schedule for a combined feed.

Q: Are there rate limits?
A: The actor paces itself against the source and honours its robots rules; there is no per-buyer limit beyond your Apify plan's concurrency.

🆘 Troubleshooting

• Run FAILED with BLOCKED → the source refused the request or changed its page shape → nothing was billed beyond the start fee; retry after a while, and if it persists open an Issue with the run id.
• Fewer rows than expected → the source had fewer items in scope → widen the input.
• Input validation error on start → a field is outside the schema's allowed values → start from the Quick start block and change one field at a time.
• Run TIMED-OUT → a very wide request on a slow day → raise the run timeout in Run options or narrow the input; what was delivered before the timeout is still in the dataset.

🔗 Related Actors

• Internal Link Architecture Verifier — Runs a bounded same-origin crawl unioned with your sitemap, builds the internal link graph, and returns one evidenced verdict per page: orphan-from-s…
• Marketing Stack Enricher — Give it a list of company domains; it returns one CRM-ready record per domain describing
• PDF Text Intake Auditor — Judges whether a PDF is ingestible before you spend on extraction: text-layer presence, page count, encryption, scan likelihood, per-page text densit…
• 🧠 Review Sentiment Analyzer — Themes, Trends & Complaints — Turn any review set into themes, complaints, sentiment % and trends
• RSS Feed Contract Monitor — Checks a feed's health and contract: RSS/Atom/RDF shape validation, item canonicalization, a freshness score, duplicate GUID/link detection, ETag/Las…
• Sitemap Indexability Auditor — Audit whether the URLs in your sitemaps (or a plain URL list) are actually indexable — sitemaps are expanded (bounded nested depth + a hard URL cap)…
• 🏢 About NexGenData — NexGen Watch is NexGenData's fleet of 256 public monitoring and lookup actors built on official sources, pay-per-result. Browse the catalog at apify.com/nexgenwatch.

⭐ Found this useful?

If this actor saved you a manual check, a quick review on the Apify Store helps other teams find it. Feature request or a source that changed? Open it from the Issues tab — every one is read.