Rescan Report
Share Report
Copy Report Link
Rescan Report
Share Report
Copy Report Link
Export Report
62/100

OVERALL SCORE

Level 3, Bot-Aware

Moderate readiness for AI agents
AIDiscoverability41%Agent Easeof Use20%Security& Trust60%GEO, AIO, AEO66%SEO100%Performance& Accessibility90%
  • AI Discoverability 41 out of 100
  • Agent Ease of Use 20 out of 100
  • Security & Trust 60 out of 100
  • GEO, AIO and AEO 66 out of 100
  • SEO 100 out of 100
  • Performance and Accessibility 90 out of 100

CAPTURED SCREENSHOT

Captured website desktop screenshot

What AI sees of your website

Enigma: Trusted business data favicon

Enigma: Trusted business data

Enigma provides the most accurate and comprehensive data on 49M+ U.S. businesses. Access deep firmographics, contacts, and exclusive card revenue data to power your GTM and risk workflows.

Next step

Turn this report into a fix workflow

25 failed checks are ready to move into MCP or CLI remediation. Generate a repair prompt, connect the scanner to your coding agent, or open the integration docs before your next rescan.

Detailed report scores grouped by capability area
MetricScoreStatusPassedFailedWarningEvidence
AI Discoverability
41
Priority fix9141View details
Discoverability
33
Priority fix360View details
Content Readiness
54
Needs work551View details
Bot Access Control
33
Priority fix130View details
Agent Ease of Use
20
Priority fix9312View details
API
0
Priority fix060View details
Auth
Not Applicable
Not Applicable070View details
MCP
47
Priority fix471View details
Skill Discovery
12
Priority fix1111View details
Agent Commerce
Not Applicable
Not Applicable400
GEO, AIO and AEO
66
Needs work3313View details
GEO Readiness
77
Mostly ready104
AIO Readiness
55
Needs work124View details
AEO Readiness
63
Needs work115View details
SEO
100
Strong1100
SEO
100
Strong1100
Security & Trust
60
Needs work720View details
Security & Trust
60
Needs work320View details
AI Training Exposure
Not Applicable
Not Applicable400
Performance and Accessibility
90
Strong2243View details
Performance
88
Mostly ready1643View details
Accessibility
94
Strong600

Prioritized recommendations

Issues ranked by score impact

48 items need attention

AI DiscoverabilityBot Access ControlEstablished

AI bot rules in robots.txt

AI bot rules in robots.txt is missing or incomplete.

50 Fail

Needs attention

AI bot rules in robots.txt

Failed check
01

Issue

No specific User-agent rules found for major AI crawlers (GPTBot, ClaudeBot, etc.) in robots.txt.

02

Why it matters

Explicit AI bot rules reduce ambiguity for crawler operators and make training, indexing, or retrieval access policy auditable.

Check name

AI bot rules in robots.txt

Score

0/100

Status

fail

Category

Bot Access Control

Maturity

Established

Goal

Add User-agent rules for AI crawlers like GPTBot, Claude-Web, and others.

Result

AI bot rules in robots.txt is missing or incomplete.

Evidence
{
  "expectedBots": [
    "GPTBot",
    "ChatGPT-User",
    "ClaudeBot",
    "Claude-Web",
    "Anthropic-AI",
    "Google-Extended",
    "PerplexityBot",
    "CCBot",
    "Applebot-Extended",
    "Meta-ExternalAgent",
    "Bytespider",
    "Amazonbot",
    "Cohere-AI"
  ],
  "configuredBots": []
}

Agent Ease of UseAPIEstablished

API Catalog

API Catalog failed at "Fetch API catalog".

50 Fail

Needs attention

API Catalog

Failed check
01

Issue

The API catalog endpoint did not return HTTP 2xx.

02

Why it matters

API catalogs help agents find service descriptions, documentation, and status resources without guessing API entry points.

Check name

API Catalog

Score

0/100

Status

fail

Category

API

Maturity

Established

Goal

Publish an API catalog for automated API discovery using RFC 9727.

Result

API Catalog failed at "Fetch API catalog".

Validation steps

  1. Fetch API catalog

    The API catalog endpoint did not return HTTP 2xx.

  2. Validate RFC 9727 linkset

    Response is not valid JSON.

  3. Fetch advertised API catalog targets

    API Catalog did not expose any same-origin hrefs to validate.

Evidence
{
  "failedStep": "fetch",
  "steps": [
    {
      "id": "fetch",
      "title": "Fetch API catalog",
      "status": "fail",
      "evidence": {
        "statusCode": 404,
        "contentType": "text/html; charset=utf-8"
      },
      "issue": "The API catalog endpoint did not return HTTP 2xx.",
      "howToFix": "Publish /.well-known/api-catalog."
    },
    {
      "id": "validate",
      "title": "Validate RFC 9727 linkset",
      "status": "fail",
      "evidence": {
        "valid": false,
        "compatibleContentType": false,
        "issue": "Response is not valid JSON.",
        "rawExcerpt": "<!DOCTYPE html><html lang=\"en\"> <head><meta charset=\"UTF-8\"><meta name=\"viewport\" content=\"width=device-width, initial-scale=1.0\"><link rel=\"icon\" type=\"image/svg+xml\" href=\"/favicon.svg\"><link rel=\"apple-touch-icon\" href=\"/favicon-260.png\"><link rel=\"canonical\" href=\"https://www.enigma.com/404/\"><title>Not Found | Enigma</title><meta name=\"title\" content=\"Not Found | Enigma\"><meta name=\"description\" content=\"Not Found\"><meta name=\"robots\" content=\"noindex, nofollow\"><meta property=\"og:type\" content=\"website\"><meta property=\"og:url\" content=\"https://www.enigma.com/404/\"><meta property=\"og:title\" content=\"Not Found | Enigma\"><meta property=\"og:description\" content=\"Not Found\"><meta property=\"og:image\" content=\"https://www.enigma.com/og/default.png\"><meta property=\"twitter:card\" content=\"sum"
      },
      "issue": "Response is not valid JSON.",
      "howToFix": "Use application/linkset+json with service-desc, service-doc, and status relations that each include href."
    },
    {
      "id": "target-validation",
      "title": "Fetch advertised API catalog targets",
      "status": "fail",
      "evidence": {
        "checked": [],
        "failures": [
          {
            "reason": "No same-origin API catalog hrefs were available to fetch."
          }
        ]
      },
      "issue": "API Catalog did not expose any same-origin hrefs to validate.",
      "howToFix": "Make each same-origin API catalog href reachable and serve the advertised media type."
    }
  ]
}

Security & TrustSecurity & TrustEstablished

Content-Security-Policy

Content-Security-Policy is missing or incomplete.

50 Fail

Needs attention

Content-Security-Policy

Failed check
01

Issue

Content-Security-Policy is missing or incomplete.

02

Why it matters

Content Security Policy limits where scripts, styles, frames, and connections can load from, reducing the impact of injection bugs.

Check name

Content-Security-Policy

Score

0/100

Status

fail

Category

Security & Trust

Maturity

Established

Goal

Constrain script, style, frame, and resource loading with a Content-Security-Policy header.

Result

Content-Security-Policy is missing or incomplete.

Evidence
{
  "header": "content-security-policy",
  "value": null
}

Security & TrustSecurity & TrustEstablished

HSTS header

HSTS header is missing or incomplete.

50 Fail

Needs attention

HSTS header

Failed check
01

Issue

HSTS header is missing or incomplete.

02

Why it matters

HSTS tells browsers to keep using HTTPS after the first secure visit, reducing downgrade and mixed-transport risk for repeat users.

Check name

HSTS header

Score

0/100

Status

fail

Category

Security & Trust

Maturity

Established

Goal

Require HTTPS for repeat visits with Strict-Transport-Security.

Result

HSTS header is missing or incomplete.

Evidence
{
  "header": "strict-transport-security",
  "value": "max-age=86400"
}

Agent Ease of UseAPIEstablished

OpenAPI discovery

OpenAPI discovery failed at "Find valid OpenAPI document".

50 Fail

Needs attention

OpenAPI discovery

Failed check
01

Issue

OpenAPI YAML document did not match the expected shape. Content-Type "text/html; charset=utf-8" is not a recognized type; unsupported version: ; missing info block with title and version; missing paths block; no operations found.

02

Why it matters

OpenAPI documents let agents understand available operations, schemas, authentication, and request formats before calling an API.

Check name

OpenAPI discovery

Score

0/100

Status

fail

Category

API

Maturity

Established

Goal

Publish a valid OpenAPI or Swagger document for API discovery.

Result

OpenAPI discovery failed at "Find valid OpenAPI document".

Validation steps

  1. Find valid OpenAPI document

    OpenAPI YAML document did not match the expected shape. Content-Type "text/html; charset=utf-8" is not a recognized type; unsupported version: ; missing info block with title and version; missing paths block; no operations found.

Evidence
{
  "failedStep": "fetch",
  "steps": [
    {
      "id": "fetch",
      "title": "Find valid OpenAPI document",
      "status": "fail",
      "evidence": {
        "checked": [
          {
            "path": "/openapi.json",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "valid": false,
            "issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html; charset=utf-8\" is not a recognized type; unsupported version: ; missing info block with title and version; missing paths block; no operations found.",
            "compatibleContentType": false,
            "format": "yaml",
            "version": "",
            "pathCount": 0,
            "operationCount": 0,
            "rawExcerpt": "<!DOCTYPE html><html lang=\"en\"> <head><meta charset=\"UTF-8\"><meta name=\"viewport\" content=\"width=device-width, initial-scale=1.0\"><link rel=\"icon\" type=\"image/svg+xml\" href=\"/favicon.svg\"><link rel=\"apple-touch-icon\" href=\"/favicon-260.png\"><link rel=\"canonical\" href=\"https://www.enigma.com/404/\"><title>Not Found | Enigma</title><meta name=\"title\" content=\"Not Found | Enigma\"><meta name=\"description\" content=\"Not Found\"><meta name=\"robots\" content=\"noindex, nofollow\"><meta property=\"og:type\" content=\"website\"><meta property=\"og:url\" content=\"https://www.enigma.com/404/\"><meta property=\"og:title\" content=\"Not Found | Enigma\"><meta property=\"og:description\" content=\"Not Found\"><meta property=\"og:image\" content=\"https://www.enigma.com/og/default.png\"><meta property=\"twitter:card\" content=\"sum"
          },
          {
            "path": "/openapi.yaml",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "valid": false,
            "issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html; charset=utf-8\" is not a recognized type; unsupported version: ; missing info block with title and version; missing paths block; no operations found.",
            "compatibleContentType": false,
            "format": "yaml",
            "version": "",
            "pathCount": 0,
            "operationCount": 0,
            "rawExcerpt": "<!DOCTYPE html><html lang=\"en\"> <head><meta charset=\"UTF-8\"><meta name=\"viewport\" content=\"width=device-width, initial-scale=1.0\"><link rel=\"icon\" type=\"image/svg+xml\" href=\"/favicon.svg\"><link rel=\"apple-touch-icon\" href=\"/favicon-260.png\"><link rel=\"canonical\" href=\"https://www.enigma.com/404/\"><title>Not Found | Enigma</title><meta name=\"title\" content=\"Not Found | Enigma\"><meta name=\"description\" content=\"Not Found\"><meta name=\"robots\" content=\"noindex, nofollow\"><meta property=\"og:type\" content=\"website\"><meta property=\"og:url\" content=\"https://www.enigma.com/404/\"><meta property=\"og:title\" content=\"Not Found | Enigma\"><meta property=\"og:description\" content=\"Not Found\"><meta property=\"og:image\" content=\"https://www.enigma.com/og/default.png\"><meta property=\"twitter:card\" content=\"sum"
          },
          {
            "path": "/swagger.json",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "valid": false,
            "issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html; charset=utf-8\" is not a recognized type; unsupported version: ; missing info block with title and version; missing paths block; no operations found.",
            "compatibleContentType": false,
            "format": "yaml",
            "version": "",
            "pathCount": 0,
            "operationCount": 0,
            "rawExcerpt": "<!DOCTYPE html><html lang=\"en\"> <head><meta charset=\"UTF-8\"><meta name=\"viewport\" content=\"width=device-width, initial-scale=1.0\"><link rel=\"icon\" type=\"image/svg+xml\" href=\"/favicon.svg\"><link rel=\"apple-touch-icon\" href=\"/favicon-260.png\"><link rel=\"canonical\" href=\"https://www.enigma.com/404/\"><title>Not Found | Enigma</title><meta name=\"title\" content=\"Not Found | Enigma\"><meta name=\"description\" content=\"Not Found\"><meta name=\"robots\" content=\"noindex, nofollow\"><meta property=\"og:type\" content=\"website\"><meta property=\"og:url\" content=\"https://www.enigma.com/404/\"><meta property=\"og:title\" content=\"Not Found | Enigma\"><meta property=\"og:description\" content=\"Not Found\"><meta property=\"og:image\" content=\"https://www.enigma.com/og/default.png\"><meta property=\"twitter:card\" content=\"sum"
          },
          {
            "path": "/swagger.yaml",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "valid": false,
            "issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html; charset=utf-8\" is not a recognized type; unsupported version: ; missing info block with title and version; missing paths block; no operations found.",
            "compatibleContentType": false,
            "format": "yaml",
            "version": "",
            "pathCount": 0,
            "operationCount": 0,
            "rawExcerpt": "<!DOCTYPE html><html lang=\"en\"> <head><meta charset=\"UTF-8\"><meta name=\"viewport\" content=\"width=device-width, initial-scale=1.0\"><link rel=\"icon\" type=\"image/svg+xml\" href=\"/favicon.svg\"><link rel=\"apple-touch-icon\" href=\"/favicon-260.png\"><link rel=\"canonical\" href=\"https://www.enigma.com/404/\"><title>Not Found | Enigma</title><meta name=\"title\" content=\"Not Found | Enigma\"><meta name=\"description\" content=\"Not Found\"><meta name=\"robots\" content=\"noindex, nofollow\"><meta property=\"og:type\" content=\"website\"><meta property=\"og:url\" content=\"https://www.enigma.com/404/\"><meta property=\"og:title\" content=\"Not Found | Enigma\"><meta property=\"og:description\" content=\"Not Found\"><meta property=\"og:image\" content=\"https://www.enigma.com/og/default.png\"><meta property=\"twitter:card\" content=\"sum"
          },
          {
            "path": "/api/openapi.json",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "valid": false,
            "issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html; charset=utf-8\" is not a recognized type; unsupported version: ; missing info block with title and version; missing paths block; no operations found.",
            "compatibleContentType": false,
            "format": "yaml",
            "version": "",
            "pathCount": 0,
            "operationCount": 0,
            "rawExcerpt": "<!DOCTYPE html><html lang=\"en\"> <head><meta charset=\"UTF-8\"><meta name=\"viewport\" content=\"width=device-width, initial-scale=1.0\"><link rel=\"icon\" type=\"image/svg+xml\" href=\"/favicon.svg\"><link rel=\"apple-touch-icon\" href=\"/favicon-260.png\"><link rel=\"canonical\" href=\"https://www.enigma.com/404/\"><title>Not Found | Enigma</title><meta name=\"title\" content=\"Not Found | Enigma\"><meta name=\"description\" content=\"Not Found\"><meta name=\"robots\" content=\"noindex, nofollow\"><meta property=\"og:type\" content=\"website\"><meta property=\"og:url\" content=\"https://www.enigma.com/404/\"><meta property=\"og:title\" content=\"Not Found | Enigma\"><meta property=\"og:description\" content=\"Not Found\"><meta property=\"og:image\" content=\"https://www.enigma.com/og/default.png\"><meta property=\"twitter:card\" content=\"sum"
          },
          {
            "path": "/api/swagger.json",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "valid": false,
            "issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html; charset=utf-8\" is not a recognized type; unsupported version: ; missing info block with title and version; missing paths block; no operations found.",
            "compatibleContentType": false,
            "format": "yaml",
            "version": "",
            "pathCount": 0,
            "operationCount": 0,
            "rawExcerpt": "<!DOCTYPE html><html lang=\"en\"> <head><meta charset=\"UTF-8\"><meta name=\"viewport\" content=\"width=device-width, initial-scale=1.0\"><link rel=\"icon\" type=\"image/svg+xml\" href=\"/favicon.svg\"><link rel=\"apple-touch-icon\" href=\"/favicon-260.png\"><link rel=\"canonical\" href=\"https://www.enigma.com/404/\"><title>Not Found | Enigma</title><meta name=\"title\" content=\"Not Found | Enigma\"><meta name=\"description\" content=\"Not Found\"><meta name=\"robots\" content=\"noindex, nofollow\"><meta property=\"og:type\" content=\"website\"><meta property=\"og:url\" content=\"https://www.enigma.com/404/\"><meta property=\"og:title\" content=\"Not Found | Enigma\"><meta property=\"og:description\" content=\"Not Found\"><meta property=\"og:image\" content=\"https://www.enigma.com/og/default.png\"><meta property=\"twitter:card\" content=\"sum"
          },
          {
            "path": "/docs/openapi.json",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "valid": false,
            "issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html; charset=utf-8\" is not a recognized type; unsupported version: ; missing info block with title and version; missing paths block; no operations found.",
            "compatibleContentType": false,
            "format": "yaml",
            "version": "",
            "pathCount": 0,
            "operationCount": 0,
            "rawExcerpt": "<!DOCTYPE html><html lang=\"en\"> <head><meta charset=\"UTF-8\"><meta name=\"viewport\" content=\"width=device-width, initial-scale=1.0\"><link rel=\"icon\" type=\"image/svg+xml\" href=\"/favicon.svg\"><link rel=\"apple-touch-icon\" href=\"/favicon-260.png\"><link rel=\"canonical\" href=\"https://www.enigma.com/404/\"><title>Not Found | Enigma</title><meta name=\"title\" content=\"Not Found | Enigma\"><meta name=\"description\" content=\"Not Found\"><meta name=\"robots\" content=\"noindex, nofollow\"><meta property=\"og:type\" content=\"website\"><meta property=\"og:url\" content=\"https://www.enigma.com/404/\"><meta property=\"og:title\" content=\"Not Found | Enigma\"><meta property=\"og:description\" content=\"Not Found\"><meta property=\"og:image\" content=\"https://www.enigma.com/og/default.png\"><meta property=\"twitter:card\" content=\"sum"
          }
        ]
      },
      "issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html; charset=utf-8\" is not a recognized type; unsupported version: ; missing info block with title and version; missing paths block; no operations found.",
      "howToFix": "Publish a valid OpenAPI 3.x or Swagger 2.0 JSON/YAML document with info, paths, operations, and responses."
    }
  ]
}

