Foglift
www.ottersbrook.com — Website Report
Scored 61/100 · Scanned with Foglift
D
ottersbrook.com scored 61. One fix would take it to 81.
2 critical14 warnings22 total issues
Quick wins
~179 min total fix time1Missing X-Frame-Options header~2m
2Missing Referrer Policy header~2m
3Missing Permissions Policy header~2m
https://www.ottersbrook.com/ · 4/25/2026, 3:49:38 PM
Scanned with Foglift · SEO + AI Visibility analysis
AI Action Plan
Website Analysis for https://www.ottersbrook.com Your site scores 61/100 overall, but AI engines may be missing you. Your AI Visibility is 58/100 — there's significant room to improve how ChatGPT, Perplexity, and Gemini surface your brand. We found 2 critical issues and 14 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. QUICK WINS (Warnings): 1. Structured data needs more detail — You have basic structured data, but it's missing the rich types that AI engines look for — like FAQ sections, how-to guides, or product info. Adding these helps AI assistants extract and cite your content more accurately. 2. No FAQ section found — AI assistants love Q&A content — it's the e
15 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
58D
85
Brand Mentions
Found 17+ web mentions of "ottersbrook"
4
Domain Authority
PageRank: 0.0/10, 1+ external references
92
Content Freshness
10 of 10 pages updated in the last 30 days
58
Technical Readiness
Moderate technical readiness — some improvements possible
Technical Issues
Structured data needs more detailwarning
You have basic structured data, but it's missing the rich types that AI engines look for — like FAQ sections, how-to guides, or product info. Adding these helps AI assistants extract and cite your content more accurately.
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.
AI doesn't know who you areinfo~10 min fix
Your site is missing identity markup that tells AI engines "we are [Company X], and here's what we do." Adding this helps AI assistants recognize your brand as an authority and recommend you by name.
Quick Fix
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Your Company",
"url": "https://yoursite.com",
"logo": "https://yoursite.com/logo.png",
"sameAs": [
"https://twitter.com/yourhandle",
"https://linkedin.com/company/yourcompany",
"https://github.com/yourorg"
],
"contactPoint": {
"@type": "ContactPoint",
"email": "hello@yoursite.com",
"contactType": "customer service"
}
}
</script>Entity markup tells AI models who you are, making them more likely to cite your brand accurately.
How does AI see Ottersbrook?
When users ask AI about your industry, are you recommended?
G
C
P
Ge
A
See how ChatGPT, Claude, Perplexity, and Gemini talk about Ottersbrook
SEO & Technical Issues (19)
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.
Missing X-Frame-Options headerwarningSecurity~2 min fix
Set X-Frame-Options to prevent clickjacking attacks.
Quick Fix
# Nginx:
add_header X-Frame-Options "SAMEORIGIN" always;
# Next.js (next.config.js headers):
{ key: 'X-Frame-Options', value: 'SAMEORIGIN' }X-Frame-Options prevents clickjacking by controlling who can embed your page in an iframe.
Missing Referrer Policy headerwarningSecurity~2 min fix
Add a Referrer-Policy header to control information leakage.
Quick Fix
# Nginx:
add_header Referrer-Policy "strict-origin-when-cross-origin" always;
# Next.js (next.config.js headers):
{ key: 'Referrer-Policy', value: 'strict-origin-when-cross-origin' }Controls how much referrer information is sent with requests, protecting user privacy.
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.
Title tag too longwarningSEO
Your title is 63 characters. Keep it under 60 for best display in search results.
Meta description too longwarningSEO
Your description is 179 characters. Keep it under 160 for best display.
Skipped heading levelwarningAccessibility
Heading hierarchy jumps from H2 to H4. Don't skip heading levels — this confuses screen readers and assistive technology.
Potential low contrast textwarningAccessibility
Some text appears to use light colors that may not have sufficient contrast against the background. WCAG requires a minimum 4.5:1 contrast ratio.
Server response could be fasterwarningPerformance
Server responded in 2.0s. Aim for under 200ms TTFB. Consider caching, CDN, or server-side optimizations.
Large HTML documentwarningPerformance
Your HTML is 2873KB. Large HTML documents take longer to parse. Consider lazy loading content or splitting into multiple pages.
11 external scripts loadedwarningPerformance
Your page loads 11 external JavaScript files. Consider bundling some together and deferring non-critical scripts.
1 render-blocking scriptwarningPerformance
1 script without async or defer attributes. These block page rendering. Add defer or async to non-critical scripts.
18 images without lazy loadingwarningPerformance
18 images don't use loading="lazy". Add lazy loading to below-the-fold images to improve initial page load.
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 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.
Heavy inline stylesinfoPerformance
Found 27 elements with large inline styles. Move these to external CSS for better caching and maintainability.
No resource hintsinfoPerformance~5 min fix
Add <link rel='preconnect'> for critical third-party domains to reduce connection setup time.
Quick Fix
<!-- Add to <head> for your critical third-party domains -->
<link rel="preconnect" href="https://fonts.googleapis.com">
<link rel="dns-prefetch" href="https://cdn.example.com">Preconnect and DNS-prefetch reduce connection time to third-party domains by starting the handshake early.
HTML contains many commentsinfoPerformance
Found 50 HTML comments. Remove unnecessary comments in production to reduce file size.
Your Potential Score
61
Now
82
Potential
+21 points possible by fixing 22 issues
That moves you from D to B — top 15% 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+17Ahead
AI Readiness
Avg: 35+24Ahead
Performance
Avg: 55-7Behind
Security
Avg: 40-5Behind
Accessibility
Avg: 68+19Ahead
Based on 120+ websites scanned across industries. See full benchmark report →
What This Score Means for You
Security gaps — Missing security headers may flag your site as unsafe in browsers, hurting trust and conversions.
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.
Security score: 35/100
Most security issues are 5-minute fixes — adding HTTP headers to your server config. Check the code fixes above for the exact headers to add — we include copy-paste code for Nginx, Apache, Vercel, and Netlify.