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
AIDiscoverability60%Agent Easeof Use10%Security& Trust60%GEO, AIO, AEO78%SEO92%Performance& Accessibility75%
  • AI Discoverability 60 out of 100
  • Agent Ease of Use 10 out of 100
  • Security & Trust 60 out of 100
  • GEO, AIO and AEO 78 out of 100
  • SEO 92 out of 100
  • Performance and Accessibility 75 out of 100

CAPTURED SCREENSHOT

Captured website desktop screenshot

What AI sees of your website

Aptly | AI Operations Layer for Property Management favicon

Aptly | AI Operations Layer for Property Management

Connect your systems, replace fragmented tools, and orchestrate every workflow with AI. The complete operating layer for modern property management teams.

Next step

Turn this report into a fix workflow

19 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
60
Needs work12111View details
Discoverability
86
Mostly ready630View details
Content Readiness
54
Needs work551View details
Bot Access Control
33
Priority fix130View details
Agent Ease of Use
10
Priority fix17221View details
API
0
Priority fix060View 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
78
Mostly ready6212View details
GEO Readiness
85
Mostly ready204
AIO Readiness
78
Mostly ready214View details
AEO Readiness
70
Needs work214View details
SEO
92
Strong1010View details
SEO
92
Strong1010View details
Security & Trust
60
Needs work720View details
Security & Trust
60
Needs work320View details
AI Training Exposure
Not Applicable
Not Applicable400
Performance and Accessibility
75
Mostly ready2142View details
Performance
68
Needs work1442View details
Accessibility
87
Mostly ready700

Prioritized recommendations

Issues ranked by score impact

39 items need attention

AI DiscoverabilityDiscoverabilityEstablished

Link headers

Link headers failed at "Find useful Link headers".

