Site QA · content

Public pages audited for content-quality issues

Audit public web pages for content quality issues and generate source-linked QA report rows.

Not a page-to-markdown dump (use Website Content Extractor). Not article boilerplate cleanup (use Article Content Extractor). Not a RAG readiness scoring pack. You supply the URLs.

from $10.00 / 1,000 Site page extracted ($0.01 per delivered site-page-extracted); $0.08 per Site QA issue detected; $5.00 per Site QA report generated; $7.00 per Site export generated. No Actor Start.

Open Site QA Content Report on Apify

Site QA Content Report, not a neighboring Actor

Use this page for this Actor’s job. Use Website Content Extractor for One-shot page-to-markdown; Use Article Content Extractor for News/blog HTML cleanup; Use Website RAG Readiness Audit for RAG coverage and chunking risk.

This ActorWebsite Content ExtractorArticle Content ExtractorWebsite RAG Readiness Audit
IntentContent-quality issues, report, and export on supplied pagesOne-shot page-to-markdownNews/blog HTML cleanupRAG coverage and chunking risk
Primary inputurlsurlsurlsurls / domain
What it readsUser-supplied public page HTMLPage HTMLArticle HTMLPublic pages
Primary outputIssue, report, and export eventsMarkdown/textHeadline/byline/bodyRAG snapshot/readiness reports
Not this jobNot a page-to-markdown dump (use Website Content Extractor). Not article boilerplate cleanup (use Article Content Extractor). Not a RAG readiness scoring pack. You supply the URLs.Not content-quality issue reports.Not site QA content reports.Not generic content-quality issue rows.

Store ID: taroyamada/site-qa-content-report-scraper. Respect source terms, robots.txt, and rate limits.

Use cases

How is Site QA Content Report different from Website Content Extractor and Article Content Extractor?

Site QA Content Report (taroyamada/site-qa-content-report-scraper): Audit public web pages for content quality issues and generate source-linked QA report rows. Not a page-to-markdown dump (use Website Content Extractor). Not article boilerplate cleanup (use Article Content Extractor). Not a RAG readiness scoring pack. You supply the URLs. Website Content Extractor is for One-shot page-to-markdown (input urls; Page HTML; Markdown/text). Not content-quality issue reports. Article Content Extractor is for News/blog HTML cleanup (input urls; Article HTML; Headline/byline/body). Not site QA content reports. Website RAG Readiness Audit is for RAG coverage and chunking risk (input urls / domain; Public pages; RAG snapshot/readiness reports). Not generic content-quality issue rows.

What input is required?

Live required fields: urls. Published exampleRunInput is shown below.

Field Type Default Notes
urls any[] ["https://example.com/?siteQaCanary=content-v2"] Public page URLs. Public URLs that you are allowed to audit. Required.
maxPages integer 10 Max pages. Maximum number of input pages to check. minimum=1 maximum=100
maxLinksPerPage integer 25 Max links per page. Maximum links to check per page for URL health workflows. minimum=1 maximum=250
emitPageRows boolean false Emit raw page rows. Emit optional raw page snapshot rows in addition to value-event issue/report rows.
generateReport boolean true Generate report row. Generate a site-level report row.
emitExport boolean false Generate export row. Generate an export row for handoff workflows.
emitUnchanged boolean false Emit unchanged rows. When false, repeated unchanged runs emit zero rows and zero charges.
dryRun boolean false Dry run. Emit local sample rows without charging.

Published Store example run input (omitted fields take schema defaults):

{
  "urls": [
    "https://example.com/?siteQaCanary=content-v2"
  ],
  "maxPages": 1,
  "maxLinksPerPage": 1,
  "dryRun": false
}

Run Site QA Content Report on Apify

How do dataset, webhook, and dry-run delivery work?

Dataset output is the billable surface when rows are written. See live PPE for which events bill. dryRun true validates or samples without the usual dataset/webhook side effects described on the Store schema. Unchanged runs that write zero default-dataset rows typically charge $0.00 on current PPE.

What does a result contain?

Published README Output Example / Sample Output JSON. Illustration: { "rowType": "site_qa_report", "billingEventName": "site-qa-report-generated", "sourceUrl": "https://example.com/?siteQaCanary=content-v2", "checkedUrlCount": 1, "issueCount": 2, "reportStatus": "action_needed" } Treat README samples as illustrations, not a live coverage guarantee. There is no published output JSON schema on the Store page.

How is Site QA Content Report priced?

Billing is pay per event. The live Store card is from $10.00 / 1,000 Site page extracted ($0.01 per delivered site-page-extracted); $0.08 per Site QA issue detected; $5.00 per Site QA report generated; $7.00 per Site export generated. No Actor Start. Current PPE:

Event Price Emitted when
site-page-extracted (Site page extracted) $0.01 Charged for each optional raw public page snapshot row.
site-qa-issue-detected (Site QA issue detected) $0.08 Charged for each source-linked page QA issue row.
site-qa-report-generated (Site QA report generated) $5.00 Charged for each site-level QA report row.
site-export-generated (Site export generated) $7.00 Charged for each generated QA export row.

from $10.00 / 1,000 Site page extracted ($0.01 per delivered site-page-extracted); $0.08 per Site QA issue detected; $5.00 per Site QA report generated; $7.00 per Site export generated. No Actor Start.

See Site QA Content Report pricing on Apify

Limits to keep in mind

Open Site QA Content Report on Apify

Related pages