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

OVERALL SCORE

Level 3, Bot-Aware

Moderate readiness for AI agents
AIDiscoverability52%Agent Easeof Use16%Security& Trust60%GEO, AIO, AEO58%SEO100%Performance& Accessibility78%
  • AI Discoverability 52 out of 100
  • Agent Ease of Use 16 out of 100
  • Security & Trust 60 out of 100
  • GEO, AIO and AEO 58 out of 100
  • SEO 100 out of 100
  • Performance and Accessibility 78 out of 100

CAPTURED SCREENSHOT

Captured website desktop screenshot

What AI sees of your website

AI Twins - Your Personal AI Extension | Prifina favicon

AI Twins - Your Personal AI Extension | Prifina

Create your personal AI Twin with Prifina - the privacy-first platform for AI-powered digital identity and personal data ownership.

Next step

Turn this report into a fix workflow

21 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
52
Needs work12110View details
Discoverability
67
Needs work540View details
Content Readiness
50
Needs work640View details
Bot Access Control
33
Priority fix130View details
Agent Ease of Use
16
Priority fix18241View details
API
17
Priority fix180View details
Auth
Not Applicable
Not Applicable1100
MCP
25
Priority fix260View details
Skill Discovery
5
Priority fix0101View details
Agent Commerce
Not Applicable
Not Applicable400
GEO, AIO and AEO
58
Needs work1414View details
GEO Readiness
60
Needs work014View details
AIO Readiness
62
Needs work115View details
AEO Readiness
53
Needs work025View 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
78
Mostly ready2250View details
Performance
73
Needs work1340View details
Accessibility
86
Mostly ready910View details

Prioritized recommendations

Issues ranked by score impact

43 items need attention

AI DiscoverabilityBot Access ControlInformational

Content Signal

Content Signal is missing or incomplete.

50 Fail

Needs attention

Content Signal

Failed check
01

Issue

No Content Signal found in robots.txt

02

Why it matters

Content Signal provides a machine-readable way to communicate AI usage preferences where participating crawlers look for policy.

Check name

Content Signal

Score

0/100

Status

fail

Category

Bot Access Control

Maturity

Informational

Goal

Declare AI content usage preferences with Content Signal in robots.txt.

Result

Content Signal is missing or incomplete.

Evidence
{
  "signals": [],
  "ai-train": false,
  "search": false,
  "ai-input": false
}

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

Frame protection

Frame protection is missing or incomplete.

50 Fail

Needs attention

Frame protection

Failed check
01

Issue

Frame protection is missing or incomplete.

02

Why it matters

Frame protection blocks hostile sites from embedding pages in deceptive frames, reducing clickjacking risk.

Check name

Frame protection

Score

0/100

Status

fail

Category

Security & Trust

Maturity

Established

Goal

Prevent unwanted framing with X-Frame-Options or CSP frame-ancestors.

Result

Frame protection is missing or incomplete.

Evidence
{
  "xFrameOptions": null,
  "validXFrame": false,
  "contentSecurityPolicy": null,
  "cspFrameAncestors": false
}

AI DiscoverabilityDiscoverabilityEstablished

High-value schema types

High-value schema types is missing or incomplete.

50 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": [
    "Organization",
    "WebSite"
  ]
}

AI DiscoverabilityDiscoverabilityEstablished

Link headers

Link headers failed at "Find useful Link headers".

50 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 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/plain; charset=UTF-8",
            "length": 9
          }
        ]
      },
      "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."
    }
  ]
}

Agent Ease of UseAPIEstablished

API Catalog

API Catalog failed at "Fetch API catalog".

33 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/plain; 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": "Not found"
      },
      "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."
    }
  ]
}

AI DiscoverabilityContent ReadinessEstablished

Content freshness signals

Content freshness signals is missing or incomplete.

33 Fail

Needs attention

Content freshness signals

Failed check
01

Issue

Content freshness signals are incomplete: missing Last-Modified HTTP header; 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

0/100

Status

fail

Category

Content Readiness

Maturity

Established

Goal

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

Result

Content freshness signals is missing or incomplete.

Evidence
{
  "lastModified": null,
  "schemaDates": [],
  "metaDateCount": 0,
  "timeDateCount": 0
}

