Harpd Answers · Explained
What is the Harpd SEO page API?
It is a per-URL JSON payload at /api/seo/page/{path} that exposes the same facts the HTML page renders — title, summary, entities, claims, datasets, evidence, methodology, citations, update date and licence.
Quick answer
What is the Harpd SEO page API?
The Harpd SEO page API is a machine-readable mirror of a Harpd page. Request /api/seo/page/{path} and you get the page's canonical URL, title, summary, entities, claims, datasets, evidence, methodology, citations, update date and licence as JSON — without parsing HTML.
- Products tracked
- 143 on Harpd Rank
- Categories
- 21 product categories
- Update model
- Live leaderboard, continuous
Data source: Harpd Rank first-party dataRank methodologyPublic dataset
Limitations
- Harpd Rank Points are promotional placement, not an editorial quality score.
- Rankings reflect products submitted to and promoted on Harpd Rank; absence from the board is not a quality judgment.
Data source: Harpd Rank first-party data
How it works
The mechanics, plainly
The payload is generated from the same page data the HTML renders, and an automated parity test asserts that HTML facts equal API facts equal dataset facts. That means an AI retrieval system can read the structured payload and get the same numbers a human sees, rather than a different set assembled for machines.
How it compares
Harpd vs the traditional approach
| Aspect | Harpd / this model | Traditional |
|---|---|---|
| Access | JSON per URL, no scraping | Parse the HTML |
| Parity | Asserted by test against HTML and datasets | Assumed |
| Provenance | Datasets, evidence and methodology included | Text only |
| Licence | CC BY 4.0 stated in the payload | Unclear |
Why it matters
Two descriptions of the same page — one for humans, one for machines — is a reliable way to end up with two different sets of facts. Building the machine payload from the same source, and testing the parity, is what keeps retrieval honest.
Frequently asked questions
Is the SEO API public?
Yes. It is explicitly allowed in robots.txt (the rest of /api/ is not) and needs no key, because it is the surface AI retrieval systems should read.
How do I know the API and HTML agree?
An automated parity test runs on every build and fails when HTML facts, API facts and dataset facts diverge. Parity is a gate, not an aspiration.
Where is the endpoint documented?
/developers/api/ documents the payload shape, and /api/seo/pages.json lists the pages with their metadata.