Help Center Sitemap Extractor
Pricing
from $4.90 / 1,000 sitemap file checkeds
Help Center Sitemap Extractor
Extract public help center sitemap URLs, article URLs, categories, locales, last-modified signals, crawl depth, and indexability clues into a clean help-center inventory.
Pricing
from $4.90 / 1,000 sitemap file checkeds
Rating
0.0
(0)
Developer
junipr
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
2 days ago
Last modified
Categories
Share
Store Positioning
Store title: Help Center Sitemap Extractor
Short description: Extract public help center sitemap URLs, article URLs, categories, locales, last-modified signals, crawl depth, and indexability clues into a clean help-center inventory.
SEO title: Help Center Sitemap Extractor — technical SEO, web, and domain audit
SEO description: Extract public help center sitemap URLs, article URLs, categories, locales, last-modified signals, crawl depth, and indexability clues into a clean help-center inventory. Use it to find crawlability, indexability, security, metadata, and page-quality issues with evidence-backed rows and audit reports.
Categories: SEO_TOOLS, DEVELOPER_TOOLS
Keywords: help, center, sitemap, extractor, 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:
sitemap-file-checkedat $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. Help Center Sitemap Extractor: charged when actor start is completed. The price includes Apify platform usage; no separate usage pass-through is intended.sitemap-file-checked: base $0.00490, GOLD $0.00392. Help Center Sitemap Extractor: charged when sitemap file checked is completed. The price includes Apify platform usage; no separate usage pass-through is intended.record-extracted: base $0.00372, GOLD $0.00298. Help Center Sitemap Extractor: 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. Help Center Sitemap Extractor: 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. Help Center Sitemap Extractor: 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 Help Center Sitemap controls on a capped public sample
- Find high-priority Help Center Sitemap issues before release
- Validate Help Center Sitemap evidence from supplied pages
- Prioritize Help Center Sitemap fixes with severity and proof
- Export Help Center Sitemap QA rows for client review
Extract public help center sitemap URLs, article URLs, categories, locales, last-modified signals, crawl depth, and indexability clues into a clean help-center inventory.
What it does
- Accept help center base URLs, sitemap URLs, robots.txt URLs, or raw sitemap XML.
- Discover sitemap indexes, article sitemaps, category pages, section pages, locale paths, and support article URLs.
- Extract URL type, title where available, locale, lastmod, changefreq, priority, depth, status code, canonical hints, and source sitemap.
- Deduplicate URLs and classify article/category/section/search/system URLs.
- Generate a support content inventory and sitemap coverage report.
What it does not do
- No private support portals, authenticated crawling, full content scraping by default, SEO ranking promises, sitemap submission, or heavy site mirroring.
Input fields
Primary inputs from the locked actor spec: startUrls, sitemapUrls, robotsUrls, rawSitemapXml, allowedDomains, includeRobotsDiscovery, classifyUrlTypes, fetchPageTitles, includeStatusChecks, localeHints, maxUrls, timeoutMs. maxChargeUsd keeps runs capped during production use.
Output fields
Dataset rows include: sourceSitemapUrl, url, urlType, title, locale, categoryHint, sectionHint, lastModified, changeFrequency, priority, statusCode, canonicalUrl, depth, isDuplicate, 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 Help Center Sitemap Extractor on supplied sample data: Run Help Center Sitemap Extractor on supplied sample data using a small bounded input.
- Generate a Help Center Sitemap Extractor QA report: Generate a Help Center Sitemap Extractor QA report using a small bounded input.
- Find invalid rows with Help Center Sitemap Extractor: Find invalid rows with Help Center Sitemap Extractor using a small bounded input.
- Create a capped local endpoint readiness check for Help Center Sitemap Extractor: Create a capped local endpoint readiness check for Help Center Sitemap Extractor using a small bounded input.
- Prepare Help Center Sitemap Extractor output for downstream automation: Prepare Help Center Sitemap Extractor output for downstream automation using a small bounded input.
Public source provenance
The starter input extracts a five-URL sample from Stripe's public Support sitemap at https://support.stripe.com/sitemap.xml. The source is fetched during each run, capped before enrichment, and restricted to the official support.stripe.com host.
Reports
help-center-sitemap-inventory.mdhelp-center-urls.jsonhelp-center-url-type-summary.csvlocale-coverage-report.jsonsitemap-discovery-log.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.