100 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."
    }
  ]
}

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><script type=\"c99addf599c156fb0190a5e6-text/javascript\">\n    window.__loadWebflow=function(){\n      if(window.__webflowLoaded)return;\n      if(/^\\/blog\\/[^/]+/.test(location.pathname))return;\n      if(!document.body){\n        document.addEventListener('DOMContentLoaded',function(){window.__loadWebflow();});\n        return;\n      }\n      window.__webflowLoaded=true;\n      var jq=document.createElement('script');\n      jq.src='https://d3e54v103j8qbb.cloudfront.net/js/jquery-3.5.1.min.dc5e7f18c8.js?site=68f83a36b62d8044fc46cd26';\n      jq.onload=function(){\n        var wf=document.createElement('script');\n        wf.src='https://cdn.prod.website-files.com/68f83a36b62d8044fc46cd26/js/webflow.c50259b6b907cae5dc9fc088b90729da.js';\n        document.body.appen"
      },
      "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 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": "upgrade-insecure-requests"
}

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=2592000; includeSubDomains; preload"
}

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><script type=\"284a186698ca86d393a9b31e-text/javascript\">\n    window.__loadWebflow=function(){\n      if(window.__webflowLoaded)return;\n      if(/^\\/blog\\/[^/]+/.test(location.pathname))return;\n      if(!document.body){\n        document.addEventListener('DOMContentLoaded',function(){window.__loadWebflow();});\n        return;\n      }\n      window.__webflowLoaded=true;\n      var jq=document.createElement('script');\n      jq.src='https://d3e54v103j8qbb.cloudfront.net/js/jquery-3.5.1.min.dc5e7f18c8.js?site=68f83a36b62d8044fc46cd26';\n      jq.onload=function(){\n        var wf=document.createElement('script');\n        wf.src='https://cdn.prod.website-files.com/68f83a36b62d8044fc46cd26/js/webflow.c50259b6b907cae5dc9fc088b90729da.js';\n        document.body.appen"
          },
          {
            "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><script type=\"0d1412575cae56448b43fc0f-text/javascript\">\n    window.__loadWebflow=function(){\n      if(window.__webflowLoaded)return;\n      if(/^\\/blog\\/[^/]+/.test(location.pathname))return;\n      if(!document.body){\n        document.addEventListener('DOMContentLoaded',function(){window.__loadWebflow();});\n        return;\n      }\n      window.__webflowLoaded=true;\n      var jq=document.createElement('script');\n      jq.src='https://d3e54v103j8qbb.cloudfront.net/js/jquery-3.5.1.min.dc5e7f18c8.js?site=68f83a36b62d8044fc46cd26';\n      jq.onload=function(){\n        var wf=document.createElement('script');\n        wf.src='https://cdn.prod.website-files.com/68f83a36b62d8044fc46cd26/js/webflow.c50259b6b907cae5dc9fc088b90729da.js';\n        document.body.appen"
          },
          {
            "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><script type=\"af21de249edb33a92f2e944f-text/javascript\">\n    window.__loadWebflow=function(){\n      if(window.__webflowLoaded)return;\n      if(/^\\/blog\\/[^/]+/.test(location.pathname))return;\n      if(!document.body){\n        document.addEventListener('DOMContentLoaded',function(){window.__loadWebflow();});\n        return;\n      }\n      window.__webflowLoaded=true;\n      var jq=document.createElement('script');\n      jq.src='https://d3e54v103j8qbb.cloudfront.net/js/jquery-3.5.1.min.dc5e7f18c8.js?site=68f83a36b62d8044fc46cd26';\n      jq.onload=function(){\n        var wf=document.createElement('script');\n        wf.src='https://cdn.prod.website-files.com/68f83a36b62d8044fc46cd26/js/webflow.c50259b6b907cae5dc9fc088b90729da.js';\n        document.body.appen"
          },
          {
            "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><script type=\"cc678b0d2f891dea0fcd7ec9-text/javascript\">\n    window.__loadWebflow=function(){\n      if(window.__webflowLoaded)return;\n      if(/^\\/blog\\/[^/]+/.test(location.pathname))return;\n      if(!document.body){\n        document.addEventListener('DOMContentLoaded',function(){window.__loadWebflow();});\n        return;\n      }\n      window.__webflowLoaded=true;\n      var jq=document.createElement('script');\n      jq.src='https://d3e54v103j8qbb.cloudfront.net/js/jquery-3.5.1.min.dc5e7f18c8.js?site=68f83a36b62d8044fc46cd26';\n      jq.onload=function(){\n        var wf=document.createElement('script');\n        wf.src='https://cdn.prod.website-files.com/68f83a36b62d8044fc46cd26/js/webflow.c50259b6b907cae5dc9fc088b90729da.js';\n        document.body.appen"
          },
          {
            "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><script type=\"ca2f6932398d169c019e9f7d-text/javascript\">\n    window.__loadWebflow=function(){\n      if(window.__webflowLoaded)return;\n      if(/^\\/blog\\/[^/]+/.test(location.pathname))return;\n      if(!document.body){\n        document.addEventListener('DOMContentLoaded',function(){window.__loadWebflow();});\n        return;\n      }\n      window.__webflowLoaded=true;\n      var jq=document.createElement('script');\n      jq.src='https://d3e54v103j8qbb.cloudfront.net/js/jquery-3.5.1.min.dc5e7f18c8.js?site=68f83a36b62d8044fc46cd26';\n      jq.onload=function(){\n        var wf=document.createElement('script');\n        wf.src='https://cdn.prod.website-files.com/68f83a36b62d8044fc46cd26/js/webflow.c50259b6b907cae5dc9fc088b90729da.js';\n        document.body.appen"
          },
          {
            "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><script type=\"bac6106b86e65c1c7db19654-text/javascript\">\n    window.__loadWebflow=function(){\n      if(window.__webflowLoaded)return;\n      if(/^\\/blog\\/[^/]+/.test(location.pathname))return;\n      if(!document.body){\n        document.addEventListener('DOMContentLoaded',function(){window.__loadWebflow();});\n        return;\n      }\n      window.__webflowLoaded=true;\n      var jq=document.createElement('script');\n      jq.src='https://d3e54v103j8qbb.cloudfront.net/js/jquery-3.5.1.min.dc5e7f18c8.js?site=68f83a36b62d8044fc46cd26';\n      jq.onload=function(){\n        var wf=document.createElement('script');\n        wf.src='https://cdn.prod.website-files.com/68f83a36b62d8044fc46cd26/js/webflow.c50259b6b907cae5dc9fc088b90729da.js';\n        document.body.appen"
          },
          {
            "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><script type=\"ab9b8f22aad436b2624672d2-text/javascript\">\n    window.__loadWebflow=function(){\n      if(window.__webflowLoaded)return;\n      if(/^\\/blog\\/[^/]+/.test(location.pathname))return;\n      if(!document.body){\n        document.addEventListener('DOMContentLoaded',function(){window.__loadWebflow();});\n        return;\n      }\n      window.__webflowLoaded=true;\n      var jq=document.createElement('script');\n      jq.src='https://d3e54v103j8qbb.cloudfront.net/js/jquery-3.5.1.min.dc5e7f18c8.js?site=68f83a36b62d8044fc46cd26';\n      jq.onload=function(){\n        var wf=document.createElement('script');\n        wf.src='https://cdn.prod.website-files.com/68f83a36b62d8044fc46cd26/js/webflow.c50259b6b907cae5dc9fc088b90729da.js';\n        document.body.appen"
          }
        ]
      },
      "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": 26929
          }
        ]
      },
      "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 "accept-encoding".

  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": "accept-encoding"
      },
      "issue": "Markdown negotiation is missing Vary: Accept; current Vary header is \"accept-encoding\".",
      "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": 3003,
        "excerpt": "<!DOCTYPE html><html lang=\"en\"> <head><script type=\"f8d572817862920b63ab9df9-text/javascript\">\n    window.__loadWebflow=function(){\n      if(window.__webflowLoaded)return;\n      if(/^\\/blog\\/[^/]+/.test(location.pathname))return;\n      if(!",
        "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."
    }
  ]
}

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/html; charset=utf-8",
            "length": 26929
          },
          {
            "path": "/.well-known/mcp/server-cards.json",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "length": 26929
          },
          {
            "path": "/.well-known/mcp.json",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "length": 26929
          }
        ]
      },
      "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/html; charset=utf-8",
            "length": 27848
          },
          {
            "path": "/.well-known/mcp.json",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "length": 26929
          },
          {
            "path": "/.well-known/mcp/server-card.json",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "length": 26929
          }
        ]
      },
      "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."
    }
  ]
}

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 <nav> landmark.

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": false,
  "footer": true,
  "meaningfulH1": true,
  "headingOrder": true,
  "accessibleLinks": true,
  "accessibleButtons": true,
  "imageAltCoverage": true,
  "formAutocompleteCoverage": true,
  "details": {
    "inaccessibleLinks": [],
    "inaccessibleButtons": [],
    "missingAutocompleteInputs": [],
    "imagesMissingAlt": [],
    "skippedHeadingLevels": []
  },
  "counts": {
    "h1": 1,
    "headings": 11,
    "links": 24,
    "inaccessibleLinks": 0,
    "buttons": 0,
    "inaccessibleButtons": 0,
    "images": 3,
    "imagesWithAlt": 3,
    "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": 26929
          },
          {
            "path": "/webmcp.json",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "length": 27848
          },
          {
            "path": "/mcp.json",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "length": 27848
          }
        ]
      },
      "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 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": "Tue, 09 Jun 2026 16:16:43 GMT",
  "schemaDates": [],
  "metaDateCount": 0,
  "timeDateCount": 0
}

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": 26929
          },
          {
            "path": "/.well-known/a2a/agent-card.json",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "length": 26929
          },
          {
            "path": "/agent-card.json",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "length": 27848
          }
        ]
      },
      "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/html; charset=utf-8",
            "length": 26929
          },
          {
            "path": "/.well-known/skills/index.json",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "length": 26929
          }
        ]
      },
      "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/html; charset=utf-8",
            "length": 26929
          },
          {
            "path": "/agent.json",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "length": 27848
          }
        ]
      },
      "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": 26929
          },
          {
            "path": "/agents.json",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "length": 27848
          }
        ]
      },
      "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 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": "www.getaptly.com",
        "probes": [
          {
            "name": "_index._agents.www.getaptly.com",
            "found": false,
            "recordCount": 1,
            "records": [],
            "hasAlpn": false,
            "hasEndpoint": false
          },
          {
            "name": "_a2a._agents.www.getaptly.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": "www.getaptly.com",
            "dnssecTypes": [],
            "dnssecRecordCount": 0
          },
          {
            "name": "getaptly.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 40/100 and needs a fix.

6 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",
      "text": "About Us",
      "html": "<a href=\"/company\" class=\"sf-link\" data-testid=\"link-footer-about-us\">About Us</a>"
    },
    {
      "href": "https://www.linkedin.com/company/getaptly/",
      "text": "",
      "html": "<a href=\"https://www.linkedin.com/company/getaptly/\" target=\"_blank\" rel=\"noopener noreferrer\" aria-label=\"Aptly on LinkedIn\" class=\"social-icon-link\" data-testid=\"link-linkedin\"><svg width=\"24\" height=\"24\" viewBox=\"0 0 24 24\" fill=\"none\" xmlns=\"http://www.w3.org/2000/svg\"><path fill-rule=\"evenodd\" clip-rule=\"evenodd\" d=\"M4.5 3C3.67157 3 3 3.67157 3 4.5V19.5C3 20.3284 3.67157 21 4.5 21H19.5C20.3284 21 21 20.3284 21 19.5V4.5C21 3.67157 20.3284 3 19.5 3H4.5ZM8.52076 7.00272C8.52639 7.95897 7.81..."
    }
  ],
  "contactLinks": [],
  "privacyLinks": [
    {
      "href": "/privacy-policy",
      "text": "Privacy Policy",
      "html": "<a href=\"/privacy-policy\" class=\"sf-legal-link\" data-testid=\"link-privacy-policy\">Privacy Policy</a>"
    },
    {
      "href": "/terms",
      "text": "Terms of Service",
      "html": "<a href=\"/terms\" class=\"sf-legal-link\" data-testid=\"link-terms\">Terms of Service</a>"
    }
  ],
  "score": 40,
  "weight": 20
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Answer evidence and trust

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

