completed

HTTP 403

1 redirects

14 checks

Website audit scorecard for getrankly.app

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

Submitted

https://getrankly.app/

Final URL

https://getrankly.app/en

Created

Jul 22, 2026, 6:48 AM

Safe fetch

772 ms

Four-score result

Needs fixes before launch (High risk): 8 passed, 6 failed, and 0 unknown. Strongest area: Security. Weakest area: Accessibility.

Overall

out of 100

SEO / AEO

out of 100

21/47 rule points

Security

out of 100

49/52 rule points

Accessibility

out of 100

0/18 rule points

Design

out of 100

19/38 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 / AEO21/47

Security49/52

Accessibility0/18

Design19/38

Biggest score-losing checks

high

Accessibility

Rendered axe accessibility violations

axe found 1 violation rule(s), including 1 serious or critical rule(s). Top rules: meta-refresh (1).

critical

SEO / AEO

Crawler access

intake returned HTTP 403 with Cloudflare signals, which can indicate crawler or bot-security blocking. robots.txt blocks Googlebot, Bingbot, DuckDuckBot, and 9 more for this page path.

high

SEO / AEO

sitemap.xml validity

HTTP 403 returned for sitemap_xml.

high

Design

Responsive viewport basics

No viewport meta tag was detected.

Recommendations

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

5 fixes

4 opportunities

9 insights

fail

critical

SEO / AEO

Priority 2

Unblock public crawlers

-14 rule pts

What failed

The public page appears blocked for FreeScan.app or for important search and AI crawler user agents.

Evidence

intake returned HTTP 403 with Cloudflare signals, which can indicate crawler or bot-security blocking. robots.txt blocks Googlebot, Bingbot, DuckDuckBot, and 9 more for this page path.

Priority

Priority 2: fix before sharing the page publicly.

Why it matters

If crawlers cannot access the page, search engines and answer engines may not discover, index, or summarize the launch page correctly.

How to fix it

Review robots.txt, Cloudflare/WAF bot rules, rate limits, and security challenges. Allow legitimate search and AI crawler access to public launch pages while keeping private, admin, and authenticated paths protected.

Copyable agent prompt

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

fail

high

Design

Priority 3

Add responsive viewport metadata

-12 rule pts

What failed

The page is missing the viewport meta tag used for mobile layout.

Evidence

No viewport meta tag was detected.

Priority

Priority 3: fix before sharing the page publicly.

Why it matters

Launch traffic often comes from phones; missing viewport metadata can make the page render poorly.

How to fix it

Add a viewport meta tag with width=device-width and initial-scale=1.

Copyable agent prompt

## Role
Act as a focused expert website launch remediation agent for this workflow.
## Inputs
- Primary context: Improve getrankly.app at https://getrankly.app/en.
- Fix title: Add responsive viewport metadata.
- Scanner check: Responsive viewport basics.
- Category: Design.
- Status: fail.
- Severity: high.
- Priority: 3; lower numbers are more urgent.
- Score impact: 12 rule points lost.
- Evidence: No viewport meta tag was detected.
- What needs attention: The page is missing the viewport meta tag used for mobile layout.
- Why it matters: Launch traffic often comes from phones; missing viewport metadata can make the page render poorly.
- 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 viewport meta tag with width=device-width and initial-scale=1.
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 7

Publish a valid sitemap.xml

-12 rule pts

What failed

The sitemap file was not reachable or did not look like valid sitemap XML.

Evidence

HTTP 403 returned for sitemap_xml.

Priority

Priority 7: fix during launch polish.

Why it matters

A sitemap helps search engines discover the landing page and related public pages sooner.

How to fix it

Add a static sitemap file or dynamic /sitemap.xml route with valid urlset or sitemapindex XML, include your public canonical URLs, and confirm it returns HTTP 200.

Copyable agent prompt

