alejandroberdonces.com
https://alejandroberdonces.com/
Scanned on July 27, 2026
Quick Wins — Top 5 Issues to Fix
- ✗Title-H1 alignment: 40% word overlap — title and H1 should share key termscontent
- ✗Readability: 24 (difficult — simplify language)content
- ✗39% long sentences (>20 words) — break up for readabilitycontent
- ✗1 of 1 images use legacy formats (JPG/PNG/GIF) — convert to WebP/AVIF for 25-50% smaller filescontent
- ✗Missing og:site_name — helps brand recognition in sharessocial
SEO — 80/100 (23 issues)
Failed Checks (23)
- ✗Title-H1 alignment: 40% word overlap — title and H1 should share key termscontent
- ✗Readability: 24 (difficult — simplify language)content
- ✗39% long sentences (>20 words) — break up for readabilitycontent
- ✗1 of 1 images use legacy formats (JPG/PNG/GIF) — convert to WebP/AVIF for 25-50% smaller filescontent
- ✗Missing og:site_name — helps brand recognition in sharessocial
- ✗Missing twitter:card meta tagsocial
- ✗Missing twitter:titlesocial
- ✗Missing twitter:descriptionsocial
- ✗Missing twitter:imagesocial
- ✗No Strict-Transport-Security headersecurity
- ✗Missing X-Content-Type-Options headersecurity
- ✗No Content-Security-Policy header — XSS risksecurity
- ✗No About page link detected — add for credibilitytrust
- ✗No Privacy Policy link — required by GDPR and improves trusttrust
- ✗No Terms of Service link — add for legal compliance and trusttrust
- ✗No author byline — add "By [Name]" for E-E-A-T trusttrust
- ✗No Web App Manifest — add for installability and modern web signalstechnical
- ✗0% sentences use transition words — aim for 20%+content
- ✗No max-image-preview:large — add to robots meta for Google Discovermeta
- ✗Missing X-Frame-Options — clickjacking risksecurity
- ✗No Referrer-Policy header — may leak URL datasecurity
- ✗No Permissions-Policy — restrict camera/mic/geo accesssecurity
- ✗No RSS/Atom feed in <head> — add for content discovery by aggregators and AItechnical
Passed Checks (76)
- ✓Title tag found: "Alejandro Berdonces | Product Manager en Turismo y IA"meta
- ✓Title length: 53 characters (optimal)meta
- ✓Meta description found (152 chars)meta
- ✓Description length: 152 chars (optimal)meta
- ✓Viewport meta tag found (mobile-friendly)meta
- ✓UTF-8 charset declaredmeta
- ✓Language attribute set on HTML tagmeta
- ✓No meta refresh redirect (good)meta
- ✓No robots meta tag (default: index, follow)meta
- ✓Single H1 tag foundcontent
- ✓4 H2 tags foundcontent
- ✓Heading hierarchy is correctcontent
- ✓666 words on page (good content depth)content
- ✓All 1 images have ALT textcontent
- ✓All 1 images have width/height attributes (prevents CLS)content
- ✓No below-fold images to lazy loadcontent
- ✓16 internal links foundcontent
- ✓3 external links foundcontent
- ✓No empty href attributes foundcontent
- ✓All link texts are descriptive (no "click here" or "read more")content
- ✓Open Graph title foundsocial
- ✓Open Graph description foundsocial
- ✓Open Graph image foundsocial
- ✓Open Graph URL foundsocial
- ✓og:type set to "website"social
- ✓HTTPS enabledtechnical
- ✓Canonical tag foundtechnical
- ✓Canonical tag is self-referencing (correct)technical
- ✓Favicon foundtechnical
- ✓Compression: gziptechnical
- ✓URL length: 31 chars (good)technical
- ✓URL uses hyphens or no separators (good)technical
- ✓6 hreflang tags found (multi-language)technical
- ✓No deprecated HTML tags foundtechnical
- ✓Text-to-HTML ratio: 21.4% (good)technical
- ✓Inline CSS: 0.0 KB (acceptable)performance
- ✓Inline JS: 1.9 KB (acceptable)performance
- ✓All 5 external scripts use defer/asyncperformance
- ✓Font preload/preconnect found — faster font loadingperformance
- ✓Cache-Control: max-age=14400performance
- ✓Contact page/email link foundtrust
- ✓1 JSON-LD schema block(s) foundschema
- ✓Schema types: Person, WebSiteschema
- ✓<!DOCTYPE html> declaredtechnical
- ✓No mixed content — all resources use HTTPStechnical
- ✓All 1 JSON-LD block(s) have valid syntaxschema
- ✓font-display: swap detected — prevents invisible textperformance
- ✓Viewport includes width=device-width (responsive)meta
- ✓robots.txt found and allows crawlingtechnical
- ✓robots.txt includes Sitemap referencetechnical
- ✓No AI crawlers blocked in robots.txt — AI search and training can access contenttechnical
- ✓sitemap.xml found with valid formattechnical
- ✓Sitemap contains 31 URL(s)technical
- ✓All 5 checked internal links are workingcontent
- ✓0% nofollow links (0/24) — good link equity flowcontent
- ✓OG image uses absolute URL (correct)social
- ✓All 3 target="_blank" links have rel="noopener"security
- ✓2 resource hint(s) (dns-prefetch/preconnect) — faster loadingperformance
- ✓All schema types have required propertiesschema
- ✓All 6 hreflang codes are valid ISO 639-1technical
- ✓hreflang x-default found — proper language fallbacktechnical
- ✓Title uses "|" separator — Google may rewrite it; consider using "—" insteadmeta
- ✓H1 length: 56 characters (optimal)content
- ✓Title and meta description are different (good)meta
- ✓OG URL matches canonical URL (consistent)social
- ✓Viewport allows zoom (good for accessibility)accessibility
- ✓29 links on page (within limit)content
- ✓DOM size: ~222 elements (good)performance
- ✓No snippet blocking detected (good — content is fully accessible)technical
- ✓No render-blocking scripts in head (good)performance
- ✓0 third-party script domain(s) (acceptable)performance
- ✓ARIA landmarks present: main, navaccessibility
- ✓All 0 form input(s) have labels or aria-labelsaccessibility
- ✓No duplicate IDs found (10 unique IDs)accessibility
- ✓No iframes on pagesecurity
- ✓All 4 H2 sections have sufficient depth (avg 148 words)content
AEO — 67/100 (15 issues)
Failed Checks (14)
- ✗No definition lists (<dl>) — great for term/value pairsdiscoverability
- ✗Few or no lists — add bullet/numbered lists for better AI parsingstructure
- ✗No data tables — tables help AI compare and cite datastructure
- ✗No numbered steps or ordered lists — add for "how to" AI answersstructure
- ✗No author information — AI values attributed contentcitation
- ✗No date information — AI prefers fresh, dated contentcitation
- ✗No Organization schema — AI may not recognize your brandcitation
- ✗Only 1/5 E-E-A-T signals — add about, contact, author infocitation
- ✗No source citations — reference studies and data for authoritycitation
- ✗Formal tone — use more "you", "your", "we" for AI readabilityvoice
- ✗Avg 21 words/sentence — simplify for AI and voicevoice
- ✗No summary section — add Key Takeaways for AI extractionvoice
- ✗No video content — multimedia increases AI engagement and citation ratediscoverability
- ✗Statistics lack source references — attribute data to boost AI trustcitation
Passed Checks (29)
- ✓Structured data found — AI can understand your contentdiscoverability
- ✓666 words in HTML — good content for AI parsingdiscoverability
- ✓Clean URL structurediscoverability
- ✓5 semantic HTML5 elements founddiscoverability
- ✓5 content sections — well-structured for AIdiscoverability
- ✓Description + OG description both present — clear topic signalsdiscoverability
- ✓19 named entities found — helps AI understand contextdiscoverability
- ✓16 internal links — good topic cluster signaldiscoverability
- ✓Q&A/FAQ content detected — useful for AI answers (note: Google retired FAQ rich results in May 2026; the schema itself no longer produces SERP features)structure
- ✓Question-style headings found — ideal for AI snippetsstructure
- ✓Concise answer paragraphs after headings — great for AI citationstructure
- ✓61% short sentences — easy for AI to extractstructure
- ✓100% concise paragraphs — scannable for AIstructure
- ✓5 key-value patterns found — structured data AI can parsestructure
- ✓Avg 154 words/section — sufficient depthstructure
- ✓Statistics and data found in content — highly citablecitation
- ✓2 external links — references authoritative sourcescitation
- ✓Content references 2026/2025 — fresh contentcitation
- ✓Topic focus: 100% — title keywords found in contentcitation
- ✓4 answer-box-ready paragraphs found after headingscitation
- ✓First paragraph is snippet-ready (20-60 words)voice
- ✓5 H2/H3 headings — good content structure for AIvoice
- ✓2 Q&A blocks — perfect format for AI extractionvoice
- ✓No AI-blocking robots directives — AI crawlers can access contentdiscoverability
- ✓Freshness signal found (Last-Modified header or dateModified)citation
- ✓AI search crawlers not blocked in robots.txt (8/8 allowed)discoverability
- ✓Content updated within 90 days — AI engines strongly prefer fresh contentcitation
- ✓Table of Contents detected — helps AI navigate long contentstructure
- ✓2 collapsible section(s) (<details>) — interactive AI-friendly contentstructure
GEO — 57/100 (28 issues)
Failed Checks (28)
- ✗No clear definitions — add "X is..." patterns for AI Overviewoverview
- ✗Content may be too thin for AI Overview (666 words, 4 sections)overview
- ✗No step-by-step content — add numbered guides for AIoverview
- ✗59% optimal paragraphs — aim for 20-80 words per paragraphoverview
- ✗No author schema — add for AI trust signalsauthority
- ✗No source citations — reference studies and data for authorityauthority
- ✗Only 0/5 trust signals — add reviews, certificationsauthority
- ✗Incomplete brand identity — add og:site_name + Organization schemaauthority
- ✗No original data signals — "our research shows..." boosts AI citationauthority
- ✗No expert quotes — add professional opinions for credibilityauthority
- ✗No examples or case studies — add real-world examplesauthority
- ✗No links to authoritative sources — cite Google, Schema.org, etc.authority
- ✗Few external source domains — diversify your referencesauthority
- ✗No comparison content — add vs. sections for AI recommendationsformat
- ✗No summary section — add Key Takeaways or TL;DR for AIformat
- ✗No BreadcrumbList schema — add for better AI contextformat
- ✗Only one list type — use both <ul> and <ol> for content varietyformat
- ✗Single-perspective content — add "on the other hand..." for balanceformat
- ✗No conclusion — add recommendations or a verdict sectionformat
- ✗No <time> elements — wrap dates in <time datetime="...">semantic
- ✗Few sections have subtopics — add H3 subheadings for depthsemantic
- ✗Only 2 Schema type(s) — add more for AI contexttechnical
- ✗Missing definition or list format — combine "X is..." with lists for snippetsoverview
- ✗Only 0 data points — adding statistics measurably boosts generative-engine visibility (GEO study, arXiv:2311.09735)authority
- ✗Author lacks credentials — anonymous content is a GEO penaltyauthority
- ✗Only 1/6 question types — add What, Why, How headingsoverview
- ✗No <figure>/<figcaption> — wrap images with descriptive captions for AIformat
- ✗Only 1 authoritative sameAs link — add Wikipedia, LinkedIn, or Wikidata for entity disambiguationauthority
Passed Checks (31)
- ✓2 question headings — matches "People Also Ask" formatoverview
- ✓Content freshness signals detectedoverview
- ✓Title and H1 are aligned — clear topic focusoverview
- ✓2-level heading hierarchy — deep content structureoverview
- ✓8 industry terms used — domain expertise signalauthority
- ✓1 images all with ALT text — AI can understand visualsformat
- ✓Data visualization elements found (tables/charts)format
- ✓3/6 formatting types used — rich contentformat
- ✓Actionable advice found — AI prefers practical contentformat
- ✓1 entity types in Schema — AI can classify contentsemantic
- ✓7/14 semantic HTML5 elements — deep semantic structuresemantic
- ✓100% title keywords in first 200 words — good prominencesemantic
- ✓21 contextual links — good cross-referencingsemantic
- ✓Content categorization found — clear topic classificationsemantic
- ✓Mobile-friendly (viewport set)technical
- ✓HTTPS secure — trusted by AI systemstechnical
- ✓Page size: 19 KB — reasonabletechnical
- ✓Open Graph fully configured (title, description, image)technical
- ✓Canonical URL set — prevents AI from citing duplicatestechnical
- ✓Page allows AI indexing (no noindex/nosnippet)technical
- ✓Language + OG locale set — clear language signaltechnical
- ✓3 ARIA landmarks found — good accessibility for AItechnical
- ✓All image ALT texts are descriptive (>5 chars)format
- ✓666 words — sufficient depth for AI analysisoverview
- ✓First 200 words contain topic keywords — AI extracts primarily from the startoverview
- ✓No snippet restrictions — AI can freely extract content (good)technical
- ✓Link anchor texts are descriptive — good AI context signalsemantic
- ✓No hidden-text cloaking patterns detectedtrust
- ✓No keyword-stuffing detectedauthority
- ✓Healthy content-to-chrome ratio (~7% boilerplate)overview
- ✓All tested AI crawlers can access the page (GPTBot, ClaudeBot, PerplexityBot)authority
Fix These Issues Automatically
Using WordPress? Install SEO Autopilot for one-click auto-fixes on 65+ issues — with full undo support.
Get SEO Autopilot Plugin