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

OVERALL SCORE

Level 3, Bot-Aware

Moderate readiness for AI agents
AIDiscoverability36%Agent Easeof Use6%Security& Trust20%GEO, AIO, AEO72%SEO85%Performance& Accessibility89%
  • AI Discoverability 36 out of 100
  • Agent Ease of Use 6 out of 100
  • Security & Trust 20 out of 100
  • GEO, AIO and AEO 72 out of 100
  • SEO 85 out of 100
  • Performance and Accessibility 89 out of 100

CAPTURED SCREENSHOT

Captured website desktop screenshot

What AI sees of your website

Zero Hassle Job Search - Instahyre favicon

Zero Hassle Job Search - Instahyre

Search and apply to jobs at 10000+ top companies. Find high paying jobs in IT, software, sales, marketing, operations, finance and more. Hire top talent.

Next step

Turn this report into a fix workflow

28 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
36
Priority fix9150View details
Discoverability
50
Needs work450View details
Content Readiness
50
Needs work560View details
Bot Access Control
0
Priority fix040View details
Agent Ease of Use
6
Priority fix4293View details
API
0
Priority fix060View details
Auth
Not Applicable
Not Applicable070View details
MCP
13
Priority fix062View details
Skill Discovery
5
Priority fix0101View details
Agent Commerce
Not Applicable
Not Applicable400
GEO, AIO and AEO
72
Needs work4213View details
GEO Readiness
84
Mostly ready104
AIO Readiness
69
Needs work214View details
AEO Readiness
62
Needs work115View details
SEO
85
Mostly ready920View details
SEO
85
Mostly ready920View details
Security & Trust
20
Priority fix540View details
Security & Trust
20
Priority fix140View details
AI Training Exposure
Not Applicable
Not Applicable400
Performance and Accessibility
89
Mostly ready2430View details
Performance
99
Strong1830View details
Accessibility
70
Needs work600

Prioritized recommendations

Issues ranked by score impact

48 items need attention

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": "\n\n\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\">\n\n        \n            <link rel=\"canonical\" href=\"https://www.instahyre.com/.well-known/api-catalog\">\n        \n\n        \n            <title>Zero Hassle Job Search - Instahyre</title>\n        \n\n        \n            <meta property=\"og:description\"     content=\"Let the best companies in India compete to hire you! Get your perfect job in tech, product, marketing, sales or operations. Hire the best talent faster.\">\n            <meta name=\"description\"            content=\"Let the best companies in India compete to hire you! Get your perfect job in tech, product, marketing, sales or operations. Hire the best talent faster.\">\n            <meta n"
      },
      "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."
    }
  ]
}

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": 403,
            "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-US\"><head><title>Just a moment...</title><meta http-equiv=\"Content-Type\" content=\"text/html; charset=UTF-8\"><meta http-equiv=\"X-UA-Compatible\" content=\"IE=Edge\"><meta name=\"robots\" content=\"noindex,nofollow\"><meta name=\"viewport\" content=\"width=device-width,initial-scale=1\"><meta http-equiv=\"content-security-policy\" content=\"default-src &#39;none&#39;; script-src &#39;nonce-jzKsGjaXp6TC60F4QxZk0y&#39; &#39;unsafe-eval&#39; https://challenges.cloudflare.com; script-src-attr &#39;none&#39;; style-src &#39;unsafe-inline&#39;; img-src &#39;self&#39; https://challenges.cloudflare.com; connect-src &#39;self&#39; https://challenges.cloudflare.com; frame-src &#39;self&#39; https://challenges.cloudflare.com blob:; child-src &#39;self&#39; https://challenges.cloudflare."
          },
          {
            "path": "/openapi.yaml",
            "statusCode": 403,
            "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-US\"><head><title>Just a moment...</title><meta http-equiv=\"Content-Type\" content=\"text/html; charset=UTF-8\"><meta http-equiv=\"X-UA-Compatible\" content=\"IE=Edge\"><meta name=\"robots\" content=\"noindex,nofollow\"><meta name=\"viewport\" content=\"width=device-width,initial-scale=1\"><meta http-equiv=\"content-security-policy\" content=\"default-src &#39;none&#39;; script-src &#39;nonce-eCVgkjbtOIKRW3UCTRyEpj&#39; &#39;unsafe-eval&#39; https://challenges.cloudflare.com; script-src-attr &#39;none&#39;; style-src &#39;unsafe-inline&#39;; img-src &#39;self&#39; https://challenges.cloudflare.com; connect-src &#39;self&#39; https://challenges.cloudflare.com; frame-src &#39;self&#39; https://challenges.cloudflare.com blob:; child-src &#39;self&#39; https://challenges.cloudflare."
          },
          {
            "path": "/swagger.json",
            "statusCode": 403,
            "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-US\"><head><title>Just a moment...</title><meta http-equiv=\"Content-Type\" content=\"text/html; charset=UTF-8\"><meta http-equiv=\"X-UA-Compatible\" content=\"IE=Edge\"><meta name=\"robots\" content=\"noindex,nofollow\"><meta name=\"viewport\" content=\"width=device-width,initial-scale=1\"><meta http-equiv=\"content-security-policy\" content=\"default-src &#39;none&#39;; script-src &#39;nonce-frBsOCvqTriXrmvR31lzOB&#39; &#39;unsafe-eval&#39; https://challenges.cloudflare.com; script-src-attr &#39;none&#39;; style-src &#39;unsafe-inline&#39;; img-src &#39;self&#39; https://challenges.cloudflare.com; connect-src &#39;self&#39; https://challenges.cloudflare.com; frame-src &#39;self&#39; https://challenges.cloudflare.com blob:; child-src &#39;self&#39; https://challenges.cloudflare."
          },
          {
            "path": "/swagger.yaml",
            "statusCode": 403,
            "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-US\"><head><title>Just a moment...</title><meta http-equiv=\"Content-Type\" content=\"text/html; charset=UTF-8\"><meta http-equiv=\"X-UA-Compatible\" content=\"IE=Edge\"><meta name=\"robots\" content=\"noindex,nofollow\"><meta name=\"viewport\" content=\"width=device-width,initial-scale=1\"><meta http-equiv=\"content-security-policy\" content=\"default-src &#39;none&#39;; script-src &#39;nonce-Wi7NBIXgCRdZu9Ut1TVP3p&#39; &#39;unsafe-eval&#39; https://challenges.cloudflare.com; script-src-attr &#39;none&#39;; style-src &#39;unsafe-inline&#39;; img-src &#39;self&#39; https://challenges.cloudflare.com; connect-src &#39;self&#39; https://challenges.cloudflare.com; frame-src &#39;self&#39; https://challenges.cloudflare.com blob:; child-src &#39;self&#39; https://challenges.cloudflare."
          },
          {
            "path": "/api/openapi.json",
            "statusCode": 403,
            "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-US\"><head><title>Just a moment...</title><meta http-equiv=\"Content-Type\" content=\"text/html; charset=UTF-8\"><meta http-equiv=\"X-UA-Compatible\" content=\"IE=Edge\"><meta name=\"robots\" content=\"noindex,nofollow\"><meta name=\"viewport\" content=\"width=device-width,initial-scale=1\"><meta http-equiv=\"content-security-policy\" content=\"default-src &#39;none&#39;; script-src &#39;nonce-37Y3VDGw26Yd63BHm0vC5i&#39; &#39;unsafe-eval&#39; https://challenges.cloudflare.com; script-src-attr &#39;none&#39;; style-src &#39;unsafe-inline&#39;; img-src &#39;self&#39; https://challenges.cloudflare.com; connect-src &#39;self&#39; https://challenges.cloudflare.com; frame-src &#39;self&#39; https://challenges.cloudflare.com blob:; child-src &#39;self&#39; https://challenges.cloudflare."
          },
          {
            "path": "/api/swagger.json",
            "statusCode": 403,
            "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-US\"><head><title>Just a moment...</title><meta http-equiv=\"Content-Type\" content=\"text/html; charset=UTF-8\"><meta http-equiv=\"X-UA-Compatible\" content=\"IE=Edge\"><meta name=\"robots\" content=\"noindex,nofollow\"><meta name=\"viewport\" content=\"width=device-width,initial-scale=1\"><meta http-equiv=\"content-security-policy\" content=\"default-src &#39;none&#39;; script-src &#39;nonce-4QM1sPMR5ou7ZPS4a4MD95&#39; &#39;unsafe-eval&#39; https://challenges.cloudflare.com; script-src-attr &#39;none&#39;; style-src &#39;unsafe-inline&#39;; img-src &#39;self&#39; https://challenges.cloudflare.com; connect-src &#39;self&#39; https://challenges.cloudflare.com; frame-src &#39;self&#39; https://challenges.cloudflare.com blob:; child-src &#39;self&#39; https://challenges.cloudflare."
          },
          {
            "path": "/docs/openapi.json",
            "statusCode": 403,
            "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-US\"><head><title>Just a moment...</title><meta http-equiv=\"Content-Type\" content=\"text/html; charset=UTF-8\"><meta http-equiv=\"X-UA-Compatible\" content=\"IE=Edge\"><meta name=\"robots\" content=\"noindex,nofollow\"><meta name=\"viewport\" content=\"width=device-width,initial-scale=1\"><meta http-equiv=\"content-security-policy\" content=\"default-src &#39;none&#39;; script-src &#39;nonce-nzbsHRon0b4gNNnkM1ypjs&#39; &#39;unsafe-eval&#39; https://challenges.cloudflare.com; script-src-attr &#39;none&#39;; style-src &#39;unsafe-inline&#39;; img-src &#39;self&#39; https://challenges.cloudflare.com; connect-src &#39;self&#39; https://challenges.cloudflare.com; frame-src &#39;self&#39; https://challenges.cloudflare.com blob:; child-src &#39;self&#39; https://challenges.cloudflare."
          }
        ]
      },
      "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 ControlEstablished

