ANALYSIS, MADE CLEAR.AnalyzeAPI.com
Documentation ↗

WEBSITE ANALYZE API

A better website
starts with a closer look.

Connect structure, content, and usability in one review plan. Inspect the experience a visitor can actually reach, not just the elements a parser can count.

Explore this sampleRead the guide

WHAT GOES IN

The right input.
The right question.

Supplied page content, authorized browser observations, and a defined review scope.

KEEP THE SCOPE CLEARHTML inspection alone cannot measure real-user performance or establish complete accessibility conformance.

WHAT COMES OUT

A report you can use.

  • Navigation and content structure findings
  • Responsive layout and accessibility review tasks
  • Evidence-linked improvement priorities

Keep the evidence, interpretation, and next action separate. Document missing inputs instead of filling them with guessed values.

A PRACTICAL WORKFLOW

Review a site before publication

Walk through important journeys on mobile and desktop. Check destinations, headings, image dimensions, focus states, and content clarity, then record repeatable acceptance checks.

Explore integration patterns

LOOK INSIDE THE OUTPUT

Evidence, not a mystery score.

An illustrative report for this workflow. Download the JSON to inspect the complete structure.

THE ANALYSIS PLAYGROUND
Interactive sample

Illustrative browser-review notes

Sample documentation journey

A small usability review with concrete next actions.

✓
The main destination is linked

The sample navigation includes Getting started.

!
A control needs a label

The illustrative notes identify an unlabeled icon button.

·
Mobile review is a separate task

Only the supplied desktop observations are included.

report.json
{
  "schema_version": "1.0",
  "report_id": "sample-website-analysis",
  "sample": true,
  "analysis_type": "website-analysis",
  "status": "complete",
  "target": {
    "label": "Sample documentation journey",
    "input_kind": "Illustrative browser-review notes"
  },
  "summary": "A small usability review with concrete next actions.",
  "findings": [
    {
      "id": "f01",
      "outcome": "pass",
      "title": "The main destination is linked",
      "evidence": "The sample navigation includes Getting started.",
      "action": "Keep the destination reachable on mobile."
    },
    {
      "id": "f02",
      "outcome": "review",
      "title": "A control needs a label",
      "evidence": "The illustrative notes identify an unlabeled icon button.",
      "action": "Add a meaningful accessible name."
    },
    {
      "id": "f03",
      "outcome": "note",
      "title": "Mobile review is a separate task",
      "evidence": "Only the supplied desktop observations are included.",
      "action": "Repeat the journey at narrow widths."
    }
  ],
  "not_measured": [
    "Live performance metrics",
    "Complete accessibility conformance",
    "Device-wide compatibility"
  ]
}
Illustrative data. No live analysis or uploads.Download JSON Explore workflow

TAKE IT FURTHER

A little context goes a long way.

Start with a decision, preserve the evidence, and design a report both humans and software can understand.

Read the full guide

Before you connect a real source

Confirm that you are authorized to use the input. Preserve its collection context and version, agree on an acceptance rule, and decide how incomplete results should be reviewed.

  • Validate the report before consuming it.
  • Keep secrets out of public browser code.
  • Show what was—and was not—measured.

Make your next move
a clearer one.

Explore the workflows. Inspect the evidence. Build something useful.

Explore the toolkitRead the docs