completed

HTTP 200

0 redirects

38 checks

Website audit scorecard for humanizemy.ai

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

Submitted

https://humanizemy.ai/

Final URL

https://humanizemy.ai

Created

Jul 31, 2026, 8:14 PM

Safe fetch

106 ms

Four-score result

Close to ready (Needs polish): 31 passed, 6 failed, and 1 unknown. Strongest area: Security. Weakest area: Accessibility.

Overall

out of 100

SEO / AEO

out of 100

93/111 rule points

Security

out of 100

68/76 rule points

Accessibility

out of 100

68/94 rule points

Design

out of 100

91/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 / AEO93/111

Security68/76

Accessibility68/94

Design91/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), region (1), empty-table-header (1).

high

SEO / AEO

Meta description

Meta description is 175 characters.

medium

Design

Text density

Detected about 4957 visible word(s).

medium

Design

Rendered layout ergonomics

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

Recommendations

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

5 fixes

3 opportunities

9 insights

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. GPTBot, ClaudeBot, Google-Extended, and 4 more are explicit training or data-use opt-outs and do not reduce the AEO score. AEO crawler readiness is 100%: discovery 45/45, index and snippet eligibility 25/25, synthetic reachability 20/20, sitemap freshness 10/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 humanizemy.ai at https://humanizemy.ai.
- 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. GPTBot, ClaudeBot, Google-Extended, and 4 more are explicit training or data-use opt-outs and do not reduce the AEO score. AEO crawler readiness is 100%: discovery 45/45, index and snippet eligibility 25/25, synthetic reachability 20/20, sitemap freshness 10/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

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), region (1), empty-table-header (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 humanizemy.ai at https://humanizemy.ai.
- 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), region (1), empty-table-header (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

SEO / AEO

Priority 3

Add a useful meta description

-10 rule pts

What failed

The page does not expose a strong short summary for search and answer engines.

Evidence

Meta description is 175 characters.

Priority

Priority 3: fix before sharing the page publicly.

Why it matters

A missing description makes previews weaker when early users share or find the page.

How to fix it

Add a meta description around 50 to 170 characters that says who the product helps and what outcome it creates.

Copyable agent prompt

## Role
Act as a focused expert website launch remediation agent for this workflow.
## Inputs
- Primary context: Improve humanizemy.ai at https://humanizemy.ai.
- Fix title: Add a useful meta description.
- Scanner check: Meta description.
- Category: SEO / AEO.
- Status: fail.
- Severity: high.
- Priority: 3; lower numbers are more urgent.
- Score impact: 10 rule points lost.
- Evidence: Meta description is 175 characters.
- What needs attention: The page does not expose a strong short summary for search and answer engines.
- Why it matters: A missing description makes previews weaker when early users share or find the page.
- 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 a meta description around 50 to 170 characters that says who the product helps and what outcome it creates.
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

-8 rule pts

What failed

Several basic browser protection headers were not visible.

Evidence

Detected 2 of 5 common public security headers. Present: strict-transport-security, content-security-policy. Missing: 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 humanizemy.ai at https://humanizemy.ai.
- 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: 8 rule points lost.
- Evidence: Detected 2 of 5 common public security headers. Present: strict-transport-security, content-security-policy. Missing: 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

medium

Design

Priority 13

Fix rendered layout ergonomics

-9 rule pts

What failed

The browser-rendered page has layout or tap-target issues.

Evidence

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

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.

How to fix it

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 humanizemy.ai at https://humanizemy.ai.
- 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 rule points lost.
- Evidence: Horizontal overflow: 0px. Small tap targets: 72.
- 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.

Score aggregation details

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

84/100

11 pass, 1 fail, 1 unknown

SEO / AEO

Severity mix: 1 critical, 7 high, 3 medium, 1 low.

high

Meta description

-10 rule pts

Meta description is 175 characters.

89/100

5 pass, 1 fail, 0 unknown

Security

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

high

Common security headers

-8 rule pts

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

72/100

6 pass, 2 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), region (1), empty-table-header (1).

medium

Basic contrast

-8 rule pts

3 of 100 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 1.

83/100

9 pass, 2 fail, 0 unknown

Design

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

medium

Text density

-10 rule pts

Detected about 4957 visible word(s).

medium

Rendered layout ergonomics

-9 rule pts

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

Full check list

Failed, unknown, and passed checks are all shown so the report is transparent even when public data is partial.

Showing failed checks.

Failed checks

These checks need attention.

fail

high

SEO / AEO

Meta description

0/10

Meta description is 175 characters.

Failed: earned 0 of 10 points.

Priority: Priority 3: fix before sharing the page publicly.

Why it matters: A missing description makes previews weaker when early users share or find the page.

Fix: Add a meta description around 50 to 170 characters that says who the product helps and what outcome it creates.

Copyable agent prompt

## Role
Act as a focused expert website launch remediation agent for this workflow.
## Inputs
- Primary context: Improve humanizemy.ai at https://humanizemy.ai.
- Fix title: Add a useful meta description.
- Scanner check: Meta description.
- Category: SEO / AEO.
- Status: fail.
- Severity: high.
- Priority: 3; lower numbers are more urgent.
- Score impact: 10 of 10 rule points lost.
- Evidence: Meta description is 175 characters.
- What needs attention: The page does not expose a strong short summary for search and answer engines.
- Why it matters: A missing description makes previews weaker when early users share or find the page.
- 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 a meta description around 50 to 170 characters that says who the product helps and what outcome it creates.
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

Common security headers

10/18

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

Failed: earned 10 of 18 points from partial coverage.

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.

Fix: 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 humanizemy.ai at https://humanizemy.ai.
- 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: 8 of 18 rule points lost.
- Evidence: Detected 2 of 5 common public security headers. Present: strict-transport-security, content-security-policy. Missing: 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

medium

Accessibility

Basic contrast

0/8

3 of 100 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 1.

Failed: earned 0 of 8 points.

Priority: Priority 20: lower-risk cleanup after urgent launch blockers.

Why it matters: Low contrast makes a launch page feel less polished and can exclude users with low vision.

Fix: Review key text, buttons, and links against a 4.5:1 contrast target for normal text.

Copyable agent prompt