AI bot rules in robots.txt

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

33 Fail

Needs attention

AI bot rules in robots.txt

Failed check
01

Issue

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

02

Why it matters

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

Check name

AI bot rules in robots.txt

Score

0/100

Status

fail

Category

Bot Access Control

Maturity

Established

Goal

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

Result

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

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

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 DiscoverabilityBot Access ControlInformational

Content Signal

Content Signal is missing or incomplete.

33 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
}

AI DiscoverabilityDiscoverabilityEstablished

High-value schema types

High-value schema types is missing or incomplete.

33 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"
  ]
}

AI DiscoverabilityDiscoverabilityEstablished

Link headers

Link headers failed at "Find useful Link headers".

33 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 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": 403,
        "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": 364,
        "excerpt": "<!DOCTYPE html><html lang=\"en-US\"><head><title>Just a moment...</title><meta http-equiv=\"Content-Type\" content=\"text/html; charset=UTF-8\"><meta http-equiv=\"X-UA-Compatible\" content=\"IE=Edge\"><meta name=\"robots\" content=\"noindex,nofollow\"><m",
        "issue": "Markdown response is missing a heading."
      },
      "issue": "Markdown response is missing a heading.",
      "howToFix": "Return Markdown with at least one heading and substantive page content, including useful links or instructions for agents."
    }
  ]
}

AI DiscoverabilityContent ReadinessEstablished

Semantic HTML

Semantic HTML is missing or incomplete.

33 Fail

Needs attention

Semantic HTML

Failed check
01

Issue

Semantic HTML is incomplete: missing <main> landmark; skipped heading levels; 3 links missing accessible names; 0/3 applicable form inputs have autocomplete attributes (3 missing).

Details

02

Why it matters

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

Check name

Semantic HTML

Score

0/100

Status

fail

Category

Content Readiness

Maturity

Established

Goal

Expose readable page structure through semantic HTML and accessible controls.

Result

Semantic HTML is missing or incomplete.

Evidence
{
  "main": false,
  "nav": true,
  "footer": true,
  "meaningfulH1": true,
  "headingOrder": false,
  "accessibleLinks": false,
  "accessibleButtons": true,
  "imageAltCoverage": true,
  "formAutocompleteCoverage": false,
  "details": {
    "inaccessibleLinks": [
      "<a id=\"footer-facebook\" href=\"https://www.facebook.com/instahyre\" target=\"_blank\"><i class=\"fa fa-facebook-square\"></i></a>",
      "<a id=\"footer-linkedin\" href=\"https://www.linkedin.com/company/instahyre\" target=\"_blank\"><i class=\"fa fa-linkedin-square\"></i></a>",
      "<a id=\"footer-twitter\" href=\"https://twitter.com/instahyre\" target=\"_blank\"><i class=\"fa fa-twitter-square\"></i></a>"
    ],
    "inaccessibleButtons": [],
    "missingAutocompleteInputs": [
      "<input auctioned-field form-name=\"anonymousContactus\" ng-model=\"formData.name\" class=\"form-control\" name=\"name\">",
      "<input auctioned-field form-name=\"anonymousContactus\" ng-model=\"formData.email\" class=\"form-control\" name=\"email\">",
      "<input class=\"form-control\" auctioned-field form-name=\"anonymousContactus\" type=\"text\" ng-model=\"formData.phone\" name=\"phone\">"
    ],
    "imagesMissingAlt": [],
    "skippedHeadingLevels": [
      "h1: Your Dream Job. Now.",
      "h2: More than 10,000 top companies",
      "h5: 5X higher response from companies",
      "h5: Your perfect job, delivered to you",
      "h5: Privacy guaranteed",
      "h4: Jobs by Location",
      "h4: Jobs by Function",
      "h4: For Employers",
      "h4: Instahyre",
      "h4: Connect",
      "h4: Contact Us",
      "h4: Your query has been sent"
    ]
  },
  "counts": {
    "h1": 1,
    "headings": 12,
    "links": 34,
    "inaccessibleLinks": 3,
    "buttons": 3,
    "inaccessibleButtons": 0,
    "images": 8,
    "imagesWithAlt": 8,
    "autocompleteInputs": 3,
    "inputsWithAutocomplete": 0,
    "missingAutocompleteInputs": 3
  }
}

AI DiscoverabilityDiscoverabilityEstablished

Sitemap

Sitemap is missing or incomplete.

33 Fail

Needs attention

Sitemap

Failed check
01

Issue

No valid XML sitemap found at checked locations: https://www.instahyre.com/sitemap.xml, https://www.instahyre.com/sitemap.xml, https://www.instahyre.com/sitemap_index.xml, https://www.instahyre.com/sitemap-index.xml.

02

Why it matters

Sitemaps help crawlers and agents discover canonical URLs, updated pages, and deeper content that may not be obvious from the homepage navigation.

Check name

Sitemap

Score

0/100

Status

fail

Category

Discoverability

Maturity

Established

Goal

Publish a sitemap and reference it from robots.txt.

Result

Sitemap is missing or incomplete.

Evidence
{
  "checked": [
    "https://www.instahyre.com/sitemap.xml",
    "https://www.instahyre.com/sitemap.xml",
    "https://www.instahyre.com/sitemap_index.xml",
    "https://www.instahyre.com/sitemap-index.xml"
  ]
}

AI DiscoverabilityBot Access ControlInformational

Web Bot Auth request signing

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

33 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": 49110
          }
        ]
      },
      "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."
    }
  ]
}

Security & TrustSecurity & TrustEstablished

Content-Security-Policy

Content-Security-Policy is missing or incomplete.

25 Fail

Needs attention

Content-Security-Policy

Failed check
01

Issue

Content-Security-Policy is missing or incomplete.

02

Why it matters

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

Check name

Content-Security-Policy

Score

0/100

Status

fail

Category

Security & Trust

Maturity

Established

Goal

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

Result

Content-Security-Policy is missing or incomplete.

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

Security & TrustSecurity & TrustEstablished

HSTS header

HSTS header is missing or incomplete.

25 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": null
}

Agent Ease of UseMCPEmerging recommendation

MCP Server Card

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

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

25 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": 403,
            "contentType": "text/html; charset=UTF-8",
            "length": 5453
          },
          {
            "path": "/.well-known/mcp.json",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "length": 49085
          },
          {
            "path": "/.well-known/mcp/server-card.json",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "length": 49097
          }
        ]
      },
      "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."
    }
  ]
}

Security & TrustSecurity & TrustEstablished

Referrer-Policy

Referrer-Policy is missing or incomplete.

25 Fail

Needs attention

Referrer-Policy

Failed check
01

Issue

Referrer-Policy is missing or incomplete.

02

Why it matters

Referrer-Policy controls how much URL context is sent to other origins, limiting accidental leakage of paths, queries, and identifiers.

Check name

Referrer-Policy

Score

0/100

Status

fail

Category

Security & Trust

Maturity

Established

Goal

Limit how much referrer data leaves the site.

Result

Referrer-Policy is missing or incomplete.

Evidence
{
  "header": "referrer-policy",
  "value": null
}

Agent Ease of UseMCPInformational

WebMCP manifest

WebMCP manifest failed at "Fetch to find resource".

25 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": 49088
          },
          {
            "path": "/webmcp.json",
            "statusCode": 403,
            "contentType": "text/html; charset=UTF-8",
            "length": 5462
          },
          {
            "path": "/mcp.json",
            "statusCode": 403,
            "contentType": "text/html; charset=UTF-8",
            "length": 5453
          }
        ]
      },
      "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."
    }
  ]
}

Security & TrustSecurity & TrustEstablished

X-Content-Type-Options

X-Content-Type-Options is missing or incomplete.

25 Fail

Needs attention

X-Content-Type-Options

Failed check
01

Issue

X-Content-Type-Options is missing or incomplete.

02

Why it matters

X-Content-Type-Options prevents browsers from treating mislabeled files as executable content, reducing content-sniffing attacks.

Check name

X-Content-Type-Options

Score

0/100

Status

fail

Category

Security & Trust

Maturity

Established

Goal

