completed

HTTP 200

0 redirects

36 checks

promptplanner.app Website Audit

Speed Insights

Grade N/A

Not captured

https://promptplanner.app

LCP

N/A

Largest paint

TBT

N/A

Blocking time

CLS

N/A

Layout shift

Four-score result

Close to ready (Strong): 30 passed, 6 failed, and 0 unknown. Strongest area: Accessibility. Weakest area: Security.

Overall

out of 100

SEO / AEO

out of 100

63/82 rule points

Security

out of 100

58/76 rule points

Accessibility

100

out of 100

94/94 rule points

Design

out of 100

94/110 rule points

Why this scored this way

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

Category point breakdown

SEO / AEO63/82

Security58/76

Accessibility94/94

Design94/110

Biggest score-losing checks

high

Security

Common security headers

Detected 0 of 5 common public security headers.

medium

Design

Rendered layout ergonomics

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

medium

SEO / AEO

robots.txt reachability

HTTP 404 returned for robots_txt.

medium

SEO / AEO

sitemap.xml reachability

HTTP 404 returned for sitemap_xml.

Recommendations

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

5 fixes

6 opportunities

9 insights

fail

high

Security

Priority 5

Add common public security headers

-18 rule pts

What failed

Several basic browser protection headers were not visible.

Evidence

Detected 0 of 5 common public security headers.

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.

Agent Prompt

## Role
Act as a focused public web security remediation expert who can inspect the public page and safely improve the underlying implementation.
## Inputs
- Primary context: Improve promptplanner.app at https://promptplanner.app.
- Scanner check ID: security_common_headers.
- 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: 18 rule points lost.
- Evidence: Detected 0 of 5 common public security headers.
- 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.
- Likely places to inspect: hosting headers, server middleware, edge/proxy config, CDN rules, and framework security header configuration; server, edge, CDN, hosting, proxy, form action, asset URL, cookie, and public file access configuration; the route, template, component, CMS entry, theme file, or static page that renders the scanned URL; shared layout, metadata, routing, middleware, server, CDN, or hosting configuration if the issue is not in page content; existing tests, build scripts, preview commands, and deployment notes before choosing verification steps.
## 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.
First reproduce or verify the issue from the public page and available implementation source. Then make the smallest stack-appropriate change that fixes the scanner signal and improves the real user experience.
Use this check-specific implementation guide:
- Add missing common browser protection headers with values appropriate for the site.
- Treat an existing CSP frame-ancestors directive as valid frame protection; preserve the directive and its allowed origins exactly instead of adding or substituting X-Frame-Options.
- Test CSP or frame policies carefully so they do not break scripts, images, analytics, payments, embeds, or auth.
- Prefer narrow, production-safe security configuration changes over blanket disables or permissive rules.
- Preserve authentication, authorization, private paths, and sensitive file protections while fixing the public launch page.
- Keep the implementation stack-appropriate: use the existing framework, CMS, hosting provider, design system, and deployment workflow already in the project.
Acceptance criteria for this fix:
- Important security headers are visible on the public response.
- Any existing CSP frame-ancestors directive and its allowed origins remain unchanged.
- The page still renders and key flows still work after header changes.
- The public URL keeps legitimate visitors and assets working while removing the reported browser-side or public exposure risk.
- The change does not weaken security headers, authentication, authorization, or private route protections.
- A fresh FreeScan rescan should show this check improved or passing after deployment.
## Output
Return a structured response with these headings: Findings, Changes Made, Verification Results, Rescan Expectation, Rollback Notes, 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.
- Prefer editing the canonical source of the page over patching built output, generated files, CDN-cached HTML, or minified assets.
- Do not make a cosmetic or placeholder change just to satisfy the scanner; the public page should be materially better for visitors, crawlers, or assistive technology.
- If an existing Content-Security-Policy contains a frame-ancestors directive, preserve that directive exactly, including its allowed origins, unless the site owner explicitly asks to change it. Do not replace it with X-Frame-Options merely to satisfy this scan.
- Verify the result with the smallest reliable test, build, browser check, or manual inspection available.
## Safety
- Do not request, expose, or reproduce sensitive data.
- Redact private details from examples unless the user explicitly says they are safe to include.
- Do not use credentials, cookies, authenticated data, hidden form values, or private response bodies.
- Do not weaken security headers, authentication, authorization, privacy controls, accessibility, or error handling to make the scan pass.

fail

medium

Design

Priority 13

Fix rendered layout ergonomics

-9 rule pts

What failed

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

Evidence

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

Priority

Priority 13: fix during launch polish.

Why it matters

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

How to fix it

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

Agent Prompt

## Role
Act as a focused conversion-focused frontend quality remediation expert who can inspect the public page and safely improve the underlying implementation.
## Inputs
- Primary context: Improve promptplanner.app at https://promptplanner.app.
- Scanner check ID: design_rendered_layout.
- Fix title: Fix rendered layout ergonomics.
- Scanner check: Rendered layout ergonomics.
- Category: Design.
- Status: fail.
- Severity: medium.
- Priority: 13; lower numbers are more urgent.
- Score impact: 9 rule points lost.
- Evidence: Horizontal overflow: 0px. Small tap targets: 11.
- What needs attention: The browser-rendered page has layout or tap-target issues.
- Why it matters: Horizontal overflow and tiny tap targets make the page feel broken on real devices, especially for mobile visitors.
- Status-specific guidance: A public check reported a failure. Reproduce or inspect the issue first, then make the smallest safe fix.
- Audience or recipient: The site owner, builder, or marketing team responsible for improving this public page.
- Constraints, examples, or source material: Treat the live URL as the public target to inspect, not as the only source of truth. When repository, CMS, or hosting access is available, use that implementation context before changing anything.
- Target outcome: After the fix is deployed and the public page is rescanned, this specific check should improve or pass without lowering other SEO / AEO, security, accessibility, or design signals.
- Likely places to inspect: mobile viewport, horizontal overflow sources, tap target sizes, fixed-position elements, menus, forms, and embeds; page layout, responsive CSS, component states, copy hierarchy, CTA placement, spacing tokens, rendered console output, and performance-sensitive assets; the route, template, component, CMS entry, theme file, or static page that renders the scanned URL; shared layout, metadata, routing, middleware, server, CDN, or hosting configuration if the issue is not in page content; existing tests, build scripts, preview commands, and deployment notes before choosing verification steps.
## Task
Use the provided context to safely complete this workflow: Remove elements wider than the viewport, add responsive constraints, and make important links, buttons, inputs, and controls at least 40px tall and wide where possible.
First reproduce or verify the issue from the public page and available implementation source. Then make the smallest stack-appropriate change that fixes the scanner signal and improves the real user experience.
Use this check-specific implementation guide:
- Constrain overflowing elements and increase small important tap targets where possible.
- Preserve layout intent while making the rendered page usable on real devices.
- Improve the actual rendered page at mobile and desktop sizes, not only the source code shape.
- Preserve core conversion flows while making layout, hierarchy, readability, or runtime health better.
- Keep the implementation stack-appropriate: use the existing framework, CMS, hosting provider, design system, and deployment workflow already in the project.
Acceptance criteria for this fix:
- The rendered page has no meaningful horizontal overflow.
- Important links, buttons, inputs, and controls are comfortably tappable.
- The rendered page is visually stable and usable on mobile and desktop viewports.
- The fix does not hide content, break CTAs, introduce console errors, or reduce clarity for visitors.
- A fresh FreeScan rescan should show this check improved or passing after deployment.
## Output
Return a structured response with these headings: Findings, Changes Made, Verification Results, Rescan Expectation, Rollback Notes, 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.
- Prefer editing the canonical source of the page over patching built output, generated files, CDN-cached HTML, or minified assets.
- Do not make a cosmetic or placeholder change just to satisfy the scanner; the public page should be materially better for visitors, crawlers, or assistive technology.
- Verify the result with the smallest reliable test, build, browser check, or manual inspection available.
## Safety
- Do not request, expose, or reproduce sensitive data.
- Redact private details from examples unless the user explicitly says they are safe to include.
- Do not use credentials, cookies, authenticated data, hidden form values, or private response bodies.
- Do not weaken security headers, authentication, authorization, privacy controls, accessibility, or error handling to make the scan pass.

fail

medium

SEO / AEO

Priority 14

Publish robots.txt

-7 rule pts

What failed

The standard crawler instruction file was not reachable.

Evidence

HTTP 404 returned for robots_txt.

Priority

Priority 14: fix during launch polish.

Why it matters

A reachable robots.txt helps crawlers understand what they can index before launch traffic arrives.

How to fix it

Add a public /robots.txt file and make sure it returns HTTP 200 without blocking the landing page.

Agent Prompt

