campoverdevecinos.org — AI Website Analysis (Score: 66/100)
66
/ 100
Grade C
https://campoverdevecinos.org
campoverdevecinos.org has good foundations but needs improvements.
✓ 146 Real Checks · 1.6s
🤖
AI Bot Access
14 / 15 passed
93
▼ View all checks
✓
robots.txt Existence
robots.txt found and accessible
✓
GPTBot Access
GPTBot is allowed to crawl
✓
ClaudeBot / anthropic-ai
ClaudeBot is allowed to crawl
✓
Google-Extended Access
Google-Extended is allowed to crawl
✓
CCBot (Common Crawl)
CCBot is allowed to crawl
✓
Bytespider Access
Bytespider is allowed to crawl
✓
PerplexityBot Access
PerplexityBot is allowed to crawl
✓
cohere-ai Access
cohere-ai is allowed to crawl
✓
Amazonbot Access
Amazonbot is allowed to crawl
✓
FacebookBot Access
Facebookbot is allowed to crawl
✓
AppleBot Access
Applebot is allowed to crawl
✓
YouBot Access
YouBot is allowed to crawl
✓
Meta-ExternalAgent Access
Meta-ExternalAgent is allowed to crawl
✓
Crawl-delay Directives
No crawl-delay — bots crawl freely
✗
ai.txt Standard Support
No ai.txt file
🏷️
Meta Tags & Directives
9 / 12 passed
83
▼ View all checks
!
Title Tag Quality
Title: "Campoverde Vecinos" (18 chars)
✓
Meta Description
Description found (123 chars)
✓
Meta Robots Directive
Robots: index, follow
✓
Canonical URL
Canonical: https://campoverdevecinos.org/home.php
✓
Open Graph Tags
OG title set, image set
✗
X (formerly Twitter) Cards
No X card
✓
hreflang Tags
4 hreflang tag(s)
✓
Viewport Meta
Viewport configured
✓
Character Encoding
Charset declared
✓
Favicon & Icons
Favicon found
✓
Author Meta Tag
Author: WALCAM WEBWORKS - https://walcam.co.uk/webworks
!
Theme-Color Meta
No theme-color — optional, adds branded browser chrome on mobile
📊
Structured Data
4 / 15 passed
57
▼ View all checks
✓
JSON-LD Present
1 JSON-LD block(s)
✓
Schema Type Detected
Types: LocalBusiness
!
BreadcrumbList Schema
Not detected — optional, improves rich result eligibility
!
FAQ Schema
Not detected — optional, improves rich result eligibility
!
Article/BlogPosting Schema
Not detected — optional, improves rich result eligibility
!
Product Schema
Not detected — optional, improves rich result eligibility
✓
LocalBusiness Schema
LocalBusiness found
!
Event Schema
Not detected — optional, improves rich result eligibility
!
Review/Rating Schema
Not detected — optional, improves rich result eligibility
!
HowTo Schema
Not detected — optional, improves rich result eligibility
!
VideoObject Schema
Not detected — optional, improves rich result eligibility
!
Organization Schema
Not detected — optional, improves rich result eligibility
✗
Sitelinks Search Box
Search box schema
✓
JSON-LD Validity
All 1 JSON-LD blocks are valid
✗
Rich Results Eligibility
Rich results eligibility
🧱
Semantic HTML
4 / 10 passed
45
▼ View all checks
✗
H1-H6 Hierarchy
H1:0 H2:0 H3:0
✗
Single H1 Tag
No H1
✗
Semantic Elements
0 elements:
!
ARIA Landmarks
0 ARIA roles, 0 labels — add role and aria-label for screen readers
✓
HTML lang Attribute
Language: en
✗
List Structure
0 list elements
✓
Table Accessibility
No tables on page
✓
Form Labels
0 labels / 0 inputs
✗
Descriptive Link Text
8 generic links (click here, read more)
✓
Empty Links Check
No empty links
🧠
AI Content Opt.
4 / 12 passed
54
▼ View all checks
✗
Q&A Content Structure
0 question headings
!
Entity Clarity & Mentions
0 bold elements — use <strong> to highlight key entities for AI
✓
Concise Answer Blocks
272 words
✗
Topic Clustering
0 headings
!
Content Depth vs Breadth
272 words
✓
Fact Attribution & Sources
0 citations, 2 external links as sources
!
Summary / TL;DR Blocks
No summary block — consider adding key takeaways for long content
!
Definition Blocks
No definitions — use <dfn> or bold key terms to help AI extract meaning
!
Comparison Tables
No tables — consider adding for data-heavy content
✓
Data Freshness Signals
Dates found
✓
Citation Format
0 citations, 2 external links
✗
AI-Friendly Headings
0 headings
📝
Content Quality
6 / 12 passed
63
▼ View all checks
!
Content Length
272 words — consider expanding to 600+
✓
Readability Score
Avg sentence: 16 words (easy)
!
Paragraph Optimization
1 paragraphs — break content into more paragraphs
✓
Keyword Distribution
Natural keyword distribution. Top: campoverde (3.3%), vecinos (2.6%), pinar (1.5%)
✗
Internal Linking
0 internal links — add links to related pages
✓
External Authority Links
2 external links
✓
Broken Links
2 links sampled, all OK
✓
Duplicate Content Signals
Canonical set
✗
Content Freshness
No date signals
✓
Multimedia Presence
15 images
!
E-E-A-T Signals
Author attributed, no publish date
✗
Topical Authority Depth
272 words, 0 internal links, 2 external — interlink related pages to show topic coverage
⚡
Performance
4 / 12 passed
58
▼ View all checks
✓
Largest Contentful Paint (LCP)
Page: 12KB, TTFB: 62ms
✓
Interaction to Next Paint (INP)
1 external scripts
!
Cumulative Layout Shift (CLS)
2 of 15 images have width/height
✓
Time to First Byte (TTFB)
TTFB: 62ms
✓
Total Blocking Time (TBT)
1 blocking, 0 async, 0 defer
!
Image Optimization
15 images, 0 lazy-loaded
✗
Lazy Loading
0 of 15 lazy
!
CSS/JS Minification
0 of 1 assets minified
✗
Gzip/Brotli Compression
Compression: gzip
!
CDN Detection
No CDN detected — consider Cloudflare (free) for faster global delivery
!
Render-Blocking Resources
1 render-blocking scripts (use async/defer)
!
Font Loading Strategy
No font-display — may cause flash of invisible text
♿
Accessibility
4 / 12 passed
46
▼ View all checks
!
Image Alt Text
10 of 15 images have alt text
✓
Color Contrast
No obvious contrast issues in CSS
✗
Keyboard Navigation
0 ARIA roles, 0 labels
✗
Focus Indicators
No custom :focus styles
✗
Skip Navigation Link
No skip navigation link — add <a href="#content" class="skip-link">
✗
ARIA Labels
0 ARIA label attributes found
✓
Text Resizable
5 relative vs 0 px font-sizes (use em/rem for accessibility)
✓
Media Captions
No video elements
✓
Form Error Messages
0 labels for 0 inputs across 0 forms
!
WCAG 2.1 AA Estimate
2 of 5 key WCAG criteria met
!
Touch Target Size
12 interactive elements — verify 44x44px minimum in browser
✗
Reduced Motion Support
No prefers-reduced-motion media query — add for users with motion sensitivity
⚙️
Technical SEO
11 / 13 passed
92
▼ View all checks
✓
sitemap.xml Existence
Sitemap found and accessible
✓
Sitemap Validity
Valid XML sitemap
✓
Indexability
No noindex in HTTP headers — page can be indexed
✓
Page Speed Estimate
TTFB: 62ms, Page: 12KB — Fast
✓
Mobile Responsiveness
Viewport meta configured
✓
Core Web Vitals Summary
TTFB:62ms Size:12KB Scripts:2 — Good
✓
URL Structure
Clean URL structure
✓
Redirect Chains
Direct access, no redirects
✓
Custom 404 Page
Custom 404 page detected (returns 404 with content)
!
Pagination
No pagination (ok for single-page content)
!
AMP Support
No AMP — not required since Google dropped AMP preference in 2021
✓
HTTP/2 or HTTP/3
HTTP/3 detected + HTTP/3 via alt-svc
✓
Server Response Compression
Compression: gzip
🔒
Security & Trust
4 / 14 passed
46
▼ View all checks
✓
HTTPS Enabled
HTTPS active
✓
SSL Certificate
SSL valid (Let's Encrypt, 34d left)
✗
HSTS Header
No HSTS
✗
Content Security Policy
No CSP
✗
X-Frame-Options
No X-Frame-Options
✗
X-Content-Type-Options
Missing
✗
Referrer-Policy
No Referrer-Policy
!
Permissions-Policy
No Permissions-Policy — optional, restricts browser features like camera/microphone
✓
No Mixed Content
No mixed content — all resources use HTTPS
!
Privacy Policy Page
No privacy link — required for GDPR compliance and ad networks
!
Subresource Integrity (SRI)
0 SRI hashes — optional, protects against compromised CDN scripts
✓
Cookie Security Flags
No cookies set — good for privacy
!
CORS Policy
No CORS headers (ok for non-API sites)
!
Rate Limiting Headers
No rate limiting headers (optional, recommended for APIs)
🌐
Social & Sharing
7 / 10 passed
80
▼ View all checks
✓
OG Image Present
OG image set
✗
X Card Validation
No X card
✓
LinkedIn Preview Ready
Ready
✓
WhatsApp Preview Ready
Ready
✓
Pinterest Rich Pins
Rich pins ready — OG data complete
!
Social Share Buttons
No share buttons detected
✓
Social Profile Links
1 social links
✓
Author Attribution
Author: WALCAM WEBWORKS - https://walcam.co.uk/webworks
✓
Canonical Social URLs
Canonical set
!
Share Metadata Complete
OG:yes X:no
🔗
Link Health
7 / 9 passed
78
▼ View all checks
✓
Broken Internal Links
0 sampled, all OK
✓
Broken External Links
2 sampled, all OK
✓
Redirect Chain Depth
No redirect chains detected
✗
Orphan Pages Detection
0 of 10 checked sitemap URLs found in internal links (279 total in sitemap)
✓
Nofollow Ratio
2 of 12 nofollow (17%)
✓
Anchor Text Diversity
6 unique anchors
✗
Internal Link Coverage
0 internal links — add internal links to improve crawlability
✓
Outbound Link Quality
2 external domains
✓
Link-to-Content Ratio
12 total links
📝
Template-Based Report
Standard recommendations based on scan results
📋 Executive Summary
campoverdevecinos.org scored 66/100 for AI bot readiness. Passed 78 of 146 checks — 30 failures, 38 warnings across 12 categories. Key issues for AI visibility: title is only 18 chars, 8 images invisible to AI bots (no alt), no security headers (low trust signal), no H1 tag (AI bots can't identify main topic). Weakest areas: Improve Semantic HTML, Fix Accessibility, Add Security Headers.
🎯 Priority Actions
critical
Improve Semantic HTML
campoverdevecinos.org: NO H1 tag found. missing semantic elements: <header>, <main>, <nav>, <footer>. (5 failing checks)
<!-- YOUR site has NO semantic elements -->
<!-- MISSING: <header>, <main>, <nav>, <footer> -->
<header><nav aria-label="Main">...</nav></header>
<main id="content">
<article>
<!-- NO H1 found! Add one: -->
<h1>Main Topic of campoverdevecinos.org</h1>
</article>
</main>
<footer>...</footer>
🤖 DIRECT: AI bots use HTML5 semantic elements (<article>, <main>, <nav>, <header>) to understand page structure. A proper H1→H2→H3 hierarchy tells AI bots the topic and subtopics. Without semantics, AI sees a flat wall of text. 🔍 INDIRECT: Google uses heading structure for featured snippets and passage ranking — the #1 source for AI-generated answers — fixing this area could add ~1.15 to your total score
critical
Fix Accessibility
campoverdevecinos.org: 8 of 15 images have no alt text. no skip navigation link. no ARIA labels. (5 failing checks)
<!-- 8 of 15 images have NO alt text! -->
<img src="photo.jpg" alt="Describe the image">
<a href="#content" class="skip-link">Skip to content</a>
🤖 DIRECT: Proper alt text on images lets AI bots understand visual content. ARIA labels help AI parse interactive elements. Skip navigation and landmark roles make content hierarchy clearer for automated parsing. 🔍 INDIRECT: Google rewards accessible sites with better crawlability scores. Well-structured accessible HTML overlaps heavily with what AI bots need — clear labels, logical order, semantic meaning — fixing this area could add ~1.13 to your total score
high
Add Security Headers
campoverdevecinos.org: missing security headers: HSTS, CSP, X-Frame, X-Content-Type. (5 failing checks)
# campoverdevecinos.org headers:
# ✓ Present: NONE
# ✗ Missing: HSTS, CSP, X-Frame, X-Content-Type, Referrer-Policy
# Add to .htaccess:
Header always set Strict-Transport-Security "max-age=31536000"
Header always set Content-Security-Policy "default-src 'self'"
Header always set X-Frame-Options "SAMEORIGIN"
Header always set X-Content-Type-Options "nosniff"
🤖 DIRECT: While AI bots do not check security headers themselves, AI systems that aggregate sources (like Perplexity) apply trust scoring. Sites without HTTPS are flagged as untrustworthy. 🔍 INDIRECT: Google has confirmed HTTPS is a ranking signal since 2014. Security headers prevent your site from being compromised and serving malware — which gets you deindexed from Google entirely, killing all AI visibility — fixing this area could add ~1.13 to your total score
high
Optimize for AI
campoverdevecinos.org: 272 words, q&a content structure missing, topic clustering missing, ai-friendly headings missing. (3 failing checks)
<!-- campoverdevecinos.org: 272 words (thin!) -->
<h2>What is your main topic?</h2>
<p><strong>Definition:</strong> Clear answer.</p>
<h3>FAQ</h3>
<details><summary>Question about your main topic?</summary>
<p>Answer.</p></details>
🤖 DIRECT: This is what gets you CITED by AI. When someone asks ChatGPT "What is X?" it looks for pages with clear definitions, Q&A headings (What is...? How to...?), FAQ sections with <details>/<summary>, and concise answers in the first paragraph. Without this structure, AI bots may crawl your page but never extract an answer from it. 🔍 INDIRECT: Google featured snippets use the same content patterns — Q&A structure, definition blocks, comparison tables. Pages in position 0 (featured snippet) are the primary source for AI answers — fixing this area could add ~0.96 to your total score
medium
Add Structured Data
Found schema types: LocalBusiness but missing: Sitelinks Search Box, Rich Results Eligibility. (2 failing checks)
<!-- YOUR site has: LocalBusiness -->
<!-- Consider adding for rich results: -->
<script type="application/ld+json">
{"@context":"https://schema.org",
"@type":"WebSite",
"name":"campoverdevecinos.org",
"url":"https://campoverdevecinos.org",
"potentialAction":{"@type":"SearchAction",
"target":"https://campoverdevecinos.org/search?q={query}",
"query-input":"required name=query"}}
</script>
🤖 DIRECT: This is the most powerful signal for AI. JSON-LD structured data (FAQ, HowTo, Product, Article) lets AI bots extract specific facts, prices, steps, and answers without interpreting your prose. Google Gemini, ChatGPT, and Perplexity all parse Schema.org data. 🔍 INDIRECT: Structured data triggers rich results in Google (stars, FAQ dropdowns, product cards) — pages with rich results get 30-50% more clicks, boosting your visibility to AI search tools — fixing this area could add ~0.9 to your total score
medium
Optimize Performance
campoverdevecinos.org: 12KB page size, 15 images, lazy loading, gzip/brotli compression. (2 failing checks)
<!-- campoverdevecinos.org: 12KB, 15 images -->
<!-- Lazy load images below fold: -->
<img src="photo.jpg" loading="lazy" width="800" height="600">
<link rel="preload" href="/fonts/main.woff2" as="font" crossorigin>
<script src="app.js" defer></script>
🤖 DIRECT: AI crawlers (GPTBot, ClaudeBot) have timeout limits of 10-30 seconds. If your page takes too long to respond, they get an incomplete or empty page. Large, unoptimized pages waste crawl budget. 🔍 INDIRECT: Core Web Vitals (LCP, CLS, INP) are a confirmed Google ranking factor since 2021. Faster sites rank higher in Google/Bing — and AI assistants like ChatGPT and Perplexity pull their search results from these rankings — fixing this area could add ~0.88 to your total score
⚡ Quick Wins
8 images on campoverdevecinos.org have no alt text — AI bots can't understand images without it
campoverdevecinos.org has no H1 tag — AI bots use H1 as the main topic identifier for your page
Add security headers (HSTS, CSP, X-Frame) — AI systems trust secure sites more when deciding what to cite
campoverdevecinos.org has only 272 words — AI assistants need substantial content to cite a page as a source
Add twitter:card meta tag — AI tools like Perplexity use this for rich preview cards when citing your site
🔍 Category Analysis
🤖 AI Bot Access
robots.txt found — 12 of 12 major AI bots are allowed to crawl your site. Excellent! GPTBot (ChatGPT), ClaudeBot (Claude), PerplexityBot, and others can all access your content for indexing and citation. No ai.txt — consider adding it for granular AI usage control (training vs. search vs. citation).
→ Fix: ai.txt Standard Support — No ai.txt file
📘 Why this matters for AI visibility
🤖 DIRECT IMPACT: This is the gateway — if AI bots cannot physically access your site, nothing else matters. GPTBot (ChatGPT, 200M+ users), ClaudeBot (Claude, 100M+ users), PerplexityBot, and Google-Extended (Gemini) all check robots.txt first. Allowing them means your content can be indexed, understood, and cited when users ask questions related to your topic.
🏷️ Meta Tags
Title: "Campoverde Vecinos" (18 chars) — too short, AI bots need descriptive titles to identify your page. Description: 123 chars ✓. OG tags: configured with image ✓.
→ Add <meta name="twitter:card" content="summary_large_image"> — enables rich previews in AI tools and social platforms
📘 Why this matters for AI visibility
🤖 DIRECT: AI bots read <title> and <meta description> as the first identifiers of your page content. When ChatGPT or Perplexity cites a source, they display the title as the link text. 🔍 VIA SEARCH: Title tags and meta descriptions are the #1 factor for click-through rates in Google/Bing search results. Higher CTR → higher ranking → AI assistants find you first when searching for answers.
📊 Structured Data
Structured data found — types: LocalBusiness. AI bots like GPTBot and Google Gemini extract facts, entities, and answers directly from JSON-LD without needing to interpret your prose. Consider adding FAQPage or HowTo schema — these are the most commonly extracted types by AI assistants.
→ Fix: Sitelinks Search Box — Search box schema
→ Add FAQ, HowTo, or Product schema — these specific types are what AI assistants extract as direct answers. Google also shows them as expandable rich results, dramatically increasing visibility
📘 Why this matters for AI visibility
🤖 DIRECT: JSON-LD is the most powerful AI optimization. AI bots parse structured data to extract specific facts (prices, ratings, steps, Q&A) without interpreting your prose. FAQPage schema lets AI extract individual question-answer pairs. 🔍 VIA SEARCH: Schema markup triggers Google rich results (stars, FAQ dropdowns, how-to steps) which get 30-50% more clicks, dramatically boosting your search visibility.
🧱 Semantic HTML
No H1 tag found — AI bots cannot determine the main topic of your page. This severely limits your chances of being cited. 0 semantic HTML5 elements — consider using <header>, <main>, <article>, <nav>, <footer> instead of generic <div>s. AI bots understand semantic elements much better. Language: en ✓ — AI bots can match your content to the correct language queries.
→ Fix heading hierarchy (H1→H2→H3) — AI bots use headings to build a topic outline of your page. Google uses them for passage ranking and featured snippets — the primary source for AI answers
→ Keep exactly one H1 per page — this tells AI bots the main topic. Multiple H1s confuse both AI parsers and Google about what your page is primarily about
→ Use <header>, <main>, <article>, <nav> — AI bots parse these to understand page structure. Google also uses semantic HTML for better content extraction and passage indexing
→ Use <ul>/<ol> lists — AI bots extract list items as structured facts. Google uses lists for featured snippet "listicle" format, one of the most common AI answer sources
📘 Why this matters for AI visibility
🤖 DIRECT: AI bots use HTML5 elements (<article>, <main>, <section>) and heading hierarchy (H1→H2→H3) to build a mental model of your content structure. Proper semantics help AI understand what your page is about and what each section covers. 🔍 VIA SEARCH: Google uses semantic HTML for passage ranking (ranking specific paragraphs, not just pages) and featured snippets — the primary source for AI-generated answers.
🧠 AI Content
272 words, 0 headings. Thin content — AI bots may crawl this page but will find insufficient material to cite. Expand to 800+ words. No FAQ section — adding <details>/<summary> FAQ blocks is one of the most effective ways to get cited by AI assistants like ChatGPT and Perplexity. Date signals present ✓ — AI bots prioritize fresh content.
→ Add Q&A headings (What is...? How to...?) — this is the #1 pattern AI assistants look for when extracting direct answers. Google also uses Q&A structure for featured snippets (position 0)
→ Fix: Topic Clustering — 0 headings
→ Fix: AI-Friendly Headings — 0 headings
📘 Why this matters for AI visibility
🤖 DIRECT: This category has the HIGHEST direct impact on AI citation. AI assistants specifically search for: Q&A headings ("What is X?"), FAQ sections, definition blocks, comparison tables, and concise answer paragraphs. Pages structured this way are 5-10x more likely to be cited as a source. 🔍 VIA SEARCH: The same Q&A structure powers Google featured snippets (position 0), which is the single most cited source in AI search results.
📝 Content Quality
272 words — thin content! AI assistants need 300+ words minimum to consider citing a page, ideally 800+. easy readability. 0 internal links — no internal links means AI crawlers discover only this page. 2 external links. 15 images.
→ Fix: Internal Linking — 0 internal links — add links to related pages
→ Fix: Content Freshness — No date signals
→ Fix: Topical Authority Depth — 272 words, 0 internal links, 2 external — interlink related pages to show topic coverage
📘 Why this matters for AI visibility
🤖 DIRECT: AI bots evaluate content depth, freshness, and authority before citing. A 12-word page gives AI nothing to reference. Comprehensive content (800+ words) with dates, author info, and expert signals makes your site a credible source worth citing. 🔍 VIA SEARCH: Google E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) directly determines your ranking. Higher ranking = AI assistants find you first.
⚡ Performance
TTFB: 62ms ✓ — fast server response. Page: 12KB ✓ — lightweight. 1 scripts, 15 images. Compressed ✓ — serving gzip/brotli reduces transfer size 60-80%.
→ Add loading="lazy" to below-fold images — improves LCP (Largest Contentful Paint), a Core Web Vitals metric Google uses for ranking. Faster pages also get more complete AI crawls
→ Enable gzip/Brotli — reduces page size 60-80%, making AI crawler visits faster and more complete. Also a Core Web Vitals factor for Google ranking
📘 Why this matters for AI visibility
🤖 DIRECT: AI crawlers have 10-30 second timeouts. Slow pages may be partially crawled, missing important content. A fast TTFB (<200ms) ensures complete crawling. 🔍 VIA SEARCH: Core Web Vitals (LCP, CLS, INP) are confirmed Google ranking factors since 2021. Faster sites rank higher → appear more often in AI search results. Studies show a 1-second delay reduces conversions by 7%.
♿ Accessibility
10/15 images with alt text — 5 images are invisible to AI bots without alt text. AI cannot interpret images directly; it relies entirely on alt descriptions. 0 ARIA labels — without ARIA labels, AI bots may misinterpret navigation, forms, and interactive content. No skip navigation — this link helps AI bots distinguish main content from navigation, and is a WCAG requirement for accessibility.
→ Fix: Keyboard Navigation — 0 ARIA roles, 0 labels
→ Fix: Focus Indicators — No custom :focus styles
→ Add "Skip to content" link — helps AI parsers identify where main content begins (vs navigation). Also a WCAG accessibility requirement that improves overall content structure
→ Add aria-label to interactive elements — helps AI bots understand navigation and form purposes. Also improves Google accessibility scoring which is an indirect ranking factor
📘 Why this matters for AI visibility
🤖 DIRECT: Alt text is critical — AI bots cannot see images and rely entirely on alt descriptions. ARIA labels help AI understand interactive elements. Good accessibility = clear content structure that AI can parse accurately. 🔍 VIA SEARCH: Google Lighthouse accessibility scores factor into overall page quality. Sites meeting WCAG guidelines tend to have cleaner HTML that both Google and AI bots parse more effectively.
⚙️ Technical SEO
XML Sitemap found ✓ — AI crawlers (GPTBot, ClaudeBot, PerplexityBot) use sitemaps to discover all your pages efficiently in a single crawl session. Google also uses lastmod dates to prioritize fresh content. Mobile ready ✓ — Google uses mobile-first indexing, meaning your mobile version determines ranking (and AI search visibility). Compression active ✓.
→ All checks passing — maintain current standards and monitor for changes in AI crawler behavior
📘 Why this matters for AI visibility
🤖 DIRECT: XML sitemaps are a discovery mechanism — they tell AI crawlers exactly which pages exist, their priority, and when they were last updated. Without a sitemap, AI bots crawl blindly following links and may miss deep pages. 🔍 VIA SEARCH: Technical SEO is the foundation of all search visibility. Mobile-readiness, proper canonicalization, compression, and indexing directly determine whether Google can find and rank your content.
🔒 Security
HTTPS active ✓ — required for Google ranking since 2014, and some AI systems (Perplexity) only cite HTTPS sources. SSL certificate valid ✓. Security headers: none! Without security headers, your site is vulnerable to XSS, clickjacking, and other attacks. A compromised site gets removed from Google, eliminating all AI visibility.
→ Add Strict-Transport-Security header — enforces HTTPS permanently, preventing downgrade attacks. Builds trust score with AI aggregation systems and improves Google security assessment
→ Fix: Content Security Policy — No CSP
→ Add X-Frame-Options: SAMEORIGIN — prevents clickjacking. Security vulnerabilities can lead to Google Safe Browsing warnings which block AI citations
→ Add X-Content-Type-Options: nosniff — prevents MIME-type confusion attacks that could serve malicious content through your domain
📘 Why this matters for AI visibility
🤖 DIRECT: While AI bots don't inspect headers directly, AI aggregation systems (like Perplexity) apply trust scoring. HTTPS is baseline trust. 🔍 VIA SEARCH: HTTPS is a confirmed Google ranking signal. A hacked site (possible without CSP, X-Frame-Options) gets flagged by Google Safe Browsing and completely deindexed — killing all search and AI visibility instantly. Security is insurance.
🌐 Social Sharing
Open Graph tags complete ✓ — AI search tools like Perplexity use og:title, og:description, and og:image to create rich preview cards when citing your content. No X card — your links look plain when shared, reducing social engagement which indirectly affects search ranking. 1 social media links — good for cross-platform presence.
→ Add <meta name="twitter:card" content="summary_large_image"> — enables rich previews when AI tools cite your site and when shared on X/Twitter
📘 Why this matters for AI visibility
🤖 DIRECT: When AI tools like Perplexity cite your site, they use og:image and og:description for rich preview cards. Without OG tags, your citation is a plain text link that users are less likely to click. 🔍 VIA SEARCH: Social sharing generates backlinks and social signals. Viral content gets linked by other sites → more backlinks → higher Google ranking → more AI visibility. OG tags are the investment that enables this cycle.
🔗 Link Health
0 internal links — no internal links! AI crawlers can only find this page, they cannot discover your other content. 2 external links to 2 domains — outbound links to authoritative sources boost your E-E-A-T credibility with both Google and AI systems. 2 nofollow links.
→ Create XML sitemap — AI crawlers (GPTBot, ClaudeBot) use sitemaps to discover pages efficiently. Google requires sitemaps for large sites and uses lastmod dates to prioritize fresh content crawling
→ Fix: Internal Link Coverage — 0 internal links — add internal links to improve crawlability
📘 Why this matters for AI visibility
🤖 DIRECT: AI crawlers follow links to discover content. Broken links = dead ends where crawling stops. Good internal linking means AI indexes more pages per visit. External links to authoritative sources signal that you cite credible information. 🔍 VIA SEARCH: Google PageRank flows through internal links. External links to authority sites boost your E-E-A-T. A clean link graph is foundational for both Google ranking and AI crawler efficiency.
🗺️ Long-Term Strategy
To improve campoverdevecinos.org's AI visibility from 66 to 80+: Start with Improve Semantic HTML — this most limits how AI bots understand your site. Then tackle Fix Accessibility. Quick wins: fix title is only 18 chars, 8 images invisible to AI bots (no alt), no security headers (low trust signal). Goal: make your content easy for ChatGPT, Claude, and Perplexity to crawl, understand, and cite.
🔄 Want a Fresh Scan?
Results may have changed since 2026-02-27 00:15:48
Re-Scan campoverdevecinos.org