Foglift
moz.com — Website Report
Scored 77/100 · Scanned with Foglift
C
moz.com scored 77. One fix would take it to 97.
2 critical7 warnings10 total issues
Quick wins
~92 min total fix time1Missing Permissions Policy header~2m
2Missing Content Security Policy header~5m
3No favicon detected~10m
https://moz.com/ · 2026-06-20
Scanned with Foglift · Technical Audit + AI Readiness analysis
AI Action Plan
Website Analysis for https://moz.com Great news — your site has strong AI visibility (77/100). Overall score: 77/100. AI engines like ChatGPT and Perplexity are likely to find and cite your content. We found 2 critical issues and 7 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. 5 render-blocking scripts — 5 scripts without async or defer attributes. These block page rendering. Add defer or async to non-critical scripts. QUICK WINS (Warnings): 1. No FAQ section found — AI assistants love Q&A content — it's the easiest format for them to extract and quote. Add a Frequently Asked Questions section to your page, and you'll significantly increase your chances of being cited in AI-generated answers. 2. Missing Permissions Policy header — Add a Permissions-Policy header t
8 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.
AI Visibility
How likely AI assistants like ChatGPT, Perplexity, and Gemini are to cite your brand
77C
85
Brand Mentions
Found 19+ web mentions of "moz"
63
Domain Authority
PageRank: 5.8/10, 7+ external references
82
Content Freshness
24 of 59 pages updated in the last 30 days
78
Technical Readiness
Moderate technical readiness — some improvements possible
Technical Issues
No FAQ section foundwarning~15 min fix
AI assistants love Q&A content — it's the easiest format for them to extract and quote. Add a Frequently Asked Questions section to your page, and you'll significantly increase your chances of being cited in AI-generated answers.
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>AI models frequently cite FAQ content. Add FAQPage schema to boost your chances of appearing in AI-generated answers.
How does AI see Moz?
When users ask AI about your industry, are you recommended?
G
C
P
Ge
A
See how ChatGPT, Claude, Perplexity, and Gemini talk about Moz
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.
5 render-blocking scriptscriticalPerformance
5 scripts without async or defer attributes. These block page rendering. Add defer or async to non-critical scripts.
Missing Permissions Policy headerwarningSecurity~2 min fix
Add a Permissions-Policy header to control browser feature access.
Quick Fix
# Nginx:
add_header Permissions-Policy "camera=(), microphone=(), geolocation=()" always;
# Next.js (next.config.js headers):
{ key: 'Permissions-Policy', value: 'camera=(), microphone=(), geolocation=()' }Permissions-Policy restricts which browser features your site can use, reducing attack surface.
Meta description too longwarningSEO
Your description is 187 characters. Keep it under 160 for best display.
1 form input may lack labelswarningAccessibility
Form inputs should have associated labels or aria-label attributes so screen readers can identify them.
Skipped heading levelwarningAccessibility
Heading hierarchy jumps from H1 to H4. Don't skip heading levels — this confuses screen readers and assistive technology.
Server response could be fasterwarningPerformance
Server responded in 1.5s. Aim for under 200ms TTFB. Consider caching, CDN, or server-side optimizations.
13 images without lazy loadingwarningPerformance
13 images don't use loading="lazy". Add lazy loading to below-the-fold images to improve initial page load.
No favicon detectedinfoSEO~10 min fix
Add a favicon so your site has an icon in browser tabs, bookmarks, and search results.
Quick Fix
<!-- Add to <head> — SVG favicon (modern browsers) + PNG fallback -->
<link rel="icon" type="image/svg+xml" href="/favicon.svg">
<link rel="icon" type="image/png" sizes="32x32" href="/favicon-32x32.png">
<link rel="apple-touch-icon" sizes="180x180" href="/apple-touch-icon.png">Favicons appear in browser tabs, bookmarks, and search results. They build brand recognition.
Your Potential Score
77
Now
90
Potential
+13 points possible by fixing 10 issues
That moves you from C to A — top 5% of all websites
Track your AI visibility over time
AI Visibility Monitoring
We check AI prompts weekly across ChatGPT, Perplexity, and Google AI. See how often your brand appears.
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.
Start monitoring — from $49/mo
Free tier available · No credit card required
Industry Benchmark
SEO
Avg: 62+32Ahead
AI Readiness
Avg: 35+41Ahead
Performance
Avg: 55+5On par
Security
Avg: 40+20Ahead
Accessibility
Avg: 68+24Ahead
Based on 120+ websites scanned across industries. See full benchmark report →
What This Score Means for You
Slow loading — Sites loading in 3+ seconds lose 53% of mobile visitors (Google data).
Most of these issues have simple, copy-paste fixes. Check the code snippets above for quick solutions.