completed

HTTP 200

0 redirects

37 checks

Website audit scorecard for getdocpilot.pro

The scanner fetched the public page, extracted deterministic facts, and stored scored results across SEO / AEO, security, accessibility, and design.

Submitted

https://getdocpilot.pro/

Final URL

https://getdocpilot.pro

Created

Jul 31, 2026, 9:03 PM

Safe fetch

79 ms

Four-score result

Needs fixes before launch (High risk): 17 passed, 19 failed, and 1 unknown. Strongest area: Security. Weakest area: Design.

Overall

out of 100

SEO / AEO

out of 100

51/103 rule points

Security

out of 100

46/76 rule points

Accessibility

out of 100

47/94 rule points

Design

out of 100

31/110 rule points

Why this scored this way

Scores are deterministic: each category earns rule points for verified public signals and loses points for failed checks. Unknown checks are shown separately instead of guessed.

Category point breakdown

SEO / AEO51/103

Security46/76

Accessibility47/94

Design31/110

Biggest score-losing checks

high

Accessibility

Rendered axe accessibility violations

axe found 3 violation rule(s), including 1 serious or critical rule(s). Top rules: color-contrast (2), heading-order (1), meta-viewport (1).

critical

Security

Sensitive file probes

A small allowlist probe returned a public success response.

high

Security

Common security headers

Detected 1 of 5 common public security headers. Present: strict-transport-security. Missing: content-security-policy, x-content-type-options, x-frame-options, referrer-policy.

high

Design

Visible primary CTA

Detected 0 CTA candidate(s).

Recommendations

Score-losing issues ordered by remediation priority, severity, and score impact.

5 fixes

7 opportunities

9 insights

fail

critical

Security

Priority 1

Remove exposed sensitive files

-16 rule pts

What failed

A small public allowlist probe found a sensitive-looking file path.

Evidence

A small allowlist probe returned a public success response.

Priority

Priority 1: fix before sharing the page publicly.

Why it matters

Publicly exposed config or backup files can leak implementation details or secrets.

How to fix it

Remove the exposed file, block public access to that path, and rotate any secrets that may have been exposed.

Copyable agent prompt

## Role
Act as a focused expert website launch remediation agent for this workflow.
## Inputs
- Primary context: Improve getdocpilot.pro at https://getdocpilot.pro.
- Fix title: Remove exposed sensitive files.
- Scanner check: Sensitive file probes.
- Category: Security.
- Status: fail.
- Severity: critical.
- Priority: 1; lower numbers are more urgent.
- Score impact: 16 rule points lost.
- Evidence: A small allowlist probe returned a public success response.
- What needs attention: A small public allowlist probe found a sensitive-looking file path.
- Why it matters: Publicly exposed config or backup files can leak implementation details or secrets.
- Status-specific guidance: A public check reported a failure. Reproduce or inspect the issue first, then make the smallest safe fix.
- Audience or recipient: The site owner, builder, or marketing team responsible for improving this public page.
- Constraints, examples, or source material: Treat the live URL as the public target to inspect, not as the only source of truth. When repository, CMS, or hosting access is available, use that implementation context before changing anything.
- Target outcome: After the fix is deployed and the public page is rescanned, this specific check should improve or pass without lowering other SEO / AEO, security, accessibility, or design signals.
## Task
Use the provided context to safely complete this workflow: Remove the exposed file, block public access to that path, and rotate any secrets that may have been exposed.
Before editing, identify the likely source of the issue, the smallest change that can fix it, and any user-visible behavior that must be preserved.
## Output
Return a structured response with headings, prioritized recommendations, changed files or page areas, verification results, rollback notes, and stated assumptions.
## Rules
- Ask a clarifying question when required context is missing.
- Preserve the user's intent and avoid inventing facts.
- Verify the issue exists before changing code or content. If the issue is not reproducible, explain what you checked and recommend no code change.
- If the live URL and implementation source disagree, trust the implementation source for edits and use the live URL only to understand current public behavior.
- Keep the change narrowly scoped to this fix unless another change is required to avoid a regression.
- Match the existing framework, style, design system, routing patterns, and content conventions.
- Preserve existing URLs, forms, analytics, SEO metadata, accessibility semantics, and conversion flows unless the fix explicitly requires changing them.
- Do not perform broad refactors, dependency upgrades, redesigns, rewrites, migrations, file deletions, route changes, or destructive commands unless they are explicitly required and approved.
- Make changes that are easy to review and roll back.
- Verify the result with the smallest reliable test, build, browser check, or manual inspection available.
## Safety
- Do not request, expose, or reproduce sensitive data.
- Redact private details from examples unless the user explicitly says they are safe to include.
- Do not use credentials, cookies, authenticated data, hidden form values, or private response bodies.
- Do not weaken security headers, authentication, authorization, privacy controls, accessibility, or error handling to make the scan pass.

unknown

critical

SEO / AEO

Priority 2

Improve AI search and crawler readiness

-8 rule pts

What needs verification

One or more AI discovery, user-fetch, indexability, snippet, synthetic reachability, or sitemap signals need attention.

Evidence

FreeScan.app reached the public page with HTTP 200. AEO crawler readiness is 92%: discovery 45/45, index and snippet eligibility 20/25, synthetic reachability 20/20, sitemap freshness 7/10. robots.txt did not block the scored AI search or user-fetch agents for this page path.

Priority

Priority 2: fix before sharing the page publicly.

Why it matters

AI search systems need crawlable, reachable, indexable, and quotable public content. Training and data-use choices remain neutral publisher preferences.

How to fix it

Use the component scores and exact matched robots rules in the crawler report. Fix blocked search agents, noindex or snippet restrictions, canonical or sitemap gaps, and synthetic WAF/challenge failures. Preserve intentional training opt-outs and keep private, admin, and authenticated paths protected before rescanning.

Copyable agent prompt

## Role
Act as a focused expert website launch remediation agent for this workflow.
## Inputs
- Primary context: Improve getdocpilot.pro at https://getdocpilot.pro.
- Fix title: Improve AI search and crawler readiness.
- Scanner check: Crawler access.
- Category: SEO / AEO.
- Status: unknown.
- Severity: critical.
- Priority: 2; lower numbers are more urgent.
- Score impact: 8 rule points lost.
- Evidence: FreeScan.app reached the public page with HTTP 200. AEO crawler readiness is 92%: discovery 45/45, index and snippet eligibility 20/25, synthetic reachability 20/20, sitemap freshness 7/10. robots.txt did not block the scored AI search or user-fetch agents for this page path.
- What needs attention: One or more AI discovery, user-fetch, indexability, snippet, synthetic reachability, or sitemap signals need attention.
- Why it matters: AI search systems need crawlable, reachable, indexable, and quotable public content. Training and data-use choices remain neutral publisher preferences.
- Status-specific guidance: The scanner could not verify this from safe public data. Manually verify first; if the site already handles it correctly, report that no code change is needed.
- Audience or recipient: The site owner, builder, or marketing team responsible for improving this public page.
- Constraints, examples, or source material: Treat the live URL as the public target to inspect, not as the only source of truth. When repository, CMS, or hosting access is available, use that implementation context before changing anything.
- Target outcome: After the fix is deployed and the public page is rescanned, this specific check should improve or pass without lowering other SEO / AEO, security, accessibility, or design signals.
## Task
Use the provided context to safely complete this workflow: Use the component scores and exact matched robots rules in the crawler report. Fix blocked search agents, noindex or snippet restrictions, canonical or sitemap gaps, and synthetic WAF/challenge failures. Preserve intentional training opt-outs and keep private, admin, and authenticated paths protected before rescanning.
Before editing, identify the likely source of the issue, the smallest change that can fix it, and any user-visible behavior that must be preserved.
## Output
Return a structured response with headings, prioritized recommendations, changed files or page areas, verification results, rollback notes, and stated assumptions.
## Rules
- Ask a clarifying question when required context is missing.
- Preserve the user's intent and avoid inventing facts.
- Verify the issue exists before changing code or content. If the issue is not reproducible, explain what you checked and recommend no code change.
- If the live URL and implementation source disagree, trust the implementation source for edits and use the live URL only to understand current public behavior.
- Keep the change narrowly scoped to this fix unless another change is required to avoid a regression.
- Match the existing framework, style, design system, routing patterns, and content conventions.
- Preserve existing URLs, forms, analytics, SEO metadata, accessibility semantics, and conversion flows unless the fix explicitly requires changing them.
- Do not perform broad refactors, dependency upgrades, redesigns, rewrites, migrations, file deletions, route changes, or destructive commands unless they are explicitly required and approved.
- Make changes that are easy to review and roll back.
- Verify the result with the smallest reliable test, build, browser check, or manual inspection available.
## Safety
- Do not request, expose, or reproduce sensitive data.
- Redact private details from examples unless the user explicitly says they are safe to include.
- Do not use credentials, cookies, authenticated data, hidden form values, or private response bodies.
- Do not weaken security headers, authentication, authorization, privacy controls, accessibility, or error handling to make the scan pass.

fail

high

Security

Priority 5

Add common public security headers

-14 rule pts

What failed

Several basic browser protection headers were not visible.

Evidence

Detected 1 of 5 common public security headers. Present: strict-transport-security. Missing: content-security-policy, x-content-type-options, x-frame-options, referrer-policy.

Priority

Priority 5: fix before sharing the page publicly.

Why it matters

These headers reduce avoidable browser-side risk and show a baseline of care before launch.

How to fix it

Configure headers such as Strict-Transport-Security, Content-Security-Policy, X-Content-Type-Options, X-Frame-Options, and Referrer-Policy.

Copyable agent prompt

## Role
Act as a focused expert website launch remediation agent for this workflow.
## Inputs
- Primary context: Improve getdocpilot.pro at https://getdocpilot.pro.
- Fix title: Add common public security headers.
- Scanner check: Common security headers.
- Category: Security.
- Status: fail.
- Severity: high.
- Priority: 5; lower numbers are more urgent.
- Score impact: 14 rule points lost.
- Evidence: Detected 1 of 5 common public security headers. Present: strict-transport-security. Missing: content-security-policy, x-content-type-options, x-frame-options, referrer-policy.
- What needs attention: Several basic browser protection headers were not visible.
- Why it matters: These headers reduce avoidable browser-side risk and show a baseline of care before launch.
- Status-specific guidance: A public check reported a failure. Reproduce or inspect the issue first, then make the smallest safe fix.
- Audience or recipient: The site owner, builder, or marketing team responsible for improving this public page.
- Constraints, examples, or source material: Treat the live URL as the public target to inspect, not as the only source of truth. When repository, CMS, or hosting access is available, use that implementation context before changing anything.
- Target outcome: After the fix is deployed and the public page is rescanned, this specific check should improve or pass without lowering other SEO / AEO, security, accessibility, or design signals.
## Task
Use the provided context to safely complete this workflow: Configure headers such as Strict-Transport-Security, Content-Security-Policy, X-Content-Type-Options, X-Frame-Options, and Referrer-Policy.
Before editing, identify the likely source of the issue, the smallest change that can fix it, and any user-visible behavior that must be preserved.
## Output
Return a structured response with headings, prioritized recommendations, changed files or page areas, verification results, rollback notes, and stated assumptions.
## Rules
- Ask a clarifying question when required context is missing.
- Preserve the user's intent and avoid inventing facts.
- Verify the issue exists before changing code or content. If the issue is not reproducible, explain what you checked and recommend no code change.
- If the live URL and implementation source disagree, trust the implementation source for edits and use the live URL only to understand current public behavior.
- Keep the change narrowly scoped to this fix unless another change is required to avoid a regression.
- Match the existing framework, style, design system, routing patterns, and content conventions.
- Preserve existing URLs, forms, analytics, SEO metadata, accessibility semantics, and conversion flows unless the fix explicitly requires changing them.
- Do not perform broad refactors, dependency upgrades, redesigns, rewrites, migrations, file deletions, route changes, or destructive commands unless they are explicitly required and approved.
- Make changes that are easy to review and roll back.
- Verify the result with the smallest reliable test, build, browser check, or manual inspection available.
## Safety
- Do not request, expose, or reproduce sensitive data.
- Redact private details from examples unless the user explicitly says they are safe to include.
- Do not use credentials, cookies, authenticated data, hidden form values, or private response bodies.
- Do not weaken security headers, authentication, authorization, privacy controls, accessibility, or error handling to make the scan pass.