## Role
Act as a focused technical SEO, AEO, and crawlability remediation expert who can inspect the public page and safely improve the underlying implementation.
## Inputs
- Primary context: Improve promptplanner.app at https://promptplanner.app.
- Scanner check ID: seo_robots_txt.
- Fix title: Publish robots.txt.
- Scanner check: robots.txt reachability.
- Category: SEO / AEO.
- Status: fail.
- Severity: medium.
- Priority: 14; lower numbers are more urgent.
- Score impact: 7 rule points lost.
- Evidence: HTTP 404 returned for robots_txt.
- What needs attention: The standard crawler instruction file was not reachable.
- Why it matters: A reachable robots.txt helps crawlers understand what they can index before launch traffic arrives.
- 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.
- Likely places to inspect: public robots.txt file or route, deployment static assets, and crawler directives for the landing page; metadata/head configuration, canonical URL logic, robots and sitemap routes, structured data blocks, page copy, headings, and internal navigation; the route, template, component, CMS entry, theme file, or static page that renders the scanned URL; shared layout, metadata, routing, middleware, server, CDN, or hosting configuration if the issue is not in page content; existing tests, build scripts, preview commands, and deployment notes before choosing verification steps.
## Task
Use the provided context to safely complete this workflow: Add a public /robots.txt file and make sure it returns HTTP 200 without blocking the landing page.
First reproduce or verify the issue from the public page and available implementation source. Then make the smallest stack-appropriate change that fixes the scanner signal and improves the real user experience.
Use this check-specific implementation guide:
- Publish a reachable robots.txt that permits crawling of the public landing page.
- Only block private, admin, search-result, staging, or low-value paths intentionally.
- Keep all metadata, headings, schema, canonical URLs, and visible copy consistent with the same public facts.
- Use accurate, crawlable, human-visible content as the source for search and answer-engine improvements.
- Keep the implementation stack-appropriate: use the existing framework, CMS, hosting provider, design system, and deployment workflow already in the project.
Acceptance criteria for this fix:
- /robots.txt returns HTTP 200 publicly.
- The scanned public page is not blocked by robots.txt.
- The public URL exposes the corrected crawl/search/answer signal in rendered HTML or reachable public files.
- The change should be visible to a fresh unauthenticated request and likely improve the related FreeScan SEO / AEO check on rescan.
- A fresh FreeScan rescan should show this check improved or passing after deployment.
## Output
Return a structured response with these headings: Findings, Changes Made, Verification Results, Rescan Expectation, Rollback Notes, 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.
- Prefer editing the canonical source of the page over patching built output, generated files, CDN-cached HTML, or minified assets.
- Do not make a cosmetic or placeholder change just to satisfy the scanner; the public page should be materially better for visitors, crawlers, or assistive technology.
- Verify the result with the smallest reliable test, build, browser check, or manual inspection available.
## Safety
- Do not request, expose, or reproduce sensitive data.
- Redact private details from examples unless the user explicitly says they are safe to include.
- Do not use credentials, cookies, authenticated data, hidden form values, or private response bodies.
- Do not weaken security headers, authentication, authorization, privacy controls, accessibility, or error handling to make the scan pass.

fail

medium

SEO / AEO

Priority 15

Publish sitemap.xml

-7 rule pts

What failed

The sitemap file was not reachable.

Evidence

HTTP 404 returned for sitemap_xml.

Priority

Priority 15: 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 /sitemap.xml with your public URLs and confirm it returns HTTP 200.

Agent Prompt

## Role
Act as a focused technical SEO, AEO, and crawlability remediation expert who can inspect the public page and safely improve the underlying implementation.
## Inputs
- Primary context: Improve promptplanner.app at https://promptplanner.app.
- Scanner check ID: seo_sitemap_xml.
- Fix title: Publish sitemap.xml.
- Scanner check: sitemap.xml reachability.
- Category: SEO / AEO.
- Status: fail.
- Severity: medium.
- Priority: 15; lower numbers are more urgent.
- Score impact: 7 rule points lost.
- Evidence: HTTP 404 returned for sitemap_xml.
- What needs attention: The sitemap file was not reachable.
- 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.
- Likely places to inspect: robots.txt Sitemap directives, static sitemap files, dynamic sitemap routes, sitemap indexes, canonical URL generation, and deployment output; metadata/head configuration, canonical URL logic, robots and sitemap routes, structured data blocks, page copy, headings, and internal navigation; the route, template, component, CMS entry, theme file, or static page that renders the scanned URL; shared layout, metadata, routing, middleware, server, CDN, or hosting configuration if the issue is not in page content; existing tests, build scripts, preview commands, and deployment notes before choosing verification steps.
## Task
Use the provided context to safely complete this workflow: Add /sitemap.xml with your public URLs and confirm it returns HTTP 200.
First reproduce or verify the issue from the public page and available implementation source. Then make the smallest stack-appropriate change that fixes the scanner signal and improves the real user experience.
Use this check-specific implementation guide:
- Provide a reachable sitemap URL with valid urlset or sitemapindex XML. Preserve an existing robots.txt Sitemap directive such as /sitemap_index.xml when it is intentional and valid.
- Include canonical public URLs and avoid localhost, staging, private, noindex, or duplicate URLs.
- Keep all metadata, headings, schema, canonical URLs, and visible copy consistent with the same public facts.
- Use accurate, crawlable, human-visible content as the source for search and answer-engine improvements.
- Keep the implementation stack-appropriate: use the existing framework, CMS, hosting provider, design system, and deployment workflow already in the project.
Acceptance criteria for this fix:
- The sitemap URL declared in robots.txt, or /sitemap.xml when no directive exists, returns HTTP 200 with a valid urlset or sitemapindex root.
- The sitemap contains at least the scanned public page or its canonical equivalent.
- The public URL exposes the corrected crawl/search/answer signal in rendered HTML or reachable public files.
- The change should be visible to a fresh unauthenticated request and likely improve the related FreeScan SEO / AEO check on rescan.
- A fresh FreeScan rescan should show this check improved or passing after deployment.
## Output
Return a structured response with these headings: Findings, Changes Made, Verification Results, Rescan Expectation, Rollback Notes, 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.
- Prefer editing the canonical source of the page over patching built output, generated files, CDN-cached HTML, or minified assets.
- Do not make a cosmetic or placeholder change just to satisfy the scanner; the public page should be materially better for visitors, crawlers, or assistive technology.
- 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

SEO / AEO

Priority 24

Add an LLM-readable product file

-5 rule pts

What failed

The scan did not find llms.txt or .well-known/llms.txt.

Evidence

HTTP 404 returned for llms_txt.

Priority

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

Why it matters

A short LLM-readable file can help answer engines and AI tools summarize your product accurately.

How to fix it

Add /llms.txt or /.well-known/llms.txt with the product name, audience, value proposition, and key public links.

Agent Prompt

## Role
Act as a focused technical SEO, AEO, and crawlability remediation expert who can inspect the public page and safely improve the underlying implementation.
## Inputs
- Primary context: Improve promptplanner.app at https://promptplanner.app.
- Scanner check ID: seo_llms_txt.
- Fix title: Add an LLM-readable product file.
- Scanner check: LLM-readable file.
- Category: SEO / AEO.
- Status: fail.
- Severity: low.
- Priority: 24; lower numbers are more urgent.
- Score impact: 5 rule points lost.
- Evidence: HTTP 404 returned for llms_txt.
- What needs attention: The scan did not find llms.txt or .well-known/llms.txt.
- Why it matters: A short LLM-readable file can help answer engines and AI tools summarize your product accurately.
- 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.
- Likely places to inspect: public /llms.txt or /.well-known/llms.txt route/file and source content used to describe the product; metadata/head configuration, canonical URL logic, robots and sitemap routes, structured data blocks, page copy, headings, and internal navigation; the route, template, component, CMS entry, theme file, or static page that renders the scanned URL; shared layout, metadata, routing, middleware, server, CDN, or hosting configuration if the issue is not in page content; existing tests, build scripts, preview commands, and deployment notes before choosing verification steps.
## Task
Use the provided context to safely complete this workflow: Add /llms.txt or /.well-known/llms.txt with the product name, audience, value proposition, and key public links.
First reproduce or verify the issue from the public page and available implementation source. Then make the smallest stack-appropriate change that fixes the scanner signal and improves the real user experience.
Use this check-specific implementation guide:
- Add a concise text file with product name, audience, value proposition, important public links, and any relevant docs/support URLs.
- Keep it factual and aligned with visible public content.
- Keep all metadata, headings, schema, canonical URLs, and visible copy consistent with the same public facts.
- Use accurate, crawlable, human-visible content as the source for search and answer-engine improvements.
- Keep the implementation stack-appropriate: use the existing framework, CMS, hosting provider, design system, and deployment workflow already in the project.
Acceptance criteria for this fix:
- /llms.txt or /.well-known/llms.txt returns HTTP 200 publicly.
- The content is short, accurate, and useful for AI tools without exposing private details.
- The public URL exposes the corrected crawl/search/answer signal in rendered HTML or reachable public files.
- The change should be visible to a fresh unauthenticated request and likely improve the related FreeScan SEO / AEO check on rescan.
- A fresh FreeScan rescan should show this check improved or passing after deployment.
## Output
Return a structured response with these headings: Findings, Changes Made, Verification Results, Rescan Expectation, Rollback Notes, 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.
- Prefer editing the canonical source of the page over patching built output, generated files, CDN-cached HTML, or minified assets.
- Do not make a cosmetic or placeholder change just to satisfy the scanner; the public page should be materially better for visitors, crawlers, or assistive technology.
- 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.

77/100

8 pass

3 fail

0 unknown

SEO / AEO

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

medium

robots.txt reachability

-7 rule pts

HTTP 404 returned for robots_txt.

medium

sitemap.xml reachability

-7 rule pts

HTTP 404 returned for sitemap_xml.

low

LLM-readable file

-5 rule pts

HTTP 404 returned for llms_txt.

76/100

5 pass

1 fail

0 unknown

Security

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