AI DiscoverabilityContent ReadinessEmerging recommendation

llms.txt

llms.txt failed at "Fetch to find resource".

33 Fail

Needs attention

llms.txt

Failed check
01

Issue

llms.txt was not found at the expected path.

02

Why it matters

llms.txt gives language-model clients a concise, curated summary of important site context and links before they crawl broadly.

Check name

llms.txt

Score

0/100

Status

fail

Category

Content Readiness

Maturity

Emerging recommendation

Goal

Publish llms.txt to summarize agent-readable site guidance.

Result

llms.txt failed at "Fetch to find resource".

Validation steps

  1. Fetch to find resource

    llms.txt was not found at the expected path.

Evidence
{
  "failedStep": "fetch",
  "steps": [
    {
      "id": "fetch",
      "title": "Fetch to find resource",
      "status": "fail",
      "evidence": {
        "checked": [
          {
            "path": "/llms.txt",
            "statusCode": 404,
            "contentType": "text/plain; charset=UTF-8",
            "length": 9
          },
          {
            "path": "/llms-full.txt",
            "statusCode": 404,
            "contentType": "text/plain; charset=UTF-8",
            "length": 9
          }
        ]
      },
      "issue": "llms.txt was not found at the expected path.",
      "howToFix": "Publish /llms.txt as Markdown with a clear title, concise site summary, and useful links for agents."
    }
  ]
}

Agent Ease of UseMCPEmerging recommendation

MCP Server Card

MCP Server Card failed at "Fetch to find resource".

33 Fail

Needs attention

MCP Server Card

Failed check
01

Issue

MCP Server Card was not found at the expected path.

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

0/100

Status

fail

Category

MCP

Maturity

Emerging recommendation

Goal

Publish an MCP Server Card for agent discovery.

Result

MCP Server Card failed at "Fetch to find resource".

Validation steps

  1. Fetch to find resource

    MCP Server 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/mcp/server-card.json",
            "statusCode": 404,
            "contentType": "text/plain; charset=UTF-8",
            "length": 9
          },
          {
            "path": "/.well-known/mcp/server-cards.json",
            "statusCode": 404,
            "contentType": "text/plain; charset=UTF-8",
            "length": 9
          },
          {
            "path": "/.well-known/mcp.json",
            "statusCode": 404,
            "contentType": "text/plain; charset=UTF-8",
            "length": 9
          }
        ]
      },
      "issue": "MCP Server Card was not found at the expected path.",
      "howToFix": "Publish an MCP server card with valid transports and make each advertised local endpoint answer an MCP initialize request."
    }
  ]
}

Agent Ease of UseMCPEmerging recommendation

mcp.json

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

33 Fail

Needs attention

mcp.json

Failed check
01

Issue

mcp.json was not found at the expected path.

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

0/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 "Fetch to find resource".

Validation steps

  1. Fetch to find resource

    mcp.json was not found at the expected path.

Evidence
{
  "failedStep": "fetch",
  "steps": [
    {
      "id": "fetch",
      "title": "Fetch to find resource",
      "status": "fail",
      "evidence": {
        "checked": [
          {
            "path": "/mcp.json",
            "statusCode": 404,
            "contentType": "text/plain; charset=UTF-8",
            "length": 9
          },
          {
            "path": "/.well-known/mcp.json",
            "statusCode": 404,
            "contentType": "text/plain; charset=UTF-8",
            "length": 9
          },
          {
            "path": "/.well-known/mcp/server-card.json",
            "statusCode": 404,
            "contentType": "text/plain; charset=UTF-8",
            "length": 9
          }
        ]
      },
      "issue": "mcp.json was not found at the expected path.",
      "howToFix": "Publish mcp.json or an MCP server card with serverInfo, protocolVersion, transport endpoint, and capabilities."
    }
  ]
}

Agent Ease of UseAPIEstablished

OpenAPI discovery

OpenAPI discovery failed at "Find valid OpenAPI document".

33 Fail

Needs attention

OpenAPI discovery

Failed check
01

Issue

