Public pages
$0 /month
Review live site data before requesting API access
- Public documentation access
- Live directory and site examples
- Reference payload previews
- No anonymous API requests
- Upgrade path via GitHub login
- Manual Pro activation available
Enter a website and get a live site data report with traffic estimates, SEO structure, technology signals, business context, and trust checks.
Traffic
Visits, rank, and audience estimates
SEO
Indexability, links, and search structure
Trust
Measured risk and quality signals
Live site data preview
The same report model powers public pages and API output.
Browse site data
Use market, technology, and topic paths to find relevant domains first. Then open live site data on the examples that deserve a closer look.
Start with market context, then open live site data on the domains that matter.
Find sites by stack, then compare traffic, trust, and business signals.
Browse niches and audience intent before drilling into individual reports.
Live site data examples
These examples show the same report model across AI, infrastructure, design, and developer tools. Open one to understand the data before you ask for an API key.
What to compare first
Start with trust, traffic, technology, and SEO structure. Those four signals usually tell you whether a domain is worth deeper research.
Explore browse pathsSee how a high-interest product site is presented across trust, traffic, SEO, and tech.
Best for
Studying breakout product positioning and authority signals.
Inspect brand authority, infrastructure, and monetization clues on a mature B2B site.
Best for
Understanding how mature platform businesses surface credibility.
Use a recognizable SaaS example to understand how the modules read on a strong brand.
Best for
Reviewing category fit, product positioning, and audience signals.
Open a developer-focused report to compare stack signals, rankings, and business posture.
Best for
Benchmarking technical maturity and ecosystem credibility.
Site data signals
SiteJSON pairs live reports with browse paths so you can inspect traffic, SEO, technology, business, and trust signals in the product before you decide to automate them.
Why this matters
Starter requests
200
Test live site data before integrating.
Free plan rate
10 req/min
Enough for manual checks and demos.
Pro quota
1000/cycle
Built for repeatable enrichment jobs.
Browse paths
3 paths
Category, technology, and topic discovery.
3 browse paths
Start from category, technology, or topic pages before you open a single report.
6 report modules
Traffic, SEO, tech, business, trust, and directory pivots stay connected in one report.
Cross-page paths
Visitors can move from browse paths to reports to adjacent examples without losing context.
API optional
The site proves the data first, then hands power users a structured API path.
Developer-ready outputs
The report view and API response share the same practical shape: inspect first, then integrate.
Use the data
Start with one browse path or one live report, then decide whether you need more comparison, deeper review, or structured output in the API.
Start with a directory, open live reports, and compare site data across traffic, SEO, and trust.
Use one report to check legitimacy, likely scale, and technical footprint before outreach.
When the on-site view is useful, move into docs and signed API access without changing the data model.
Public pages show the report model first. GitHub login unlocks 200 one-time starter requests, a signed API key, and 10 req/min. Pro adds 1000 requests per billing cycle at 100 req/min through manual activation.
$0 /month
Review live site data before requesting API access
$0 /month
GitHub login unlocks your free API key
Manual activation
For teams that need higher-volume site data access
Site data and SEO
Site data turns a domain into usable evidence: estimated traffic, search structure, technical footprint, business signals, and trust context. The point is not just to identify a website. The point is to help someone decide what the website means.
SiteJSON keeps that evidence connected. You can start from a directory, open a live report, compare related domains, and export the same shape as structured JSON when the data needs to move into code.
Teams rarely decide from one metric. They want a compact read on traffic, search structure, technology, business posture, and trust. That is why SiteJSON groups the report around modules that are easy to scan before you commit to deeper research.
The workflow is simple: open live site data, compare what matters, and move to the API when the model fits the job. Browse paths create context. Report pages provide evidence. Related links keep the next step obvious.
| Experience | Primary output | Decision value | SEO durability |
|---|---|---|---|
| Basic lookup tool | Single metric | Low | Weak |
| Unstructured scraper | Raw page dump | Medium | Medium |
| SiteJSON site data | Browse to report to export | High | High |
This keeps pages connected instead of isolated. Browse pages frame the question. Reports explain the data. Related links keep the next action obvious.
Programmatic SEO works when templates have distinct jobs. A thin directory can be crawled, but it does not build trust. A thin report may rank briefly, but it does not explain the data or earn repeat visits.
SiteJSON already has the right surfaces: browse paths, domain reports, subpages, comparisons, and insights. Each surface should feel like part of the same site data system: one place to discover, one place to inspect, and one path into reusable JSON.
Browse paths
Start broad when you need market context for the site data.
Category paths
Browse commercial markets before opening individual reports.
Technology paths
See which stacks cluster together, then open live reports.
Topic paths
Explore niches and audience intent before picking target domains.
Sample live report
See one domain across traffic, SEO, tech, business, and trust.
Insights
Open broader site data views that support repeat analysis.
If you want to understand the product fast, open the browse paths, then a live domain report, then one of the technology paths or topic paths. That sequence explains the site data and keeps the next action clear.
FAQ
Learn what the product shows, how browse paths work, and when API access is the right next step.
You can browse market, technology, and topic paths, open live reports, compare site data across trust, traffic, SEO, and tech, and decide whether you need the API.
They create crawlable discovery paths and help users move from broad market questions into specific domain reports without losing context.
Each report organizes site data into clear modules so a visitor can understand what matters and where to go next.
This version is built for analysts, buyers, growth teams, sales operators, and builders who want utility first and integration second.