## Role
Act as a focused expert website launch remediation agent for this workflow.
## Inputs
- Primary context: Improve humanizemy.ai at https://humanizemy.ai.
- Fix title: Improve detectable color contrast.
- Scanner check: Basic contrast.
- Category: Accessibility.
- Status: fail.
- Severity: medium.
- Priority: 20; lower numbers are more urgent.
- Score impact: 8 of 8 rule points lost.
- Evidence: 3 of 100 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 1.
- What needs attention: The scanner found text/background color pairs that may be hard to read, or could not verify contrast.
- Why it matters: Low contrast makes a launch page feel less polished and can exclude users with low vision.
- 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: Review key text, buttons, and links against a 4.5:1 contrast target for normal text.
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

Rendered axe accessibility violations

0/18

axe found 3 violation rule(s), including 1 serious or critical rule(s). Top rules: color-contrast (2), region (1), empty-table-header (1).

Failed: earned 0 of 18 points.

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.

Fix: 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 humanizemy.ai at https://humanizemy.ai.
- 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 of 18 rule points lost.
- Evidence: axe found 3 violation rule(s), including 1 serious or critical rule(s). Top rules: color-contrast (2), region (1), empty-table-header (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

medium

Design

Text density

0/10

Detected about 4957 visible word(s).

Failed: earned 0 of 10 points.

Priority: Priority 21: lower-risk cleanup after urgent launch blockers.

Why it matters: Too little copy can leave visitors confused; too much copy can bury the value proposition.

Fix: Add concise sections for value, proof, how it works, and next steps, then remove repetitive copy.

Copyable agent prompt

## Role
Act as a focused expert website launch remediation agent for this workflow.
## Inputs
- Primary context: Improve humanizemy.ai at https://humanizemy.ai.
- Fix title: Balance landing page copy.
- Scanner check: Text density.
- Category: Design.
- Status: fail.
- Severity: medium.
- Priority: 21; lower numbers are more urgent.
- Score impact: 10 of 10 rule points lost.
- Evidence: Detected about 4957 visible word(s).
- What needs attention: The page has too little or too much detectable text for a useful launch page.
- Why it matters: Too little copy can leave visitors confused; too much copy can bury the value proposition.
- 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 concise sections for value, proof, how it works, and next steps, then remove repetitive copy.
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

medium

Design

Rendered layout ergonomics

0/9

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

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 humanizemy.ai at https://humanizemy.ai.
- 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: 72.
- 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.

100/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

The canonical resolves to the scanned public URL.

Sitemap coverage and freshness

The exact URL appears in sitemap.xml with lastmod 2026-07-31T20:12:03.684Z.

Structured data

Detected 3 JSON-LD block(s), 0 parse error(s), and types Offer, Organization, Person, SoftwareApplication, WebSite.

Public or paywalled content

No isAccessibleForFree structured-data value was detected.

Entity clarity

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

Answer-ready visible text

Detected 4957 visible words and 90 audience, use-case, pricing, or integration signals.

Authorship and accountability

Detected author or accountable entity: HumanizeMyAI.

Published or updated date

No datePublished or dateModified value was detected in structured data.

Supporting-source links

Detected 5 external source or reference link(s); link quality still requires editorial review.

Rendered content availability

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

Synthetic search-agent reachability

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

Optional LLM-readable summary

https://humanizemy.ai/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 31

Probe: reachable · HTTP 200 · 100% parity

IndexSnippetsSitemapPublic content

Controls: robots meta: index, follow

Vendor documentationDefinition checked 2026-07-30

OpenAIOpenAI model training

GPTBot

OPTED OUT

Model training

Robots: blocked by gptbot disallow: / · line 55

Probe: not tested for this control

IndexSnippetsSitemapPublic content

Controls: robots meta: index, follow

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

Controls: robots meta: index, follow

Vendor documentationDefinition checked 2026-07-30

AnthropicClaude model training

ClaudeBot

OPTED OUT

Model training

Robots: blocked by claudebot disallow: / · line 46

Probe: not tested for this control

IndexSnippetsSitemapPublic content

Controls: robots meta: index, follow

Vendor documentationDefinition checked 2026-07-30

AnthropicClaude search

Claude-SearchBot

PASS · ALLOWED

AI search

Robots: allowed by * allow: / · line 31

Probe: reachable · HTTP 200 · 100% parity

IndexSnippetsSitemapPublic content

Controls: robots meta: index, follow

Vendor documentationDefinition checked 2026-07-30

AnthropicClaude user fetches

Claude-User

PASS · ALLOWED

User-requested fetch

Robots: allowed by * allow: / · line 31

Probe: reachable · HTTP 200 · 100% parity

IndexSnippetsSitemapPublic content

Controls: robots meta: index, follow

Vendor documentationDefinition checked 2026-07-30

GoogleGoogle Search and AI features

Googlebot

PASS · ALLOWED

Search and discovery

Robots: allowed by * allow: / · line 31

Probe: reachable · HTTP 200 · 100% parity

IndexSnippetsSitemapPublic content

Controls: robots meta: index, follow; Googlebot meta: index, follow, max-video-preview:-1, max-image-preview:large, max-snippet:-1

Vendor documentationDefinition checked 2026-07-30

GoogleGemini data use and grounding

Google-Extended

OPTED OUT

Data-use policy control

Robots: blocked by google-extended disallow: / · line 52

Probe: not tested for this control

IndexSnippetsSitemapPublic content

Controls: robots meta: index, follow

Vendor documentationDefinition checked 2026-07-30

MicrosoftBing and Copilot

Bingbot

PASS · ALLOWED

Search and discovery

Robots: allowed by * allow: / · line 31

Probe: reachable · HTTP 200 · 100% parity

IndexSnippetsSitemapPublic content

Controls: robots meta: index, follow

Vendor documentationDefinition checked 2026-07-30

PerplexityPerplexity search

PerplexityBot

PASS · ALLOWED

AI search

Robots: allowed by * allow: / · line 31

Probe: reachable · HTTP 200 · 100% parity

IndexSnippetsSitemapPublic content

Controls: robots meta: index, follow

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

Controls: robots meta: index, follow

Vendor documentationDefinition checked 2026-07-30

AppleSiri, Spotlight, and Safari search

Applebot

PASS · ALLOWED

Search and discovery

Robots: allowed by * allow: / · line 31

Probe: reachable · HTTP 200 · 100% parity

IndexSnippetsSitemapPublic content

Controls: robots meta: index, follow

Vendor documentationDefinition checked 2026-07-30

AppleApple foundation-model training

Applebot-Extended

OPTED OUT

Data-use policy control

Robots: blocked by applebot-extended disallow: / · line 37

Probe: not tested for this control

IndexSnippetsSitemapPublic content

Controls: robots meta: index, follow

Vendor documentationDefinition checked 2026-07-30

Mistral AIMistral search

MistralAI-Index

PASS · ALLOWED

AI search

Robots: allowed by * allow: / · line 31

Probe: reachable · HTTP 200 · 100% parity

IndexSnippetsSitemapPublic content

Controls: robots meta: index, follow

Vendor documentationDefinition checked 2026-07-30

Mistral AIMistral user fetches

MistralAI-User

PASS · ALLOWED

User-requested fetch

Robots: allowed by * allow: / · line 31

Probe: reachable · HTTP 200 · 100% parity

IndexSnippetsSitemapPublic content

Controls: robots meta: index, follow

Vendor documentationDefinition checked 2026-07-30

MetaMeta AI model and product data

meta-externalagent

OPTED OUT

Model training

Robots: blocked by meta-externalagent disallow: / · line 58

Probe: not tested for this control

IndexSnippetsSitemapPublic content

Controls: robots meta: index, follow

Vendor documentationDefinition checked 2026-07-30

MetaMeta AI user fetches

meta-externalfetcher

PASS · ALLOWED

User-requested fetch

Robots: allowed by * allow: / · line 31

Probe: reachable · HTTP 200 · 100% parity

IndexSnippetsSitemapPublic content

Controls: robots meta: index, follow

Vendor documentationDefinition checked 2026-07-30

AmazonAmazon model training

Amazonbot

OPTED OUT

Model training

Robots: blocked by amazonbot disallow: / · line 34

Probe: not tested for this control

IndexSnippetsSitemapPublic content

Controls: robots meta: index, follow

Vendor documentationDefinition checked 2026-07-30

AmazonAlexa and Rufus search

Amzn-SearchBot

PASS · ALLOWED

AI search

Robots: allowed by * allow: / · line 31

Probe: reachable · HTTP 200 · 100% parity

IndexSnippetsSitemapPublic content

Controls: robots meta: index, follow

Vendor documentationDefinition checked 2026-07-30

AmazonAlexa user fetches

Amzn-User

PASS · ALLOWED

User-requested fetch

Robots: allowed by * allow: / · line 31

Probe: reachable · HTTP 200 · 100% parity

IndexSnippetsSitemapPublic content

Controls: robots meta: index, follow

Vendor documentationDefinition checked 2026-07-30

Common CrawlOpen web datasets

CCBot

OPTED OUT

Model training

Robots: blocked by ccbot disallow: / · line 43

Probe: not tested for this control

IndexSnippetsSitemapPublic content

Controls: robots meta: index, follow

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

humanizemy.ai website audit report

Close to ready: 82/100 overall, with prioritized fixes for SEO, security, accessibility, and design.

Public report link

Markdown report

# humanizemy.ai Website Scan

Scanned URL: [https://humanizemy.ai](https://humanizemy.ai)
Report URL: /scan/humanizemy-ai-82-launch-readiness-report-48b15ec7
Created: 2026-07-31T20:14:17.340Z

## Score Summary

- Overall: 82/100
- SEO / AEO: 84/100
- Security: 89/100
- Accessibility: 72/100
- Design: 83/100

## Launch Readiness

Close to ready (Needs polish).

Passed: 31. Failed: 6. Unknown: 1.
Strongest area: Security. Weakest area: Accessibility.

## 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 31. Synthetic User-Agent probe returned HTTP 200 with 100% sampled-content parity. Relevant page controls: robots meta: index, follow.
- **OpenAI — OpenAI model training** (GPTBot): PREFERENCE — robots blocked; synthetic probe not_tested. Blocked by gptbot disallow: / on line 55. No synthetic fetch is appropriate for this policy or training control. Relevant page controls: robots meta: index, follow.
- **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. Relevant page controls: robots meta: index, follow.
- **Anthropic — Claude model training** (ClaudeBot): PREFERENCE — robots blocked; synthetic probe not_tested. Blocked by claudebot disallow: / on line 46. No synthetic fetch is appropriate for this policy or training control. Relevant page controls: robots meta: index, follow.
- **Anthropic — Claude search** (Claude-SearchBot): PASS — robots allowed; synthetic probe reachable (HTTP 200). Allowed by * allow: / on line 31. Synthetic User-Agent probe returned HTTP 200 with 100% sampled-content parity. Relevant page controls: robots meta: index, follow.
- **Anthropic — Claude user fetches** (Claude-User): PASS — robots allowed; synthetic probe reachable (HTTP 200). Allowed by * allow: / on line 31. Synthetic User-Agent probe returned HTTP 200 with 100% sampled-content parity. Relevant page controls: robots meta: index, follow.
- **Google — Google Search and AI features** (Googlebot): PASS — robots allowed; synthetic probe reachable (HTTP 200). Allowed by * allow: / on line 31. Synthetic User-Agent probe returned HTTP 200 with 100% sampled-content parity. Relevant page controls: robots meta: index, follow; Googlebot meta: index, follow, max-video-preview:-1, max-image-preview:large, max-snippet:-1.
- **Google — Gemini data use and grounding** (Google-Extended): PREFERENCE — robots blocked; synthetic probe not_tested. Blocked by google-extended disallow: / on line 52. No synthetic fetch is appropriate for this policy or training control. Relevant page controls: robots meta: index, follow.
- **Microsoft — Bing and Copilot** (Bingbot): PASS — robots allowed; synthetic probe reachable (HTTP 200). Allowed by * allow: / on line 31. Synthetic User-Agent probe returned HTTP 200 with 100% sampled-content parity. Relevant page controls: robots meta: index, follow.
- **Perplexity — Perplexity search** (PerplexityBot): PASS — robots allowed; synthetic probe reachable (HTTP 200). Allowed by * allow: / on line 31. Synthetic User-Agent probe returned HTTP 200 with 100% sampled-content parity. Relevant page controls: robots meta: index, follow.
- **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. Relevant page controls: robots meta: index, follow.
- **Apple — Siri, Spotlight, and Safari search** (Applebot): PASS — robots allowed; synthetic probe reachable (HTTP 200). Allowed by * allow: / on line 31. Synthetic User-Agent probe returned HTTP 200 with 100% sampled-content parity. Relevant page controls: robots meta: index, follow.
- **Apple — Apple foundation-model training** (Applebot-Extended): PREFERENCE — robots blocked; synthetic probe not_tested. Blocked by applebot-extended disallow: / on line 37. No synthetic fetch is appropriate for this policy or training control. Relevant page controls: robots meta: index, follow.
- **Mistral AI — Mistral search** (MistralAI-Index): PASS — robots allowed; synthetic probe reachable (HTTP 200). Allowed by * allow: / on line 31. Synthetic User-Agent probe returned HTTP 200 with 100% sampled-content parity. Relevant page controls: robots meta: index, follow.
- **Mistral AI — Mistral user fetches** (MistralAI-User): PASS — robots allowed; synthetic probe reachable (HTTP 200). Allowed by * allow: / on line 31. Synthetic User-Agent probe returned HTTP 200 with 100% sampled-content parity. Relevant page controls: robots meta: index, follow.
- **Meta — Meta AI model and product data** (meta-externalagent): PREFERENCE — robots blocked; synthetic probe not_tested. Blocked by meta-externalagent disallow: / on line 58. No synthetic fetch is appropriate for this policy or training control. Relevant page controls: robots meta: index, follow.
- **Meta — Meta AI user fetches** (meta-externalfetcher): PASS — robots allowed; synthetic probe reachable (HTTP 200). Allowed by * allow: / on line 31. Synthetic User-Agent probe returned HTTP 200 with 100% sampled-content parity. Relevant page controls: robots meta: index, follow.
- **Amazon — Amazon model training** (Amazonbot): PREFERENCE — robots blocked; synthetic probe not_tested. Blocked by amazonbot disallow: / on line 34. No synthetic fetch is appropriate for this policy or training control. Relevant page controls: robots meta: index, follow.
- **Amazon — Alexa and Rufus search** (Amzn-SearchBot): PASS — robots allowed; synthetic probe reachable (HTTP 200). Allowed by * allow: / on line 31. Synthetic User-Agent probe returned HTTP 200 with 100% sampled-content parity. Relevant page controls: robots meta: index, follow.
- **Amazon — Alexa user fetches** (Amzn-User): PASS — robots allowed; synthetic probe reachable (HTTP 200). Allowed by * allow: / on line 31. Synthetic User-Agent probe returned HTTP 200 with 100% sampled-content parity. Relevant page controls: robots meta: index, follow.
- **Common Crawl — Open web datasets** (CCBot): PREFERENCE — robots blocked; synthetic probe not_tested. Blocked by ccbot disallow: / on line 43. No synthetic fetch is appropriate for this policy or training control. Relevant page controls: robots meta: index, follow.

## Page-level AEO Readiness

Readiness: 100/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**: PASS — The canonical resolves to the scanned public URL.
- **Sitemap coverage and freshness**: PASS — The exact URL appears in sitemap.xml with lastmod 2026-07-31T20:12:03.684Z.
- **Structured data**: PASS — Detected 3 JSON-LD block(s), 0 parse error(s), and types Offer, Organization, Person, SoftwareApplication, WebSite.
- **Public or paywalled content**: UNKNOWN — No isAccessibleForFree structured-data value was detected.
- **Entity clarity**: PASS — Detected 3 of 3 core identity signals across the title, description, and H1.
- **Answer-ready visible text**: PASS — Detected 4957 visible words and 90 audience, use-case, pricing, or integration signals.
- **Authorship and accountability**: PASS — Detected author or accountable entity: HumanizeMyAI.
- **Published or updated date**: UNKNOWN — No datePublished or dateModified value was detected in structured data.
- **Supporting-source links**: PASS — Detected 5 external source or reference link(s); link quality still requires editorial review.
- **Rendered content availability**: PASS — Rendered audit completed with 629 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://humanizemy.ai/llms.txt returned HTTP 200; this is supplemental and does not determine AI-search eligibility.

## Prioritized Fixes

### 1. 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. GPTBot, ClaudeBot, Google-Extended, and 4 more are explicit training or data-use opt-outs and do not reduce the AEO score. AEO crawler readiness is 100%: discovery 45/45, index and snippet eligibility 25/25, synthetic reachability 20/20, sitemap freshness 10/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.

### 2. 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), region (1), empty-table-header (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.

### 3. Add a useful meta description

- Category: SEO / AEO
- Status: fail
- Severity: high
- Rule points lost: 10
- Evidence: Meta description is 175 characters.
- Why it matters: A missing description makes previews weaker when early users share or find the page.
- Fix: Add a meta description around 50 to 170 characters that says who the product helps and what outcome it creates.

### 4. Add common public security headers

- Category: Security
- Status: fail
- Severity: high
- Rule points lost: 8
- Evidence: Detected 2 of 5 common public security headers. Present: strict-transport-security, content-security-policy. Missing: 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.

### 5. Fix rendered layout ergonomics

- Category: Design
- Status: fail
- Severity: medium
- Rule points lost: 9
- Evidence: Horizontal overflow: 0px. Small tap targets: 72.
- 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.

## Opportunities

### Tighten the live color system

- Impact: high
- Category: Accessibility
- Evidence: 3 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: 72.
- 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: 4957. H1 count: 1. Audience signals: 71. CTA labels: Get started, Try sample.
- 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: Humanize AI Text for SEO & Content Marketing · HumanizeMyAI. H1: Humanize AI Text in   One Click. Schema types: Offer, Organization, Person, SoftwareApplication, WebSite.
- 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.

### Structured data is present

- Category: SEO / AEO
- Evidence: JSON-LD blocks: 3. Types: Offer, Organization, Person, SoftwareApplication, WebSite. Parse errors: 0.
- Interpretation: The page exposes machine-readable facts, but quality still depends on whether those facts match visible content.
- Recommended use: Validate JSON-LD and use only accurate facts that are visible or clearly supported on the public page.

### Weakest score area

- Category: Accessibility
- Evidence: SEO / AEO: 84/100. Security: 89/100. Accessibility: 72/100. Design: 83/100
- Interpretation: The weakest area is Accessibility, 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://humanizemy.ai/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: 3. Console errors: 0. 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: 723ms. Load complete: 723ms. First contentful paint: 664ms. Resources: 31. Scripts: 14. Images: 2. Third-party origins: 1. 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, region, empty-table-header.
- 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 humanizemy.ai 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

38 checks

Website audit scorecard for humanizemy.ai

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

Submitted

https://humanizemy.ai/

Final URL

https://humanizemy.ai

Created

Jul 31, 2026, 8:14 PM

Safe fetch

106 ms

Four-score result

Close to ready (Needs polish): 31 passed, 6 failed, and 1 unknown. Strongest area: Security. Weakest area: Accessibility.

Overall

out of 100

SEO / AEO

out of 100

93/111 rule points

Security

out of 100

68/76 rule points

Accessibility

out of 100

68/94 rule points

Design

out of 100

91/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 / AEO93/111

Security68/76

Accessibility68/94

Design91/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), region (1), empty-table-header (1).

high

SEO / AEO

Meta description

Meta description is 175 characters.

medium

Design

Text density

Detected about 4957 visible word(s).

medium

Design

Rendered layout ergonomics

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

Recommendations

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

5 fixes

3 opportunities

9 insights

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 humanizemy.ai at https://humanizemy.ai.
- 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. GPTBot, ClaudeBot, Google-Extended, and 4 more are explicit training or data-use opt-outs and do not reduce the AEO score. AEO crawler readiness is 100%: discovery 45/45, index and snippet eligibility 25/25, synthetic reachability 20/20, sitemap freshness 10/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

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), region (1), empty-table-header (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 humanizemy.ai at https://humanizemy.ai.
- 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), region (1), empty-table-header (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

SEO / AEO

Priority 3

Add a useful meta description

-10 rule pts

What failed

The page does not expose a strong short summary for search and answer engines.

Evidence

Meta description is 175 characters.

Priority

Priority 3: fix before sharing the page publicly.

Why it matters

A missing description makes previews weaker when early users share or find the page.

How to fix it

Add a meta description around 50 to 170 characters that says who the product helps and what outcome it creates.

Copyable agent prompt

## Role
Act as a focused expert website launch remediation agent for this workflow.
## Inputs
- Primary context: Improve humanizemy.ai at https://humanizemy.ai.
- Fix title: Add a useful meta description.
- Scanner check: Meta description.
- Category: SEO / AEO.
- Status: fail.
- Severity: high.
- Priority: 3; lower numbers are more urgent.
- Score impact: 10 rule points lost.
- Evidence: Meta description is 175 characters.
- What needs attention: The page does not expose a strong short summary for search and answer engines.
- Why it matters: A missing description makes previews weaker when early users share or find the page.
- 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 a meta description around 50 to 170 characters that says who the product helps and what outcome it creates.
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

-8 rule pts

What failed

Several basic browser protection headers were not visible.

Evidence

Detected 2 of 5 common public security headers. Present: strict-transport-security, content-security-policy. Missing: 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 humanizemy.ai at https://humanizemy.ai.
- 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: 8 rule points lost.
- Evidence: Detected 2 of 5 common public security headers. Present: strict-transport-security, content-security-policy. Missing: 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

medium

Design

Priority 13

Fix rendered layout ergonomics

-9 rule pts

What failed

The browser-rendered page has layout or tap-target issues.

Evidence

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

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.

How to fix it

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 humanizemy.ai at https://humanizemy.ai.
- 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 rule points lost.
- Evidence: Horizontal overflow: 0px. Small tap targets: 72.
- 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.

Score aggregation details

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

84/100

11 pass, 1 fail, 1 unknown

SEO / AEO

Severity mix: 1 critical, 7 high, 3 medium, 1 low.

high

Meta description

-10 rule pts

Meta description is 175 characters.

89/100

5 pass, 1 fail, 0 unknown

Security

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

high

Common security headers

-8 rule pts

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

72/100

6 pass, 2 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), region (1), empty-table-header (1).