6 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",
      "text": "About Us",
      "html": "<a href=\"/company\" class=\"sf-link\" data-testid=\"link-footer-about-us\">About Us</a>"
    },
    {
      "href": "https://www.linkedin.com/company/getaptly/",
      "text": "",
      "html": "<a href=\"https://www.linkedin.com/company/getaptly/\" target=\"_blank\" rel=\"noopener noreferrer\" aria-label=\"Aptly on LinkedIn\" class=\"social-icon-link\" data-testid=\"link-linkedin\"><svg width=\"24\" height=\"24\" viewBox=\"0 0 24 24\" fill=\"none\" xmlns=\"http://www.w3.org/2000/svg\"><path fill-rule=\"evenodd\" clip-rule=\"evenodd\" d=\"M4.5 3C3.67157 3 3 3.67157 3 4.5V19.5C3 20.3284 3.67157 21 4.5 21H19.5C20.3284 21 21 20.3284 21 19.5V4.5C21 3.67157 20.3284 3 19.5 3H4.5ZM8.52076 7.00272C8.52639 7.95897 7.81..."
    }
  ],
  "contactLinks": [],
  "privacyLinks": [
    {
      "href": "/privacy-policy",
      "text": "Privacy Policy",
      "html": "<a href=\"/privacy-policy\" class=\"sf-legal-link\" data-testid=\"link-privacy-policy\">Privacy Policy</a>"
    },
    {
      "href": "/terms",
      "text": "Terms of Service",
      "html": "<a href=\"/terms\" class=\"sf-legal-link\" data-testid=\"link-terms\">Terms of Service</a>"
    }
  ],
  "score": 40,
  "weight": 22
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Answer-first sections

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

