ANALYSIS, MADE CLEAR.AnalyzeAPI.com
Documentation ↗

SEO ANALYZE API

See the details.
Find your next fix.

Make website evidence actionable. Explore metadata, internal links, canonical declarations, and content structure without hiding the findings behind a mystery score.

Explore this sampleRead the guide

WHAT GOES IN

The right input.
The right question.

An authorized crawl, supplied HTML, URL inventory, and optional owner-provided search data.

KEEP THE SCOPE CLEARRetrieval, indexing, and ranking are different states. A successful page fetch does not establish search visibility.

WHAT COMES OUT

A report you can use.

  • Page-level metadata observations
  • Internal-link and canonical review tasks
  • Prioritized findings with reproducible evidence

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

A PRACTICAL WORKFLOW

Turn an audit into an editorial backlog

Group findings by page template, attach the affected URLs, and distinguish a missing element from a content recommendation. Give each issue an owner and a check that confirms the fix.

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

Supplied HTML

Documentation page

A small page review, with the evidence attached.

✓
A descriptive title is present

<title>Getting started with the sample project</title>

!
The description needs attention

The supplied document has no description meta element.

✓
The main heading is clear

One H1 is present: Getting started.

report.json
{
  "schema_version": "1.0",
  "report_id": "sample-seo-analysis",
  "sample": true,
  "analysis_type": "seo-analysis",
  "status": "complete",
  "target": {
    "label": "Documentation page",
    "input_kind": "Supplied HTML"
  },
  "summary": "A small page review, with the evidence attached.",
  "findings": [
    {
      "id": "f01",
      "outcome": "pass",
      "title": "A descriptive title is present",
      "evidence": "<title>Getting started with the sample project</title>",
      "action": "Keep the title specific to this guide."
    },
    {
      "id": "f02",
      "outcome": "review",
      "title": "The description needs attention",
      "evidence": "The supplied document has no description meta element.",
      "action": "Write an accurate summary of the page."
    },
    {
      "id": "f03",
      "outcome": "pass",
      "title": "The main heading is clear",
      "evidence": "One H1 is present: Getting started.",
      "action": "Keep a logical heading hierarchy."
    }
  ],
  "not_measured": [
    "Live indexing status",
    "Search rankings",
    "Real-user performance"
  ]
}
Illustrative data. No live analysis or uploads.Download JSON Explore workflow

TAKE IT FURTHER

A little context goes a long way.

Define coverage, inspect metadata and links, then prioritize evidence-backed changes that your team can verify.

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