medium

Basic contrast

-8 rule pts

3 of 100 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 1.

83/100

9 pass, 2 fail, 0 unknown

Design

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

medium

Text density

-10 rule pts

Detected about 4957 visible word(s).

medium

Rendered layout ergonomics

-9 rule pts

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

Full check list

Failed, unknown, and passed checks are all shown so the report is transparent even when public data is partial.

Showing failed checks.

Failed checks

These checks need attention.

fail

high

SEO / AEO

Meta description

0/10

Meta description is 175 characters.

Failed: earned 0 of 10 points.

Priority: Priority 3: fix before sharing the page publicly.

Why it matters: A missing description makes previews weaker when early users share or find the page.

Fix: Add a meta description around 50 to 170 characters that says who the product helps and what outcome it creates.

Copyable agent prompt

## Role
Act as a focused expert website launch remediation agent for this workflow.
## Inputs
- Primary context: Improve humanizemy.ai at https://humanizemy.ai.
- Fix title: Add a useful meta description.
- Scanner check: Meta description.
- Category: SEO / AEO.
- Status: fail.
- Severity: high.
- Priority: 3; lower numbers are more urgent.
- Score impact: 10 of 10 rule points lost.
- Evidence: Meta description is 175 characters.
- What needs attention: The page does not expose a strong short summary for search and answer engines.
- Why it matters: A missing description makes previews weaker when early users share or find the page.
- 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 a meta description around 50 to 170 characters that says who the product helps and what outcome it creates.
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

