Este informe de auditoría web analiza http://maryland.gov en 12 dimensiones críticas con recomendaciones accionables.
http://maryland.gov
58Necesita Mejorasde 100
Informe de Auditoría Web
Maryland.gov
1 de junio de 2026 583ms respuesta HTTPS Seguro301 Redirección
Resumen Ejecutivo
http://maryland.gov scores 58/100 (F). Strong areas include Accessibility. Priority improvements needed in SEO, Performance, AI Readiness. The site has 657 words, 15 images, and 0 schema blocks. Data confidence: 85%. Sustainability score: 100/100. Focus on the top recommendations below to improve your score.
583ms
Tiempo de Respuesta
657
Conteo de Palabras
15
Imágenes
113
Enlaces
Vista Previa del Sitio
Visitar SitioRedirección HTTP → HTTPS
301 Permanenteredirección detectada — su sitio fuerza correctamente conexiones seguras.
Cargando vista previa…
Historial de Puntuación
Escaneo actual2 escaneos registrados↑ 5 pts desde el primer escaneo
Desglose de Puntuación — 12 Dimensiones
Problemas Principales a Solucionar
1[SEO] Title tag is very short (12 chars)
2[SEO] Meta description is slightly short (133 chars)
3[SEO] 41 external links missing rel="nofollow noopener noreferrer" — potential link equity leakage
4[SEO] Title and description are identical to Open Graph tags — missed optimization opportunity
5[SEO] Title and H1 share no keywords — misaligned topic signals
6[SEO] High dofollow external link count (41) — excessive link equity leakage
7[SEO] Primary keyword "marylandgov" not found in H1
8[SEO] Primary keyword missing from first paragraph
9[SEO] Weak E-E-A-T signals (2 indicators)
10[SEO] Low readability score (15 Flesch) — content is hard to read
Recomendaciones Principales
1[Impact: High | Effort: Low] Expand your title to 50–60 characters for better click-through rates and SERP visibility
2[Impact: High | Effort: Low] Expand your meta description to 140–160 characters — this range maximizes SERP visibility in 2025-2026
3[Impact: Medium | Effort: Medium] Add rel="nofollow noopener noreferrer" and target="_blank" to all external links to prevent equity leakage and improve security
4[Impact: High | Effort: Low] Customize og:title and og:description separately from page title/meta description for better social sharing CTR
5[Impact: High | Effort: Low] Align your title tag and H1 heading around the same primary keyword for clearer topical relevance
6[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
7[Impact: High | Effort: Low] Include your primary keyword in the H1 heading for strongest on-page SEO signal
8[Impact: High | Effort: Low] Include your primary keyword naturally in the first paragraph to establish topical relevance early
9[Impact: High | Effort: Low] Include your primary keyword in the URL slug for improved crawlability and click-through rates
10[Impact: High | Effort: Medium] Strengthen E-E-A-T: add author bios, about page link, testimonials, trust badges, and credentials to demonstrate expertise and trustworthiness
11[Impact: High | Effort: Medium] Link to an About page to establish authoritativeness and brand trust (E-E-A-T)
12[Impact: High | Effort: Medium] Link to a Contact page — essential trust signal for E-E-A-T and local SEO
Análisis Detallado por Categoría
Hallazgos Clave
1Single H1 tag present: "Welcome to
Maryland"
2Clean heading hierarchy with no skipped levels
3Canonical URL is set and matches the page URL
4Complete Open Graph tags (title, description, image, url, type)
5Complete Twitter Card tags present
6HTML lang attribute set to "en"
7Favicon present
872 internal links help establish site architecture
940 external links provide reference signals
10Content length of 657 words is adequate
11113 total links — within recommended range
12URL length (25 chars) is within optimal range
13No redirect chain — direct URL resolution
14Healthy internal link ratio: 64% of links are internal
15Good anchor text diversity: 78% unique anchor texts
16Primary keyword not in URL — acceptable for homepage/root URLs
17Low passive voice ratio (7%) — clear, active writing style
18Moderate entity presence: Translate Official, United States, Lock Locked
Problemas Encontrados
1Title tag is very short (12 chars)
2Meta description is slightly short (133 chars)
341 external links missing rel="nofollow noopener noreferrer" — potential link equity leakage
4Title and description are identical to Open Graph tags — missed optimization opportunity
5Title and H1 share no keywords — misaligned topic signals
6High dofollow external link count (41) — excessive link equity leakage
7Primary keyword "marylandgov" not found in H1
8Primary keyword missing from first paragraph
9Weak E-E-A-T signals (2 indicators)
10Low readability score (15 Flesch) — content is hard to read
11Missing og:locale tag — social platforms may guess language/region
12Very high internal link density (109.6/1k words) — may appear spammy
13Primary keyword "marylandgov" not found in body content
14No social sharing buttons/widgets detected
Recomendaciones para Alcanzar 100%
1Expand your title to 50–60 characters for better click-through rates and SERP visibility
2Expand your meta description to 140–160 characters — this range maximizes SERP visibility in 2025-2026
3Add rel="nofollow noopener noreferrer" and target="_blank" to all external links to prevent equity leakage and improve security
4Customize og:title and og:description separately from page title/meta description for better social sharing CTR
5Align your title tag and H1 heading around the same primary keyword for clearer topical relevance
6Reduce dofollow external links to 2–5 per page. Add rel="nofollow" to low-value or affiliate links to preserve PageRank
7Include your primary keyword in the H1 heading for strongest on-page SEO signal
8Include your primary keyword naturally in the first paragraph to establish topical relevance early
9Include your primary keyword in the URL slug for improved crawlability and click-through rates
10Strengthen E-E-A-T: add author bios, about page link, testimonials, trust badges, and credentials to demonstrate expertise and trustworthiness
11Link to an About page to establish authoritativeness and brand trust (E-E-A-T)
12Link to a Contact page — essential trust signal for E-E-A-T and local SEO
13Significantly simplify your content — aim for 60+ Flesch Reading Ease with shorter sentences and simpler vocabulary
14Add <meta property="og:locale" content="en_US"> (or your locale) for precise language targeting in social shares
15Convert your OG image to WebP format for faster social media loading (1200×630px recommended)
16Add <meta property="article:published_time"> for content freshness signals in social shares
17Add <meta property="article:modified_time"> to signal content freshness
18Upgrade Twitter card to "summary_large_image" for larger, more engaging previews
19Reduce internal link density — excessive linking dilutes individual link value
20Include your primary keyword naturally throughout the content body — aim for 0.5–2.5% density
21Add TL;DR summaries or definition-style opening paragraphs ("X is...") for zero-click/featured snippet capture
22Add social share buttons (Facebook, Twitter/X, LinkedIn, WhatsApp) to encourage content distribution and earn social signals
23OG sharing completeness at 83% — add missing tags for better social previews
Hallazgos Clave
1Acceptable response time: 583ms
2HTML size is 109KB — acceptable
310/15 images use lazy loading
4Modern image formats (WebP/AVIF) detected
5Responsive images with srcset detected
60 async and 2 deferred scripts
7Cache-Control header with max-age is set
8Lean CSS payload (~90KB)
9JavaScript payload (~253KB) is acceptable
10CDN detected: Cloudflare — reduces latency for global users
11Gzip compression enabled
122 third-party script(s) — manageable count
13Estimated LCP: ~1523ms — within Google's "good" threshold (<2.5s)
14Estimated INP: ~90ms — within Google's "good" threshold (<200ms)
15Server-Timing header present — enables performance debugging
Problemas Encontrados
13 render-blocking scripts slow down initial paint
2No font-display property found
3HTTP/1.1 detected — no multiplexing
4No resource hints found
53 render-blocking CSS file(s)
6Moderate estimated CLS: 0.22 — above 0.1 "good" threshold
7Basic analytics only — missing event tracking or tag management
Recomendaciones para Alcanzar 100%
1Optimize server response time to under 500ms with caching or a CDN
2Convert all non-critical scripts to async/defer to eliminate render-blocking resources
3Add <link rel="preconnect"> for critical third-party domains to reduce DNS lookup time
4Preload critical resources (fonts, hero images) with <link rel="preload">
5Add font-display: swap to web font declarations to show fallback text while fonts load
6Upgrade to HTTP/2 or HTTP/3 for faster parallel resource loading and header compression
7Add preconnect, prefetch, and preload hints for critical third-party resources and fonts
8Consider inlining critical CSS and deferring non-essential stylesheets
9Reduce CLS: set image dimensions, preload web fonts, reserve space for ads and dynamic content
10Upgrade analytics: add Google Tag Manager for flexible tag deployment and configure custom events (form submissions, CTA clicks, scroll depth)
Hallazgos Clave
1Viewport meta tag present: width=device-width, initial-scale=1.0
2HTML5 doctype declared
3Character encoding declared
4Responsive images via srcset serve appropriate sizes per device
510 images with lazy loading benefit mobile data users
Problemas Encontrados
1No theme-color meta tag
2No web app manifest found
3Missing Apple touch icon
4Only 1 manifest icon size(s) — recommend at least 4 (192, 384, 512, maskable)
Recomendaciones para Alcanzar 100%
1Add <meta name="theme-color"> for browser chrome styling on mobile
2Create a manifest.json for PWA capabilities and add-to-homescreen support
3Add <link rel="apple-touch-icon"> for iOS homescreen icons
4Consider implementing a service worker for offline support and faster repeat visits
5Add multiple icon sizes (192x192, 384x384, 512x512, plus maskable) to your manifest for cross-device support
6Add env(safe-area-inset-*) CSS for proper display on notched/island devices
7Add :active / touch-action CSS for tactile feedback on mobile interactions
Hallazgos Clave
1HTTPS enabled — encrypted connection
2HTTP → HTTPS 301 redirect detected — properly forces secure connections
3HSTS header present — enforces HTTPS
4X-Content-Type-Options: nosniff is set
5X-Frame-Options header prevents clickjacking
6Permissions-Policy header restricts browser features
7Server via CDN proxy (cloudflare) — header added by infrastructure, not application
8HSTS with preload and adequate max-age — eligible for browser preload list
9No cookie security issues detected
10Privacy policy link detected
11Subresource Integrity (SRI) on 1 resource(s) — prevents CDN tampering
12Permissions-Policy restricts 21 browser features (accelerometer, autoplay, camera, cross-origin-isolated)
13Rate limiting recommended for form endpoints
Problemas Encontrados
1Missing Content-Security-Policy header
2Missing Referrer-Policy header
341 external links missing rel="noopener noreferrer" — security risk
4No cookie consent banner detected
Recomendaciones para Alcanzar 100%
1Implement a Content Security Policy to prevent XSS and injection attacks
2Add Referrer-Policy: strict-origin-when-cross-origin to control referrer leakage
3Add Cross-Origin-Opener-Policy: same-origin-allow-popups
4Add Cross-Origin-Resource-Policy: cross-origin
5Add rel="noopener noreferrer" to all external links with target="_blank" to prevent tabnabbing attacks
6Implement a cookie consent banner for GDPR/ePrivacy compliance
7Implement rate limiting on form endpoints to prevent brute-force attacks and spam submissions
Hallazgos Clave
1Language declared: en
2Skip navigation link present
3All key landmarks present (main, nav, footer)
4All 15 images have alt attributes
5All 2 forms have proper labels
6All 9 buttons have accessible labels
7Rich ARIA implementation: 32 elements with ARIA attributes
Problemas Encontrados
1No focus styles detected
24 minor HTML validity issue(s)
Recomendaciones para Alcanzar 100%
1Add :focus-visible styles to all interactive elements for keyboard navigation visibility
2Review and fix HTML structure issues for better accessibility and cross-browser compatibility
Hallazgos Clave
1Strong semantic markup: header, section, nav, main, article, figure, footer
2Complete social metadata (OG + Twitter Card)
3FAQ/Q&A content patterns detected — highly valuable for AI citation
4Social presence signals: instagram, youtube, facebook, twitter
51 call-to-action elements detected
6No AI crawlers blocked via meta tags — content accessible to AI search engines
7robots.txt file found
8llms.txt detected (score: 68/100, quality: detailed)
9llms.txt has 11 well-organized sections
10llms.txt references 6 URLs for AI navigation
11llms.txt includes service/product catalog
12llms.txt uses proper Markdown formatting for machine readability
13llms.txt uses canonical domain in URLs
14llms.txt provides content usage guidelines for AI
15llms.txt includes version/date for freshness tracking
16High RAG-friendliness (100/100): 13 headings with IDs, 10 section anchors
17Content provenance signals detected (citations with sources, attributed claims)
18Content freshness signals present (dateModified/datePublished/time elements)
Problemas Encontrados
1No structured data (Schema.org) found
2No breadcrumb navigation
3No sitemap reference found
4robots.txt has no Sitemap directive
5llms.txt missing blockquote description
6No llms-full.txt companion file found
7llms.txt is not referenced in HTML
8Very low HTML-to-text ratio (7%) — mostly markup, little visible content
Recomendaciones para Alcanzar 100%
1Implement JSON-LD structured data — start with Organization, BreadcrumbList, and page-specific types
2Add hreflang tags if your site serves multiple languages or regions
3Add breadcrumb navigation with BreadcrumbList schema for better site hierarchy signals
4Create and reference an XML sitemap for AI crawler discoverability
5Add a Sitemap: directive to your robots.txt pointing to your XML sitemap for AI and search crawler discoverability
6Enhance llms.txt: add citation guidelines, version date, content usage policy, and expand URL list to cover all major pages
7Add a > blockquote summary on line 2-3 describing your business in 1-2 sentences
8Create /llms-full.txt with detailed documentation — services, pricing, case studies, technical specs — for AI models that want depth
9Add <link rel="alternate" type="text/plain" href="/llms.txt"> in your <head> for discoverability
10Increase text-to-HTML ratio by adding more substantive content and reducing excessive markup/scripts
Hallazgos Clave
1Moderate content depth (657 words)
21 FAQ/Q&A elements detected
35 emphasized entities
4Good semantic-to-div ratio: 22 semantic elements
5Structured content: 16 lists, 0 tables — easily parsed by AI
637 external citations — strong reference density for AI model training
7Good form usability score: 90/100
8Trust signals present: HTTPS Security, Privacy Policy
9Clear value proposition detected in heading elements
Problemas Encontrados
1Weak E-E-A-T schema signals
2Paragraphs are too long for optimal AI consumption
3No author or expertise signals
4No clear call-to-action elements detected
5No CTA above the fold
6No social proof elements
Recomendaciones para Alcanzar 100%
1Expand FAQ section with more questions to increase AI training coverage
2Add Person, Article, and Review schemas to demonstrate expertise, experience, authoritativeness, and trustworthiness
3Break long paragraphs into shorter ones (under 30 words) for better AI comprehension and snippet extraction
4Add Speakable schema markup to help voice assistants identify the most important content
5Include specific statistics, percentages, and data points that AI models can extract and cite in responses
6Include expert quotes in <blockquote> elements to boost E-E-A-T and citation potential
7Add visible author bylines with bios and link to author pages — AI models evaluate content credibility through authorship signals
8Add prominent CTAs with action-oriented text ("Get Started", "Book a Call", "Try Free") — every page should guide users toward conversion
9Place a clear CTA in your hero/header section so visitors see a conversion path immediately upon landing
10Add social proof: testimonials, client counts ("500+ businesses served"), case studies, or review snippets near CTAs
Hallazgos Clave
116 lists provide scannable, AI-friendly content
23 original data elements (charts, figures, data tables)
3Content is fresh (updated within 30 days) — strong recency signal
445 unique insight patterns detected (original research/analysis signals)
Problemas Encontrados
1No direct Q&A patterns for generative AI extraction
2No data tables for AI comparison extraction
3Insufficient structured data for generative engine context
4paragraphs may be too long for featured snippets
5No hreflang tags — generative engines cannot determine language/region targeting
6No statistics or data points in substantial content
Recomendaciones para Alcanzar 100%
1Structure content with clear questions as headings (H2/H3) followed by concise, definitive answers in the first paragraph
2Add comparison tables with structured data — generative AI engines frequently cite tabular content
3Include how-to or step-by-step instructional content for generative AI answer inclusion
4Consider using <dl>/<dt>/<dd> definition lists for key terms and concepts
5Include unique statistics, expert quotes, and original insights that generative AI would want to cite
6Add multiple schema types (Article, FAQ, HowTo) to help generative engines contextualize your content
7Add bidirectional hreflang tags with x-default to help AI engines serve the correct language variant
8Include specific statistics, percentages, and numerical data — generative engines prefer content with verifiable data points
Hallazgos Clave
116 lists provide scannable answers for People Also Ask
211 concise answer-length paragraphs (10–50 words) — ideal for snippet extraction
Problemas Encontrados
1FAQ content exists but lacks FAQPage schema
2Content not optimized for featured snippets
3No Speakable schema for voice search
4Paragraphs too long for answer engine extraction
5No breadcrumb navigation
6No direct answer patterns ("X is defined as...", "X refers to...")
7Paragraphs too long for voice assistant extraction
Recomendaciones para Alcanzar 100%
1Add FAQPage schema markup to your FAQ section for rich snippet eligibility in search results
2Consider adding how-to content with HowTo schema for step-by-step rich results
3Use question-based H2/H3 headings followed by a direct 40–60 word answer paragraph for featured snippet targeting
4Add Speakable schema to mark sections suitable for text-to-speech by voice assistants
5Keep answer paragraphs under 30 words — voice assistants and answer engines prefer concise, direct responses
6Add breadcrumb navigation with BreadcrumbList schema for better content hierarchy signals
7Consider adding video content with VideoObject schema for multimedia search results
8Include direct definitional statements like "X is..." or "X refers to..." — answer engines extract these as zero-click results
9Keep paragraphs under 30 words for voice search — voice assistants read concise, conversational content
Hallazgos Clave
1NAP information detected: phone: 2026052
2Phone number(s) visible: 2026052, 8876482
Problemas Encontrados
1No LocalBusiness structured data
2No Google Maps embed
3No address microdata
4No geo meta tags
5No review/rating schema
Recomendaciones para Alcanzar 100%
1Consider displaying a business email for direct contact signals
2Add LocalBusiness (or specific subtype like ProfessionalService) JSON-LD schema with name, address, phone, hours, and geo coordinates
3Add an embedded Google Map to your contact or about page for local search signals
4Add PostalAddress schema or itemprop="address" microdata to your address elements
5Add geo.region, geo.placename, and geo.position meta tags for geographic targeting
6Add AggregateRating schema to display star ratings in search results — reviews significantly impact local click-through rates
Problemas Encontrados
1No Schema.org structured data found
2Missing high-impact schema types: Organization, WebSite, FAQPage
Recomendaciones para Alcanzar 100%
1Implement JSON-LD structured data immediately — start with Organization, WebSite, and BreadcrumbList
2Priority schema types to add: Organization, WebSite, FAQPage — these have the highest SEO impact for your page type
Hallazgos Clave
1Relative units (rem/em/clamp) detected — supports text resizing
2Good semantic element usage (22 semantic elements)
3Page language declared — aids assistive technology
4All ARIA roles are valid
5Focus not obscured by sticky/fixed elements (WCAG 2.4.11)
6Accessible authentication detected (autocomplete, no CAPTCHA barriers) — WCAG 3.3.8
Problemas Encontrados
1No prefers-reduced-motion support
2No high contrast mode support
3Links may not be distinguishable from surrounding text
4No error suggestion mechanisms detected in forms
5No focus styles detected
6No form error identification detected
Recomendaciones para Alcanzar 100%
1Add @media (prefers-reduced-motion: reduce) to disable animations for users who are sensitive to motion
2Add @media (prefers-contrast: high) or (forced-colors: active) styles for users with low vision
3Ensure links have visible underlines or other non-color visual indicators (WCAG 1.4.1)
4Add aria-invalid, aria-errormessage, and visible error messages for form validation (WCAG 3.3.3)
5Add :focus-visible CSS styles to all interactive elements (WCAG 2.4.7)
6Add aria-invalid, aria-errormessage, and inline error messages to form fields (WCAG 3.3.1/3.3.3)
7Add aria-live regions (role="status" or role="alert") for form feedback, notifications, and dynamic content updates (WCAG 4.1.3)
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.