5 Warning

Needs attention

AEO: Answer-first sections

Warning
01

Issue

10 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": 10,
  "passing": 0,
  "failing": [
    {
      "heading": "The complete operating system for modern property teams",
      "headingHtml": "<h2>The complete operating system for modern property teams</h2>",
      "firstParagraph": "Everything your team needs to communicate, automate, and grow — unified in one intelligent platform.",
      "paragraphHtml": "<p>Everything your team needs to communicate, automate, and grow &#x2014; unified in one intelligent platform.</p>",
      "words": 14,
      "direct": false,
      "issue": "First paragraph is 14 words and does not look like a concise direct answer."
    },
    {
      "heading": "AI Agents",
      "headingHtml": "<h3>AI Agents</h3>",
      "firstParagraph": "Intelligent digital teammates that handle leasing inquiries, maintenance requests, and resident communication 24/7.",
      "paragraphHtml": "<p>Intelligent digital teammates that handle leasing inquiries, maintenance requests, and resident communication 24/7.</p>",
      "words": 14,
      "direct": false,
      "issue": "First paragraph is 14 words and does not look like a concise direct answer."
    },
    {
      "heading": "Unified Inbox",
      "headingHtml": "<h3>Unified Inbox</h3>",
      "firstParagraph": "Calls, texts, emails, and chat — all in one place with full context and AI-powered suggestions.",
      "paragraphHtml": "<p>Calls, texts, emails, and chat &#x2014; all in one place with full context and AI-powered suggestions.</p>",
      "words": 15,
      "direct": false,
      "issue": "First paragraph is 15 words and does not look like a concise direct answer."
    },
    {
      "heading": "Workflow Automation",
      "headingHtml": "<h3>Workflow Automation</h3>",
      "firstParagraph": "Build, trigger, and optimize any recurring process from renewals to inspections to owner updates.",
      "paragraphHtml": "<p>Build, trigger, and optimize any recurring process from renewals to inspections to owner updates.</p>",
      "words": 14,
      "direct": false,
      "issue": "First paragraph is 14 words and does not look like a concise direct answer."
    },
    {
      "heading": "Smart Routing",
      "headingHtml": "<h3>Smart Routing</h3>",
      "firstParagraph": "Automatically route requests to the right person based on property, issue type, and team availability.",
      "paragraphHtml": "<p>Automatically route requests to the right person based on property, issue type, and team availability.</p>",
      "words": 15,
      "direct": false,
      "issue": "First paragraph is 15 words and does not look like a concise direct answer."
    },
    {
      "heading": "How it works",
      "headingHtml": "<h2>How it works</h2>",
      "firstParagraph": "Aptly integrates with your existing property management software and becomes the AI-powered operations layer on top.",
      "paragraphHtml": "<p>Aptly integrates with your existing property management software and becomes the AI-powered operations layer on top.</p>",
      "words": 16,
      "direct": false,
      "issue": "First paragraph is 16 words and does not look like a concise direct answer."
    },
    {
      "heading": "1. Connect",
      "headingHtml": "<h3>1. Connect</h3>",
      "firstParagraph": "Plug into your PMS (Yardi, RealPage, Entrata, AppFolio, and more) with bidirectional data sync.",
      "paragraphHtml": "<p>Plug into your PMS (Yardi, RealPage, Entrata, AppFolio, and more) with bidirectional data sync.</p>",
      "words": 14,
      "direct": false,
      "issue": "First paragraph is 14 words and does not look like a concise direct answer."
    },
    {
      "heading": "2. Automate",
      "headingHtml": "<h3>2. Automate</h3>",
      "firstParagraph": "Set up AI agents and automated workflows for leasing, maintenance, collections, and resident support.",
      "paragraphHtml": "<p>Set up AI agents and automated workflows for leasing, maintenance, collections, and resident support.</p>",
      "words": 14,
      "direct": false,
      "issue": "First paragraph is 14 words and does not look like a concise direct answer."
    },
    {
      "heading": "3. Optimize",
      "headingHtml": "<h3>3. Optimize</h3>",
      "firstParagraph": "Track performance with real-time analytics and continuously improve your operations.",
      "paragraphHtml": "<p>Track performance with real-time analytics and continuously improve your operations.</p>",
      "words": 10,
      "direct": false,
      "issue": "First paragraph is 10 words and does not look like a concise direct answer."
    },
    {
      "heading": "Ready to see the future of property management?",
      "headingHtml": "<h2>Ready to see the future of property management?</h2>",
      "firstParagraph": "Book a demo to discover how Aptly can transform your property management operations with AI-powered automation.",
      "paragraphHtml": "<p>Book a demo to discover how Aptly can transform your property management operations with AI-powered automation.</p>",
      "words": 16,
      "direct": false,
      "issue": "First paragraph is 16 words and does not look like a concise direct answer."
    }
  ],
  "score": 65,
  "weight": 28
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