OpenAPI YAML document did not match the expected shape. 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. 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/plain; charset=UTF-8",
            "valid": false,
            "issue": "OpenAPI YAML document did not match the expected shape. unsupported version: ; missing info block with title and version; missing paths block; no operations found.",
            "compatibleContentType": true,
            "format": "yaml",
            "version": "",
            "pathCount": 0,
            "operationCount": 0,
            "rawExcerpt": "Not found"
          },
          {
            "path": "/openapi.yaml",
            "statusCode": 404,
            "contentType": "text/plain; charset=UTF-8",
            "valid": false,
            "issue": "OpenAPI YAML document did not match the expected shape. unsupported version: ; missing info block with title and version; missing paths block; no operations found.",
            "compatibleContentType": true,
            "format": "yaml",
            "version": "",
            "pathCount": 0,
            "operationCount": 0,
            "rawExcerpt": "Not found"
          },
          {
            "path": "/swagger.json",
            "statusCode": 404,
            "contentType": "text/plain; charset=UTF-8",
            "valid": false,
            "issue": "OpenAPI YAML document did not match the expected shape. unsupported version: ; missing info block with title and version; missing paths block; no operations found.",
            "compatibleContentType": true,
            "format": "yaml",
            "version": "",
            "pathCount": 0,
            "operationCount": 0,
            "rawExcerpt": "Not found"
          },
          {
            "path": "/swagger.yaml",
            "statusCode": 404,
            "contentType": "text/plain; charset=UTF-8",
            "valid": false,
            "issue": "OpenAPI YAML document did not match the expected shape. unsupported version: ; missing info block with title and version; missing paths block; no operations found.",
            "compatibleContentType": true,
            "format": "yaml",
            "version": "",
            "pathCount": 0,
            "operationCount": 0,
            "rawExcerpt": "Not found"
          },
          {
            "path": "/api/openapi.json",
            "statusCode": 404,
            "contentType": "text/plain; charset=UTF-8",
            "valid": false,
            "issue": "OpenAPI YAML document did not match the expected shape. unsupported version: ; missing info block with title and version; missing paths block; no operations found.",
            "compatibleContentType": true,
            "format": "yaml",
            "version": "",
            "pathCount": 0,
            "operationCount": 0,
            "rawExcerpt": "Not found"
          },
          {
            "path": "/api/swagger.json",
            "statusCode": 404,
            "contentType": "text/plain; charset=UTF-8",
            "valid": false,
            "issue": "OpenAPI YAML document did not match the expected shape. unsupported version: ; missing info block with title and version; missing paths block; no operations found.",
            "compatibleContentType": true,
            "format": "yaml",
            "version": "",
            "pathCount": 0,
            "operationCount": 0,
            "rawExcerpt": "Not found"
          },
          {
            "path": "/docs/openapi.json",
            "statusCode": 404,
            "contentType": "text/plain; charset=UTF-8",
            "valid": false,
            "issue": "OpenAPI YAML document did not match the expected shape. unsupported version: ; missing info block with title and version; missing paths block; no operations found.",
            "compatibleContentType": true,
            "format": "yaml",
            "version": "",
            "pathCount": 0,
            "operationCount": 0,
            "rawExcerpt": "Not found"
          }
        ]
      },
      "issue": "OpenAPI YAML document did not match the expected shape. 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 DiscoverabilityContent ReadinessEstablished

Semantic HTML

Semantic HTML is missing or incomplete.

33 Fail

Needs attention

Semantic HTML

Failed check
01

Issue