high

Common security headers

-18 rule pts

Detected 0 of 5 common public security headers.

100/100

8 pass

0 fail

0 unknown

Accessibility

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

No failed checks in this category.

85/100

9 pass

2 fail

0 unknown

Design

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

medium

Rendered layout ergonomics

-9 rule pts

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

low

Spacing consistency

-7 rule pts

Detected 0 spacing class/style signal(s).

Full check list

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

Failed checks

These checks need attention.

fail

medium

SEO / AEO

robots.txt reachability

0/7

HTTP 404 returned for robots_txt.

Failed: earned 0 of 7 points.

Priority: Priority 14: fix during launch polish.

Why it matters: A reachable robots.txt helps crawlers understand what they can index before launch traffic arrives.

Fix: Add a public /robots.txt file and make sure it returns HTTP 200 without blocking the landing page.

Agent Prompt

## Role
Act as a focused technical SEO, AEO, and crawlability remediation expert who can inspect the public page and safely improve the underlying implementation.
## Inputs
- Primary context: Improve promptplanner.app at https://promptplanner.app.
- Scanner check ID: seo_robots_txt.
- Fix title: Publish robots.txt.
- Scanner check: robots.txt reachability.
- Category: SEO / AEO.
- Status: fail.
- Severity: medium.
- Priority: 14; lower numbers are more urgent.
- Score impact: 7 of 7 rule points lost.
- Evidence: HTTP 404 returned for robots_txt.
- What needs attention: The standard crawler instruction file was not reachable.
- Why it matters: A reachable robots.txt helps crawlers understand what they can index before launch traffic arrives.
- 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.
- Likely places to inspect: public robots.txt file or route, deployment static assets, and crawler directives for the landing page; metadata/head configuration, canonical URL logic, robots and sitemap routes, structured data blocks, page copy, headings, and internal navigation; the route, template, component, CMS entry, theme file, or static page that renders the scanned URL; shared layout, metadata, routing, middleware, server, CDN, or hosting configuration if the issue is not in page content; existing tests, build scripts, preview commands, and deployment notes before choosing verification steps.
## Task
Use the provided context to safely complete this workflow: Add a public /robots.txt file and make sure it returns HTTP 200 without blocking the landing page.
First reproduce or verify the issue from the public page and available implementation source. Then make the smallest stack-appropriate change that fixes the scanner signal and improves the real user experience.
Use this check-specific implementation guide:
- Publish a reachable robots.txt that permits crawling of the public landing page.
- Only block private, admin, search-result, staging, or low-value paths intentionally.
- Keep all metadata, headings, schema, canonical URLs, and visible copy consistent with the same public facts.
- Use accurate, crawlable, human-visible content as the source for search and answer-engine improvements.
- Keep the implementation stack-appropriate: use the existing framework, CMS, hosting provider, design system, and deployment workflow already in the project.
Acceptance criteria for this fix:
- /robots.txt returns HTTP 200 publicly.
- The scanned public page is not blocked by robots.txt.
- The public URL exposes the corrected crawl/search/answer signal in rendered HTML or reachable public files.
- The change should be visible to a fresh unauthenticated request and likely improve the related FreeScan SEO / AEO check on rescan.
- A fresh FreeScan rescan should show this check improved or passing after deployment.
## Output
Return a structured response with these headings: Findings, Changes Made, Verification Results, Rescan Expectation, Rollback Notes, 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.
- Prefer editing the canonical source of the page over patching built output, generated files, CDN-cached HTML, or minified assets.
- Do not make a cosmetic or placeholder change just to satisfy the scanner; the public page should be materially better for visitors, crawlers, or assistive technology.
- Verify the result with the smallest reliable test, build, browser check, or manual inspection available.
## Safety
- Do not request, expose, or reproduce sensitive data.
- Redact private details from examples unless the user explicitly says they are safe to include.
- Do not use credentials, cookies, authenticated data, hidden form values, or private response bodies.
- Do not weaken security headers, authentication, authorization, privacy controls, accessibility, or error handling to make the scan pass.

fail

medium

SEO / AEO

sitemap.xml reachability

0/7

HTTP 404 returned for sitemap_xml.

Failed: earned 0 of 7 points.

Priority: Priority 15: fix during launch polish.

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

Fix: Add /sitemap.xml with your public URLs and confirm it returns HTTP 200.

Agent Prompt

## Role
Act as a focused technical SEO, AEO, and crawlability remediation expert who can inspect the public page and safely improve the underlying implementation.
## Inputs
- Primary context: Improve promptplanner.app at https://promptplanner.app.
- Scanner check ID: seo_sitemap_xml.
- Fix title: Publish sitemap.xml.
- Scanner check: sitemap.xml reachability.
- Category: SEO / AEO.
- Status: fail.
- Severity: medium.
- Priority: 15; lower numbers are more urgent.
- Score impact: 7 of 7 rule points lost.
- Evidence: HTTP 404 returned for sitemap_xml.
- What needs attention: The sitemap file was not reachable.
- 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.
- Likely places to inspect: robots.txt Sitemap directives, static sitemap files, dynamic sitemap routes, sitemap indexes, canonical URL generation, and deployment output; metadata/head configuration, canonical URL logic, robots and sitemap routes, structured data blocks, page copy, headings, and internal navigation; the route, template, component, CMS entry, theme file, or static page that renders the scanned URL; shared layout, metadata, routing, middleware, server, CDN, or hosting configuration if the issue is not in page content; existing tests, build scripts, preview commands, and deployment notes before choosing verification steps.
## Task
Use the provided context to safely complete this workflow: Add /sitemap.xml with your public URLs and confirm it returns HTTP 200.
First reproduce or verify the issue from the public page and available implementation source. Then make the smallest stack-appropriate change that fixes the scanner signal and improves the real user experience.
Use this check-specific implementation guide:
- Provide a reachable sitemap URL with valid urlset or sitemapindex XML. Preserve an existing robots.txt Sitemap directive such as /sitemap_index.xml when it is intentional and valid.
- Include canonical public URLs and avoid localhost, staging, private, noindex, or duplicate URLs.
- Keep all metadata, headings, schema, canonical URLs, and visible copy consistent with the same public facts.
- Use accurate, crawlable, human-visible content as the source for search and answer-engine improvements.
- Keep the implementation stack-appropriate: use the existing framework, CMS, hosting provider, design system, and deployment workflow already in the project.
Acceptance criteria for this fix:
- The sitemap URL declared in robots.txt, or /sitemap.xml when no directive exists, returns HTTP 200 with a valid urlset or sitemapindex root.
- The sitemap contains at least the scanned public page or its canonical equivalent.
- The public URL exposes the corrected crawl/search/answer signal in rendered HTML or reachable public files.
- The change should be visible to a fresh unauthenticated request and likely improve the related FreeScan SEO / AEO check on rescan.
- A fresh FreeScan rescan should show this check improved or passing after deployment.
## Output
Return a structured response with these headings: Findings, Changes Made, Verification Results, Rescan Expectation, Rollback Notes, 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.
- Prefer editing the canonical source of the page over patching built output, generated files, CDN-cached HTML, or minified assets.
- Do not make a cosmetic or placeholder change just to satisfy the scanner; the public page should be materially better for visitors, crawlers, or assistive technology.
- 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

SEO / AEO

LLM-readable file

0/5

HTTP 404 returned for llms_txt.

Failed: earned 0 of 5 points.

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

Why it matters: A short LLM-readable file can help answer engines and AI tools summarize your product accurately.

Fix: Add /llms.txt or /.well-known/llms.txt with the product name, audience, value proposition, and key public links.

Agent Prompt

## Role
Act as a focused technical SEO, AEO, and crawlability remediation expert who can inspect the public page and safely improve the underlying implementation.
## Inputs
- Primary context: Improve promptplanner.app at https://promptplanner.app.
- Scanner check ID: seo_llms_txt.
- Fix title: Add an LLM-readable product file.
- Scanner check: LLM-readable file.
- Category: SEO / AEO.
- Status: fail.
- Severity: low.
- Priority: 24; lower numbers are more urgent.
- Score impact: 5 of 5 rule points lost.
- Evidence: HTTP 404 returned for llms_txt.
- What needs attention: The scan did not find llms.txt or .well-known/llms.txt.
- Why it matters: A short LLM-readable file can help answer engines and AI tools summarize your product accurately.
- 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.
- Likely places to inspect: public /llms.txt or /.well-known/llms.txt route/file and source content used to describe the product; metadata/head configuration, canonical URL logic, robots and sitemap routes, structured data blocks, page copy, headings, and internal navigation; the route, template, component, CMS entry, theme file, or static page that renders the scanned URL; shared layout, metadata, routing, middleware, server, CDN, or hosting configuration if the issue is not in page content; existing tests, build scripts, preview commands, and deployment notes before choosing verification steps.
## Task
Use the provided context to safely complete this workflow: Add /llms.txt or /.well-known/llms.txt with the product name, audience, value proposition, and key public links.
First reproduce or verify the issue from the public page and available implementation source. Then make the smallest stack-appropriate change that fixes the scanner signal and improves the real user experience.
Use this check-specific implementation guide:
- Add a concise text file with product name, audience, value proposition, important public links, and any relevant docs/support URLs.
- Keep it factual and aligned with visible public content.
- Keep all metadata, headings, schema, canonical URLs, and visible copy consistent with the same public facts.
- Use accurate, crawlable, human-visible content as the source for search and answer-engine improvements.
- Keep the implementation stack-appropriate: use the existing framework, CMS, hosting provider, design system, and deployment workflow already in the project.
Acceptance criteria for this fix:
- /llms.txt or /.well-known/llms.txt returns HTTP 200 publicly.
- The content is short, accurate, and useful for AI tools without exposing private details.
- The public URL exposes the corrected crawl/search/answer signal in rendered HTML or reachable public files.
- The change should be visible to a fresh unauthenticated request and likely improve the related FreeScan SEO / AEO check on rescan.
- A fresh FreeScan rescan should show this check improved or passing after deployment.
## Output
Return a structured response with these headings: Findings, Changes Made, Verification Results, Rescan Expectation, Rollback Notes, 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.
- Prefer editing the canonical source of the page over patching built output, generated files, CDN-cached HTML, or minified assets.
- Do not make a cosmetic or placeholder change just to satisfy the scanner; the public page should be materially better for visitors, crawlers, or assistive technology.
- 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