GEO: Extraction-friendly structure

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

3 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, 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

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: Extraction-friendly structure scored 75/100 and needs improvement.

Evidence
{
  "hasSummary": false,
  "tableCount": 0,
  "tablesWithHead": 0,
  "tablesMissingThead": [],
  "orderedLists": 0,
  "hasFaq": true,
  "definitionPatterns": 0,
  "schemaBlocks": 6,
  "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",
    "clear definition sentence using \"is\", \"means\", or \"refers to\" where natural"
  ],
  "score": 75,
  "weight": 24
}

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

AEO: Entity and definition clarity

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

2 Warning

Needs attention

AEO: Entity and definition clarity

Warning
01

Issue

Entity or definition gaps: aptly, operations, intelligent.

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

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

Evidence
{
  "title": "Aptly | AI Operations Layer for Property Management",
  "h1": "The intelligent operations layer for property management",
  "description": "Connect your systems, replace fragmented tools, and orchestrate every workflow with AI. The complete operating layer for modern property management teams.",
  "topicOverlap": 0.5,
  "definitionCount": 0,
  "topicTerms": [
    "aptly",
    "operations",
    "layer",
    "property",
    "management",
    "intelligent"
  ],
  "descriptionTerms": [
    "connect",
    "systems",
    "replace",
    "fragmented",
    "tools",
    "orchestrate",
    "every",
    "workflow",
    "complete",
    "operating",
    "layer",
    "modern",
    "property",
    "management",
    "teams"
  ],
  "missingFromDescription": [
    "aptly",
    "operations",
    "intelligent"
  ],
  "score": 73,
  "weight": 18
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

GEO: Entity clarity

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

2 Warning

Needs attention

GEO: Entity clarity

Warning
01

Issue

Title/H1 terms missing from description: aptly, operations, intelligent.

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

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

Evidence
{
  "title": "Aptly | AI Operations Layer for Property Management",
  "h1": "The intelligent operations layer for property management",
  "description": "Connect your systems, replace fragmented tools, and orchestrate every workflow with AI. The complete operating layer for modern property management teams.",
  "topicOverlap": 0.5,
  "topicTerms": [
    "aptly",
    "operations",
    "layer",
    "property",
    "management",
    "intelligent"
  ],
  "descriptionTerms": [
    "connect",
    "systems",
    "replace",
    "fragmented",
    "tools",
    "orchestrate",
    "every",
    "workflow",
    "complete",
    "operating",
    "layer",
    "modern",
    "property",
    "management",
    "teams"
  ],
  "missingFromDescription": [
    "aptly",
    "operations",
    "intelligent"
  ],
  "score": 85,
  "weight": 28
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AIO: Answer block readiness

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

2 Warning

Needs attention

AIO: Answer block readiness

Warning
01

Issue

10 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": 10,
  "passing": 0,
  "failing": [
    {
      "heading": "The complete operating system for modern property teams",
      "headingHtml": "<h2>The complete operating system for modern property teams</h2>",
      "firstParagraph": "Everything your team needs to communicate, automate, and grow — unified in one intelligent platform.",
      "paragraphHtml": "<p>Everything your team needs to communicate, automate, and grow &#x2014; unified in one intelligent platform.</p>",
      "words": 14,
      "direct": false,
      "issue": "First paragraph is 14 words and does not look like a concise direct answer."
    },
    {
      "heading": "AI Agents",
      "headingHtml": "<h3>AI Agents</h3>",
      "firstParagraph": "Intelligent digital teammates that handle leasing inquiries, maintenance requests, and resident communication 24/7.",
      "paragraphHtml": "<p>Intelligent digital teammates that handle leasing inquiries, maintenance requests, and resident communication 24/7.</p>",
      "words": 14,
      "direct": false,
      "issue": "First paragraph is 14 words and does not look like a concise direct answer."
    },
    {
      "heading": "Unified Inbox",
      "headingHtml": "<h3>Unified Inbox</h3>",
      "firstParagraph": "Calls, texts, emails, and chat — all in one place with full context and AI-powered suggestions.",
      "paragraphHtml": "<p>Calls, texts, emails, and chat &#x2014; all in one place with full context and AI-powered suggestions.</p>",
      "words": 15,
      "direct": false,
      "issue": "First paragraph is 15 words and does not look like a concise direct answer."
    },
    {
      "heading": "Workflow Automation",
      "headingHtml": "<h3>Workflow Automation</h3>",
      "firstParagraph": "Build, trigger, and optimize any recurring process from renewals to inspections to owner updates.",
      "paragraphHtml": "<p>Build, trigger, and optimize any recurring process from renewals to inspections to owner updates.</p>",
      "words": 14,
      "direct": false,
      "issue": "First paragraph is 14 words and does not look like a concise direct answer."
    },
    {
      "heading": "Smart Routing",
      "headingHtml": "<h3>Smart Routing</h3>",
      "firstParagraph": "Automatically route requests to the right person based on property, issue type, and team availability.",
      "paragraphHtml": "<p>Automatically route requests to the right person based on property, issue type, and team availability.</p>",
      "words": 15,
      "direct": false,
      "issue": "First paragraph is 15 words and does not look like a concise direct answer."
    },
    {
      "heading": "How it works",
      "headingHtml": "<h2>How it works</h2>",
      "firstParagraph": "Aptly integrates with your existing property management software and becomes the AI-powered operations layer on top.",
      "paragraphHtml": "<p>Aptly integrates with your existing property management software and becomes the AI-powered operations layer on top.</p>",
      "words": 16,
      "direct": false,
      "issue": "First paragraph is 16 words and does not look like a concise direct answer."
    },
    {
      "heading": "1. Connect",
      "headingHtml": "<h3>1. Connect</h3>",
      "firstParagraph": "Plug into your PMS (Yardi, RealPage, Entrata, AppFolio, and more) with bidirectional data sync.",
      "paragraphHtml": "<p>Plug into your PMS (Yardi, RealPage, Entrata, AppFolio, and more) with bidirectional data sync.</p>",
      "words": 14,
      "direct": false,
      "issue": "First paragraph is 14 words and does not look like a concise direct answer."
    },
    {
      "heading": "2. Automate",
      "headingHtml": "<h3>2. Automate</h3>",
      "firstParagraph": "Set up AI agents and automated workflows for leasing, maintenance, collections, and resident support.",
      "paragraphHtml": "<p>Set up AI agents and automated workflows for leasing, maintenance, collections, and resident support.</p>",
      "words": 14,
      "direct": false,
      "issue": "First paragraph is 14 words and does not look like a concise direct answer."
    },
    {
      "heading": "3. Optimize",
      "headingHtml": "<h3>3. Optimize</h3>",
      "firstParagraph": "Track performance with real-time analytics and continuously improve your operations.",
      "paragraphHtml": "<p>Track performance with real-time analytics and continuously improve your operations.</p>",
      "words": 10,
      "direct": false,
      "issue": "First paragraph is 10 words and does not look like a concise direct answer."
    },
    {
      "heading": "Ready to see the future of property management?",
      "headingHtml": "<h2>Ready to see the future of property management?</h2>",
      "firstParagraph": "Book a demo to discover how Aptly can transform your property management operations with AI-powered automation.",
      "paragraphHtml": "<p>Book a demo to discover how Aptly can transform your property management operations with AI-powered automation.</p>",
      "words": 16,
      "direct": false,
      "issue": "First paragraph is 16 words and does not look like a concise direct answer."
    }
  ],
  "score": 65,
  "weight": 8
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AIO: Visible structured data match

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

1 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

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

Evidence
{
  "schemaCount": 6,
  "checkedFields": [
    {
      "path": "$[0].name",
      "value": "Aptly"
    },
    {
      "path": "$[0].description",
      "value": "Aptly is the all-in-one operating system for property management teams, connecting workflows, automations, communication, and reporting."
    },
    {
      "path": "$[1].name",
      "value": "Aptly"
    },
    {
      "path": "$[2].name",
      "value": "Aptly"
    },
    {
      "path": "$[2].description",
      "value": "AI-powered CRM and workflow management platform for property management teams. Automate leasing, maintenance, collections, and resident communication."
    },
    {
      "path": "$[3].name",
      "value": "Aptly | The Intelligent Operations Layer for Property Management"
    },
    {
      "path": "$[3].description",
      "value": "Connect your systems, replace fragmented tools, and orchestrate every workflow with AI. The complete operating layer for modern property management teams."
    },
    {
      "path": "$[4].itemListElement[0].name",
      "value": "Home"
    },
    {
      "path": "$[5].mainEntity[0].name",
      "value": "What is Aptly?"
    },
    {
      "path": "$[5].mainEntity[1].name",
      "value": "Does Aptly replace my property management software?"
    },
    {
      "path": "$[5].mainEntity[2].name",
      "value": "Which property management systems does Aptly integrate with?"
    },
    {
      "path": "$[5].mainEntity[3].name",
      "value": "What can Aptly's AI Agents do?"
    },
    {
      "path": "$[5].mainEntity[4].name",
      "value": "How quickly can a team get started with Aptly?"
    }
  ],
  "mismatches": [
    {
      "path": "$[4].itemListElement[0].name",
      "value": "Home"
    },
    {
      "path": "$[5].mainEntity[4].name",
      "value": "How quickly can a team get started with Aptly?"
    }
  ],
  "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, 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": "The complete operating system for modern property teams",
      "html": "<h2>The complete operating system for modern property teams</h2>"
    },
    {
      "text": "How it works",
      "html": "<h2>How it works</h2>"
    },
    {
      "text": "Ready to see the future of property management?",
      "html": "<h2>Ready to see the future of property management?</h2>"
    }
  ],
  "expected": [
    {
      "id": "what",
      "label": "What is Aptly?",
      "pattern": {}
    },
    {
      "id": "how",
      "label": "How does Aptly work?",
      "pattern": {}
    },
    {
      "id": "benefits",
      "label": "Why use Aptly?",
      "pattern": {}
    },
    {
      "id": "cost",
      "label": "Is Aptly free or paid?",
      "pattern": {}
    },
    {
      "id": "compare",
      "label": "How does Aptly compare with alternatives?",
      "pattern": {}
    }
  ],
  "missing": [
    {
      "id": "what",
      "label": "What is Aptly?",
      "pattern": {}
    },
    {
      "id": "benefits",
      "label": "Why use Aptly?",
      "pattern": {}
    },
    {
      "id": "cost",
      "label": "Is Aptly free or paid?",
      "pattern": {}
    },
    {
      "id": "compare",
      "label": "How does Aptly 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 85/100 and needs improvement.

1 Warning

Needs attention

AIO: Page experience for AIO

Warning
01

Issue

3 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

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

Evidence
{
  "viewportContent": "width=device-width, initial-scale=1",
  "visibleWords": 259,
  "htmlBytes": 29907,
  "imagesMissingDimensions": [
    {
      "src": "/images/aptly-logo-white.png",
      "width": "",
      "height": "",
      "loading": "lazy",
      "html": "<img src=\"/images/aptly-logo-white.png\" alt=\"Aptly\" class=\"sf-logo\" loading=\"lazy\">"
    },
    {
      "src": "https://cdn.prod.website-files.com/68f83a36b62d8044fc46cd26/695f73407ae84cbdda60624c_Store%20Name%3DApple%20App%20Store%2C%20Badge%20Color%20Type%3DBlack%2C%20Language%3DEN.png",
      "width": "",
      "height": "",
      "loading": "lazy",
      "html": "<img src=\"https://cdn.prod.website-files.com/68f83a36b62d8044fc46cd26/695f73407ae84cbdda60624c_Store%20Name%3DApple%20App%20Store%2C%20Badge%20Color%20Type%3DBlack%2C%20Language%3DEN.png\" alt=\"Download on the App Store\" class=\"sf-badge\" loading=\"lazy\">"
    },
    {
      "src": "https://cdn.prod.website-files.com/68f83a36b62d8044fc46cd26/695f7340df353dce414b5fd7_Store%20Name%3DGoogle%20Play%2C%20Badge%20Color%20Type%3DBlack%2C%20Language%3DEN.png",
      "width": "",
      "height": "",
      "loading": "lazy",
      "html": "<img src=\"https://cdn.prod.website-files.com/68f83a36b62d8044fc46cd26/695f7340df353dce414b5fd7_Store%20Name%3DGoogle%20Play%2C%20Badge%20Color%20Type%3DBlack%2C%20Language%3DEN.png\" alt=\"Get it on Google Play\" class=\"sf-badge\" loading=\"lazy\">"
    }
  ],
  "possibleDialogs": [],
  "score": 85,
  "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": 27848
          },
          {
            "path": "/api/context",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "length": 27848
          },
          {
            "path": "/context",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "length": 27848
          }
        ]
      },
      "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, 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": "The complete operating system for modern property teams",
      "html": "<h2>The complete operating system for modern property teams</h2>"
    },
    {
      "text": "How it works",
      "html": "<h2>How it works</h2>"
    },
    {
      "text": "Ready to see the future of property management?",
      "html": "<h2>Ready to see the future of property management?</h2>"
    }
  ],
  "expected": [
    {
      "id": "what",
      "label": "What is Aptly?",
      "pattern": {}
    },
    {
      "id": "how",
      "label": "How does Aptly work?",
      "pattern": {}
    },
    {
      "id": "benefits",
      "label": "Why use Aptly?",
      "pattern": {}
    },
    {
      "id": "cost",
      "label": "Is Aptly free or paid?",
      "pattern": {}
    },
    {
      "id": "compare",
      "label": "How does Aptly compare with alternatives?",
      "pattern": {}
    }
  ],
  "missing": [
    {
      "id": "what",
      "label": "What is Aptly?",
      "pattern": {}
    },
    {
      "id": "benefits",
      "label": "Why use Aptly?",
      "pattern": {}
    },
    {
      "id": "cost",
      "label": "Is Aptly free or paid?",
      "pattern": {}
    },
    {
      "id": "compare",
      "label": "How does Aptly compare with alternatives?",
      "pattern": {}
    }
  ],
  "score": 70,
  "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."
    }
  ]
}

