Loading scan status...
completed
HTTP 200
0 redirects
36 checks
Website audit scorecard for promptplanner.app
The scanner fetched the public page, extracted deterministic facts, and stored scored results across SEO / AEO, security, accessibility, and design.
Submitted
https://promptplanner.app
Final URL
https://promptplanner.app
Created
Jun 29, 2026, 1:57 PM
Safe fetch
414 ms
Four-score result
Close to ready (Strong): 30 passed, 6 failed, and 0 unknown. Strongest area: Accessibility. Weakest area: Security.
Overall
85
out of 100
SEO / AEO
77
out of 100
63/82 rule points
Security
76
out of 100
58/76 rule points
Accessibility
100
out of 100
94/94 rule points
Design
85
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 headersDetected 0 of 5 common public security headers.
medium
Design
Rendered layout ergonomicsHorizontal overflow: 0px. Small tap targets: 11.
medium
SEO / AEO
robots.txt reachabilityHTTP 404 returned for robots_txt.
medium
SEO / AEO
sitemap.xml reachabilityHTTP 404 returned for sitemap_xml.
Recommendations
Score-losing issues ordered by remediation priority, severity, and score impact.
5 fixes
6 opportunities
9 insights
1
fail
high
Security
Priority 5
Add common public security headers
-18 rule ptsWhat 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.
2
fail
medium
Design
Priority 13
Fix rendered layout ergonomics
-9 rule ptsWhat 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.
3
fail
medium
SEO / AEO
Priority 14
Publish robots.txt
-7 rule ptsWhat 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.
4
fail
medium
SEO / AEO
Priority 15
Publish sitemap.xml
-7 rule ptsWhat 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.
5
fail
low
SEO / AEO
Priority 24
Add an LLM-readable product file
-5 rule ptsWhat 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.
Unknown and not detected states
FreeScan.app keeps partial public data explicit. It marks unverifiable signals as unknown or not detected instead of inventing evidence.
0 unknown
Safe public scans cannot see private cookies, authenticated content, browser-rendered state, or reliable contrast values unless they are present in static public markup.This scan did not produce unknown checks. If a future page has partial public data, the report will show those checks here instead of guessing.
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 ptsHTTP 404 returned for robots_txt.
medium
sitemap.xml reachability
-7 rule ptsHTTP 404 returned for sitemap_xml.
low
LLM-readable file
-5 rule ptsHTTP 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 ptsDetected 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 ptsHorizontal overflow: 0px. Small tap targets: 11.
low
Spacing consistency
-7 rule ptsDetected 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.
Showing failed checks.
Failed checks
These checks need attention.
fail
medium
SEO / AEO
robots.txt reachability
0/7HTTP 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.
fail
medium
SEO / AEO
sitemap.xml reachability
0/7HTTP 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.
fail
low
SEO / AEO
LLM-readable file
0/5HTTP 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.
fail
high
Security
Common security headers
0/18Detected 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.
fail
low
Design
Spacing consistency
0/7Detected 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.
fail
medium
Design
Rendered layout ergonomics
0/9Horizontal 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.
Safe fetch metadata
Public headers and redirects captured during intake. Response bodies, cookies, and credentials are not stored.
Security and accessibility checks are basic automated public checks. They are not a complete security audit, penetration test, privacy review, or WCAG certification.
Landing page
Step 1HTTP 2001 captured header(s)Checked: https://promptplanner.app
Next/final: https://promptplanner.app
Content type: text/html
Landing page
Step 2HTTP 2001 captured header(s)Checked: https://promptplanner.app
Next/final: https://promptplanner.app
Content type: text/html
Content hash: 4c4cef7f2f171b0db6204a95d47db32f05ff7c7392f77475c6613c37d9105c1e
robots.txt
Step 3HTTP 4041 captured header(s)Checked: https://promptplanner.app/robots.txt
Next/final: https://promptplanner.app/robots.txt
Content type: text/html
Fetch result: HTTP 404 returned for robots_txt.
sitemap.xml
Step 4HTTP 4041 captured header(s)Checked: https://promptplanner.app/sitemap.xml
Next/final: https://promptplanner.app/sitemap.xml
Content type: text/html
Fetch result: HTTP 404 returned for sitemap_xml.
llms.txt
Step 5HTTP 4041 captured header(s)Checked: https://promptplanner.app/llms.txt
Next/final: https://promptplanner.app/llms.txt
Content type: text/html
Fetch result: HTTP 404 returned for llms_txt.
Security probe
Step 6HTTP 4041 captured header(s)Checked: https://promptplanner.app/.env
Next/final: https://promptplanner.app/.env
Content type: text/html
Fetch result: HTTP 404 returned for security_probe.
Security probe
Step 7HTTP 4041 captured header(s)Checked: https://promptplanner.app/.git/config
Next/final: https://promptplanner.app/.git/config
Content type: text/html
Fetch result: HTTP 404 returned for security_probe.
Security probe
Step 8HTTP 4041 captured header(s)Checked: https://promptplanner.app/wp-config.php
Next/final: https://promptplanner.app/wp-config.php
Content type: text/html
Fetch result: HTTP 404 returned for security_probe.
Security probe
Step 9HTTP 4041 captured header(s)Checked: https://promptplanner.app/backup.zip
Next/final: https://promptplanner.app/backup.zip
Content type: text/html
Fetch result: HTTP 404 returned for security_probe.
Captured public headers
content-type
text/html
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 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.