AI DiscoverabilityBot Access ControlInformational

Web Bot Auth request signing

Web Bot Auth request signing failed at "Fetch to find resource".

50 Fail

Needs attention

Web Bot Auth request signing

Failed check
01

Issue

Web Bot Auth request signing was not found at the expected path.

02

Why it matters

Web Bot Auth discovery lets servers and clients find signing keys for bot identity workflows based on HTTP Message Signatures.

Check name

Web Bot Auth request signing

Score

0/100

Status

fail

Category

Bot Access Control

Maturity

Informational

Goal

Advertise HTTP Message Signatures keys when this site operates signed bot clients or supports Web Bot Auth workflows.

Result

Web Bot Auth request signing failed at "Fetch to find resource".

Validation steps

  1. Fetch to find resource

    Web Bot Auth request signing was not found at the expected path.

Evidence
{
  "failedStep": "fetch",
  "steps": [
    {
      "id": "fetch",
      "title": "Fetch to find resource",
      "status": "fail",
      "evidence": {
        "checked": [
          {
            "path": "/.well-known/http-message-signatures-directory",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "length": 38999
          }
        ]
      },
      "issue": "Web Bot Auth request signing was not found at the expected path.",
      "howToFix": "If publishing Web Bot Auth keys, return a JSON key directory with a non-empty keys array and the draft media type."
    }
  ]
}

AI DiscoverabilityContent ReadinessEstablished

Markdown negotiation

Markdown negotiation failed at "Markdown content type".

33 Fail

Needs attention

Markdown negotiation

Failed check
01

Issue

Content-Type "text/html; charset=utf-8" does not indicate Markdown when requested with Accept: text/markdown.

02

Why it matters

Markdown negotiation gives agents a cleaner representation of page content while preserving normal HTML for browsers.

Check name

Markdown negotiation

Score

0/100

Status

fail

Category

Content Readiness

Maturity

Established

Goal

Return HTML responses as markdown when agents request it.

Result

Markdown negotiation failed at "Markdown content type".

Validation steps

  1. Markdown content type

    Content-Type "text/html; charset=utf-8" does not indicate Markdown when requested with Accept: text/markdown.

  2. Vary: Accept header

    Markdown negotiation is missing Vary: Accept; current Vary header is "(none)".

  3. Structured Markdown body

    Markdown response is missing a heading.

Evidence
{
  "failedStep": "content-type",
  "steps": [
    {
      "id": "content-type",
      "title": "Markdown content type",
      "status": "fail",
      "evidence": {
        "statusCode": 200,
        "contentType": "text/html; charset=utf-8"
      },
      "issue": "Content-Type \"text/html; charset=utf-8\" does not indicate Markdown when requested with Accept: text/markdown.",
      "howToFix": "Return Content-Type: text/markdown; charset=utf-8 for requests with Accept: text/markdown."
    },
    {
      "id": "vary-accept",
      "title": "Vary: Accept header",
      "status": "fail",
      "evidence": {
        "vary": ""
      },
      "issue": "Markdown negotiation is missing Vary: Accept; current Vary header is \"(none)\".",
      "howToFix": "Add Vary: Accept on negotiated Markdown responses so shared caches keep HTML and Markdown variants separate."
    },
    {
      "id": "markdown-content",
      "title": "Structured Markdown body",
      "status": "fail",
      "evidence": {
        "valid": false,
        "hasHeading": false,
        "wordCount": 6156,
        "excerpt": "<!DOCTYPE html><html lang=\"en\"> <head><meta charset=\"UTF-8\"><meta name=\"viewport\" content=\"width=device-width, initial-scale=1.0\"><link rel=\"icon\" type=\"image/svg+xml\" href=\"/favicon.svg\"><link rel=\"apple-touch-icon\" href=\"/favicon-260.png\"",
        "issue": "Markdown response is missing a heading."
      },
      "issue": "Markdown response is missing a heading.",
      "howToFix": "Return Markdown with at least one heading and substantive page content, including useful links or instructions for agents."
    }
  ]
}

AI DiscoverabilityContent ReadinessEstablished

Semantic HTML

Semantic HTML is missing or incomplete.

33 Fail

Needs attention

Semantic HTML

Failed check
01

Issue

Semantic HTML is incomplete: skipped heading levels.

Details

02

Why it matters

Semantic HTML gives browsers, assistive technology, search systems, and agents reliable landmarks, headings, controls, form semantics, and image context.

Check name

Semantic HTML

Score

0/100

Status

fail

Category

Content Readiness

Maturity

Established

Goal

Expose readable page structure through semantic HTML and accessible controls.

Result

Semantic HTML is missing or incomplete.

Evidence
{
  "main": true,
  "nav": true,
  "footer": true,
  "meaningfulH1": true,
  "headingOrder": false,
  "accessibleLinks": true,
  "accessibleButtons": true,
  "imageAltCoverage": true,
  "formAutocompleteCoverage": true,
  "details": {
    "inaccessibleLinks": [],
    "inaccessibleButtons": [],
    "missingAutocompleteInputs": [],
    "imagesMissingAlt": [],
    "skippedHeadingLevels": [
      "h1: Trusted Entity Data",
      "h2: Enigma provides business identity infrastructure, built on unparalleled entity resolution. With Enigma's business identity graph, you can verify customers faster, surface fraud signals buried in government records, and give AI systems ground truth on every U.S. business.",
      "h6: Business Identity Infrastructure",
      "h2: The knowledge graph of every U.S. Business.",
      "h6: Streamline Business Verification with more instant approvals",
      "h2: KYB & Onboarding",
      "h6: Screen customers and transactions at scale for a fraction of the cost",
      "h2: Customer & Transaction Screening",
      "h6: Unlock True Merchant GPV",
      "h2: Ground Truth for Payments Leaders",
      "h6: Graph-Model-1",
      "h2: The Enigma Identity Graph: A Single Source of Truth for Every US Business",
      "h6: Start today",
      "h2: Explore Enigma Data"
    ]
  },
  "counts": {
    "h1": 1,
    "headings": 14,
    "links": 59,
    "inaccessibleLinks": 0,
    "buttons": 4,
    "inaccessibleButtons": 0,
    "images": 36,
    "imagesWithAlt": 36,
    "autocompleteInputs": 0,
    "inputsWithAutocomplete": 0,
    "missingAutocompleteInputs": 0
  }
}

Agent Ease of UseMCPInformational

WebMCP manifest

WebMCP manifest failed at "Fetch to find resource".

33 Fail

Needs attention

WebMCP manifest

Failed check
01

Issue

WebMCP manifest was not found at the expected path.

02

Why it matters

A WebMCP manifest advertises browser-exposed tools declaratively so agents can understand available site actions before invoking them.

Check name

WebMCP manifest

Score

0/100

Status

fail

Category

MCP

Maturity

Informational

Goal

Publish a WebMCP manifest for declarative browser tool discovery when using the draft manifest convention.

Result

WebMCP manifest failed at "Fetch to find resource".

Validation steps

  1. Fetch to find resource

    WebMCP manifest was not found at the expected path.

Evidence
{
  "failedStep": "fetch",
  "steps": [
    {
      "id": "fetch",
      "title": "Fetch to find resource",
      "status": "fail",
      "evidence": {
        "checked": [
          {
            "path": "/.well-known/webmcp.json",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "length": 38999
          },
          {
            "path": "/webmcp.json",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "length": 38999
          },
          {
            "path": "/mcp.json",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "length": 38999
          }
        ]
      },
      "issue": "WebMCP manifest was not found at the expected path.",
      "howToFix": "Keep declarative WebMCP manifest discovery informational until the manifest shape stabilizes; validate tools if you publish one."
    }
  ]
}

AI DiscoverabilityDiscoverabilityEstablished

High-value schema types

High-value schema types is missing or incomplete.

25 Fail

Needs attention

High-value schema types

Failed check
01

Issue

No high-value schema types (e.g. Article, Product, Service) were found.

02

Why it matters

High-value schema types tell agents whether a page is an article, product, event, service, or other actionable content type.

Check name

High-value schema types

Score

0/100

Status

fail

Category

Discoverability

Maturity

Established

Goal

Use schema types that describe the page's primary content or offering.

Result

High-value schema types is missing or incomplete.

Evidence
{
  "found": [],
  "expected": [
    "Article",
    "BlogPosting",
    "NewsArticle",
    "Product",
    "SoftwareApplication",
    "FAQPage",
    "LocalBusiness",
    "VideoObject",
    "HowTo",
    "Event",
    "Course",
    "Review",
    "Service"
  ],
  "allTypes": []
}

AI DiscoverabilityDiscoverabilityEstablished

JSON-LD present

JSON-LD present is missing or incomplete.

25 Fail

Needs attention

JSON-LD present

Failed check
01

Issue

No JSON-LD blocks found.

02

Why it matters

JSON-LD is a low-friction structured data format that agents can extract without interpreting page presentation or microdata markup.

Check name

JSON-LD present

Score

0/100

Status

fail

Category

Discoverability

Maturity

Established

Goal

Expose schema.org JSON-LD so AI search systems can parse page entities.

Result

JSON-LD present is missing or incomplete.

Evidence
{
  "blocks": 0,
  "validBlocks": 0,
  "schemaContextBlocks": 0,
  "errors": [],
  "documents": [],
  "nodes": []
}

AI DiscoverabilityDiscoverabilityEstablished

Link headers

Link headers failed at "Find useful Link headers".

25 Fail

Needs attention

Link headers

Failed check
01

Issue

No useful agent discovery Link headers were found.

02

Why it matters

Link headers let automated clients discover API catalogs, documentation, and machine-readable alternates without parsing page markup first.

Check name

Link headers

Score

0/100

Status

fail

Category

Discoverability

Maturity

Established

Goal

Include Link response headers for agent discovery using RFC 8288.

Result

Link headers failed at "Find useful Link headers".

Validation steps

  1. Find useful Link headers

    No useful agent discovery Link headers were found.

  2. Fetch same-origin Link header targets

    Link headers did not expose any same-origin targets to validate.

Evidence
{
  "failedStep": "presence",
  "steps": [
    {
      "id": "presence",
      "title": "Find useful Link headers",
      "status": "fail",
      "evidence": {
        "links": []
      },
      "issue": "No useful agent discovery Link headers were found.",
      "howToFix": "Expose useful Link headers such as rel=\"api-catalog\", rel=\"service-doc\", and rel=\"service-desc\"."
    },
    {
      "id": "target-validation",
      "title": "Fetch same-origin Link header targets",
      "status": "fail",
      "evidence": {
        "checked": [],
        "failures": [
          {
            "reason": "No same-origin Link header targets were available to fetch."
          }
        ]
      },
      "issue": "Link headers did not expose any same-origin targets to validate.",
      "howToFix": "Make each same-origin Link href reachable and serve the advertised media type."
    }
  ]
}

AI DiscoverabilityDiscoverabilityEstablished

Organization / WebSite schema

Organization / WebSite schema is missing or incomplete.

25 Fail

Needs attention

Organization / WebSite schema

Failed check
01

Issue

Neither Organization nor WebSite schema types were found in JSON-LD.

02

Why it matters

Organization and WebSite schema help agents identify the publisher, canonical site identity, logo, and related profiles for attribution.

Check name

Organization / WebSite schema

Score

0/100

Status

fail

Category

Discoverability

Maturity

Established

Goal

Identify the site owner and website entity in structured data.

Result

Organization / WebSite schema is missing or incomplete.

Evidence
{
  "found": [],
  "allTypes": []
}

AI DiscoverabilityContent ReadinessEstablished

Content freshness signals

Content freshness signals is partially implemented.

25 Warning

Needs attention

Content freshness signals

Warning
01

Issue

Content freshness signals are incomplete: missing dateModified/datePublished in JSON-LD; missing meta or <time> freshness tags.

02

Why it matters

Freshness signals help agents decide whether content is current enough to cite, summarize, or compare against newer sources.

Check name

Content freshness signals

Score

25/100

Status

warning

Category

Content Readiness

Maturity

Established

Goal

Expose modified and published dates for freshness-aware retrieval and ranking.

Result

Content freshness signals is partially implemented.

Evidence
{
  "lastModified": "Fri, 12 Jun 2026 14:26:24 GMT",
  "schemaDates": [],
  "metaDateCount": 0,
  "timeDateCount": 0
}

Agent Ease of UseMCPEmerging recommendation

MCP Server Card

MCP Server Card failed at "Validate resource body".

21 Fail

Needs attention

MCP Server Card

Failed check
01

Issue

MCP Server Card response is missing required fields or has invalid transports.

Details

02

Why it matters

MCP Server Cards help agents discover server transports, capabilities, and protocol details before opening an MCP session.

Check name

MCP Server Card

Score

38/100

Status

fail

Category

MCP

Maturity

Emerging recommendation

Goal

Publish an MCP Server Card for agent discovery.

Result

MCP Server Card failed at "Validate resource body".

Validation steps

  1. Validate resource body

    MCP Server Card response is missing required fields or has invalid transports.

    Missing required fields
    • serverInfo.name
    • serverInfo.version
    • protocolVersion
    • capabilities object
    • transports array
  2. Verify advertised MCP transport endpoints

    At least one same-origin transport failed MCP initialize or advertised capability list probes. See probes[].capabilityProbes for the exact method, status, JSON-RPC error, and response excerpt.

  3. Verify advertised MCP tool execution

    MCP discovery passed, but no advertised tool could be safely executed by this scanner.

