This website audit report analyzes http://AgenciaDeMarketing.org across 12 critical dimensions with actionable recommendations.
http://AgenciaDeMarketing.org
87Goodout of 100
Website Audit Report
Agencia de Marketing Digital | SEO, AIO, GEO, AEO y PPC en LatAm
August 1, 2026 · 23:54 (America/New_York) 102ms response HTTPS Secure301 Redirect
Executive Summary
http://AgenciaDeMarketing.org scores 87/100 (B+). Strong areas include Performance, AI Readiness, Accessibility. The site has 1194 words, 2 images, and 2 schema blocks. Data confidence: 100%. Sustainability score: 90/100. Focus on the top recommendations below to improve your score.
102ms
Response Time
1,194
Word Count
2
Images
72
Links
Website Preview
Visit SiteHTTP → HTTPS Redirect
301 Permanentredirect detected — your site correctly forces secure connections.
Loading preview…
Score History
Current scan20 scans recorded· Tap or hover a point for score & time↑ 18 pts since first scan
Score Breakdown — 12 Dimensions
Top Issues to Fix
1[SEO] Title tag is too long (64 chars — may be truncated in SERPs)
2[SEO] 6 dofollow external links — slightly above optimal range
3[SEO] Primary keyword "agencia marketing digital" not found in H1
4[SEO] Primary keyword missing from first paragraph
5[SEO] Primary keyword "agencia marketing digital" not found in body content
6[Security] No cookie consent banner detected
7[Security] No Subresource Integrity (SRI) on external scripts
8[Security] 1 email address(es) exposed in page source (e.g. [email protected]) — can be harvested for spam/phishing
9[Security] A private/internal IP address (RFC 1918) is disclosed in the page source — reveals internal network topology
10[AIO] No clear call-to-action elements detected
Top Recommendations
1[Impact: High | Effort: Low] Shorten your title to under 60 characters to prevent truncation in search results
2[Impact: Medium | Effort: Medium] Consider nofollowing 2–3 less authoritative outbound links to stay in the 2–5 optimal range
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: High | Effort: Low] Include your primary keyword naturally throughout the content body — aim for 0.5–2.5% density
9[Impact: Medium | Effort: Medium] Add TL;DR summaries or definition-style opening paragraphs ("X is...") for zero-click/featured snippet capture
10[Impact: Medium | Effort: Low] Add engagement signals: related posts section, "Read next" links, and table of contents to increase dwell time
11[Impact: Medium | Effort: Medium] SEO: no IndexNow signal detected. Adopt the IndexNow protocol (Bing/Yandex/Seznam) to push instant crawl notifications when content changes.
12[Impact: High | Effort: Medium] Upgrade to HTTP/2 or HTTP/3 for faster parallel resource loading and header compression
Detailed Category Analysis
Key Findings
1Meta description is 144 characters — within optimal 140–160 range (2025-2026)
2Single H1 tag present: "Agencia de Marketing Digital"
3Clean heading hierarchy with no skipped levels
4Canonical URL is set and matches the page URL
5Complete Open Graph tags (title, description, image, url, type)
6Complete Twitter Card tags present
7HTML lang attribute set to "es"
8Favicon present
959 internal links help establish site architecture
1011 external links provide reference signals
11Content length of 1194 words is adequate
1272 total links — within recommended range
13URL length (31 chars) is within optimal range
14All external links have proper rel attributes (nofollow/noopener)
15No redirect chain — direct URL resolution
16Healthy internal link ratio: 82% of links are internal
17Good anchor text diversity: 88% unique anchor texts
18Good keyword alignment between title and H1
19Primary keyword not in URL — acceptable for homepage/root URLs
20Strong E-E-A-T signals detected (6 indicators)
21og:locale set to "es_419"
22OG image dimensions ≥1200×630px — optimal for all platforms
23article:published_time present — content freshness signal for social platforms
24article:modified_time present — update recency signal
25Twitter card uses summary_large_image — maximum visual impact
26Internal link density (49.4/1k words) — above average but acceptable for navigation-heavy pages
27Moderate entity presence: Video Publicitario, Marketing Digital, Jeremy Valdivia
28Social share buttons detected: ShareThis
29OG sharing completeness: 100% — all tags present for optimal social previews
Issues Found
1Title tag is too long (64 chars — may be truncated in SERPs)
26 dofollow external links — slightly above optimal range
3Primary keyword "agencia marketing digital" not found in H1
4Primary keyword missing from first paragraph
5Primary keyword "agencia marketing digital" not found in body content
Recommendations to Reach 100%
1Shorten your title to under 60 characters to prevent truncation in search results
2Consider nofollowing 2–3 less authoritative outbound links to stay in the 2–5 optimal range
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)
8Include your primary keyword naturally throughout the content body — aim for 0.5–2.5% density
9Add TL;DR summaries or definition-style opening paragraphs ("X is...") for zero-click/featured snippet capture
10Add engagement signals: related posts section, "Read next" links, and table of contents to increase dwell time
11SEO: no IndexNow signal detected. Adopt the IndexNow protocol (Bing/Yandex/Seznam) to push instant crawl notifications when content changes.
Key Findings
1Excellent server response time: 102ms
2HTML size is 198KB — acceptable
31 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
1016 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 (~967KB) 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: ~762ms — within Google's "good" threshold (<2.5s)
22Estimated CLS: 0.1 — within Google's "good" threshold (<0.1)
23Estimated INP: ~174ms — 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
Recommendations to Reach 100%
1Upgrade to HTTP/2 or HTTP/3 for faster parallel resource loading and header compression
2Performance: no Speculation Rules API detected. Add <script type="speculationrules"> to prerender/prefetch likely next navigations for near-instant page transitions.
Key Findings
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
Recommendations to Reach 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
3Mobile/PWA: incomplete Apple web-app meta tags (missing capable, status-bar-style, title). Add apple-mobile-web-app-capable, -status-bar-style and -title for a polished iOS home-screen install.
4Mobile/PWA: viewport meta lacks viewport-fit=cover. Add it (with safe-area-inset padding) so content renders edge-to-edge on notched/dynamic-island devices.
Key Findings
1HTTPS enabled — encrypted connection
2HTTP → HTTPS 301 redirect detected — properly forces secure connections
3HSTS header present — enforces HTTPS
4Content Security Policy header present
5X-Content-Type-Options: nosniff is set
6X-Frame-Options header prevents clickjacking
7Referrer-Policy set to: strict-origin-when-cross-origin
8Permissions-Policy header restricts browser features
9Cross-Origin-Opener-Policy set
10Cross-Origin-Resource-Policy set
11Cross-Origin-Embedder-Policy set
12Server via CDN proxy (cloudflare) — header added by infrastructure, not application
13All external links have security-safe rel attributes
14HSTS with preload and adequate max-age — eligible for browser preload list
15No cookie security issues detected
16Privacy policy link detected
17CSP strictness score 40/100 — adequate for modern framework apps that require inline styles/scripts
18CSP uses 2 unsafe-inline directive(s) — standard requirement for modern SSR frameworks
19Permissions-Policy restricts 10 browser features (camera, microphone, geolocation, payment)
20No server software/technology fingerprints exposed in headers or markup
21security.txt present and valid (/.well-known/security.txt) — provides a channel for vulnerability disclosure
22No stack traces or sensitive error details exposed in responses
23No obvious secret/API-key patterns exposed in page source
2417 script resource(s) catalogued for software-composition review
25No common sensitive paths (.git, .env, server-status, …) were publicly accessible
26Cross-origin isolation enabled (COOP + COEP) — hardened against Spectre-style side-channel and cross-origin leaks
Issues Found
1No cookie consent banner detected
2No Subresource Integrity (SRI) on external scripts
31 email address(es) exposed in page source (e.g. [email protected]) — can be harvested for spam/phishing
4A private/internal IP address (RFC 1918) is disclosed in the page source — reveals internal network topology
Recommendations to Reach 100%
1Implement a cookie consent banner for GDPR/ePrivacy compliance
2Add integrity attributes to external scripts/stylesheets to prevent supply-chain attacks
3Strengthen CSP: consider nonce-based policies when feasible
4When feasible, migrate to nonce-based CSP for inline scripts/styles
5If 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]
6Remove references to internal hostnames/IP addresses from public responses [Impact: Medium | Effort: Low]
7A05 Injection: 1 raw-HTML binding sink(s) detected (dangerouslySetInnerHTML / v-html / [innerHTML]). Sanitize with a trusted library (DOMPurify) and adopt Trusted Types to close DOM-XSS vectors.
8A06 Insecure Design: authentication/high-value form present with no visible bot/abuse challenge (CAPTCHA/Turnstile). Add anti-automation, rate limiting and account-lockout as a threat-modeled control.
9A07 Authentication Failures: no phishing-resistant factor detected (WebAuthn/passkeys/TOTP MFA). Offer passkeys or TOTP and enforce ASVS L2 credential and session controls.
10A08 Integrity Failures: dynamic remote script injection detected. Load third-party code with static tags carrying SRI, or gate it behind a strict CSP with Trusted Types to prevent tampered-update execution.
11A09 Logging & Alerting Failures: no client-side error/security monitoring detected. Add centralized logging with tamper-evident storage and real-time alerting on auth failures and anomalies.
Key Findings
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
Issues Found
1Potential contrast issues: white text on very light background detected
Recommendations to Reach 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
3Accessibility: no forced-colors / prefers-contrast media handling detected. Test and support Windows High Contrast / forced-colors mode so essential UI remains visible.
Key Findings
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, time
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
15llms.txt detected (score: 83/100, quality: comprehensive)
16llms-full.txt companion file detected (6KB)
17llms.txt has proper title and description block
18llms.txt has 5 well-organized sections
19llms.txt references 25 URLs for AI navigation
20llms.txt includes service/product catalog
21llms.txt uses proper Markdown formatting for machine readability
22llms.txt links to detailed documentation (llms-full.txt)
23llms.txt referenced in HTML for discoverability
24llms.txt uses canonical domain in URLs
25Moderate RAG-friendliness (58/100)
26Additional AI crawlers allowed: PerplexityBot, Bytespider, Amazonbot, Applebot-Extended, Cohere-ai
27Content provenance signals detected (citations with sources, attributed claims)
28Content freshness signals present (dateModified/datePublished/time elements)
29JS content ratio 59% — expected for SSR framework apps that serve pre-rendered HTML with hydration scripts
Recommendations to Reach 100%
1Add more structured data types (FAQ, HowTo, Breadcrumb) to improve AI comprehension
2Add id attributes to headings and section elements for better RAG (Retrieval Augmented Generation) chunk targeting by AI systems
Key Findings
1Moderate content depth (1194 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
910 statistics/data points — excellent for AI knowledge extraction
10Author attribution present but missing expertise signals
11Clear value proposition detected in heading elements
Issues Found
1No clear call-to-action elements detected
2No CTA above the fold
3Insufficient trust signals for conversion optimization
4No social proof elements
Recommendations to Reach 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
7AIO: primary entity name is inconsistent across title, H1 and schema "name". Align the brand/entity term across all three so AI systems resolve a single, unambiguous entity.
Key Findings
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 (1194 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
1110 data points/statistics — content has original research signals
12Content is fresh (updated within 30 days) — strong recency signal
Recommendations to Reach 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
4GEO: only 1/18 sub-headings are question-phrased. Convert key sections into natural-language questions so generative engines can extract and cite direct answers.
Key Findings
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
825 concise answer-length paragraphs (10–50 words) — ideal for snippet extraction
Issues Found
1No direct answer patterns ("X is defined as...", "X refers to...")
Recommendations to Reach 100%
1Include direct definitional statements like "X is..." or "X refers to..." — answer engines extract these as zero-click results
2AEO: no 40–60 word concise answer directly follows a question heading. Lead each question section with a self-contained ~40–60 word answer to win featured snippets and voice answers.
Key Findings
1NAP information detected: phone: 5195547504, email: [email protected]
2Phone number(s) visible: 5195547504, 0484562807
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
Issues Found
1No review/rating schema
Recommendations to Reach 100%
1Add AggregateRating schema to display star ratings in search results — reviews significantly impact local click-through rates
2Local SEO: local business signals present but no explicit city/region in the title, H1 or opening paragraph. Add "City, State" to your title/H1 and intro to reinforce local relevance.
Key Findings
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
18Schema.org: a connected @graph with 11 entity types is present — strong structured-data maturity.
Recommendations to Reach 100%
1When feasible, consolidate all structured data into JSON-LD format
2Add missing high-impact schemas: Article
3Schema.org (maximize): long-form article content detected but no Article/BlogPosting schema. Add Article with headline, author, datePublished, dateModified, image and publisher for maximal eligibility.
4Schema.org (maximize): commerce signals detected but no Product schema. Add Product with offers (price, priceCurrency, availability), aggregateRating and review for product rich results.
Key Findings
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
Issues Found
11 potential color contrast issue(s)
Recommendations to Reach 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)
3WCAG 2.2 (1.4.13 Content on Hover/Focus): 26 interactive elements rely on native title tooltips, which are not dismissable, hoverable or persistent. Replace with accessible tooltip components.
Limited-Time Offer
Audit-informed Optimizations for Your Custom Website
We're currently bundling every optimization from this audit — SEO, AIO, GEO, AEO, Schema.org, WCAG accessibility, performance, security, and more — directly into our Custom Web Application Development service.
Use the audit findings to prioritize improvements during development. Scores depend on measured conditions; rankings and fixed scores are not guaranteed.