Prevent MIME sniffing for browser-loaded resources.

Result

X-Content-Type-Options is missing or incomplete.

Evidence
{
  "header": "x-content-type-options",
  "value": null
}

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": 49092
          },
          {
            "path": "/.well-known/a2a/agent-card.json",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "length": 49096
          },
          {
            "path": "/agent-card.json",
            "statusCode": 403,
            "contentType": "text/html; charset=UTF-8",
            "length": 5474
          }
        ]
      },
      "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": 49100
          },
          {
            "path": "/.well-known/skills/index.json",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "length": 49094
          }
        ]
      },
      "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": 49087
          },
          {
            "path": "/agent.json",
            "statusCode": 403,
            "contentType": "text/html; charset=UTF-8",
            "length": 5459
          }
        ]
      },
      "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": 49088
          },
          {
            "path": "/agents.json",
            "statusCode": 403,
            "contentType": "text/html; charset=UTF-8",
            "length": 5462
          }
        ]
      },
      "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.instahyre.com",
        "probes": [
          {
            "name": "_index._agents.www.instahyre.com",
            "found": false,
            "recordCount": 1,
            "records": [],
            "hasAlpn": false,
            "hasEndpoint": false
          },
          {
            "name": "_a2a._agents.www.instahyre.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.instahyre.com",
            "dnssecTypes": [],
            "dnssecRecordCount": 0
          },
          {
            "name": "instahyre.com",
            "dnssecTypes": [],
            "dnssecRecordCount": 0
          }
        ]
      },
      "issue": "DNSSEC material was not visible for the hostname or parent zone from this resolver.",
      "howToFix": "Sign the public discovery zone with DNSSEC so validating resolvers can return authenticated data."
    }
  ]
}

Agent Ease of UseMCPInformational

WebMCP

WebMCP has a validation warning at "Validate WebMCP declarative annotation quality".

13 Warning

Needs attention

WebMCP

Warning
01

Issue

WebMCP declarative annotations need fixes.

Details

02

Why it matters

WebMCP can expose page context and actions directly through the browser, giving agents safer structured hooks than screen scraping alone.

Check name

WebMCP

Score

50/100

Status

warning

Category

MCP

Maturity

Informational

Goal

Support WebMCP to expose site tools to AI agents via the browser.

Result

WebMCP has a validation warning at "Validate WebMCP declarative annotation quality".

Validation steps

  1. Detect data-mcp-tool annotations

    No data-mcp-tool attributes were found on interactive elements.

  2. Detect WebMCP declarative tags

    No elements found with tool-name or tool-description attributes.

  3. Validate WebMCP declarative annotation quality

    WebMCP declarative annotations need fixes.

    WebMCP declarative annotation issues
    • <textarea name="message"> is missing a label.
    • <textarea name="message"> is missing tool-param-description.
    • <input name="name"> is missing a label.
    • <input name="name"> is missing tool-param-description.
    • <input name="email"> is missing a label.
    • <input name="email"> is missing tool-param-description.
    • <select> is missing a name attribute.
    • <select> is missing a label.
    • <select> is missing tool-param-description.
    • <input name="phone"> is missing a label.
    • <input name="phone"> is missing tool-param-description.
    • <input name="attachments"> is missing tool-param-description.
  4. Detect WebMCP imperative API usage

    navigator.modelContext.provideContext(), navigator.modelContext.registerTool(), or other imperative signals were not detected in rendered browser state.

  5. Detect WebMCP browser navigator injection

    navigator.modelContext was not detected in the rendered browser page.

  6. Interactive surface coverage

    Only 0% of interactive surfaces are annotated.