Evidence
{
  "failedStep": "validate",
  "steps": [
    {
      "id": "fetch",
      "title": "Fetch discovery resource",
      "status": "pass",
      "evidence": {
        "path": "/.well-known/mcp/server-card.json",
        "statusCode": 200,
        "contentType": "application/json"
      }
    },
    {
      "id": "validate",
      "title": "Validate resource body",
      "status": "fail",
      "evidence": {
        "valid": false,
        "validJson": true,
        "compatibleContentType": true,
        "document": {
          "$schema": "https://static.modelcontextprotocol.io/schemas/2025-10-17/server.schema.json",
          "name": "com.enigma/enigma-mcp",
          "version": "1.0.0",
          "title": "Enigma MCP",
          "description": "Remote MCP server for U.S. business intelligence: entity resolution, KYB verification, sanctions and negative-news screening, card-transaction analytics, and public-records search.",
          "websiteUrl": "https://documentation.enigma.com/guides/ai-mcp",
          "remotes": [
            {
              "transport": "streamable-http",
              "url": "https://mcp.enigma.com/mcp"
            }
          ]
        },
        "rawExcerpt": "{\n  \"$schema\": \"https://static.modelcontextprotocol.io/schemas/2025-10-17/server.schema.json\",\n  \"name\": \"com.enigma/enigma-mcp\",\n  \"version\": \"1.0.0\",\n  \"title\": \"Enigma MCP\",\n  \"description\": \"Remote MCP server for U.S. business intelligence: entity resolution, KYB verification, sanctions and negative-news screening, card-transaction analytics, and public-records search.\",\n  \"websiteUrl\": \"https://documentation.enigma.com/guides/ai-mcp\",\n  \"remotes\": [\n    {\n      \"transport\": \"streamable-http\",\n      \"url\": \"https://mcp.enigma.com/mcp\"\n    }\n  ]\n}\n",
        "issue": "MCP Server Card response is missing required fields or has invalid transports.",
        "issueDetails": [
          {
            "title": "Missing required fields",
            "items": [
              "serverInfo.name",
              "serverInfo.version",
              "protocolVersion",
              "capabilities object",
              "transports array"
            ]
          }
        ],
        "missing": [
          "serverInfo.name",
          "serverInfo.version",
          "protocolVersion",
          "capabilities object",
          "transports array"
        ],
        "protocolVersion": "",
        "transportCount": 0,
        "transports": [],
        "invalidTransports": [],
        "capabilityKeys": []
      },
      "issue": "MCP Server Card response is missing required fields or has invalid transports.",
      "howToFix": "Publish an MCP server card with valid transports and make each advertised local endpoint answer an MCP initialize request.",
      "issueDetails": [
        {
          "title": "Missing required fields",
          "items": [
            "serverInfo.name",
            "serverInfo.version",
            "protocolVersion",
            "capabilities object",
            "transports array"
          ]
        }
      ]
    },
    {
      "id": "endpoint-verification",
      "title": "Verify advertised MCP transport endpoints",
      "status": "fail",
      "evidence": {
        "probes": []
      },
      "issue": "At least one same-origin transport failed MCP initialize or advertised capability list probes. See probes[].capabilityProbes for the exact method, status, JSON-RPC error, and response excerpt.",
      "howToFix": "Expose a real MCP endpoint for advertised transports, or remove transports that point to ordinary HTTP APIs."
    },
    {
      "id": "tool-execution",
      "title": "Verify advertised MCP tool execution",
      "status": "warning",
      "evidence": {
        "probes": []
      },
      "issue": "MCP discovery passed, but no advertised tool could be safely executed by this scanner.",
      "howToFix": "Implement tools/call for advertised tools, or report the MCP card as discovery-only until tools are executable."
    }
  ]
}

Agent Ease of UseSkill DiscoveryEmerging recommendation

A2A Agent Card

A2A Agent Card failed at "Fetch to find resource".

20 Fail

Needs attention

A2A Agent Card

Failed check
01

Issue

A2A Agent Card was not found at the expected path.

02

Why it matters

A2A Agent Cards let compatible clients discover agent skills, input and output modes, and the endpoint used to invoke those skills.

Check name

A2A Agent Card

Score

0/100

Status

fail

Category

Skill Discovery

Maturity

Emerging recommendation

Goal

Publish an agent card so A2A-compatible clients can discover capabilities.

Result

A2A Agent Card failed at "Fetch to find resource".

Validation steps

  1. Fetch to find resource

    A2A Agent Card was not found at the expected path.

Evidence
{
  "failedStep": "fetch",
  "steps": [
    {
      "id": "fetch",
      "title": "Fetch to find resource",
      "status": "fail",
      "evidence": {
        "checked": [
          {
            "path": "/.well-known/agent-card.json",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "length": 38999
          },
          {
            "path": "/.well-known/a2a/agent-card.json",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "length": 38999
          },
          {
            "path": "/agent-card.json",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "length": 38999
          }
        ]
      },
      "issue": "A2A Agent Card was not found at the expected path.",
      "howToFix": "Publish an A2A Agent Card with required skill details and make the advertised url answer A2A JSON-RPC requests."
    }
  ]
}

Agent Ease of UseSkill DiscoveryEmerging recommendation

agent.json

agent.json failed at "Fetch to find resource".

20 Fail

Needs attention

agent.json

Failed check
01

Issue

agent.json was not found at the expected path.

02

Why it matters

agent.json is an emerging machine-readable manifest for declaring what a website does, how agents authenticate, and which actions or protocols are available.

Check name

agent.json

Score

0/100

Status

fail

Category

Skill Discovery

Maturity

Emerging recommendation

Goal

Publish the singular Agent Web Protocol agent.json manifest without confusing it with the separate agents.json directory convention.

Result

agent.json failed at "Fetch to find resource".

Validation steps

  1. Fetch to find resource

    agent.json was not found at the expected path.

Evidence
{
  "failedStep": "fetch",
  "steps": [
    {
      "id": "fetch",
      "title": "Fetch to find resource",
      "status": "fail",
      "evidence": {
        "checked": [
          {
            "path": "/.well-known/agent.json",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "length": 38999
          },
          {
            "path": "/agent.json",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "length": 38999
          }
        ]
      },
      "issue": "agent.json was not found at the expected path.",
      "howToFix": "Publish agent.json with awp_version, domain, intent, and typed actions that point to real same-origin API or protocol endpoints."
    }
  ]
}

Agent Ease of UseSkill DiscoveryInformational

agents.json

agents.json failed at "Fetch to find resource".

20 Fail

Needs attention

agents.json

Failed check
01

Issue

agents.json was not found at the expected path.

02

Why it matters

agents.json gives clients a simple directory of agent-facing capabilities and contacts when a site chooses to advertise them.

Check name

agents.json

Score

0/100

Status

fail

Category

Skill Discovery

Maturity

Informational

Goal

Publish an agents.json directory for agent-facing capabilities and contacts when using this convention.

Result

agents.json failed at "Fetch to find resource".

Validation steps

  1. Fetch to find resource

    agents.json was not found at the expected path.

Evidence
{
  "failedStep": "fetch",
  "steps": [
    {
      "id": "fetch",
      "title": "Fetch to find resource",
      "status": "fail",
      "evidence": {
        "checked": [
          {
            "path": "/.well-known/agents.json",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "length": 38999
          },
          {
            "path": "/agents.json",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "length": 38999
          }
        ]
      },
      "issue": "agents.json was not found at the expected path.",
      "howToFix": "If this site uses agents.json, publish JSON with an agents array containing name and url for each agent."
    }
  ]
}

Agent Ease of UseMCPEmerging recommendation

mcp.json

mcp.json failed at "Validate resource body".

17 Fail

Needs attention

mcp.json

Failed check
01

Issue

mcp.json response did not match the expected MCP server metadata shape. missing: serverInfo.name, protocolVersion, capabilities object, transport or transports.

Details

02

Why it matters

MCP clients need trustworthy server metadata, protocol version, transport details, and capability hints before connecting to a remote MCP server.

Check name

mcp.json

Score

50/100

Status

fail

Category

MCP

Maturity

Emerging recommendation

Goal

Expose a stable MCP server metadata document that points agents to the site's MCP endpoint.

Result

mcp.json failed at "Validate resource body".

Validation steps

  1. Validate resource body

    mcp.json response did not match the expected MCP server metadata shape. missing: serverInfo.name, protocolVersion, capabilities object, transport or transports.

    Missing required fields
    • serverInfo.name
    • protocolVersion
    • capabilities object
    • transport or transports
Evidence
{
  "failedStep": "validate",
  "steps": [
    {
      "id": "fetch",
      "title": "Fetch discovery resource",
      "status": "pass",
      "evidence": {
        "path": "/.well-known/mcp/server-card.json",
        "statusCode": 200,
        "contentType": "application/json"
      }
    },
    {
      "id": "validate",
      "title": "Validate resource body",
      "status": "fail",
      "evidence": {
        "valid": false,
        "validJson": true,
        "compatibleContentType": true,
        "document": {
          "$schema": "https://static.modelcontextprotocol.io/schemas/2025-10-17/server.schema.json",
          "name": "com.enigma/enigma-mcp",
          "version": "1.0.0",
          "title": "Enigma MCP",
          "description": "Remote MCP server for U.S. business intelligence: entity resolution, KYB verification, sanctions and negative-news screening, card-transaction analytics, and public-records search.",
          "websiteUrl": "https://documentation.enigma.com/guides/ai-mcp",
          "remotes": [
            {
              "transport": "streamable-http",
              "url": "https://mcp.enigma.com/mcp"
            }
          ]
        },
        "rawExcerpt": "{\n  \"$schema\": \"https://static.modelcontextprotocol.io/schemas/2025-10-17/server.schema.json\",\n  \"name\": \"com.enigma/enigma-mcp\",\n  \"version\": \"1.0.0\",\n  \"title\": \"Enigma MCP\",\n  \"description\": \"Remote MCP server for U.S. business intelligence: entity resolution, KYB verification, sanctions and negative-news screening, card-transaction analytics, and public-records search.\",\n  \"websiteUrl\": \"https://documentation.enigma.com/guides/ai-mcp\",\n  \"remotes\": [\n    {\n      \"transport\": \"streamable-http\",\n      \"url\": \"https://mcp.enigma.com/mcp\"\n    }\n  ]\n}\n",
        "issue": "mcp.json response did not match the expected MCP server metadata shape. missing: serverInfo.name, protocolVersion, capabilities object, transport or transports.",
        "issueDetails": [
          {
            "title": "Missing required fields",
            "items": [
              "serverInfo.name",
              "protocolVersion",
              "capabilities object",
              "transport or transports"
            ]
          }
        ],
        "missing": [
          "serverInfo.name",
          "protocolVersion",
          "capabilities object",
          "transport or transports"
        ],
        "protocolVersion": "",
        "transportCount": 0,
        "transports": [],
        "invalidTransports": [],
        "toolCount": 0,
        "capabilityKeys": []
      },
      "issue": "mcp.json response did not match the expected MCP server metadata shape. missing: serverInfo.name, protocolVersion, capabilities object, transport or transports.",
      "howToFix": "Publish mcp.json or an MCP server card with serverInfo, protocolVersion, transport endpoint, and capabilities.",
      "issueDetails": [
        {
          "title": "Missing required fields",
          "items": [
            "serverInfo.name",
            "protocolVersion",
            "capabilities object",
            "transport or transports"
          ]
        }
      ]
    }
  ]
}

Agent Ease of UseSkill DiscoveryEmerging recommendation

DNS-AID Agent Discovery

DNS-AID Agent Discovery failed at "Resolve DNS-AID SVCB/HTTPS records".

15 Fail

Needs attention

DNS-AID Agent Discovery

Failed check
01

Issue

No DNS-AID entrypoint records were found under _agents.

02

Why it matters

DNS-AID lets agents discover index, A2A, and other agent entrypoints before fetching HTTP metadata, while DNSSEC can authenticate the discovery zone.

Check name

DNS-AID Agent Discovery

Score

25/100

Status

fail

Category

Skill Discovery

Maturity

Emerging recommendation

Goal

Publish DNS for AI Discovery records under _agents for DNS-based agent entrypoint discovery.

Result

DNS-AID Agent Discovery failed at "Resolve DNS-AID SVCB/HTTPS records".

Validation steps

  1. Resolve DNS-AID SVCB/HTTPS records

    No DNS-AID entrypoint records were found under _agents.

  2. Validate alpn and endpoint parameters

    Include alpn and endpoint service parameters in each DNS-AID record so agents know the protocol and target entrypoint.

  3. Check DNSSEC material

    DNSSEC material was not visible for the hostname or parent zone from this resolver.

Evidence
{
  "failedStep": "svcb-https-records",
  "steps": [
    {
      "id": "svcb-https-records",
      "title": "Resolve DNS-AID SVCB/HTTPS records",
      "status": "fail",
      "evidence": {
        "hostname": "enigma.com",
        "probes": [
          {
            "name": "_index._agents.enigma.com",
            "found": false,
            "recordCount": 1,
            "records": [],
            "hasAlpn": false,
            "hasEndpoint": false
          },
          {
            "name": "_a2a._agents.enigma.com",
            "found": false,
            "recordCount": 1,
            "records": [],
            "hasAlpn": false,
            "hasEndpoint": false
          }
        ]
      },
      "issue": "No DNS-AID entrypoint records were found under _agents.",
      "howToFix": "Publish ServiceMode SVCB/HTTPS records such as _index._agents.example.com or _a2a._agents.example.com."
    },
    {
      "id": "service-params",
      "title": "Validate alpn and endpoint parameters",
      "status": "informational",
      "evidence": {
        "discovered": []
      },
      "howToFix": "Include alpn and endpoint service parameters in each DNS-AID record so agents know the protocol and target entrypoint."
    },
    {
      "id": "dnssec",
      "title": "Check DNSSEC material",
      "status": "warning",
      "evidence": {
        "hasDnssecMaterial": false,
        "checked": [
          {
            "name": "enigma.com",
            "dnssecTypes": [],
            "dnssecRecordCount": 0
          }
        ]
      },
      "issue": "DNSSEC material was not visible for the hostname or parent zone from this resolver.",
      "howToFix": "Sign the public discovery zone with DNSSEC so validating resolvers can return authenticated data."
    }
  ]
}

Agent Ease of UseSkill DiscoveryEmerging recommendation

Agent Skills index

Agent Skills index failed at "Validate resource body".

13 Fail

Needs attention

Agent Skills index

Failed check
01

Issue

Agent Skills Index response did not match the expected shape. missing or invalid top-level fields: version=0.2.0.

02

Why it matters

An Agent Skills index lets clients find task-specific SKILL.md documents that describe how to use site capabilities correctly.

Check name

Agent Skills index

Score

33/100

Status

fail

Category

Skill Discovery

Maturity

Emerging recommendation

Goal

Publish an agent skills discovery index.

Result

Agent Skills index failed at "Validate resource body".

Validation steps

  1. Validate resource body

    Agent Skills Index response did not match the expected shape. missing or invalid top-level fields: version=0.2.0.

  2. Fetch advertised SKILL.md files

    One or more advertised skill URLs were missing, did not look like SKILL.md Markdown, or failed digest verification.

