Loading scan status...
completed
HTTP 200
0 redirects
36 checks
Website audit scorecard for digibull.ai
The scanner fetched the public page, extracted deterministic facts, and stored scored results across SEO / AEO, security, accessibility, and design.
Submitted
Https://digibull.ai
Final URL
https://digibull.ai
Created
Jul 2, 2026, 9:37 AM
Safe fetch
492 ms
Four-score result
Close to ready (Needs polish): 28 passed, 8 failed, and 0 unknown. Strongest area: Design. Weakest area: Security.
Overall
74
out of 100
SEO / AEO
75
out of 100
69/92 rule points
Security
55
out of 100
42/76 rule points
Accessibility
72
out of 100
68/94 rule points
Design
92
out of 100
101/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 / AEO69/92
Security42/76
Accessibility68/94
Design101/110
Biggest score-losing checks
high
Security
Common security headersDetected 0 of 5 common public security headers. Present: none. Missing: strict-transport-security, content-security-policy, x-content-type-options, x-frame-options, referrer-policy.
high
Accessibility
Rendered axe accessibility violationsaxe found 5 violation rule(s), including 3 serious or critical rule(s). Top rules: color-contrast (24), link-name (3), listitem (12), landmark-one-main (1), region (56).
critical
Security
Sensitive file probesA small allowlist probe returned a public success response.
high
SEO / AEO
Canonical tagNo canonical link tag was detected.
Recommendations
Score-losing issues ordered by remediation priority, severity, and score impact.
5 fixes
5 opportunities
9 insights
1
fail
critical
Security
Priority 1
Remove exposed sensitive files
-16 rule ptsWhat failed
A small public allowlist probe found a sensitive-looking file path.
Evidence
A small allowlist probe returned a public success response.
Priority
Priority 1: fix before sharing the page publicly.
Why it matters
Publicly exposed config or backup files can leak implementation details or secrets.
How to fix it
Remove the exposed file, block public access to that path, and rotate any secrets that may have been exposed.
2
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. Present: none. Missing: strict-transport-security, content-security-policy, x-content-type-options, x-frame-options, referrer-policy.
Priority
Priority 5: fix before sharing the page publicly.
Why it matters
These headers reduce avoidable browser-side risk and show a baseline of care before launch.
How to fix it
Configure headers such as Strict-Transport-Security, Content-Security-Policy, X-Content-Type-Options, X-Frame-Options, and Referrer-Policy.
3
fail
high
Accessibility
Priority 5
Fix rendered axe accessibility violations
-18 rule ptsWhat failed
The rendered page has accessibility rule violations detected by axe-core.
Evidence
axe found 5 violation rule(s), including 3 serious or critical rule(s). Top rules: color-contrast (24), link-name (3), listitem (12), landmark-one-main (1), region (56).
Priority
Priority 5: fix before sharing the page publicly.
Why it matters
axe checks the actual browser-rendered page, so these issues can affect people using keyboards, screen readers, or other assistive technology.
How to fix it
Fix the top axe rule IDs first, especially critical and serious violations around names, roles, labels, headings, contrast, landmarks, and keyboard-accessible controls.
4
fail
high
SEO / AEO
Priority 2
Remove noindex signals
-9 rule ptsWhat failed
The page appears to tell crawlers not to index it.
Evidence
A noindex directive was detected.
Priority
Priority 2: fix before sharing the page publicly.
Why it matters
A noindex directive can prevent the launch page from appearing in search results.
How to fix it
Remove noindex from meta robots or X-Robots-Tag headers once the page is ready to be public.
5
fail
high
SEO / AEO
Priority 9
Add a canonical URL
-10 rule ptsWhat failed
The page does not declare which public URL is the preferred version.
Evidence
No canonical link tag was detected.
Priority
Priority 9: fix during launch polish.
Why it matters
A canonical tag reduces duplicate URL confusion before marketing links start spreading.
How to fix it
Add a canonical link tag that points to the final public landing page URL.
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.
75/100
8 pass, 3 fail, 0 unknown
SEO / AEO
Severity mix: 0 critical, 6 high, 3 medium, 2 low.
high
Canonical tag
-10 rule ptsNo canonical link tag was detected.
high
Indexability signals
-9 rule ptsA noindex directive was detected.
low
LLM-readable file
-4 rule ptsHTTP 404 returned for llms_txt.
55/100
4 pass, 2 fail, 0 unknown
Security
Severity mix: 2 critical, 3 high, 0 medium, 0 low.
critical
Sensitive file probes
-16 rule ptsA small allowlist probe returned a public success response.
high
Common security headers
-18 rule ptsDetected 0 of 5 common public security headers. Present: none. Missing: strict-transport-security, content-security-policy, x-content-type-options, x-frame-options, referrer-policy.
72/100
6 pass, 2 fail, 0 unknown
Accessibility
Severity mix: 0 critical, 3 high, 5 medium, 0 low.
high
Rendered axe accessibility violations
-18 rule ptsaxe found 5 violation rule(s), including 3 serious or critical rule(s). Top rules: color-contrast (24), link-name (3), listitem (12), landmark-one-main (1), region (56).
medium
Basic contrast
-8 rule pts49 of 100 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 1.
92/100
10 pass, 1 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: 17.
Full check list
Failed, unknown, and passed checks are all shown so the report is transparent even when public data is partial.
Showing failed checks.
Failed checks
These checks need attention.
fail
high
SEO / AEO
Canonical tag
0/10No canonical link tag was detected.
Failed: earned 0 of 10 points.
Priority: Priority 9: fix during launch polish.
Why it matters: A canonical tag reduces duplicate URL confusion before marketing links start spreading.
Fix: Add a canonical link tag that points to the final public landing page URL.
fail
low
SEO / AEO
LLM-readable file
0/4HTTP 404 returned for llms_txt.
Failed: earned 0 of 4 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
SEO / AEO
Indexability signals
0/9A noindex directive was detected.
Failed: earned 0 of 9 points.
Priority: Priority 2: fix before sharing the page publicly.
Why it matters: A noindex directive can prevent the launch page from appearing in search results.
Fix: Remove noindex from meta robots or X-Robots-Tag headers once the page is ready to be public.
fail
high
Security
Common security headers
0/18Detected 0 of 5 common public security headers. Present: none. Missing: strict-transport-security, content-security-policy, x-content-type-options, x-frame-options, referrer-policy.
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
critical
Security
Sensitive file probes
0/16A small allowlist probe returned a public success response.
Failed: earned 0 of 16 points.
Priority: Priority 1: fix before sharing the page publicly.
Why it matters: Publicly exposed config or backup files can leak implementation details or secrets.
Fix: Remove the exposed file, block public access to that path, and rotate any secrets that may have been exposed.
fail
medium
Accessibility
Basic contrast
0/849 of 100 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 1.
Failed: earned 0 of 8 points.
Priority: Priority 20: lower-risk cleanup after urgent launch blockers.
Why it matters: Low contrast makes a launch page feel less polished and can exclude users with low vision.
Fix: Review key text, buttons, and links against a 4.5:1 contrast target for normal text.
fail
high
Accessibility
Rendered axe accessibility violations
0/18axe found 5 violation rule(s), including 3 serious or critical rule(s). Top rules: color-contrast (24), link-name (3), listitem (12), landmark-one-main (1), region (56).
Failed: earned 0 of 18 points.
Priority: Priority 5: fix before sharing the page publicly.
Why it matters: axe checks the actual browser-rendered page, so these issues can affect people using keyboards, screen readers, or other assistive technology.
Fix: Fix the top axe rule IDs first, especially critical and serious violations around names, roles, labels, headings, contrast, landmarks, and keyboard-accessible controls.
fail
medium
Design
Rendered layout ergonomics
0/9Horizontal overflow: 0px. Small tap targets: 17.
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://digibull.ai
Next/final: https://digibull.ai
Content type: text/html; charset=UTF-8
Landing page
Step 2HTTP 2001 captured header(s)Checked: https://digibull.ai
Next/final: https://digibull.ai
Content type: text/html; charset=UTF-8
Content hash: 8f266088894bcc17dac40555e7876ad110d450a93a472c21d14163c13fe656bb
robots.txt
Step 3HTTP 2001 captured header(s)Checked: https://digibull.ai/robots.txt
Next/final: https://digibull.ai/robots.txt
Content type: text/plain; charset=utf-8
Content hash: 21812115d469138e71fba697edf9128e964e93cd441221d146f2e4552c3f7987
sitemap.xml
Step 4HTTP 3012 captured header(s)Checked: https://digibull.ai/sitemap.xml
Next/final: https://digibull.ai/sitemap.xml
Content type: text/html; charset=UTF-8
llms.txt
Step 5HTTP 4041 captured header(s)Checked: https://digibull.ai/llms.txt
Next/final: https://digibull.ai/llms.txt
Content type: text/html; charset=UTF-8
Fetch result: HTTP 404 returned for llms_txt.
Security probe
Step 6HTTP 4031 captured header(s)Checked: https://digibull.ai/.env
Next/final: https://digibull.ai/.env
Content type: text/html
Fetch result: HTTP 403 returned for security_probe.
Security probe
Step 7HTTP 4031 captured header(s)Checked: https://digibull.ai/.git/config
Next/final: https://digibull.ai/.git/config
Content type: text/html
Fetch result: HTTP 403 returned for security_probe.
Security probe
Step 8HTTP 4031 captured header(s)Checked: https://digibull.ai/wp-config.php
Next/final: https://digibull.ai/wp-config.php
Content type: text/html
Fetch result: HTTP 403 returned for security_probe.
Security probe
Step 9HTTP 2002 captured header(s)Checked: https://digibull.ai/backup.zip
Next/final: https://digibull.ai/backup.zip
Content type: application/zip
Content hash: 6b91f6f94e70c212afb9e4fea01b9c61532d696579445a1cafbe6ab8b0ff7943
Captured public headers
content-type
text/html; charset=UTF-8
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
digibull.ai website audit report
Close to ready: 74/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 digibull.ai without re-entering the URL. The previous report stays saved so the next result can be compared against it.