Este informe de auditoría web analiza https://AgenciaDeMarketing.org/ en 12 dimensiones críticas con recomendaciones accionables.
https://AgenciaDeMarketing.org/
87Buenode 100
Informe de Auditoría Web
Agencia de Marketing Digital en Lima, Perú y LatAm
1 de agosto de 2026 178ms respuesta HTTPS Seguro
Resumen Ejecutivo
https://AgenciaDeMarketing.org/ scores 87/100 (B+). Strong areas include Performance, Accessibility, GEO. The site has 1174 words, 2 images, and 2 schema blocks. Data confidence: 95%. Sustainability score: 90/100. Focus on the top recommendations below to improve your score.
178ms
Tiempo de Respuesta
1,174
Conteo de Palabras
2
Imágenes
72
Enlaces
Vista Previa del Sitio
Visitar SitioCargando vista previa…
Historial de Puntuación
Escaneo actual9 escaneos registrados↓ 6 pts desde el primer escaneo
Desglose de Puntuación — 12 Dimensiones
Problemas Principales a Solucionar
1[SEO] Cloudflare Email Protection detected (1 obfuscated links) — these appear as /cdn-cgi/l/email-protection and return 404 to crawlers
2[SEO] High dofollow external link count (11) — excessive link equity leakage
3[SEO] Primary keyword "agencia marketing digital" not found in H1
4[SEO] Primary keyword missing from first paragraph
5[SEO] Very high internal link density (50.3/1k words) — may appear spammy
6[SEO] Primary keyword "agencia marketing digital" not found in body content
7[Security] No privacy policy detected
8[Security] No cookie consent banner detected
9[Security] No Subresource Integrity (SRI) on external scripts
10[Security] security.txt file is missing — no standardized channel for reporting vulnerabilities
Recomendaciones Principales
1[Impact: Medium | Effort: Low] Use JavaScript-rendered email addresses (client-side assembly) instead of plain mailto: links to prevent Cloudflare from obfuscating them. Alternative: disable Email Address Obfuscation in Cloudflare dashboard [Impact: Medium | Effort: Low]
2[Impact: Medium | Effort: Low] Reduce dofollow external links to 2–5 per page. Add rel="nofollow" to low-value or affiliate links to preserve PageRank
3[Impact: High | Effort: Low] Include your primary keyword in the H1 heading for strongest on-page SEO signal
4[Impact: High | Effort: Low] Include your primary keyword naturally in the first paragraph to establish topical relevance early
5[Impact: High | Effort: Low] Include your primary keyword in the URL slug for improved crawlability and click-through rates
6[Impact: High | Effort: Medium] Link to an About page to establish authoritativeness and brand trust (E-E-A-T)
7[Impact: Medium | Effort: Medium] Convert your OG image to WebP format for faster social media loading (1200×630px recommended)
8[Impact: Medium | Effort: Low] Add <meta property="article:published_time"> for content freshness signals in social shares
9[Impact: Medium | Effort: Medium] Add <meta property="article:modified_time"> to signal content freshness
10[Impact: High | Effort: Medium] Reduce internal link density — excessive linking dilutes individual link value
11[Impact: High | Effort: Low] Include your primary keyword naturally throughout the content body — aim for 0.5–2.5% density
12[Impact: Medium | Effort: Medium] Add TL;DR summaries or definition-style opening paragraphs ("X is...") for zero-click/featured snippet capture
Análisis Detallado por Categoría
Hallazgos Clave
1Title tag is 50 characters — within optimal 50–60 range (Google 2025-2026)
2Meta description is 144 characters — within optimal 140–160 range (2025-2026)
3Single H1 tag present: "Agencia de Marketing Digital"
4Clean heading hierarchy with no skipped levels
5Canonical URL is set and matches the page URL
6Complete Open Graph tags (title, description, image, url, type)
7Complete Twitter Card tags present
8HTML lang attribute set to "es"
9Favicon present
1059 internal links help establish site architecture
1111 external links provide reference signals
12Content length of 1174 words is adequate
1372 total links — within recommended range
14URL length (31 chars) is within optimal range
15All external links have proper rel attributes (nofollow/noopener)
16No redirect chain — direct URL resolution
17Healthy internal link ratio: 82% of links are internal
18Good anchor text diversity: 88% unique anchor texts
19Good keyword alignment between title and H1
20Primary keyword not in URL — acceptable for homepage/root URLs
21Strong E-E-A-T signals detected (5 indicators)
22og:locale set to "es_419"
23OG image dimensions ≥1200×630px — optimal for all platforms
24Twitter card uses summary_large_image — maximum visual impact
25Moderate entity presence: Video Publicitario, Marketing Digital, Jeremy Valdivia
26Social share buttons detected: ShareThis
27OG sharing completeness: 100% — all tags present for optimal social previews
Problemas Encontrados
1Cloudflare Email Protection detected (1 obfuscated links) — these appear as /cdn-cgi/l/email-protection and return 404 to crawlers
2High dofollow external link count (11) — excessive link equity leakage
3Primary keyword "agencia marketing digital" not found in H1
4Primary keyword missing from first paragraph
5Very high internal link density (50.3/1k words) — may appear spammy
6Primary keyword "agencia marketing digital" not found in body content
Recomendaciones para Alcanzar 100%
1Use JavaScript-rendered email addresses (client-side assembly) instead of plain mailto: links to prevent Cloudflare from obfuscating them. Alternative: disable Email Address Obfuscation in Cloudflare dashboard [Impact: Medium | Effort: Low]
2Reduce dofollow external links to 2–5 per page. Add rel="nofollow" to low-value or affiliate links to preserve PageRank
3Include your primary keyword in the H1 heading for strongest on-page SEO signal
4Include your primary keyword naturally in the first paragraph to establish topical relevance early
5Include your primary keyword in the URL slug for improved crawlability and click-through rates
6Link to an About page to establish authoritativeness and brand trust (E-E-A-T)
7Convert your OG image to WebP format for faster social media loading (1200×630px recommended)
8Add <meta property="article:published_time"> for content freshness signals in social shares
9Add <meta property="article:modified_time"> to signal content freshness
10Reduce internal link density — excessive linking dilutes individual link value
11Include your primary keyword naturally throughout the content body — aim for 0.5–2.5% density
12Add TL;DR summaries or definition-style opening paragraphs ("X is...") for zero-click/featured snippet capture
13Add engagement signals: related posts section, "Read next" links, and table of contents to increase dwell time
Hallazgos Clave
1Excellent server response time: 178ms
2HTML size is 189KB — acceptable
32 framework-managed script(s) — optimized by build pipeline
4Modern image formats (WebP/AVIF) detected
5Responsive images with srcset detected
6Most images have explicit width/height attributes (prevents layout shift)
7Preconnect hints for: https://www.googletagmanager.com, https://analytics.ahrefs.com
8Preloaded resources: image, script, image
9font-display property detected — reduces invisible text during font loading
1017 async and 0 deferred scripts
11Cache-Control header with max-age is set
1218 inline scripts (framework hydration/data — standard for SSR apps)
13Lean CSS payload (~60KB)
14JavaScript payload (~1061KB) is acceptable for framework app
15HTTP/1.1 detected — protocol upgrade managed at CDN/infrastructure level
16CDN detected: Cloudflare — reduces latency for global users
17Gzip compression enabled
181 third-party script(s) — manageable count
198 resource hints (preconnect/prefetch/preload) optimize loading
203 framework hydration script(s) — standard for SSR apps
21Estimated LCP: ~938ms — within Google's "good" threshold (<2.5s)
22Estimated CLS: 0.1 — within Google's "good" threshold (<0.1)
23Estimated INP: ~185ms — within Google's "good" threshold (<200ms)
24Variable fonts detected — reduces total font file downloads
25Comprehensive analytics: GA4 (G-ZGLL048NNT) + GTM (GTM-KLRCQSFK) with event tracking
Recomendaciones para Alcanzar 100%
1Upgrade to HTTP/2 or HTTP/3 for faster parallel resource loading and header compression
Hallazgos Clave
1Viewport meta tag present: width=device-width, initial-scale=1
2HTML5 doctype declared
3Character encoding declared
4Theme color meta tag set for mobile browsers
5Web app manifest detected — PWA-ready
6Apple touch icons present
7Service worker detected — offline capability possible
8Responsive images via srcset serve appropriate sizes per device
9PWA install-ready: manifest + service worker + HTTPS all present
10Web app manifest includes 7 icon sizes — good coverage
Recomendaciones para Alcanzar 100%
1Add env(safe-area-inset-*) CSS for proper display on notched/island devices
2Add :active / touch-action CSS for tactile feedback on mobile interactions
Hallazgos Clave
1HTTPS enabled — encrypted connection
2HSTS header present — enforces HTTPS
3Content Security Policy header present
4X-Content-Type-Options: nosniff is set
5X-Frame-Options header prevents clickjacking
6Referrer-Policy set to: strict-origin-when-cross-origin
7Permissions-Policy header restricts browser features
8Cross-Origin-Opener-Policy set
9Cross-Origin-Resource-Policy set
10Cross-Origin-Embedder-Policy set
11Server via CDN proxy (cloudflare) — header added by infrastructure, not application
12All external links have security-safe rel attributes
13HSTS with preload and adequate max-age — eligible for browser preload list
14No cookie security issues detected
15CSP strictness score 40/100 — adequate for modern framework apps that require inline styles/scripts
16CSP uses 2 unsafe-inline directive(s) — standard requirement for modern SSR frameworks
17Permissions-Policy restricts 4 feature(s) — consider expanding to more features
18No server software/technology fingerprints exposed in headers or markup
19No stack traces or sensitive error details exposed in responses
20No obvious secret/API-key patterns exposed in page source
2119 script resource(s) catalogued for software-composition review
22No common sensitive paths (.git, .env, server-status, …) were publicly accessible
23Cross-origin isolation enabled (COOP + COEP) — hardened against Spectre-style side-channel and cross-origin leaks
Problemas Encontrados
1No privacy policy detected
2No cookie consent banner detected
3No Subresource Integrity (SRI) on external scripts
4security.txt file is missing — no standardized channel for reporting vulnerabilities
52 email address(es) exposed in page source (e.g. [email protected], [email protected]) — can be harvested for spam/phishing
6Legacy X-XSS-Protection header present — deprecated and can introduce vulnerabilities in older browsers
7robots.txt discloses sensitive-looking path(s): /admin/ — Disallow entries can act as a map for attackers
8A private/internal IP address (RFC 1918) is disclosed in the page source — reveals internal network topology
91 untrusted <iframe>(s) without a sandbox attribute — embedded content runs with full privileges
Recomendaciones para Alcanzar 100%
1Add a privacy policy link — required by GDPR, CCPA, and builds user trust
2Implement a cookie consent banner for GDPR/ePrivacy compliance
3Add integrity attributes to external scripts/stylesheets to prevent supply-chain attacks
4Strengthen CSP: consider nonce-based policies when feasible
5When feasible, migrate to nonce-based CSP for inline scripts/styles
6Expand Permissions-Policy to restrict camera, microphone, geolocation, payment, usb, and autoplay
7Add an RFC 9116 security.txt at /.well-known/security.txt with Contact and Expires fields so researchers can responsibly report security issues [Impact: Low | Effort: Low]
8If these emails are not meant to be public, obfuscate them or replace with a contact form; for intentional contact addresses this is informational only [Impact: Info | Effort: Low]
9Remove the deprecated X-XSS-Protection header and rely on a strong Content-Security-Policy instead [Impact: Low | Effort: Low]
10Avoid listing admin/private paths in robots.txt; protect them with authentication instead of relying on obscurity [Impact: Low | Effort: Low]
11Remove references to internal hostnames/IP addresses from public responses [Impact: Medium | Effort: Low]
12Add the sandbox attribute (with the minimum required allow-* tokens) to iframes embedding third-party/untrusted content [Impact: Medium | Effort: Low]
Hallazgos Clave
1Language declared: es
2Skip navigation link present
3All key landmarks present (main, nav, footer)
4All 2 images have alt attributes
5All iframes have title attributes
6Rich ARIA implementation: 20 elements with ARIA attributes
7Focus styles detected for keyboard navigation
83 minor HTML validity issue(s) — common in modern framework component patterns
91 table(s) have captions/labels
Problemas Encontrados
1Potential contrast issues: white text on very light background detected
21 duplicate ID(s) — breaks ARIA references and label associations
Recomendaciones para Alcanzar 100%
1Ensure all text meets WCAG AA contrast ratio of at least 4.5:1
2Review HTML structure for any non-framework-related nesting issues
3Ensure all element IDs are unique — duplicate IDs break form labels, ARIA relationships, and fragment navigation
Hallazgos Clave
12 schema block(s): Organization, Organization, WebSite, WebPage, ProfessionalService, LocalBusiness, FAQPage, Person, BreadcrumbList, HowTo, VideoObject
2Hreflang tags: es, es-419, es-ES, x-default
3Strong semantic markup: header, nav, main, section, details, summary, article, footer, aside, address
4Complete social metadata (OG + Twitter Card)
5Breadcrumb navigation present — aids AI in understanding site hierarchy
6FAQ/Q&A content patterns detected — highly valuable for AI citation
7Sitemap reference detected
88 strong entity mentions (bold/emphasized text)
9Social presence signals: youtube, facebook, instagram, tiktok, linkedin
104 call-to-action elements detected
11No AI crawlers blocked via meta tags — content accessible to AI search engines
12robots.txt file found
13AI crawlers explicitly allowed in robots.txt: GPTBot, ChatGPT-User, Google-Extended, ClaudeBot, PerplexityBot, Amazonbot, anthropic-ai, Applebot-Extended, Bytespider, CCBot, Cohere-ai, Diffbot, FacebookBot, ImagesiftBot
14robots.txt references 1 sitemap(s) — aids AI crawler discoverability
15Moderate RAG-friendliness (58/100)
16Additional AI crawlers allowed: PerplexityBot, Bytespider, Amazonbot, Applebot-Extended, Cohere-ai
17Content provenance signals detected (citations with sources, attributed claims)
18JS content ratio 59% — expected for SSR framework apps that serve pre-rendered HTML with hydration scripts
Problemas Encontrados
1No llms.txt file found — AI models cannot find structured guidance for your site
2No content freshness signals (dateModified, datePublished, <time> elements)
Recomendaciones para Alcanzar 100%
1Add more structured data types (FAQ, HowTo, Breadcrumb) to improve AI comprehension
2Create /llms.txt following the llms.txt standard: # Title, > description, ## Overview, ## Core Services, ## Key Pages with full URLs
3Create /llms-full.txt with comprehensive documentation (services, pricing, team, case studies) for AI models that need depth
4Add <link rel="alternate" type="text/plain" href="/llms.txt"> in your HTML <head> for AI discoverability
5Add id attributes to headings and section elements for better RAG (Retrieval Augmented Generation) chunk targeting by AI systems
6Add dateModified and datePublished meta tags and use <time datetime="..."> elements — AI models prefer fresh, timestamped content
Hallazgos Clave
1Moderate content depth (1174 words)
2Rich Q&A content (10 FAQ/accordion elements)
38 emphasized entities
4Good semantic-to-div ratio: 38 semantic elements
5Structured content: 6 lists, 1 tables — easily parsed by AI
6E-E-A-T schema signals present (2 types)
7Speakable schema detected — content optimized for voice assistants
86 external citations — strong reference density for AI model training
99 statistics/data points — excellent for AI knowledge extraction
10Author attribution present but missing expertise signals
11Clear value proposition detected in heading elements
Problemas Encontrados
1No clear call-to-action elements detected
2No CTA above the fold
3Insufficient trust signals for conversion optimization
4No social proof elements
Recomendaciones para Alcanzar 100%
1Include expert quotes in <blockquote> elements to boost E-E-A-T and citation potential
2Add author bio, credentials, and links to establish expertise signals for AI E-E-A-T evaluation
3Add prominent CTAs with action-oriented text ("Get Started", "Book a Call", "Try Free") — every page should guide users toward conversion
4Place a clear CTA in your hero/header section so visitors see a conversion path immediately upon landing
5Add trust signals: testimonials, trust badges, guarantees, client logos, and privacy indicators to boost conversion confidence
6Add social proof: testimonials, client counts ("500+ businesses served"), case studies, or review snippets near CTAs
Hallazgos Clave
1Direct question-answer patterns found — good for Google SGE and AI citations
21 comparison/data table(s) — highly extractable by AI
36 lists provide scannable, AI-friendly content
42 ordered lists provide step-by-step structure
51 definition list(s) — excellent for AI glossary extraction
6Comprehensive content depth (1174 words) supports AI citation
78 emphasized terms suggest unique, quotable insights
82 schema blocks help AI engines understand content context
9Hreflang includes self-referencing tag
10x-default hreflang fallback present
119 data points/statistics — content has original research signals
Recomendaciones para Alcanzar 100%
1Include how-to or step-by-step instructional content for generative AI answer inclusion
2Add original data visualizations, charts, or data tables — generative engines cite pages with unique, first-party data
3Include first-hand insights using phrases like "our research found" or "based on our analysis" to demonstrate original expertise
Hallazgos Clave
1FAQPage schema markup present — eligible for rich FAQ results
2HowTo schema markup present — eligible for how-to rich results
3Question-answer heading patterns support featured snippet capture
4Speakable schema supports voice search optimization
5Breadcrumb navigation with schema aids answer context
66 lists provide scannable answers for People Also Ask
7Video content detected — supports multimedia answer results
824 concise answer-length paragraphs (10–50 words) — ideal for snippet extraction
Problemas Encontrados
1No direct answer patterns ("X is defined as...", "X refers to...")
Recomendaciones para Alcanzar 100%
1Include direct definitional statements like "X is..." or "X refers to..." — answer engines extract these as zero-click results
Hallazgos Clave
1NAP information detected: phone: 5195547504, email: [email protected]
2Phone number(s) visible: 5195547504, 6760636
3Email address found: [email protected]
4LocalBusiness schema: LocalBusiness
5Google Maps embed present — provides visual location confirmation
6Address microdata markup detected
7Geo meta tags present for location targeting
8Business hours/opening hours detected
9Service area defined in schema
Problemas Encontrados
1No review/rating schema
Recomendaciones para Alcanzar 100%
1Add AggregateRating schema to display star ratings in search results — reviews significantly impact local click-through rates
Hallazgos Clave
12 JSON-LD block(s) with types: Organization, Organization, WebSite, WebPage, ProfessionalService, LocalBusiness, FAQPage, Person, BreadcrumbList, HowTo
2Some microdata attributes detected alongside JSON-LD — common for address/local business markup in modern frameworks
3Comprehensive schema implementation
4Strong top-tier schema coverage: LocalBusiness, Organization, FAQPage, BreadcrumbList, WebSite
5Good secondary schema coverage: Person, HowTo, VideoObject
6BreadcrumbList schema → breadcrumb rich results
7FAQPage schema → expandable FAQ rich results
8Person schema strengthens E-E-A-T and Knowledge Graph
9Service schema describes your offerings
10HowTo schema → step-by-step rich results
11No schema validity issues detected
12Rich schema diversity: 9 distinct types with properties
13Entity linking via sameAs: 10 external profiles linked — strengthens Knowledge Graph
14Average schema property completeness: 95% — well-implemented
15Rich results eligible: FAQ, HowTo, Breadcrumbs, Video
16Schema nesting depth: 2 levels — rich entity relationships
17SearchAction schema present — eligible for sitelinks search box in Google
Recomendaciones para Alcanzar 100%
1When feasible, consolidate all structured data into JSON-LD format
2Add missing high-impact schemas: Article
Hallazgos Clave
1prefers-reduced-motion support detected — respects user motion preferences
2High contrast / forced-colors mode supported
3Links are visually distinguishable (underline or decoration detected)
4Relative units (rem/em/clamp) detected — supports text resizing
5Good semantic element usage (38 semantic elements)
6Focus styles detected for keyboard navigation visibility
7Page language declared — aids assistive technology
8All ARIA roles are valid
9Moderate cognitive load — acceptable for interactive modern web apps with rich UI patterns
10Focus not obscured by sticky/fixed elements (WCAG 2.4.11)
11prefers-reduced-motion detected but enforcement unclear
Problemas Encontrados
11 potential color contrast issue(s)
Recomendaciones para Alcanzar 100%
1Audit color contrast ratios — ensure at least 4.5:1 for normal text and 3:1 for large text (WCAG 1.4.3)
2Ensure prefers-reduced-motion actually disables animations (set animation: none and transition: none in the media query)
Oferta por Tiempo Limitado
Las 12 Optimizaciones — Incluidas en Tu Sitio Web Personalizado
We're currently bundling cada optimización de esta auditoría — SEO, AIO, GEO, AEO, Schema.org, accesibilidad WCAG, rendimiento, seguridad y más — directamente en nuestro servicio de Desarrollo de Aplicaciones Web Personalizadas service.
En lugar de corregir problemas después del lanzamiento, los eliminamos desde el inicio. Cada sitio web que construimos se entrega listo para producción con una puntuación de 90+ en las 12 dimensiones de auditoría.