fail

high

Accessibility

Priority 5

Fix rendered axe accessibility violations

-18 rule pts

What failed

The rendered page has accessibility rule violations detected by axe-core.

Evidence

axe found 3 violation rule(s), including 1 serious or critical rule(s). Top rules: color-contrast (2), heading-order (1), meta-viewport (1).

Priority

Priority 5: fix before sharing the page publicly.

Why it matters

axe checks the actual browser-rendered page, so these issues can affect people using keyboards, screen readers, or other assistive technology.

How to fix it

Fix the top axe rule IDs first, especially critical and serious violations around names, roles, labels, headings, contrast, landmarks, and keyboard-accessible controls.

Copyable agent prompt

## Role
Act as a focused expert website launch remediation agent for this workflow.
## Inputs
- Primary context: Improve getdocpilot.pro at https://getdocpilot.pro.
- Fix title: Fix rendered axe accessibility violations.
- Scanner check: Rendered axe accessibility violations.
- Category: Accessibility.
- Status: fail.
- Severity: high.
- Priority: 5; lower numbers are more urgent.
- Score impact: 18 rule points lost.
- Evidence: axe found 3 violation rule(s), including 1 serious or critical rule(s). Top rules: color-contrast (2), heading-order (1), meta-viewport (1).
- What needs attention: The rendered page has accessibility rule violations detected by axe-core.
- Why it matters: axe checks the actual browser-rendered page, so these issues can affect people using keyboards, screen readers, or other assistive technology.
- Status-specific guidance: A public check reported a failure. Reproduce or inspect the issue first, then make the smallest safe fix.
- Audience or recipient: The site owner, builder, or marketing team responsible for improving this public page.
- Constraints, examples, or source material: Treat the live URL as the public target to inspect, not as the only source of truth. When repository, CMS, or hosting access is available, use that implementation context before changing anything.
- Target outcome: After the fix is deployed and the public page is rescanned, this specific check should improve or pass without lowering other SEO / AEO, security, accessibility, or design signals.
## Task
Use the provided context to safely complete this workflow: Fix the top axe rule IDs first, especially critical and serious violations around names, roles, labels, headings, contrast, landmarks, and keyboard-accessible controls.
Before editing, identify the likely source of the issue, the smallest change that can fix it, and any user-visible behavior that must be preserved.
## Output
Return a structured response with headings, prioritized recommendations, changed files or page areas, verification results, rollback notes, and stated assumptions.
## Rules
- Ask a clarifying question when required context is missing.
- Preserve the user's intent and avoid inventing facts.
- Verify the issue exists before changing code or content. If the issue is not reproducible, explain what you checked and recommend no code change.
- If the live URL and implementation source disagree, trust the implementation source for edits and use the live URL only to understand current public behavior.
- Keep the change narrowly scoped to this fix unless another change is required to avoid a regression.
- Match the existing framework, style, design system, routing patterns, and content conventions.
- Preserve existing URLs, forms, analytics, SEO metadata, accessibility semantics, and conversion flows unless the fix explicitly requires changing them.
- Do not perform broad refactors, dependency upgrades, redesigns, rewrites, migrations, file deletions, route changes, or destructive commands unless they are explicitly required and approved.
- Make changes that are easy to review and roll back.
- Verify the result with the smallest reliable test, build, browser check, or manual inspection available.
## Safety
- Do not request, expose, or reproduce sensitive data.
- Redact private details from examples unless the user explicitly says they are safe to include.
- Do not use credentials, cookies, authenticated data, hidden form values, or private response bodies.
- Do not weaken security headers, authentication, authorization, privacy controls, accessibility, or error handling to make the scan pass.

fail

high

Design

Priority 4

Make the primary CTA obvious

-14 rule pts

What failed

The page does not have a detectable call to action.

Evidence

Detected 0 CTA candidate(s).

Priority

Priority 4: fix before sharing the page publicly.

Why it matters

Early visitors need a clear next step, such as trying the product, joining a waitlist, or booking a demo.

How to fix it

Add one prominent CTA above the fold with action-oriented text such as Start, Join, Try, Book, or Get started.

Copyable agent prompt

## Role
Act as a focused expert website launch remediation agent for this workflow.
## Inputs
- Primary context: Improve getdocpilot.pro at https://getdocpilot.pro.
- Fix title: Make the primary CTA obvious.
- Scanner check: Visible primary CTA.
- Category: Design.
- Status: fail.
- Severity: high.
- Priority: 4; lower numbers are more urgent.
- Score impact: 14 rule points lost.
- Evidence: Detected 0 CTA candidate(s).
- What needs attention: The page does not have a detectable call to action.
- Why it matters: Early visitors need a clear next step, such as trying the product, joining a waitlist, or booking a demo.
- Status-specific guidance: A public check reported a failure. Reproduce or inspect the issue first, then make the smallest safe fix.
- Audience or recipient: The site owner, builder, or marketing team responsible for improving this public page.
- Constraints, examples, or source material: Treat the live URL as the public target to inspect, not as the only source of truth. When repository, CMS, or hosting access is available, use that implementation context before changing anything.
- Target outcome: After the fix is deployed and the public page is rescanned, this specific check should improve or pass without lowering other SEO / AEO, security, accessibility, or design signals.
## Task
Use the provided context to safely complete this workflow: Add one prominent CTA above the fold with action-oriented text such as Start, Join, Try, Book, or Get started.
Before editing, identify the likely source of the issue, the smallest change that can fix it, and any user-visible behavior that must be preserved.
## Output
Return a structured response with headings, prioritized recommendations, changed files or page areas, verification results, rollback notes, and stated assumptions.
## Rules
- Ask a clarifying question when required context is missing.
- Preserve the user's intent and avoid inventing facts.
- Verify the issue exists before changing code or content. If the issue is not reproducible, explain what you checked and recommend no code change.
- If the live URL and implementation source disagree, trust the implementation source for edits and use the live URL only to understand current public behavior.
- Keep the change narrowly scoped to this fix unless another change is required to avoid a regression.
- Match the existing framework, style, design system, routing patterns, and content conventions.
- Preserve existing URLs, forms, analytics, SEO metadata, accessibility semantics, and conversion flows unless the fix explicitly requires changing them.
- Do not perform broad refactors, dependency upgrades, redesigns, rewrites, migrations, file deletions, route changes, or destructive commands unless they are explicitly required and approved.
- Make changes that are easy to review and roll back.
- Verify the result with the smallest reliable test, build, browser check, or manual inspection available.
## Safety
- Do not request, expose, or reproduce sensitive data.
- Redact private details from examples unless the user explicitly says they are safe to include.
- Do not use credentials, cookies, authenticated data, hidden form values, or private response bodies.
- Do not weaken security headers, authentication, authorization, privacy controls, accessibility, or error handling to make the scan pass.

Score aggregation details

Category scores come from earned rule points divided by available rule points. Failed checks are ordered by severity and score lost.

50/100

6 pass, 5 fail, 1 unknown

-10 rule pts

Detected 0 JSON-LD schema block(s).

61/100

4 pass, 2 fail, 0 unknown

Security

Severity mix: 2 critical, 3 high, 0 medium, 0 low.

critical

Sensitive file probes

-16 rule pts

A small allowlist probe returned a public success response.

high

Common security headers

-14 rule pts

Detected 1 of 5 common public security headers. Present: strict-transport-security. Missing: content-security-policy, x-content-type-options, x-frame-options, referrer-policy.

50/100

4 pass, 4 fail, 0 unknown

Accessibility

Severity mix: 0 critical, 3 high, 5 medium, 0 low.

high

Rendered axe accessibility violations

-18 rule pts

axe found 3 violation rule(s), including 1 serious or critical rule(s). Top rules: color-contrast (2), heading-order (1), meta-viewport (1).

medium

Heading order

-11 rule pts

Heading levels found: none.

medium

Landmark presence

-10 rule pts

Detected 0 landmark element(s) or roles.

28/100

3 pass, 8 fail, 0 unknown

Design

Severity mix: 0 critical, 3 high, 6 medium, 2 low.

high

Visible primary CTA

-14 rule pts

Detected 0 CTA candidate(s).

high

Hero clarity signals

-13 rule pts

Detected 0 H1 heading(s) and 106 meta-description characters.

medium

Text density

Horizontal overflow: 0px. Small tap targets: 32.

Failed: earned 0 of 9 points.

Priority: Priority 13: fix during launch polish.

Why it matters: Horizontal overflow and tiny tap targets make the page feel broken on real devices, especially for mobile visitors.

Fix: Remove elements wider than the viewport, add responsive constraints, and make important links, buttons, inputs, and controls at least 40px tall and wide where possible.

Copyable agent prompt

## Role
Act as a focused expert website launch remediation agent for this workflow.
## Inputs
- Primary context: Improve getdocpilot.pro at https://getdocpilot.pro.
- Fix title: Fix rendered layout ergonomics.
- Scanner check: Rendered layout ergonomics.
- Category: Design.
- Status: fail.
- Severity: medium.
- Priority: 13; lower numbers are more urgent.
- Score impact: 9 of 9 rule points lost.
- Evidence: Horizontal overflow: 0px. Small tap targets: 32.
- What needs attention: The browser-rendered page has layout or tap-target issues.
- Why it matters: Horizontal overflow and tiny tap targets make the page feel broken on real devices, especially for mobile visitors.
- Status-specific guidance: A public check reported a failure. Reproduce or inspect the issue first, then make the smallest safe fix.
- Audience or recipient: The site owner, builder, or marketing team responsible for improving this public page.
- Constraints, examples, or source material: Treat the live URL as the public target to inspect, not as the only source of truth. When repository, CMS, or hosting access is available, use that implementation context before changing anything.
- Target outcome: After the fix is deployed and the public page is rescanned, this specific check should improve or pass without lowering other SEO / AEO, security, accessibility, or design signals.
## Task
Use the provided context to safely complete this workflow: Remove elements wider than the viewport, add responsive constraints, and make important links, buttons, inputs, and controls at least 40px tall and wide where possible.
Before editing, identify the likely source of the issue, the smallest change that can fix it, and any user-visible behavior that must be preserved.
## Output
Return a structured response with headings, prioritized recommendations, changed files or page areas, verification results, rollback notes, and stated assumptions.
## Rules
- Ask a clarifying question when required context is missing.
- Preserve the user's intent and avoid inventing facts.
- Verify the issue exists before changing code or content. If the issue is not reproducible, explain what you checked and recommend no code change.
- If the live URL and implementation source disagree, trust the implementation source for edits and use the live URL only to understand current public behavior.
- Keep the change narrowly scoped to this fix unless another change is required to avoid a regression.
- Match the existing framework, style, design system, routing patterns, and content conventions.
- Preserve existing URLs, forms, analytics, SEO metadata, accessibility semantics, and conversion flows unless the fix explicitly requires changing them.
- Do not perform broad refactors, dependency upgrades, redesigns, rewrites, migrations, file deletions, route changes, or destructive commands unless they are explicitly required and approved.
- Make changes that are easy to review and roll back.
- Verify the result with the smallest reliable test, build, browser check, or manual inspection available.
## Safety
- Do not request, expose, or reproduce sensitive data.
- Redact private details from examples unless the user explicitly says they are safe to include.
- Do not use credentials, cookies, authenticated data, hidden form values, or private response bodies.
- Do not weaken security headers, authentication, authorization, privacy controls, accessibility, or error handling to make the scan pass.

Page-level AEO readiness

Shared eligibility and content signals that affect every search and answer agent.

60/100 ready

Index and citation eligibility

No general noindex directive was detected.

Snippet and answer controls

No general nosnippet or max-snippet:0 control was detected.

Canonical alignment

No canonical URL was detected.

Sitemap coverage and freshness

The exact URL appears in sitemap.xml.

Structured data

Detected 0 JSON-LD block(s), 0 parse error(s), and types none.

Public or paywalled content

No isAccessibleForFree structured-data value was detected.

Entity clarity

Detected 2 of 3 core identity signals across the title, description, and H1.

Answer-ready visible text

Detected 4 visible words and 0 audience, use-case, pricing, or integration signals.

