Harpd Answers · Explained
What is a product entity on Harpd?
A product entity is the canonical record of one product on Harpd: a stable id, name, slug, description, category, product type, capabilities, website, verification status and rank data — reused by every page type.
Quick answer
What is a product entity on Harpd?
A product entity is Harpd's single canonical record of a product. It carries a stable identifier that survives a rename, plus the product's name, slug, description, category, type, capabilities, website, verification status and current rank data.
- 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 entity is built once from the listing and reused everywhere: the board row, the product profile, the comparison table, the alternatives card, the datasets and the entity graph all read the same object. Fields that the listing does not carry are emitted as unknown rather than guessed, so a page can render "not stated" instead of inventing a capability.
How it compares
Harpd vs the traditional approach
| Aspect | Harpd / this model | Traditional |
|---|---|---|
| Identity | Stable id, never the product name | Name used as the key |
| Consistency | One object reused by every page type | Each page reads raw fields |
| Unknowns | Emitted as unknown, not guessed | Filled with plausible values |
| Access | Published at /data/entities.json | HTML only |
Why it matters
Entity drift is the quiet failure of every directory: the same product described differently on three pages, and an AI system that concludes there are three products. One canonical object per product is the fix.
Frequently asked questions
Why not use the product name as the identifier?
Names change and collide. A stable id keeps every historical reference, dataset row and citation resolvable after a rebrand.
What happens to fields the product does not declare?
They are emitted as unknown. Harpd does not infer a capability or a product type that the listing does not state.
How do I get the entity data?
/data/entities.json publishes the product node set, and /data/entity-graph.json publishes nodes with the relationships between them.