Evidence
{
  "failedStep": "declarative-annotation-quality",
  "steps": [
    {
      "id": "data-mcp-tool-attributes",
      "title": "Detect data-mcp-tool annotations",
      "status": "informational",
      "evidence": {
        "dataMcpToolCount": 0,
        "dataMcpTools": []
      },
      "issue": "No data-mcp-tool attributes were found on interactive elements.",
      "howToFix": "Add data-mcp-tool attributes to high-value forms, buttons, and links so generic MCP-aware tooling can identify intended actions."
    },
    {
      "id": "declarative-tags",
      "title": "Detect WebMCP declarative tags",
      "status": "informational",
      "evidence": {
        "totalForms": 1,
        "formsWithTags": 0,
        "totalInteractive": 41,
        "interactiveWithTags": 0,
        "totalCount": 42,
        "taggedCount": 0,
        "dataMcpToolCount": 0,
        "dataMcpTools": [],
        "coverage": 0,
        "annotationIssues": [
          "<textarea name=\"message\"> is missing a label.",
          "<textarea name=\"message\"> is missing tool-param-description.",
          "<input name=\"name\"> is missing a label.",
          "<input name=\"name\"> is missing tool-param-description.",
          "<input name=\"email\"> is missing a label.",
          "<input name=\"email\"> is missing tool-param-description.",
          "<select> is missing a name attribute.",
          "<select> is missing a label.",
          "<select> is missing tool-param-description.",
          "<input name=\"phone\"> is missing a label.",
          "<input name=\"phone\"> is missing tool-param-description.",
          "<input name=\"attachments\"> is missing tool-param-description."
        ]
      },
      "issue": "No elements found with tool-name or tool-description attributes.",
      "howToFix": "Add tool-name and tool-description attributes to forms and interactive elements."
    },
    {
      "id": "declarative-annotation-quality",
      "title": "Validate WebMCP declarative annotation quality",
      "status": "warning",
      "evidence": {
        "issueCount": 12,
        "issues": [
          "<textarea name=\"message\"> is missing a label.",
          "<textarea name=\"message\"> is missing tool-param-description.",
          "<input name=\"name\"> is missing a label.",
          "<input name=\"name\"> is missing tool-param-description.",
          "<input name=\"email\"> is missing a label.",
          "<input name=\"email\"> is missing tool-param-description.",
          "<select> is missing a name attribute.",
          "<select> is missing a label.",
          "<select> is missing tool-param-description.",
          "<input name=\"phone\"> is missing a label.",
          "<input name=\"phone\"> is missing tool-param-description.",
          "<input name=\"attachments\"> is missing tool-param-description."
        ]
      },
      "issue": "WebMCP declarative annotations need fixes.",
      "issueDetails": [
        {
          "title": "WebMCP declarative annotation issues",
          "items": [
            {
              "type": "code",
              "value": "<textarea name=\"message\"> is missing a label."
            },
            {
              "type": "code",
              "value": "<textarea name=\"message\"> is missing tool-param-description."
            },
            {
              "type": "code",
              "value": "<input name=\"name\"> is missing a label."
            },
            {
              "type": "code",
              "value": "<input name=\"name\"> is missing tool-param-description."
            },
            {
              "type": "code",
              "value": "<input name=\"email\"> is missing a label."
            },
            {
              "type": "code",
              "value": "<input name=\"email\"> is missing tool-param-description."
            },
            {
              "type": "code",
              "value": "<select> is missing a name attribute."
            },
            {
              "type": "code",
              "value": "<select> is missing a label."
            },
            {
              "type": "code",
              "value": "<select> is missing tool-param-description."
            },
            {
              "type": "code",
              "value": "<input name=\"phone\"> is missing a label."
            },
            {
              "type": "code",
              "value": "<input name=\"phone\"> is missing tool-param-description."
            },
            {
              "type": "code",
              "value": "<input name=\"attachments\"> is missing tool-param-description."
            }
          ]
        }
      ],
      "howToFix": "Use snake_case tool-name values, descriptive tool-description values, named and labeled fields, and tool-param-description on inputs."
    },
    {
      "id": "imperative-api",
      "title": "Detect WebMCP imperative API usage",
      "status": "informational",
      "evidence": {
        "staticSignals": {
          "detected": false,
          "matched": []
        },
        "browser": {
          "checked": true,
          "detected": false,
          "hasNavigatorModelContext": false,
          "modelContextType": "undefined",
          "hasProvideContext": false,
          "hasRegisterTool": false
        }
      },
      "issue": "navigator.modelContext.provideContext(), navigator.modelContext.registerTool(), or other imperative signals were not detected in rendered browser state.",
      "howToFix": "Use navigator.modelContext.provideContext() to register tools programmatically."
    },
    {
      "id": "browser-navigator-injection",
      "title": "Detect WebMCP browser navigator injection",
      "status": "informational",
      "evidence": {
        "browser": {
          "checked": true,
          "detected": false,
          "hasNavigatorModelContext": false,
          "modelContextType": "undefined",
          "hasProvideContext": false,
          "hasRegisterTool": false
        }
      },
      "issue": "navigator.modelContext was not detected in the rendered browser page.",
      "howToFix": "Expose WebMCP through navigator.modelContext in the browser runtime when the page is intended to provide in-page tools."
    },
    {
      "id": "surface-coverage",
      "title": "Interactive surface coverage",
      "status": "informational",
      "evidence": {
        "totalForms": 1,
        "formsWithTags": 0,
        "totalInteractive": 41,
        "interactiveWithTags": 0,
        "totalCount": 42,
        "taggedCount": 0,
        "dataMcpToolCount": 0,
        "dataMcpTools": [],
        "coverage": 0,
        "annotationIssues": [
          "<textarea name=\"message\"> is missing a label.",
          "<textarea name=\"message\"> is missing tool-param-description.",
          "<input name=\"name\"> is missing a label.",
          "<input name=\"name\"> is missing tool-param-description.",
          "<input name=\"email\"> is missing a label.",
          "<input name=\"email\"> is missing tool-param-description.",
          "<select> is missing a name attribute.",
          "<select> is missing a label.",
          "<select> is missing tool-param-description.",
          "<input name=\"phone\"> is missing a label.",
          "<input name=\"phone\"> is missing tool-param-description.",
          "<input name=\"attachments\"> is missing tool-param-description."
        ]
      },
      "issue": "Only 0% of interactive surfaces are annotated.",
      "howToFix": "Add WebMCP annotations to all forms and interactive elements to increase agent coverage."
    }
  ],
  "staticSignals": {
    "detected": false,
    "matched": []
  },
  "coverage": {
    "totalForms": 1,
    "formsWithTags": 0,
    "totalInteractive": 41,
    "interactiveWithTags": 0,
    "totalCount": 42,
    "taggedCount": 0,
    "dataMcpToolCount": 0,
    "dataMcpTools": [],
    "coverage": 0,
    "annotationIssues": [
      "<textarea name=\"message\"> is missing a label.",
      "<textarea name=\"message\"> is missing tool-param-description.",
      "<input name=\"name\"> is missing a label.",
      "<input name=\"name\"> is missing tool-param-description.",
      "<input name=\"email\"> is missing a label.",
      "<input name=\"email\"> is missing tool-param-description.",
      "<select> is missing a name attribute.",
      "<select> is missing a label.",
      "<select> is missing tool-param-description.",
      "<input name=\"phone\"> is missing a label.",
      "<input name=\"phone\"> is missing tool-param-description.",
      "<input name=\"attachments\"> is missing tool-param-description."
    ]
  },
  "browserWebMcp": {
    "checked": true,
    "detected": false,
    "hasNavigatorModelContext": false,
    "modelContextType": "undefined",
    "hasProvideContext": false,
    "hasRegisterTool": false
  }
}

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": "/about/",
      "text": "About",
      "html": "<a id=\"footer-about\" href=\"/about/\">About</a>"
    },
    {
      "href": "https://www.linkedin.com/company/instahyre",
      "text": "",
      "html": "<a id=\"footer-linkedin\" href=\"https://www.linkedin.com/company/instahyre\" target=\"_blank\"><i class=\"fa fa-linkedin-square\"></i></a>"
    }
  ],
  "contactLinks": [
    {
      "href": "https://instahyre.crisp.help/en/",
      "text": "Help Center",
      "html": "<a id=\"footer-blog\" href=\"https://instahyre.crisp.help/en/\" target=\"_blank\">Help Center</a>"
    }
  ],
  "privacyLinks": [
    {
      "href": "/privacy/",
      "text": "Privacy",
      "html": "<a id=\"footer-privacy\" href=\"/privacy/\">Privacy</a>"
    },
    {
      "href": "/terms/",
      "text": "Terms",
      "html": "<a id=\"footer-terms\" href=\"/terms/\">Terms</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.

5 Fail

Needs attention

AEO: Answer evidence and trust

Failed check
01

Issue

Missing AIO trust signals: author, publisher, freshnessDate.

Details

02

Why it matters

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

Check name

AEO: Answer evidence and trust

Score

40/100

Status

fail

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

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

Result

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

Evidence
{
  "signals": {
    "author": false,
    "publisher": false,
    "freshnessDate": false,
    "aboutOrContact": true,
    "policyLinks": true
  },
  "missing": [
    "author",
    "publisher",
    "freshnessDate"
  ],
  "authorMeta": "",
  "schemaAuthors": [],
  "schemaPublishers": [],
  "schemaDates": [],
  "visibleDates": [],
  "aboutLinks": [
    {
      "href": "/about/",
      "text": "About",
      "html": "<a id=\"footer-about\" href=\"/about/\">About</a>"
    },
    {
      "href": "https://www.linkedin.com/company/instahyre",
      "text": "",
      "html": "<a id=\"footer-linkedin\" href=\"https://www.linkedin.com/company/instahyre\" target=\"_blank\"><i class=\"fa fa-linkedin-square\"></i></a>"
    }
  ],
  "contactLinks": [
    {
      "href": "https://instahyre.crisp.help/en/",
      "text": "Help Center",
      "html": "<a id=\"footer-blog\" href=\"https://instahyre.crisp.help/en/\" target=\"_blank\">Help Center</a>"
    }
  ],
  "privacyLinks": [
    {
      "href": "/privacy/",
      "text": "Privacy",
      "html": "<a id=\"footer-privacy\" href=\"/privacy/\">Privacy</a>"
    },
    {
      "href": "/terms/",
      "text": "Terms",
      "html": "<a id=\"footer-terms\" href=\"/terms/\">Terms</a>"
    }
  ],
  "score": 40,
  "weight": 22
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AIO: Visible structured data match

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

5 Warning

Needs attention

AIO: Visible structured data match

Warning
01

Issue

1 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": 1,
  "checkedFields": [
    {
      "path": "$[0].name",
      "value": "Instahyre"
    },
    {
      "path": "$[0].description",
      "value": "Instahyre is an advanced hiring platform based on artificial intelligence, enabling recruiters to hire top talent effortlessly and candidates to find their dream job."
    }
  ],
  "mismatches": [
    {
      "path": "$[0].description",
      "value": "Instahyre is an advanced hiring platform based on artificial intelligence, enabling recruiters to hire top talent effortlessly and candidates to find their dream job."
    }
  ],
  "score": 50,
  "weight": 18
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Answer-first sections

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

4 Warning

Needs attention

AEO: Answer-first sections

Warning
01

Issue

1 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": 1,
  "passing": 0,
  "failing": [
    {
      "heading": "More than 10,000 top companies",
      "headingHtml": "<h2>More than 10,000 top companies</h2>",
      "firstParagraph": "Tired of having your applications ignored by companies? Instahyre only matches you with the right jobs, leading to 5X response rates from companies compared to other job sites!",
      "paragraphHtml": "<p>Tired of having your applications ignored by companies? Instahyre only matches you with the right jobs, leading to 5X response rates from companies compared to other job sites!</p>",
      "words": 28,
      "direct": false,
      "issue": "First paragraph is 28 words and does not look like a concise direct answer."
    }
  ],
  "score": 65,
  "weight": 28
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

GEO: Entity clarity

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

4 Warning

Needs attention

GEO: Entity clarity

Warning
01

Issue

Title/H1 terms missing from description: zero, hassle, job, instahyre, dream, now.

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

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

Evidence
{
  "title": "Zero Hassle Job Search - Instahyre",
  "h1": "Your Dream Job. Now.",
  "description": "Search and apply to jobs at 10000+ top companies. Find high paying jobs in IT, software, sales, marketing, operations, finance and more. Hire top talent.",
  "topicOverlap": 0.14285714285714285,
  "topicTerms": [
    "zero",
    "hassle",
    "job",
    "search",
    "instahyre",
    "dream",
    "now"
  ],
  "descriptionTerms": [
    "search",
    "apply",
    "jobs",
    "10000",
    "top",
    "companies",
    "find",
    "high",
    "paying",
    "software",
    "sales",
    "marketing",
    "operations",
    "finance",
    "more",
    "hire",
    "talent"
  ],
  "missingFromDescription": [
    "zero",
    "hassle",
    "job",
    "instahyre",
    "dream",
    "now"
  ],
  "score": 74,
  "weight": 28
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Question-led structure

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

3 Warning

Needs attention

AEO: Question-led structure

Warning
01

Issue

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

Details

02

Why it matters

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

Check name

AEO: Question-led structure

Score

50/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

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

Result

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

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

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

GEO: Extraction-friendly structure

GEO: Extraction-friendly structure scored 85/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, ordered list only if the page explains a workflow/process, optional visible FAQ or FAQPage schema.

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

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

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

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AIO: Page experience for AIO

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

2 Warning

Needs attention

AIO: Page experience for AIO

Warning
01

Issue

7 image(s) are missing width/height attributes. 16 possible modal/interstitial element(s) 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

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

Evidence
{
  "viewportContent": "width=device-width, initial-scale=1",
  "visibleWords": 363,
  "htmlBytes": 52732,
  "imagesMissingDimensions": [
    {
      "src": "https://static.instahyre.com/images/logos/logo.webp",
      "width": "",
      "height": "",
      "loading": "",
      "html": "<img class=\"logo navbar-logo\" src=\"https://static.instahyre.com/images/logos/logo.webp\" alt=\"Instahyre\">"
    },
    {
      "src": "https://static.instahyre.com/images/icons/google-signin.webp",
      "width": "",
      "height": "",
      "loading": "",
      "html": "<img class=\"google-signin\" src=\"https://static.instahyre.com/images/icons/google-signin.webp\" alt=\"Sign in with Google\">"
    },
    {
      "src": "https://static.instahyre.com/images/icons/response.webp",
      "width": "",
      "height": "",
      "loading": "",
      "html": "<img src=\"https://static.instahyre.com/images/icons/response.webp\" alt=\"5x higher response from companies\">"
    },
    {
      "src": "https://static.instahyre.com/images/icons/target.webp",
      "width": "",
      "height": "",
      "loading": "",
      "html": "<img src=\"https://static.instahyre.com/images/icons/target.webp\" alt=\"Your perfect job delivered to you\">"
    },
    {
      "src": "https://static.instahyre.com/images/icons/privacy.webp",
      "width": "",
      "height": "",
      "loading": "",
      "html": "<img src=\"https://static.instahyre.com/images/icons/privacy.webp\" alt=\"Privacy guaranteed\">"
    },
    {
      "src": "https://static.instahyre.com/images/candidates/tushar.webp",
      "width": "",
      "height": "",
      "loading": "",
      "html": "<img src=\"https://static.instahyre.com/images/candidates/tushar.webp\" alt=\"Tushar, Hired by Paytm\">"
    },
    {
      "src": "https://static.instahyre.com/images/candidates/anurag.webp",
      "width": "",
      "height": "",
      "loading": "",
      "html": "<img src=\"https://static.instahyre.com/images/candidates/anurag.webp\" alt=\"Anurag Gupta, Hired by Arcana\">"
    }
  ],
  "possibleDialogs": [
    "<div id=\"anonymous-contact-modal\" ng-if=\"showAnonContactModal\" ng-cloak class=\"application-modal contact-modal\"><!-- djlint:on --> <div class=\"application-modal-block\"> <div ng-click=\"closeForm(false, true)\" class=\"application-modal-backdrop close-form \"> </div> <div class=\"application-modal-wrap\"> <div class=\"application-modal-heading\"> <h4 id=\"anonymous-modal-heading\">Contact Us</h4> </div> <form name=\"anonymousContactus\" ng-submit=\"submitForm()\" enctype=\"multipart/form-data\"> <div class=\"a...",
    "<div class=\"application-modal-block\"> <div ng-click=\"closeForm(false, true)\" class=\"application-modal-backdrop close-form \"> </div> <div class=\"application-modal-wrap\"> <div class=\"application-modal-heading\"> <h4 id=\"anonymous-modal-heading\">Contact Us</h4> </div> <form name=\"anonymousContactus\" ng-submit=\"submitForm()\" enctype=\"multipart/form-data\"> <div class=\"application-modal-content\"> <div class=\"row\"> <div class=\"col-sm-12\"> <div class=\"form-group\"> <label>Message / Query:</label> <text...",
    "<div ng-click=\"closeForm(false, true)\" class=\"application-modal-backdrop close-form \"> </div>",
    "<div class=\"application-modal-wrap\"> <div class=\"application-modal-heading\"> <h4 id=\"anonymous-modal-heading\">Contact Us</h4> </div> <form name=\"anonymousContactus\" ng-submit=\"submitForm()\" enctype=\"multipart/form-data\"> <div class=\"application-modal-content\"> <div class=\"row\"> <div class=\"col-sm-12\"> <div class=\"form-group\"> <label>Message / Query:</label> <textarea auctioned-field form-name=\"anonymousContactus\" name=\"message\" ng-model=\"formData.message\" class=\"form-control message-box\" rows...",
    "<div class=\"application-modal-heading\"> <h4 id=\"anonymous-modal-heading\">Contact Us</h4> </div>",
    "<h4 id=\"anonymous-modal-heading\">Contact Us</h4>",
    "<div class=\"application-modal-content\"> <div class=\"row\"> <div class=\"col-sm-12\"> <div class=\"form-group\"> <label>Message / Query:</label> <textarea auctioned-field form-name=\"anonymousContactus\" name=\"message\" ng-model=\"formData.message\" class=\"form-control message-box\" rows=\"4\"></textarea> <input auctioned-field form-name=\"anonymousContactus\" name=\"message\" type=\"hidden\"> </div> </div> <div class=\"col-sm-12\"> <div class=\"form-group\"> <label>Your name:</label> <input auctioned-field form-nam...",
    "<div class=\"application-modal-action text-center\"> <button ng-click=\"closeForm(false, true)\" type=\"button\" class=\"btn btn-default close-form\">Cancel</button> <button class=\"btn btn-primary anonymous_submit\" type=\"submit\">Submit</button> </div>",
    "<div id=\"anonymous-contact-modal\" ng-show=\"anonContactSubmitMsg\" ng-cloak class=\"application-modal contact-modal\"> <div class=\"application-modal-block\"> <div ng-click=\"closeForm(false, true)\" class=\"application-modal-backdrop close-form \"> </div> <div class=\"application-modal-wrap\"> <div class=\"application-modal-heading\"> <h4 id=\"anonymous-modal-heading\">Your query has been sent</h4> </div> <div class=\"application-modal-content\"> <center>One of our representatives will contact you shortly.</c...",
    "<div class=\"application-modal-block\"> <div ng-click=\"closeForm(false, true)\" class=\"application-modal-backdrop close-form \"> </div> <div class=\"application-modal-wrap\"> <div class=\"application-modal-heading\"> <h4 id=\"anonymous-modal-heading\">Your query has been sent</h4> </div> <div class=\"application-modal-content\"> <center>One of our representatives will contact you shortly.</center> </div> <div class=\"application-modal-action text-center\"> <button ng-click=\"closeForm(false, false)\" class=\"...",
    "<div ng-click=\"closeForm(false, true)\" class=\"application-modal-backdrop close-form \"> </div>",
    "<div class=\"application-modal-wrap\"> <div class=\"application-modal-heading\"> <h4 id=\"anonymous-modal-heading\">Your query has been sent</h4> </div> <div class=\"application-modal-content\"> <center>One of our representatives will contact you shortly.</center> </div> <div class=\"application-modal-action text-center\"> <button ng-click=\"closeForm(false, false)\" class=\"btn btn-default close-form\">Close</button> </div> </div>",
    "<div class=\"application-modal-heading\"> <h4 id=\"anonymous-modal-heading\">Your query has been sent</h4> </div>",
    "<h4 id=\"anonymous-modal-heading\">Your query has been sent</h4>",
    "<div class=\"application-modal-content\"> <center>One of our representatives will contact you shortly.</center> </div>",
    "<div class=\"application-modal-action text-center\"> <button ng-click=\"closeForm(false, false)\" class=\"btn btn-default close-form\">Close</button> </div>"
  ],
  "score": 70,
  "weight": 10
}

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

1 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": 1,
  "passing": 0,
  "failing": [
    {
      "heading": "More than 10,000 top companies",
      "headingHtml": "<h2>More than 10,000 top companies</h2>",
      "firstParagraph": "Tired of having your applications ignored by companies? Instahyre only matches you with the right jobs, leading to 5X response rates from companies compared to other job sites!",
      "paragraphHtml": "<p>Tired of having your applications ignored by companies? Instahyre only matches you with the right jobs, leading to 5X response rates from companies compared to other job sites!</p>",
      "words": 28,
      "direct": false,
      "issue": "First paragraph is 28 words and does not look like a concise direct answer."
    }
  ],
  "score": 65,
  "weight": 8
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Entity and definition clarity

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

1 Warning

Needs attention

AEO: Entity and definition clarity

Warning
01

Issue

Entity or definition gaps: zero, hassle, job, instahyre, dream, now.

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

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

Evidence
{
  "title": "Zero Hassle Job Search - Instahyre",
  "h1": "Your Dream Job. Now.",
  "description": "Search and apply to jobs at 10000+ top companies. Find high paying jobs in IT, software, sales, marketing, operations, finance and more. Hire top talent.",
  "topicOverlap": 0.14285714285714285,
  "definitionCount": 2,
  "topicTerms": [
    "zero",
    "hassle",
    "job",
    "search",
    "instahyre",
    "dream",
    "now"
  ],
  "descriptionTerms": [
    "search",
    "apply",
    "jobs",
    "10000",
    "top",
    "companies",
    "find",
    "high",
    "paying",
    "software",
    "sales",
    "marketing",
    "operations",
    "finance",
    "more",
    "hire",
    "talent"
  ],
  "missingFromDescription": [
    "zero",
    "hassle",
    "job",
    "instahyre",
    "dream",
    "now"
  ],
  "score": 79,
  "weight": 18
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Answer intent coverage

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

1 Warning

Needs attention

AEO: Answer intent coverage

Warning
01

Issue

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

Details

02

Why it matters

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

Check name

AEO: Answer intent coverage

Score

70/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

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

Result

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

Evidence
{
  "headings": [
    {
      "text": "More than 10,000 top companies",
      "html": "<h2>More than 10,000 top companies</h2>"
    }
  ],
  "expected": [
    {
      "id": "what",
      "label": "What is Zero Hassle Job Search - Instahyre?",
      "pattern": {}
    },
    {
      "id": "how",
      "label": "How does Zero Hassle Job Search - Instahyre work?",
      "pattern": {}
    },
    {
      "id": "benefits",
      "label": "Why use Zero Hassle Job Search - Instahyre?",
      "pattern": {}
    },
    {
      "id": "cost",
      "label": "Is Zero Hassle Job Search - Instahyre free or paid?",
      "pattern": {}
    },
    {
      "id": "compare",
      "label": "How does Zero Hassle Job Search - Instahyre compare with alternatives?",
      "pattern": {}
    }
  ],
  "missing": [
    {
      "id": "what",
      "label": "What is Zero Hassle Job Search - Instahyre?",
      "pattern": {}
    },
    {
      "id": "how",
      "label": "How does Zero Hassle Job Search - Instahyre work?",
      "pattern": {}
    },
    {
      "id": "benefits",
      "label": "Why use Zero Hassle Job Search - Instahyre?",
      "pattern": {}
    },
    {
      "id": "cost",
      "label": "Is Zero Hassle Job Search - Instahyre free or paid?",
      "pattern": {}
    },
    {
      "id": "compare",
      "label": "How does Zero Hassle Job Search - Instahyre compare with alternatives?",
      "pattern": {}
    }
  ],
  "score": 70,
  "weight": 8
}

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": 403,
            "contentType": "text/html; charset=UTF-8",
            "length": 5471
          },
          {
            "path": "/api/context",
            "statusCode": 403,
            "contentType": "text/html; charset=UTF-8",
            "length": 5462
          },
          {
            "path": "/context",
            "statusCode": 403,
            "contentType": "text/html; charset=UTF-8",
            "length": 5450
          }
        ]
      },
      "issue": "AI context endpoint was not found at the expected path.",
      "howToFix": "Publish a concise JSON or Markdown AI context endpoint describing the product, public actions, and machine-readable resources."
    }
  ]
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AIO: Query intent coverage