## Role
Act as a focused expert website launch remediation agent for this workflow.
## Inputs
- Primary context: Improve getrankly.app at https://getrankly.app/en.
- Fix title: Publish a valid sitemap.xml.
- Scanner check: sitemap.xml validity.
- Category: SEO / AEO.
- Status: fail.
- Severity: high.
- Priority: 7; lower numbers are more urgent.
- Score impact: 12 rule points lost.
- Evidence: HTTP 403 returned for sitemap_xml.
- What needs attention: The sitemap file was not reachable or did not look like valid sitemap XML.
- Why it matters: A sitemap helps search engines discover the landing page and related public pages sooner.
- 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 static sitemap file or dynamic /sitemap.xml route with valid urlset or sitemapindex XML, include your public canonical URLs, and confirm it returns HTTP 200.
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

-3 rule pts

What failed

Several basic browser protection headers were not visible.

Evidence

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

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 getrankly.app at https://getrankly.app/en.
- 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: 3 rule points lost.
- Evidence: Detected 4 of 5 common public security headers. Present: strict-transport-security, content-security-policy, x-content-type-options, referrer-policy. Missing: x-frame-options.
- 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.

Score aggregation details

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

45/100

3 pass, 2 fail, 0 unknown

SEO / AEO

Severity mix: 1 critical, 2 high, 1 medium, 1 low.

critical

Crawler access

-14 rule pts

intake returned HTTP 403 with Cloudflare signals, which can indicate crawler or bot-security blocking. robots.txt blocks Googlebot, Bingbot, DuckDuckBot, and 9 more for this page path.

high

sitemap.xml validity

-12 rule pts

HTTP 403 returned for sitemap_xml.

94/100

3 pass, 1 fail, 0 unknown

Security

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

high

Common security headers

-3 rule pts

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

0/100

0 pass, 1 fail, 0 unknown

Accessibility

Severity mix: 0 critical, 1 high, 0 medium, 0 low.

high

Rendered axe accessibility violations

-18 rule pts

axe found 1 violation rule(s), including 1 serious or critical rule(s). Top rules: meta-refresh (1).

50/100

2 pass, 2 fail, 0 unknown

Design

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

high

Responsive viewport basics

-12 rule pts

No viewport meta tag was detected.

low

Runtime console health

-7 rule pts

Detected 1 console error(s) and 0 uncaught page error(s) during render.

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

critical

SEO / AEO

Crawler access

0/14

intake returned HTTP 403 with Cloudflare signals, which can indicate crawler or bot-security blocking. robots.txt blocks Googlebot, Bingbot, DuckDuckBot, and 9 more for this page path.

Failed: earned 0 of 14 points.

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

Why it matters: If crawlers cannot access the page, search engines and answer engines may not discover, index, or summarize the launch page correctly.

Fix: Review robots.txt, Cloudflare/WAF bot rules, rate limits, and security challenges. Allow legitimate search and AI crawler access to public launch pages while keeping private, admin, and authenticated paths protected.

Copyable agent prompt

## Role
Act as a focused expert website launch remediation agent for this workflow.
## Inputs
- Primary context: Improve getrankly.app at https://getrankly.app/en.
- Fix title: Unblock public crawlers.
- Scanner check: Crawler access.
- Category: SEO / AEO.
- Status: fail.
- Severity: critical.
- Priority: 2; lower numbers are more urgent.
- Score impact: 14 of 14 rule points lost.
- Evidence: intake returned HTTP 403 with Cloudflare signals, which can indicate crawler or bot-security blocking. robots.txt blocks Googlebot, Bingbot, DuckDuckBot, and 9 more for this page path.
- What needs attention: The public page appears blocked for FreeScan.app or for important search and AI crawler user agents.
- Why it matters: If crawlers cannot access the page, search engines and answer engines may not discover, index, or summarize the launch page correctly.
- 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 robots.txt, Cloudflare/WAF bot rules, rate limits, and security challenges. Allow legitimate search and AI crawler access to public launch pages while keeping private, admin, and authenticated paths protected.
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

sitemap.xml validity

0/12

HTTP 403 returned for sitemap_xml.

Failed: earned 0 of 12 points.

Priority: Priority 7: fix during launch polish.

Why it matters: A sitemap helps search engines discover the landing page and related public pages sooner.

Fix: Add a static sitemap file or dynamic /sitemap.xml route with valid urlset or sitemapindex XML, include your public canonical URLs, and confirm it returns HTTP 200.

Copyable agent prompt