SEOSEOBrowser audit

Links do not have descriptive text

100 Fail

Check name

Links do not have descriptive text

Score

0/100

Status

fail

Device

desktop

Category

SEO

Estimated savings

1 link found

Fix guidance

Descriptive link text helps search engines understand your content. [Learn how to make links more accessible](https://developer.chrome.com/docs/lighthouse/seo/link-text/).

Evidence
{
  "displayValue": "1 link found",
  "description": "Descriptive link text helps search engines understand your content. [Learn how to make links more accessible](https://developer.chrome.com/docs/lighthouse/seo/link-text/)."
}

Performance and AccessibilityPerformanceBrowser audit

Layout shift culprits

17 Fail

Check name

Layout shift culprits

Score

0/100

Status

fail

Device

desktop

Category

Performance

Fix guidance

Layout shifts occur when elements move absent any user interaction. [Investigate the causes of layout shifts](https://developer.chrome.com/docs/performance/insights/cls-culprit), such as elements being added, removed, or their fonts changing as the page loads.

Evidence
{
  "description": "Layout shifts occur when elements move absent any user interaction. [Investigate the causes of layout shifts](https://developer.chrome.com/docs/performance/insights/cls-culprit), such as elements being added, removed, or their fonts changing as the page loads."
}

Performance and AccessibilityPerformanceBrowser audit

Reduce unused CSS

17 Fail

Check name

Reduce unused CSS

Score

0/100

Status

fail

Device

desktop

Category

Performance

Estimated savings

Est savings of 141 KiB

Fix guidance

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. [Learn how to reduce unused CSS](https://developer.chrome.com/docs/lighthouse/performance/unused-css-rules/).

Evidence
{
  "displayValue": "Est savings of 141 KiB",
  "description": "Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. [Learn how to reduce unused CSS](https://developer.chrome.com/docs/lighthouse/performance/unused-css-rules/).",
  "numericValue": 130
}

Performance and AccessibilityPerformanceBrowser audit

Reduce unused JavaScript

17 Fail

Check name

Reduce unused JavaScript

Score

0/100

Status

fail

Device

desktop

Category

Performance

Estimated savings

Est savings of 109 KiB

Fix guidance

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. [Learn how to reduce unused JavaScript](https://developer.chrome.com/docs/lighthouse/performance/unused-javascript/).

Evidence
{
  "displayValue": "Est savings of 109 KiB",
  "description": "Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. [Learn how to reduce unused JavaScript](https://developer.chrome.com/docs/lighthouse/performance/unused-javascript/).",
  "numericValue": 160
}

Performance and AccessibilityPerformanceBrowser audit

Avoid enormous network payloads

8 Warning

Check name

Avoid enormous network payloads

Score

50/100

Status

warning

Device

desktop

Category

Performance

Estimated savings

Total size was 5,089 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 5,089 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": 5211577
}

Performance and AccessibilityPerformanceBrowser audit

Minify CSS

8 Warning

Check name

Minify CSS

Score

50/100

Status

warning

Device

desktop

Category

Performance

Estimated savings

Est savings of 10 KiB

Fix guidance

Minifying CSS files can reduce network payload sizes. [Learn how to minify CSS](https://developer.chrome.com/docs/lighthouse/performance/unminified-css/).

Evidence
{
  "displayValue": "Est savings of 10 KiB",
  "description": "Minifying CSS files can reduce network payload sizes. [Learn how to minify CSS](https://developer.chrome.com/docs/lighthouse/performance/unminified-css/).",
  "numericValue": 0
}

Performance and AccessibilityPerformanceBrowser audit

Loading performance

2 Fail

Check name

Loading performance

Score

89/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": "total-blocking-time",
      "title": "Total Blocking Time",
      "score": 100,
      "displayValue": "40 ms",
      "numericValue": 44
    },
    {
      "id": "interactive",
      "title": "Time to Interactive",
      "score": 96,
      "displayValue": "1.9 s",
      "numericValue": 1939.452831912984
    },
    {
      "id": "first-contentful-paint",
      "title": "First Contentful Paint",
      "score": 95,
      "displayValue": "0.8 s",
      "numericValue": 779.0312140261615
    },
    {
      "id": "speed-index",
      "title": "Speed Index",
      "score": 39,
      "displayValue": "2.6 s",
      "numericValue": 2587.5360825230323
    },
    {
      "id": "max-potential-fid",
      "title": "Max Potential First Input Delay",
      "score": 98,
      "displayValue": "90 ms",
      "numericValue": 90
    },
    {
      "id": "largest-contentful-paint",
      "title": "Largest Contentful Paint",
      "score": 80,
      "displayValue": "1.5 s",
      "numericValue": 1507.55955088155
    },
    {
      "id": "server-response-time",
      "title": "Initial server response time was short",
      "score": 100,
      "displayValue": "Root document took 0 ms",
      "numericValue": 2
    },
    {
      "id": "network-rtt",
      "title": "Network Round Trip Times",
      "score": 100,
      "displayValue": "30 ms",
      "numericValue": 25.45047
    }
  ]
}

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
getaptly.com AI SEO Report: 62/100 (Level 3, Bot-Aware)