AIO: Query intent coverage is informational for this page.

Informational

Needs attention

AIO: Query intent coverage

Informational
01

Issue

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

Details

02

Why it matters

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

Check name

AIO: Query intent coverage

Score

70/100

Status

informational

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

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

Result

AIO: Query intent coverage is informational for this page.

Evidence
{
  "headings": [
    {
      "text": "More than 10,000 top companies",
      "html": "<h2>More than 10,000 top companies</h2>"
    }
  ],
  "expected": [
    {
      "id": "what",
      "label": "What is Zero Hassle Job Search - Instahyre?",
      "pattern": {}
    },
    {
      "id": "how",
      "label": "How does Zero Hassle Job Search - Instahyre work?",
      "pattern": {}
    },
    {
      "id": "benefits",
      "label": "Why use Zero Hassle Job Search - Instahyre?",
      "pattern": {}
    },
    {
      "id": "cost",
      "label": "Is Zero Hassle Job Search - Instahyre free or paid?",
      "pattern": {}
    },
    {
      "id": "compare",
      "label": "How does Zero Hassle Job Search - Instahyre compare with alternatives?",
      "pattern": {}
    }
  ],
  "missing": [
    {
      "id": "what",
      "label": "What is Zero Hassle Job Search - Instahyre?",
      "pattern": {}
    },
    {
      "id": "how",
      "label": "How does Zero Hassle Job Search - Instahyre work?",
      "pattern": {}
    },
    {
      "id": "benefits",
      "label": "Why use Zero Hassle Job Search - Instahyre?",
      "pattern": {}
    },
    {
      "id": "cost",
      "label": "Is Zero Hassle Job Search - Instahyre free or paid?",
      "pattern": {}
    },
    {
      "id": "compare",
      "label": "How does Zero Hassle Job Search - Instahyre compare with alternatives?",
      "pattern": {}
    }
  ],
  "score": 70,
  "weight": 4
}

