Intercom Help Center Public Crawler
Pricing
from $4.90 / 1,000 page auditeds
Intercom Help Center Public Crawler
Crawl public Intercom-style help centers and extract collections, sections, article URLs, titles, descriptions, breadcrumbs, locale, update signals, and article content into structured inventory rows.
Store Positioning
Store title: Intercom Help Center Public Crawler
Short description: Crawl public Intercom-style help centers and extract collections, sections, article URLs, titles, descriptions, breadcrumbs, locale, update signals, and article content into structured inventory rows.
SEO title: Intercom Help Center Public Crawler — technical SEO, web, and domain audit
SEO description: Crawl public Intercom-style help centers and extract collections, sections, article URLs, titles, descriptions, breadcrumbs, locale, update signals, and article content into structured inventory rows. Use it to find crawlability, indexability, security, metadata, and page-quality issues with evidence-backed rows and audit reports.
Categories: SEO_TOOLS
Keywords: intercom, help, center, public, crawler, structured data, public data, local seo, web/domain audit
Pay-Per-Event Pricing
This actor uses pay-per-event pricing. Event prices include Apify platform usage; users are not expected to pay a separate platform-usage pass-through charge for the configured pricing model.
- Tier: W1 — Web/domain audit
- Primary event:
page-auditedat $0.00490 base - Default max charge: $10.00
- Store discounts: FREE/BRONZE base, SILVER discounted, GOLD deepest approved discount
Event set:
actor-start: base $0.00500, GOLD $0.00400. Intercom Help Center Public Crawler: charged when actor start is completed. The price includes Apify platform usage; no separate usage pass-through is intended.page-audited: base $0.00490, GOLD $0.00392. Intercom Help Center Public Crawler: charged when page audited is completed. The price includes Apify platform usage; no separate usage pass-through is intended.record-extracted: base $0.00372, GOLD $0.00298. Intercom Help Center Public Crawler: charged when record extracted is completed. The price includes Apify platform usage; no separate usage pass-through is intended.finding-emitted: base $0.00372, GOLD $0.00298. Intercom Help Center Public Crawler: charged when finding emitted is completed. The price includes Apify platform usage; no separate usage pass-through is intended.audit-report-generated: base $0.05000, GOLD $0.04000. Intercom Help Center Public Crawler: charged when audit report generated is completed. The price includes Apify platform usage; no separate usage pass-through is intended.
The actor accepts actor-start before work, accepts the primary event before each dataset row, and accepts the configured report event before writing report files. If maxChargeUsd or the live PPE limit blocks a charge, the corresponding row or report is not written.
Public Task Concepts
- Audit Intercom Help Center Public Crawler controls on a capped public sample
- Find high-priority Intercom Help Center Public Crawler issues before release
- Validate Intercom Help Center Public Crawler evidence from supplied pages
- Prioritize Intercom Help Center Public Crawler fixes with severity and proof
- Export Intercom Help Center Public Crawler QA rows for client review
Crawl public Intercom-style help centers and extract collections, sections, article URLs, titles, descriptions, breadcrumbs, locale, update signals, and article content into structured inventory rows.
What it does
- Accept public Intercom help center base URLs, collection URLs, article URLs, or sitemap URLs.
- Crawl bounded public help center pages.
- Extract collection names, collection URLs, article URLs, titles, subtitles/descriptions, article body text, breadcrumbs, locale, author/update signals where visible, and related article links.
- Preserve hierarchy and source evidence.
- Generate collection map and article inventory for migration, SEO, and support QA.
What it does not do
- No Intercom admin API access, Messenger conversations, user/customer data, private help center crawling, access-control bypass, official certification, or heavy mirroring.
Input fields
Primary inputs from the locked actor spec: startUrls, helpCenterBaseUrl, sitemapUrls, allowedDomains, localeHints, maxPages, maxDepth, includeArticleBody, includeCollections, includeRelatedArticles, includeAuthorSignals, requestDelayMs, timeoutMs. maxChargeUsd keeps runs capped during production use.
Output fields
Dataset rows include: sourceUrl, pageType, collectionName, collectionUrl, sectionName, articleTitle, articleUrl, articleDescription, breadcrumbs, locale, authorName, updatedAt, articleBodyText, relatedArticleUrls, statusCode, warning.
Starter example
Use examples/input.tiny.json as a small starter input. Keep the first run capped and review the dataset before increasing limits.
Public task examples
- Run Intercom Help Center Public Crawler on supplied sample data: Run Intercom Help Center Public Crawler on supplied sample data using a small bounded input.
- Generate a Intercom Help Center Public Crawler QA report: Generate a Intercom Help Center Public Crawler QA report using a small bounded input.
- Find invalid rows with Intercom Help Center Public Crawler: Find invalid rows with Intercom Help Center Public Crawler using a small bounded input.
- Create a capped local endpoint readiness check for Intercom Help Center Public Crawler: Create a capped local endpoint readiness check for Intercom Help Center Public Crawler using a small bounded input.
- Prepare Intercom Help Center Public Crawler output for downstream automation: Prepare Intercom Help Center Public Crawler output for downstream automation using a small bounded input.
Public source provenance
The starter input fetches one public Intercom-hosted Fieldwork article directly from https://intercom.help/fieldwork/en/articles/927524-getting-started-welcome-to-fieldwork, constrained to intercom.help and one page.
Reports
intercom-help-center-public-crawl-report.mdintercom-article-inventory.csvintercom-collection-map.jsonintercom-locale-summary.jsonintercom-crawl-errors.json
Limitations and safe use
Start with supplied-input runs, then enable live endpoints only with tight caps, domain allowlists, and no secrets in public examples.