## Role
Act as a focused expert website launch remediation agent for this workflow.
## Inputs
- Primary context: Improve getrankly.app at https://getrankly.app/en.
- Fix title: Publish a valid sitemap.xml.
- Scanner check: sitemap.xml validity.
- Category: SEO / AEO.
- Status: fail.
- Severity: high.
- Priority: 7; lower numbers are more urgent.
- Score impact: 12 of 12 rule points lost.
- Evidence: HTTP 403 returned for sitemap_xml.
- What needs attention: The sitemap file was not reachable or did not look like valid sitemap XML.
- Why it matters: A sitemap helps search engines discover the landing page and related public pages sooner.
- 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 static sitemap file or dynamic /sitemap.xml route with valid urlset or sitemapindex XML, include your public canonical URLs, and confirm it returns HTTP 200.
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

15/18

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

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

fail

high

Accessibility

Rendered axe accessibility violations

0/18

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

fail

high

Design

Responsive viewport basics

0/12

No viewport meta tag was detected.

Failed: earned 0 of 12 points.

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

Why it matters: Launch traffic often comes from phones; missing viewport metadata can make the page render poorly.

Fix: Add a viewport meta tag with width=device-width and initial-scale=1.

Copyable agent prompt

## Role
Act as a focused expert website launch remediation agent for this workflow.
## Inputs
- Primary context: Improve getrankly.app at https://getrankly.app/en.
- Fix title: Add responsive viewport metadata.
- Scanner check: Responsive viewport basics.
- Category: Design.
- Status: fail.
- Severity: high.
- Priority: 3; lower numbers are more urgent.
- Score impact: 12 of 12 rule points lost.
- Evidence: No viewport meta tag was detected.
- What needs attention: The page is missing the viewport meta tag used for mobile layout.
- Why it matters: Launch traffic often comes from phones; missing viewport metadata can make the page render poorly.
- 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 viewport meta tag with width=device-width and initial-scale=1.
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

low

Design

Runtime console health

0/7

Detected 1 console error(s) and 0 uncaught page error(s) during render.

Failed: earned 0 of 7 points.

Priority: Priority 15: fix during launch polish.

Why it matters: Runtime errors can break forms, CTAs, animations, tracking, or responsive behavior even when the static HTML looks fine.

Fix: Open the page in a browser, reproduce the console errors, and fix missing assets, hydration problems, client-side exceptions, or failing third-party scripts.

Copyable agent prompt

## Role
Act as a focused expert website launch remediation agent for this workflow.
## Inputs
- Primary context: Improve getrankly.app at https://getrankly.app/en.
- Fix title: Fix runtime browser errors.
- Scanner check: Runtime console health.
- Category: Design.
- Status: fail.
- Severity: low.
- Priority: 15; lower numbers are more urgent.
- Score impact: 7 of 7 rule points lost.
- Evidence: Detected 1 console error(s) and 0 uncaught page error(s) during render.
- What needs attention: The rendered page produced console or uncaught JavaScript errors.
- Why it matters: Runtime errors can break forms, CTAs, animations, tracking, or responsive behavior even when the static HTML looks fine.
- 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: Open the page in a browser, reproduce the console errors, and fix missing assets, hydration problems, client-side exceptions, or failing third-party scripts.
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.

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

getrankly.app website audit report

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

Public report link

Markdown report

# getrankly.app Website Scan