0/18

Detected 0 of 5 common public security headers.

Failed: earned 0 of 18 points.

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.

Agent Prompt

## Role
Act as a focused public web security remediation expert who can inspect the public page and safely improve the underlying implementation.
## Inputs
- Primary context: Improve promptplanner.app at https://promptplanner.app.
- Scanner check ID: security_common_headers.
- 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: 18 of 18 rule points lost.
- Evidence: Detected 0 of 5 common public security headers.
- 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.
- Likely places to inspect: hosting headers, server middleware, edge/proxy config, CDN rules, and framework security header configuration; server, edge, CDN, hosting, proxy, form action, asset URL, cookie, and public file access configuration; the route, template, component, CMS entry, theme file, or static page that renders the scanned URL; shared layout, metadata, routing, middleware, server, CDN, or hosting configuration if the issue is not in page content; existing tests, build scripts, preview commands, and deployment notes before choosing verification steps.
## 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.
First reproduce or verify the issue from the public page and available implementation source. Then make the smallest stack-appropriate change that fixes the scanner signal and improves the real user experience.
Use this check-specific implementation guide:
- Add missing common browser protection headers with values appropriate for the site.
- Treat an existing CSP frame-ancestors directive as valid frame protection; preserve the directive and its allowed origins exactly instead of adding or substituting X-Frame-Options.
- Test CSP or frame policies carefully so they do not break scripts, images, analytics, payments, embeds, or auth.
- Prefer narrow, production-safe security configuration changes over blanket disables or permissive rules.
- Preserve authentication, authorization, private paths, and sensitive file protections while fixing the public launch page.
- Keep the implementation stack-appropriate: use the existing framework, CMS, hosting provider, design system, and deployment workflow already in the project.
Acceptance criteria for this fix:
- Important security headers are visible on the public response.
- Any existing CSP frame-ancestors directive and its allowed origins remain unchanged.
- The page still renders and key flows still work after header changes.
- The public URL keeps legitimate visitors and assets working while removing the reported browser-side or public exposure risk.
- The change does not weaken security headers, authentication, authorization, or private route protections.
- A fresh FreeScan rescan should show this check improved or passing after deployment.
## Output
Return a structured response with these headings: Findings, Changes Made, Verification Results, Rescan Expectation, Rollback Notes, 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.
- Prefer editing the canonical source of the page over patching built output, generated files, CDN-cached HTML, or minified assets.
- Do not make a cosmetic or placeholder change just to satisfy the scanner; the public page should be materially better for visitors, crawlers, or assistive technology.
- If an existing Content-Security-Policy contains a frame-ancestors directive, preserve that directive exactly, including its allowed origins, unless the site owner explicitly asks to change it. Do not replace it with X-Frame-Options merely to satisfy this scan.
- 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

Spacing consistency

0/7

Detected 0 spacing class/style signal(s).

Failed: earned 0 of 7 points.

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

Why it matters: Consistent spacing helps the page feel deliberate and easier to scan.

Fix: Use consistent section padding, gaps, and margins across repeated content blocks.

Agent Prompt

## Role
Act as a focused conversion-focused frontend quality remediation expert who can inspect the public page and safely improve the underlying implementation.
## Inputs
- Primary context: Improve promptplanner.app at https://promptplanner.app.
- Scanner check ID: design_spacing_consistency.
- Fix title: Make spacing more consistent.
- Scanner check: Spacing consistency.
- Category: Design.
- Status: fail.
- Severity: low.
- Priority: 25; lower numbers are more urgent.
- Score impact: 7 of 7 rule points lost.
- Evidence: Detected 0 spacing class/style signal(s).
- What needs attention: The page exposes few consistent spacing signals in class or inline styles.
- Why it matters: Consistent spacing helps the page feel deliberate and easier to scan.
- 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.
- Likely places to inspect: layout spacing tokens, component padding, section gaps, card grids, mobile breakpoints, and repeated patterns; page layout, responsive CSS, component states, copy hierarchy, CTA placement, spacing tokens, rendered console output, and performance-sensitive assets; the route, template, component, CMS entry, theme file, or static page that renders the scanned URL; shared layout, metadata, routing, middleware, server, CDN, or hosting configuration if the issue is not in page content; existing tests, build scripts, preview commands, and deployment notes before choosing verification steps.
## Task
Use the provided context to safely complete this workflow: Use consistent section padding, gaps, and margins across repeated content blocks.
First reproduce or verify the issue from the public page and available implementation source. Then make the smallest stack-appropriate change that fixes the scanner signal and improves the real user experience.
Use this check-specific implementation guide:
- Normalize spacing using existing tokens or local conventions.
- Avoid one-off spacing hacks that create new breakpoints or layout shifts.
- Improve the actual rendered page at mobile and desktop sizes, not only the source code shape.
- Preserve core conversion flows while making layout, hierarchy, readability, or runtime health better.
- Keep the implementation stack-appropriate: use the existing framework, CMS, hosting provider, design system, and deployment workflow already in the project.
Acceptance criteria for this fix:
- Spacing feels consistent across related sections and viewport sizes.
- No important UI shifts or overlaps after the change.
- The rendered page is visually stable and usable on mobile and desktop viewports.
- The fix does not hide content, break CTAs, introduce console errors, or reduce clarity for visitors.
- A fresh FreeScan rescan should show this check improved or passing after deployment.
## Output
Return a structured response with these headings: Findings, Changes Made, Verification Results, Rescan Expectation, Rollback Notes, 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.
- Prefer editing the canonical source of the page over patching built output, generated files, CDN-cached HTML, or minified assets.
- Do not make a cosmetic or placeholder change just to satisfy the scanner; the public page should be materially better for visitors, crawlers, or assistive technology.
- Verify the result with the smallest reliable test, build, browser check, or manual inspection available.
## Safety
- Do not request, expose, or reproduce sensitive data.
- Redact private details from examples unless the user explicitly says they are safe to include.
- Do not use credentials, cookies, authenticated data, hidden form values, or private response bodies.
- Do not weaken security headers, authentication, authorization, privacy controls, accessibility, or error handling to make the scan pass.

fail

medium

Design

Rendered layout ergonomics

0/9

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

Failed: earned 0 of 9 points.

Priority: Priority 13: fix during launch polish.

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

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

Agent Prompt

## Role
Act as a focused conversion-focused frontend quality remediation expert who can inspect the public page and safely improve the underlying implementation.
## Inputs
- Primary context: Improve promptplanner.app at https://promptplanner.app.
- Scanner check ID: design_rendered_layout.
- Fix title: Fix rendered layout ergonomics.
- Scanner check: Rendered layout ergonomics.
- Category: Design.
- Status: fail.
- Severity: medium.
- Priority: 13; lower numbers are more urgent.
- Score impact: 9 of 9 rule points lost.
- Evidence: Horizontal overflow: 0px. Small tap targets: 11.
- What needs attention: The browser-rendered page has layout or tap-target issues.
- Why it matters: Horizontal overflow and tiny tap targets make the page feel broken on real devices, especially for mobile visitors.
- Status-specific guidance: A public check reported a failure. Reproduce or inspect the issue first, then make the smallest safe fix.
- Audience or recipient: The site owner, builder, or marketing team responsible for improving this public page.
- Constraints, examples, or source material: Treat the live URL as the public target to inspect, not as the only source of truth. When repository, CMS, or hosting access is available, use that implementation context before changing anything.
- Target outcome: After the fix is deployed and the public page is rescanned, this specific check should improve or pass without lowering other SEO / AEO, security, accessibility, or design signals.
- Likely places to inspect: mobile viewport, horizontal overflow sources, tap target sizes, fixed-position elements, menus, forms, and embeds; page layout, responsive CSS, component states, copy hierarchy, CTA placement, spacing tokens, rendered console output, and performance-sensitive assets; the route, template, component, CMS entry, theme file, or static page that renders the scanned URL; shared layout, metadata, routing, middleware, server, CDN, or hosting configuration if the issue is not in page content; existing tests, build scripts, preview commands, and deployment notes before choosing verification steps.
## Task
Use the provided context to safely complete this workflow: Remove elements wider than the viewport, add responsive constraints, and make important links, buttons, inputs, and controls at least 40px tall and wide where possible.
First reproduce or verify the issue from the public page and available implementation source. Then make the smallest stack-appropriate change that fixes the scanner signal and improves the real user experience.
Use this check-specific implementation guide:
- Constrain overflowing elements and increase small important tap targets where possible.
- Preserve layout intent while making the rendered page usable on real devices.
- Improve the actual rendered page at mobile and desktop sizes, not only the source code shape.
- Preserve core conversion flows while making layout, hierarchy, readability, or runtime health better.
- Keep the implementation stack-appropriate: use the existing framework, CMS, hosting provider, design system, and deployment workflow already in the project.
Acceptance criteria for this fix:
- The rendered page has no meaningful horizontal overflow.
- Important links, buttons, inputs, and controls are comfortably tappable.
- The rendered page is visually stable and usable on mobile and desktop viewports.
- The fix does not hide content, break CTAs, introduce console errors, or reduce clarity for visitors.
- A fresh FreeScan rescan should show this check improved or passing after deployment.
## Output
Return a structured response with these headings: Findings, Changes Made, Verification Results, Rescan Expectation, Rollback Notes, 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.
- Prefer editing the canonical source of the page over patching built output, generated files, CDN-cached HTML, or minified assets.
- Do not make a cosmetic or placeholder change just to satisfy the scanner; the public page should be materially better for visitors, crawlers, or assistive technology.
- 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