Authorship and accountability

No author meta value or structured-data author was detected.

Published or updated date

No datePublished or dateModified value was detected in structured data.

Supporting-source links

No external supporting links were detected; this is contextual rather than a universal requirement.

Rendered content availability

Rendered audit completed with 217 visible text element(s).

Synthetic search-agent reachability

8 of 8 search/discovery User-Agent probes returned reachable content.

Optional LLM-readable summary

https://getdocpilot.pro/llms.txt returned HTTP 200; this is supplemental and does not determine AI-search eligibility.

OpenAIChatGPT search

OAI-SearchBot

PASS · ALLOWED

AI search

Robots: allowed by * allow: / · line 2

Probe: reachable · HTTP 200 · 100% parity

IndexSnippetsSitemapPublic content

Vendor documentationDefinition checked 2026-07-30

OpenAIOpenAI model training

GPTBot

POLICY ALLOWED

Model training

Robots: allowed by * allow: / · line 2

Probe: not tested for this control

IndexSnippetsSitemapPublic content

Vendor documentationDefinition checked 2026-07-30

OpenAIChatGPT user fetches

ChatGPT-User

UNKNOWN

User-requested fetch

Robots: not applicable to user-requested fetches

Probe: not tested for this control

IndexSnippetsSitemapPublic content

Vendor documentationDefinition checked 2026-07-30

AnthropicClaude model training

ClaudeBot

POLICY ALLOWED

Model training

Robots: allowed by * allow: / · line 2

Probe: not tested for this control

IndexSnippetsSitemapPublic content

Vendor documentationDefinition checked 2026-07-30

AnthropicClaude search

Claude-SearchBot

PASS · ALLOWED

AI search

Robots: allowed by * allow: / · line 2

Probe: reachable · HTTP 200 · 100% parity

IndexSnippetsSitemapPublic content

Vendor documentationDefinition checked 2026-07-30

AnthropicClaude user fetches

Claude-User

PASS · ALLOWED

User-requested fetch

Robots: allowed by * allow: / · line 2

Probe: reachable · HTTP 200 · 100% parity

IndexSnippetsSitemapPublic content

Vendor documentationDefinition checked 2026-07-30

GoogleGoogle Search and AI features

Googlebot

PASS · ALLOWED

Search and discovery

Robots: allowed by * allow: / · line 2

Probe: reachable · HTTP 200 · 100% parity

IndexSnippetsSitemapPublic content

Vendor documentationDefinition checked 2026-07-30

GoogleGemini data use and grounding

Google-Extended

POLICY ALLOWED

Data-use policy control

Robots: allowed by * allow: / · line 2

Probe: not tested for this control

IndexSnippetsSitemapPublic content

Vendor documentationDefinition checked 2026-07-30

MicrosoftBing and Copilot

Bingbot

PASS · ALLOWED

Search and discovery

Robots: allowed by * allow: / · line 2

Probe: reachable · HTTP 200 · 100% parity

IndexSnippetsSitemapPublic content

Vendor documentationDefinition checked 2026-07-30

PerplexityPerplexity search

PerplexityBot

PASS · ALLOWED

AI search

Robots: allowed by * allow: / · line 2

Probe: reachable · HTTP 200 · 100% parity

IndexSnippetsSitemapPublic content

Vendor documentationDefinition checked 2026-07-30

PerplexityPerplexity user fetches

Perplexity-User

UNKNOWN

User-requested fetch

Robots: not applicable to user-requested fetches

Probe: not tested for this control

IndexSnippetsSitemapPublic content

Vendor documentationDefinition checked 2026-07-30

AppleSiri, Spotlight, and Safari search

Applebot

PASS · ALLOWED

Search and discovery

Robots: allowed by * allow: / · line 2

Probe: reachable · HTTP 200 · 100% parity

IndexSnippetsSitemapPublic content

Vendor documentationDefinition checked 2026-07-30

AppleApple foundation-model training

Applebot-Extended

POLICY ALLOWED

Data-use policy control

Robots: allowed by * allow: / · line 2

Probe: not tested for this control

IndexSnippetsSitemapPublic content

Vendor documentationDefinition checked 2026-07-30

Mistral AIMistral search

MistralAI-Index

PASS · ALLOWED

AI search

Robots: allowed by * allow: / · line 2

Probe: reachable · HTTP 200 · 100% parity

IndexSnippetsSitemapPublic content

Vendor documentationDefinition checked 2026-07-30

Mistral AIMistral user fetches

MistralAI-User

PASS · ALLOWED

User-requested fetch

Robots: allowed by * allow: / · line 2

Probe: reachable · HTTP 200 · 100% parity

IndexSnippetsSitemapPublic content

Vendor documentationDefinition checked 2026-07-30

MetaMeta AI model and product data

meta-externalagent

POLICY ALLOWED

Model training

Robots: allowed by * allow: / · line 2

Probe: not tested for this control

IndexSnippetsSitemapPublic content

Vendor documentationDefinition checked 2026-07-30

MetaMeta AI user fetches

meta-externalfetcher

PASS · ALLOWED

User-requested fetch

Robots: allowed by * allow: / · line 2

Probe: reachable · HTTP 200 · 100% parity

IndexSnippetsSitemapPublic content

Vendor documentationDefinition checked 2026-07-30

AmazonAmazon model training

Amazonbot

POLICY ALLOWED

Model training

Robots: allowed by * allow: / · line 2

Probe: not tested for this control

IndexSnippetsSitemapPublic content

Vendor documentationDefinition checked 2026-07-30

AmazonAlexa and Rufus search

Amzn-SearchBot

PASS · ALLOWED

AI search

Robots: allowed by * allow: / · line 2

Probe: reachable · HTTP 200 · 100% parity

IndexSnippetsSitemapPublic content

Vendor documentationDefinition checked 2026-07-30

AmazonAlexa user fetches

Amzn-User

PASS · ALLOWED

User-requested fetch

Robots: allowed by * allow: / · line 2

Probe: reachable · HTTP 200 · 100% parity

IndexSnippetsSitemapPublic content

Vendor documentationDefinition checked 2026-07-30

Common CrawlOpen web datasets

CCBot

POLICY ALLOWED

Model training

Robots: allowed by * allow: / · line 2

Probe: not tested for this control

IndexSnippetsSitemapPublic content

Vendor documentationDefinition checked 2026-07-30

Ready combines robots policy, a bounded synthetic User-Agent fetch, indexability, and snippet eligibility. Synthetic probes do not prove vendor-origin traffic. Purple preference states are training or data-use choices and do not lower the AEO score.

Public report link

Markdown export

Share the website audit report

Copy a public report link or a Markdown version with scores, fixes, opportunities, insights, and a normal link back to the scanned site.

Share preview

getdocpilot.pro website audit report

Needs fixes before launch: 47/100 overall, with prioritized fixes for SEO, security, accessibility, and design.

Public report link

Markdown report

# getdocpilot.pro Website Scan

