achapubli.com.br — Website Report
Scored 60/100 · Scanned with Foglift
achapubli.com.br scored 60. Addressing the 17 listed issues could raise its estimated score to 78.
Quick wins
~117 min total fix timehttps://achapubli.com.br/ · 2026-08-13
Scanned with Foglift · Technical Audit + AI Readiness analysis
AI Search Readiness Risk
Your AI Readiness score of 30/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://achapubli.com.br Your site scores 60/100 overall. AI Readiness is 30/100 — structural barriers may make this page harder for AI systems to access, understand, and reuse. We found 3 critical issues and 11 warnings. Here's your prioritized action plan:
FIX FIRST (Critical): 1. AI search engines can't read your site — Your site blocks 4 AI crawlers (GPTBot, ClaudeBot, Google-Extended...). This means ChatGPT, Perplexity, and other AI assistants won't recommend your site in their answers. Ask your developer to update the robots.txt file to allow these crawlers.
2. Missing Content Security Policy header — Add a Content-Security-Policy header to prevent XSS and injection attacks. 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. 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 the
13 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 Readiness
Technical and authority signals that support AI systems in accessing, understanding, and reusing your content
Technical Issues
Your site blocks 4 AI crawlers (GPTBot, ClaudeBot, Google-Extended...). This means ChatGPT, Perplexity, and other AI assistants won't recommend your site in their answers. Ask your developer to update the robots.txt file to allow these crawlers.
# Add to your robots.txt to allow AI crawlers:
User-agent: GPTBot
Allow: /
User-agent: ChatGPT-User
Allow: /
User-agent: ClaudeBot
Allow: /
User-agent: PerplexityBot
Allow: /
User-agent: Google-Extended
Allow: /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.
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.
<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>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.
<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>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 Achapubli?
When users ask AI about your industry, are you recommended?
Start with weekly Google AI Overview checks for Achapubli. Paid plans add ChatGPT, Perplexity, Gemini, and Claude.
SEO & Technical Issues (13)
Add a Content-Security-Policy header to prevent XSS and injection attacks.
# 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'" }Your viewport meta tag prevents users from zooming. This is an accessibility violation — users with low vision need to zoom to read content.
<!-- 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 -->Set X-Content-Type-Options: nosniff to prevent MIME-type sniffing.
# Nginx:
add_header X-Content-Type-Options "nosniff" always;
# Next.js (next.config.js headers):
{ key: 'X-Content-Type-Options', value: 'nosniff' }Set X-Frame-Options to prevent clickjacking attacks.
# Nginx:
add_header X-Frame-Options "SAMEORIGIN" always;
# Next.js (next.config.js headers):
{ key: 'X-Frame-Options', value: 'SAMEORIGIN' }Add a Referrer-Policy header to control information leakage.
# 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' }Add a Permissions-Policy header to control browser feature access.
# Nginx:
add_header Permissions-Policy "camera=(), microphone=(), geolocation=()" always;
# Next.js (next.config.js headers):
{ key: 'Permissions-Policy', value: 'camera=(), microphone=(), geolocation=()' }Found 2 of 8 images without alt attributes. Alt text is critical for accessibility (screen readers) and SEO (image search).
2 of 8 images have no alt attribute. Screen readers cannot describe these images to visually impaired users.
Form inputs should have associated labels or aria-label attributes so screen readers can identify them.
1 script without async or defer attributes. These block page rendering. Add defer or async to non-critical scripts.
6 images don't use loading="lazy". Add lazy loading to below-the-fold images to improve initial page load.
Add more internal links to help search engines discover and index your other pages. Internal linking also helps distribute page authority.
Add a 'Skip to main content' link at the top of the page so keyboard users can bypass repetitive navigation.
<!-- 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>Your Potential Score
60
Now
78
Estimated potential
+18 points estimated improvement from addressing 17 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.
Weekly Google AI Overview while active · No credit card required
Compare paid plans — from $49/moIndustry Benchmark
Based on 120+ websites scanned across industries. See full benchmark report →
What This Score Means for You
Readiness gaps — This Technical Audit found barriers that can make your page harder for AI systems to access, understand, or reuse. It does not measure citations, recommendations, or answer-level visibility.
Security gaps — Missing security headers may flag your site as unsafe in browsers, hurting trust and conversions.
Most of these issues have simple, copy-paste fixes. Check the code snippets above for quick solutions.
Security score: 20/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.
AI visibility preview
See which brands Google AI Overview surfaces for your category.