actaeongroup.com — Website Report

Scored 77/100 · Scanned with Foglift

OverallⓘOverall Score — weighted average of all category scores

actaeongroup.com scored 77. Addressing the 9 listed issues could raise its estimated score to 91.

Scan another domain Save this scan to your free account

1 critical3 warnings9 total issues

Quick wins

~62 min total fix time

1Missing Permissions Policy header~2m

2Missing Content Security Policy header~5m

3Missing Twitter Card tags~5m

https://actaeongroup.com/ · 2026-08-12

Scanned with Foglift · Technical Audit + AI Readiness analysis

AI Search Readiness Risk

Your AI Readiness score of 47/100 identifies technical and content barriers that may make this page harder for AI systems to access, understand, or reuse. It does not show whether AI assistants recommend or cite your site. Check answer-level AI visibility →

AI Action Plan

Website Analysis for https://actaeongroup.com/ Your site scores 77/100 overall. AI Readiness is 47/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 1 critical issue 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. QUICK WINS (Warnings):

1. Missing Permissions Policy header — Add a Permissions-Policy header to control browser feature access. 2. 1 form input may lack labels — Form inputs should have associated labels or aria-label attributes so screen readers can identify them. 3. Skipped heading level — Heading hierarchy jumps from H1 to H3. Don't skip heading levels — this confuses screen readers and assistive technology. AI READINESS BREAKDOWN: • Technical Readiness (T1): 79/100 • Authority Readiness (T2): 21/100 YOUR PRIOR

3 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

47F

Technical79

Authority21

Set up all 6 tiers free →

Brand Mentions

Found 3+ web mentions of "actaeongroup"

Domain Authority

PageRank: 1.1/10, 0+ external references

Content Freshness

21 of 152 pages updated in the last 30 days

Technical Readiness

Moderate technical readiness — some improvements possible

Technical Issues

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.

Pro tip: The biggest drivers of AI visibility are brand mentions and domain authority — not just technical setup. Set up Free monitoring →

How does AI see Actaeongroup?

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

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

Set up weekly monitoring free

SEO & Technical Issues (8)

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 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.

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 H3. Don't skip heading levels — this confuses screen readers and assistive technology.

Missing Twitter Card tagsinfoSEO~5 min fix

Add twitter:card meta tags for optimized appearance when your pages are shared on Twitter/X.

Quick Fix

<meta name="twitter:card" content="summary_large_image">
<meta name="twitter:title" content="Your Page Title">
<meta name="twitter:description" content="A compelling description">
<meta name="twitter:image" content="https://yoursite.com/twitter-image.jpg">

Twitter Card tags control how your page appears when shared on Twitter/X.

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 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 30 HTML comments. Remove unnecessary comments in production to reduce file size.

Your Potential Score

Now

Estimated potential

+14 points estimated improvement from addressing 9 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 Google AI Overview weekly while you're active. Paid plans add ChatGPT, Perplexity, 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 Google AI Overview while active · No credit card required

Compare paid plans — from $49/mo