Site Signal — Public-Surface Website Profiler
Pricing
from $10.00 / 1,000 site profiles
Site Signal — Public-Surface Website Profiler
Pricing
from $10.00 / 1,000 site profiles
Rating
0.0
(0)
Developer
QualifyOps
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
13 hours ago
Last modified
Categories
Share
Site Signal — public-surface site profiler
Given one or more domains, returns a structured profile built only from what the
site owner publicly publishes for machines: homepage <head> (title, description,
generator/CMS, OpenGraph, JSON-LD), robots.txt (honoured), sitemap.xml,
.well-known/security.txt, and declared RSS/Atom feeds. No login-walled pages, no
protected data, no proxies, no scraping of a hostile source.
Commercial ancestry (why this exists)
Reverse-engineers the proven "site metadata / contactability enrichment" mechanism
(Apify: compass, lukaskrivka, vdrmota; Hunter.io) — see
../../OPERATOR_BLOOD_TRAILS_TEST_002_PROVEN_OPERATOR_CORPUS_2026-07-10.md and
../../lane-000-money-artery-discovery.md. It follows the IPinfo counter-model
(self-source / genuinely-public data, Test 002 §7-2) and deliberately avoids the
Google/LinkedIn-owned hostile surfaces that produced the Proxycurl legal tombstone.
- Demand → asset → payment → delivery → maintenance: domain-enrichment demand → single-purpose profiler → Apify pay-per-event → automatic dataset delivery → selector/parse upkeep only.
Run / verify locally (no Docker, no deps)
Core profileSite() is dependency-free and verified working (HTTP 200, structured
signals, completeness score). The apify dependency and Store packaging are only used
inside the Apify runtime.
Status
Minimum executable form is built and verified. Publication to the Apify Store is
owner-gated — see EXECUTION_STATUS.md.
