Public Help Center & FAQ Answerability Snapshot Agent avatar

Public Help Center & FAQ Answerability Snapshot Agent

Pricing

from $5.00 / 1,000 useful help center answerability results

Go to Apify Store
Public Help Center & FAQ Answerability Snapshot Agent

Public Help Center & FAQ Answerability Snapshot Agent

Analyze public help centers, FAQ pages, docs pages, and support pages for self-service answerability evidence, risks, missing fields, and change status.

Pricing

from $5.00 / 1,000 useful help center answerability results

Rating

0.0

(0)

Developer

jack su

jack su

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

6 days ago

Last modified

Share

Turn a public help center, FAQ, docs, or support page into a compact answerability snapshot for AI agents, support teams, SEO reviewers, and customer-success workflows.

The Actor fetches only the supplied public page, parses visible HTML, and reports whether users or AI agents can self-serve answers from the page.

What It Detects

  • FAQ or question-style headings.
  • Topic/category navigation hints.
  • Help center type such as FAQ, docs, support, knowledge base, or help center.
  • Search input presence.
  • Contact or ticket escalation paths.
  • Last-updated, version, modified, or visible freshness hints.
  • Optional focus-topic matches.
  • Risk labels, missing fields, diagnostics, evidence URLs, and a stable helpCenterHash.

Safety Boundary

  • Public HTTP/HTTPS pages only.
  • No browser rendering, login, cookies, form submission, private APIs, or whole-site crawling.
  • Rejects credentials, path parameters, query strings, fragments, localhost, .local, private/non-global IPs, sensitive account paths, and token-like path segments.
  • HTML/text response size is capped at 3 MB, including gzip decompression.
  • Discovered links are sanitized and not fetched.

Pricing Intent

Pricing model: PAY_PER_EVENT

  • apify-actor-start: minimum run-start event.
  • useful-help-center-answerability-result: charged only for useful public help-center snapshots that are new or changed.

Error, unsupported URL, unchanged, focus-miss, low-evidence, and low-completeness records should not charge the useful event. Do not configure apify-default-dataset-item.

Example Input

{
"urls": ["https://help.apify.com/"],
"focusTopics": ["billing", "API"],
"requestTimeoutSecs": 20
}

Example Output Shape

{
"status": "ok",
"normalizedUrl": "https://example.com/help",
"title": "Acme Help Center",
"helpCenterType": "help-center",
"answerabilityScore": 0.9,
"faqQuestionHints": [{"question": "How do I reset my password?"}],
"topicCategoryHints": [{"text": "Billing and plans", "topic": "billing"}],
"searchInputDetected": true,
"contactEscalationLinks": [{"text": "Contact support", "url": "https://example.com/support/contact"}],
"freshnessHints": [{"text": "Last updated June 10, 2026"}],
"matchedFocusTopics": ["billing"],
"changeStatus": "new",
"billableEventName": "useful-help-center-answerability-result"
}