superdesign.dev — Website Report

Scored 78/100 · Scanned with Foglift

OverallⓘOverall Score — weighted average of all category scores

superdesign.dev scored 78. Addressing the 12 listed issues could raise its estimated score to 87.

Scan another domain Save this scan to your free account

3 critical3 warnings12 total issues

Quick wins

~88 min total fix time

1Zooming is disabled~2m

2Missing H1 heading~3m

3No main landmark~3m

https://superdesign.dev/ · 2026-08-17

Scanned with Foglift · Technical Audit + AI Readiness analysis

AI Action Plan

Website Analysis for https://superdesign.dev Your site scores 78/100 overall. AI Readiness is 67/100 — there's significant room to improve the technical, content, and authority signals that help AI systems access, understand, and reuse the page. We found 3 critical issues and 3 warnings. Here's your prioritized action plan:

FIX FIRST (Critical): 1. Missing Content Security Policy header — Add a Content-Security-Policy header to prevent XSS and injection attacks.

2. Missing H1 heading — Every page should have exactly one H1 heading that describes the main topic. This is important for SEO and accessibility. 3. Zooming is disabled — Your viewport meta tag prevents users from zooming. This is an accessibility violation — users with low vision need to zoom to read content. QUICK WINS (Warnings): 1. No FAQ section found — A clear Frequently Asked Questions section presents important questions and answers in a directly extractable format. Add one when it refl

5 more critical fixes + quick wins in your full report

Enter your email and we'll send the complete action plan to your inbox.

No spam. Just your report.

Share This Report

Send this scan to a teammate or contact. The shareable link includes all scores and issues.

Email to Contact

AI Readiness

Technical and authority signals that support AI systems in accessing, understanding, and reusing your content

67D

Technical52

Authority79

Set up all 6 tiers free →

100

Brand Mentions

Found 20+ web mentions of "superdesign"

Domain Authority

PageRank: 3.3/10, 17+ external references

Content Freshness

465 of 500 pages updated in the last 30 days

Technical Readiness

Moderate technical readiness — some improvements possible

Technical Issues

No FAQ section foundwarning~15 min fix

A clear Frequently Asked Questions section presents important questions and answers in a directly extractable format. Add one when it reflects real customer questions, and keep each answer factual and self-contained.

Quick Fix

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [{
    "@type": "Question",
    "name": "What does your company do?",
    "acceptedAnswer": {
      "@type": "Answer",
      "text": "We provide [your service]. Our solution helps..."
    }
  }]
}
</script>

FAQPage schema labels questions and answers in a machine-readable format, making the page easier for search and AI systems to extract accurately.

Page content is too thin for AIwarning

Your page has very few headings and paragraphs. AI assistants need well-organized, text-rich content to understand and recommend your site. Add clear headings, descriptive paragraphs, and detailed information about your offerings.

Content is hard for AI to scaninfo

Your page relies on plain text without lists, tables, or comparison charts. AI assistants extract and cite structured content (bullet points, comparison tables, step-by-step lists) far more accurately than long paragraphs.

How does AI see Superdesign?

When users ask AI about your industry, are you recommended?

Start with weekly Perplexity checks for Superdesign. Paid plans add ChatGPT, Google AI Overview, Gemini, and Claude.

Set up weekly monitoring free

SEO & Technical Issues (9)

Missing Content Security Policy headercriticalSecurity~5 min fix

Add a Content-Security-Policy header to prevent XSS and injection attacks.

Quick Fix

# Nginx:
add_header Content-Security-Policy "default-src 'self'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline';" always;

# Apache (.htaccess):
Header set Content-Security-Policy "default-src 'self'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline';"

# Next.js (next.config.js headers):
{ key: 'Content-Security-Policy', value: "default-src 'self'; script-src 'self' 'unsafe-inline'" }

Content-Security-Policy prevents XSS attacks by controlling which resources the browser can load.

Missing H1 headingcriticalSEO~3 min fix

Every page should have exactly one H1 heading that describes the main topic. This is important for SEO and accessibility.

Quick Fix

<h1>Your Main Page Heading</h1>
<!-- Only use one H1 per page. Make it descriptive and include your target keyword. -->

Every page needs exactly one H1 that describes the main topic. It's a key SEO signal.

Zooming is disabledcriticalAccessibility~2 min fix

Your viewport meta tag prevents users from zooming. This is an accessibility violation — users with low vision need to zoom to read content.

Quick Fix

<!-- Replace your viewport meta tag with this (allows zooming) -->
<meta name="viewport" content="width=device-width, initial-scale=1">
<!-- Do NOT use: maximum-scale=1, user-scalable=no -->

Preventing zoom is an accessibility violation. Users with low vision need to zoom to read content.

No H2 subheadingswarningSEO

Add H2 subheadings to organize your content. Good heading hierarchy helps search engines understand your page structure.

Few internal linksinfoSEO

Add more internal links to help search engines discover and index your other pages. Internal linking also helps distribute page authority.

No navigation landmarkinfoAccessibility~5 min fix

Add a <nav> element to help screen reader users quickly find the navigation. This is a WCAG 2.4.1 requirement.

Quick Fix

<!-- Wrap your navigation in a <nav> element -->
<nav aria-label="Main navigation">
  <ul>
    <li><a href="/">Home</a></li>
    <li><a href="/about">About</a></li>
    <li><a href="/contact">Contact</a></li>
  </ul>
</nav>

The <nav> landmark lets screen reader users quickly jump to navigation (WCAG 2.4.1).

No main landmarkinfoAccessibility~3 min fix

Add a <main> element to identify the primary content area. Screen reader users use this to skip navigation.

Quick Fix

<!-- Wrap your primary content in a <main> element -->
<main id="main-content">
  <h1>Page Title</h1>
  <p>Your primary content here...</p>
</main>

The <main> element identifies the primary content area, letting screen reader users skip to it directly.

No skip navigation linkinfoAccessibility~5 min fix

Add a 'Skip to main content' link at the top of the page so keyboard users can bypass repetitive navigation.

Quick Fix

<!-- Add as the first element inside <body> -->
<a href="#main-content" class="sr-only focus:not-sr-only focus:absolute focus:top-2 focus:left-2 focus:z-50 focus:px-4 focus:py-2 focus:bg-blue-600 focus:text-white focus:rounded">
  Skip to main content
</a>

<!-- Add id to your main content area -->
<main id="main-content">
  ...
</main>

Skip links let keyboard users bypass repetitive navigation and jump straight to content.

HTML contains many commentsinfoPerformance

Found 8 HTML comments. Remove unnecessary comments in production to reduce file size.

Your Potential Score

Now

Estimated potential

+9 points estimated improvement from addressing 12 listed issues

Estimate based on the measured category scores and the issues listed in this audit.

Track your AI visibility over time

AI Visibility Monitoring

Free checks Perplexity weekly while you're active. Paid plans add ChatGPT, Google AI Overview, Gemini, and Claude with daily, twice-daily, or hourly monitoring.

Competitor Tracking

Compare your AI visibility against competitors. Know when they overtake you.

Weekly Digest

Get AI-generated insights emailed every Monday with action items.

Set up Free monitoring

Weekly Perplexity while active · No credit card required

Compare paid plans — from $49/mo