Website audit scorecard for aayatana.tech
The scanner fetched the public page, extracted deterministic facts, and stored scored results across SEO / AEO, security, accessibility, and design.
Submitted
https://aayatana.tech/
Final URL
https://aayatana.tech
Created
Jul 23, 2026, 8:34 AM
Safe fetch
148 ms
68
out of 100
70
out of 100
74/106 rule points
95
out of 100
72/76 rule points
50
out of 100
47/94 rule points
58
out of 100
64/110 rule points
Category point breakdown
Biggest score-losing checks
axe found 5 violation rule(s), including 2 serious or critical rule(s). Top rules: color-contrast (9), link-name (10), heading-order (2), landmark-one-main (1), region (4).
Detected 0 CTA candidate(s).
Detected 5 H1 heading(s) and 174 meta-description characters.
Heading levels found: 2, 1, 1, 1, 1, 6, 6, 6, 4, 4, 4, 4, 4, 4, 4, 4, 4, 6, 1, 5, 5, 5, 5, 5, 5, 6, 3, 3, 3, 3.
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 2 serious or critical rule(s). Top rules: color-contrast (9), link-name (10), heading-order (2), landmark-one-main (1), region (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.
Copyable agent prompt
Make the primary CTA obvious
-14 rule ptsWhat failed
The page does not have a detectable call to action.
Evidence
Detected 0 CTA candidate(s).
Priority
Priority 4: fix before sharing the page publicly.
Why it matters
Early visitors need a clear next step, such as trying the product, joining a waitlist, or booking a demo.
How to fix it
Add one prominent CTA above the fold with action-oriented text such as Start, Join, Try, Book, or Get started.
Copyable agent prompt
Add a useful meta description
-10 rule ptsWhat failed
The page does not expose a strong short summary for search and answer engines.
Evidence
Meta description is 174 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.
Copyable agent prompt
Clarify the hero promise
-13 rule ptsWhat failed
The hero area does not provide enough clear product context.
Evidence
Detected 5 H1 heading(s) and 174 meta-description characters.
Priority
Priority 6: fix during launch polish.
Why it matters
Visitors decide quickly whether the product is relevant; a vague hero weakens every acquisition channel.
How to fix it
Use one clear H1 plus supporting copy that names the audience, problem, and outcome.
Copyable agent prompt
Add common public security headers
-4 rule ptsWhat failed
Several basic browser protection headers were not visible.
Evidence
Detected 4 of 5 common public security headers. Present: content-security-policy, x-content-type-options, x-frame-options, referrer-policy. Missing: strict-transport-security.
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.
Copyable agent prompt
SEO / AEO
Severity mix: 1 critical, 6 high, 3 medium, 2 low.
Meta description
-10 rule ptsMeta description is 174 characters.
Schema presence
-10 rule ptsDetected 0 JSON-LD schema block(s).
Heading structure
-8 rule ptsDetected 5 H1 heading(s) and 30 total headings.
Security
Severity mix: 2 critical, 3 high, 0 medium, 0 low.
Common security headers
-4 rule ptsDetected 4 of 5 common public security headers. Present: content-security-policy, x-content-type-options, x-frame-options, referrer-policy. Missing: strict-transport-security.
Accessibility
Severity mix: 0 critical, 3 high, 5 medium, 0 low.
Rendered axe accessibility violations
-18 rule ptsaxe found 5 violation rule(s), including 2 serious or critical rule(s). Top rules: color-contrast (9), link-name (10), heading-order (2), landmark-one-main (1), region (4).
Heading order
-11 rule ptsHeading levels found: 2, 1, 1, 1, 1, 6, 6, 6, 4, 4, 4, 4, 4, 4, 4, 4, 4, 6, 1, 5, 5, 5, 5, 5, 5, 6, 3, 3, 3, 3.
Landmark presence
-10 rule ptsDetected 1 landmark element(s) or roles.
Design
Severity mix: 0 critical, 3 high, 6 medium, 2 low.
Visible primary CTA
-14 rule ptsDetected 0 CTA candidate(s).
Hero clarity signals
-13 rule ptsDetected 5 H1 heading(s) and 174 meta-description characters.
Trust signals
-10 rule ptsDetected 0 trust-signal keyword occurrence(s).
Showing failed checks.
Failed checks
These checks need attention.
Meta description
0/10Meta description is 174 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.
Copyable agent prompt
Heading structure
0/8Detected 5 H1 heading(s) and 30 total headings.
Failed: earned 0 of 8 points.
Priority: Priority 9: fix during launch polish.
Why it matters: Clear headings help visitors, search engines, and assistive technology understand the page quickly.
Fix: Keep one H1 for the main promise, then use H2 and H3 headings in order for sections below it.
Copyable agent prompt
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.
Copyable agent prompt
Schema presence
0/10Detected 0 JSON-LD schema block(s).
Failed: earned 0 of 10 points.
Priority: Priority 12: fix during launch polish.
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.
Copyable agent prompt
Common security headers
14/18Detected 4 of 5 common public security headers. Present: content-security-policy, x-content-type-options, x-frame-options, referrer-policy. Missing: strict-transport-security.
Failed: earned 14 of 18 points from partial coverage.
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.
Copyable agent prompt
Heading order
0/11Heading levels found: 2, 1, 1, 1, 1, 6, 6, 6, 4, 4, 4, 4, 4, 4, 4, 4, 4, 6, 1, 5, 5, 5, 5, 5, 5, 6, 3, 3, 3, 3.
Failed: earned 0 of 11 points.
Priority: Priority 13: fix during launch polish.
Why it matters: A clean heading outline helps visitors scan the page and helps assistive technology navigate it.
Fix: Use headings in order: one H1, then H2 for major sections, then H3 for subsections.
Copyable agent prompt
Landmark presence
0/10Detected 1 landmark element(s) or roles.
Failed: earned 0 of 10 points.
Priority: Priority 18: lower-risk cleanup after urgent launch blockers.
Why it matters: Landmarks make the page easier to navigate for assistive technology and keyboard users.
Fix: Use semantic elements such as header, nav, main, and footer around the appropriate page areas.
Copyable agent prompt
Basic contrast
0/839 of 100 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 2.64.
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.
Copyable agent prompt
Rendered axe accessibility violations
0/18axe found 5 violation rule(s), including 2 serious or critical rule(s). Top rules: color-contrast (9), link-name (10), heading-order (2), landmark-one-main (1), region (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.
Copyable agent prompt
Visible primary CTA
0/14Detected 0 CTA candidate(s).
Failed: earned 0 of 14 points.
Priority: Priority 4: fix before sharing the page publicly.
Why it matters: Early visitors need a clear next step, such as trying the product, joining a waitlist, or booking a demo.
Fix: Add one prominent CTA above the fold with action-oriented text such as Start, Join, Try, Book, or Get started.
Copyable agent prompt
Hero clarity signals
0/13Detected 5 H1 heading(s) and 174 meta-description characters.
Failed: earned 0 of 13 points.
Priority: Priority 6: fix during launch polish.
Why it matters: Visitors decide quickly whether the product is relevant; a vague hero weakens every acquisition channel.
Fix: Use one clear H1 plus supporting copy that names the audience, problem, and outcome.
Copyable agent prompt
Trust signals
0/10Detected 0 trust-signal keyword occurrence(s).
Failed: earned 0 of 10 points.
Priority: Priority 16: lower-risk cleanup after urgent launch blockers.
Why it matters: Trust signals reduce hesitation when strangers see the product for the first time.
Fix: Add honest proof such as customer quotes, usage stats, founder credibility, security notes, or relevant logos.
Copyable agent prompt
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.
Copyable agent prompt
Share preview
aayatana.tech website audit report
Needs fixes before launch: 68/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.