promptplanner.app website audit report

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

Public report link

Markdown report

# promptplanner.app Website Scan

Scanned URL: [https://promptplanner.app](https://promptplanner.app)
Report URL: /scan/promptplanner-app-85-launch-readiness-report-32cafacd
Created: 2026-06-29T13:57:13.767Z

## Score Summary

- Overall: 85/100
- SEO / AEO: 77/100
- Security: 76/100
- Accessibility: 100/100
- Design: 85/100

## Launch Readiness

Close to ready (Strong).

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

## Prioritized Fixes

### 1. Add common public security headers

- Category: Security
- Status: fail
- Severity: high
- Rule points lost: 18
- Evidence: Detected 0 of 5 common public security headers.
- 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.

### 2. Fix rendered layout ergonomics

- Category: Design
- Status: fail
- Severity: medium
- Rule points lost: 9
- Evidence: Horizontal overflow: 0px. Small tap targets: 11.
- Why it matters: Horizontal overflow and tiny tap targets make the page feel broken on real devices, especially for mobile visitors.
- Fix: Remove elements wider than the viewport, add responsive constraints, and make important links, buttons, inputs, and controls at least 40px tall and wide where possible.

### 3. Publish robots.txt

- Category: SEO / AEO
- Status: fail
- Severity: medium
- Rule points lost: 7
- Evidence: HTTP 404 returned for robots_txt.
- Why it matters: A reachable robots.txt helps crawlers understand what they can index before launch traffic arrives.
- Fix: Add a public /robots.txt file and make sure it returns HTTP 200 without blocking the landing page.

### 4. Publish sitemap.xml

- Category: SEO / AEO
- Status: fail
- Severity: medium
- Rule points lost: 7
- Evidence: HTTP 404 returned for sitemap_xml.
- Why it matters: A sitemap helps search engines discover the landing page and related public pages sooner.
- Fix: Add /sitemap.xml with your public URLs and confirm it returns HTTP 200.

### 5. Add an LLM-readable product file

- Category: SEO / AEO
- Status: fail
- Severity: low
- Rule points lost: 5
- Evidence: HTTP 404 returned for llms_txt.
- Why it matters: A short LLM-readable file can help answer engines and AI tools summarize your product accurately.
- Fix: Add /llms.txt or /.well-known/llms.txt with the product name, audience, value proposition, and key public links.

## Opportunities

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

- Impact: high
- Category: SEO / AEO
- Evidence: Pricing signals: 4. Use-case signals: 6. 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: Detected 1 important internal link(s): privacy/.
- 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 1 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.

### Add an optional LLM-readable site summary

- Impact: low
- Category: SEO / AEO
- Evidence: HTTP 404 returned for llms_txt.
- Why it matters: This is not required for Google AI features, but a concise public markdown summary can help AI agents and internal tools understand key pages.
- Next step: Publish a short llms.txt with product facts, audience, key public links, docs, pricing, support, and usage boundaries.

### Review snippet and preview controls

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

### Polish rendered responsive ergonomics

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

## Insights

### Crawlability needs review

- Category: SEO / AEO
- Evidence: HTTP 200. robots.txt: not reachable. 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: 591. H1 count: 1. Audience signals: 5. 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: PromptPlanner - Organize and reuse AI prompts on your Mac. H1: Organize and reuse  AI prompts  across projects on your Mac. Schema types: SoftwareApplication.
- Interpretation: The stronger and more consistent these entity signals are, the easier it is for search and answer systems to identify the brand, product category, and page purpose.
- Recommended use: Keep the title, H1, meta description, Open Graph, schema, footer, and about/pricing/docs pages aligned around the same product facts.

### Structured data is present

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

### Weakest score area

- Category: Security
- Evidence: SEO / AEO: 77/100. Security: 76/100. Accessibility: 100/100. Design: 85/100
- Interpretation: The weakest area is Security, 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 not found

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

### Rendered page experience snapshot

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

### Rendered speed snapshot

- Category: Design
- Evidence: DOMContentLoaded: 546ms. Load complete: 0ms. First contentful paint: 640ms. Resources: 10. Scripts: 1. Images: 7. Third-party origins: 2. 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: 0. Critical: 0. Serious: 0. Top rules: none.
- 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 promptplanner.app without re-entering the URL. The previous report stays saved so the next result can be compared against it.

## Role Act as a focused public web security remediation expert who can inspect the public page and safely improve the underlying implementation. ## Inputs - Primary context: Improve promptplanner.app at https://promptplanner.app. - Scanner check ID: security_common_headers. - 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: 18 rule points lost. - Evidence: Detected 0 of 5 common public security headers. - 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. - Likely places to inspect: hosting headers, server middleware, edge/proxy config, CDN rules, and framework security header configuration; server, edge, CDN, hosting, proxy, form action, asset URL, cookie, and public file access configuration; the route, template, component, CMS entry, theme file, or static page that renders the scanned URL; shared layout, metadata, routing, middleware, server, CDN, or hosting configuration if the issue is not in page content; existing tests, build scripts, preview commands, and deployment notes before choosing verification steps. ## 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. First reproduce or verify the issue from the public page and available implementation source. Then make the smallest stack-appropriate change that fixes the scanner signal and improves the real user experience. Use this check-specific implementation guide: - Add missing common browser protection headers with values appropriate for the site. - Treat an existing CSP frame-ancestors directive as valid frame protection; preserve the directive and its allowed origins exactly instead of adding or substituting X-Frame-Options. - Test CSP or frame policies carefully so they do not break scripts, images, analytics, payments, embeds, or auth. - Prefer narrow, production-safe security configuration changes over blanket disables or permissive rules. - Preserve authentication, authorization, private paths, and sensitive file protections while fixing the public launch page. - Keep the implementation stack-appropriate: use the existing framework, CMS, hosting provider, design system, and deployment workflow already in the project. Acceptance criteria for this fix: - Important security headers are visible on the public response. - Any existing CSP frame-ancestors directive and its allowed origins remain unchanged. - The page still renders and key flows still work after header changes. - The public URL keeps legitimate visitors and assets working while removing the reported browser-side or public exposure risk. - The change does not weaken security headers, authentication, authorization, or private route protections. - A fresh FreeScan rescan should show this check improved or passing after deployment. ## Output Return a structured response with these headings: Findings, Changes Made, Verification Results, Rescan Expectation, Rollback Notes, 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. - Prefer editing the canonical source of the page over patching built output, generated files, CDN-cached HTML, or minified assets. - Do not make a cosmetic or placeholder change just to satisfy the scanner; the public page should be materially better for visitors, crawlers, or assistive technology. - If an existing Content-Security-Policy contains a frame-ancestors directive, preserve that directive exactly, including its allowed origins, unless the site owner explicitly asks to change it. Do not replace it with X-Frame-Options merely to satisfy this scan. - 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.

## Role Act as a focused conversion-focused frontend quality remediation expert who can inspect the public page and safely improve the underlying implementation. ## Inputs - Primary context: Improve promptplanner.app at https://promptplanner.app. - Scanner check ID: design_rendered_layout. - Fix title: Fix rendered layout ergonomics. - Scanner check: Rendered layout ergonomics. - Category: Design. - Status: fail. - Severity: medium. - Priority: 13; lower numbers are more urgent. - Score impact: 9 rule points lost. - Evidence: Horizontal overflow: 0px. Small tap targets: 11. - What needs attention: The browser-rendered page has layout or tap-target issues. - Why it matters: Horizontal overflow and tiny tap targets make the page feel broken on real devices, especially for mobile visitors. - Status-specific guidance: A public check reported a failure. Reproduce or inspect the issue first, then make the smallest safe fix. - Audience or recipient: The site owner, builder, or marketing team responsible for improving this public page. - Constraints, examples, or source material: Treat the live URL as the public target to inspect, not as the only source of truth. When repository, CMS, or hosting access is available, use that implementation context before changing anything. - Target outcome: After the fix is deployed and the public page is rescanned, this specific check should improve or pass without lowering other SEO / AEO, security, accessibility, or design signals. - Likely places to inspect: mobile viewport, horizontal overflow sources, tap target sizes, fixed-position elements, menus, forms, and embeds; page layout, responsive CSS, component states, copy hierarchy, CTA placement, spacing tokens, rendered console output, and performance-sensitive assets; the route, template, component, CMS entry, theme file, or static page that renders the scanned URL; shared layout, metadata, routing, middleware, server, CDN, or hosting configuration if the issue is not in page content; existing tests, build scripts, preview commands, and deployment notes before choosing verification steps. ## Task Use the provided context to safely complete this workflow: Remove elements wider than the viewport, add responsive constraints, and make important links, buttons, inputs, and controls at least 40px tall and wide where possible. First reproduce or verify the issue from the public page and available implementation source. Then make the smallest stack-appropriate change that fixes the scanner signal and improves the real user experience. Use this check-specific implementation guide: - Constrain overflowing elements and increase small important tap targets where possible. - Preserve layout intent while making the rendered page usable on real devices. - Improve the actual rendered page at mobile and desktop sizes, not only the source code shape. - Preserve core conversion flows while making layout, hierarchy, readability, or runtime health better. - Keep the implementation stack-appropriate: use the existing framework, CMS, hosting provider, design system, and deployment workflow already in the project. Acceptance criteria for this fix: - The rendered page has no meaningful horizontal overflow. - Important links, buttons, inputs, and controls are comfortably tappable. - The rendered page is visually stable and usable on mobile and desktop viewports. - The fix does not hide content, break CTAs, introduce console errors, or reduce clarity for visitors. - A fresh FreeScan rescan should show this check improved or passing after deployment. ## Output Return a structured response with these headings: Findings, Changes Made, Verification Results, Rescan Expectation, Rollback Notes, 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. - Prefer editing the canonical source of the page over patching built output, generated files, CDN-cached HTML, or minified assets. - Do not make a cosmetic or placeholder change just to satisfy the scanner; the public page should be materially better for visitors, crawlers, or assistive technology. - 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.

## Role Act as a focused technical SEO, AEO, and crawlability remediation expert who can inspect the public page and safely improve the underlying implementation. ## Inputs - Primary context: Improve promptplanner.app at https://promptplanner.app. - Scanner check ID: seo_robots_txt. - Fix title: Publish robots.txt. - Scanner check: robots.txt reachability. - Category: SEO / AEO. - Status: fail. - Severity: medium. - Priority: 14; lower numbers are more urgent. - Score impact: 7 rule points lost. - Evidence: HTTP 404 returned for robots_txt. - What needs attention: The standard crawler instruction file was not reachable. - Why it matters: A reachable robots.txt helps crawlers understand what they can index before launch traffic arrives. - 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. - Likely places to inspect: public robots.txt file or route, deployment static assets, and crawler directives for the landing page; metadata/head configuration, canonical URL logic, robots and sitemap routes, structured data blocks, page copy, headings, and internal navigation; the route, template, component, CMS entry, theme file, or static page that renders the scanned URL; shared layout, metadata, routing, middleware, server, CDN, or hosting configuration if the issue is not in page content; existing tests, build scripts, preview commands, and deployment notes before choosing verification steps. ## Task Use the provided context to safely complete this workflow: Add a public /robots.txt file and make sure it returns HTTP 200 without blocking the landing page. First reproduce or verify the issue from the public page and available implementation source. Then make the smallest stack-appropriate change that fixes the scanner signal and improves the real user experience. Use this check-specific implementation guide: - Publish a reachable robots.txt that permits crawling of the public landing page. - Only block private, admin, search-result, staging, or low-value paths intentionally. - Keep all metadata, headings, schema, canonical URLs, and visible copy consistent with the same public facts. - Use accurate, crawlable, human-visible content as the source for search and answer-engine improvements. - Keep the implementation stack-appropriate: use the existing framework, CMS, hosting provider, design system, and deployment workflow already in the project. Acceptance criteria for this fix: - /robots.txt returns HTTP 200 publicly. - The scanned public page is not blocked by robots.txt. - The public URL exposes the corrected crawl/search/answer signal in rendered HTML or reachable public files. - The change should be visible to a fresh unauthenticated request and likely improve the related FreeScan SEO / AEO check on rescan. - A fresh FreeScan rescan should show this check improved or passing after deployment. ## Output Return a structured response with these headings: Findings, Changes Made, Verification Results, Rescan Expectation, Rollback Notes, 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. - Prefer editing the canonical source of the page over patching built output, generated files, CDN-cached HTML, or minified assets. - Do not make a cosmetic or placeholder change just to satisfy the scanner; the public page should be materially better for visitors, crawlers, or assistive technology. - 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.

## Role Act as a focused technical SEO, AEO, and crawlability remediation expert who can inspect the public page and safely improve the underlying implementation. ## Inputs - Primary context: Improve promptplanner.app at https://promptplanner.app. - Scanner check ID: seo_sitemap_xml. - Fix title: Publish sitemap.xml. - Scanner check: sitemap.xml reachability. - Category: SEO / AEO. - Status: fail. - Severity: medium. - Priority: 15; lower numbers are more urgent. - Score impact: 7 rule points lost. - Evidence: HTTP 404 returned for sitemap_xml. - What needs attention: The sitemap file was not reachable. - 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. - Likely places to inspect: robots.txt Sitemap directives, static sitemap files, dynamic sitemap routes, sitemap indexes, canonical URL generation, and deployment output; metadata/head configuration, canonical URL logic, robots and sitemap routes, structured data blocks, page copy, headings, and internal navigation; the route, template, component, CMS entry, theme file, or static page that renders the scanned URL; shared layout, metadata, routing, middleware, server, CDN, or hosting configuration if the issue is not in page content; existing tests, build scripts, preview commands, and deployment notes before choosing verification steps. ## Task Use the provided context to safely complete this workflow: Add /sitemap.xml with your public URLs and confirm it returns HTTP 200. First reproduce or verify the issue from the public page and available implementation source. Then make the smallest stack-appropriate change that fixes the scanner signal and improves the real user experience. Use this check-specific implementation guide: - Provide a reachable sitemap URL with valid urlset or sitemapindex XML. Preserve an existing robots.txt Sitemap directive such as /sitemap_index.xml when it is intentional and valid. - Include canonical public URLs and avoid localhost, staging, private, noindex, or duplicate URLs. - Keep all metadata, headings, schema, canonical URLs, and visible copy consistent with the same public facts. - Use accurate, crawlable, human-visible content as the source for search and answer-engine improvements. - Keep the implementation stack-appropriate: use the existing framework, CMS, hosting provider, design system, and deployment workflow already in the project. Acceptance criteria for this fix: - The sitemap URL declared in robots.txt, or /sitemap.xml when no directive exists, returns HTTP 200 with a valid urlset or sitemapindex root. - The sitemap contains at least the scanned public page or its canonical equivalent. - The public URL exposes the corrected crawl/search/answer signal in rendered HTML or reachable public files. - The change should be visible to a fresh unauthenticated request and likely improve the related FreeScan SEO / AEO check on rescan. - A fresh FreeScan rescan should show this check improved or passing after deployment. ## Output Return a structured response with these headings: Findings, Changes Made, Verification Results, Rescan Expectation, Rollback Notes, 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. - Prefer editing the canonical source of the page over patching built output, generated files, CDN-cached HTML, or minified assets. - Do not make a cosmetic or placeholder change just to satisfy the scanner; the public page should be materially better for visitors, crawlers, or assistive technology. - 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.

## Role Act as a focused technical SEO, AEO, and crawlability remediation expert who can inspect the public page and safely improve the underlying implementation. ## Inputs - Primary context: Improve promptplanner.app at https://promptplanner.app. - Scanner check ID: seo_llms_txt. - Fix title: Add an LLM-readable product file. - Scanner check: LLM-readable file. - Category: SEO / AEO. - Status: fail. - Severity: low. - Priority: 24; lower numbers are more urgent. - Score impact: 5 rule points lost. - Evidence: HTTP 404 returned for llms_txt. - What needs attention: The scan did not find llms.txt or .well-known/llms.txt. - Why it matters: A short LLM-readable file can help answer engines and AI tools summarize your product accurately. - 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. - Likely places to inspect: public /llms.txt or /.well-known/llms.txt route/file and source content used to describe the product; metadata/head configuration, canonical URL logic, robots and sitemap routes, structured data blocks, page copy, headings, and internal navigation; the route, template, component, CMS entry, theme file, or static page that renders the scanned URL; shared layout, metadata, routing, middleware, server, CDN, or hosting configuration if the issue is not in page content; existing tests, build scripts, preview commands, and deployment notes before choosing verification steps. ## Task Use the provided context to safely complete this workflow: Add /llms.txt or /.well-known/llms.txt with the product name, audience, value proposition, and key public links. First reproduce or verify the issue from the public page and available implementation source. Then make the smallest stack-appropriate change that fixes the scanner signal and improves the real user experience. Use this check-specific implementation guide: - Add a concise text file with product name, audience, value proposition, important public links, and any relevant docs/support URLs. - Keep it factual and aligned with visible public content. - Keep all metadata, headings, schema, canonical URLs, and visible copy consistent with the same public facts. - Use accurate, crawlable, human-visible content as the source for search and answer-engine improvements. - Keep the implementation stack-appropriate: use the existing framework, CMS, hosting provider, design system, and deployment workflow already in the project. Acceptance criteria for this fix: - /llms.txt or /.well-known/llms.txt returns HTTP 200 publicly. - The content is short, accurate, and useful for AI tools without exposing private details. - The public URL exposes the corrected crawl/search/answer signal in rendered HTML or reachable public files. - The change should be visible to a fresh unauthenticated request and likely improve the related FreeScan SEO / AEO check on rescan. - A fresh FreeScan rescan should show this check improved or passing after deployment. ## Output Return a structured response with these headings: Findings, Changes Made, Verification Results, Rescan Expectation, Rollback Notes, 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. - Prefer editing the canonical source of the page over patching built output, generated files, CDN-cached HTML, or minified assets. - Do not make a cosmetic or placeholder change just to satisfy the scanner; the public page should be materially better for visitors, crawlers, or assistive technology. - 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.

## Role Act as a focused technical SEO, AEO, and crawlability remediation expert who can inspect the public page and safely improve the underlying implementation. ## Inputs - Primary context: Improve promptplanner.app at https://promptplanner.app. - Scanner check ID: seo_robots_txt. - Fix title: Publish robots.txt. - Scanner check: robots.txt reachability. - Category: SEO / AEO. - Status: fail. - Severity: medium. - Priority: 14; lower numbers are more urgent. - Score impact: 7 of 7 rule points lost. - Evidence: HTTP 404 returned for robots_txt. - What needs attention: The standard crawler instruction file was not reachable. - Why it matters: A reachable robots.txt helps crawlers understand what they can index before launch traffic arrives. - 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. - Likely places to inspect: public robots.txt file or route, deployment static assets, and crawler directives for the landing page; metadata/head configuration, canonical URL logic, robots and sitemap routes, structured data blocks, page copy, headings, and internal navigation; the route, template, component, CMS entry, theme file, or static page that renders the scanned URL; shared layout, metadata, routing, middleware, server, CDN, or hosting configuration if the issue is not in page content; existing tests, build scripts, preview commands, and deployment notes before choosing verification steps. ## Task Use the provided context to safely complete this workflow: Add a public /robots.txt file and make sure it returns HTTP 200 without blocking the landing page. First reproduce or verify the issue from the public page and available implementation source. Then make the smallest stack-appropriate change that fixes the scanner signal and improves the real user experience. Use this check-specific implementation guide: - Publish a reachable robots.txt that permits crawling of the public landing page. - Only block private, admin, search-result, staging, or low-value paths intentionally. - Keep all metadata, headings, schema, canonical URLs, and visible copy consistent with the same public facts. - Use accurate, crawlable, human-visible content as the source for search and answer-engine improvements. - Keep the implementation stack-appropriate: use the existing framework, CMS, hosting provider, design system, and deployment workflow already in the project. Acceptance criteria for this fix: - /robots.txt returns HTTP 200 publicly. - The scanned public page is not blocked by robots.txt. - The public URL exposes the corrected crawl/search/answer signal in rendered HTML or reachable public files. - The change should be visible to a fresh unauthenticated request and likely improve the related FreeScan SEO / AEO check on rescan. - A fresh FreeScan rescan should show this check improved or passing after deployment. ## Output Return a structured response with these headings: Findings, Changes Made, Verification Results, Rescan Expectation, Rollback Notes, 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. - Prefer editing the canonical source of the page over patching built output, generated files, CDN-cached HTML, or minified assets. - Do not make a cosmetic or placeholder change just to satisfy the scanner; the public page should be materially better for visitors, crawlers, or assistive technology. - 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.

## Role Act as a focused technical SEO, AEO, and crawlability remediation expert who can inspect the public page and safely improve the underlying implementation. ## Inputs - Primary context: Improve promptplanner.app at https://promptplanner.app. - Scanner check ID: seo_sitemap_xml. - Fix title: Publish sitemap.xml. - Scanner check: sitemap.xml reachability. - Category: SEO / AEO. - Status: fail. - Severity: medium. - Priority: 15; lower numbers are more urgent. - Score impact: 7 of 7 rule points lost. - Evidence: HTTP 404 returned for sitemap_xml. - What needs attention: The sitemap file was not reachable. - 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. - Likely places to inspect: robots.txt Sitemap directives, static sitemap files, dynamic sitemap routes, sitemap indexes, canonical URL generation, and deployment output; metadata/head configuration, canonical URL logic, robots and sitemap routes, structured data blocks, page copy, headings, and internal navigation; the route, template, component, CMS entry, theme file, or static page that renders the scanned URL; shared layout, metadata, routing, middleware, server, CDN, or hosting configuration if the issue is not in page content; existing tests, build scripts, preview commands, and deployment notes before choosing verification steps. ## Task Use the provided context to safely complete this workflow: Add /sitemap.xml with your public URLs and confirm it returns HTTP 200. First reproduce or verify the issue from the public page and available implementation source. Then make the smallest stack-appropriate change that fixes the scanner signal and improves the real user experience. Use this check-specific implementation guide: - Provide a reachable sitemap URL with valid urlset or sitemapindex XML. Preserve an existing robots.txt Sitemap directive such as /sitemap_index.xml when it is intentional and valid. - Include canonical public URLs and avoid localhost, staging, private, noindex, or duplicate URLs. - Keep all metadata, headings, schema, canonical URLs, and visible copy consistent with the same public facts. - Use accurate, crawlable, human-visible content as the source for search and answer-engine improvements. - Keep the implementation stack-appropriate: use the existing framework, CMS, hosting provider, design system, and deployment workflow already in the project. Acceptance criteria for this fix: - The sitemap URL declared in robots.txt, or /sitemap.xml when no directive exists, returns HTTP 200 with a valid urlset or sitemapindex root. - The sitemap contains at least the scanned public page or its canonical equivalent. - The public URL exposes the corrected crawl/search/answer signal in rendered HTML or reachable public files. - The change should be visible to a fresh unauthenticated request and likely improve the related FreeScan SEO / AEO check on rescan. - A fresh FreeScan rescan should show this check improved or passing after deployment. ## Output Return a structured response with these headings: Findings, Changes Made, Verification Results, Rescan Expectation, Rollback Notes, 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. - Prefer editing the canonical source of the page over patching built output, generated files, CDN-cached HTML, or minified assets. - Do not make a cosmetic or placeholder change just to satisfy the scanner; the public page should be materially better for visitors, crawlers, or assistive technology. - 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.

## Role Act as a focused technical SEO, AEO, and crawlability remediation expert who can inspect the public page and safely improve the underlying implementation. ## Inputs - Primary context: Improve promptplanner.app at https://promptplanner.app. - Scanner check ID: seo_llms_txt. - Fix title: Add an LLM-readable product file. - Scanner check: LLM-readable file. - Category: SEO / AEO. - Status: fail. - Severity: low. - Priority: 24; lower numbers are more urgent. - Score impact: 5 of 5 rule points lost. - Evidence: HTTP 404 returned for llms_txt. - What needs attention: The scan did not find llms.txt or .well-known/llms.txt. - Why it matters: A short LLM-readable file can help answer engines and AI tools summarize your product accurately. - 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. - Likely places to inspect: public /llms.txt or /.well-known/llms.txt route/file and source content used to describe the product; metadata/head configuration, canonical URL logic, robots and sitemap routes, structured data blocks, page copy, headings, and internal navigation; the route, template, component, CMS entry, theme file, or static page that renders the scanned URL; shared layout, metadata, routing, middleware, server, CDN, or hosting configuration if the issue is not in page content; existing tests, build scripts, preview commands, and deployment notes before choosing verification steps. ## Task Use the provided context to safely complete this workflow: Add /llms.txt or /.well-known/llms.txt with the product name, audience, value proposition, and key public links. First reproduce or verify the issue from the public page and available implementation source. Then make the smallest stack-appropriate change that fixes the scanner signal and improves the real user experience. Use this check-specific implementation guide: - Add a concise text file with product name, audience, value proposition, important public links, and any relevant docs/support URLs. - Keep it factual and aligned with visible public content. - Keep all metadata, headings, schema, canonical URLs, and visible copy consistent with the same public facts. - Use accurate, crawlable, human-visible content as the source for search and answer-engine improvements. - Keep the implementation stack-appropriate: use the existing framework, CMS, hosting provider, design system, and deployment workflow already in the project. Acceptance criteria for this fix: - /llms.txt or /.well-known/llms.txt returns HTTP 200 publicly. - The content is short, accurate, and useful for AI tools without exposing private details. - The public URL exposes the corrected crawl/search/answer signal in rendered HTML or reachable public files. - The change should be visible to a fresh unauthenticated request and likely improve the related FreeScan SEO / AEO check on rescan. - A fresh FreeScan rescan should show this check improved or passing after deployment. ## Output Return a structured response with these headings: Findings, Changes Made, Verification Results, Rescan Expectation, Rollback Notes, 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. - Prefer editing the canonical source of the page over patching built output, generated files, CDN-cached HTML, or minified assets. - Do not make a cosmetic or placeholder change just to satisfy the scanner; the public page should be materially better for visitors, crawlers, or assistive technology. - 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.

## Role Act as a focused public web security remediation expert who can inspect the public page and safely improve the underlying implementation. ## Inputs - Primary context: Improve promptplanner.app at https://promptplanner.app. - Scanner check ID: security_common_headers. - 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: 18 of 18 rule points lost. - Evidence: Detected 0 of 5 common public security headers. - 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. - Likely places to inspect: hosting headers, server middleware, edge/proxy config, CDN rules, and framework security header configuration; server, edge, CDN, hosting, proxy, form action, asset URL, cookie, and public file access configuration; the route, template, component, CMS entry, theme file, or static page that renders the scanned URL; shared layout, metadata, routing, middleware, server, CDN, or hosting configuration if the issue is not in page content; existing tests, build scripts, preview commands, and deployment notes before choosing verification steps. ## 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. First reproduce or verify the issue from the public page and available implementation source. Then make the smallest stack-appropriate change that fixes the scanner signal and improves the real user experience. Use this check-specific implementation guide: - Add missing common browser protection headers with values appropriate for the site. - Treat an existing CSP frame-ancestors directive as valid frame protection; preserve the directive and its allowed origins exactly instead of adding or substituting X-Frame-Options. - Test CSP or frame policies carefully so they do not break scripts, images, analytics, payments, embeds, or auth. - Prefer narrow, production-safe security configuration changes over blanket disables or permissive rules. - Preserve authentication, authorization, private paths, and sensitive file protections while fixing the public launch page. - Keep the implementation stack-appropriate: use the existing framework, CMS, hosting provider, design system, and deployment workflow already in the project. Acceptance criteria for this fix: - Important security headers are visible on the public response. - Any existing CSP frame-ancestors directive and its allowed origins remain unchanged. - The page still renders and key flows still work after header changes. - The public URL keeps legitimate visitors and assets working while removing the reported browser-side or public exposure risk. - The change does not weaken security headers, authentication, authorization, or private route protections. - A fresh FreeScan rescan should show this check improved or passing after deployment. ## Output Return a structured response with these headings: Findings, Changes Made, Verification Results, Rescan Expectation, Rollback Notes, 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. - Prefer editing the canonical source of the page over patching built output, generated files, CDN-cached HTML, or minified assets. - Do not make a cosmetic or placeholder change just to satisfy the scanner; the public page should be materially better for visitors, crawlers, or assistive technology. - If an existing Content-Security-Policy contains a frame-ancestors directive, preserve that directive exactly, including its allowed origins, unless the site owner explicitly asks to change it. Do not replace it with X-Frame-Options merely to satisfy this scan. - 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.

## Role Act as a focused conversion-focused frontend quality remediation expert who can inspect the public page and safely improve the underlying implementation. ## Inputs - Primary context: Improve promptplanner.app at https://promptplanner.app. - Scanner check ID: design_spacing_consistency. - Fix title: Make spacing more consistent. - Scanner check: Spacing consistency. - Category: Design. - Status: fail. - Severity: low. - Priority: 25; lower numbers are more urgent. - Score impact: 7 of 7 rule points lost. - Evidence: Detected 0 spacing class/style signal(s). - What needs attention: The page exposes few consistent spacing signals in class or inline styles. - Why it matters: Consistent spacing helps the page feel deliberate and easier to scan. - 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. - Likely places to inspect: layout spacing tokens, component padding, section gaps, card grids, mobile breakpoints, and repeated patterns; page layout, responsive CSS, component states, copy hierarchy, CTA placement, spacing tokens, rendered console output, and performance-sensitive assets; the route, template, component, CMS entry, theme file, or static page that renders the scanned URL; shared layout, metadata, routing, middleware, server, CDN, or hosting configuration if the issue is not in page content; existing tests, build scripts, preview commands, and deployment notes before choosing verification steps. ## Task Use the provided context to safely complete this workflow: Use consistent section padding, gaps, and margins across repeated content blocks. First reproduce or verify the issue from the public page and available implementation source. Then make the smallest stack-appropriate change that fixes the scanner signal and improves the real user experience. Use this check-specific implementation guide: - Normalize spacing using existing tokens or local conventions. - Avoid one-off spacing hacks that create new breakpoints or layout shifts. - Improve the actual rendered page at mobile and desktop sizes, not only the source code shape. - Preserve core conversion flows while making layout, hierarchy, readability, or runtime health better. - Keep the implementation stack-appropriate: use the existing framework, CMS, hosting provider, design system, and deployment workflow already in the project. Acceptance criteria for this fix: - Spacing feels consistent across related sections and viewport sizes. - No important UI shifts or overlaps after the change. - The rendered page is visually stable and usable on mobile and desktop viewports. - The fix does not hide content, break CTAs, introduce console errors, or reduce clarity for visitors. - A fresh FreeScan rescan should show this check improved or passing after deployment. ## Output Return a structured response with these headings: Findings, Changes Made, Verification Results, Rescan Expectation, Rollback Notes, 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. - Prefer editing the canonical source of the page over patching built output, generated files, CDN-cached HTML, or minified assets. - Do not make a cosmetic or placeholder change just to satisfy the scanner; the public page should be materially better for visitors, crawlers, or assistive technology. - 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.

## Role Act as a focused conversion-focused frontend quality remediation expert who can inspect the public page and safely improve the underlying implementation. ## Inputs - Primary context: Improve promptplanner.app at https://promptplanner.app. - Scanner check ID: design_rendered_layout. - Fix title: Fix rendered layout ergonomics. - Scanner check: Rendered layout ergonomics. - Category: Design. - Status: fail. - Severity: medium. - Priority: 13; lower numbers are more urgent. - Score impact: 9 of 9 rule points lost. - Evidence: Horizontal overflow: 0px. Small tap targets: 11. - What needs attention: The browser-rendered page has layout or tap-target issues. - Why it matters: Horizontal overflow and tiny tap targets make the page feel broken on real devices, especially for mobile visitors. - Status-specific guidance: A public check reported a failure. Reproduce or inspect the issue first, then make the smallest safe fix. - Audience or recipient: The site owner, builder, or marketing team responsible for improving this public page. - Constraints, examples, or source material: Treat the live URL as the public target to inspect, not as the only source of truth. When repository, CMS, or hosting access is available, use that implementation context before changing anything. - Target outcome: After the fix is deployed and the public page is rescanned, this specific check should improve or pass without lowering other SEO / AEO, security, accessibility, or design signals. - Likely places to inspect: mobile viewport, horizontal overflow sources, tap target sizes, fixed-position elements, menus, forms, and embeds; page layout, responsive CSS, component states, copy hierarchy, CTA placement, spacing tokens, rendered console output, and performance-sensitive assets; the route, template, component, CMS entry, theme file, or static page that renders the scanned URL; shared layout, metadata, routing, middleware, server, CDN, or hosting configuration if the issue is not in page content; existing tests, build scripts, preview commands, and deployment notes before choosing verification steps. ## Task Use the provided context to safely complete this workflow: Remove elements wider than the viewport, add responsive constraints, and make important links, buttons, inputs, and controls at least 40px tall and wide where possible. First reproduce or verify the issue from the public page and available implementation source. Then make the smallest stack-appropriate change that fixes the scanner signal and improves the real user experience. Use this check-specific implementation guide: - Constrain overflowing elements and increase small important tap targets where possible. - Preserve layout intent while making the rendered page usable on real devices. - Improve the actual rendered page at mobile and desktop sizes, not only the source code shape. - Preserve core conversion flows while making layout, hierarchy, readability, or runtime health better. - Keep the implementation stack-appropriate: use the existing framework, CMS, hosting provider, design system, and deployment workflow already in the project. Acceptance criteria for this fix: - The rendered page has no meaningful horizontal overflow. - Important links, buttons, inputs, and controls are comfortably tappable. - The rendered page is visually stable and usable on mobile and desktop viewports. - The fix does not hide content, break CTAs, introduce console errors, or reduce clarity for visitors. - A fresh FreeScan rescan should show this check improved or passing after deployment. ## Output Return a structured response with these headings: Findings, Changes Made, Verification Results, Rescan Expectation, Rollback Notes, 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. - Prefer editing the canonical source of the page over patching built output, generated files, CDN-cached HTML, or minified assets. - Do not make a cosmetic or placeholder change just to satisfy the scanner; the public page should be materially better for visitors, crawlers, or assistive technology. - 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.

promptplanner.app Website Audit

Add common public security headers

Agent Prompt

Fix rendered layout ergonomics

Agent Prompt

Publish robots.txt

Agent Prompt

Publish sitemap.xml

Agent Prompt

Add an LLM-readable product file

Agent Prompt

SEO / AEO

robots.txt reachability

sitemap.xml reachability

LLM-readable file

Security

Common security headers

Accessibility

Design

Rendered layout ergonomics

Spacing consistency

Failed checks

robots.txt reachability

Agent Prompt

sitemap.xml reachability

Agent Prompt

LLM-readable file

Agent Prompt

Common security headers

Agent Prompt

Spacing consistency

Agent Prompt

Rendered layout ergonomics

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.

promptplanner.app Website Audit

Add common public security headers

Agent Prompt

Fix rendered layout ergonomics

Agent Prompt

Publish robots.txt

Agent Prompt

Publish sitemap.xml

Agent Prompt

Add an LLM-readable product file

Agent Prompt

SEO / AEO

robots.txt reachability

sitemap.xml reachability

LLM-readable file

Security

Common security headers

Accessibility

Design

Rendered layout ergonomics

Spacing consistency

Failed checks

robots.txt reachability

Agent Prompt

sitemap.xml reachability

Agent Prompt

LLM-readable file

Agent Prompt

Common security headers

Agent Prompt

Spacing consistency

Agent Prompt

Rendered layout ergonomics

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.