Scanned URL: [https://getrankly.app/en](https://getrankly.app/en)
Report URL: /scan/getrankly-app-47-launch-readiness-report-4e95570f
Created: 2026-07-22T06:48:21.627Z

## Score Summary

- Overall: 47/100
- SEO / AEO: 45/100
- Security: 94/100
- Accessibility: 0/100
- Design: 50/100

## Launch Readiness

Needs fixes before launch (High risk).

Passed: 8. Failed: 6. Unknown: 0.
Strongest area: Security. Weakest area: Accessibility.

## Prioritized Fixes

### 1. Unblock public crawlers

- Category: SEO / AEO
- Status: fail
- Severity: critical
- Rule points lost: 14
- Evidence: intake returned HTTP 403 with Cloudflare signals, which can indicate crawler or bot-security blocking. robots.txt blocks Googlebot, Bingbot, DuckDuckBot, and 9 more for this page path.
- Why it matters: If crawlers cannot access the page, search engines and answer engines may not discover, index, or summarize the launch page correctly.
- Fix: Review robots.txt, Cloudflare/WAF bot rules, rate limits, and security challenges. Allow legitimate search and AI crawler access to public launch pages while keeping private, admin, and authenticated paths protected.

### 2. Fix rendered axe accessibility violations

- Category: Accessibility
- Status: fail
- Severity: high
- Rule points lost: 18
- Evidence: axe found 1 violation rule(s), including 1 serious or critical rule(s). Top rules: meta-refresh (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 responsive viewport metadata

- Category: Design
- Status: fail
- Severity: high
- Rule points lost: 12
- Evidence: No viewport meta tag was detected.
- Why it matters: Launch traffic often comes from phones; missing viewport metadata can make the page render poorly.
- Fix: Add a viewport meta tag with width=device-width and initial-scale=1.

### 4. Publish a valid sitemap.xml

- Category: SEO / AEO
- Status: fail
- Severity: high
- Rule points lost: 12
- Evidence: HTTP 403 returned for sitemap_xml.
- Why it matters: A sitemap helps search engines discover the landing page and related public pages sooner.
- Fix: Add a static sitemap file or dynamic /sitemap.xml route with valid urlset or sitemapindex XML, include your public canonical URLs, and confirm it returns HTTP 200.

### 5. Add common public security headers

- Category: Security
- Status: fail
- Severity: high
- Rule points lost: 3
- Evidence: Detected 4 of 5 common public security headers. Present: strict-transport-security, content-security-policy, x-content-type-options, referrer-policy. Missing: x-frame-options.
- 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.

## Opportunities

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

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

### Expose important supporting pages in navigation or footer

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

### Make trust and proof easier to detect

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

### Tighten the live color system

- Impact: high
- Category: Accessibility
- Evidence: 14 of 14 rendered contrast sample(s) missed target. Worst ratio: 1.61.
- 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.

## Insights

### Crawlability needs review

- Category: SEO / AEO
- Evidence: HTTP 403. robots.txt: HTTP 200. sitemap.xml: not reachable. noindex check: clear.
- Interpretation: One or more crawl/index signals could prevent the page from being reliably discovered or shown.
- 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: 0. H1 count: 0. Audience signals: 0. CTA labels: none detected.
- Interpretation: Google AI features currently rely on standard Search eligibility; the extra advantage comes from content that is easy to quote, summarize, and verify.
- Recommended use: Prioritize clear text answers, crawlable support pages, accurate schema, and visible proof over speculative AI-only markup.

### Detected entity signals

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

### No structured data detected

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

### Weakest score area

- Category: Accessibility
- Evidence: SEO / AEO: 45/100. Security: 94/100. Accessibility: 0/100. Design: 50/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://getrankly.app/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: 14. Contrast failures: 14. Console errors: 1. Horizontal overflow: 0px.
- Interpretation: The scan inspected the browser-rendered page, so contrast, runtime, layout, and timing signals are more representative than static markup alone.
- Recommended use: Use rendered checks to prioritize issues that visitors actually experience after JavaScript and CSS load.

### Rendered speed snapshot

- Category: Design
- Evidence: DOMContentLoaded: 193ms. Load complete: 335ms. First contentful paint: 332ms. Resources: 5. Scripts: 2. Images: 1. 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: 1. Critical: 1. Serious: 0. Top rules: meta-refresh.
- 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 getrankly.app 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 403

1 redirects

14 checks

Website audit scorecard for getrankly.app

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

Submitted

https://getrankly.app/

Final URL

https://getrankly.app/en

Created

Jul 22, 2026, 6:48 AM

Safe fetch

772 ms

Four-score result

Needs fixes before launch (High risk): 8 passed, 6 failed, and 0 unknown. Strongest area: Security. Weakest area: Accessibility.

Overall

out of 100

SEO / AEO

out of 100

21/47 rule points

Security

out of 100

49/52 rule points

Accessibility

out of 100

0/18 rule points

Design

out of 100

19/38 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 / AEO21/47

Security49/52

Accessibility0/18

Design19/38

Biggest score-losing checks

high

Accessibility

Rendered axe accessibility violations

axe found 1 violation rule(s), including 1 serious or critical rule(s). Top rules: meta-refresh (1).

critical

SEO / AEO

Crawler access

intake returned HTTP 403 with Cloudflare signals, which can indicate crawler or bot-security blocking. robots.txt blocks Googlebot, Bingbot, DuckDuckBot, and 9 more for this page path.

high

SEO / AEO

sitemap.xml validity

HTTP 403 returned for sitemap_xml.

high

Design

Responsive viewport basics

No viewport meta tag was detected.

Recommendations

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

5 fixes

4 opportunities

9 insights

fail

critical

SEO / AEO

Priority 2

Unblock public crawlers

-14 rule pts

What failed

The public page appears blocked for FreeScan.app or for important search and AI crawler user agents.

Evidence

intake returned HTTP 403 with Cloudflare signals, which can indicate crawler or bot-security blocking. robots.txt blocks Googlebot, Bingbot, DuckDuckBot, and 9 more for this page path.

Priority

Priority 2: fix before sharing the page publicly.

Why it matters

If crawlers cannot access the page, search engines and answer engines may not discover, index, or summarize the launch page correctly.

How to fix it

Copyable agent prompt

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

fail

high

Design

Priority 3

Add responsive viewport metadata

-12 rule pts

What failed

The page is missing the viewport meta tag used for mobile layout.

Evidence

No viewport meta tag was detected.

Priority

Priority 3: fix before sharing the page publicly.

Why it matters

Launch traffic often comes from phones; missing viewport metadata can make the page render poorly.

How to fix it

Add a viewport meta tag with width=device-width and initial-scale=1.

Copyable agent prompt

## Role
Act as a focused expert website launch remediation agent for this workflow.
## Inputs
- Primary context: Improve getrankly.app at https://getrankly.app/en.
- Fix title: Add responsive viewport metadata.
- Scanner check: Responsive viewport basics.
- Category: Design.
- Status: fail.
- Severity: high.
- Priority: 3; lower numbers are more urgent.
- Score impact: 12 rule points lost.
- Evidence: No viewport meta tag was detected.
- What needs attention: The page is missing the viewport meta tag used for mobile layout.
- Why it matters: Launch traffic often comes from phones; missing viewport metadata can make the page render poorly.
- 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 viewport meta tag with width=device-width and initial-scale=1.
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 7

Publish a valid sitemap.xml

-12 rule pts

What failed

The sitemap file was not reachable or did not look like valid sitemap XML.

Evidence

HTTP 403 returned for sitemap_xml.

Priority

Priority 7: fix during launch polish.

Why it matters

A sitemap helps search engines discover the landing page and related public pages sooner.

How to fix it

Add a static sitemap file or dynamic /sitemap.xml route with valid urlset or sitemapindex XML, include your public canonical URLs, and confirm it returns HTTP 200.

Copyable agent prompt

## Role
Act as a focused expert website launch remediation agent for this workflow.
## Inputs
- Primary context: Improve getrankly.app at https://getrankly.app/en.
- Fix title: Publish a valid sitemap.xml.
- Scanner check: sitemap.xml validity.
- Category: SEO / AEO.
- Status: fail.
- Severity: high.
- Priority: 7; lower numbers are more urgent.
- Score impact: 12 rule points lost.
- Evidence: HTTP 403 returned for sitemap_xml.
- What needs attention: The sitemap file was not reachable or did not look like valid sitemap XML.
- Why it matters: A sitemap helps search engines discover the landing page and related public pages sooner.
- 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 static sitemap file or dynamic /sitemap.xml route with valid urlset or sitemapindex XML, include your public canonical URLs, and confirm it returns HTTP 200.
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

-3 rule pts

What failed

Several basic browser protection headers were not visible.

Evidence

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

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 getrankly.app at https://getrankly.app/en.
- 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: 3 rule points lost.
- Evidence: Detected 4 of 5 common public security headers. Present: strict-transport-security, content-security-policy, x-content-type-options, referrer-policy. Missing: x-frame-options.
- 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.

Score aggregation details

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

45/100

3 pass, 2 fail, 0 unknown

SEO / AEO

Severity mix: 1 critical, 2 high, 1 medium, 1 low.

critical

Crawler access

-14 rule pts

intake returned HTTP 403 with Cloudflare signals, which can indicate crawler or bot-security blocking. robots.txt blocks Googlebot, Bingbot, DuckDuckBot, and 9 more for this page path.

high

sitemap.xml validity

-12 rule pts

HTTP 403 returned for sitemap_xml.

94/100

3 pass, 1 fail, 0 unknown

Security

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

high

Common security headers

-3 rule pts

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

0/100

0 pass, 1 fail, 0 unknown

Accessibility

Severity mix: 0 critical, 1 high, 0 medium, 0 low.

high

Rendered axe accessibility violations

-18 rule pts

axe found 1 violation rule(s), including 1 serious or critical rule(s). Top rules: meta-refresh (1).

50/100

2 pass, 2 fail, 0 unknown

Design

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

high

Responsive viewport basics

-12 rule pts

No viewport meta tag was detected.

low

Runtime console health

-7 rule pts

Detected 1 console error(s) and 0 uncaught page error(s) during render.

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

critical

SEO / AEO

Crawler access

0/14

intake returned HTTP 403 with Cloudflare signals, which can indicate crawler or bot-security blocking. robots.txt blocks Googlebot, Bingbot, DuckDuckBot, and 9 more for this page path.

Failed: earned 0 of 14 points.

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

Why it matters: If crawlers cannot access the page, search engines and answer engines may not discover, index, or summarize the launch page correctly.

Copyable agent prompt

## Role
Act as a focused expert website launch remediation agent for this workflow.
## Inputs
- Primary context: Improve getrankly.app at https://getrankly.app/en.
- Fix title: Unblock public crawlers.
- Scanner check: Crawler access.
- Category: SEO / AEO.
- Status: fail.
- Severity: critical.
- Priority: 2; lower numbers are more urgent.
- Score impact: 14 of 14 rule points lost.
- Evidence: intake returned HTTP 403 with Cloudflare signals, which can indicate crawler or bot-security blocking. robots.txt blocks Googlebot, Bingbot, DuckDuckBot, and 9 more for this page path.
- What needs attention: The public page appears blocked for FreeScan.app or for important search and AI crawler user agents.
- Why it matters: If crawlers cannot access the page, search engines and answer engines may not discover, index, or summarize the launch page correctly.
- 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 robots.txt, Cloudflare/WAF bot rules, rate limits, and security challenges. Allow legitimate search and AI crawler access to public launch pages while keeping private, admin, and authenticated paths protected.
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

sitemap.xml validity

0/12

HTTP 403 returned for sitemap_xml.

Failed: earned 0 of 12 points.

Priority: Priority 7: fix during launch polish.

Why it matters: A sitemap helps search engines discover the landing page and related public pages sooner.

Fix: Add a static sitemap file or dynamic /sitemap.xml route with valid urlset or sitemapindex XML, include your public canonical URLs, and confirm it returns HTTP 200.

Copyable agent prompt

## Role
Act as a focused expert website launch remediation agent for this workflow.
## Inputs
- Primary context: Improve getrankly.app at https://getrankly.app/en.
- Fix title: Publish a valid sitemap.xml.
- Scanner check: sitemap.xml validity.
- Category: SEO / AEO.
- Status: fail.
- Severity: high.
- Priority: 7; lower numbers are more urgent.
- Score impact: 12 of 12 rule points lost.
- Evidence: HTTP 403 returned for sitemap_xml.
- What needs attention: The sitemap file was not reachable or did not look like valid sitemap XML.
- Why it matters: A sitemap helps search engines discover the landing page and related public pages sooner.
- 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 static sitemap file or dynamic /sitemap.xml route with valid urlset or sitemapindex XML, include your public canonical URLs, and confirm it returns HTTP 200.
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

15/18

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

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

fail

high

Accessibility

Rendered axe accessibility violations

0/18

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

fail

high

Design

Responsive viewport basics

0/12

No viewport meta tag was detected.

Failed: earned 0 of 12 points.

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

Why it matters: Launch traffic often comes from phones; missing viewport metadata can make the page render poorly.

Fix: Add a viewport meta tag with width=device-width and initial-scale=1.

Copyable agent prompt

## Role
Act as a focused expert website launch remediation agent for this workflow.
## Inputs
- Primary context: Improve getrankly.app at https://getrankly.app/en.
- Fix title: Add responsive viewport metadata.
- Scanner check: Responsive viewport basics.
- Category: Design.
- Status: fail.
- Severity: high.
- Priority: 3; lower numbers are more urgent.
- Score impact: 12 of 12 rule points lost.
- Evidence: No viewport meta tag was detected.
- What needs attention: The page is missing the viewport meta tag used for mobile layout.
- Why it matters: Launch traffic often comes from phones; missing viewport metadata can make the page render poorly.
- 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 viewport meta tag with width=device-width and initial-scale=1.
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

low

Design

Runtime console health

0/7

Detected 1 console error(s) and 0 uncaught page error(s) during render.

Failed: earned 0 of 7 points.

Priority: Priority 15: fix during launch polish.

Why it matters: Runtime errors can break forms, CTAs, animations, tracking, or responsive behavior even when the static HTML looks fine.

Fix: Open the page in a browser, reproduce the console errors, and fix missing assets, hydration problems, client-side exceptions, or failing third-party scripts.

Copyable agent prompt

## Role
Act as a focused expert website launch remediation agent for this workflow.
## Inputs
- Primary context: Improve getrankly.app at https://getrankly.app/en.
- Fix title: Fix runtime browser errors.
- Scanner check: Runtime console health.
- Category: Design.
- Status: fail.
- Severity: low.
- Priority: 15; lower numbers are more urgent.
- Score impact: 7 of 7 rule points lost.
- Evidence: Detected 1 console error(s) and 0 uncaught page error(s) during render.
- What needs attention: The rendered page produced console or uncaught JavaScript errors.
- Why it matters: Runtime errors can break forms, CTAs, animations, tracking, or responsive behavior even when the static HTML looks fine.
- 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: Open the page in a browser, reproduce the console errors, and fix missing assets, hydration problems, client-side exceptions, or failing third-party scripts.
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.

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

getrankly.app website audit report

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

Public report link

Markdown report

# getrankly.app Website Scan

Scanned URL: [https://getrankly.app/en](https://getrankly.app/en)
Report URL: /scan/getrankly-app-47-launch-readiness-report-4e95570f
Created: 2026-07-22T06:48:21.627Z

## Score Summary

- Overall: 47/100
- SEO / AEO: 45/100
- Security: 94/100
- Accessibility: 0/100
- Design: 50/100

## Launch Readiness

Needs fixes before launch (High risk).

Passed: 8. Failed: 6. Unknown: 0.
Strongest area: Security. Weakest area: Accessibility.

## Prioritized Fixes

### 1. Unblock public crawlers

- Category: SEO / AEO
- Status: fail
- Severity: critical
- Rule points lost: 14
- Evidence: intake returned HTTP 403 with Cloudflare signals, which can indicate crawler or bot-security blocking. robots.txt blocks Googlebot, Bingbot, DuckDuckBot, and 9 more for this page path.
- Why it matters: If crawlers cannot access the page, search engines and answer engines may not discover, index, or summarize the launch page correctly.
- Fix: Review robots.txt, Cloudflare/WAF bot rules, rate limits, and security challenges. Allow legitimate search and AI crawler access to public launch pages while keeping private, admin, and authenticated paths protected.

### 2. Fix rendered axe accessibility violations

- Category: Accessibility
- Status: fail
- Severity: high
- Rule points lost: 18
- Evidence: axe found 1 violation rule(s), including 1 serious or critical rule(s). Top rules: meta-refresh (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 responsive viewport metadata

- Category: Design
- Status: fail
- Severity: high
- Rule points lost: 12
- Evidence: No viewport meta tag was detected.
- Why it matters: Launch traffic often comes from phones; missing viewport metadata can make the page render poorly.
- Fix: Add a viewport meta tag with width=device-width and initial-scale=1.

### 4. Publish a valid sitemap.xml

- Category: SEO / AEO
- Status: fail
- Severity: high
- Rule points lost: 12
- Evidence: HTTP 403 returned for sitemap_xml.
- Why it matters: A sitemap helps search engines discover the landing page and related public pages sooner.
- Fix: Add a static sitemap file or dynamic /sitemap.xml route with valid urlset or sitemapindex XML, include your public canonical URLs, and confirm it returns HTTP 200.

### 5. Add common public security headers

- Category: Security
- Status: fail
- Severity: high
- Rule points lost: 3
- Evidence: Detected 4 of 5 common public security headers. Present: strict-transport-security, content-security-policy, x-content-type-options, referrer-policy. Missing: x-frame-options.
- 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.

## Opportunities

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

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

### Expose important supporting pages in navigation or footer

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

### Make trust and proof easier to detect

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

### Tighten the live color system

- Impact: high
- Category: Accessibility
- Evidence: 14 of 14 rendered contrast sample(s) missed target. Worst ratio: 1.61.
- 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.

## Insights

### Crawlability needs review

- Category: SEO / AEO
- Evidence: HTTP 403. robots.txt: HTTP 200. sitemap.xml: not reachable. noindex check: clear.
- Interpretation: One or more crawl/index signals could prevent the page from being reliably discovered or shown.
- 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: 0. H1 count: 0. Audience signals: 0. CTA labels: none detected.
- Interpretation: Google AI features currently rely on standard Search eligibility; the extra advantage comes from content that is easy to quote, summarize, and verify.
- Recommended use: Prioritize clear text answers, crawlable support pages, accurate schema, and visible proof over speculative AI-only markup.

### Detected entity signals

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

### No structured data detected

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

### Weakest score area

- Category: Accessibility
- Evidence: SEO / AEO: 45/100. Security: 94/100. Accessibility: 0/100. Design: 50/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://getrankly.app/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: 14. Contrast failures: 14. Console errors: 1. Horizontal overflow: 0px.
- Interpretation: The scan inspected the browser-rendered page, so contrast, runtime, layout, and timing signals are more representative than static markup alone.
- Recommended use: Use rendered checks to prioritize issues that visitors actually experience after JavaScript and CSS load.

### Rendered speed snapshot

- Category: Design
- Evidence: DOMContentLoaded: 193ms. Load complete: 335ms. First contentful paint: 332ms. Resources: 5. Scripts: 2. Images: 1. 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: 1. Critical: 1. Serious: 0. Top rules: meta-refresh.
- 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 getrankly.app without re-entering the URL. The previous report stays saved so the next result can be compared against it.

Website audit scorecard for getrankly.app

Unblock public crawlers

Copyable agent prompt

Fix rendered axe accessibility violations

Copyable agent prompt

Add responsive viewport metadata

Copyable agent prompt

Publish a valid sitemap.xml

Copyable agent prompt

Add common public security headers

Copyable agent prompt

SEO / AEO

Crawler access

sitemap.xml validity

Security

Common security headers

Accessibility

Rendered axe accessibility violations

Design

Responsive viewport basics

Runtime console health

Failed checks

Crawler access

Copyable agent prompt

sitemap.xml validity

Copyable agent prompt

Common security headers

Copyable agent prompt

Rendered axe accessibility violations

Copyable agent prompt

Responsive viewport basics

Copyable agent prompt

Runtime console health

Copyable agent prompt

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 getrankly.app

Unblock public crawlers

Copyable agent prompt

Fix rendered axe accessibility violations

Copyable agent prompt

Add responsive viewport metadata

Copyable agent prompt

Publish a valid sitemap.xml

Copyable agent prompt

Add common public security headers

Copyable agent prompt

SEO / AEO

Crawler access

sitemap.xml validity

Security

Common security headers

Accessibility

Rendered axe accessibility violations

Design

Responsive viewport basics

Runtime console health

Failed checks

Crawler access

Copyable agent prompt

sitemap.xml validity

Copyable agent prompt

Common security headers

Copyable agent prompt

Rendered axe accessibility violations

Copyable agent prompt

Responsive viewport basics

Copyable agent prompt

Runtime console health

Copyable agent prompt

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.