Common security headers

10/18

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

Failed: earned 10 of 18 points from partial coverage.

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.

Fix: 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 humanizemy.ai at https://humanizemy.ai.
- 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: 8 of 18 rule points lost.
- Evidence: Detected 2 of 5 common public security headers. Present: strict-transport-security, content-security-policy. Missing: 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

medium

Accessibility

Basic contrast

0/8

3 of 100 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 1.

Failed: earned 0 of 8 points.

Priority: Priority 20: lower-risk cleanup after urgent launch blockers.

Why it matters: Low contrast makes a launch page feel less polished and can exclude users with low vision.

Fix: Review key text, buttons, and links against a 4.5:1 contrast target for normal text.

Copyable agent prompt

## Role
Act as a focused expert website launch remediation agent for this workflow.
## Inputs
- Primary context: Improve humanizemy.ai at https://humanizemy.ai.
- Fix title: Improve detectable color contrast.
- Scanner check: Basic contrast.
- Category: Accessibility.
- Status: fail.
- Severity: medium.
- Priority: 20; lower numbers are more urgent.
- Score impact: 8 of 8 rule points lost.
- Evidence: 3 of 100 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 1.
- What needs attention: The scanner found text/background color pairs that may be hard to read, or could not verify contrast.
- Why it matters: Low contrast makes a launch page feel less polished and can exclude users with low vision.
- 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: Review key text, buttons, and links against a 4.5:1 contrast target for normal text.
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

