This website audit report analyzes http://State.gov across 12 critical dimensions with actionable recommendations.
http://State.gov
54Needs Workout of 100
Website Audit Report
U.S. Department of State – Home
September 7, 2026 · 13:46 (America/New_York) 563ms response HTTPS Secure301 Redirect
Executive Summary
http://State.gov scores 54/100 (F). Strong areas include WCAG. Priority improvements needed in SEO, Performance, Security. The site has 1440 words, 20 images, and 0 schema blocks. Data confidence: 90%. Sustainability score: 90/100. Focus on the top recommendations below to improve your score.
563ms
Response Time
1,440
Word Count
20
Images
389
Links
Website Preview
Visit SiteHTTP → HTTPS Redirect
301 Permanentredirect detected — your site correctly forces secure connections.
Loading preview…
Score Breakdown — 12 Dimensions
Top Issues to Fix
1[SEO] Title tag is short (31 chars)
2[SEO] Meta description is short (89 chars)
3[SEO] Missing Twitter tags: twitter:title, twitter:description
4[SEO] Excessive links on page (389) — search engines may devalue link equity
5[SEO] 42 external links missing rel="nofollow noopener noreferrer" — potential link equity leakage
6[SEO] Title and description are identical to Open Graph tags — missed optimization opportunity
7[SEO] Title and H1 share no keywords — misaligned topic signals
8[SEO] High dofollow external link count (42) — excessive link equity leakage
9[SEO] Primary keyword "department state" not found in H1
10[SEO] Primary keyword missing from first paragraph
Top Recommendations
1[Impact: High | Effort: Low] Expand your title to 50–60 characters — Google now favors this range for optimal SERP display (2025-2026)
2[Impact: High | Effort: Low] Expand your meta description to 140–160 characters for better SERP visibility
3[Impact: Medium | Effort: Medium] Reduce total links to under 200 per page. Use pagination, nofollow on low-value links, and consolidate navigation
4[Impact: Medium | Effort: Medium] Add rel="nofollow noopener noreferrer" and target="_blank" to all external links to prevent equity leakage and improve security
5[Impact: High | Effort: Low] Customize og:title and og:description separately from page title/meta description for better social sharing CTR
6[Impact: High | Effort: Low] Align your title tag and H1 heading around the same primary keyword for clearer topical relevance
7[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
8[Impact: High | Effort: Low] Include your primary keyword in the H1 heading for strongest on-page SEO signal
9[Impact: High | Effort: Low] Include your primary keyword naturally in the first paragraph to establish topical relevance early
10[Impact: High | Effort: Low] Include your primary keyword in the URL slug for improved crawlability and click-through rates
11[Impact: Medium | Effort: Medium] Convert your OG image to WebP format for faster social media loading (1200×630px recommended)
12[Impact: Medium | Effort: Low] Add <meta property="article:published_time"> for content freshness signals in social shares
Detailed Category Analysis
Key Findings
1Single H1 tag present: "Secretary Rubio's Remarks at the Trump Administration’s Foun…"
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)
5HTML lang attribute set to "en"
6Favicon present
7345 internal links help establish site architecture
844 external links provide reference signals
9Content length of 1440 words is adequate
10URL length (22 chars) is within optimal range
11No redirect chain — direct URL resolution
12Healthy internal link ratio: 89% of links are internal
13Good anchor text diversity: 98% unique anchor texts
14Primary keyword not in URL — acceptable for homepage/root URLs
15Moderate E-E-A-T signals (4 indicators)
16og:locale set to "en_US"
17OG image dimensions ≥1200×630px — optimal for all platforms
18article:modified_time present — update recency signal
19Twitter card uses summary_large_image — maximum visual impact
20Table of Contents detected — improves dwell time and jump-link navigation
21Strong entity salience: Secretary Rubio, State Deputy Secretary, Instagram Instagram (score: 56)
22Social share buttons detected: ShareThis
23OG sharing completeness: 100% — all tags present for optimal social previews
Issues Found
1Title tag is short (31 chars)
2Meta description is short (89 chars)
3Missing Twitter tags: twitter:title, twitter:description
4Excessive links on page (389) — search engines may devalue link equity
542 external links missing rel="nofollow noopener noreferrer" — potential link equity leakage
6Title and description are identical to Open Graph tags — missed optimization opportunity
7Title and H1 share no keywords — misaligned topic signals
8High dofollow external link count (42) — excessive link equity leakage
9Primary keyword "department state" not found in H1
10Primary keyword missing from first paragraph
11Very high internal link density (239.6/1k words) — may appear spammy
12Primary keyword "department state" not found in body content
13Moderate passive voice (26%)
Recommendations to Reach 100%
1Expand your title to 50–60 characters — Google now favors this range for optimal SERP display (2025-2026)
2Expand your meta description to 140–160 characters for better SERP visibility
3Reduce total links to under 200 per page. Use pagination, nofollow on low-value links, and consolidate navigation
4Add rel="nofollow noopener noreferrer" and target="_blank" to all external links to prevent equity leakage and improve security
5Customize og:title and og:description separately from page title/meta description for better social sharing CTR
6Align your title tag and H1 heading around the same primary keyword for clearer topical relevance
7Reduce dofollow external links to 2–5 per page. Add rel="nofollow" to low-value or affiliate links to preserve PageRank
8Include your primary keyword in the H1 heading for strongest on-page SEO signal
9Include your primary keyword naturally in the first paragraph to establish topical relevance early
10Include your primary keyword in the URL slug for improved crawlability and click-through rates
11Convert your OG image to WebP format for faster social media loading (1200×630px recommended)
12Add <meta property="article:published_time"> for content freshness signals in social shares
13Reduce internal link density — excessive linking dilutes individual link value
14Include your primary keyword naturally throughout the content body — aim for 0.5–2.5% density
15Reduce passive voice to under 15% for clearer, more engaging content that AI and readers prefer
16Add TL;DR summaries or definition-style opening paragraphs ("X is...") for zero-click/featured snippet capture
17SEO (E-E-A-T): no author linkage or sameAs identity markup detected. Add a verifiable author byline with rel="author" and sameAs links to strengthen Experience/Expertise signals.
18SEO: no IndexNow signal detected. Adopt the IndexNow protocol (Bing/Yandex/Seznam) to push instant crawl notifications when content changes.
Key Findings
1Acceptable response time: 563ms
2HTML size is 244KB — acceptable
313/20 images use lazy loading
4Responsive images with srcset detected
5Most images have explicit width/height attributes (prevents layout shift)
6Preloaded resources: font, font, image, image, image
70 async and 1 deferred scripts
8Cache-Control header with max-age is set
9CDN detected: CloudFront — reduces latency for global users
10Gzip compression enabled
111 third-party script(s) — manageable count
125 resource hints (preconnect/prefetch/preload) optimize loading
132 font(s) preloaded for faster text rendering
14Estimated LCP: ~2463ms — within Google's "good" threshold (<2.5s)
15Estimated INP: ~174ms — within Google's "good" threshold (<200ms)
16Variable fonts detected — reduces total font file downloads
Issues Found
111 render-blocking scripts slow down initial paint
2No WebP or AVIF image formats found
3No font-display property found
420 inline <style> blocks
519 inline scripts
6Moderate CSS payload (~211KB)
7Moderate JavaScript payload (~619KB)
8389 links increase DOM size and parsing time
9HTTP/1.1 detected — no multiplexing
105 render-blocking CSS files — delays first paint
11Moderate estimated CLS: 0.19 — above 0.1 "good" threshold
12Basic analytics only — missing event tracking or tag management
Recommendations to Reach 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
3Convert images to WebP or AVIF format for 30–50% file size reduction
4Add <link rel="preconnect"> for critical third-party domains to reduce DNS lookup time
5Add font-display: swap to web font declarations to show fallback text while fonts load
6Extract inline styles into external CSS files for better caching and maintainability
7Move inline scripts to external files with defer attributes
8Consider purging unused CSS and using critical CSS extraction to reduce render-blocking stylesheets
9Optimize JavaScript delivery with code splitting, deferred loading, and removing duplicate modules
10Reduce links per page to improve DOM parsing performance and reduce memory usage
11Upgrade to HTTP/2 or HTTP/3 for faster parallel resource loading and header compression
12Reduce render-blocking CSS by inlining critical CSS, using media queries on non-critical stylesheets, and loading non-critical CSS asynchronously
13Reduce CLS: set image dimensions, preload web fonts, reserve space for ads and dynamic content
14Upgrade analytics: add Google Tag Manager for flexible tag deployment and configure custom events (form submissions, CTA clicks, scroll depth)
15Performance: ES modules are used without modulepreload. Add <link rel="modulepreload"> for critical modules to remove waterfall latency on module graphs.
Key Findings
1Viewport meta tag present: width=device-width, initial-scale=1
2HTML5 doctype declared
3Character encoding declared
4Apple touch icons present
5Responsive images via srcset serve appropriate sizes per device
613 images with lazy loading benefit mobile data users
7Touch feedback CSS detected (active states or touch-action)
83 internationalization signals detected (hreflang, lang, dir, locale meta)
Issues Found
1No theme-color meta tag
2No web app manifest found
3Popup/modal/interstitial detected — Google penalizes intrusive interstitials on mobile
4Only 3 manifest icon size(s) — recommend at least 4 (192, 384, 512, maskable)
Recommendations to Reach 100%
1Add <meta name="theme-color"> for browser chrome styling on mobile
2Create a manifest.json for PWA capabilities and add-to-homescreen support
3Consider implementing a service worker for offline support and faster repeat visits
4Remove or minimize intrusive interstitials on mobile — Google's Page Experience update penalizes full-screen popups that block content
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
7Mobile/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.
8Mobile/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
7HSTS with preload and adequate max-age — eligible for browser preload list
8No cookie security issues detected
9Privacy policy link detected
10Cookie consent mechanism detected
11jQuery 3.7.1 — current version
12Rate limiting recommended for form endpoints
13No stack traces or sensitive error details exposed in responses
14No raw email addresses exposed in page source
15No obvious secret/API-key patterns exposed in page source
16Client-side library inventory (SBOM): jQuery 3.7.1, WordPress
1712 script resource(s) catalogued for software-composition review
18No common sensitive paths (.git, .env, server-status, …) were publicly accessible
Issues Found
1Missing Referrer-Policy header
2Missing Permissions-Policy header
3Server header exposes technology: Apache
442 external links missing rel="noopener noreferrer" — security risk
5No Subresource Integrity (SRI) on external scripts
6Weak CSP implementation (strictness score: 30/100)
7CSP contains 3 unsafe-inline directive(s) — weakens XSS protection
8Server-side software version disclosed: WordPress 7.0.4 — enables version-based vulnerability (CVE) lookups
9Additional technology fingerprints exposed: Server: Apache; Generator meta tag: WordPress 7.0.4
10security.txt file is missing — no standardized channel for reporting vulnerabilities
Recommendations to Reach 100%
1Add Referrer-Policy: strict-origin-when-cross-origin to control referrer leakage
2Add Permissions-Policy to restrict access to camera, microphone, geolocation, etc.
3Add Cross-Origin-Opener-Policy: same-origin-allow-popups
4Add Cross-Origin-Resource-Policy: cross-origin
5Remove or obfuscate the Server header to avoid exposing your technology stack
6Add rel="noopener noreferrer" to all external links with target="_blank" to prevent tabnabbing attacks
7Add integrity attributes to external scripts/stylesheets to prevent supply-chain attacks
8Significantly strengthen CSP: eliminate unsafe-inline and unsafe-eval, use nonce-based policies, define explicit source lists per directive (OWASP Level 3)
9Replace unsafe-inline with nonce-based CSP or hash-based allowlisting for inline scripts/styles
10Implement rate limiting on form endpoints to prevent brute-force attacks and spam submissions
11Suppress version numbers in the Server / X-Powered-By headers and generator meta tag, and keep the framework patched to its latest release to close known CVEs [Impact: High | Effort: Low]
12Add 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]
13A03 Software Supply Chain: only 0% of 12 cross-origin scripts use Subresource Integrity. Pin every third-party script with integrity+crossorigin and adopt SLSA provenance / a published SBOM for build integrity.
14A05 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.
15A08 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.
16A09 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: en
2Skip navigation link present
3All key landmarks present (main, nav, footer)
4All 2 forms have proper labels
5All 57 buttons have accessible labels
6Rich ARIA implementation: 316 elements with ARIA attributes
7Focus styles detected for keyboard navigation
8Language-specific content sections marked with lang attribute (WCAG 3.1.2)
Issues Found
12 of 20 images (10%) missing alt text
21 iframe(s) missing title
34 minor HTML validity issue(s)
48 button(s) with no accessible label
Recommendations to Reach 100%
1Add descriptive alt text to all images — use empty alt="" only for decorative images
2Add descriptive title attributes to all iframes
3Review and fix HTML structure issues for better accessibility and cross-browser compatibility
4Add text content, aria-label, or title to all buttons — icon-only buttons need aria-label (WCAG 4.1.2)
Key Findings
1Strong semantic markup: header, nav, section, main, article, figure, aside, footer
2Complete social metadata (OG + Twitter Card)
3FAQ/Q&A content patterns detected — highly valuable for AI citation
49 strong entity mentions (bold/emphasized text)
5Social presence signals: facebook, twitter, instagram, youtube
617 call-to-action elements detected
7No AI crawlers blocked via meta tags — content accessible to AI search engines
8robots.txt file found
9robots.txt references 1 sitemap(s) — aids AI crawler discoverability
10High RAG-friendliness (100/100): 0 headings with IDs, 27 section anchors
11Content provenance signals detected (citations with sources, attributed claims)
12Content freshness signals present (dateModified/datePublished/time elements)
13Good HTML-to-text ratio (39%) — AI crawlers can extract content efficiently
Issues Found
1No structured data (Schema.org) found
2No breadcrumb navigation
3No sitemap reference found
4No llms.txt file found — AI models cannot find structured guidance for your site
Recommendations to Reach 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
5Create /llms.txt following the llms.txt standard: # Title, > description, ## Overview, ## Core Services, ## Key Pages with full URLs
6Create /llms-full.txt with comprehensive documentation (services, pricing, team, case studies) for AI models that need depth
7Add <link rel="alternate" type="text/plain" href="/llms.txt"> in your HTML <head> for AI discoverability
Key Findings
1Moderate content depth (1440 words)
21 FAQ/Q&A elements detected
39 emphasized entities
4Good semantic-to-div ratio: 37 semantic elements
5Structured content: 25 lists, 0 tables — easily parsed by AI
635 external citations — strong reference density for AI model training
7Strong CRO: 3 clear call-to-action elements detected
8Above-the-fold CTA detected — captures immediate visitor attention
9Good form usability score: 90/100
10Trust signals present: HTTPS Security, Privacy Policy
11Clear value proposition detected in heading elements
Issues Found
1Weak E-E-A-T schema signals
2Paragraphs are too long for optimal AI consumption
3No author or expertise signals
4No social proof elements
Recommendations to Reach 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 social proof: testimonials, client counts ("500+ businesses served"), case studies, or review snippets near CTAs
9AIO: no schema "name" property to anchor your primary entity. Declare a consistent Organization/Person/Product name in JSON-LD matching your title and H1.
Key Findings
1Direct question-answer patterns found — good for Google SGE and AI citations
225 lists provide scannable, AI-friendly content
3Comprehensive content depth (1440 words) supports AI citation
49 emphasized terms suggest unique, quotable insights
523 original data elements (charts, figures, data tables)
6Content is fresh (updated within 30 days) — strong recency signal
Issues Found
1No data tables for AI comparison extraction
2Insufficient structured data for generative engine context
3paragraphs may be too long for featured snippets
4No hreflang tags — generative engines cannot determine language/region targeting
5No statistics or data points in substantial content
Recommendations to Reach 100%
1Add comparison tables with structured data — generative AI engines frequently cite tabular content
2Include how-to or step-by-step instructional content for generative AI answer inclusion
3Consider using <dl>/<dt>/<dd> definition lists for key terms and concepts
4Add multiple schema types (Article, FAQ, HowTo) to help generative engines contextualize your content
5Add bidirectional hreflang tags with x-default to help AI engines serve the correct language variant
6Include specific statistics, percentages, and numerical data — generative engines prefer content with verifiable data points
7Include first-hand insights using phrases like "our research found" or "based on our analysis" to demonstrate original expertise
8GEO: only 1/23 sub-headings are question-phrased. Convert key sections into natural-language questions so generative engines can extract and cite direct answers.
9GEO: no comparison tables or step-by-step structured blocks found. Add comparison tables and ordered how-to steps — formats generative engines favor for structured, citable answers.
Key Findings
1Question-answer heading patterns support featured snippet capture
225 lists provide scannable answers for People Also Ask
311 concise answer-length paragraphs (10–50 words) — ideal for snippet extraction
Issues Found
1FAQ content exists but lacks FAQPage schema
2No Speakable schema for voice search
3Paragraphs too long for answer engine extraction
4No breadcrumb navigation
5No direct answer patterns ("X is defined as...", "X refers to...")
6Paragraphs too long for voice assistant extraction
Recommendations to Reach 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
3Add Speakable schema to mark sections suitable for text-to-speech by voice assistants
4Keep answer paragraphs under 30 words — voice assistants and answer engines prefer concise, direct responses
5Add breadcrumb navigation with BreadcrumbList schema for better content hierarchy signals
6Consider adding video content with VideoObject schema for multimedia search results
7Include direct definitional statements like "X is..." or "X refers to..." — answer engines extract these as zero-click results
8Keep paragraphs under 30 words for voice search — voice assistants read concise, conversational content
9AEO: 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: 768.0602
2Phone number(s) visible: 768.0602, 911.5634
Issues Found
1No LocalBusiness structured data
2No Google Maps embed
3No address microdata
4No geo meta tags
5No review/rating schema
Recommendations to Reach 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
7Local 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.
8Local SEO (NAP): a phone number is shown but not declared in structured data. Add telephone (and address) to LocalBusiness schema so NAP is machine-verifiable.
Issues Found
1No Schema.org structured data found
2Missing high-impact schema types: Organization, WebSite, FAQPage
Recommendations to Reach 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
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.
Key Findings
1prefers-reduced-motion support detected — respects user motion preferences
2Links are visually distinguishable (underline or decoration detected)
3Form error/validation feedback detected
4Relative units (rem/em/clamp) detected — supports text resizing
5Good semantic element usage (37 semantic elements)
6Focus styles detected for keyboard navigation visibility
7Page language declared — aids assistive technology
8Form error identification mechanisms present (WCAG 3.3.1)
9Focus not obscured by sticky/fixed elements (WCAG 2.4.11)
10Accessible authentication detected (autocomplete, no CAPTCHA barriers) — WCAG 3.3.8
112 ARIA live regions for dynamic content announcements
12Reduced motion enforced: animations disabled when prefers-reduced-motion is set
Issues Found
1No high contrast mode support
210 elements with tabindex="-1" — may hide content from keyboard users
3Invalid ARIA roles: social media links
Recommendations to Reach 100%
1Add @media (prefers-contrast: high) or (forced-colors: active) styles for users with low vision
2Review elements with tabindex="-1" — ensure important interactive elements remain keyboard-accessible
3Use only valid WAI-ARIA roles — invalid roles are ignored by assistive technology and may confuse screen readers (WCAG 4.1.2)
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.