Agent Ease of UseAuthEmerging recommendation

Auth.md Agent Registration

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

Informational

Needs attention

Auth.md Agent Registration

Informational
01

Issue

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

02

Why it matters

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

Check name

Auth.md Agent Registration

Score

0/100

Status

informational

Category

Auth

Maturity

Emerging recommendation

Goal

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

Result

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

Validation steps

  1. Fetch and validate /auth.md

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

  2. Publish protected resource metadata

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

  3. Validate agent_auth authorization metadata

    OAuth authorization server metadata could not be fetched.

Evidence
{
  "failedStep": "auth-md",
  "steps": [
    {
      "id": "auth-md",
      "title": "Fetch and validate /auth.md",
      "status": "fail",
      "evidence": {
        "path": "/auth.md",
        "ok": false,
        "statusCode": 403,
        "contentType": "text/html; charset=UTF-8",
        "length": 5450,
        "validation": {
          "valid": false,
          "issue": "auth.md response did not match the expected agent registration shape. Content-Type \"text/html; charset=UTF-8\" is not Markdown or text/plain; missing registration instructions; missing /.well-known/oauth-protected-resource link; missing /.well-known/oauth-authorization-server link; missing supported identity type language; missing credential type language.",
          "compatibleContentType": false,
          "contentLength": 5428,
          "hasRegisterInstructions": false,
          "hasProtectedResourceLink": false,
          "hasAuthorizationServerLink": false,
          "mentionsIdentity": false,
          "mentionsCredential": false,
          "links": [
            "/title",
            "/html;",
            "https://challenges.cloudflare.com;",
            "https://challenges.cloudflare.com;",
            "https://challenges.cloudflare.com;",
            "https://challenges.cloudflare.com",
            "https://challenges.cloudflare.com",
            "/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHdpZHRoPSIzMiIgaGVpZ2h0PSIzMiIgZmlsbD0ibm9uZSI+PHBhdGggZmlsbD0iI0IyMEYwMyIgZD0iTTE2IDNhMTMgMTMgMCAxIDAgMTMgMTNBMTMuMDE1IDEzLjAxNSAwIDAgMCAxNiAzbTAgMjRhMTEgMTEgMCAxIDEgMTEtMTEgMTEuMDEgMTEuMDEgMCAwIDEtMTEgMTEiLz48cGF0aCBmaWxsPSIjQjIwRjAzIiBkPSJNMTcuMDM4IDE4LjYxNUgxNC44N0wxNC41NjMgOS41aDIuNzgzem0tMS4wODQgMS40MjdxLjY2IDAgMS4wNTcuMzg4LjQwNy4zODkuNDA3Ljk5NCAwIC41OTYtLjQwNy45ODQtLjM5Ny4zOS0xLjA1Ny4zODktLjY1IDAtMS4wNTYtLjM4OS0uMzk4LS4zODktLjM5OC0uOTg0IDAtLjU5Ny4zOTgtLjk4NS40MDYtLjM5NyAxLjA1Ni0uMzk3Ii8+PC9zdmc+",
            "/style",
            "/head"
          ],
          "rawExcerpt": "<!DOCTYPE html><html lang=\"en-US\"><head><title>Just a moment...</title><meta http-equiv=\"Content-Type\" content=\"text/html; charset=UTF-8\"><meta http-equiv=\"X-UA-Compatible\" content=\"IE=Edge\"><meta name=\"robots\" content=\"noindex,nofollow\"><meta name=\"viewport\" content=\"width=device-width,initial-scale=1\"><meta http-equiv=\"content-security-policy\" content=\"default-src &#39;none&#39;; script-src &#39;nonce-FgN3HsErzd2HNCnOU9E0xG&#39; &#39;unsafe-eval&#39; https://challenges.cloudflare.com; script-src-attr &#39;none&#39;; style-src &#39;unsafe-inline&#39;; img-src &#39;self&#39; https://challenges.cloudflare.com; connect-src &#39;self&#39; https://challenges.cloudflare.com; frame-src &#39;self&#39; https://challenges.cloudflare.com blob:; child-src &#39;self&#39; https://challenges.cloudflare."
        }
      },
      "issue": "auth.md response did not match the expected agent registration shape. Content-Type \"text/html; charset=UTF-8\" is not Markdown or text/plain; missing registration instructions; missing /.well-known/oauth-protected-resource link; missing /.well-known/oauth-authorization-server link; missing supported identity type language; missing credential type language.",
      "howToFix": "Serve /auth.md at the site root as Markdown with agent registration instructions and links to OAuth metadata."
    },
    {
      "id": "oauth-protected-resource",
      "title": "Publish protected resource metadata",
      "status": "fail",
      "evidence": {
        "path": "/.well-known/oauth-protected-resource",
        "ok": false,
        "statusCode": 404,
        "contentType": "text/html; charset=utf-8",
        "length": 49101,
        "text": "\n\n\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\">\n\n        \n            <link rel=\"canonical\" href=\"https://www.instahyre.com/.well-known/oauth-protected-resource\">\n        \n\n        \n            <title>Zero Hassle Job Search - Instahyre</title>\n        \n\n        \n            <meta property=\"og:description\"     content=\"Let the best companies in India compete to hire you! Get your perfect job in tech, product, marketing, sales or operations. Hire the best talent faster.\">\n            <meta name=\"description\"            content=\"Let the best companies in India compete to hire you! Get your perfect job in tech, product, marketing, sales or operations. Hire the best talent faster.\">\n            <meta name=\"twitter:description\"    content=\"Let the best companies in India compete to hire you! Get your perfect job in tech, product, marketing, sales or operations. Hire the best talent faster.\">\n        \n\n        \n            <meta property=\"og:title\"           content=\"The Zero Hassle Hiring Platform - Instahyre\">\n            <meta property=\"og:type\"            content=\"website\">\n            <meta property=\"og:url\"             content=\"https://www.instahyre.com\">\n            <meta property=\"og:image\"           content=\"https://static.instahyre.com/images/misc/facebook-image.webp\">\n            <meta property=\"og:image:width\"     content=\"800\">\n            <meta property=\"og:image:height\"    content=\"500\">\n            <meta property=\"og:site_name\"       content=\"Instahyre\">\n\n            <meta name=\"twitter:card\"           content=\"summary_large_image\">\n            <meta name=\"twitter:site\"           content=\"@instahyre\">\n            <meta name=\"twitter:title\"          content=\"The Zero Hassle Hiring Platform - Instahyre\">\n            <meta name=\"twitter:image\"          content=\"https://static.instahyre.com/images/misc/facebook-image.webp\">\n        \n\n        <link rel=\"apple-touch-icon\" sizes=\"57x57\" href=\"https://static.instahyre.com/images/apple-touch/apple-touch-icon-57x57.webp\">\n        <link rel=\"apple-touch-icon\" sizes=\"114x114\" href=\"https://static.instahyre.com/images/apple-touch/apple-touch-icon-114x114.webp\">\n        <link rel=\"apple-touch-icon\" sizes=\"72x72\" href=\"https://static.instahyre.com/images/apple-touch/apple-touch-icon-72x72.webp\">\n        <link rel=\"apple-touch-icon\" sizes=\"144x144\" href=\"https://static.instahyre.com/images/apple-touch/apple-touch-icon-144x144.webp\">\n        <link rel=\"apple-touch-icon\" sizes=\"60x60\" href=\"https://static.instahyre.com/images/apple-touch/apple-touch-icon-60x60.webp\">\n        <link rel=\"apple-touch-icon\" sizes=\"120x120\" href=\"https://static.instahyre.com/images/apple-touch/apple-touch-icon-120x120.webp\">\n        <link rel=\"apple-touch-icon\" sizes=\"76x76\" href=\"https://static.instahyre.com/images/apple-touch/apple-touch-icon-76x76.webp\">\n        <link rel=\"apple-touch-icon\" sizes=\"152x152\" href=\"https://static.instahyre.com/images/apple-touch/apple-touch-icon-152x152.webp\">\n        <link rel=\"apple-touch-icon\" sizes=\"180x180\" href=\"https://static.instahyre.com/images/apple-touch/apple-touch-icon-180x180.webp\">\n        <link rel=\"manifest\" href=\"https://static.instahyre.com/images/android-homescreen/manifest.json\">\n\n        \n            <link rel=\"icon\" type=\"image/x-icon\" href=\"/favicon.ico\"/>\n        \n\n        <!-- CSS Stylesheets -->\n        \n            \n                \n\n<link href=\"//cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.7/css/bootstrap.min.css\" rel=\"stylesheet\">\n\n\n    <link rel=\"stylesheet\" href=\"https://static.instahyre.com/css/output.661c5e47ab02.css\" type=\"text/css\">\n\n\n\n\n\n    <link rel=\"stylesheet\" href=\"https://static.instahyre.com/css/output.22f3fff48233.css\" type=\"text/css\">\n\n\n\n            \n\n            \n                <link rel=\"stylesheet\" href=\"https://static.instahyre.com/css/output.37d00aab9bd5.css\" type=\"text/css\">\n            \n\n            <!-- Sta"
      },
      "issue": "The OAuth Protected Resource metadata endpoint did not return HTTP 2xx.",
      "howToFix": "Publish /.well-known/oauth-protected-resource with resource and authorization_servers fields."
    },
    {
      "id": "agent-auth-block",
      "title": "Validate agent_auth authorization metadata",
      "status": "fail",
      "evidence": {
        "valid": false,
        "issue": "OAuth authorization server metadata could not be fetched.",
        "fetch": {
          "ok": false,
          "statusCode": 404,
          "contentType": "text/html; charset=utf-8",
          "length": 49103,
          "text": "\n\n\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\">\n\n        \n            <link rel=\"canonical\" href=\"https://www.instahyre.com/.well-known/oauth-authorization-server\">\n        \n\n        \n            <title>Zero Hassle Job Search - Instahyre</title>\n        \n\n        \n            <meta property=\"og:description\"     content=\"Let the best companies in India compete to hire you! Get your perfect job in tech, product, marketing, sales or operations. Hire the best talent faster.\">\n            <meta name=\"description\"            content=\"Let the best companies in India compete to hire you! Get your perfect job in tech, product, marketing, sales or operations. Hire the best talent faster.\">\n            <meta name=\"twitter:description\"    content=\"Let the best companies in India compete to hire you! Get your perfect job in tech, product, marketing, sales or operations. Hire the best talent faster.\">\n        \n\n        \n            <meta property=\"og:title\"           content=\"The Zero Hassle Hiring Platform - Instahyre\">\n            <meta property=\"og:type\"            content=\"website\">\n            <meta property=\"og:url\"             content=\"https://www.instahyre.com\">\n            <meta property=\"og:image\"           content=\"https://static.instahyre.com/images/misc/facebook-image.webp\">\n            <meta property=\"og:image:width\"     content=\"800\">\n            <meta property=\"og:image:height\"    content=\"500\">\n            <meta property=\"og:site_name\"       content=\"Instahyre\">\n\n            <meta name=\"twitter:card\"           content=\"summary_large_image\">\n            <meta name=\"twitter:site\"           content=\"@instahyre\">\n            <meta name=\"twitter:title\"          content=\"The Zero Hassle Hiring Platform - Instahyre\">\n            <meta name=\"twitter:image\"          content=\"https://static.instahyre.com/images/misc/facebook-image.webp\">\n        \n\n        <link rel=\"apple-touch-icon\" sizes=\"57x57\" href=\"https://static.instahyre.com/images/apple-touch/apple-touch-icon-57x57.webp\">\n        <link rel=\"apple-touch-icon\" sizes=\"114x114\" href=\"https://static.instahyre.com/images/apple-touch/apple-touch-icon-114x114.webp\">\n        <link rel=\"apple-touch-icon\" sizes=\"72x72\" href=\"https://static.instahyre.com/images/apple-touch/apple-touch-icon-72x72.webp\">\n        <link rel=\"apple-touch-icon\" sizes=\"144x144\" href=\"https://static.instahyre.com/images/apple-touch/apple-touch-icon-144x144.webp\">\n        <link rel=\"apple-touch-icon\" sizes=\"60x60\" href=\"https://static.instahyre.com/images/apple-touch/apple-touch-icon-60x60.webp\">\n        <link rel=\"apple-touch-icon\" sizes=\"120x120\" href=\"https://static.instahyre.com/images/apple-touch/apple-touch-icon-120x120.webp\">\n        <link rel=\"apple-touch-icon\" sizes=\"76x76\" href=\"https://static.instahyre.com/images/apple-touch/apple-touch-icon-76x76.webp\">\n        <link rel=\"apple-touch-icon\" sizes=\"152x152\" href=\"https://static.instahyre.com/images/apple-touch/apple-touch-icon-152x152.webp\">\n        <link rel=\"apple-touch-icon\" sizes=\"180x180\" href=\"https://static.instahyre.com/images/apple-touch/apple-touch-icon-180x180.webp\">\n        <link rel=\"manifest\" href=\"https://static.instahyre.com/images/android-homescreen/manifest.json\">\n\n        \n            <link rel=\"icon\" type=\"image/x-icon\" href=\"/favicon.ico\"/>\n        \n\n        <!-- CSS Stylesheets -->\n        \n            \n                \n\n<link href=\"//cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.7/css/bootstrap.min.css\" rel=\"stylesheet\">\n\n\n    <link rel=\"stylesheet\" href=\"https://static.instahyre.com/css/output.661c5e47ab02.css\" type=\"text/css\">\n\n\n\n\n\n    <link rel=\"stylesheet\" href=\"https://static.instahyre.com/css/output.22f3fff48233.css\" type=\"text/css\">\n\n\n\n            \n\n            \n                <link rel=\"stylesheet\" href=\"https://static.instahyre.com/css/output.37d00aab9bd5.css\" type=\"text/css\">\n            \n\n            <!-- S"
        }
      },
      "issue": "OAuth authorization server metadata could not be fetched.",
      "howToFix": "Add agent_auth to /.well-known/oauth-authorization-server with register_uri, supported identity types, credential types, and claim or revocation URLs where applicable."
    }
  ],
  "authApplicability": {
    "supportsAuth": true,
    "score": 15,
    "signals": [
      {
        "source": "link:href",
        "weight": 3,
        "match": "auth link"
      },
      {
        "source": "visible-text",
        "weight": 3,
        "match": "login"
      },
      {
        "source": "visible-text",
        "weight": 3,
        "match": "sign in"
      },
      {
        "source": "visible-text",
        "weight": 3,
        "match": "sign up"
      },
      {
        "source": "visible-text",
        "weight": 3,
        "match": "signup"
      }
    ]
  },
  "resourceFetchSucceeded": false
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

GEO: Q&A and FAQ opportunities

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

Informational

Needs attention

GEO: Q&A and FAQ opportunities

Informational
01

Issue

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

Details

02

Why it matters

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

Check name

GEO: Q&A and FAQ opportunities

Score

75/100

Status

informational

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

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

Result

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

Evidence
{
  "h2Count": 1,
  "questionH2s": 0,
  "hasFaq": false,
  "nonQuestionH2s": [
    {
      "index": 1,
      "text": "More than 10,000 top companies",
      "isQuestion": false,
      "html": "<h2>More than 10,000 top companies</h2>"
    }
  ],
  "score": 75,
  "weight": 4
}

AI DiscoverabilityDiscoverabilityEstablished

IndexNow key

IndexNow key is informational for this page.

Informational

Needs attention

IndexNow key

Informational
01

Issue

IndexNow key is informational for this page.

02

Why it matters

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

Check name

IndexNow key

Score

100/100

Status

informational

Category

Discoverability

Maturity

Established

Goal

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

Result

IndexNow key is informational for this page.

Validation steps

  1. Find advertised IndexNow key location

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

  2. Fetch and validate IndexNow key file

    No discoverable IndexNow key file was found.

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

Agent Ease of UseAuthEstablished

OAuth / OIDC discovery

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

Informational

Needs attention

OAuth / OIDC discovery

Informational
01

Issue

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

02

Why it matters

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

Check name

OAuth / OIDC discovery

Score

0/100

Status

informational

Category

Auth

Maturity

Established

Goal

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

Result

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

Validation steps

  1. Fetch to find resource

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

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

Agent Ease of UseAuthEmerging recommendation

OAuth Protected Resource

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

Informational

Needs attention

OAuth Protected Resource

Informational
01

Issue

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

02

Why it matters

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

Check name

OAuth Protected Resource

Score

0/100

Status

informational

Category

Auth

Maturity

Emerging recommendation

Goal

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

Result

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

Validation steps

  1. Fetch protected resource metadata

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

  2. Validate protected resource metadata

    Response is not valid JSON.

  3. Validate protected resource identity

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

  4. Probe protected API Bearer challenge

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

Evidence
{
  "failedStep": "fetch",
  "steps": [
    {
      "id": "fetch",
      "title": "Fetch protected resource metadata",
      "status": "fail",
      "evidence": {
        "path": "/.well-known/oauth-protected-resource",
        "statusCode": 404,
        "contentType": "text/html; charset=utf-8"
      },
      "issue": "The OAuth Protected Resource metadata endpoint did not return HTTP 2xx.",
      "howToFix": "Publish /.well-known/oauth-protected-resource JSON."
    },
    {
      "id": "metadata",
      "title": "Validate protected resource metadata",
      "status": "fail",
      "evidence": {
        "valid": false,
        "compatibleContentType": false,
        "issue": "Response is not valid JSON.",
        "rawExcerpt": "\n\n\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\">\n\n        \n            <link rel=\"canonical\" href=\"https://www.instahyre.com/.well-known/oauth-protected-resource\">\n        \n\n        \n            <title>Zero Hassle Job Search - Instahyre</title>\n        \n\n        \n            <meta property=\"og:description\"     content=\"Let the best companies in India compete to hire you! Get your perfect job in tech, product, marketing, sales or operations. Hire the best talent faster.\">\n            <meta name=\"description\"            content=\"Let the best companies in India compete to hire you! Get your perfect job in tech, product, marketing, sales or operations. Hire the best talent faster.\">\n      "
      },
      "issue": "Response is not valid JSON.",
      "howToFix": "Publish resource and authorization_servers as absolute URLs."
    },
    {
      "id": "resource-identity",
      "title": "Validate protected resource identity",
      "status": "fail",
      "evidence": {
        "expectedResource": "https://www.instahyre.com"
      },
      "issue": "Protected resource metadata `resource` did not match the resource identifier used to retrieve it.",
      "howToFix": "Set `resource` to the origin/resource identifier represented by /.well-known/oauth-protected-resource."
    },
    {
      "id": "protected-route-challenge",
      "title": "Probe protected API Bearer challenge",
      "status": "informational",
      "evidence": {
        "checked": [
          {
            "path": "/api/admin/scans",
            "statusCode": 403,
            "wwwAuthenticate": {
              "valid": false,
              "present": false
            },
            "expectedMetadataUrl": "https://www.instahyre.com/.well-known/oauth-protected-resource",
            "metadataUrlMatches": true,
            "resourceMatchesRequestContext": true
          },
          {
            "path": "/api/admin/summary",
            "statusCode": 403,
            "wwwAuthenticate": {
              "valid": false,
              "present": false
            },
            "expectedMetadataUrl": "https://www.instahyre.com/.well-known/oauth-protected-resource",
            "metadataUrlMatches": true,
            "resourceMatchesRequestContext": true
          },
          {
            "path": "/api/scans",
            "statusCode": 403,
            "wwwAuthenticate": {
              "valid": false,
              "present": false
            },
            "expectedMetadataUrl": "https://www.instahyre.com/.well-known/oauth-protected-resource",
            "metadataUrlMatches": true,
            "resourceMatchesRequestContext": true
          }
        ]
      },
      "issue": "No protected route with a 401 Bearer challenge was detected; metadata alone does not prove a protected resource.",
      "howToFix": "When this site exposes bearer-protected APIs, return 401 with WWW-Authenticate: Bearer and link resource_metadata."
    }
  ],
  "authApplicability": {
    "supportsAuth": true,
    "score": 15,
    "signals": [
      {
        "source": "link:href",
        "weight": 3,
        "match": "auth link"
      },
      {
        "source": "visible-text",
        "weight": 3,
        "match": "login"
      },
      {
        "source": "visible-text",
        "weight": 3,
        "match": "sign in"
      },
      {
        "source": "visible-text",
        "weight": 3,
        "match": "sign up"
      },
      {
        "source": "visible-text",
        "weight": 3,
        "match": "signup"
      }
    ]
  },
  "resourceFetchSucceeded": false
}

SEOSEOBrowser audit

Links are not crawlable

50 Fail

Check name

Links are not crawlable

Score

0/100

Status

fail

Device

desktop

Category

SEO

Fix guidance

Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. [Learn how to make links crawlable](https://support.google.com/webmasters/answer/9112205)

Evidence
{
  "description": "Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. [Learn how to make links crawlable](https://support.google.com/webmasters/answer/9112205)"
}

SEOSEOBrowser audit

robots.txt is not valid

50 Fail

Check name

robots.txt is not valid

Score

0/100

Status

fail

Device

desktop

Category

SEO

Estimated savings

Request for robots.txt returned HTTP status: 520

Fix guidance

If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. [Learn more about robots.txt](https://developer.chrome.com/docs/lighthouse/seo/invalid-robots-txt/).

Evidence
{
  "displayValue": "Request for robots.txt returned HTTP status: 520",
  "description": "If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. [Learn more about robots.txt](https://developer.chrome.com/docs/lighthouse/seo/invalid-robots-txt/)."
}

Performance and AccessibilityPerformanceBrowser audit

List items (`<li>`) are not contained within `<ul>`, `<ol>` or `<menu>` parent elements.

33 Fail

Check name

List items (`<li>`) are not contained within `<ul>`, `<ol>` or `<menu>` parent elements.

Score

0/100

Status

fail

Device

desktop

Category

Performance

Fix guidance

Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. [Learn more about proper list structure](https://dequeuniversity.com/rules/axe/4.11/listitem).

Evidence
{
  "description": "Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. [Learn more about proper list structure](https://dequeuniversity.com/rules/axe/4.11/listitem)."
}

Performance and AccessibilityPerformanceBrowser audit

Reduce unused JavaScript

33 Fail

Check name

Reduce unused JavaScript

Score

0/100

Status

fail

Device

desktop

Category

Performance

Estimated savings

Est savings of 207 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 207 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": 80
}

Performance and AccessibilityPerformanceBrowser audit

Use efficient cache lifetimes

33 Fail

Check name

Use efficient cache lifetimes

Score

0/100

Status

fail

Device

desktop

Category

Performance

Estimated savings

Est savings of 401 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 401 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)."
}

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
56/100Level 3, Bot-AwareCurrent report
instahyre.com AI SEO Report: 56/100 (Level 3, Bot-Aware)