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
66
out of 100
48
out of 100
39/82 rule points
76
out of 100
58/76 rule points
72
out of 100
68/94 rule points
68
out of 100
75/110 rule points
Category point breakdown
Biggest score-losing checks
Detected 1 of 5 common public security headers.
axe found 1 violation rule(s), including 1 serious or critical rule(s). Top rules: color-contrast (4).
Meta description is 184 characters.
DOMContentLoaded: 552ms. Load complete: 1467ms. First contentful paint: 756ms. Resources: 57. Scripts: 9. Images: 43. Third-party origins: 10. Transfer: not available.
What 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.
What 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.
What failed
The rendered page has accessibility rule violations detected by axe-core.
Evidence
axe found 1 violation rule(s), including 1 serious or critical rule(s). Top rules: 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.
What 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.
What 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.
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.
Severity mix: 0 critical, 3 high, 6 medium, 2 low.
Meta description is 184 characters.
No canonical link tag was detected.
HTTP 404 returned for robots_txt.
Severity mix: 2 critical, 3 high, 0 medium, 0 low.
Detected 1 of 5 common public security headers.
Severity mix: 0 critical, 3 high, 5 medium, 0 low.
axe found 1 violation rule(s), including 1 serious or critical rule(s). Top rules: color-contrast (4).
6 of 100 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 3.24.
Severity mix: 0 critical, 3 high, 6 medium, 2 low.
DOMContentLoaded: 552ms. Load complete: 1467ms. First contentful paint: 756ms. Resources: 57. Scripts: 9. Images: 43. Third-party origins: 10. Transfer: not available.
Detected 2 hierarchy signal(s) from headings, CTA, and emphasized text.
Horizontal overflow: 0px. Small tap targets: 173.
Showing failed checks.
These checks need attention.
Meta 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.
No 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.
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.
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.
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.
Detected 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.
Detected 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.
6 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.
axe 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.
Detected 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.
DOMContentLoaded: 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.
Detected 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.
Horizontal 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.
Security and accessibility checks are basic automated public checks. They are not a complete security audit, penetration test, privacy review, or WCAG certification.
Checked: https://www.easydofollow.dev
Next/final: https://www.easydofollow.dev
Content type: text/html; charset=utf-8
Checked: https://www.easydofollow.dev
Next/final: https://www.easydofollow.dev
Content type: text/html; charset=utf-8
Content hash: 3203daadace8cf046e007745c3f6e475656d82e2306ab52fadc0895f4a72b60a
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.
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.
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.
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.
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.
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.
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
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.