Rendered axe accessibility violations

0/18

axe found 3 violation rule(s), including 1 serious or critical rule(s). Top rules: color-contrast (2), region (1), empty-table-header (1).

Failed: earned 0 of 18 points.

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.

Fix: 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 humanizemy.ai at https://humanizemy.ai.
- 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 of 18 rule points lost.
- Evidence: axe found 3 violation rule(s), including 1 serious or critical rule(s). Top rules: color-contrast (2), region (1), empty-table-header (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

medium

Design

Text density

0/10

Detected about 4957 visible word(s).

Failed: earned 0 of 10 points.

Priority: Priority 21: lower-risk cleanup after urgent launch blockers.

Why it matters: Too little copy can leave visitors confused; too much copy can bury the value proposition.

Fix: Add concise sections for value, proof, how it works, and next steps, then remove repetitive copy.

Copyable agent prompt

## Role
Act as a focused expert website launch remediation agent for this workflow.
## Inputs
- Primary context: Improve humanizemy.ai at https://humanizemy.ai.
- Fix title: Balance landing page copy.
- Scanner check: Text density.
- Category: Design.
- Status: fail.
- Severity: medium.
- Priority: 21; lower numbers are more urgent.
- Score impact: 10 of 10 rule points lost.
- Evidence: Detected about 4957 visible word(s).
- What needs attention: The page has too little or too much detectable text for a useful launch page.
- Why it matters: Too little copy can leave visitors confused; too much copy can bury the value proposition.
- 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 concise sections for value, proof, how it works, and next steps, then remove repetitive copy.
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

medium

Design

Rendered layout ergonomics

0/9

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

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 humanizemy.ai at https://humanizemy.ai.
- 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: 72.
- 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.

100/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

The canonical resolves to the scanned public URL.

Sitemap coverage and freshness

The exact URL appears in sitemap.xml with lastmod 2026-07-31T20:12:03.684Z.

Structured data

Detected 3 JSON-LD block(s), 0 parse error(s), and types Offer, Organization, Person, SoftwareApplication, WebSite.

Public or paywalled content

No isAccessibleForFree structured-data value was detected.

Entity clarity

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

Answer-ready visible text

Detected 4957 visible words and 90 audience, use-case, pricing, or integration signals.

Authorship and accountability

Detected author or accountable entity: HumanizeMyAI.

Published or updated date

No datePublished or dateModified value was detected in structured data.

Supporting-source links

Detected 5 external source or reference link(s); link quality still requires editorial review.

Rendered content availability

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

Synthetic search-agent reachability

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

Optional LLM-readable summary

https://humanizemy.ai/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 31

Probe: reachable · HTTP 200 · 100% parity

IndexSnippetsSitemapPublic content

Controls: robots meta: index, follow

Vendor documentationDefinition checked 2026-07-30

OpenAIOpenAI model training

GPTBot

OPTED OUT

Model training

Robots: blocked by gptbot disallow: / · line 55

Probe: not tested for this control

IndexSnippetsSitemapPublic content

Controls: robots meta: index, follow

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

Controls: robots meta: index, follow

Vendor documentationDefinition checked 2026-07-30

AnthropicClaude model training

ClaudeBot

OPTED OUT

Model training

Robots: blocked by claudebot disallow: / · line 46

Probe: not tested for this control

IndexSnippetsSitemapPublic content

Controls: robots meta: index, follow

Vendor documentationDefinition checked 2026-07-30

AnthropicClaude search

Claude-SearchBot

PASS · ALLOWED

AI search

Robots: allowed by * allow: / · line 31

Probe: reachable · HTTP 200 · 100% parity

IndexSnippetsSitemapPublic content

Controls: robots meta: index, follow

Vendor documentationDefinition checked 2026-07-30

AnthropicClaude user fetches

Claude-User

PASS · ALLOWED

User-requested fetch

Robots: allowed by * allow: / · line 31

Probe: reachable · HTTP 200 · 100% parity

IndexSnippetsSitemapPublic content

Controls: robots meta: index, follow

Vendor documentationDefinition checked 2026-07-30

GoogleGoogle Search and AI features

Googlebot

PASS · ALLOWED

Search and discovery

Robots: allowed by * allow: / · line 31

Probe: reachable · HTTP 200 · 100% parity

IndexSnippetsSitemapPublic content

Controls: robots meta: index, follow; Googlebot meta: index, follow, max-video-preview:-1, max-image-preview:large, max-snippet:-1

Vendor documentationDefinition checked 2026-07-30

GoogleGemini data use and grounding

Google-Extended

OPTED OUT

Data-use policy control

Robots: blocked by google-extended disallow: / · line 52

Probe: not tested for this control

IndexSnippetsSitemapPublic content

Controls: robots meta: index, follow

Vendor documentationDefinition checked 2026-07-30

MicrosoftBing and Copilot

Bingbot

PASS · ALLOWED

Search and discovery

Robots: allowed by * allow: / · line 31

Probe: reachable · HTTP 200 · 100% parity

IndexSnippetsSitemapPublic content

Controls: robots meta: index, follow

Vendor documentationDefinition checked 2026-07-30

PerplexityPerplexity search

PerplexityBot

PASS · ALLOWED

AI search

Robots: allowed by * allow: / · line 31

Probe: reachable · HTTP 200 · 100% parity

IndexSnippetsSitemapPublic content

Controls: robots meta: index, follow

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

Controls: robots meta: index, follow

Vendor documentationDefinition checked 2026-07-30

AppleSiri, Spotlight, and Safari search

Applebot

PASS · ALLOWED

Search and discovery

Robots: allowed by * allow: / · line 31

Probe: reachable · HTTP 200 · 100% parity

IndexSnippetsSitemapPublic content

Controls: robots meta: index, follow

Vendor documentationDefinition checked 2026-07-30

AppleApple foundation-model training

Applebot-Extended

OPTED OUT

Data-use policy control

Robots: blocked by applebot-extended disallow: / · line 37

Probe: not tested for this control

IndexSnippetsSitemapPublic content

Controls: robots meta: index, follow

Vendor documentationDefinition checked 2026-07-30

Mistral AIMistral search

MistralAI-Index

PASS · ALLOWED

AI search

Robots: allowed by * allow: / · line 31

Probe: reachable · HTTP 200 · 100% parity

IndexSnippetsSitemapPublic content

Controls: robots meta: index, follow

Vendor documentationDefinition checked 2026-07-30

Mistral AIMistral user fetches

MistralAI-User

PASS · ALLOWED

User-requested fetch

Robots: allowed by * allow: / · line 31

Probe: reachable · HTTP 200 · 100% parity

IndexSnippetsSitemapPublic content

Controls: robots meta: index, follow

Vendor documentationDefinition checked 2026-07-30

MetaMeta AI model and product data

meta-externalagent

OPTED OUT

Model training

Robots: blocked by meta-externalagent disallow: / · line 58

Probe: not tested for this control

IndexSnippetsSitemapPublic content

Controls: robots meta: index, follow

Vendor documentationDefinition checked 2026-07-30

MetaMeta AI user fetches

meta-externalfetcher

PASS · ALLOWED

User-requested fetch

Robots: allowed by * allow: / · line 31

Probe: reachable · HTTP 200 · 100% parity

IndexSnippetsSitemapPublic content

Controls: robots meta: index, follow

Vendor documentationDefinition checked 2026-07-30

AmazonAmazon model training

Amazonbot

OPTED OUT

Model training

Robots: blocked by amazonbot disallow: / · line 34

Probe: not tested for this control

IndexSnippetsSitemapPublic content

Controls: robots meta: index, follow

Vendor documentationDefinition checked 2026-07-30

AmazonAlexa and Rufus search

Amzn-SearchBot

PASS · ALLOWED

AI search

Robots: allowed by * allow: / · line 31

Probe: reachable · HTTP 200 · 100% parity

IndexSnippetsSitemapPublic content

Controls: robots meta: index, follow

Vendor documentationDefinition checked 2026-07-30

AmazonAlexa user fetches

Amzn-User

PASS · ALLOWED

User-requested fetch

Robots: allowed by * allow: / · line 31

Probe: reachable · HTTP 200 · 100% parity

IndexSnippetsSitemapPublic content

Controls: robots meta: index, follow

Vendor documentationDefinition checked 2026-07-30

Common CrawlOpen web datasets

CCBot

OPTED OUT

Model training

Robots: blocked by ccbot disallow: / · line 43

Probe: not tested for this control

IndexSnippetsSitemapPublic content

Controls: robots meta: index, follow

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

humanizemy.ai website audit report

Close to ready: 82/100 overall, with prioritized fixes for SEO, security, accessibility, and design.

Public report link

Markdown report

# humanizemy.ai Website Scan

Scanned URL: [https://humanizemy.ai](https://humanizemy.ai)
Report URL: /scan/humanizemy-ai-82-launch-readiness-report-48b15ec7
Created: 2026-07-31T20:14:17.340Z

## Score Summary

- Overall: 82/100
- SEO / AEO: 84/100
- Security: 89/100
- Accessibility: 72/100
- Design: 83/100

## Launch Readiness

Close to ready (Needs polish).

Passed: 31. Failed: 6. Unknown: 1.
Strongest area: Security. Weakest area: Accessibility.

## 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 31. Synthetic User-Agent probe returned HTTP 200 with 100% sampled-content parity. Relevant page controls: robots meta: index, follow.
- **OpenAI — OpenAI model training** (GPTBot): PREFERENCE — robots blocked; synthetic probe not_tested. Blocked by gptbot disallow: / on line 55. No synthetic fetch is appropriate for this policy or training control. Relevant page controls: robots meta: index, follow.
- **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. Relevant page controls: robots meta: index, follow.
- **Anthropic — Claude model training** (ClaudeBot): PREFERENCE — robots blocked; synthetic probe not_tested. Blocked by claudebot disallow: / on line 46. No synthetic fetch is appropriate for this policy or training control. Relevant page controls: robots meta: index, follow.
- **Anthropic — Claude search** (Claude-SearchBot): PASS — robots allowed; synthetic probe reachable (HTTP 200). Allowed by * allow: / on line 31. Synthetic User-Agent probe returned HTTP 200 with 100% sampled-content parity. Relevant page controls: robots meta: index, follow.
- **Anthropic — Claude user fetches** (Claude-User): PASS — robots allowed; synthetic probe reachable (HTTP 200). Allowed by * allow: / on line 31. Synthetic User-Agent probe returned HTTP 200 with 100% sampled-content parity. Relevant page controls: robots meta: index, follow.
- **Google — Google Search and AI features** (Googlebot): PASS — robots allowed; synthetic probe reachable (HTTP 200). Allowed by * allow: / on line 31. Synthetic User-Agent probe returned HTTP 200 with 100% sampled-content parity. Relevant page controls: robots meta: index, follow; Googlebot meta: index, follow, max-video-preview:-1, max-image-preview:large, max-snippet:-1.
- **Google — Gemini data use and grounding** (Google-Extended): PREFERENCE — robots blocked; synthetic probe not_tested. Blocked by google-extended disallow: / on line 52. No synthetic fetch is appropriate for this policy or training control. Relevant page controls: robots meta: index, follow.
- **Microsoft — Bing and Copilot** (Bingbot): PASS — robots allowed; synthetic probe reachable (HTTP 200). Allowed by * allow: / on line 31. Synthetic User-Agent probe returned HTTP 200 with 100% sampled-content parity. Relevant page controls: robots meta: index, follow.
- **Perplexity — Perplexity search** (PerplexityBot): PASS — robots allowed; synthetic probe reachable (HTTP 200). Allowed by * allow: / on line 31. Synthetic User-Agent probe returned HTTP 200 with 100% sampled-content parity. Relevant page controls: robots meta: index, follow.
- **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. Relevant page controls: robots meta: index, follow.
- **Apple — Siri, Spotlight, and Safari search** (Applebot): PASS — robots allowed; synthetic probe reachable (HTTP 200). Allowed by * allow: / on line 31. Synthetic User-Agent probe returned HTTP 200 with 100% sampled-content parity. Relevant page controls: robots meta: index, follow.
- **Apple — Apple foundation-model training** (Applebot-Extended): PREFERENCE — robots blocked; synthetic probe not_tested. Blocked by applebot-extended disallow: / on line 37. No synthetic fetch is appropriate for this policy or training control. Relevant page controls: robots meta: index, follow.
- **Mistral AI — Mistral search** (MistralAI-Index): PASS — robots allowed; synthetic probe reachable (HTTP 200). Allowed by * allow: / on line 31. Synthetic User-Agent probe returned HTTP 200 with 100% sampled-content parity. Relevant page controls: robots meta: index, follow.
- **Mistral AI — Mistral user fetches** (MistralAI-User): PASS — robots allowed; synthetic probe reachable (HTTP 200). Allowed by * allow: / on line 31. Synthetic User-Agent probe returned HTTP 200 with 100% sampled-content parity. Relevant page controls: robots meta: index, follow.
- **Meta — Meta AI model and product data** (meta-externalagent): PREFERENCE — robots blocked; synthetic probe not_tested. Blocked by meta-externalagent disallow: / on line 58. No synthetic fetch is appropriate for this policy or training control. Relevant page controls: robots meta: index, follow.
- **Meta — Meta AI user fetches** (meta-externalfetcher): PASS — robots allowed; synthetic probe reachable (HTTP 200). Allowed by * allow: / on line 31. Synthetic User-Agent probe returned HTTP 200 with 100% sampled-content parity. Relevant page controls: robots meta: index, follow.
- **Amazon — Amazon model training** (Amazonbot): PREFERENCE — robots blocked; synthetic probe not_tested. Blocked by amazonbot disallow: / on line 34. No synthetic fetch is appropriate for this policy or training control. Relevant page controls: robots meta: index, follow.
- **Amazon — Alexa and Rufus search** (Amzn-SearchBot): PASS — robots allowed; synthetic probe reachable (HTTP 200). Allowed by * allow: / on line 31. Synthetic User-Agent probe returned HTTP 200 with 100% sampled-content parity. Relevant page controls: robots meta: index, follow.
- **Amazon — Alexa user fetches** (Amzn-User): PASS — robots allowed; synthetic probe reachable (HTTP 200). Allowed by * allow: / on line 31. Synthetic User-Agent probe returned HTTP 200 with 100% sampled-content parity. Relevant page controls: robots meta: index, follow.
- **Common Crawl — Open web datasets** (CCBot): PREFERENCE — robots blocked; synthetic probe not_tested. Blocked by ccbot disallow: / on line 43. No synthetic fetch is appropriate for this policy or training control. Relevant page controls: robots meta: index, follow.

## Page-level AEO Readiness

Readiness: 100/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**: PASS — The canonical resolves to the scanned public URL.
- **Sitemap coverage and freshness**: PASS — The exact URL appears in sitemap.xml with lastmod 2026-07-31T20:12:03.684Z.
- **Structured data**: PASS — Detected 3 JSON-LD block(s), 0 parse error(s), and types Offer, Organization, Person, SoftwareApplication, WebSite.
- **Public or paywalled content**: UNKNOWN — No isAccessibleForFree structured-data value was detected.
- **Entity clarity**: PASS — Detected 3 of 3 core identity signals across the title, description, and H1.
- **Answer-ready visible text**: PASS — Detected 4957 visible words and 90 audience, use-case, pricing, or integration signals.
- **Authorship and accountability**: PASS — Detected author or accountable entity: HumanizeMyAI.
- **Published or updated date**: UNKNOWN — No datePublished or dateModified value was detected in structured data.
- **Supporting-source links**: PASS — Detected 5 external source or reference link(s); link quality still requires editorial review.
- **Rendered content availability**: PASS — Rendered audit completed with 629 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://humanizemy.ai/llms.txt returned HTTP 200; this is supplemental and does not determine AI-search eligibility.

## Prioritized Fixes

### 1. 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. GPTBot, ClaudeBot, Google-Extended, and 4 more are explicit training or data-use opt-outs and do not reduce the AEO score. AEO crawler readiness is 100%: discovery 45/45, index and snippet eligibility 25/25, synthetic reachability 20/20, sitemap freshness 10/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.

### 2. 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), region (1), empty-table-header (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.

### 3. Add a useful meta description

- Category: SEO / AEO
- Status: fail
- Severity: high
- Rule points lost: 10
- Evidence: Meta description is 175 characters.
- Why it matters: A missing description makes previews weaker when early users share or find the page.
- Fix: Add a meta description around 50 to 170 characters that says who the product helps and what outcome it creates.

### 4. Add common public security headers

- Category: Security
- Status: fail
- Severity: high
- Rule points lost: 8
- Evidence: Detected 2 of 5 common public security headers. Present: strict-transport-security, content-security-policy. Missing: 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.

### 5. Fix rendered layout ergonomics

- Category: Design
- Status: fail
- Severity: medium
- Rule points lost: 9
- Evidence: Horizontal overflow: 0px. Small tap targets: 72.
- 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.

## Opportunities

### Tighten the live color system

- Impact: high
- Category: Accessibility
- Evidence: 3 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: 72.
- 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: 4957. H1 count: 1. Audience signals: 71. CTA labels: Get started, Try sample.
- 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: Humanize AI Text for SEO & Content Marketing · HumanizeMyAI. H1: Humanize AI Text in   One Click. Schema types: Offer, Organization, Person, SoftwareApplication, WebSite.
- 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.

### Structured data is present

- Category: SEO / AEO
- Evidence: JSON-LD blocks: 3. Types: Offer, Organization, Person, SoftwareApplication, WebSite. Parse errors: 0.
- Interpretation: The page exposes machine-readable facts, but quality still depends on whether those facts match visible content.
- Recommended use: Validate JSON-LD and use only accurate facts that are visible or clearly supported on the public page.

### Weakest score area

- Category: Accessibility
- Evidence: SEO / AEO: 84/100. Security: 89/100. Accessibility: 72/100. Design: 83/100
- Interpretation: The weakest area is Accessibility, 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://humanizemy.ai/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: 3. Console errors: 0. 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: 723ms. Load complete: 723ms. First contentful paint: 664ms. Resources: 31. Scripts: 14. Images: 2. Third-party origins: 1. 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, region, empty-table-header.
- 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 humanizemy.ai without re-entering the URL. The previous report stays saved so the next result can be compared against it.

Website audit scorecard for humanizemy.ai

Improve AI search and crawler readiness

Copyable agent prompt

Fix rendered axe accessibility violations

Copyable agent prompt

Add a useful meta description

Copyable agent prompt

Add common public security headers

Copyable agent prompt

Fix rendered layout ergonomics

Copyable agent prompt

SEO / AEO

Meta description

Security

Common security headers

Accessibility

Rendered axe accessibility violations

Basic contrast

Design

Text density

Rendered layout ergonomics

Failed checks

Meta description

Copyable agent prompt

Common security headers

Copyable agent prompt

Basic contrast

Copyable agent prompt

Rendered axe accessibility violations

Copyable agent prompt

Text density

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 humanizemy.ai

Improve AI search and crawler readiness

Copyable agent prompt

Fix rendered axe accessibility violations

Copyable agent prompt

Add a useful meta description

Copyable agent prompt

Add common public security headers

Copyable agent prompt

Fix rendered layout ergonomics

Copyable agent prompt

SEO / AEO

Meta description

Security

Common security headers

Accessibility

Rendered axe accessibility violations

Basic contrast

Design

Text density

Rendered layout ergonomics

Failed checks

Meta description

Copyable agent prompt

Common security headers

Copyable agent prompt

Basic contrast

Copyable agent prompt

Rendered axe accessibility violations

Copyable agent prompt

Text density

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.