Scanned URL: [https://getdocpilot.pro](https://getdocpilot.pro)
Report URL: /scan/getdocpilot-pro-47-launch-readiness-report-d545a2b2
Created: 2026-07-31T21:03:35.782Z

## Score Summary

- Overall: 47/100
- SEO / AEO: 50/100
- Security: 61/100
- Accessibility: 50/100
- Design: 28/100

## Launch Readiness

Needs fixes before launch (High risk).

Passed: 17. Failed: 19. Unknown: 1.
Strongest area: Security. Weakest area: Design.

## AI Crawler Access

These results combine robots.txt policy, page controls, and bounded synthetic User-Agent probes. Synthetic probes do not prove that traffic came from the vendor; training and data-use choices are neutral publisher preferences.

- **OpenAI — ChatGPT search** (OAI-SearchBot): PASS — robots allowed; synthetic probe reachable (HTTP 200). Allowed by * allow: / on line 2. Synthetic User-Agent probe returned HTTP 200 with 100% sampled-content parity.
- **OpenAI — OpenAI model training** (GPTBot): PREFERENCE — robots allowed; synthetic probe not_tested. Allowed by * allow: / on line 2. No synthetic fetch is appropriate for this policy or training control.
- **OpenAI — ChatGPT user fetches** (ChatGPT-User): UNKNOWN — robots not_applicable; synthetic probe not_tested. ChatGPT-User is used for user-requested retrieval, so robots.txt is not treated as a reliable access control for this row. No synthetic fetch is appropriate for this policy or training control.
- **Anthropic — Claude model training** (ClaudeBot): PREFERENCE — robots allowed; synthetic probe not_tested. Allowed by * allow: / on line 2. No synthetic fetch is appropriate for this policy or training control.
- **Anthropic — Claude search** (Claude-SearchBot): PASS — robots allowed; synthetic probe reachable (HTTP 200). Allowed by * allow: / on line 2. Synthetic User-Agent probe returned HTTP 200 with 100% sampled-content parity.
- **Anthropic — Claude user fetches** (Claude-User): PASS — robots allowed; synthetic probe reachable (HTTP 200). Allowed by * allow: / on line 2. Synthetic User-Agent probe returned HTTP 200 with 100% sampled-content parity.
- **Google — Google Search and AI features** (Googlebot): PASS — robots allowed; synthetic probe reachable (HTTP 200). Allowed by * allow: / on line 2. Synthetic User-Agent probe returned HTTP 200 with 100% sampled-content parity.
- **Google — Gemini data use and grounding** (Google-Extended): PREFERENCE — robots allowed; synthetic probe not_tested. Allowed by * allow: / on line 2. No synthetic fetch is appropriate for this policy or training control.
- **Microsoft — Bing and Copilot** (Bingbot): PASS — robots allowed; synthetic probe reachable (HTTP 200). Allowed by * allow: / on line 2. Synthetic User-Agent probe returned HTTP 200 with 100% sampled-content parity.
- **Perplexity — Perplexity search** (PerplexityBot): PASS — robots allowed; synthetic probe reachable (HTTP 200). Allowed by * allow: / on line 2. Synthetic User-Agent probe returned HTTP 200 with 100% sampled-content parity.
- **Perplexity — Perplexity user fetches** (Perplexity-User): UNKNOWN — robots not_applicable; synthetic probe not_tested. Perplexity-User is used for user-requested retrieval, so robots.txt is not treated as a reliable access control for this row. No synthetic fetch is appropriate for this policy or training control.
- **Apple — Siri, Spotlight, and Safari search** (Applebot): PASS — robots allowed; synthetic probe reachable (HTTP 200). Allowed by * allow: / on line 2. Synthetic User-Agent probe returned HTTP 200 with 100% sampled-content parity.
- **Apple — Apple foundation-model training** (Applebot-Extended): PREFERENCE — robots allowed; synthetic probe not_tested. Allowed by * allow: / on line 2. No synthetic fetch is appropriate for this policy or training control.
- **Mistral AI — Mistral search** (MistralAI-Index): PASS — robots allowed; synthetic probe reachable (HTTP 200). Allowed by * allow: / on line 2. Synthetic User-Agent probe returned HTTP 200 with 100% sampled-content parity.
- **Mistral AI — Mistral user fetches** (MistralAI-User): PASS — robots allowed; synthetic probe reachable (HTTP 200). Allowed by * allow: / on line 2. Synthetic User-Agent probe returned HTTP 200 with 100% sampled-content parity.
- **Meta — Meta AI model and product data** (meta-externalagent): PREFERENCE — robots allowed; synthetic probe not_tested. Allowed by * allow: / on line 2. No synthetic fetch is appropriate for this policy or training control.
- **Meta — Meta AI user fetches** (meta-externalfetcher): PASS — robots allowed; synthetic probe reachable (HTTP 200). Allowed by * allow: / on line 2. Synthetic User-Agent probe returned HTTP 200 with 100% sampled-content parity.
- **Amazon — Amazon model training** (Amazonbot): PREFERENCE — robots allowed; synthetic probe not_tested. Allowed by * allow: / on line 2. No synthetic fetch is appropriate for this policy or training control.
- **Amazon — Alexa and Rufus search** (Amzn-SearchBot): PASS — robots allowed; synthetic probe reachable (HTTP 200). Allowed by * allow: / on line 2. Synthetic User-Agent probe returned HTTP 200 with 100% sampled-content parity.
- **Amazon — Alexa user fetches** (Amzn-User): PASS — robots allowed; synthetic probe reachable (HTTP 200). Allowed by * allow: / on line 2. Synthetic User-Agent probe returned HTTP 200 with 100% sampled-content parity.
- **Common Crawl — Open web datasets** (CCBot): PREFERENCE — robots allowed; synthetic probe not_tested. Allowed by * allow: / on line 2. No synthetic fetch is appropriate for this policy or training control.

## Page-level AEO Readiness

Readiness: 60/100

- **Index and citation eligibility**: PASS — No general noindex directive was detected.
- **Snippet and answer controls**: PASS — No general nosnippet or max-snippet:0 control was detected.
- **Canonical alignment**: FAIL — No canonical URL was detected.
- **Sitemap coverage and freshness**: PASS — The exact URL appears in sitemap.xml.
- **Structured data**: UNKNOWN — Detected 0 JSON-LD block(s), 0 parse error(s), and types none.
- **Public or paywalled content**: UNKNOWN — No isAccessibleForFree structured-data value was detected.
- **Entity clarity**: UNKNOWN — Detected 2 of 3 core identity signals across the title, description, and H1.
- **Answer-ready visible text**: FAIL — Detected 4 visible words and 0 audience, use-case, pricing, or integration signals.
- **Authorship and accountability**: UNKNOWN — No author meta value or structured-data author was detected.
- **Published or updated date**: UNKNOWN — No datePublished or dateModified value was detected in structured data.
- **Supporting-source links**: UNKNOWN — No external supporting links were detected; this is contextual rather than a universal requirement.
- **Rendered content availability**: PASS — Rendered audit completed with 217 visible text element(s).
- **Synthetic search-agent reachability**: PASS — 8 of 8 search/discovery User-Agent probes returned reachable content.
- **Optional LLM-readable summary**: INFO — https://getdocpilot.pro/llms.txt returned HTTP 200; this is supplemental and does not determine AI-search eligibility.

## Prioritized Fixes

### 1. Remove exposed sensitive files

- Category: Security
- Status: fail
- Severity: critical
- Rule points lost: 16
- Evidence: A small allowlist probe returned a public success response.
- Why it matters: Publicly exposed config or backup files can leak implementation details or secrets.
- Fix: Remove the exposed file, block public access to that path, and rotate any secrets that may have been exposed.

### 2. Improve AI search and crawler readiness

- Category: SEO / AEO
- Status: unknown
- Severity: critical
- Rule points lost: 8
- Evidence: FreeScan.app reached the public page with HTTP 200. AEO crawler readiness is 92%: discovery 45/45, index and snippet eligibility 20/25, synthetic reachability 20/20, sitemap freshness 7/10. robots.txt did not block the scored AI search or user-fetch agents for this page path.
- Why it matters: AI search systems need crawlable, reachable, indexable, and quotable public content. Training and data-use choices remain neutral publisher preferences.
- Fix: Use the component scores and exact matched robots rules in the crawler report. Fix blocked search agents, noindex or snippet restrictions, canonical or sitemap gaps, and synthetic WAF/challenge failures. Preserve intentional training opt-outs and keep private, admin, and authenticated paths protected before rescanning.

### 3. Add common public security headers

- Category: Security
- Status: fail
- Severity: high
- Rule points lost: 14
- Evidence: Detected 1 of 5 common public security headers. Present: strict-transport-security. Missing: content-security-policy, x-content-type-options, x-frame-options, referrer-policy.
- Why it matters: These headers reduce avoidable browser-side risk and show a baseline of care before launch.
- Fix: Configure headers such as Strict-Transport-Security, Content-Security-Policy, X-Content-Type-Options, X-Frame-Options, and Referrer-Policy.

### 4. Fix rendered axe accessibility violations

- Category: Accessibility
- Status: fail
- Severity: high
- Rule points lost: 18
- Evidence: axe found 3 violation rule(s), including 1 serious or critical rule(s). Top rules: color-contrast (2), heading-order (1), meta-viewport (1).
- Why it matters: axe checks the actual browser-rendered page, so these issues can affect people using keyboards, screen readers, or other assistive technology.
- Fix: Fix the top axe rule IDs first, especially critical and serious violations around names, roles, labels, headings, contrast, landmarks, and keyboard-accessible controls.

### 5. Make the primary CTA obvious

- Category: Design
- Status: fail
- Severity: high
- Rule points lost: 14
- Evidence: Detected 0 CTA candidate(s).
- Why it matters: Early visitors need a clear next step, such as trying the product, joining a waitlist, or booking a demo.
- Fix: Add one prominent CTA above the fold with action-oriented text such as Start, Join, Try, Book, or Get started.

## Opportunities

### Add answer-ready sections for common buyer questions

- Impact: high
- Category: SEO / AEO
- Evidence: Pricing signals: 0. Use-case signals: 0. Integration/API signals: 0.
- Why it matters: Answer engines and search visitors need concise textual answers to summarize who the product is for, how it works, what it costs, and what it connects with.
- Next step: Add short, crawlable sections for pricing or plans, ideal users, use cases, integrations, security, and how the product differs from alternatives.

### Expose important supporting pages in navigation or footer

- Impact: medium
- Category: SEO / AEO
- Evidence: No pricing, docs, contact, security, privacy, terms, or about links were detected in public internal links.
- Why it matters: Internal links help visitors, crawlers, and AI answer systems discover supporting facts instead of relying on one landing page.
- Next step: Link to the most useful public pages, especially pricing, docs, contact, security, privacy, terms, and about pages where applicable.

### Make trust and proof easier to detect

- Impact: medium
- Category: Design
- Evidence: Detected 0 trust-signal keyword occurrence(s).
- Why it matters: Visitors who arrive cold from search, social, or AI citations need proof before they submit a form, start a trial, or buy.
- Next step: Add honest proof such as customer quotes, recognizable logos, security notes, usage stats, reviews, case studies, or founder credibility.

### Review snippet and preview controls

- Impact: low
- Category: SEO / AEO
- Evidence: Open Graph image was detected. Preview controls detected: 0.
- Why it matters: Preview controls can clarify how much text, image, and video content search systems may show from the page.
- Next step: Only add robots preview controls when you intentionally want to limit snippets or image/video previews; otherwise leave previews open.

### Tighten the live color system

- Impact: high
- Category: Accessibility
- Evidence: 16 of 100 rendered contrast sample(s) missed target. Worst ratio: 1.
- Why it matters: Computed contrast catches the actual colors visitors see after CSS, themes, and overlays are applied.
- Next step: Audit foreground/background token pairs for body text, muted text, links, buttons, inputs, and badges, then raise weak pairs to WCAG AA contrast targets.

### Polish rendered responsive ergonomics

- Impact: medium
- Category: Design
- Evidence: Horizontal overflow: 0px. Small tap targets: 32.
- Why it matters: Overflow and tiny controls are easy for static scans to miss but obvious to real users, especially on mobile and tablet layouts.
- Next step: Constrain wide elements, avoid fixed-width content that exceeds the viewport, and increase touch target sizes for interactive controls.

### Measure search performance with first-party data

- Impact: medium
- Category: SEO / AEO
- Evidence: robots.txt and sitemap.xml were reachable, so the site has the basics needed for Search Console verification and monitoring.
- Why it matters: A scan can identify technical readiness, but Search Console and analytics reveal impressions, queries, clicks, pages, and conversions over time.
- Next step: Verify the domain in Search Console, submit the sitemap, and pair query/page data with analytics events for signups, demo requests, and purchases.

## Insights

### The page appears basically crawlable

- Category: SEO / AEO
- Evidence: HTTP 200. robots.txt: HTTP 200. sitemap.xml: HTTP 200. noindex check: clear.
- Interpretation: The public page satisfies the basic crawl/index path the scan can verify.
- Recommended use: Use this as the first launch gate before deeper content, ranking, or AI visibility work.

### AEO depends on normal SEO plus answerable text

- Category: SEO / AEO
- Evidence: Visible words: 4. H1 count: 0. Audience signals: 0. CTA labels: none detected.
- Interpretation: Google AI features currently rely on standard Search eligibility; the extra advantage comes from content that is easy to quote, summarize, and verify.
- Recommended use: Prioritize clear text answers, crawlable support pages, accurate schema, and visible proof over speculative AI-only markup.

### Detected entity signals

- Category: SEO / AEO
- Evidence: Title: DocPilot. H1: missing. Schema types: none.
- Interpretation: The stronger and more consistent these entity signals are, the easier it is for search and answer systems to identify the brand, product category, and page purpose.
- Recommended use: Keep the title, H1, meta description, Open Graph, schema, footer, and about/pricing/docs pages aligned around the same product facts.

### No structured data detected

- Category: SEO / AEO
- Evidence: JSON-LD blocks: 0. Types: none. Parse errors: 0.
- Interpretation: Missing or invalid structured data makes the page rely more heavily on inferred meaning from text and layout.
- Recommended use: Validate JSON-LD and use only accurate facts that are visible or clearly supported on the public page.

### Weakest score area

- Category: Design
- Evidence: SEO / AEO: 50/100. Security: 61/100. Accessibility: 50/100. Design: 28/100
- Interpretation: The weakest area is Design, so improvements there should have the most visible effect on readiness.
- Recommended use: Use the score mix to choose the next workstream instead of treating every issue as equally urgent.

### LLM-readable file found

- Category: SEO / AEO
- Evidence: https://getdocpilot.pro/llms.txt returned HTTP 200.
- Interpretation: llms.txt can be a useful optional summary for agents, but it should not be treated as a guaranteed AI search ranking factor.
- Recommended use: Invest first in crawlability, helpful visible content, internal links, and accurate schema; add llms.txt as a tidy supplement.

### Rendered page experience snapshot

- Category: Design
- Evidence: Rendered text samples: 100. Contrast failures: 16. Console errors: 1. Horizontal overflow: 0px.
- Interpretation: The scan inspected the browser-rendered page, so contrast, runtime, layout, and timing signals are more representative than static markup alone.
- Recommended use: Use rendered checks to prioritize issues that visitors actually experience after JavaScript and CSS load.

### Rendered speed snapshot

- Category: Design
- Evidence: DOMContentLoaded: 666ms. Load complete: 681ms. First contentful paint: 224ms. Resources: 8. Scripts: 3. Images: 2. Third-party origins: 5. Transfer: not available.
- Interpretation: These are lightweight browser timings from one rendered scan, so they are useful directional signals rather than real-user performance proof.
- Recommended use: Use slow timings, high script counts, heavy transfer size, and many third-party origins to choose focused speed work, then verify important changes with analytics or field data when available.

### Rendered axe accessibility snapshot

- Category: Accessibility
- Evidence: axe violations: 3. Critical: 0. Serious: 1. Top rules: color-contrast, heading-order, meta-viewport.
- Interpretation: axe-core catches common accessibility failures in the actual rendered DOM, but it is still automated coverage and not a full manual accessibility audit.
- Recommended use: Treat critical and serious axe failures as high-priority fixes, then manually review keyboard flow, focus states, screen reader meaning, and interaction states.

## Scope

FreeScan.app performs safe public checks only. It is not a penetration test, full SEO engagement, full accessibility audit, WCAG certification, backlink audit, rank tracker, or analytics platform.

Public reports expose the scanned public URL, safe scores, sanitized public evidence, and fix guidance. They do not include credentials, cookies, hidden form values, or sensitive response bodies.

Rescan same URL

Rerun the full deterministic scanner for getdocpilot.pro without re-entering the URL. The previous report stays saved so the next result can be compared against it.

Start free audit

New scan Visit scanned site

completed

HTTP 200

0 redirects

37 checks

Website audit scorecard for getdocpilot.pro

The scanner fetched the public page, extracted deterministic facts, and stored scored results across SEO / AEO, security, accessibility, and design.

Submitted

https://getdocpilot.pro/

Final URL

https://getdocpilot.pro

Created

Jul 31, 2026, 9:03 PM

Safe fetch

79 ms

Four-score result

Needs fixes before launch (High risk): 17 passed, 19 failed, and 1 unknown. Strongest area: Security. Weakest area: Design.

Overall

out of 100

SEO / AEO

out of 100

51/103 rule points

Security

out of 100

46/76 rule points

Accessibility

out of 100

47/94 rule points

Design

out of 100

31/110 rule points

Why this scored this way

Scores are deterministic: each category earns rule points for verified public signals and loses points for failed checks. Unknown checks are shown separately instead of guessed.

Category point breakdown

SEO / AEO51/103

Security46/76

Accessibility47/94

Design31/110

Biggest score-losing checks

high

Accessibility

Rendered axe accessibility violations

axe found 3 violation rule(s), including 1 serious or critical rule(s). Top rules: color-contrast (2), heading-order (1), meta-viewport (1).

critical

Security

Sensitive file probes

A small allowlist probe returned a public success response.

high

Security

Common security headers

Detected 1 of 5 common public security headers. Present: strict-transport-security. Missing: content-security-policy, x-content-type-options, x-frame-options, referrer-policy.

high

Design

Visible primary CTA

Detected 0 CTA candidate(s).

Recommendations

Score-losing issues ordered by remediation priority, severity, and score impact.

5 fixes

7 opportunities

9 insights

fail

critical

Security

Priority 1

Remove exposed sensitive files

-16 rule pts

What failed

A small public allowlist probe found a sensitive-looking file path.

Evidence

A small allowlist probe returned a public success response.

Priority

Priority 1: fix before sharing the page publicly.

Why it matters

Publicly exposed config or backup files can leak implementation details or secrets.

How to fix it

Remove the exposed file, block public access to that path, and rotate any secrets that may have been exposed.

Copyable agent prompt

## Role
Act as a focused expert website launch remediation agent for this workflow.
## Inputs
- Primary context: Improve getdocpilot.pro at https://getdocpilot.pro.
- Fix title: Remove exposed sensitive files.
- Scanner check: Sensitive file probes.
- Category: Security.
- Status: fail.
- Severity: critical.
- Priority: 1; lower numbers are more urgent.
- Score impact: 16 rule points lost.
- Evidence: A small allowlist probe returned a public success response.
- What needs attention: A small public allowlist probe found a sensitive-looking file path.
- Why it matters: Publicly exposed config or backup files can leak implementation details or secrets.
- Status-specific guidance: A public check reported a failure. Reproduce or inspect the issue first, then make the smallest safe fix.
- Audience or recipient: The site owner, builder, or marketing team responsible for improving this public page.
- Constraints, examples, or source material: Treat the live URL as the public target to inspect, not as the only source of truth. When repository, CMS, or hosting access is available, use that implementation context before changing anything.
- Target outcome: After the fix is deployed and the public page is rescanned, this specific check should improve or pass without lowering other SEO / AEO, security, accessibility, or design signals.
## Task
Use the provided context to safely complete this workflow: Remove the exposed file, block public access to that path, and rotate any secrets that may have been exposed.
Before editing, identify the likely source of the issue, the smallest change that can fix it, and any user-visible behavior that must be preserved.
## Output
Return a structured response with headings, prioritized recommendations, changed files or page areas, verification results, rollback notes, and stated assumptions.
## Rules
- Ask a clarifying question when required context is missing.
- Preserve the user's intent and avoid inventing facts.
- Verify the issue exists before changing code or content. If the issue is not reproducible, explain what you checked and recommend no code change.
- If the live URL and implementation source disagree, trust the implementation source for edits and use the live URL only to understand current public behavior.
- Keep the change narrowly scoped to this fix unless another change is required to avoid a regression.
- Match the existing framework, style, design system, routing patterns, and content conventions.
- Preserve existing URLs, forms, analytics, SEO metadata, accessibility semantics, and conversion flows unless the fix explicitly requires changing them.
- Do not perform broad refactors, dependency upgrades, redesigns, rewrites, migrations, file deletions, route changes, or destructive commands unless they are explicitly required and approved.
- Make changes that are easy to review and roll back.
- Verify the result with the smallest reliable test, build, browser check, or manual inspection available.
## Safety
- Do not request, expose, or reproduce sensitive data.
- Redact private details from examples unless the user explicitly says they are safe to include.
- Do not use credentials, cookies, authenticated data, hidden form values, or private response bodies.
- Do not weaken security headers, authentication, authorization, privacy controls, accessibility, or error handling to make the scan pass.

unknown

critical

SEO / AEO

Priority 2

Improve AI search and crawler readiness

-8 rule pts

What needs verification

One or more AI discovery, user-fetch, indexability, snippet, synthetic reachability, or sitemap signals need attention.

Evidence

Priority

Priority 2: fix before sharing the page publicly.

Why it matters

AI search systems need crawlable, reachable, indexable, and quotable public content. Training and data-use choices remain neutral publisher preferences.

How to fix it

Copyable agent prompt

## Role
Act as a focused expert website launch remediation agent for this workflow.
## Inputs
- Primary context: Improve getdocpilot.pro at https://getdocpilot.pro.
- Fix title: Improve AI search and crawler readiness.
- Scanner check: Crawler access.
- Category: SEO / AEO.
- Status: unknown.
- Severity: critical.
- Priority: 2; lower numbers are more urgent.
- Score impact: 8 rule points lost.
- Evidence: FreeScan.app reached the public page with HTTP 200. AEO crawler readiness is 92%: discovery 45/45, index and snippet eligibility 20/25, synthetic reachability 20/20, sitemap freshness 7/10. robots.txt did not block the scored AI search or user-fetch agents for this page path.
- What needs attention: One or more AI discovery, user-fetch, indexability, snippet, synthetic reachability, or sitemap signals need attention.
- Why it matters: AI search systems need crawlable, reachable, indexable, and quotable public content. Training and data-use choices remain neutral publisher preferences.
- Status-specific guidance: The scanner could not verify this from safe public data. Manually verify first; if the site already handles it correctly, report that no code change is needed.
- Audience or recipient: The site owner, builder, or marketing team responsible for improving this public page.
- Constraints, examples, or source material: Treat the live URL as the public target to inspect, not as the only source of truth. When repository, CMS, or hosting access is available, use that implementation context before changing anything.
- Target outcome: After the fix is deployed and the public page is rescanned, this specific check should improve or pass without lowering other SEO / AEO, security, accessibility, or design signals.
## Task
Use the provided context to safely complete this workflow: Use the component scores and exact matched robots rules in the crawler report. Fix blocked search agents, noindex or snippet restrictions, canonical or sitemap gaps, and synthetic WAF/challenge failures. Preserve intentional training opt-outs and keep private, admin, and authenticated paths protected before rescanning.
Before editing, identify the likely source of the issue, the smallest change that can fix it, and any user-visible behavior that must be preserved.
## Output
Return a structured response with headings, prioritized recommendations, changed files or page areas, verification results, rollback notes, and stated assumptions.
## Rules
- Ask a clarifying question when required context is missing.
- Preserve the user's intent and avoid inventing facts.
- Verify the issue exists before changing code or content. If the issue is not reproducible, explain what you checked and recommend no code change.
- If the live URL and implementation source disagree, trust the implementation source for edits and use the live URL only to understand current public behavior.
- Keep the change narrowly scoped to this fix unless another change is required to avoid a regression.
- Match the existing framework, style, design system, routing patterns, and content conventions.
- Preserve existing URLs, forms, analytics, SEO metadata, accessibility semantics, and conversion flows unless the fix explicitly requires changing them.
- Do not perform broad refactors, dependency upgrades, redesigns, rewrites, migrations, file deletions, route changes, or destructive commands unless they are explicitly required and approved.
- Make changes that are easy to review and roll back.
- Verify the result with the smallest reliable test, build, browser check, or manual inspection available.
## Safety
- Do not request, expose, or reproduce sensitive data.
- Redact private details from examples unless the user explicitly says they are safe to include.
- Do not use credentials, cookies, authenticated data, hidden form values, or private response bodies.
- Do not weaken security headers, authentication, authorization, privacy controls, accessibility, or error handling to make the scan pass.

fail

high

Security

Priority 5

Add common public security headers

-14 rule pts

What failed

Several basic browser protection headers were not visible.

Evidence

Detected 1 of 5 common public security headers. Present: strict-transport-security. Missing: content-security-policy, x-content-type-options, x-frame-options, referrer-policy.

Priority

Priority 5: fix before sharing the page publicly.

Why it matters

These headers reduce avoidable browser-side risk and show a baseline of care before launch.

How to fix it

Configure headers such as Strict-Transport-Security, Content-Security-Policy, X-Content-Type-Options, X-Frame-Options, and Referrer-Policy.

Copyable agent prompt

## Role
Act as a focused expert website launch remediation agent for this workflow.
## Inputs
- Primary context: Improve getdocpilot.pro at https://getdocpilot.pro.
- Fix title: Add common public security headers.
- Scanner check: Common security headers.
- Category: Security.
- Status: fail.
- Severity: high.
- Priority: 5; lower numbers are more urgent.
- Score impact: 14 rule points lost.
- Evidence: Detected 1 of 5 common public security headers. Present: strict-transport-security. Missing: content-security-policy, x-content-type-options, x-frame-options, referrer-policy.
- What needs attention: Several basic browser protection headers were not visible.
- Why it matters: These headers reduce avoidable browser-side risk and show a baseline of care before launch.
- Status-specific guidance: A public check reported a failure. Reproduce or inspect the issue first, then make the smallest safe fix.
- Audience or recipient: The site owner, builder, or marketing team responsible for improving this public page.
- Constraints, examples, or source material: Treat the live URL as the public target to inspect, not as the only source of truth. When repository, CMS, or hosting access is available, use that implementation context before changing anything.
- Target outcome: After the fix is deployed and the public page is rescanned, this specific check should improve or pass without lowering other SEO / AEO, security, accessibility, or design signals.
## Task
Use the provided context to safely complete this workflow: Configure headers such as Strict-Transport-Security, Content-Security-Policy, X-Content-Type-Options, X-Frame-Options, and Referrer-Policy.
Before editing, identify the likely source of the issue, the smallest change that can fix it, and any user-visible behavior that must be preserved.
## Output
Return a structured response with headings, prioritized recommendations, changed files or page areas, verification results, rollback notes, and stated assumptions.
## Rules
- Ask a clarifying question when required context is missing.
- Preserve the user's intent and avoid inventing facts.
- Verify the issue exists before changing code or content. If the issue is not reproducible, explain what you checked and recommend no code change.
- If the live URL and implementation source disagree, trust the implementation source for edits and use the live URL only to understand current public behavior.
- Keep the change narrowly scoped to this fix unless another change is required to avoid a regression.
- Match the existing framework, style, design system, routing patterns, and content conventions.
- Preserve existing URLs, forms, analytics, SEO metadata, accessibility semantics, and conversion flows unless the fix explicitly requires changing them.
- Do not perform broad refactors, dependency upgrades, redesigns, rewrites, migrations, file deletions, route changes, or destructive commands unless they are explicitly required and approved.
- Make changes that are easy to review and roll back.
- Verify the result with the smallest reliable test, build, browser check, or manual inspection available.
## Safety
- Do not request, expose, or reproduce sensitive data.
- Redact private details from examples unless the user explicitly says they are safe to include.
- Do not use credentials, cookies, authenticated data, hidden form values, or private response bodies.
- Do not weaken security headers, authentication, authorization, privacy controls, accessibility, or error handling to make the scan pass.

fail

high

Accessibility

Priority 5

Fix rendered axe accessibility violations

-18 rule pts

What failed

The rendered page has accessibility rule violations detected by axe-core.

Evidence

axe found 3 violation rule(s), including 1 serious or critical rule(s). Top rules: color-contrast (2), heading-order (1), meta-viewport (1).

Priority

Priority 5: fix before sharing the page publicly.

Why it matters

axe checks the actual browser-rendered page, so these issues can affect people using keyboards, screen readers, or other assistive technology.

How to fix it

Fix the top axe rule IDs first, especially critical and serious violations around names, roles, labels, headings, contrast, landmarks, and keyboard-accessible controls.

Copyable agent prompt

## Role
Act as a focused expert website launch remediation agent for this workflow.
## Inputs
- Primary context: Improve getdocpilot.pro at https://getdocpilot.pro.
- Fix title: Fix rendered axe accessibility violations.
- Scanner check: Rendered axe accessibility violations.
- Category: Accessibility.
- Status: fail.
- Severity: high.
- Priority: 5; lower numbers are more urgent.
- Score impact: 18 rule points lost.
- Evidence: axe found 3 violation rule(s), including 1 serious or critical rule(s). Top rules: color-contrast (2), heading-order (1), meta-viewport (1).
- What needs attention: The rendered page has accessibility rule violations detected by axe-core.
- Why it matters: axe checks the actual browser-rendered page, so these issues can affect people using keyboards, screen readers, or other assistive technology.
- Status-specific guidance: A public check reported a failure. Reproduce or inspect the issue first, then make the smallest safe fix.
- Audience or recipient: The site owner, builder, or marketing team responsible for improving this public page.
- Constraints, examples, or source material: Treat the live URL as the public target to inspect, not as the only source of truth. When repository, CMS, or hosting access is available, use that implementation context before changing anything.
- Target outcome: After the fix is deployed and the public page is rescanned, this specific check should improve or pass without lowering other SEO / AEO, security, accessibility, or design signals.
## Task
Use the provided context to safely complete this workflow: Fix the top axe rule IDs first, especially critical and serious violations around names, roles, labels, headings, contrast, landmarks, and keyboard-accessible controls.
Before editing, identify the likely source of the issue, the smallest change that can fix it, and any user-visible behavior that must be preserved.
## Output
Return a structured response with headings, prioritized recommendations, changed files or page areas, verification results, rollback notes, and stated assumptions.
## Rules
- Ask a clarifying question when required context is missing.
- Preserve the user's intent and avoid inventing facts.
- Verify the issue exists before changing code or content. If the issue is not reproducible, explain what you checked and recommend no code change.
- If the live URL and implementation source disagree, trust the implementation source for edits and use the live URL only to understand current public behavior.
- Keep the change narrowly scoped to this fix unless another change is required to avoid a regression.
- Match the existing framework, style, design system, routing patterns, and content conventions.
- Preserve existing URLs, forms, analytics, SEO metadata, accessibility semantics, and conversion flows unless the fix explicitly requires changing them.
- Do not perform broad refactors, dependency upgrades, redesigns, rewrites, migrations, file deletions, route changes, or destructive commands unless they are explicitly required and approved.
- Make changes that are easy to review and roll back.
- Verify the result with the smallest reliable test, build, browser check, or manual inspection available.
## Safety
- Do not request, expose, or reproduce sensitive data.
- Redact private details from examples unless the user explicitly says they are safe to include.
- Do not use credentials, cookies, authenticated data, hidden form values, or private response bodies.
- Do not weaken security headers, authentication, authorization, privacy controls, accessibility, or error handling to make the scan pass.

fail

high

Design

Priority 4

Make the primary CTA obvious

-14 rule pts

What failed

The page does not have a detectable call to action.

Evidence

Detected 0 CTA candidate(s).

Priority

Priority 4: fix before sharing the page publicly.

Why it matters

Early visitors need a clear next step, such as trying the product, joining a waitlist, or booking a demo.

How to fix it

Add one prominent CTA above the fold with action-oriented text such as Start, Join, Try, Book, or Get started.

Copyable agent prompt

## Role
Act as a focused expert website launch remediation agent for this workflow.
## Inputs
- Primary context: Improve getdocpilot.pro at https://getdocpilot.pro.
- Fix title: Make the primary CTA obvious.
- Scanner check: Visible primary CTA.
- Category: Design.
- Status: fail.
- Severity: high.
- Priority: 4; lower numbers are more urgent.
- Score impact: 14 rule points lost.
- Evidence: Detected 0 CTA candidate(s).
- What needs attention: The page does not have a detectable call to action.
- Why it matters: Early visitors need a clear next step, such as trying the product, joining a waitlist, or booking a demo.
- Status-specific guidance: A public check reported a failure. Reproduce or inspect the issue first, then make the smallest safe fix.
- Audience or recipient: The site owner, builder, or marketing team responsible for improving this public page.
- Constraints, examples, or source material: Treat the live URL as the public target to inspect, not as the only source of truth. When repository, CMS, or hosting access is available, use that implementation context before changing anything.
- Target outcome: After the fix is deployed and the public page is rescanned, this specific check should improve or pass without lowering other SEO / AEO, security, accessibility, or design signals.
## Task
Use the provided context to safely complete this workflow: Add one prominent CTA above the fold with action-oriented text such as Start, Join, Try, Book, or Get started.
Before editing, identify the likely source of the issue, the smallest change that can fix it, and any user-visible behavior that must be preserved.
## Output
Return a structured response with headings, prioritized recommendations, changed files or page areas, verification results, rollback notes, and stated assumptions.
## Rules
- Ask a clarifying question when required context is missing.
- Preserve the user's intent and avoid inventing facts.
- Verify the issue exists before changing code or content. If the issue is not reproducible, explain what you checked and recommend no code change.
- If the live URL and implementation source disagree, trust the implementation source for edits and use the live URL only to understand current public behavior.
- Keep the change narrowly scoped to this fix unless another change is required to avoid a regression.
- Match the existing framework, style, design system, routing patterns, and content conventions.
- Preserve existing URLs, forms, analytics, SEO metadata, accessibility semantics, and conversion flows unless the fix explicitly requires changing them.
- Do not perform broad refactors, dependency upgrades, redesigns, rewrites, migrations, file deletions, route changes, or destructive commands unless they are explicitly required and approved.
- Make changes that are easy to review and roll back.
- Verify the result with the smallest reliable test, build, browser check, or manual inspection available.
## Safety
- Do not request, expose, or reproduce sensitive data.
- Redact private details from examples unless the user explicitly says they are safe to include.
- Do not use credentials, cookies, authenticated data, hidden form values, or private response bodies.
- Do not weaken security headers, authentication, authorization, privacy controls, accessibility, or error handling to make the scan pass.

Score aggregation details

Category scores come from earned rule points divided by available rule points. Failed checks are ordered by severity and score lost.

50/100

6 pass, 5 fail, 1 unknown

-10 rule pts

Detected 0 JSON-LD schema block(s).

61/100

4 pass, 2 fail, 0 unknown

Security

Severity mix: 2 critical, 3 high, 0 medium, 0 low.

critical

Sensitive file probes

-16 rule pts

A small allowlist probe returned a public success response.

high

Common security headers

-14 rule pts

Detected 1 of 5 common public security headers. Present: strict-transport-security. Missing: content-security-policy, x-content-type-options, x-frame-options, referrer-policy.

50/100

4 pass, 4 fail, 0 unknown

Accessibility

Severity mix: 0 critical, 3 high, 5 medium, 0 low.

high

Rendered axe accessibility violations

-18 rule pts

axe found 3 violation rule(s), including 1 serious or critical rule(s). Top rules: color-contrast (2), heading-order (1), meta-viewport (1).

medium

Heading order

-11 rule pts

Heading levels found: none.

medium

Landmark presence

-10 rule pts

Detected 0 landmark element(s) or roles.

28/100

3 pass, 8 fail, 0 unknown

Design

Severity mix: 0 critical, 3 high, 6 medium, 2 low.

high

Visible primary CTA

-14 rule pts

Detected 0 CTA candidate(s).

high

Hero clarity signals

-13 rule pts

Detected 0 H1 heading(s) and 106 meta-description characters.

medium

Text density

Horizontal overflow: 0px. Small tap targets: 32.

Failed: earned 0 of 9 points.

Priority: Priority 13: fix during launch polish.

Why it matters: Horizontal overflow and tiny tap targets make the page feel broken on real devices, especially for mobile visitors.

Fix: Remove elements wider than the viewport, add responsive constraints, and make important links, buttons, inputs, and controls at least 40px tall and wide where possible.

Copyable agent prompt

## Role
Act as a focused expert website launch remediation agent for this workflow.
## Inputs
- Primary context: Improve getdocpilot.pro at https://getdocpilot.pro.
- Fix title: Fix rendered layout ergonomics.
- Scanner check: Rendered layout ergonomics.
- Category: Design.
- Status: fail.
- Severity: medium.
- Priority: 13; lower numbers are more urgent.
- Score impact: 9 of 9 rule points lost.
- Evidence: Horizontal overflow: 0px. Small tap targets: 32.
- What needs attention: The browser-rendered page has layout or tap-target issues.
- Why it matters: Horizontal overflow and tiny tap targets make the page feel broken on real devices, especially for mobile visitors.
- Status-specific guidance: A public check reported a failure. Reproduce or inspect the issue first, then make the smallest safe fix.
- Audience or recipient: The site owner, builder, or marketing team responsible for improving this public page.
- Constraints, examples, or source material: Treat the live URL as the public target to inspect, not as the only source of truth. When repository, CMS, or hosting access is available, use that implementation context before changing anything.
- Target outcome: After the fix is deployed and the public page is rescanned, this specific check should improve or pass without lowering other SEO / AEO, security, accessibility, or design signals.
## Task
Use the provided context to safely complete this workflow: Remove elements wider than the viewport, add responsive constraints, and make important links, buttons, inputs, and controls at least 40px tall and wide where possible.
Before editing, identify the likely source of the issue, the smallest change that can fix it, and any user-visible behavior that must be preserved.
## Output
Return a structured response with headings, prioritized recommendations, changed files or page areas, verification results, rollback notes, and stated assumptions.
## Rules
- Ask a clarifying question when required context is missing.
- Preserve the user's intent and avoid inventing facts.
- Verify the issue exists before changing code or content. If the issue is not reproducible, explain what you checked and recommend no code change.
- If the live URL and implementation source disagree, trust the implementation source for edits and use the live URL only to understand current public behavior.
- Keep the change narrowly scoped to this fix unless another change is required to avoid a regression.
- Match the existing framework, style, design system, routing patterns, and content conventions.
- Preserve existing URLs, forms, analytics, SEO metadata, accessibility semantics, and conversion flows unless the fix explicitly requires changing them.
- Do not perform broad refactors, dependency upgrades, redesigns, rewrites, migrations, file deletions, route changes, or destructive commands unless they are explicitly required and approved.
- Make changes that are easy to review and roll back.
- Verify the result with the smallest reliable test, build, browser check, or manual inspection available.
## Safety
- Do not request, expose, or reproduce sensitive data.
- Redact private details from examples unless the user explicitly says they are safe to include.
- Do not use credentials, cookies, authenticated data, hidden form values, or private response bodies.
- Do not weaken security headers, authentication, authorization, privacy controls, accessibility, or error handling to make the scan pass.

Page-level AEO readiness

Shared eligibility and content signals that affect every search and answer agent.

60/100 ready

Index and citation eligibility

No general noindex directive was detected.

Snippet and answer controls

No general nosnippet or max-snippet:0 control was detected.

Canonical alignment

No canonical URL was detected.

Sitemap coverage and freshness

The exact URL appears in sitemap.xml.

Structured data

Detected 0 JSON-LD block(s), 0 parse error(s), and types none.

Public or paywalled content

No isAccessibleForFree structured-data value was detected.

Entity clarity

Detected 2 of 3 core identity signals across the title, description, and H1.

Answer-ready visible text

Detected 4 visible words and 0 audience, use-case, pricing, or integration signals.

Authorship and accountability

No author meta value or structured-data author was detected.

Published or updated date

No datePublished or dateModified value was detected in structured data.

Supporting-source links

No external supporting links were detected; this is contextual rather than a universal requirement.

Rendered content availability

Rendered audit completed with 217 visible text element(s).

Synthetic search-agent reachability

8 of 8 search/discovery User-Agent probes returned reachable content.

Optional LLM-readable summary

https://getdocpilot.pro/llms.txt returned HTTP 200; this is supplemental and does not determine AI-search eligibility.

OpenAIChatGPT search

OAI-SearchBot

PASS · ALLOWED

AI search

Robots: allowed by * allow: / · line 2

Probe: reachable · HTTP 200 · 100% parity

IndexSnippetsSitemapPublic content

Vendor documentationDefinition checked 2026-07-30

OpenAIOpenAI model training

GPTBot

POLICY ALLOWED

Model training

Robots: allowed by * allow: / · line 2

Probe: not tested for this control

IndexSnippetsSitemapPublic content

Vendor documentationDefinition checked 2026-07-30

OpenAIChatGPT user fetches

ChatGPT-User

UNKNOWN

User-requested fetch

Robots: not applicable to user-requested fetches

Probe: not tested for this control

IndexSnippetsSitemapPublic content

Vendor documentationDefinition checked 2026-07-30

AnthropicClaude model training

ClaudeBot

POLICY ALLOWED

Model training

Robots: allowed by * allow: / · line 2

Probe: not tested for this control

IndexSnippetsSitemapPublic content

Vendor documentationDefinition checked 2026-07-30

AnthropicClaude search

Claude-SearchBot

PASS · ALLOWED

AI search

Robots: allowed by * allow: / · line 2

Probe: reachable · HTTP 200 · 100% parity

IndexSnippetsSitemapPublic content

Vendor documentationDefinition checked 2026-07-30

AnthropicClaude user fetches

Claude-User

PASS · ALLOWED

User-requested fetch

Robots: allowed by * allow: / · line 2

Probe: reachable · HTTP 200 · 100% parity

IndexSnippetsSitemapPublic content

Vendor documentationDefinition checked 2026-07-30

GoogleGoogle Search and AI features

Googlebot

PASS · ALLOWED

Search and discovery

Robots: allowed by * allow: / · line 2

Probe: reachable · HTTP 200 · 100% parity

IndexSnippetsSitemapPublic content

Vendor documentationDefinition checked 2026-07-30

GoogleGemini data use and grounding

Google-Extended

POLICY ALLOWED

Data-use policy control

Robots: allowed by * allow: / · line 2

Probe: not tested for this control

IndexSnippetsSitemapPublic content

Vendor documentationDefinition checked 2026-07-30

MicrosoftBing and Copilot

Bingbot

PASS · ALLOWED

Search and discovery

Robots: allowed by * allow: / · line 2

Probe: reachable · HTTP 200 · 100% parity

IndexSnippetsSitemapPublic content

Vendor documentationDefinition checked 2026-07-30

PerplexityPerplexity search

PerplexityBot

PASS · ALLOWED

AI search

Robots: allowed by * allow: / · line 2

Probe: reachable · HTTP 200 · 100% parity

IndexSnippetsSitemapPublic content

Vendor documentationDefinition checked 2026-07-30

PerplexityPerplexity user fetches

Perplexity-User

UNKNOWN

User-requested fetch

Robots: not applicable to user-requested fetches

Probe: not tested for this control

IndexSnippetsSitemapPublic content

Vendor documentationDefinition checked 2026-07-30

AppleSiri, Spotlight, and Safari search

Applebot

PASS · ALLOWED

Search and discovery

Robots: allowed by * allow: / · line 2

Probe: reachable · HTTP 200 · 100% parity

IndexSnippetsSitemapPublic content

Vendor documentationDefinition checked 2026-07-30

AppleApple foundation-model training

Applebot-Extended

POLICY ALLOWED

Data-use policy control

Robots: allowed by * allow: / · line 2

Probe: not tested for this control

IndexSnippetsSitemapPublic content

Vendor documentationDefinition checked 2026-07-30

Mistral AIMistral search

MistralAI-Index

PASS · ALLOWED

AI search

Robots: allowed by * allow: / · line 2

Probe: reachable · HTTP 200 · 100% parity

IndexSnippetsSitemapPublic content

Vendor documentationDefinition checked 2026-07-30

Mistral AIMistral user fetches

MistralAI-User

PASS · ALLOWED

User-requested fetch

Robots: allowed by * allow: / · line 2

Probe: reachable · HTTP 200 · 100% parity

IndexSnippetsSitemapPublic content

Vendor documentationDefinition checked 2026-07-30

MetaMeta AI model and product data

meta-externalagent

POLICY ALLOWED

Model training

Robots: allowed by * allow: / · line 2

Probe: not tested for this control

IndexSnippetsSitemapPublic content

Vendor documentationDefinition checked 2026-07-30

MetaMeta AI user fetches

meta-externalfetcher

PASS · ALLOWED

User-requested fetch

Robots: allowed by * allow: / · line 2

Probe: reachable · HTTP 200 · 100% parity

IndexSnippetsSitemapPublic content

Vendor documentationDefinition checked 2026-07-30

AmazonAmazon model training

Amazonbot

POLICY ALLOWED

Model training

Robots: allowed by * allow: / · line 2

Probe: not tested for this control

IndexSnippetsSitemapPublic content

Vendor documentationDefinition checked 2026-07-30

AmazonAlexa and Rufus search

Amzn-SearchBot

PASS · ALLOWED

AI search

Robots: allowed by * allow: / · line 2

Probe: reachable · HTTP 200 · 100% parity

IndexSnippetsSitemapPublic content

Vendor documentationDefinition checked 2026-07-30

AmazonAlexa user fetches

Amzn-User

PASS · ALLOWED

User-requested fetch

Robots: allowed by * allow: / · line 2

Probe: reachable · HTTP 200 · 100% parity

IndexSnippetsSitemapPublic content

Vendor documentationDefinition checked 2026-07-30

Common CrawlOpen web datasets

CCBot

POLICY ALLOWED

Model training

Robots: allowed by * allow: / · line 2

Probe: not tested for this control

IndexSnippetsSitemapPublic content

Vendor documentationDefinition checked 2026-07-30

Public report link

Markdown export

Share the website audit report

Copy a public report link or a Markdown version with scores, fixes, opportunities, insights, and a normal link back to the scanned site.

Share preview

getdocpilot.pro website audit report

Needs fixes before launch: 47/100 overall, with prioritized fixes for SEO, security, accessibility, and design.

Public report link

Markdown report

# getdocpilot.pro Website Scan

Scanned URL: [https://getdocpilot.pro](https://getdocpilot.pro)
Report URL: /scan/getdocpilot-pro-47-launch-readiness-report-d545a2b2
Created: 2026-07-31T21:03:35.782Z

## Score Summary

- Overall: 47/100
- SEO / AEO: 50/100
- Security: 61/100
- Accessibility: 50/100
- Design: 28/100

## Launch Readiness

Needs fixes before launch (High risk).

Passed: 17. Failed: 19. Unknown: 1.
Strongest area: Security. Weakest area: Design.

## AI Crawler Access

These results combine robots.txt policy, page controls, and bounded synthetic User-Agent probes. Synthetic probes do not prove that traffic came from the vendor; training and data-use choices are neutral publisher preferences.

- **OpenAI — ChatGPT search** (OAI-SearchBot): PASS — robots allowed; synthetic probe reachable (HTTP 200). Allowed by * allow: / on line 2. Synthetic User-Agent probe returned HTTP 200 with 100% sampled-content parity.
- **OpenAI — OpenAI model training** (GPTBot): PREFERENCE — robots allowed; synthetic probe not_tested. Allowed by * allow: / on line 2. No synthetic fetch is appropriate for this policy or training control.
- **OpenAI — ChatGPT user fetches** (ChatGPT-User): UNKNOWN — robots not_applicable; synthetic probe not_tested. ChatGPT-User is used for user-requested retrieval, so robots.txt is not treated as a reliable access control for this row. No synthetic fetch is appropriate for this policy or training control.
- **Anthropic — Claude model training** (ClaudeBot): PREFERENCE — robots allowed; synthetic probe not_tested. Allowed by * allow: / on line 2. No synthetic fetch is appropriate for this policy or training control.
- **Anthropic — Claude search** (Claude-SearchBot): PASS — robots allowed; synthetic probe reachable (HTTP 200). Allowed by * allow: / on line 2. Synthetic User-Agent probe returned HTTP 200 with 100% sampled-content parity.
- **Anthropic — Claude user fetches** (Claude-User): PASS — robots allowed; synthetic probe reachable (HTTP 200). Allowed by * allow: / on line 2. Synthetic User-Agent probe returned HTTP 200 with 100% sampled-content parity.
- **Google — Google Search and AI features** (Googlebot): PASS — robots allowed; synthetic probe reachable (HTTP 200). Allowed by * allow: / on line 2. Synthetic User-Agent probe returned HTTP 200 with 100% sampled-content parity.
- **Google — Gemini data use and grounding** (Google-Extended): PREFERENCE — robots allowed; synthetic probe not_tested. Allowed by * allow: / on line 2. No synthetic fetch is appropriate for this policy or training control.
- **Microsoft — Bing and Copilot** (Bingbot): PASS — robots allowed; synthetic probe reachable (HTTP 200). Allowed by * allow: / on line 2. Synthetic User-Agent probe returned HTTP 200 with 100% sampled-content parity.
- **Perplexity — Perplexity search** (PerplexityBot): PASS — robots allowed; synthetic probe reachable (HTTP 200). Allowed by * allow: / on line 2. Synthetic User-Agent probe returned HTTP 200 with 100% sampled-content parity.
- **Perplexity — Perplexity user fetches** (Perplexity-User): UNKNOWN — robots not_applicable; synthetic probe not_tested. Perplexity-User is used for user-requested retrieval, so robots.txt is not treated as a reliable access control for this row. No synthetic fetch is appropriate for this policy or training control.
- **Apple — Siri, Spotlight, and Safari search** (Applebot): PASS — robots allowed; synthetic probe reachable (HTTP 200). Allowed by * allow: / on line 2. Synthetic User-Agent probe returned HTTP 200 with 100% sampled-content parity.
- **Apple — Apple foundation-model training** (Applebot-Extended): PREFERENCE — robots allowed; synthetic probe not_tested. Allowed by * allow: / on line 2. No synthetic fetch is appropriate for this policy or training control.
- **Mistral AI — Mistral search** (MistralAI-Index): PASS — robots allowed; synthetic probe reachable (HTTP 200). Allowed by * allow: / on line 2. Synthetic User-Agent probe returned HTTP 200 with 100% sampled-content parity.
- **Mistral AI — Mistral user fetches** (MistralAI-User): PASS — robots allowed; synthetic probe reachable (HTTP 200). Allowed by * allow: / on line 2. Synthetic User-Agent probe returned HTTP 200 with 100% sampled-content parity.
- **Meta — Meta AI model and product data** (meta-externalagent): PREFERENCE — robots allowed; synthetic probe not_tested. Allowed by * allow: / on line 2. No synthetic fetch is appropriate for this policy or training control.
- **Meta — Meta AI user fetches** (meta-externalfetcher): PASS — robots allowed; synthetic probe reachable (HTTP 200). Allowed by * allow: / on line 2. Synthetic User-Agent probe returned HTTP 200 with 100% sampled-content parity.
- **Amazon — Amazon model training** (Amazonbot): PREFERENCE — robots allowed; synthetic probe not_tested. Allowed by * allow: / on line 2. No synthetic fetch is appropriate for this policy or training control.
- **Amazon — Alexa and Rufus search** (Amzn-SearchBot): PASS — robots allowed; synthetic probe reachable (HTTP 200). Allowed by * allow: / on line 2. Synthetic User-Agent probe returned HTTP 200 with 100% sampled-content parity.
- **Amazon — Alexa user fetches** (Amzn-User): PASS — robots allowed; synthetic probe reachable (HTTP 200). Allowed by * allow: / on line 2. Synthetic User-Agent probe returned HTTP 200 with 100% sampled-content parity.
- **Common Crawl — Open web datasets** (CCBot): PREFERENCE — robots allowed; synthetic probe not_tested. Allowed by * allow: / on line 2. No synthetic fetch is appropriate for this policy or training control.

## Page-level AEO Readiness

Readiness: 60/100

- **Index and citation eligibility**: PASS — No general noindex directive was detected.
- **Snippet and answer controls**: PASS — No general nosnippet or max-snippet:0 control was detected.
- **Canonical alignment**: FAIL — No canonical URL was detected.
- **Sitemap coverage and freshness**: PASS — The exact URL appears in sitemap.xml.
- **Structured data**: UNKNOWN — Detected 0 JSON-LD block(s), 0 parse error(s), and types none.
- **Public or paywalled content**: UNKNOWN — No isAccessibleForFree structured-data value was detected.
- **Entity clarity**: UNKNOWN — Detected 2 of 3 core identity signals across the title, description, and H1.
- **Answer-ready visible text**: FAIL — Detected 4 visible words and 0 audience, use-case, pricing, or integration signals.
- **Authorship and accountability**: UNKNOWN — No author meta value or structured-data author was detected.
- **Published or updated date**: UNKNOWN — No datePublished or dateModified value was detected in structured data.
- **Supporting-source links**: UNKNOWN — No external supporting links were detected; this is contextual rather than a universal requirement.
- **Rendered content availability**: PASS — Rendered audit completed with 217 visible text element(s).
- **Synthetic search-agent reachability**: PASS — 8 of 8 search/discovery User-Agent probes returned reachable content.
- **Optional LLM-readable summary**: INFO — https://getdocpilot.pro/llms.txt returned HTTP 200; this is supplemental and does not determine AI-search eligibility.

## Prioritized Fixes

### 1. Remove exposed sensitive files

- Category: Security
- Status: fail
- Severity: critical
- Rule points lost: 16
- Evidence: A small allowlist probe returned a public success response.
- Why it matters: Publicly exposed config or backup files can leak implementation details or secrets.
- Fix: Remove the exposed file, block public access to that path, and rotate any secrets that may have been exposed.

### 2. Improve AI search and crawler readiness

- Category: SEO / AEO
- Status: unknown
- Severity: critical
- Rule points lost: 8
- Evidence: FreeScan.app reached the public page with HTTP 200. AEO crawler readiness is 92%: discovery 45/45, index and snippet eligibility 20/25, synthetic reachability 20/20, sitemap freshness 7/10. robots.txt did not block the scored AI search or user-fetch agents for this page path.
- Why it matters: AI search systems need crawlable, reachable, indexable, and quotable public content. Training and data-use choices remain neutral publisher preferences.
- Fix: Use the component scores and exact matched robots rules in the crawler report. Fix blocked search agents, noindex or snippet restrictions, canonical or sitemap gaps, and synthetic WAF/challenge failures. Preserve intentional training opt-outs and keep private, admin, and authenticated paths protected before rescanning.

### 3. Add common public security headers

- Category: Security
- Status: fail
- Severity: high
- Rule points lost: 14
- Evidence: Detected 1 of 5 common public security headers. Present: strict-transport-security. Missing: content-security-policy, x-content-type-options, x-frame-options, referrer-policy.
- Why it matters: These headers reduce avoidable browser-side risk and show a baseline of care before launch.
- Fix: Configure headers such as Strict-Transport-Security, Content-Security-Policy, X-Content-Type-Options, X-Frame-Options, and Referrer-Policy.

### 4. Fix rendered axe accessibility violations

- Category: Accessibility
- Status: fail
- Severity: high
- Rule points lost: 18
- Evidence: axe found 3 violation rule(s), including 1 serious or critical rule(s). Top rules: color-contrast (2), heading-order (1), meta-viewport (1).
- Why it matters: axe checks the actual browser-rendered page, so these issues can affect people using keyboards, screen readers, or other assistive technology.
- Fix: Fix the top axe rule IDs first, especially critical and serious violations around names, roles, labels, headings, contrast, landmarks, and keyboard-accessible controls.

### 5. Make the primary CTA obvious

- Category: Design
- Status: fail
- Severity: high
- Rule points lost: 14
- Evidence: Detected 0 CTA candidate(s).
- Why it matters: Early visitors need a clear next step, such as trying the product, joining a waitlist, or booking a demo.
- Fix: Add one prominent CTA above the fold with action-oriented text such as Start, Join, Try, Book, or Get started.

## Opportunities

### Add answer-ready sections for common buyer questions

- Impact: high
- Category: SEO / AEO
- Evidence: Pricing signals: 0. Use-case signals: 0. Integration/API signals: 0.
- Why it matters: Answer engines and search visitors need concise textual answers to summarize who the product is for, how it works, what it costs, and what it connects with.
- Next step: Add short, crawlable sections for pricing or plans, ideal users, use cases, integrations, security, and how the product differs from alternatives.

### Expose important supporting pages in navigation or footer

- Impact: medium
- Category: SEO / AEO
- Evidence: No pricing, docs, contact, security, privacy, terms, or about links were detected in public internal links.
- Why it matters: Internal links help visitors, crawlers, and AI answer systems discover supporting facts instead of relying on one landing page.
- Next step: Link to the most useful public pages, especially pricing, docs, contact, security, privacy, terms, and about pages where applicable.

### Make trust and proof easier to detect

- Impact: medium
- Category: Design
- Evidence: Detected 0 trust-signal keyword occurrence(s).
- Why it matters: Visitors who arrive cold from search, social, or AI citations need proof before they submit a form, start a trial, or buy.
- Next step: Add honest proof such as customer quotes, recognizable logos, security notes, usage stats, reviews, case studies, or founder credibility.

### Review snippet and preview controls

- Impact: low
- Category: SEO / AEO
- Evidence: Open Graph image was detected. Preview controls detected: 0.
- Why it matters: Preview controls can clarify how much text, image, and video content search systems may show from the page.
- Next step: Only add robots preview controls when you intentionally want to limit snippets or image/video previews; otherwise leave previews open.

### Tighten the live color system

- Impact: high
- Category: Accessibility
- Evidence: 16 of 100 rendered contrast sample(s) missed target. Worst ratio: 1.
- Why it matters: Computed contrast catches the actual colors visitors see after CSS, themes, and overlays are applied.
- Next step: Audit foreground/background token pairs for body text, muted text, links, buttons, inputs, and badges, then raise weak pairs to WCAG AA contrast targets.

### Polish rendered responsive ergonomics

- Impact: medium
- Category: Design
- Evidence: Horizontal overflow: 0px. Small tap targets: 32.
- Why it matters: Overflow and tiny controls are easy for static scans to miss but obvious to real users, especially on mobile and tablet layouts.
- Next step: Constrain wide elements, avoid fixed-width content that exceeds the viewport, and increase touch target sizes for interactive controls.

### Measure search performance with first-party data

- Impact: medium
- Category: SEO / AEO
- Evidence: robots.txt and sitemap.xml were reachable, so the site has the basics needed for Search Console verification and monitoring.
- Why it matters: A scan can identify technical readiness, but Search Console and analytics reveal impressions, queries, clicks, pages, and conversions over time.
- Next step: Verify the domain in Search Console, submit the sitemap, and pair query/page data with analytics events for signups, demo requests, and purchases.

## Insights

### The page appears basically crawlable

- Category: SEO / AEO
- Evidence: HTTP 200. robots.txt: HTTP 200. sitemap.xml: HTTP 200. noindex check: clear.
- Interpretation: The public page satisfies the basic crawl/index path the scan can verify.
- Recommended use: Use this as the first launch gate before deeper content, ranking, or AI visibility work.

### AEO depends on normal SEO plus answerable text

- Category: SEO / AEO
- Evidence: Visible words: 4. H1 count: 0. Audience signals: 0. CTA labels: none detected.
- Interpretation: Google AI features currently rely on standard Search eligibility; the extra advantage comes from content that is easy to quote, summarize, and verify.
- Recommended use: Prioritize clear text answers, crawlable support pages, accurate schema, and visible proof over speculative AI-only markup.

### Detected entity signals

- Category: SEO / AEO
- Evidence: Title: DocPilot. H1: missing. Schema types: none.
- Interpretation: The stronger and more consistent these entity signals are, the easier it is for search and answer systems to identify the brand, product category, and page purpose.
- Recommended use: Keep the title, H1, meta description, Open Graph, schema, footer, and about/pricing/docs pages aligned around the same product facts.

### No structured data detected

- Category: SEO / AEO
- Evidence: JSON-LD blocks: 0. Types: none. Parse errors: 0.
- Interpretation: Missing or invalid structured data makes the page rely more heavily on inferred meaning from text and layout.
- Recommended use: Validate JSON-LD and use only accurate facts that are visible or clearly supported on the public page.

### Weakest score area

- Category: Design
- Evidence: SEO / AEO: 50/100. Security: 61/100. Accessibility: 50/100. Design: 28/100
- Interpretation: The weakest area is Design, so improvements there should have the most visible effect on readiness.
- Recommended use: Use the score mix to choose the next workstream instead of treating every issue as equally urgent.

### LLM-readable file found

- Category: SEO / AEO
- Evidence: https://getdocpilot.pro/llms.txt returned HTTP 200.
- Interpretation: llms.txt can be a useful optional summary for agents, but it should not be treated as a guaranteed AI search ranking factor.
- Recommended use: Invest first in crawlability, helpful visible content, internal links, and accurate schema; add llms.txt as a tidy supplement.

### Rendered page experience snapshot

- Category: Design
- Evidence: Rendered text samples: 100. Contrast failures: 16. Console errors: 1. Horizontal overflow: 0px.
- Interpretation: The scan inspected the browser-rendered page, so contrast, runtime, layout, and timing signals are more representative than static markup alone.
- Recommended use: Use rendered checks to prioritize issues that visitors actually experience after JavaScript and CSS load.

### Rendered speed snapshot

- Category: Design
- Evidence: DOMContentLoaded: 666ms. Load complete: 681ms. First contentful paint: 224ms. Resources: 8. Scripts: 3. Images: 2. Third-party origins: 5. Transfer: not available.
- Interpretation: These are lightweight browser timings from one rendered scan, so they are useful directional signals rather than real-user performance proof.
- Recommended use: Use slow timings, high script counts, heavy transfer size, and many third-party origins to choose focused speed work, then verify important changes with analytics or field data when available.

### Rendered axe accessibility snapshot

- Category: Accessibility
- Evidence: axe violations: 3. Critical: 0. Serious: 1. Top rules: color-contrast, heading-order, meta-viewport.
- Interpretation: axe-core catches common accessibility failures in the actual rendered DOM, but it is still automated coverage and not a full manual accessibility audit.
- Recommended use: Treat critical and serious axe failures as high-priority fixes, then manually review keyboard flow, focus states, screen reader meaning, and interaction states.

## Scope

FreeScan.app performs safe public checks only. It is not a penetration test, full SEO engagement, full accessibility audit, WCAG certification, backlink audit, rank tracker, or analytics platform.

Public reports expose the scanned public URL, safe scores, sanitized public evidence, and fix guidance. They do not include credentials, cookies, hidden form values, or sensitive response bodies.

Rescan same URL

Rerun the full deterministic scanner for getdocpilot.pro without re-entering the URL. The previous report stays saved so the next result can be compared against it.

Website audit scorecard for getdocpilot.pro

Remove exposed sensitive files

Copyable agent prompt

Improve AI search and crawler readiness

Copyable agent prompt

Add common public security headers

Copyable agent prompt

Fix rendered axe accessibility violations

Copyable agent prompt

Make the primary CTA obvious

Copyable agent prompt

SEO / AEO

Page title

Canonical tag

Schema presence

Security

Sensitive file probes

Common security headers

Accessibility

Rendered axe accessibility violations

Heading order

Landmark presence

Design

Visible primary CTA

Hero clarity signals

Text density

Failed checks

Page title

Copyable agent prompt

Heading structure

Copyable agent prompt

Canonical tag

Copyable agent prompt

Schema presence

Copyable agent prompt

Internal link basics

Copyable agent prompt

Common security headers

Copyable agent prompt

Sensitive file probes

Copyable agent prompt

Heading order

Copyable agent prompt

Landmark presence

Copyable agent prompt

Basic contrast

Copyable agent prompt

Rendered axe accessibility violations

Copyable agent prompt

Visible primary CTA

Copyable agent prompt

Hero clarity signals

Copyable agent prompt

Text density

Copyable agent prompt

Trust signals

Copyable agent prompt

Spacing consistency

Copyable agent prompt

Visual hierarchy

Copyable agent prompt

Runtime console health

Copyable agent prompt

Rendered layout ergonomics

Copyable agent prompt

AI crawler accessMajor AI search, user-fetch, and data-use agents checked for /, with robots evidence, synthetic reachability, and page-level AEO controls.12 pass0 fail2 unknown7 preferences

Unknown and not detected statesFreeScan.app keeps partial public data explicit. It marks unverifiable signals as unknown or not detected instead of inventing evidence.

Safe fetch metadataPublic headers and redirects captured during intake. Response bodies, cookies, and credentials are not stored.

Website audit scorecard for getdocpilot.pro

Remove exposed sensitive files

Copyable agent prompt

Improve AI search and crawler readiness

Copyable agent prompt

Add common public security headers

Copyable agent prompt

Fix rendered axe accessibility violations

Copyable agent prompt

Make the primary CTA obvious

Copyable agent prompt

SEO / AEO