ANALYSIS, MADE CLEAR.AnalyzeAPI.com
Documentation ↗

KEYWORD ANALYZE API

Find the intent.
Connect the ideas.

Organize keyword collections around the questions people need answered. Build clear topic clusters, content maps, and editorial next steps.

Explore this sampleRead the guide

WHAT GOES IN

The right input.
The right question.

Keyword lists with language, source, and optional documented historical metrics.

KEEP THE SCOPE CLEARNo search-volume or difficulty numbers are inferred from wording. Provider metrics need their own source, market, and time period.

WHAT COMES OUT

A report you can use.

  • Intent labels and ambiguous cases
  • Topic clusters with original phrases
  • Existing-page mappings and content actions

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

A PRACTICAL WORKFLOW

Build a useful content map

Group phrases by reader task, map each group to an existing page, and identify the specific gap. Preserve the original wording and review ambiguous phrases before creating more content.

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

Keyword list

Three sample search phrases

Three phrases. Three different reader needs.

·
Learning intent

“what is an analysis API” asks for an explanation.

·
Implementation intent

“parse analysis API JSON” asks how to build.

!
Ambiguous intent

“SEO API” alone does not establish a specific task.

report.json
{
  "schema_version": "1.0",
  "report_id": "sample-keyword-analysis",
  "sample": true,
  "analysis_type": "keyword-analysis",
  "status": "complete",
  "target": {
    "label": "Three sample search phrases",
    "input_kind": "Keyword list"
  },
  "summary": "Three phrases. Three different reader needs.",
  "findings": [
    {
      "id": "f01",
      "outcome": "note",
      "title": "Learning intent",
      "evidence": "“what is an analysis API” asks for an explanation.",
      "action": "Map to an introductory guide."
    },
    {
      "id": "f02",
      "outcome": "note",
      "title": "Implementation intent",
      "evidence": "“parse analysis API JSON” asks how to build.",
      "action": "Map to a response-format tutorial."
    },
    {
      "id": "f03",
      "outcome": "review",
      "title": "Ambiguous intent",
      "evidence": "“SEO API” alone does not establish a specific task.",
      "action": "Review with additional audience context."
    }
  ],
  "not_measured": [
    "Search volume",
    "Keyword difficulty",
    "Future traffic"
  ]
}
Illustrative data. No live analysis or uploads.Download JSON Explore workflow

TAKE IT FURTHER

A little context goes a long way.

Preserve original phrases, define intent, and map useful clusters to real editorial actions—without invented metrics.

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