Evidence
{
  "failedStep": "validate",
  "steps": [
    {
      "id": "fetch",
      "title": "Fetch discovery resource",
      "status": "pass",
      "evidence": {
        "path": "/.well-known/agent-skills/index.json",
        "statusCode": 200,
        "contentType": "application/json"
      }
    },
    {
      "id": "validate",
      "title": "Validate resource body",
      "status": "fail",
      "evidence": {
        "valid": false,
        "validJson": true,
        "compatibleContentType": true,
        "document": {
          "$schema": "https://schemas.agentskills.io/discovery/0.2.0/schema.json",
          "skills": [
            {
              "name": "enigma-graphql",
              "type": "archive",
              "description": "Search and discover businesses using the Enigma GraphQL API. Use when the user wants to find/search/discover/list businesses (by name, industry, location, or characteristics), look up a specific company, search for people or business owners, analyze market segments (e.g., \"coffee shops in California\", \"restaurants in New York\"), find businesses by criteria (revenue, operating status, has/lacks phone/email, technology used), verify legal entities, check corporate structure, or explore the Enigma business intelligence graph. Handles both entity resolution (known business names like \"Starbucks\") and semantic discovery (industry/type-based search like \"coffee shops\" or \"auto repair\"). This is the primary skill for ALL Enigma business data lookups and market research queries.",
              "url": "/.well-known/agent-skills/enigma-graphql.tar.gz",
              "digest": "sha256:eeec92a39cd6ff40dd22d4f9de1effdb8481414a0a3bae28cf645faeaec43ecd"
            },
            {
              "name": "enigma-kyb",
              "type": "skill-md",
              "description": "Verify businesses using the Enigma KYB (Know Your Business) API. Use when the user wants to verify a business identity, check registration status, screen officers, or perform KYB due diligence.",
              "url": "/.well-known/agent-skills/enigma-kyb/SKILL.md",
              "digest": "sha256:3572edd531f4c7f9f3bd47729d60a4d5bae3a7f6d869c408bf62af4e2161aecd"
            },
            {
              "name": "enigma-screen",
              "type": "skill-md",
              "description": "Screen persons and organizations against sanctions and PEP lists using the Enigma Screen API. Use ONLY when the user explicitly asks for compliance screening, sanctions checks, watchlist checks, or PEP screening — NOT for general person/business search or lookup.",
              "url": "/.well-known/agent-skills/enigma-screen/SKILL.md",
              "digest": "sha256:d062c501ba54ecef65f1686d3077e49b04bdca2c4519f1a60dd88559bbf206ac"
            }
          ]
        },
        "rawExcerpt": "{\n  \"$schema\": \"https://schemas.agentskills.io/discovery/0.2.0/schema.json\",\n  \"skills\": [\n    {\n      \"name\": \"enigma-graphql\",\n      \"type\": \"archive\",\n      \"description\": \"Search and discover businesses using the Enigma GraphQL API. Use when the user wants to find/search/discover/list businesses (by name, industry, location, or characteristics), look up a specific company, search for people or business owners, analyze market segments (e.g., \\\"coffee shops in California\\\", \\\"restaurants in New York\\\"), find businesses by criteria (revenue, operating status, has/lacks phone/email, technology used), verify legal entities, check corporate structure, or explore the Enigma business intelligence graph. Handles both entity resolution (known business names like \\\"Starbucks\\\") and semantic disco",
        "issue": "Agent Skills Index response did not match the expected shape. missing or invalid top-level fields: version=0.2.0.",
        "schema": "https://schemas.agentskills.io/discovery/0.2.0/schema.json",
        "skillCount": 3,
        "validSkillCount": 3,
        "invalidSkills": [],
        "skills": [
          {
            "name": "enigma-graphql",
            "type": "archive",
            "description": "Search and discover businesses using the Enigma GraphQL API. Use when the user wants to find/search/discover/list businesses (by name, industry, location, or characteristics), look up a specific company, search for people or business owners, analyze market segments (e.g., \"coffee shops in California\", \"restaurants in New York\"), find businesses by criteria (revenue, operating status, has/lacks phone/email, technology used), verify legal entities, check corporate structure, or explore the Enigma business intelligence graph. Handles both entity resolution (known business names like \"Starbucks\") and semantic discovery (industry/type-based search like \"coffee shops\" or \"auto repair\"). This is the primary skill for ALL Enigma business data lookups and market research queries.",
            "url": "/.well-known/agent-skills/enigma-graphql.tar.gz",
            "digest": "sha256:eeec92a39cd6ff40dd22d4f9de1effdb8481414a0a3bae28cf645faeaec43ecd"
          },
          {
            "name": "enigma-kyb",
            "type": "skill-md",
            "description": "Verify businesses using the Enigma KYB (Know Your Business) API. Use when the user wants to verify a business identity, check registration status, screen officers, or perform KYB due diligence.",
            "url": "/.well-known/agent-skills/enigma-kyb/SKILL.md",
            "digest": "sha256:3572edd531f4c7f9f3bd47729d60a4d5bae3a7f6d869c408bf62af4e2161aecd"
          },
          {
            "name": "enigma-screen",
            "type": "skill-md",
            "description": "Screen persons and organizations against sanctions and PEP lists using the Enigma Screen API. Use ONLY when the user explicitly asks for compliance screening, sanctions checks, watchlist checks, or PEP screening — NOT for general person/business search or lookup.",
            "url": "/.well-known/agent-skills/enigma-screen/SKILL.md",
            "digest": "sha256:d062c501ba54ecef65f1686d3077e49b04bdca2c4519f1a60dd88559bbf206ac"
          }
        ]
      },
      "issue": "Agent Skills Index response did not match the expected shape. missing or invalid top-level fields: version=0.2.0.",
      "howToFix": "Publish an index with a non-empty skills array and reachable SKILL.md URLs."
    },
    {
      "id": "skill-documents",
      "title": "Fetch advertised SKILL.md files",
      "status": "fail",
      "evidence": {
        "checkedCount": 3,
        "totalCount": 3,
        "checked": [
          {
            "url": "https://enigma.com/.well-known/agent-skills/enigma-graphql.tar.gz",
            "statusCode": 200,
            "contentType": "application/x-tar",
            "hasSkillHeading": false,
            "length": 38436,
            "advertisedDigest": "sha256:eeec92a39cd6ff40dd22d4f9de1effdb8481414a0a3bae28cf645faeaec43ecd",
            "actualDigest": "sha256:6822cb9be58a79730b913eece0c44f1c16fd09ba506aa604282488a2a7dfb759",
            "digestMatches": false
          },
          {
            "url": "https://enigma.com/.well-known/agent-skills/enigma-kyb/SKILL.md",
            "statusCode": 200,
            "contentType": "text/markdown",
            "hasSkillHeading": true,
            "length": 14657,
            "advertisedDigest": "sha256:3572edd531f4c7f9f3bd47729d60a4d5bae3a7f6d869c408bf62af4e2161aecd",
            "actualDigest": "sha256:3572edd531f4c7f9f3bd47729d60a4d5bae3a7f6d869c408bf62af4e2161aecd",
            "digestMatches": true
          },
          {
            "url": "https://enigma.com/.well-known/agent-skills/enigma-screen/SKILL.md",
            "statusCode": 200,
            "contentType": "text/markdown",
            "hasSkillHeading": true,
            "length": 10697,
            "advertisedDigest": "sha256:d062c501ba54ecef65f1686d3077e49b04bdca2c4519f1a60dd88559bbf206ac",
            "actualDigest": "sha256:d062c501ba54ecef65f1686d3077e49b04bdca2c4519f1a60dd88559bbf206ac",
            "digestMatches": true
          }
        ]
      },
      "issue": "One or more advertised skill URLs were missing, did not look like SKILL.md Markdown, or failed digest verification.",
      "howToFix": "Make every advertised skill URL return Markdown with a top-level heading and a matching sha256 digest, or remove broken entries from the index."
    }
  ]
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AIO: Visible structured data match

AIO: Visible structured data match scored 0/100 and needs a fix.

7 Fail

Needs attention

AIO: Visible structured data match

Failed check
01

Issue

No JSON-LD structured data was detected.

Details

02

Why it matters

AI Overviews depend on Google-search eligibility, useful visible content, consistent structured data, answer-first sections, trust signals, and preview controls that permit snippets.

Check name

AIO: Visible structured data match

Score

0/100

Status

fail

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content eligible and useful for Google AI Overviews and AI Mode extraction.

Result

AIO: Visible structured data match scored 0/100 and needs a fix.

Evidence
{
  "schemaCount": 0,
  "mismatches": [],
  "score": 0,
  "weight": 18
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Answer evidence and trust

AEO: Answer evidence and trust scored 40/100 and needs a fix.

5 Fail

Needs attention

AEO: Answer evidence and trust

Failed check
01

Issue

Missing AIO trust signals: author, publisher, freshnessDate.

Details

02

Why it matters

Answer engines need concise answers, question-led structure, entity clarity, visible evidence, and trust signals that can be extracted without relying on search-only metadata checks.

Check name

AEO: Answer evidence and trust

Score

40/100

Status

fail

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content easy for answer engines and assistants to answer from directly.

Result

AEO: Answer evidence and trust scored 40/100 and needs a fix.

Evidence
{
  "signals": {
    "author": false,
    "publisher": false,
    "freshnessDate": false,
    "aboutOrContact": true,
    "policyLinks": true
  },
  "missing": [
    "author",
    "publisher",
    "freshnessDate"
  ],
  "authorMeta": "",
  "schemaAuthors": [],
  "schemaPublishers": [],
  "schemaDates": [],
  "visibleDates": [],
  "aboutLinks": [
    {
      "href": "/company/about-us",
      "text": "About Us",
      "html": "<a href=\"/company/about-us\" class=\"footer-list-item\" data-astro-cid-cmhnwpac>About Us</a>"
    },
    {
      "href": "/company/support",
      "text": "Support",
      "html": "<a href=\"/company/support\" class=\"footer-list-item\" data-astro-cid-cmhnwpac>Support</a>"
    },
    {
      "href": "https://www.linkedin.com/company/enigma-technologies-inc-/",
      "text": "",
      "html": "<a href=\"https://www.linkedin.com/company/enigma-technologies-inc-/\" target=\"_blank\" rel=\"noopener\" class=\"footer-social-link\" aria-label=\"Enigma on LinkedIn\" data-astro-cid-cmhnwpac> <img src=\"/images/home/linkedin_1.svg\" alt=\"Enigma LinkedIn Link\" class=\"footer-social-icon\" data-astro-cid-cmhnwpac> </a>"
    }
  ],
  "contactLinks": [
    {
      "href": "/contact-us",
      "text": "Contact Us",
      "html": "<a class=\"btn-secondary\" href=\"/contact-us\" data-astro-cid-yikpzsy5>Contact Us</a>"
    },
    {
      "href": "/contact-us",
      "text": "Request a Demo →",
      "html": "<a class=\"btn-secondary\" href=\"/contact-us\" data-astro-cid-j7pv25f6> Request a Demo <span class=\"btn-arrow\" aria-hidden=\"true\" data-astro-cid-j7pv25f6>&#x2192;</span> </a>"
    },
    {
      "href": "/contact-us",
      "text": "Contact Us",
      "html": "<a href=\"/contact-us\" class=\"footer-list-item\" data-astro-cid-cmhnwpac>Contact Us</a>"
    },
    {
      "href": "/company/support",
      "text": "Support",
      "html": "<a href=\"/company/support\" class=\"footer-list-item\" data-astro-cid-cmhnwpac>Support</a>"
    }
  ],
  "privacyLinks": [
    {
      "href": "/legal/privacy-policy",
      "text": "Privacy Policy",
      "html": "<a href=\"/legal/privacy-policy\" class=\"footer-list-item\" data-astro-cid-cmhnwpac> Privacy Policy </a>"
    },
    {
      "href": "/legal/terms-of-service",
      "text": "Terms of Service",
      "html": "<a href=\"/legal/terms-of-service\" class=\"footer-list-item\" data-astro-cid-cmhnwpac> Terms of Service </a>"
    }
  ],
  "score": 40,
  "weight": 22
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AIO: Source and trust signals

AIO: Source and trust signals scored 40/100 and needs a fix.

5 Fail

Needs attention

AIO: Source and trust signals

Failed check
01

Issue

Missing AIO trust signals: author, publisher, freshnessDate.

Details

02

Why it matters

AI Overviews depend on Google-search eligibility, useful visible content, consistent structured data, answer-first sections, trust signals, and preview controls that permit snippets.

Check name

AIO: Source and trust signals

Score

40/100

Status

fail

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content eligible and useful for Google AI Overviews and AI Mode extraction.

Result

AIO: Source and trust signals scored 40/100 and needs a fix.

Evidence
{
  "signals": {
    "author": false,
    "publisher": false,
    "freshnessDate": false,
    "aboutOrContact": true,
    "policyLinks": true
  },
  "missing": [
    "author",
    "publisher",
    "freshnessDate"
  ],
  "authorMeta": "",
  "schemaAuthors": [],
  "schemaPublishers": [],
  "schemaDates": [],
  "visibleDates": [],
  "aboutLinks": [
    {
      "href": "/company/about-us",
      "text": "About Us",
      "html": "<a href=\"/company/about-us\" class=\"footer-list-item\" data-astro-cid-cmhnwpac>About Us</a>"
    },
    {
      "href": "/company/support",
      "text": "Support",
      "html": "<a href=\"/company/support\" class=\"footer-list-item\" data-astro-cid-cmhnwpac>Support</a>"
    },
    {
      "href": "https://www.linkedin.com/company/enigma-technologies-inc-/",
      "text": "",
      "html": "<a href=\"https://www.linkedin.com/company/enigma-technologies-inc-/\" target=\"_blank\" rel=\"noopener\" class=\"footer-social-link\" aria-label=\"Enigma on LinkedIn\" data-astro-cid-cmhnwpac> <img src=\"/images/home/linkedin_1.svg\" alt=\"Enigma LinkedIn Link\" class=\"footer-social-icon\" data-astro-cid-cmhnwpac> </a>"
    }
  ],
  "contactLinks": [
    {
      "href": "/contact-us",
      "text": "Contact Us",
      "html": "<a class=\"btn-secondary\" href=\"/contact-us\" data-astro-cid-yikpzsy5>Contact Us</a>"
    },
    {
      "href": "/contact-us",
      "text": "Request a Demo →",
      "html": "<a class=\"btn-secondary\" href=\"/contact-us\" data-astro-cid-j7pv25f6> Request a Demo <span class=\"btn-arrow\" aria-hidden=\"true\" data-astro-cid-j7pv25f6>&#x2192;</span> </a>"
    },
    {
      "href": "/contact-us",
      "text": "Contact Us",
      "html": "<a href=\"/contact-us\" class=\"footer-list-item\" data-astro-cid-cmhnwpac>Contact Us</a>"
    },
    {
      "href": "/company/support",
      "text": "Support",
      "html": "<a href=\"/company/support\" class=\"footer-list-item\" data-astro-cid-cmhnwpac>Support</a>"
    }
  ],
  "privacyLinks": [
    {
      "href": "/legal/privacy-policy",
      "text": "Privacy Policy",
      "html": "<a href=\"/legal/privacy-policy\" class=\"footer-list-item\" data-astro-cid-cmhnwpac> Privacy Policy </a>"
    },
    {
      "href": "/legal/terms-of-service",
      "text": "Terms of Service",
      "html": "<a href=\"/legal/terms-of-service\" class=\"footer-list-item\" data-astro-cid-cmhnwpac> Terms of Service </a>"
    }
  ],
  "score": 40,
  "weight": 20
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

GEO: Extraction-friendly structure

GEO: Extraction-friendly structure scored 60/100 and needs improvement.

5 Warning

Needs attention

GEO: Extraction-friendly structure

Warning
01

Issue

Missing extraction signals: optional top summary / TL;DR / key takeaways block, table with <thead> only if the page already has tabular/comparative data, ordered list only if the page explains a workflow/process, optional visible FAQ or FAQPage schema, JSON-LD structured data.

Details

02

Why it matters

Generative engines favor pages with self-contained answer passages, clear entities, structured data, summaries, FAQ patterns, and crawler-accessible HTML that can be cited without extra interpretation.

Check name

GEO: Extraction-friendly structure

Score

60/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content easy for AI answer engines to extract, cite, and attribute.

Result

GEO: Extraction-friendly structure scored 60/100 and needs improvement.

Evidence
{
  "hasSummary": false,
  "tableCount": 0,
  "tablesWithHead": 0,
  "tablesMissingThead": [],
  "orderedLists": 0,
  "hasFaq": false,
  "definitionPatterns": 3,
  "schemaBlocks": 0,
  "missingSignals": [
    "optional top summary / TL;DR / key takeaways block",
    "table with <thead> only if the page already has tabular/comparative data",
    "ordered list only if the page explains a workflow/process",
    "optional visible FAQ or FAQPage schema",
    "JSON-LD structured data"
  ],
  "score": 60,
  "weight": 24
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Answer-first sections

AEO: Answer-first sections scored 65/100 and needs improvement.

4 Warning

Needs attention

AEO: Answer-first sections

Warning
01

Issue

7 section(s) may benefit from a clearer opening answer; this is optional for feature/card sections.

Details

02

Why it matters

Answer engines need concise answers, question-led structure, entity clarity, visible evidence, and trust signals that can be extracted without relying on search-only metadata checks.

Check name

AEO: Answer-first sections

Score

65/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content easy for answer engines and assistants to answer from directly.

Result

AEO: Answer-first sections scored 65/100 and needs improvement.

Evidence
{
  "sectionCount": 7,
  "passing": 0,
  "failing": [
    {
      "heading": "Enigma provides business identity infrastructure, built on unparalleled entity resolution. With Enigma's business identity graph, you can verify customers faster, surface fraud signals buried in government records, and give AI systems ground truth on every U.S. business.",
      "headingHtml": "<h2 class=\"home-hero-subhead\" data-astro-cid-f2t6dg3d> Enigma provides business identity infrastructure, built on unparalleled entity resolution. With Enigma&apos;s business identity graph, you can verify customers faster, surface fraud signals buried in government records, and give AI systems ground truth on every U.S. business. </h2>",
      "firstParagraph": "",
      "paragraphHtml": "",
      "words": 0,
      "direct": false,
      "issue": "No paragraph follows this heading."
    },
    {
      "heading": "The knowledge graph of every U.S. Business.",
      "headingHtml": "<h2 class=\"subheader-headline purple\" data-astro-cid-j7pv25f6> The knowledge graph of every U.S. Business. </h2>",
      "firstParagraph": "Public, private, large, small. Every U.S. business linked to its legal entities, operating locations, ownership, and government record. 100M+ registrations, 30M+ brands, 2B+ relationships, resolved before the query.",
      "paragraphHtml": "<p class=\"subheader-text\" data-astro-cid-j7pv25f6> Public, private, large, small. Every U.S. business linked to its legal entities, operating locations, ownership, and government record. 100M+ registrations, 30M+ brands, 2B+ relationships, resolved before the query. </p>",
      "words": 29,
      "direct": false,
      "issue": "First paragraph is 29 words and does not look like a concise direct answer."
    },
    {
      "heading": "KYB & Onboarding",
      "headingHtml": "<h2 class=\"subheader-headline purple\" data-astro-cid-j7pv25f6>KYB &amp; Onboarding</h2>",
      "firstParagraph": "Cut operational overhead",
      "paragraphHtml": "<p class=\"feature-header\" data-astro-cid-j7pv25f6> <strong data-astro-cid-j7pv25f6>Cut operational overhead</strong> </p>",
      "words": 3,
      "direct": false,
      "issue": "First paragraph is 3 words and does not look like a concise direct answer."
    },
    {
      "heading": "Customer & Transaction Screening",
      "headingHtml": "<h2 class=\"subheader-headline purple\" data-astro-cid-j7pv25f6> Customer &amp; Transaction Screening </h2>",
      "firstParagraph": "Meet your sanctions screening requirements confidently and cost effectively",
      "paragraphHtml": "<p class=\"feature-header\" data-astro-cid-j7pv25f6> <strong data-astro-cid-j7pv25f6> Meet your sanctions screening requirements confidently and cost effectively </strong> </p>",
      "words": 9,
      "direct": false,
      "issue": "First paragraph is 9 words and does not look like a concise direct answer."
    },
    {
      "heading": "Ground Truth for Payments Leaders",
      "headingHtml": "<h2 class=\"subheader-headline purple\" data-astro-cid-j7pv25f6> Ground Truth for Payments Leaders </h2>",
      "firstParagraph": "Maximize merchant share-of-wallet",
      "paragraphHtml": "<p class=\"feature-header\" data-astro-cid-j7pv25f6> <strong data-astro-cid-j7pv25f6>Maximize merchant share-of-wallet</strong> </p>",
      "words": 3,
      "direct": false,
      "issue": "First paragraph is 3 words and does not look like a concise direct answer."
    },
    {
      "heading": "The Enigma Identity Graph: A Single Source of Truth for Every US Business",
      "headingHtml": "<h2 class=\"subheader-headline purple\" data-astro-cid-j7pv25f6> The Enigma Identity Graph: A Single Source of Truth for Every US Business </h2>",
      "firstParagraph": "Before you can trust any data point, you must trust the business it's attached to. Our Identity Graph solves the chaotic problem of business identity by connecting every brand, DBA, location, and legal entity to its single unified profile.",
      "paragraphHtml": "<p class=\"subheader-text\" data-astro-cid-j7pv25f6> Before you can trust any data point, you must trust the business it&apos;s attached to. Our Identity Graph solves the chaotic problem of business identity by connecting every brand, DBA, location, and legal entity to its single unified profile. </p>",
      "words": 39,
      "direct": false,
      "issue": "First paragraph is 39 words and does not look like a concise direct answer."
    },
    {
      "heading": "Explore Enigma Data",
      "headingHtml": "<h2 class=\"subheader-headline dark color\" data-astro-cid-j7pv25f6>Explore Enigma Data</h2>",
      "firstParagraph": "Access Enigma Data instantly or talk to our business data experts.",
      "paragraphHtml": "<p class=\"subheader-text dark\" data-astro-cid-j7pv25f6> Access Enigma Data instantly or talk to our business data experts. </p>",
      "words": 11,
      "direct": false,
      "issue": "First paragraph is 11 words and does not look like a concise direct answer."
    }
  ],
  "score": 65,
  "weight": 28
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Question-led structure

AEO: Question-led structure scored 50/100 and needs improvement.

3 Warning

Needs attention

AEO: Question-led structure

Warning
01

Issue

No question-led h2 sections or FAQ pattern was detected.

Details

02

Why it matters

Answer engines need concise answers, question-led structure, entity clarity, visible evidence, and trust signals that can be extracted without relying on search-only metadata checks.

Check name

AEO: Question-led structure

Score

50/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content easy for answer engines and assistants to answer from directly.

Result

AEO: Question-led structure scored 50/100 and needs improvement.

Evidence
{
  "h2Count": 7,
  "questionH2s": [],
  "hasFaq": false,
  "score": 50,
  "weight": 18
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

GEO: Entity clarity

GEO: Entity clarity scored 82/100 and needs improvement.

3 Warning

Needs attention

GEO: Entity clarity

Warning
01

Issue

Title/H1 terms missing from description: trusted, business, entity.

Details

02

Why it matters

Generative engines favor pages with self-contained answer passages, clear entities, structured data, summaries, FAQ patterns, and crawler-accessible HTML that can be cited without extra interpretation.

Check name

GEO: Entity clarity

Score

82/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content easy for AI answer engines to extract, cite, and attribute.

Result

GEO: Entity clarity scored 82/100 and needs improvement.

Evidence
{
  "title": "Enigma: Trusted business data",
  "h1": "Trusted Entity Data",
  "description": "Enigma provides the most accurate and comprehensive data on 49M+ U.S. businesses. Access deep firmographics, contacts, and exclusive card revenue data to power your GTM and risk workflows.",
  "topicOverlap": 0.4,
  "topicTerms": [
    "enigma",
    "trusted",
    "business",
    "data",
    "entity"
  ],
  "descriptionTerms": [
    "enigma",
    "provides",
    "most",
    "accurate",
    "comprehensive",
    "data",
    "49m",
    "businesses",
    "access",
    "deep",
    "firmographics",
    "contacts",
    "exclusive",
    "card",
    "revenue",
    "power",
    "gtm",
    "risk",
    "workflows"
  ],
  "missingFromDescription": [
    "trusted",
    "business",
    "entity"
  ],
  "score": 82,
  "weight": 28
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

GEO: Explanatory content depth

GEO: Explanatory content depth scored 75/100 and needs improvement.

2 Warning

Needs attention

GEO: Explanatory content depth

Warning
01

Issue

No substantial explanatory paragraphs were found.

Details

02

Why it matters

Generative engines favor pages with self-contained answer passages, clear entities, structured data, summaries, FAQ patterns, and crawler-accessible HTML that can be cited without extra interpretation.

Check name

GEO: Explanatory content depth

Score

75/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content easy for AI answer engines to extract, cite, and attribute.

Result

GEO: Explanatory content depth scored 75/100 and needs improvement.

Evidence
{
  "candidatePassages": 1,
  "citablePassages": 0,
  "failingCandidateParagraphs": [],
  "citableParagraphs": [],
  "score": 75,
  "weight": 18
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AIO: Google eligibility and indexability

AIO: Google eligibility and indexability scored 80/100 and needs improvement.

1 Warning

Needs attention

AIO: Google eligibility and indexability

Warning
01

Issue

Canonical does not self-reference the scanned page.

Details

02

Why it matters

AI Overviews depend on Google-search eligibility, useful visible content, consistent structured data, answer-first sections, trust signals, and preview controls that permit snippets.

Check name

AIO: Google eligibility and indexability

Score

80/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content eligible and useful for Google AI Overviews and AI Mode extraction.

Result

AIO: Google eligibility and indexability scored 80/100 and needs improvement.

Evidence
{
  "status": 200,
  "googlebotBlocked": false,
  "metaRobotsTags": [],
  "xRobotsTag": "",
  "canonical": "https://www.enigma.com/",
  "finalUrl": "https://enigma.com/",
  "canonicalScore": 60,
  "score": 80,
  "weight": 18
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AIO: Answer block readiness

AIO: Answer block readiness scored 65/100 and needs improvement.

1 Warning

Needs attention

AIO: Answer block readiness

Warning
01

Issue

7 section(s) may benefit from a clearer opening answer; this is optional for feature/card sections.

Details

02

Why it matters

AI Overviews depend on Google-search eligibility, useful visible content, consistent structured data, answer-first sections, trust signals, and preview controls that permit snippets.

Check name

AIO: Answer block readiness

Score

65/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content eligible and useful for Google AI Overviews and AI Mode extraction.

Result

AIO: Answer block readiness scored 65/100 and needs improvement.

Evidence
{
  "sectionCount": 7,
  "passing": 0,
  "failing": [
    {
      "heading": "Enigma provides business identity infrastructure, built on unparalleled entity resolution. With Enigma's business identity graph, you can verify customers faster, surface fraud signals buried in government records, and give AI systems ground truth on every U.S. business.",
      "headingHtml": "<h2 class=\"home-hero-subhead\" data-astro-cid-f2t6dg3d> Enigma provides business identity infrastructure, built on unparalleled entity resolution. With Enigma&apos;s business identity graph, you can verify customers faster, surface fraud signals buried in government records, and give AI systems ground truth on every U.S. business. </h2>",
      "firstParagraph": "",
      "paragraphHtml": "",
      "words": 0,
      "direct": false,
      "issue": "No paragraph follows this heading."
    },
    {
      "heading": "The knowledge graph of every U.S. Business.",
      "headingHtml": "<h2 class=\"subheader-headline purple\" data-astro-cid-j7pv25f6> The knowledge graph of every U.S. Business. </h2>",
      "firstParagraph": "Public, private, large, small. Every U.S. business linked to its legal entities, operating locations, ownership, and government record. 100M+ registrations, 30M+ brands, 2B+ relationships, resolved before the query.",
      "paragraphHtml": "<p class=\"subheader-text\" data-astro-cid-j7pv25f6> Public, private, large, small. Every U.S. business linked to its legal entities, operating locations, ownership, and government record. 100M+ registrations, 30M+ brands, 2B+ relationships, resolved before the query. </p>",
      "words": 29,
      "direct": false,
      "issue": "First paragraph is 29 words and does not look like a concise direct answer."
    },
    {
      "heading": "KYB & Onboarding",
      "headingHtml": "<h2 class=\"subheader-headline purple\" data-astro-cid-j7pv25f6>KYB &amp; Onboarding</h2>",
      "firstParagraph": "Cut operational overhead",
      "paragraphHtml": "<p class=\"feature-header\" data-astro-cid-j7pv25f6> <strong data-astro-cid-j7pv25f6>Cut operational overhead</strong> </p>",
      "words": 3,
      "direct": false,
      "issue": "First paragraph is 3 words and does not look like a concise direct answer."
    },
    {
      "heading": "Customer & Transaction Screening",
      "headingHtml": "<h2 class=\"subheader-headline purple\" data-astro-cid-j7pv25f6> Customer &amp; Transaction Screening </h2>",
      "firstParagraph": "Meet your sanctions screening requirements confidently and cost effectively",
      "paragraphHtml": "<p class=\"feature-header\" data-astro-cid-j7pv25f6> <strong data-astro-cid-j7pv25f6> Meet your sanctions screening requirements confidently and cost effectively </strong> </p>",
      "words": 9,
      "direct": false,
      "issue": "First paragraph is 9 words and does not look like a concise direct answer."
    },
    {
      "heading": "Ground Truth for Payments Leaders",
      "headingHtml": "<h2 class=\"subheader-headline purple\" data-astro-cid-j7pv25f6> Ground Truth for Payments Leaders </h2>",
      "firstParagraph": "Maximize merchant share-of-wallet",
      "paragraphHtml": "<p class=\"feature-header\" data-astro-cid-j7pv25f6> <strong data-astro-cid-j7pv25f6>Maximize merchant share-of-wallet</strong> </p>",
      "words": 3,
      "direct": false,
      "issue": "First paragraph is 3 words and does not look like a concise direct answer."
    },
    {
      "heading": "The Enigma Identity Graph: A Single Source of Truth for Every US Business",
      "headingHtml": "<h2 class=\"subheader-headline purple\" data-astro-cid-j7pv25f6> The Enigma Identity Graph: A Single Source of Truth for Every US Business </h2>",
      "firstParagraph": "Before you can trust any data point, you must trust the business it's attached to. Our Identity Graph solves the chaotic problem of business identity by connecting every brand, DBA, location, and legal entity to its single unified profile.",
      "paragraphHtml": "<p class=\"subheader-text\" data-astro-cid-j7pv25f6> Before you can trust any data point, you must trust the business it&apos;s attached to. Our Identity Graph solves the chaotic problem of business identity by connecting every brand, DBA, location, and legal entity to its single unified profile. </p>",
      "words": 39,
      "direct": false,
      "issue": "First paragraph is 39 words and does not look like a concise direct answer."
    },
    {
      "heading": "Explore Enigma Data",
      "headingHtml": "<h2 class=\"subheader-headline dark color\" data-astro-cid-j7pv25f6>Explore Enigma Data</h2>",
      "firstParagraph": "Access Enigma Data instantly or talk to our business data experts.",
      "paragraphHtml": "<p class=\"subheader-text dark\" data-astro-cid-j7pv25f6> Access Enigma Data instantly or talk to our business data experts. </p>",
      "words": 11,
      "direct": false,
      "issue": "First paragraph is 11 words and does not look like a concise direct answer."
    }
  ],
  "score": 65,
  "weight": 8
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Entity and definition clarity

AEO: Entity and definition clarity scored 85/100 and needs improvement.

1 Warning

Needs attention

AEO: Entity and definition clarity

Warning
01

Issue

Entity or definition gaps: trusted, business, entity.

Details

02

Why it matters

Answer engines need concise answers, question-led structure, entity clarity, visible evidence, and trust signals that can be extracted without relying on search-only metadata checks.

Check name

AEO: Entity and definition clarity

Score

85/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content easy for answer engines and assistants to answer from directly.

Result

AEO: Entity and definition clarity scored 85/100 and needs improvement.

Evidence
{
  "title": "Enigma: Trusted business data",
  "h1": "Trusted Entity Data",
  "description": "Enigma provides the most accurate and comprehensive data on 49M+ U.S. businesses. Access deep firmographics, contacts, and exclusive card revenue data to power your GTM and risk workflows.",
  "topicOverlap": 0.4,
  "definitionCount": 3,
  "topicTerms": [
    "enigma",
    "trusted",
    "business",
    "data",
    "entity"
  ],
  "descriptionTerms": [
    "enigma",
    "provides",
    "most",
    "accurate",
    "comprehensive",
    "data",
    "49m",
    "businesses",
    "access",
    "deep",
    "firmographics",
    "contacts",
    "exclusive",
    "card",
    "revenue",
    "power",
    "gtm",
    "risk",
    "workflows"
  ],
  "missingFromDescription": [
    "trusted",
    "business",
    "entity"
  ],
  "score": 85,
  "weight": 18
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Answer intent coverage

AEO: Answer intent coverage scored 70/100 and needs improvement.

1 Warning

Needs attention

AEO: Answer intent coverage

Warning
01

Issue

Missing likely AI Overview intent sections: what, how, benefits, cost, compare.

Details

02

Why it matters

Answer engines need concise answers, question-led structure, entity clarity, visible evidence, and trust signals that can be extracted without relying on search-only metadata checks.

Check name

AEO: Answer intent coverage

Score

70/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content easy for answer engines and assistants to answer from directly.

Result

AEO: Answer intent coverage scored 70/100 and needs improvement.

Evidence
{
  "headings": [
    {
      "text": "Enigma provides business identity infrastructure, built on unparalleled entity resolution. With Enigma's business identity graph, you can verify customers faster, surface fraud signals buried in government records, and give AI systems ground truth on every U.S. business.",
      "html": "<h2 class=\"home-hero-subhead\" data-astro-cid-f2t6dg3d> Enigma provides business identity infrastructure, built on unparalleled entity resolution. With Enigma&apos;s business identity graph, you can verify customers faster, surface fraud signals buried in government records, and give AI systems ground truth on every U.S. business. </h2>"
    },
    {
      "text": "The knowledge graph of every U.S. Business.",
      "html": "<h2 class=\"subheader-headline purple\" data-astro-cid-j7pv25f6> The knowledge graph of every U.S. Business. </h2>"
    },
    {
      "text": "KYB & Onboarding",
      "html": "<h2 class=\"subheader-headline purple\" data-astro-cid-j7pv25f6>KYB &amp; Onboarding</h2>"
    },
    {
      "text": "Customer & Transaction Screening",
      "html": "<h2 class=\"subheader-headline purple\" data-astro-cid-j7pv25f6> Customer &amp; Transaction Screening </h2>"
    },
    {
      "text": "Ground Truth for Payments Leaders",
      "html": "<h2 class=\"subheader-headline purple\" data-astro-cid-j7pv25f6> Ground Truth for Payments Leaders </h2>"
    },
    {
      "text": "The Enigma Identity Graph: A Single Source of Truth for Every US Business",
      "html": "<h2 class=\"subheader-headline purple\" data-astro-cid-j7pv25f6> The Enigma Identity Graph: A Single Source of Truth for Every US Business </h2>"
    },
    {
      "text": "Explore Enigma Data",
      "html": "<h2 class=\"subheader-headline dark color\" data-astro-cid-j7pv25f6>Explore Enigma Data</h2>"
    }
  ],
  "expected": [
    {
      "id": "what",
      "label": "What is Enigma: Trusted business data?",
      "pattern": {}
    },
    {
      "id": "how",
      "label": "How does Enigma: Trusted business data work?",
      "pattern": {}
    },
    {
      "id": "benefits",
      "label": "Why use Enigma: Trusted business data?",
      "pattern": {}
    },
    {
      "id": "cost",
      "label": "Is Enigma: Trusted business data free or paid?",
      "pattern": {}
    },
    {
      "id": "compare",
      "label": "How does Enigma: Trusted business data compare with alternatives?",
      "pattern": {}
    }
  ],
  "missing": [
    {
      "id": "what",
      "label": "What is Enigma: Trusted business data?",
      "pattern": {}
    },
    {
      "id": "how",
      "label": "How does Enigma: Trusted business data work?",
      "pattern": {}
    },
    {
      "id": "benefits",
      "label": "Why use Enigma: Trusted business data?",
      "pattern": {}
    },
    {
      "id": "cost",
      "label": "Is Enigma: Trusted business data free or paid?",
      "pattern": {}
    },
    {
      "id": "compare",
      "label": "How does Enigma: Trusted business data compare with alternatives?",
      "pattern": {}
    }
  ],
  "score": 70,
  "weight": 8
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AIO: Page experience for AIO

AIO: Page experience for AIO scored 80/100 and needs improvement.

1 Warning

Needs attention

AIO: Page experience for AIO

Warning
01

Issue

30 image(s) are missing width/height attributes.

Details

02

Why it matters

AI Overviews depend on Google-search eligibility, useful visible content, consistent structured data, answer-first sections, trust signals, and preview controls that permit snippets.

Check name

AIO: Page experience for AIO

Score

80/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content eligible and useful for Google AI Overviews and AI Mode extraction.

Result

AIO: Page experience for AIO scored 80/100 and needs improvement.

Evidence
{
  "viewportContent": "width=device-width, initial-scale=1.0",
  "visibleWords": 628,
  "htmlBytes": 57391,
  "imagesMissingDimensions": [
    {
      "src": "/images/home/arrow-large-right.svg",
      "width": "",
      "height": "",
      "loading": "",
      "html": "<img src=\"/images/home/arrow-large-right.svg\" alt class=\"site-nav-dropdown-arrow\" aria-hidden=\"true\" data-astro-cid-yikpzsy5>"
    },
    {
      "src": "/images/home/arrow-large-right.svg",
      "width": "",
      "height": "",
      "loading": "",
      "html": "<img src=\"/images/home/arrow-large-right.svg\" alt class=\"site-nav-dropdown-arrow\" aria-hidden=\"true\" data-astro-cid-yikpzsy5>"
    },
    {
      "src": "/images/home/arrow-large-right.svg",
      "width": "",
      "height": "",
      "loading": "",
      "html": "<img src=\"/images/home/arrow-large-right.svg\" alt class=\"site-nav-dropdown-arrow\" aria-hidden=\"true\" data-astro-cid-yikpzsy5>"
    },
    {
      "src": "/images/home/arrow-large-right.svg",
      "width": "",
      "height": "",
      "loading": "",
      "html": "<img src=\"/images/home/arrow-large-right.svg\" alt class=\"site-nav-dropdown-arrow\" aria-hidden=\"true\" data-astro-cid-yikpzsy5>"
    },
    {
      "src": "/images/home/arrow-large-right.svg",
      "width": "",
      "height": "",
      "loading": "",
      "html": "<img src=\"/images/home/arrow-large-right.svg\" alt class=\"site-nav-dropdown-arrow\" aria-hidden=\"true\" data-astro-cid-yikpzsy5>"
    },
    {
      "src": "/images/home/arrow-large-right.svg",
      "width": "",
      "height": "",
      "loading": "",
      "html": "<img src=\"/images/home/arrow-large-right.svg\" alt class=\"site-nav-dropdown-arrow\" aria-hidden=\"true\" data-astro-cid-yikpzsy5>"
    },
    {
      "src": "/images/home/arrow-large-right.svg",
      "width": "",
      "height": "",
      "loading": "",
      "html": "<img src=\"/images/home/arrow-large-right.svg\" alt class=\"site-nav-dropdown-arrow\" aria-hidden=\"true\" data-astro-cid-yikpzsy5>"
    },
    {
      "src": "/images/home/arrow-large-right.svg",
      "width": "",
      "height": "",
      "loading": "",
      "html": "<img src=\"/images/home/arrow-large-right.svg\" alt class=\"site-nav-dropdown-arrow\" aria-hidden=\"true\" data-astro-cid-yikpzsy5>"
    },
    {
      "src": "/images/home/arrow-large-right.svg",
      "width": "",
      "height": "",
      "loading": "",
      "html": "<img src=\"/images/home/arrow-large-right.svg\" alt class=\"site-nav-dropdown-arrow\" aria-hidden=\"true\" data-astro-cid-yikpzsy5>"
    },
    {
      "src": "/images/home/arrow-large-right.svg",
      "width": "",
      "height": "",
      "loading": "",
      "html": "<img src=\"/images/home/arrow-large-right.svg\" alt class=\"site-nav-dropdown-arrow\" aria-hidden=\"true\" data-astro-cid-yikpzsy5>"
    },
    {
      "src": "/images/home/arrow-large-right.svg",
      "width": "",
      "height": "",
      "loading": "",
      "html": "<img src=\"/images/home/arrow-large-right.svg\" alt class=\"site-nav-dropdown-arrow\" aria-hidden=\"true\" data-astro-cid-yikpzsy5>"
    },
    {
      "src": "/images/home/arrow-large-right.svg",
      "width": "",
      "height": "",
      "loading": "",
      "html": "<img src=\"/images/home/arrow-large-right.svg\" alt class=\"site-nav-dropdown-arrow\" aria-hidden=\"true\" data-astro-cid-yikpzsy5>"
    },
    {
      "src": "/images/home/arrow-large-right.svg",
      "width": "",
      "height": "",
      "loading": "",
      "html": "<img src=\"/images/home/arrow-large-right.svg\" alt class=\"site-nav-dropdown-arrow\" aria-hidden=\"true\" data-astro-cid-yikpzsy5>"
    },
    {
      "src": "/images/home/logo-color-capitalone.svg",
      "width": "",
      "height": "",
      "loading": "eager",
      "html": "<img src=\"/images/home/logo-color-capitalone.svg\" alt=\"Capital One\" loading=\"eager\" data-astro-cid-m4thvre5>"
    },
    {
      "src": "/images/home/logo-color-chase.svg",
      "width": "",
      "height": "",
      "loading": "eager",
      "html": "<img src=\"/images/home/logo-color-chase.svg\" alt=\"Chase\" loading=\"eager\" data-astro-cid-m4thvre5>"
    },
    {
      "src": "/images/home/logo-color-parallel.svg",
      "width": "",
      "height": "",
      "loading": "eager",
      "html": "<img src=\"/images/home/logo-color-parallel.svg\" alt=\"Parallel\" loading=\"eager\" data-astro-cid-m4thvre5>"
    },
    {
      "src": "/images/home/Ramp-Lockup-RGB-Slate-0125.svg",
      "width": "",
      "height": "",
      "loading": "eager",
      "html": "<img src=\"/images/home/Ramp-Lockup-RGB-Slate-0125.svg\" alt=\"Ramp\" loading=\"eager\" data-astro-cid-m4thvre5>"
    },
    {
      "src": "/images/home/logo-color-doordash.svg",
      "width": "",
      "height": "",
      "loading": "eager",
      "html": "<img src=\"/images/home/logo-color-doordash.svg\" alt=\"DoorDash\" loading=\"eager\" data-astro-cid-m4thvre5>"
    },
    {
      "src": "/images/home/logo-color-alloy.svg",
      "width": "",
      "height": "",
      "loading": "eager",
      "html": "<img src=\"/images/home/logo-color-alloy.svg\" alt=\"Alloy\" loading=\"eager\" data-astro-cid-m4thvre5>"
    },
    {
      "src": "/images/home/logo-color-gusto.svg",
      "width": "",
      "height": "",
      "loading": "eager",
      "html": "<img src=\"/images/home/logo-color-gusto.svg\" alt=\"Gusto\" loading=\"eager\" data-astro-cid-m4thvre5>"
    },
    {
      "src": "/images/home/logo-color-bill.svg",
      "width": "",
      "height": "",
      "loading": "eager",
      "html": "<img src=\"/images/home/logo-color-bill.svg\" alt=\"Bill\" loading=\"eager\" data-astro-cid-m4thvre5>"
    },
    {
      "src": "/images/home/subheader-background.svg",
      "width": "",
      "height": "",
      "loading": "",
      "html": "<img src=\"/images/home/subheader-background.svg\" alt class=\"bg-image\" data-astro-cid-j7pv25f6>"
    },
    {
      "src": "/images/home/subheader-background.svg",
      "width": "",
      "height": "",
      "loading": "",
      "html": "<img src=\"/images/home/subheader-background.svg\" alt class=\"bg-image\" data-astro-cid-j7pv25f6>"
    },
    {
      "src": "/images/home/subheader-background.svg",
      "width": "",
      "height": "",
      "loading": "",
      "html": "<img src=\"/images/home/subheader-background.svg\" alt class=\"bg-image\" data-astro-cid-j7pv25f6>"
    },
    {
      "src": "/images/home/subheader-background.svg",
      "width": "",
      "height": "",
      "loading": "",
      "html": "<img src=\"/images/home/subheader-background.svg\" alt class=\"bg-image\" data-astro-cid-j7pv25f6>"
    },
    {
      "src": "/images/home/subheader-background.svg",
      "width": "",
      "height": "",
      "loading": "",
      "html": "<img src=\"/images/home/subheader-background.svg\" alt class=\"bg-image\" data-astro-cid-j7pv25f6>"
    },
    {
      "src": "/images/home/background-elipsis.svg",
      "width": "",
      "height": "",
      "loading": "",
      "html": "<img src=\"/images/home/background-elipsis.svg\" alt class=\"bg-image decoration\" data-astro-cid-j7pv25f6>"
    },
    {
      "src": "/images/home/Logo.gif",
      "width": "",
      "height": "",
      "loading": "",
      "html": "<img src=\"/images/home/Logo.gif\" alt=\"Enigma logo\" class=\"footer-logo\" data-astro-cid-cmhnwpac>"
    },
    {
      "src": "/images/home/linkedin_1.svg",
      "width": "",
      "height": "",
      "loading": "",
      "html": "<img src=\"/images/home/linkedin_1.svg\" alt=\"Enigma LinkedIn Link\" class=\"footer-social-icon\" data-astro-cid-cmhnwpac>"
    },
    {
      "src": "/images/home/Twitter_X.svg",
      "width": "",
      "height": "",
      "loading": "",
      "html": "<img src=\"/images/home/Twitter_X.svg\" alt=\"Enigma X (Twitter) Link\" class=\"footer-social-icon\" data-astro-cid-cmhnwpac>"
    }
  ],
  "possibleDialogs": [],
  "score": 80,
  "weight": 10
}

Agent Ease of UseAPIEmerging recommendation

AI context endpoint

AI context endpoint is informational for this page.

Informational

Needs attention

AI context endpoint

Informational
01

Issue

AI context endpoint is informational for this page.

02

Why it matters

A context endpoint gives agents a small, low-latency summary of product purpose, safe actions, and canonical machine-readable resources without scraping the whole site.

Check name

AI context endpoint

Score

100/100

Status

informational

Category

API

Maturity

Emerging recommendation

Goal

Expose a compact API context endpoint agents can fetch before deciding which public API or discovery resource to use.

Result

AI context endpoint is informational for this page.

Validation steps

  1. Fetch to find resource

    AI context endpoint was not found at the expected path.

Evidence
{
  "steps": [
    {
      "id": "fetch",
      "title": "Fetch to find resource",
      "status": "informational",
      "evidence": {
        "checked": [
          {
            "path": "/api/ai/context",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "length": 38999
          },
          {
            "path": "/api/context",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "length": 38999
          },
          {
            "path": "/context",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "length": 38999
          }
        ]
      },
      "issue": "AI context endpoint was not found at the expected path.",
      "howToFix": "Publish a concise JSON or Markdown AI context endpoint describing the product, public actions, and machine-readable resources."
    }
  ]
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AIO: Query intent coverage

AIO: Query intent coverage is informational for this page.

Informational

Needs attention

AIO: Query intent coverage

Informational
01

Issue

Missing likely AI Overview intent sections: what, how, benefits, cost, compare.

Details

02

Why it matters

AI Overviews depend on Google-search eligibility, useful visible content, consistent structured data, answer-first sections, trust signals, and preview controls that permit snippets.

Check name

AIO: Query intent coverage

Score

70/100

Status

informational

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content eligible and useful for Google AI Overviews and AI Mode extraction.

Result

AIO: Query intent coverage is informational for this page.

Evidence
{
  "headings": [
    {
      "text": "Enigma provides business identity infrastructure, built on unparalleled entity resolution. With Enigma's business identity graph, you can verify customers faster, surface fraud signals buried in government records, and give AI systems ground truth on every U.S. business.",
      "html": "<h2 class=\"home-hero-subhead\" data-astro-cid-f2t6dg3d> Enigma provides business identity infrastructure, built on unparalleled entity resolution. With Enigma&apos;s business identity graph, you can verify customers faster, surface fraud signals buried in government records, and give AI systems ground truth on every U.S. business. </h2>"
    },
    {
      "text": "The knowledge graph of every U.S. Business.",
      "html": "<h2 class=\"subheader-headline purple\" data-astro-cid-j7pv25f6> The knowledge graph of every U.S. Business. </h2>"
    },
    {
      "text": "KYB & Onboarding",
      "html": "<h2 class=\"subheader-headline purple\" data-astro-cid-j7pv25f6>KYB &amp; Onboarding</h2>"
    },
    {
      "text": "Customer & Transaction Screening",
      "html": "<h2 class=\"subheader-headline purple\" data-astro-cid-j7pv25f6> Customer &amp; Transaction Screening </h2>"
    },
    {
      "text": "Ground Truth for Payments Leaders",
      "html": "<h2 class=\"subheader-headline purple\" data-astro-cid-j7pv25f6> Ground Truth for Payments Leaders </h2>"
    },
    {
      "text": "The Enigma Identity Graph: A Single Source of Truth for Every US Business",
      "html": "<h2 class=\"subheader-headline purple\" data-astro-cid-j7pv25f6> The Enigma Identity Graph: A Single Source of Truth for Every US Business </h2>"
    },
    {
      "text": "Explore Enigma Data",
      "html": "<h2 class=\"subheader-headline dark color\" data-astro-cid-j7pv25f6>Explore Enigma Data</h2>"
    }
  ],
  "expected": [
    {
      "id": "what",
      "label": "What is Enigma: Trusted business data?",
      "pattern": {}
    },
    {
      "id": "how",
      "label": "How does Enigma: Trusted business data work?",
      "pattern": {}
    },
    {
      "id": "benefits",
      "label": "Why use Enigma: Trusted business data?",
      "pattern": {}
    },
    {
      "id": "cost",
      "label": "Is Enigma: Trusted business data free or paid?",
      "pattern": {}
    },
    {
      "id": "compare",
      "label": "How does Enigma: Trusted business data compare with alternatives?",
      "pattern": {}
    }
  ],
  "missing": [
    {
      "id": "what",
      "label": "What is Enigma: Trusted business data?",
      "pattern": {}
    },
    {
      "id": "how",
      "label": "How does Enigma: Trusted business data work?",
      "pattern": {}
    },
    {
      "id": "benefits",
      "label": "Why use Enigma: Trusted business data?",
      "pattern": {}
    },
    {
      "id": "cost",
      "label": "Is Enigma: Trusted business data free or paid?",
      "pattern": {}
    },
    {
      "id": "compare",
      "label": "How does Enigma: Trusted business data compare with alternatives?",
      "pattern": {}
    }
  ],
  "score": 70,
  "weight": 4
}

Agent Ease of UseAuthEmerging recommendation

Auth.md Agent Registration

Auth.md Agent Registration has an informational finding because the page appears to support authentication.

Informational

Needs attention

Auth.md Agent Registration

Informational
01

Issue

auth.md response did not match the expected agent registration shape. Content-Type "text/html; charset=utf-8" is not Markdown or text/plain; missing /.well-known/oauth-protected-resource link; missing /.well-known/oauth-authorization-server link; missing supported identity type language; missing credential type language.

02

Why it matters

Agent registration metadata lets automated clients find the registration path, supported identity types, credential types, and related claim or revocation endpoints without scraping human docs.

Check name

Auth.md Agent Registration

Score

0/100

Status

informational

Category

Auth

Maturity

Emerging recommendation

Goal

Publish Auth.md and agent_auth metadata so agents can discover registration and credential requirements.

Result

Auth.md Agent Registration has an informational finding because the page appears to support authentication.

Validation steps

  1. Fetch and validate /auth.md

    auth.md response did not match the expected agent registration shape. Content-Type "text/html; charset=utf-8" is not Markdown or text/plain; missing /.well-known/oauth-protected-resource link; missing /.well-known/oauth-authorization-server link; missing supported identity type language; missing credential type language.

  2. Publish protected resource metadata

    The OAuth Protected Resource metadata endpoint did not return HTTP 2xx.

  3. Validate agent_auth authorization metadata

    OAuth authorization server metadata could not be fetched.

Evidence
{
  "failedStep": "auth-md",
  "steps": [
    {
      "id": "auth-md",
      "title": "Fetch and validate /auth.md",
      "status": "fail",
      "evidence": {
        "path": "/auth.md",
        "ok": false,
        "statusCode": 404,
        "contentType": "text/html; charset=utf-8",
        "length": 38999,
        "validation": {
          "valid": false,
          "issue": "auth.md response did not match the expected agent registration shape. Content-Type \"text/html; charset=utf-8\" is not Markdown or text/plain; missing /.well-known/oauth-protected-resource link; missing /.well-known/oauth-authorization-server link; missing supported identity type language; missing credential type language.",
          "compatibleContentType": false,
          "contentLength": 38302,
          "hasRegisterInstructions": true,
          "hasProtectedResourceLink": false,
          "hasAuthorizationServerLink": false,
          "mentionsIdentity": false,
          "mentionsCredential": false,
          "links": [
            "/svg+xml",
            "/favicon.svg",
            "/favicon-260.png",
            "https://www.enigma.com/404/\"><title>Not",
            "/title",
            "https://www.enigma.com/404/\"><meta",
            "https://www.enigma.com/og/default.png\"><meta",
            "https://www.enigma.com/404/\"><meta",
            "https://www.enigma.com/og/default.png\"><meta",
            "/_astro/fonts/a70dd30af94115f3.ttf"
          ],
          "rawExcerpt": "<!DOCTYPE html><html lang=\"en\"> <head><meta charset=\"UTF-8\"><meta name=\"viewport\" content=\"width=device-width, initial-scale=1.0\"><link rel=\"icon\" type=\"image/svg+xml\" href=\"/favicon.svg\"><link rel=\"apple-touch-icon\" href=\"/favicon-260.png\"><link rel=\"canonical\" href=\"https://www.enigma.com/404/\"><title>Not Found | Enigma</title><meta name=\"title\" content=\"Not Found | Enigma\"><meta name=\"description\" content=\"Not Found\"><meta name=\"robots\" content=\"noindex, nofollow\"><meta property=\"og:type\" content=\"website\"><meta property=\"og:url\" content=\"https://www.enigma.com/404/\"><meta property=\"og:title\" content=\"Not Found | Enigma\"><meta property=\"og:description\" content=\"Not Found\"><meta property=\"og:image\" content=\"https://www.enigma.com/og/default.png\"><meta property=\"twitter:card\" content=\"sum"
        }
      },
      "issue": "auth.md response did not match the expected agent registration shape. Content-Type \"text/html; charset=utf-8\" is not Markdown or text/plain; missing /.well-known/oauth-protected-resource link; missing /.well-known/oauth-authorization-server link; missing supported identity type language; missing credential type language.",
      "howToFix": "Serve /auth.md at the site root as Markdown with agent registration instructions and links to OAuth metadata."
    },
    {
      "id": "oauth-protected-resource",
      "title": "Publish protected resource metadata",
      "status": "fail",
      "evidence": {
        "path": "/.well-known/oauth-protected-resource",
        "ok": false,
        "statusCode": 404,
        "contentType": "text/html; charset=utf-8",
        "length": 38999,
        "text": "<!DOCTYPE html><html lang=\"en\"> <head><meta charset=\"UTF-8\"><meta name=\"viewport\" content=\"width=device-width, initial-scale=1.0\"><link rel=\"icon\" type=\"image/svg+xml\" href=\"/favicon.svg\"><link rel=\"apple-touch-icon\" href=\"/favicon-260.png\"><link rel=\"canonical\" href=\"https://www.enigma.com/404/\"><title>Not Found | Enigma</title><meta name=\"title\" content=\"Not Found | Enigma\"><meta name=\"description\" content=\"Not Found\"><meta name=\"robots\" content=\"noindex, nofollow\"><meta property=\"og:type\" content=\"website\"><meta property=\"og:url\" content=\"https://www.enigma.com/404/\"><meta property=\"og:title\" content=\"Not Found | Enigma\"><meta property=\"og:description\" content=\"Not Found\"><meta property=\"og:image\" content=\"https://www.enigma.com/og/default.png\"><meta property=\"twitter:card\" content=\"summary_large_image\"><meta property=\"twitter:url\" content=\"https://www.enigma.com/404/\"><meta property=\"twitter:title\" content=\"Not Found | Enigma\"><meta property=\"twitter:description\" content=\"Not Found\"><meta property=\"twitter:image\" content=\"https://www.enigma.com/og/default.png\"><meta name=\"generator\" content=\"Astro v6.1.10\"><style>@font-face{font-family:Aeonik-8f83e2d58e43829d;src:url(\"/_astro/fonts/a70dd30af94115f3.ttf\") format(\"truetype\");font-display:swap;font-weight:100;font-style:normal;}@font-face{font-family:Aeonik-8f83e2d58e43829d;src:url(\"/_astro/fonts/77f826545551764c.ttf\") format(\"truetype\");font-display:swap;font-weight:100;font-style:italic;}@font-face{font-family:Aeonik-8f83e2d58e43829d;src:url(\"/_astro/fonts/134ae4628847654e.ttf\") format(\"truetype\");font-display:swap;font-weight:200;font-style:normal;}@font-face{font-family:Aeonik-8f83e2d58e43829d;src:url(\"/_astro/fonts/2b083ad49a475f13.ttf\") format(\"truetype\");font-display:swap;font-weight:200;font-style:italic;}@font-face{font-family:Aeonik-8f83e2d58e43829d;src:url(\"/_astro/fonts/de1234dcc5c30f92.ttf\") format(\"truetype\");font-display:swap;font-weight:300;font-style:normal;}@font-face{font-family:Aeonik-8f83e2d58e43829d;src:url(\"/_astro/fonts/6478431d37d11f90.ttf\") format(\"truetype\");font-display:swap;font-weight:300;font-style:italic;}@font-face{font-family:Aeonik-8f83e2d58e43829d;src:url(\"/_astro/fonts/c3ec5000803a1028.ttf\") format(\"truetype\");font-display:swap;font-weight:400;font-style:normal;}@font-face{font-family:Aeonik-8f83e2d58e43829d;src:url(\"/_astro/fonts/21067f4df88ace52.ttf\") format(\"truetype\");font-display:swap;font-weight:400;font-style:italic;}@font-face{font-family:Aeonik-8f83e2d58e43829d;src:url(\"/_astro/fonts/6be67351d7553f0b.ttf\") format(\"truetype\");font-display:swap;font-weight:500;font-style:normal;}@font-face{font-family:Aeonik-8f83e2d58e43829d;src:url(\"/_astro/fonts/4c31f19b55b5cb1c.ttf\") format(\"truetype\");font-display:swap;font-weight:500;font-style:italic;}@font-face{font-family:Aeonik-8f83e2d58e43829d;src:url(\"/_astro/fonts/1b53c6f29d8b6fe0.ttf\") format(\"truetype\");font-display:swap;font-weight:700;font-style:normal;}@font-face{font-family:Aeonik-8f83e2d58e43829d;src:url(\"/_astro/fonts/c829703b6848d103.ttf\") format(\"truetype\");font-display:swap;font-weight:700;font-style:italic;}@font-face{font-family:Aeonik-8f83e2d58e43829d;src:url(\"/_astro/fonts/f80af174cebfa2dc.ttf\") format(\"truetype\");font-display:swap;font-weight:900;font-style:normal;}@font-face{font-family:Aeonik-8f83e2d58e43829d;src:url(\"/_astro/fonts/b3dad4601e9751d9.ttf\") format(\"truetype\");font-display:swap;font-weight:900;font-style:italic;}@font-face{font-family:\"Aeonik-8f83e2d58e43829d fallback: Arial\";src:local(\"Arial\");font-display:swap;font-weight:100;font-style:normal;size-adjust:96.2313%;ascent-override:103.9163%;descent-override:20.7833%;line-gap-override:0%;}@font-face{font-family:\"Aeonik-8f83e2d58e43829d fallback: Arial\";src:local(\"Arial\");font-display:swap;font-weight:100;font-style:italic;size-adjust:96.2313%;ascent-override:103.9163%;descent-override:20.7833%;line-gap-override:0%;}@font-face{font-family:\"Aeonik-8f83e2d58e43829d fallback: Arial\";src:local(\"Arial\");font-disp"
      },
      "issue": "The OAuth Protected Resource metadata endpoint did not return HTTP 2xx.",
      "howToFix": "Publish /.well-known/oauth-protected-resource with resource and authorization_servers fields."
    },
    {
      "id": "agent-auth-block",
      "title": "Validate agent_auth authorization metadata",
      "status": "fail",
      "evidence": {
        "valid": false,
        "issue": "OAuth authorization server metadata could not be fetched.",
        "fetch": {
          "ok": false,
          "statusCode": 404,
          "contentType": "text/html; charset=utf-8",
          "length": 38999,
          "text": "<!DOCTYPE html><html lang=\"en\"> <head><meta charset=\"UTF-8\"><meta name=\"viewport\" content=\"width=device-width, initial-scale=1.0\"><link rel=\"icon\" type=\"image/svg+xml\" href=\"/favicon.svg\"><link rel=\"apple-touch-icon\" href=\"/favicon-260.png\"><link rel=\"canonical\" href=\"https://www.enigma.com/404/\"><title>Not Found | Enigma</title><meta name=\"title\" content=\"Not Found | Enigma\"><meta name=\"description\" content=\"Not Found\"><meta name=\"robots\" content=\"noindex, nofollow\"><meta property=\"og:type\" content=\"website\"><meta property=\"og:url\" content=\"https://www.enigma.com/404/\"><meta property=\"og:title\" content=\"Not Found | Enigma\"><meta property=\"og:description\" content=\"Not Found\"><meta property=\"og:image\" content=\"https://www.enigma.com/og/default.png\"><meta property=\"twitter:card\" content=\"summary_large_image\"><meta property=\"twitter:url\" content=\"https://www.enigma.com/404/\"><meta property=\"twitter:title\" content=\"Not Found | Enigma\"><meta property=\"twitter:description\" content=\"Not Found\"><meta property=\"twitter:image\" content=\"https://www.enigma.com/og/default.png\"><meta name=\"generator\" content=\"Astro v6.1.10\"><style>@font-face{font-family:Aeonik-8f83e2d58e43829d;src:url(\"/_astro/fonts/a70dd30af94115f3.ttf\") format(\"truetype\");font-display:swap;font-weight:100;font-style:normal;}@font-face{font-family:Aeonik-8f83e2d58e43829d;src:url(\"/_astro/fonts/77f826545551764c.ttf\") format(\"truetype\");font-display:swap;font-weight:100;font-style:italic;}@font-face{font-family:Aeonik-8f83e2d58e43829d;src:url(\"/_astro/fonts/134ae4628847654e.ttf\") format(\"truetype\");font-display:swap;font-weight:200;font-style:normal;}@font-face{font-family:Aeonik-8f83e2d58e43829d;src:url(\"/_astro/fonts/2b083ad49a475f13.ttf\") format(\"truetype\");font-display:swap;font-weight:200;font-style:italic;}@font-face{font-family:Aeonik-8f83e2d58e43829d;src:url(\"/_astro/fonts/de1234dcc5c30f92.ttf\") format(\"truetype\");font-display:swap;font-weight:300;font-style:normal;}@font-face{font-family:Aeonik-8f83e2d58e43829d;src:url(\"/_astro/fonts/6478431d37d11f90.ttf\") format(\"truetype\");font-display:swap;font-weight:300;font-style:italic;}@font-face{font-family:Aeonik-8f83e2d58e43829d;src:url(\"/_astro/fonts/c3ec5000803a1028.ttf\") format(\"truetype\");font-display:swap;font-weight:400;font-style:normal;}@font-face{font-family:Aeonik-8f83e2d58e43829d;src:url(\"/_astro/fonts/21067f4df88ace52.ttf\") format(\"truetype\");font-display:swap;font-weight:400;font-style:italic;}@font-face{font-family:Aeonik-8f83e2d58e43829d;src:url(\"/_astro/fonts/6be67351d7553f0b.ttf\") format(\"truetype\");font-display:swap;font-weight:500;font-style:normal;}@font-face{font-family:Aeonik-8f83e2d58e43829d;src:url(\"/_astro/fonts/4c31f19b55b5cb1c.ttf\") format(\"truetype\");font-display:swap;font-weight:500;font-style:italic;}@font-face{font-family:Aeonik-8f83e2d58e43829d;src:url(\"/_astro/fonts/1b53c6f29d8b6fe0.ttf\") format(\"truetype\");font-display:swap;font-weight:700;font-style:normal;}@font-face{font-family:Aeonik-8f83e2d58e43829d;src:url(\"/_astro/fonts/c829703b6848d103.ttf\") format(\"truetype\");font-display:swap;font-weight:700;font-style:italic;}@font-face{font-family:Aeonik-8f83e2d58e43829d;src:url(\"/_astro/fonts/f80af174cebfa2dc.ttf\") format(\"truetype\");font-display:swap;font-weight:900;font-style:normal;}@font-face{font-family:Aeonik-8f83e2d58e43829d;src:url(\"/_astro/fonts/b3dad4601e9751d9.ttf\") format(\"truetype\");font-display:swap;font-weight:900;font-style:italic;}@font-face{font-family:\"Aeonik-8f83e2d58e43829d fallback: Arial\";src:local(\"Arial\");font-display:swap;font-weight:100;font-style:normal;size-adjust:96.2313%;ascent-override:103.9163%;descent-override:20.7833%;line-gap-override:0%;}@font-face{font-family:\"Aeonik-8f83e2d58e43829d fallback: Arial\";src:local(\"Arial\");font-display:swap;font-weight:100;font-style:italic;size-adjust:96.2313%;ascent-override:103.9163%;descent-override:20.7833%;line-gap-override:0%;}@font-face{font-family:\"Aeonik-8f83e2d58e43829d fallback: Arial\";src:local(\"Arial\");font-disp"
        }
      },
      "issue": "OAuth authorization server metadata could not be fetched.",
      "howToFix": "Add agent_auth to /.well-known/oauth-authorization-server with register_uri, supported identity types, credential types, and claim or revocation URLs where applicable."
    }
  ],
  "authApplicability": {
    "supportsAuth": true,
    "score": 3,
    "signals": [
      {
        "source": "visible-text",
        "weight": 3,
        "match": "sign in"
      }
    ]
  },
  "resourceFetchSucceeded": false
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

GEO: Q&A and FAQ opportunities

GEO: Q&A and FAQ opportunities is informational for this page.

Informational

Needs attention

GEO: Q&A and FAQ opportunities

Informational
01

Issue

7 h2 heading(s) are not phrased as questions; this is optional and only useful where Q&A wording is natural. No visible FAQ or FAQPage schema was detected; this is optional unless the page answers common questions.

Details

02

Why it matters

Generative engines favor pages with self-contained answer passages, clear entities, structured data, summaries, FAQ patterns, and crawler-accessible HTML that can be cited without extra interpretation.

Check name

GEO: Q&A and FAQ opportunities

Score

75/100

Status

informational

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content easy for AI answer engines to extract, cite, and attribute.

Result

GEO: Q&A and FAQ opportunities is informational for this page.

Evidence
{
  "h2Count": 7,
  "questionH2s": 0,
  "hasFaq": false,
  "nonQuestionH2s": [
    {
      "index": 1,
      "text": "Enigma provides business identity infrastructure, built on unparalleled entity resolution. With Enigma's business identity graph, you can verify customers faster, surface fraud signals buried in government records, and give AI systems ground truth on every U.S. business.",
      "isQuestion": false,
      "html": "<h2 class=\"home-hero-subhead\" data-astro-cid-f2t6dg3d> Enigma provides business identity infrastructure, built on unparalleled entity resolution. With Enigma&apos;s business identity graph, you can verify customers faster, surface fraud signals buried in government records, and give AI systems ground truth on every U.S. business. </h2>"
    },
    {
      "index": 2,
      "text": "The knowledge graph of every U.S. Business.",
      "isQuestion": false,
      "html": "<h2 class=\"subheader-headline purple\" data-astro-cid-j7pv25f6> The knowledge graph of every U.S. Business. </h2>"
    },
    {
      "index": 3,
      "text": "KYB & Onboarding",
      "isQuestion": false,
      "html": "<h2 class=\"subheader-headline purple\" data-astro-cid-j7pv25f6>KYB &amp; Onboarding</h2>"
    },
    {
      "index": 4,
      "text": "Customer & Transaction Screening",
      "isQuestion": false,
      "html": "<h2 class=\"subheader-headline purple\" data-astro-cid-j7pv25f6> Customer &amp; Transaction Screening </h2>"
    },
    {
      "index": 5,
      "text": "Ground Truth for Payments Leaders",
      "isQuestion": false,
      "html": "<h2 class=\"subheader-headline purple\" data-astro-cid-j7pv25f6> Ground Truth for Payments Leaders </h2>"
    },
    {
      "index": 6,
      "text": "The Enigma Identity Graph: A Single Source of Truth for Every US Business",
      "isQuestion": false,
      "html": "<h2 class=\"subheader-headline purple\" data-astro-cid-j7pv25f6> The Enigma Identity Graph: A Single Source of Truth for Every US Business </h2>"
    },
    {
      "index": 7,
      "text": "Explore Enigma Data",
      "isQuestion": false,
      "html": "<h2 class=\"subheader-headline dark color\" data-astro-cid-j7pv25f6>Explore Enigma Data</h2>"
    }
  ],
  "score": 75,
  "weight": 4
}

AI DiscoverabilityDiscoverabilityEstablished

IndexNow key

IndexNow key is informational for this page.

Informational

Needs attention

IndexNow key

Informational
01

Issue

IndexNow key is informational for this page.

02

Why it matters

IndexNow lets sites notify participating search engines about changed URLs, but ownership verification requires a UTF-8 key file whose filename matches the key.

Check name

IndexNow key

Score

100/100

Status

informational

Category

Discoverability

Maturity

Established

Goal

Verify that IndexNow ownership key placement is detectable when the site advertises it.

Result

IndexNow key is informational for this page.

Validation steps

  1. Find advertised IndexNow key location

    No IndexNow key location was advertised in HTML, Link headers, or robots.txt.

  2. Fetch and validate IndexNow key file

    No discoverable IndexNow key file was found.

Evidence
{
  "steps": [
    {
      "id": "advertised-location",
      "title": "Find advertised IndexNow key location",
      "status": "informational",
      "evidence": {
        "advertised": []
      },
      "issue": "No IndexNow key location was advertised in HTML, Link headers, or robots.txt.",
      "howToFix": "Advertise the key location with robots.txt IndexNow-Key, rel=\"indexnow-key\", or meta name=\"indexnow-key-location\" if you want scanners to verify it."
    },
    {
      "id": "fetch-key",
      "title": "Fetch and validate IndexNow key file",
      "status": "informational",
      "evidence": {
        "advertised": [],
        "checked": []
      },
      "issue": "No discoverable IndexNow key file was found.",
      "howToFix": "Host a UTF-8 text file named {key}.txt using a 32-character hexadecimal key whose body exactly matches the key."
    }
  ]
}

Agent Ease of UseAuthEstablished

OAuth / OIDC discovery

OAuth / OIDC discovery has an informational finding because the page appears to support authentication.

Informational

Needs attention

OAuth / OIDC discovery

Informational
01

Issue

OAuth / OIDC discovery was not found at the expected path.

02

Why it matters

OAuth and OIDC discovery let agents find authorization, token, and key endpoints programmatically instead of relying on human documentation.

Check name

OAuth / OIDC discovery

Score

0/100

Status

informational

Category

Auth

Maturity

Established

Goal

Publish OAuth/OIDC discovery metadata so agents can authenticate with your APIs.

Result

OAuth / OIDC discovery has an informational finding because the page appears to support authentication.

Validation steps

  1. Fetch to find resource

    OAuth / OIDC discovery was not found at the expected path.

Evidence
{
  "failedStep": "fetch",
  "steps": [
    {
      "id": "fetch",
      "title": "Fetch to find resource",
      "status": "fail",
      "evidence": {
        "checked": [
          {
            "path": "/.well-known/openid-configuration",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "length": 38999
          },
          {
            "path": "/.well-known/oauth-authorization-server",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "length": 38999
          }
        ]
      },
      "issue": "OAuth / OIDC discovery was not found at the expected path.",
      "howToFix": "Publish valid OAuth/OIDC metadata only when the site actually supports OAuth/OIDC. Otherwise omit provider discovery and document any unauthenticated public APIs separately."
    }
  ],
  "authApplicability": {
    "supportsAuth": true,
    "score": 3,
    "signals": [
      {
        "source": "visible-text",
        "weight": 3,
        "match": "sign in"
      }
    ]
  },
  "resourceFetchSucceeded": false
}

Agent Ease of UseAuthEmerging recommendation

OAuth Protected Resource

OAuth Protected Resource has an informational finding because the page appears to support authentication.

Informational

Needs attention

OAuth Protected Resource

Informational
01

Issue

The OAuth Protected Resource metadata endpoint did not return HTTP 2xx.

02

Why it matters

Protected Resource metadata tells agents which authorization servers protect an API and how to connect authentication challenges to the right resource.

Check name

OAuth Protected Resource

Score

0/100

Status

informational

Category

Auth

Maturity

Emerging recommendation

Goal

Publish OAuth Protected Resource Metadata so agents can discover how to authenticate.

Result

OAuth Protected Resource has an informational finding because the page appears to support authentication.

Validation steps

  1. Fetch protected resource metadata

    The OAuth Protected Resource metadata endpoint did not return HTTP 2xx.

  2. Validate protected resource metadata

    Response is not valid JSON.

  3. Validate protected resource identity

    Protected resource metadata `resource` did not match the resource identifier used to retrieve it.

  4. Probe protected API Bearer challenge

    No protected route with a 401 Bearer challenge was detected; metadata alone does not prove a protected resource.

Evidence
{
  "failedStep": "fetch",
  "steps": [
    {
      "id": "fetch",
      "title": "Fetch protected resource metadata",
      "status": "fail",
      "evidence": {
        "path": "/.well-known/oauth-protected-resource",
        "statusCode": 404,
        "contentType": "text/html; charset=utf-8"
      },
      "issue": "The OAuth Protected Resource metadata endpoint did not return HTTP 2xx.",
      "howToFix": "Publish /.well-known/oauth-protected-resource JSON."
    },
    {
      "id": "metadata",
      "title": "Validate protected resource metadata",
      "status": "fail",
      "evidence": {
        "valid": false,
        "compatibleContentType": false,
        "issue": "Response is not valid JSON.",
        "rawExcerpt": "<!DOCTYPE html><html lang=\"en\"> <head><meta charset=\"UTF-8\"><meta name=\"viewport\" content=\"width=device-width, initial-scale=1.0\"><link rel=\"icon\" type=\"image/svg+xml\" href=\"/favicon.svg\"><link rel=\"apple-touch-icon\" href=\"/favicon-260.png\"><link rel=\"canonical\" href=\"https://www.enigma.com/404/\"><title>Not Found | Enigma</title><meta name=\"title\" content=\"Not Found | Enigma\"><meta name=\"description\" content=\"Not Found\"><meta name=\"robots\" content=\"noindex, nofollow\"><meta property=\"og:type\" content=\"website\"><meta property=\"og:url\" content=\"https://www.enigma.com/404/\"><meta property=\"og:title\" content=\"Not Found | Enigma\"><meta property=\"og:description\" content=\"Not Found\"><meta property=\"og:image\" content=\"https://www.enigma.com/og/default.png\"><meta property=\"twitter:card\" content=\"sum"
      },
      "issue": "Response is not valid JSON.",
      "howToFix": "Publish resource and authorization_servers as absolute URLs."
    },
    {
      "id": "resource-identity",
      "title": "Validate protected resource identity",
      "status": "fail",
      "evidence": {
        "expectedResource": "https://enigma.com"
      },
      "issue": "Protected resource metadata `resource` did not match the resource identifier used to retrieve it.",
      "howToFix": "Set `resource` to the origin/resource identifier represented by /.well-known/oauth-protected-resource."
    },
    {
      "id": "protected-route-challenge",
      "title": "Probe protected API Bearer challenge",
      "status": "informational",
      "evidence": {
        "checked": [
          {
            "path": "/api/admin/scans",
            "statusCode": 404,
            "wwwAuthenticate": {
              "valid": false,
              "present": false
            },
            "expectedMetadataUrl": "https://enigma.com/.well-known/oauth-protected-resource",
            "metadataUrlMatches": true,
            "resourceMatchesRequestContext": true
          },
          {
            "path": "/api/admin/summary",
            "statusCode": 404,
            "wwwAuthenticate": {
              "valid": false,
              "present": false
            },
            "expectedMetadataUrl": "https://enigma.com/.well-known/oauth-protected-resource",
            "metadataUrlMatches": true,
            "resourceMatchesRequestContext": true
          },
          {
            "path": "/api/scans",
            "statusCode": 404,
            "wwwAuthenticate": {
              "valid": false,
              "present": false
            },
            "expectedMetadataUrl": "https://enigma.com/.well-known/oauth-protected-resource",
            "metadataUrlMatches": true,
            "resourceMatchesRequestContext": true
          }
        ]
      },
      "issue": "No protected route with a 401 Bearer challenge was detected; metadata alone does not prove a protected resource.",
      "howToFix": "When this site exposes bearer-protected APIs, return 401 with WWW-Authenticate: Bearer and link resource_metadata."
    }
  ],
  "authApplicability": {
    "supportsAuth": true,
    "score": 3,
    "signals": [
      {
        "source": "visible-text",
        "weight": 3,
        "match": "sign in"
      }
    ]
  },
  "resourceFetchSucceeded": false
}

Performance and AccessibilityPerformanceBrowser audit

Network dependency tree

14 Fail

Check name

Network dependency tree

Score

0/100

Status

fail

Device

desktop

Category

Performance

Fix guidance

[Avoid chaining critical requests](https://developer.chrome.com/docs/performance/insights/network-dependency-tree) by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Evidence
{
  "description": "[Avoid chaining critical requests](https://developer.chrome.com/docs/performance/insights/network-dependency-tree) by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load."
}

Performance and AccessibilityPerformanceBrowser audit

Render-blocking requests

14 Fail

Check name

Render-blocking requests

Score

0/100

Status

fail

Device

desktop

Category

Performance

Estimated savings

Est savings of 210 ms

Fix guidance

Requests are blocking the page's initial render, which may delay LCP. [Deferring or inlining](https://developer.chrome.com/docs/performance/insights/render-blocking) can move these network requests out of the critical path.

Evidence
{
  "displayValue": "Est savings of 210 ms",
  "description": "Requests are blocking the page's initial render, which may delay LCP. [Deferring or inlining](https://developer.chrome.com/docs/performance/insights/render-blocking) can move these network requests out of the critical path."
}

Performance and AccessibilityPerformanceBrowser audit

Use efficient cache lifetimes

14 Fail

Check name

Use efficient cache lifetimes

Score

0/100

Status

fail

Device

desktop

Category

Performance

Estimated savings

Est savings of 1,741 KiB

Fix guidance

A long cache lifetime can speed up repeat visits to your page. [Learn more about caching](https://developer.chrome.com/docs/performance/insights/cache).

Evidence
{
  "displayValue": "Est savings of 1,741 KiB",
  "description": "A long cache lifetime can speed up repeat visits to your page. [Learn more about caching](https://developer.chrome.com/docs/performance/insights/cache)."
}

Performance and AccessibilityPerformanceBrowser audit

Avoid enormous network payloads

7 Warning

Check name

Avoid enormous network payloads

Score

50/100

Status

warning

Device

desktop

Category

Performance

Estimated savings

Total size was 4,373 KiB

Fix guidance

Large network payloads cost users real money and are highly correlated with long load times. [Learn how to reduce payload sizes](https://developer.chrome.com/docs/lighthouse/performance/total-byte-weight/).

Evidence
{
  "displayValue": "Total size was 4,373 KiB",
  "description": "Large network payloads cost users real money and are highly correlated with long load times. [Learn how to reduce payload sizes](https://developer.chrome.com/docs/lighthouse/performance/total-byte-weight/).",
  "numericValue": 4477696
}

Performance and AccessibilityPerformanceBrowser audit

Improve image delivery

7 Warning

Check name

Improve image delivery

Score

50/100

Status

warning

Device

desktop

Category

Performance

Estimated savings

Est savings of 7 KiB

Fix guidance

Reducing the download time of images can improve the perceived load time of the page and LCP. [Learn more about optimizing image size](https://developer.chrome.com/docs/performance/insights/image-delivery)

Evidence
{
  "displayValue": "Est savings of 7 KiB",
  "description": "Reducing the download time of images can improve the perceived load time of the page and LCP. [Learn more about optimizing image size](https://developer.chrome.com/docs/performance/insights/image-delivery)"
}

Performance and AccessibilityPerformanceBrowser audit

Legacy JavaScript

7 Warning

Check name

Legacy JavaScript

Score

50/100

Status

warning

Device

desktop

Category

Performance

Estimated savings

Est savings of 9 KiB

Fix guidance

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile [Baseline](https://web.dev/articles/baseline-and-polyfills) features, unless you know you must support older browsers. [Learn why most sites can deploy ES6+ code without transpiling](https://developer.chrome.com/docs/performance/insights/legacy-javascript)

Evidence
{
  "displayValue": "Est savings of 9 KiB",
  "description": "Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile [Baseline](https://web.dev/articles/baseline-and-polyfills) features, unless you know you must support older browsers. [Learn why most sites can deploy ES6+ code without transpiling](https://developer.chrome.com/docs/performance/insights/legacy-javascript)"
}

Performance and AccessibilityPerformanceBrowser audit

Loading performance

2 Fail

Check name

Loading performance

Score

88/100

Status

fail

Device

desktop

Category

Performance

Fix guidance

Review the grouped loading performance checks and improve the failing sub-checks listed in evidence.

Evidence
{
  "checks": [
    {
      "id": "largest-contentful-paint",
      "title": "Largest Contentful Paint",
      "score": 67,
      "displayValue": "1.9 s",
      "numericValue": 1877.0109578120969
    },
    {
      "id": "speed-index",
      "title": "Speed Index",
      "score": 61,
      "displayValue": "2.0 s",
      "numericValue": 2029.6632116855162
    },
    {
      "id": "interactive",
      "title": "Time to Interactive",
      "score": 77,
      "displayValue": "3.1 s",
      "numericValue": 3145.725632735918
    },
    {
      "id": "server-response-time",
      "title": "Initial server response time was short",
      "score": 100,
      "displayValue": "Root document took 180 ms",
      "numericValue": 177
    },
    {
      "id": "first-contentful-paint",
      "title": "First Contentful Paint",
      "score": 100,
      "displayValue": "0.5 s",
      "numericValue": 500.0013528163082
    },
    {
      "id": "network-rtt",
      "title": "Network Round Trip Times",
      "score": 100,
      "displayValue": "40 ms",
      "numericValue": 43.352729999999994
    },
    {
      "id": "max-potential-fid",
      "title": "Max Potential First Input Delay",
      "score": 99,
      "displayValue": "80 ms",
      "numericValue": 78
    },
    {
      "id": "total-blocking-time",
      "title": "Total Blocking Time",
      "score": 100,
      "displayValue": "20 ms",
      "numericValue": 23.5
    }
  ]
}

Fix with MCP or CLI

Use this report as the handoff into remediation. Generate a coding-agent prompt with the failing checks attached, or jump to the MCP and CLI setup docs before your next rescan.

Score history

Public scan score over time

Public reports for this website origin. Select any point or report link to open that canonical report.

1 reports
Public score history report links
Scan dateScoreReadinessReport
62/100Level 3, Bot-AwareCurrent report
enigma.com AI SEO Report: 62/100 (Level 3, Bot-Aware)