Semantic HTML is incomplete: missing <main> landmark; missing <nav> landmark; missing <footer> landmark; invalid h1 (found 0).

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": false,
  "nav": false,
  "footer": false,
  "meaningfulH1": false,
  "headingOrder": true,
  "accessibleLinks": true,
  "accessibleButtons": true,
  "imageAltCoverage": true,
  "formAutocompleteCoverage": true,
  "details": {
    "inaccessibleLinks": [],
    "inaccessibleButtons": [],
    "missingAutocompleteInputs": [],
    "imagesMissingAlt": [],
    "skippedHeadingLevels": []
  },
  "counts": {
    "h1": 0,
    "headings": 0,
    "links": 0,
    "inaccessibleLinks": 0,
    "buttons": 0,
    "inaccessibleButtons": 0,
    "images": 0,
    "imagesWithAlt": 0,
    "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/plain; charset=UTF-8",
            "length": 9
          },
          {
            "path": "/webmcp.json",
            "statusCode": 404,
            "contentType": "text/plain; charset=UTF-8",
            "length": 9
          },
          {
            "path": "/mcp.json",
            "statusCode": 404,
            "contentType": "text/plain; charset=UTF-8",
            "length": 9
          }
        ]
      },
      "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."
    }
  ]
}

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/plain; charset=UTF-8",
            "length": 9
          },
          {
            "path": "/.well-known/a2a/agent-card.json",
            "statusCode": 404,
            "contentType": "text/plain; charset=UTF-8",
            "length": 9
          },
          {
            "path": "/agent-card.json",
            "statusCode": 404,
            "contentType": "text/plain; charset=UTF-8",
            "length": 9
          }
        ]
      },
      "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 Skills index

Agent Skills index failed at "Fetch to find resource".

20 Fail

Needs attention

Agent Skills index

Failed check
01

Issue

Agent Skills index was not found at the expected path.

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

0/100

Status

fail

Category

Skill Discovery

Maturity

Emerging recommendation

Goal

Publish an agent skills discovery index.

Result

Agent Skills index failed at "Fetch to find resource".

Validation steps

  1. Fetch to find resource

    Agent Skills index 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-skills/index.json",
            "statusCode": 404,
            "contentType": "text/plain; charset=UTF-8",
            "length": 9
          },
          {
            "path": "/.well-known/skills/index.json",
            "statusCode": 404,
            "contentType": "text/plain; charset=UTF-8",
            "length": 9
          }
        ]
      },
      "issue": "Agent Skills index was not found at the expected path.",
      "howToFix": "Publish an index with a non-empty skills array and reachable SKILL.md URLs."
    }
  ]
}

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/plain; charset=UTF-8",
            "length": 9
          },
          {
            "path": "/agent.json",
            "statusCode": 404,
            "contentType": "text/plain; charset=UTF-8",
            "length": 9
          }
        ]
      },
      "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/plain; charset=UTF-8",
            "length": 9
          },
          {
            "path": "/agents.json",
            "statusCode": 404,
            "contentType": "text/plain; charset=UTF-8",
            "length": 9
          }
        ]
      },
      "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 UseAPIEmerging recommendation

AI context endpoint

AI context endpoint failed at "Validate resource body".

17 Fail

Needs attention

AI context endpoint

Failed check
01

Issue

Content-Type "text/html" is not JSON, Markdown, or text/plain.

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

50/100

Status

fail

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 failed at "Validate resource body".

Validation steps

  1. Validate resource body

    Content-Type "text/html" is not JSON, Markdown, or text/plain.

Evidence
{
  "failedStep": "validate",
  "steps": [
    {
      "id": "fetch",
      "title": "Fetch discovery resource",
      "status": "pass",
      "evidence": {
        "path": "/api/ai/context",
        "statusCode": 200,
        "contentType": "text/html"
      }
    },
    {
      "id": "validate",
      "title": "Validate resource body",
      "status": "fail",
      "evidence": {
        "valid": false,
        "compatibleContentType": false,
        "issue": "Content-Type \"text/html\" is not JSON, Markdown, or text/plain.",
        "rawExcerpt": "\n<!DOCTYPE html>\n<html lang=\"en\">\n  <head>\n    <meta charset=\"UTF-8\" />\n    <meta name=\"viewport\" content=\"width=device-width, initial-scale=1.0\" />\n    <link rel=\"icon\" href=\"/prifina-logo.png\" type=\"image/png\">\n    \n    <!-- Google Analytics will be loaded dynamically after user consent -->\n    \n    <title>AI Twins - Your Personal AI Extension | Prifina</title>\n    <meta name=\"description\" content=\"Create your personal AI Twin with Prifina - the privacy-first platform for AI-powered digital identity and personal data ownership.\">\n    <meta name=\"author\" content=\"Prifina\" />\n    <meta name=\"keywords\" content=\"AI Twin, personal AI, data ownership, privacy-first AI, digital identity, AI platform\">\n    <link rel=\"canonical\" href=\"https://www.prifina.com/\" />\n\n    <!-- Open Graph -->\n    <met"
      },
      "issue": "Content-Type \"text/html\" is not JSON, Markdown, or text/plain.",
      "howToFix": "Publish a concise JSON or Markdown AI context endpoint describing the product, public actions, and machine-readable resources."
    }
  ]
}

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": "prifina.com",
        "probes": [
          {
            "name": "_index._agents.prifina.com",
            "found": false,
            "recordCount": 1,
            "records": [],
            "hasAlpn": false,
            "hasEndpoint": false
          },
          {
            "name": "_a2a._agents.prifina.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": "prifina.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."
    }
  ]
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AIO: Source and trust signals

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

