✦ YOUR NEXT INSIGHT STARTS HERE

Less guesswork.
More clarity.

Analyze websites, keywords, code & AI.

Eight ways to ask better questions. One place to explore the evidence.
Find your next move with clear workflows and structured insights.

8 analysis workflowsStructured JSON examplesNo account needed
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
SEO AnalysisLLM EvaluationKeyword IntentGit RepositoriesWebsite GEOStructured JSONClearer Answers

FROM CURIOSITY TO CLARITY

Three steps. One clearer view.

A practical approach to analysis, whether you are reviewing a page, a codebase, or an AI response.

01

Choose your question.

Pick a workflow and define the input. A useful analysis starts with a decision worth making.

02

Inspect the evidence.

See observations, context, and what remains unknown. Every finding should have a reason.

03

Build your next step.

Turn a structured report into an editorial task, a review queue, or a better developer experience.

FOR THE BUILDERS

Made for humans.
Ready for your code.

Less digging through output. More doing something useful with it.

Explore a consistent JSON envelope, evidence-linked findings, and practical examples in JavaScript, Python, and cURL.

  • Downloadable sample reports
  • A documented JSON Schema
  • Clear scope, explicit unknowns
Open the documentation
// Read a bundled sample — no API key needed.
async function readSample() {
  const response = await fetch(
    "/assets/samples/seo-analysis.json"
  );
  if (!response.ok) {
    throw new Error(`HTTP ${response.status}`);
  }
  const report = await response.json();
  console.table(report.findings);
  return report;
}
readSample().catch(console.error);
Static sample files · same-origin JavaScript example

THE ANALYSIS JOURNAL

Good questions.
Even better reading.

Practical guides for curious builders. Get beyond the buzzwords and into the work.
Read the journal

A LITTLE MORE CONTEXT

Questions?
Good. So do we.

Here is how the toolkit, samples, and guides fit together.

More answers
What can I explore with AnalyzeAPI?

Explore eight analysis workflows: AI text, LLM responses, SEO, website GEO, search results, keywords, Git repositories, and broader website reviews. Each has its own guide and illustrative JSON report.

Does the playground analyze my live website?

No. The playground switches between bundled sample reports. It does not crawl a website, run a model, connect to a repository, or upload visitor data. The sample labels stay visible throughout the experience.

Do I need an API key or an account?

No account or API key is needed to browse these pages or download the sample JSON files. Connecting a production analysis provider would be a separate integration with its own authentication and data-handling requirements.

How is website GEO different from SEO?

Here, GEO means generative engine optimization. Its workflow reviews supplied AI-answer mentions, citations, and supporting sources. The SEO workflow focuses on page structure, metadata, internal links, and other supplied website evidence.

Can I use the examples in my own project?

Yes. The original code examples and sample JSON are available for adaptation in your projects. Read the response-format guide before relying on a field, and keep illustrative reports separate from live measurements.

Where should I start?

Begin with the analysis overview to choose a workflow, or open the developer quickstart to load a sample report. The Analysis Journal adds longer, practical guides for each topic.

Less guessworkBetter questionsUseful evidenceClear next stepsBuilt for curiosity

Make your next move
a clearer one.

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