Loading scan status...
completed
HTTP 200
0 redirects
36 checks
Website audit scorecard for easydofollow.dev
The scanner fetched the public page, extracted deterministic facts, and stored scored results across SEO / AEO, security, accessibility, and design.
Submitted
https://www.easydofollow.dev/
Final URL
https://www.easydofollow.dev
Created
Jun 29, 2026, 4:18 AM
Safe fetch
200 ms
Four-score result
Needs fixes before launch (Needs focused fixes): 23 passed, 13 failed, and 0 unknown. Strongest area: Security. Weakest area: SEO / AEO.
Overall
66
out of 100
SEO / AEO
48
out of 100
39/82 rule points
Security
76
out of 100
58/76 rule points
Accessibility
72
out of 100
68/94 rule points
Design
68
out of 100
75/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 / AEO39/82
Security58/76
Accessibility68/94
Design75/110
Biggest score-losing checks
high
Security
Common security headersDetected 1 of 5 common public security headers.
high
Accessibility
Rendered axe accessibility violationsaxe found 1 violation rule(s), including 1 serious or critical rule(s). Top rules: color-contrast (4).
high
SEO / AEO
Meta descriptionMeta description is 184 characters.
medium
Design
Rendered speed signalsDOMContentLoaded: 552ms. Load complete: 1467ms. First contentful paint: 756ms. Resources: 57. Scripts: 9. Images: 43. Third-party origins: 10. Transfer: not available.
Recommendations
Score-losing issues ordered by remediation priority, severity, and score impact.
5 fixes
6 opportunities
9 insights
1
high
SEO / AEO
Priority 3
Add a useful meta description
-10 ptsWhat failed
The page does not expose a strong short summary for search and answer engines.
Evidence
Meta description is 184 characters.
Priority
Priority 3: fix before sharing the page publicly.
Why it matters
A missing description makes previews weaker when early users share or find the page.
How to fix it
Add a meta description around 50 to 170 characters that says who the product helps and what outcome it creates.
2
high
Security
Priority 5
Add common public security headers
-18 ptsWhat failed
Several basic browser protection headers were not visible.
Evidence
Detected 1 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.
3
high
Accessibility
Priority 5
Fix rendered axe accessibility violations
-18 ptsWhat failed
The rendered page has accessibility rule violations detected by axe-core.
Evidence
axe found 1 violation rule(s), including 1 serious or critical rule(s). Top rules: color-contrast (4).
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
medium
Design
Priority 12
Strengthen visual hierarchy
-9 ptsWhat failed
The page does not expose enough hierarchy signals from headings, emphasis, or CTA structure.
Evidence
Detected 2 hierarchy signal(s) from headings, CTA, and emphasized text.
Priority
Priority 12: fix during launch polish.
Why it matters
Hierarchy tells visitors what to read first and what action to take next.
How to fix it
Create a clear H1, supportive section headings, emphasized proof, and one visually prominent primary CTA.
5
medium
SEO / AEO
Priority 12
Add a canonical URL
-7 ptsWhat failed
The page does not declare which public URL is the preferred version.
Evidence
No canonical link tag was detected.
Priority
Priority 12: 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.
48/100
5 pass, 6 fail, 0 unknown
SEO / AEO
Severity mix: 0 critical, 3 high, 6 medium, 2 low.
high
Meta description
-10 ptsMeta description is 184 characters.
medium
Canonical tag
-7 ptsNo canonical link tag was detected.
medium
robots.txt reachability
-7 ptsHTTP 404 returned for robots_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 ptsDetected 1 of 5 common public security headers.
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 ptsaxe found 1 violation rule(s), including 1 serious or critical rule(s). Top rules: color-contrast (4).
medium
Basic contrast
-8 pts6 of 100 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 3.24.
68/100
7 pass, 4 fail, 0 unknown
Design
Severity mix: 0 critical, 3 high, 6 medium, 2 low.
medium
Rendered speed signals
-10 ptsDOMContentLoaded: 552ms. Load complete: 1467ms. First contentful paint: 756ms. Resources: 57. Scripts: 9. Images: 43. Third-party origins: 10. Transfer: not available.
medium
Visual hierarchy
-9 ptsDetected 2 hierarchy signal(s) from headings, CTA, and emphasized text.
medium
Rendered layout ergonomics
-9 ptsHorizontal overflow: 0px. Small tap targets: 173.
Full check list
Failed, unknown, and passed checks are all shown so the report is transparent even when public data is partial.
Showing failed checks.
Failed checks
These checks need attention.
fail
high
SEO / AEO
Meta description
0/10Meta description is 184 characters.
Failed: earned 0 of 10 points.
Priority: Priority 3: fix before sharing the page publicly.
Why it matters: A missing description makes previews weaker when early users share or find the page.
Fix: Add a meta description around 50 to 170 characters that says who the product helps and what outcome it creates.
fail
medium
SEO / AEO
Canonical tag
0/7No canonical link tag was detected.
Failed: earned 0 of 7 points.
Priority: Priority 12: 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
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
medium
SEO / AEO
Schema presence
0/7Detected 0 JSON-LD schema block(s).
Failed: earned 0 of 7 points.
Priority: Priority 16: lower-risk cleanup after urgent launch blockers.
Why it matters: Structured data gives search and answer engines explicit facts about your product.
Fix: Add JSON-LD for SoftwareApplication, Product, Organization, or WebSite using only accurate public facts.
fail
high
Security
Common security headers
0/18Detected 1 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
medium
Accessibility
Basic contrast
0/86 of 100 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 3.24.
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 1 violation rule(s), including 1 serious or critical rule(s). Top rules: color-contrast (4).
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
Visual hierarchy
0/9Detected 2 hierarchy signal(s) from headings, CTA, and emphasized text.
Failed: earned 0 of 9 points.
Priority: Priority 12: fix during launch polish.
Why it matters: Hierarchy tells visitors what to read first and what action to take next.
Fix: Create a clear H1, supportive section headings, emphasized proof, and one visually prominent primary CTA.
fail
medium
Design
Rendered speed signals
0/10DOMContentLoaded: 552ms. Load complete: 1467ms. First contentful paint: 756ms. Resources: 57. Scripts: 9. Images: 43. Third-party origins: 10. Transfer: not available.
Failed: earned 0 of 10 points.
Priority: Priority 14: fix during launch polish.
Why it matters: Slow pages lose impatient visitors and make every SEO, social, and paid-traffic visit work harder.
Fix: Reduce render-blocking scripts/styles, compress and size images, defer non-critical JavaScript, reduce third-party tags, and keep above-the-fold content quick to paint.
fail
low
Design
Runtime console health
0/7Detected 3 console error(s) and 0 uncaught page error(s) during render.
Failed: earned 0 of 7 points.
Priority: Priority 15: fix during launch polish.
Why it matters: Runtime errors can break forms, CTAs, animations, tracking, or responsive behavior even when the static HTML looks fine.
Fix: Open the page in a browser, reproduce the console errors, and fix missing assets, hydration problems, client-side exceptions, or failing third-party scripts.
fail
medium
Design
Rendered layout ergonomics
0/9Horizontal overflow: 0px. Small tap targets: 173.
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 2002 captured header(s)Checked: https://www.easydofollow.dev
Next/final: https://www.easydofollow.dev
Content type: text/html; charset=utf-8
Landing page
Step 2HTTP 2002 captured header(s)Checked: https://www.easydofollow.dev
Next/final: https://www.easydofollow.dev
Content type: text/html; charset=utf-8
Content hash: 3203daadace8cf046e007745c3f6e475656d82e2306ab52fadc0895f4a72b60a
robots.txt
Step 3HTTP 4042 captured header(s)Checked: https://www.easydofollow.dev/robots.txt
Next/final: https://www.easydofollow.dev/robots.txt
Content type: text/html; charset=utf-8
Fetch result: HTTP 404 returned for robots_txt.
sitemap.xml
Step 4HTTP 4042 captured header(s)Checked: https://www.easydofollow.dev/sitemap.xml
Next/final: https://www.easydofollow.dev/sitemap.xml
Content type: text/html; charset=utf-8
Fetch result: HTTP 404 returned for sitemap_xml.
llms.txt
Step 5HTTP 4042 captured header(s)Checked: https://www.easydofollow.dev/llms.txt
Next/final: https://www.easydofollow.dev/llms.txt
Content type: text/html; charset=utf-8
Fetch result: HTTP 404 returned for llms_txt.
Security probe
Step 6HTTP 4042 captured header(s)Checked: https://www.easydofollow.dev/.env
Next/final: https://www.easydofollow.dev/.env
Content type: text/html; charset=utf-8
Fetch result: HTTP 404 returned for security_probe.
Security probe
Step 7HTTP 4042 captured header(s)Checked: https://www.easydofollow.dev/.git/config
Next/final: https://www.easydofollow.dev/.git/config
Content type: text/html; charset=utf-8
Fetch result: HTTP 404 returned for security_probe.
Security probe
Step 8HTTP 4031 captured header(s)Checked: https://www.easydofollow.dev/wp-config.php
Next/final: https://www.easydofollow.dev/wp-config.php
Content type: text/html; charset=utf-8
Fetch result: HTTP 403 returned for security_probe.
Security probe
Step 9HTTP 4042 captured header(s)Checked: https://www.easydofollow.dev/backup.zip
Next/final: https://www.easydofollow.dev/backup.zip
Content type: text/html; charset=utf-8
Fetch result: HTTP 404 returned for security_probe.
Captured public headers
content-type
text/html; charset=utf-8
strict-transport-security
max-age=63072000
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
easydofollow.dev website audit report
Needs fixes before launch: 66/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 easydofollow.dev without re-entering the URL. The previous report stays saved so the next result can be compared against it.