6 Fail

Needs attention

AIO: Source and trust signals

Failed check
01

Issue

Missing AIO trust signals: publisher, freshnessDate, aboutOrContact, policyLinks.

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

20/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 20/100 and needs a fix.

Evidence
{
  "signals": {
    "author": true,
    "publisher": false,
    "freshnessDate": false,
    "aboutOrContact": false,
    "policyLinks": false
  },
  "missing": [
    "publisher",
    "freshnessDate",
    "aboutOrContact",
    "policyLinks"
  ],
  "authorMeta": "Prifina",
  "schemaAuthors": [],
  "schemaPublishers": [],
  "schemaDates": [],
  "visibleDates": [],
  "aboutLinks": [],
  "contactLinks": [],
  "privacyLinks": [],
  "score": 20,
  "weight": 20
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Answer evidence and trust

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

6 Fail

Needs attention

AEO: Answer evidence and trust

Failed check
01

Issue

Missing AIO trust signals: publisher, freshnessDate, aboutOrContact, policyLinks.

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

20/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 20/100 and needs a fix.

Evidence
{
  "signals": {
    "author": true,
    "publisher": false,
    "freshnessDate": false,
    "aboutOrContact": false,
    "policyLinks": false
  },
  "missing": [
    "publisher",
    "freshnessDate",
    "aboutOrContact",
    "policyLinks"
  ],
  "authorMeta": "Prifina",
  "schemaAuthors": [],
  "schemaPublishers": [],
  "schemaDates": [],
  "visibleDates": [],
  "aboutLinks": [],
  "contactLinks": [],
  "privacyLinks": [],
  "score": 20,
  "weight": 22
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

GEO: Explanatory content depth

GEO: Explanatory content depth scored 25/100 and needs a fix.

5 Fail

Needs attention

GEO: Explanatory content depth

Failed check
01

Issue

No substantial explanatory paragraphs were found.

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

25/100

Status

fail

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 25/100 and needs a fix.

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

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

GEO: Entity clarity

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

4 Warning

Needs attention

GEO: Entity clarity

Warning
01

Issue

Title/H1 terms missing from description: twins, extension.

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

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: Entity clarity scored 60/100 and needs improvement.

Evidence
{
  "title": "AI Twins - Your Personal AI Extension | Prifina",
  "h1": "",
  "description": "Create your personal AI Twin with Prifina - the privacy-first platform for AI-powered digital identity and personal data ownership.",
  "topicOverlap": 0.5,
  "topicTerms": [
    "twins",
    "personal",
    "extension",
    "prifina"
  ],
  "descriptionTerms": [
    "create",
    "personal",
    "twin",
    "prifina",
    "privacy",
    "first",
    "platform",
    "powered",
    "digital",
    "identity",
    "data",
    "ownership"
  ],
  "missingFromDescription": [
    "twins",
    "extension"
  ],
  "score": 60,
  "weight": 28
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AIO: Visible structured data match

AIO: Visible structured data match scored 50/100 and needs improvement.

4 Warning

Needs attention

AIO: Visible structured data match

Warning
01

Issue

2 structured-data value(s) were not found in visible page text.

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

50/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: Visible structured data match scored 50/100 and needs improvement.

Evidence
{
  "schemaCount": 2,
  "checkedFields": [
    {
      "path": "$[0].name",
      "value": "Prifina"
    },
    {
      "path": "$[0].description",
      "value": "Privacy-first AI Twins platform for personal data ownership and digital identity"
    },
    {
      "path": "$[1].name",
      "value": "Prifina"
    },
    {
      "path": "$[1].description",
      "value": "Privacy-first AI Twins platform for personal data ownership and digital identity"
    }
  ],
  "mismatches": [
    {
      "path": "$[0].description",
      "value": "Privacy-first AI Twins platform for personal data ownership and digital identity"
    },
    {
      "path": "$[1].description",
      "value": "Privacy-first AI Twins platform for personal data ownership and digital identity"
    }
  ],
  "score": 50,
  "weight": 18
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

GEO: AI crawler accessibility

GEO: AI crawler accessibility scored 65/100 and needs improvement.

3 Warning

Needs attention

GEO: AI crawler accessibility

Warning
01

Issue

Only 7 words of Chrome-rendered body text were detected.

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: AI crawler accessibility

Score

65/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: AI crawler accessibility scored 65/100 and needs improvement.

Evidence
{
  "textWords": 7,
  "htmlBytes": 17433,
  "robots": {
    "checkedCrawlers": [
      "gptbot",
      "chatgpt-user",
      "claudebot",
      "perplexitybot",
      "google-extended"
    ],
    "blocked": [],
    "allows": true
  },
  "schemaBlocks": 2,
  "finalUrl": "https://prifina.com/",
  "robotsExcerpt": "# Default: everything public is crawlable\nUser-agent: *\nDisallow: /admin/\nDisallow: /api/private/\nDisallow: /drafts/\nDisallow: /x7k9m2p\nDisallow: /interface-9x2b7\nDisallow: /_redirects\nDisallow: /_headers\nAllow: /\n\n# --- Search engines ---\nUser-agent: Googlebot\nAllow: /\nUser-agent: bingbot\nAllow: /\nUser-agent: DuckDuckBot\nAllow: /\nUser-agent: Applebot\nAllow: /\nUser-agent: Amazonbot\nAllow: /\n\n# --- AI + assistant crawlers ---\nUser-agent: GPTBot\nAllow: /\nUser-agent: ChatGPT-User\nAllow: /\nUser-agent: ClaudeBot\nAllow: /\nUser-agent: Claude-User\nAllow: /\nUser-agent: PerplexityBot\nAllow: /\n\n# --- Social/link unfurlers ---\nUser-agent: facebookexternalhit\nAllow: /\nUser-agent: Facebot\nAllow: /\nUser-agent: LinkedInBot\nAllow: /\nUser-agent: Twitterbot\nAllow: /\nUser-agent: Slackbot\nAllow: /\nUser-agent: ",
  "score": 65,
  "weight": 26
}

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": 0,
  "questionH2s": [],
  "hasFaq": false,
  "score": 50,
  "weight": 18
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Entity and definition clarity

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

3 Warning

Needs attention

AEO: Entity and definition clarity

Warning
01

Issue

Entity or definition gaps: twins, extension.

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

53/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 53/100 and needs improvement.

Evidence
{
  "title": "AI Twins - Your Personal AI Extension | Prifina",
  "h1": "",
  "description": "Create your personal AI Twin with Prifina - the privacy-first platform for AI-powered digital identity and personal data ownership.",
  "topicOverlap": 0.5,
  "definitionCount": 0,
  "topicTerms": [
    "twins",
    "personal",
    "extension",
    "prifina"
  ],
  "descriptionTerms": [
    "create",
    "personal",
    "twin",
    "prifina",
    "privacy",
    "first",
    "platform",
    "powered",
    "digital",
    "identity",
    "data",
    "ownership"
  ],
  "missingFromDescription": [
    "twins",
    "extension"
  ],
  "score": 53,
  "weight": 18
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Answer-first sections

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

2 Warning

Needs attention

AEO: Answer-first sections

Warning
01

Issue

AEO readiness is incomplete.

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

80/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 80/100 and needs improvement.

Evidence
{
  "sectionCount": 0,
  "passing": 0,
  "failing": [],
  "score": 80,
  "weight": 28
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

GEO: Extraction-friendly structure

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

2 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, optional visible FAQ or FAQPage schema, clear definition sentence using "is", "means", or "refers to" where natural.

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

80/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 80/100 and needs improvement.

Evidence
{
  "hasSummary": false,
  "tableCount": 0,
  "tablesWithHead": 0,
  "tablesMissingThead": [],
  "orderedLists": 1,
  "hasFaq": false,
  "definitionPatterns": 0,
  "schemaBlocks": 2,
  "missingSignals": [
    "optional top summary / TL;DR / key takeaways block",
    "table with <thead> only if the page already has tabular/comparative data",
    "optional visible FAQ or FAQPage schema",
    "clear definition sentence using \"is\", \"means\", or \"refers to\" where natural"
  ],
  "score": 80,
  "weight": 24
}

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.prifina.com/",
  "finalUrl": "https://prifina.com/",
  "canonicalScore": 60,
  "score": 80,
  "weight": 18
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Extractable visible copy

AEO: Extractable visible copy scored 35/100 and needs a fix.

1 Fail

Needs attention

AEO: Extractable visible copy

Failed check
01

Issue

Only 7 visible words were detected for answer extraction.

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: Extractable visible copy

Score

35/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: Extractable visible copy scored 35/100 and needs a fix.

Evidence
{
  "visibleWords": 7,
  "schemaCount": 2,
  "score": 35,
  "weight": 6
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AIO: Page experience for AIO

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

1 Warning

Needs attention

AIO: Page experience for AIO

Warning
01

Issue

Only 7 words of visible rendered text were 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: Page experience for AIO

Score

75/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 75/100 and needs improvement.

Evidence
{
  "viewportContent": "width=device-width, initial-scale=1.0",
  "visibleWords": 7,
  "htmlBytes": 17433,
  "imagesMissingDimensions": [],
  "possibleDialogs": [],
  "score": 75,
  "weight": 10
}

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": [],
  "expected": [
    {
      "id": "what",
      "label": "What is AI Twins - Your Personal AI Extension?",
      "pattern": {}
    },
    {
      "id": "how",
      "label": "How does AI Twins - Your Personal AI Extension work?",
      "pattern": {}
    },
    {
      "id": "benefits",
      "label": "Why use AI Twins - Your Personal AI Extension?",
      "pattern": {}
    },
    {
      "id": "cost",
      "label": "Is AI Twins - Your Personal AI Extension free or paid?",
      "pattern": {}
    },
    {
      "id": "compare",
      "label": "How does AI Twins - Your Personal AI Extension compare with alternatives?",
      "pattern": {}
    }
  ],
  "missing": [
    {
      "id": "what",
      "label": "What is AI Twins - Your Personal AI Extension?",
      "pattern": {}
    },
    {
      "id": "how",
      "label": "How does AI Twins - Your Personal AI Extension work?",
      "pattern": {}
    },
    {
      "id": "benefits",
      "label": "Why use AI Twins - Your Personal AI Extension?",
      "pattern": {}
    },
    {
      "id": "cost",
      "label": "Is AI Twins - Your Personal AI Extension free or paid?",
      "pattern": {}
    },
    {
      "id": "compare",
      "label": "How does AI Twins - Your Personal AI Extension compare with alternatives?",
      "pattern": {}
    }
  ],
  "score": 70,
  "weight": 8
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AIO: Answer block readiness

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

1 Warning

Needs attention

AIO: Answer block readiness

Warning
01

Issue

Canonical does not self-reference the scanned page.

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

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: Answer block readiness scored 80/100 and needs improvement.

Evidence
{
  "sectionCount": 0,
  "passing": 0,
  "failing": [],
  "score": 80,
  "weight": 8
}

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": [],
  "expected": [
    {
      "id": "what",
      "label": "What is AI Twins - Your Personal AI Extension?",
      "pattern": {}
    },
    {
      "id": "how",
      "label": "How does AI Twins - Your Personal AI Extension work?",
      "pattern": {}
    },
    {
      "id": "benefits",
      "label": "Why use AI Twins - Your Personal AI Extension?",
      "pattern": {}
    },
    {
      "id": "cost",
      "label": "Is AI Twins - Your Personal AI Extension free or paid?",
      "pattern": {}
    },
    {
      "id": "compare",
      "label": "How does AI Twins - Your Personal AI Extension compare with alternatives?",
      "pattern": {}
    }
  ],
  "missing": [
    {
      "id": "what",
      "label": "What is AI Twins - Your Personal AI Extension?",
      "pattern": {}
    },
    {
      "id": "how",
      "label": "How does AI Twins - Your Personal AI Extension work?",
      "pattern": {}
    },
    {
      "id": "benefits",
      "label": "Why use AI Twins - Your Personal AI Extension?",
      "pattern": {}
    },
    {
      "id": "cost",
      "label": "Is AI Twins - Your Personal AI Extension free or paid?",
      "pattern": {}
    },
    {
      "id": "compare",
      "label": "How does AI Twins - Your Personal AI Extension compare with alternatives?",
      "pattern": {}
    }
  ],
  "score": 70,
  "weight": 4
}

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

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": 0,
  "questionH2s": 0,
  "hasFaq": false,
  "nonQuestionH2s": [],
  "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."
    }
  ]
}

Performance and AccessibilityAccessibilityBrowser audit

Form elements do not have associated labels

100 Fail

Check name

Form elements do not have associated labels

Score

0/100

Status

fail

Device

desktop

Category

Accessibility

Fix guidance

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. [Learn more about form element labels](https://dequeuniversity.com/rules/axe/4.11/label).

Evidence
{
  "description": "Labels ensure that form controls are announced properly by assistive technologies, like screen readers. [Learn more about form element labels](https://dequeuniversity.com/rules/axe/4.11/label)."
}

Performance and AccessibilityPerformanceBrowser audit

LCP request discovery

25 Fail

Check name

LCP request discovery

Score

0/100

Status

fail

Device

desktop

Category

Performance

Fix guidance

[Optimize LCP](https://developer.chrome.com/docs/performance/insights/lcp-discovery) by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

Evidence
{
  "description": "[Optimize LCP](https://developer.chrome.com/docs/performance/insights/lcp-discovery) by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading"
}

Performance and AccessibilityPerformanceBrowser audit

Touch targets do not have sufficient size or spacing.

25 Fail

Check name

Touch targets do not have sufficient size or spacing.

Score

0/100

Status

fail

Device

desktop

Category

Performance

Fix guidance

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. [Learn more about touch targets](https://dequeuniversity.com/rules/axe/4.11/target-size).

Evidence
{
  "description": "Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. [Learn more about touch targets](https://dequeuniversity.com/rules/axe/4.11/target-size)."
}

Performance and AccessibilityPerformanceBrowser audit

Use efficient cache lifetimes

25 Fail

Check name

Use efficient cache lifetimes

Score

0/100

Status

fail

Device

desktop

Category

Performance

Estimated savings

Est savings of 5,484 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 5,484 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

Loading performance

6 Fail

Check name

Loading performance

Score

76/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": "max-potential-fid",
      "title": "Max Potential First Input Delay",
      "score": 100,
      "displayValue": "50 ms",
      "numericValue": 49
    },
    {
      "id": "speed-index",
      "title": "Speed Index",
      "score": 1,
      "displayValue": "6.0 s",
      "numericValue": 5960.532261082217
    },
    {
      "id": "first-contentful-paint",
      "title": "First Contentful Paint",
      "score": 96,
      "displayValue": "0.7 s",
      "numericValue": 741.5
    },
    {
      "id": "interactive",
      "title": "Time to Interactive",
      "score": 79,
      "displayValue": "3.0 s",
      "numericValue": 3042.5
    },
    {
      "id": "total-blocking-time",
      "title": "Total Blocking Time",
      "score": 100,
      "displayValue": "0 ms",
      "numericValue": 0
    },
    {
      "id": "network-rtt",
      "title": "Network Round Trip Times",
      "score": 100,
      "displayValue": "0 ms",
      "numericValue": 0.016145799356969217
    },
    {
      "id": "server-response-time",
      "title": "Initial server response time was short",
      "score": 100,
      "displayValue": "Root document took 0 ms",
      "numericValue": 2
    },
    {
      "id": "largest-contentful-paint",
      "title": "Largest Contentful Paint",
      "score": 33,
      "displayValue": "3.0 s",
      "numericValue": 3042.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
59/100Level 3, Bot-AwareCurrent report
prifina.com AI SEO Report: 59/100 (Level 3, Bot-Aware)