Print Stylesheet Checker — is your page print-friendly?

Check whether a page has print-specific CSS: <link media="print"> stylesheets, @media print blocks, and inline print rules — plus hints about missing page-break/@page rules and print-hostile backgrounds. Single URL or bulk. $0.0005 per page. Failed fetches are recorded free.

What you get

• hasPrintStyles and printStylesheetCount.
• printStyleSources breakdown: linkMediaPrint, styleMediaPrint, atMediaPrintBlocks, inlineStyleBlocks.
• hints — print-readiness advice (page-break rules, background printing, etc.).
• Fail-soft: an unreachable URL returns {ok:false, error} and is never charged.

Input

{ "url": "https://en.wikipedia.org/wiki/HTTP", "urls": ["https://example.com"], "maxUrls": 25 }

Output (real run, 2026-08-07)

{
  "ok": true, "url": "https://en.wikipedia.org/wiki/HTTP", "status": 200,
  "hasPrintStyles": true, "printStylesheetCount": 5,
  "printStyleSources": { "linkMediaPrint": 0, "styleMediaPrint": 0, "atMediaPrintBlocks": 5, "inlineStyleBlocks": 12 },
  "hints": ["Print styles present but no page-break / @page rules — long content may break awkwardly across pages.", "…"]
}

Pricing — $0.0005 per page

Priced at the floor. No directly comparable print-stylesheet checker was found on the Apify Store on 2026-08-07, so there is no competitor price to quote.

Limits (honest ones)

• Detects print styles declared in the served HTML (media="print", @media print, inline <style> blocks). Print rules that live only in externally-linked CSS files are counted by their <link media="print"> reference, not by fetching the file.
• hints are heuristics for common print problems, not a full print-render preview.
• maxUrls capped per run.

FAQ

• Why does print-friendliness matter? Users and tools still print/save-to-PDF pages; without print CSS, content breaks and wastes ink.
• What does it detect? <link media="print">, @media print blocks, and inline print styles, with a source breakdown.
• Does it render a print preview? No — it analyzes the CSS declarations and flags common issues.
• What about a dead URL? You get an {ok:false, error} record, uncharged.

Use from code or AI agents

curl -X POST "https://api.apify.com/v2/acts/EliAI~webpage-print-css-checker/runs?token=YOUR_APIFY_TOKEN" \
  -H 'content-type: application/json' -d '{"url":"https://en.wikipedia.org/wiki/HTTP"}'

Callable as an agent tool through the Apify MCP server (mcp.apify.com).