Heading Structure Checker & Outliner - H1-H6 SEO Flags
Pricing
from $1.20 / 1,000 scanned pages
Heading Structure Checker & Outliner - H1-H6 SEO Flags
Extracts the H1-H6 heading structure of page URLs, single or bulk, as an ordered outline. Returns each heading and level, an indented outline, H1 count and SEO flags for missing or multiple H1s, skipped levels and empty headings. For SEO specialists, accessibility auditors and editors.
Pricing
from $1.20 / 1,000 scanned pages
Rating
0.0
(0)
Developer
Broke to Built
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
15 days ago
Last modified
Categories
Features
Share
Heading Structure Outliner — H1–H6 outline + SEO flags
Extract a page's heading structure (H1–H6) as an ordered outline, with SEO issue flags: missing H1, multiple H1s, skipped levels, empty headings. Built for SEO audits, accessibility checks, and content-structure review. Single URL or bulk.
$0.0015 per page — a fraction of the paid SEO-audit actors measured on the Store. Failed fetches are recorded free.
Who uses it
- SEO specialists finding pages with missing or multiple H1s across a URL list
- Accessibility auditors flagging skipped heading levels for screen-reader users
- Content strategists outlining competitor articles by their H2 and H3 structure
- Editors checking a published post's heading hierarchy matches its brief
- Developers catching empty headings left by a CMS template
What you get
- Every heading in document order:
{ level, text }. outline— an indented text tree of the heading hierarchy.issues— SEO flags (no H1, multiple H1s, a skipped level like H2→H4, empty headings).h1CountandheadingCount.- Fail-soft: an unreachable URL returns
{ok:false, error}and is never charged.
Input
{ "url": "https://github.com", "urls": ["https://example.com/blog"], "maxUrls": 25 }
Output (real run, 2026-08-07)
{"ok": true,"url": "https://github.com","status": 200,"h1Count": 1,"headingCount": 26,"headings": [{ "level": 2, "text": "Navigation Menu" },{ "level": 1, "text": "The future of building happens together" },{ "level": 2, "text": "GitHub features" }],"outline": " H2: Navigation Menu\nH1: The future of building happens together\n H2: GitHub features\n...","issues": []}
Example
A real run on 2026-10-31 with the input this page's form is prefilled with:
{"url": "https://github.com","urls": []}
It finished in 1 second and returned 1 result. It was charged for 1 page-scanned event ($0.0015 on the Free plan). The first result (long text and lists cut for display):
{"ok": true,"url": "https://github.com/","finalUrl": "https://github.com/","status": 200,"h1Count": 1,"headingCount": 28,"headings": [{"level": 2,"text": "Navigation Menu"},{"level": 1,"text": "Software still starts with you"},{"level": 2,"text": "Product walkthrough"},"… 25 more"],"outline": " H2: Navigation Menu\nH1: Software still starts with you\n H2: Product walkthrough\n H2: GitHub activity\n H2: GitHub Platform\n H3: GitHub\n H3: Copilot\n …","issues": []}
Pricing — $0.0015 per page
A dedicated heading outliner, not a heavyweight full-site audit. Prices below checked via the Apify Store API on 2026-08-07:
| Actor | Pricing | One page |
|---|---|---|
| This actor | $0.0015 per page | $0.0015 |
| dltik/geo-site-audit | $0.00005 start + $0.01 per page-audited | $0.01 |
| alizarin_refrigerator-owner/technical-seo-auditor | $0.1 start + $0.1 per page_audit | $0.20 |
Limits (honest ones)
- Reads the server HTML; headings rendered later by JavaScript are not counted.
- The
issueslist flags common structural problems; it is not a full accessibility or SEO audit. maxUrlscapped per run.
FAQ
- What issues does it flag? Missing H1, multiple H1s, skipped heading levels, and empty headings.
- Is the outline machine-readable? You get both the raw
headingsarray (for code) and the indentedoutlinestring (for humans). - Does it run JavaScript? No — server HTML only.
- 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-headings-outliner/runs?token=YOUR_APIFY_TOKEN" \-H 'content-type: application/json' \-d '{"url":"https://github.com"}'
Callable as an agent tool through the Apify MCP server (mcp.apify.com).
Changelog
- 2026-11-01: Page text only: an Example section from a real run. Code, output and price are unchanged.
For AI agents
This Actor is built to be called by software, not just by people.
- Mount it directly as an MCP tool — no Store search, no ranking, just this one tool:
https://mcp.apify.com/?actors=eliai/webpage-headings-outliner - Or call it over HTTP and get the results in the same request:
POST https://api.apify.com/v2/acts/eliai~webpage-headings-outliner/run-sync-get-dataset-items - Costs are predictable before you call. Pricing is pay-per-event (see Pricing above), so an agent can budget a run in advance instead of discovering the bill afterwards.
- Send only the field you mean. If you pass the bulk field, it is used on its own; the single-value field is a fallback, never merged into your request. You are charged for the items you sent and nothing else.