This website audit report analyzes https://moz.com across 12 critical dimensions with actionable recommendations.
https://moz.com
60Needs Workout of 100
Website Audit Report
Moz - SEO Software for Smarter Marketing
August 18, 2026 at 7:31 AM EDT 137ms response HTTPS Secure
Executive Summary
https://moz.com scores 60/100 (D-). Priority improvements needed in SEO, Security, GEO. The site has 2620 words, 49 images, and 1 schema blocks. Data confidence: 95%. Sustainability score: 75/100. Focus on the top recommendations below to improve your score.
137ms
Response Time
2,620
Word Count
49
Images
190
Links
Website Preview
Visit SiteLoading preview…
Score Breakdown — 12 Dimensions
Top Issues to Fix
1[SEO] Title tag is short (40 chars)
2[SEO] Meta description may be truncated (187 chars)
3[SEO] Heading hierarchy gaps: h1 → h4 (skips h2), h3 → h5 (skips h4), h2 → h5 (skips h3), h2 → h5 (skips h3), h2 → h5 (skips h3), h3 → h5 (skips h4)
4[SEO] Missing favicon
5[SEO] 8 empty/unlabeled links found
6[SEO] Title and H1 share no keywords — misaligned topic signals
7[SEO] 10 dofollow external links — slightly above optimal range
8[SEO] Primary keyword "moz" not found in H1
9[SEO] Primary keyword missing from first paragraph
10[SEO] Low readability score (34 Flesch) — content is hard to read
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] Trim your meta description to under 160 characters to prevent truncation
3[Impact: High | Effort: Low] Fix heading hierarchy to use sequential levels (H1 → H2 → H3) without skipping
4[Impact: Medium | Effort: Medium] Add a favicon for brand recognition in browser tabs and bookmarks
5[Impact: Medium | Effort: Medium] Add descriptive anchor text to all links for better SEO and accessibility
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: Medium] Consider nofollowing 2–3 less authoritative outbound links to stay in the 2–5 optimal range
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: Medium | Effort: Medium] Significantly simplify your content — aim for 60+ Flesch Reading Ease with shorter sentences and simpler vocabulary
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: "Show up in search. Show up in AI. Own the results."
2Canonical URL is set and matches the page URL
3Complete Open Graph tags (title, description, image, url, type)
4Complete Twitter Card tags present
5HTML lang attribute set to "en-US"
6179 internal links help establish site architecture
710 external links provide reference signals
8Content length of 2620 words is adequate
9190 total links — within recommended range
10URL length (16 chars) is within optimal range
11No redirect chain — direct URL resolution
12Healthy internal link ratio: 94% of links are internal
13Primary keyword present in URL — good URL optimization
14Strong E-E-A-T signals detected (8 indicators)
15og:locale set to "en_US"
16OG image dimensions ≥1200×630px — optimal for all platforms
17Twitter card uses summary_large_image — maximum visual impact
18Low passive voice ratio (4%) — clear, active writing style
19Table of Contents detected — improves dwell time and jump-link navigation
20Strong entity salience: Moz Pro, Moz Local, Moz Data (score: 54)
21Strong dwell/engagement signals: 3 indicators (ToC, related content, internal links)
22Social share buttons detected: ShareThis
23OG sharing completeness: 100% — all tags present for optimal social previews
Issues Found
1Title tag is short (40 chars)
2Meta description may be truncated (187 chars)
3Heading hierarchy gaps: h1 → h4 (skips h2), h3 → h5 (skips h4), h2 → h5 (skips h3), h2 → h5 (skips h3), h2 → h5 (skips h3), h3 → h5 (skips h4)
4Missing favicon
58 empty/unlabeled links found
6Title and H1 share no keywords — misaligned topic signals
710 dofollow external links — slightly above optimal range
8Primary keyword "moz" not found in H1
9Primary keyword missing from first paragraph
10Low readability score (34 Flesch) — content is hard to read
11Very high internal link density (68.3/1k words) — may appear spammy
12Keyword stuffing detected: "moz" appears 99 times (3.8% density — exceeds 3%)
Recommendations to Reach 100%
1Expand your title to 50–60 characters — Google now favors this range for optimal SERP display (2025-2026)
2Trim your meta description to under 160 characters to prevent truncation
3Fix heading hierarchy to use sequential levels (H1 → H2 → H3) without skipping
4Add a favicon for brand recognition in browser tabs and bookmarks
5Add descriptive anchor text to all links for better SEO and accessibility
6Align your title tag and H1 heading around the same primary keyword for clearer topical relevance
7Consider nofollowing 2–3 less authoritative outbound links to stay in the 2–5 optimal range
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
10Significantly simplify your content — aim for 60+ Flesch Reading Ease with shorter sentences and simpler vocabulary
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
13Add <meta property="article:modified_time"> to signal content freshness
14Reduce internal link density — excessive linking dilutes individual link value
15Reduce keyword density from 3.8% to 0.5–2.5% — Google penalizes keyword stuffing. Use synonyms and natural language variations
16Add TL;DR summaries or definition-style opening paragraphs ("X is...") for zero-click/featured snippet capture
17SEO: 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: 137ms
2HTML size is 164KB — acceptable
336/49 images use lazy loading
4Modern image formats (WebP/AVIF) detected
5Responsive images with srcset detected
6Preconnect hints for: https://moz.com/mozbootstrap/fonts
7Preloaded resources: font, font, font, script
82 async and 1 deferred scripts
9Cache-Control header with max-age is set
10Lean CSS payload (~150KB)
11JavaScript payload (~404KB) is acceptable
12HTTP/3 (QUIC) detected — fastest connection protocol
13CDN detected: Cloudflare — reduces latency for global users
14Brotli compression enabled — best-in-class compression
153 third-party script(s) — manageable count
166 resource hints (preconnect/prefetch/preload) optimize loading
173 font(s) preloaded for faster text rendering
18Estimated LCP: ~1437ms — within Google's "good" threshold (<2.5s)
19Estimated INP: ~108ms — within Google's "good" threshold (<200ms)
20Alternative analytics platform detected (Plausible/Umami/Matomo)
Issues Found
15 render-blocking scripts slow down initial paint
2No font-display property found
35 font files loaded — excessive font weight
45 render-blocking CSS files — delays first paint
5Moderate estimated CLS: 0.15 — above 0.1 "good" threshold
Recommendations to Reach 100%
1Convert all non-critical scripts to async/defer to eliminate render-blocking resources
2Add font-display: swap to web font declarations to show fallback text while fonts load
3Limit web fonts to 2–3 families with subset character ranges to reduce font loading impact
4Reduce render-blocking CSS by inlining critical CSS, using media queries on non-critical stylesheets, and loading non-critical CSS asynchronously
5Reduce CLS: set image dimensions, preload web fonts, reserve space for ads and dynamic content
6Consider adding Google Search Console integration alongside your analytics for SEO-specific insights
7Performance: no Speculation Rules API detected. Add <script type="speculationrules"> to prerender/prefetch likely next navigations for near-instant page transitions.
8Performance (LCP): no image declares fetchpriority="high". Mark the LCP hero image with fetchpriority="high" so the browser prioritizes it during initial load.
9Performance: only 0/49 images set decoding="async". Add decoding="async" to non-critical images to keep image decode off the main thread.
Key Findings
1Viewport meta tag present: width=device-width, initial-scale=1
2HTML5 doctype declared
3Character encoding declared
4Responsive images via srcset serve appropriate sizes per device
536 images with lazy loading benefit mobile data users
6Mobile-responsive hamburger menu detected
Issues Found
1No theme-color meta tag
2No web app manifest found
3Missing Apple touch icon
4Popup/modal/interstitial detected — Google penalizes intrusive interstitials on mobile
5Estimated page weight ~3298KB — heavy for mobile data plans
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
3Add <link rel="apple-touch-icon"> for iOS homescreen icons
4Consider implementing a service worker for offline support and faster repeat visits
5Remove or minimize intrusive interstitials on mobile — Google's Page Experience update penalizes full-screen popups that block content
6Add env(safe-area-inset-*) CSS for proper display on notched/island devices
7Add :active / touch-action CSS for tactile feedback on mobile interactions
8Reduce page weight below 2MB: optimize images (WebP/AVIF), defer non-critical JS, remove unused CSS
9Mobile/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.
10Mobile/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
2HSTS header present — enforces HTTPS
3X-Content-Type-Options: nosniff is set
4X-Frame-Options header prevents clickjacking
5Referrer-Policy set to: no-referrer-when-downgrade
6Server via CDN proxy (cloudflare) — header added by infrastructure, not application
7No cookie security issues detected
8Privacy policy link detected
9Rate limiting recommended for form endpoints
10No server software/technology fingerprints exposed in headers or markup
11No stack traces or sensitive error details exposed in responses
12No raw email addresses exposed in page source
13No obvious secret/API-key patterns exposed in page source
148 script resource(s) catalogued for software-composition review
15No common sensitive paths (.git, .env, server-status, …) were publicly accessible
Issues Found
1Missing Content-Security-Policy header
2Missing Permissions-Policy header
31 external link(s) without noopener/noreferrer
4HSTS header present but missing preload directive
5HSTS max-age is only 30 days — should be at least 1 year
6No cookie consent banner detected
7No Subresource Integrity (SRI) on external scripts
8security.txt found but has issues: Missing recommended "Expires:" field
9Legacy X-XSS-Protection header present — deprecated and can introduce vulnerabilities in older browsers
10Dangerous client-side sink(s) detected in inline scripts: innerHTML assignment — potential DOM-based XSS vectors
11robots.txt discloses sensitive-looking path(s): /blog/, /admin-preview/* — Disallow entries can act as a map for attackers
Recommendations to Reach 100%
1Implement a Content Security Policy to prevent XSS and injection attacks
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
5Add rel="noopener noreferrer" to external links for security
6Add "preload" to your HSTS header and submit to hstspreload.org for maximum HTTPS enforcement
7Set HSTS max-age to at least 31536000 (1 year) for proper security enforcement
8Implement a cookie consent banner for GDPR/ePrivacy compliance
9Add integrity attributes to external scripts/stylesheets to prevent supply-chain attacks
10Implement rate limiting on form endpoints to prevent brute-force attacks and spam submissions
11Fix your security.txt so it is RFC 9116-compliant: serve it from /.well-known/security.txt with valid Contact and future-dated Expires fields
12Remove the deprecated X-XSS-Protection header and rely on a strong Content-Security-Policy instead [Impact: Low | Effort: Low]
13Avoid eval, document.write, innerHTML and Function() with untrusted input; prefer textContent, DOM APIs and a trusted-types policy [Impact: Medium | Effort: Medium]
14Avoid listing admin/private paths in robots.txt; protect them with authentication instead of relying on obscurity [Impact: Low | Effort: Low]
15A01 Broken Access Control: 3 links expose sequential/direct object identifiers (IDOR surface). Use unguessable references (UUID/ULID) and verify object-level ownership on every request (ASVS 4.2).
16A03 Software Supply Chain: only 0% of 7 cross-origin scripts use Subresource Integrity. Pin every third-party script with integrity+crossorigin and adopt SLSA provenance / a published SBOM for build integrity.
17A06 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.
18A07 Authentication Failures: no phishing-resistant factor detected (WebAuthn/passkeys/TOTP MFA). Offer passkeys or TOTP and enforce ASVS L2 credential and session controls.
19A07 Authentication Failures: cookies do not use the __Host-/__Secure- prefix. Prefix session cookies with __Host- (with Secure, Path=/, no Domain) and add the Partitioned (CHIPS) attribute for cross-site isolation.
20A08 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.
21A09 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-US
2Skip navigation link present
3All key landmarks present (main, nav, footer)
4All 49 images have alt attributes
5All 18 buttons have accessible labels
6Rich ARIA implementation: 51 elements with ARIA attributes
7Focus styles detected for keyboard navigation
Issues Found
11 form(s) missing proper labels
2Heading hierarchy has gaps — confusing for screen readers
34 minor HTML validity issue(s)
Recommendations to Reach 100%
1Add <label> elements associated with every form input via for/id attributes
2Review and fix HTML structure issues for better accessibility and cross-browser compatibility
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
11 schema block(s): WebPage, Organization, Organization, BreadcrumbList
2Strong semantic markup: nav, section, main, article, footer, address, time
3Complete social metadata (OG + Twitter Card)
4FAQ/Q&A content patterns detected — highly valuable for AI citation
57 strong entity mentions (bold/emphasized text)
6Social presence signals: twitter, facebook, instagram, linkedin, youtube
723 call-to-action elements detected
8No AI crawlers blocked via meta tags — content accessible to AI search engines
9robots.txt file found
10robots.txt references 2 sitemap(s) — aids AI crawler discoverability
11High RAG-friendliness (100/100): 0 headings with IDs, 44 section anchors
12Content provenance signals detected (citations with sources, attributed claims)
13Content freshness signals present (dateModified/datePublished/time elements)
Issues Found
1No breadcrumb navigation
2No sitemap reference found
3No llms.txt file found — AI models cannot find structured guidance for your site
Recommendations to Reach 100%
1Add more structured data types (FAQ, HowTo, Breadcrumb) to improve AI comprehension
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
8AI Readiness (multimodal): only 31% of images have descriptive alt text (≥15 chars). Rich, standalone alt text lets multimodal models understand and cite your imagery.
Key Findings
1Comprehensive content (2620 words) — strong for AI model training
2Rich Q&A content (28 FAQ/accordion elements)
37 emphasized entities
4Structured content: 32 lists, 0 tables — easily parsed by AI
5Good paragraph length for readability and AI parsing
65 external citations — strong reference density for AI model training
76 statistics/data points — excellent for AI knowledge extraction
8Author expertise signals detected (bio, credentials, Person schema)
9Strong CRO: 9 clear call-to-action elements detected
10Above-the-fold CTA detected — captures immediate visitor attention
11Trust signals present: Reviews/Testimonials, Trust Badges, HTTPS Security
12Social proof elements detected — builds credibility and conversion confidence
13Clear value proposition detected in heading elements
Issues Found
1Low semantic markup ratio — 467 divs vs 17 semantic elements
2Weak E-E-A-T schema signals
Recommendations to Reach 100%
1Replace generic <div> wrappers with semantic elements (article, section, aside, figure) for AI clarity
2Add Person, Article, and Review schemas to demonstrate expertise, experience, authoritativeness, and trustworthiness
3Add Speakable schema markup to help voice assistants identify the most important content
4Include expert quotes in <blockquote> elements to boost E-E-A-T and citation potential
5AIO: 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
232 lists provide scannable, AI-friendly content
3How-to instructional patterns detected — valued by AI answer engines
4Comprehensive content depth (2620 words) supports AI citation
56 data points/statistics — content has original research signals
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
3No hreflang tags — generative engines cannot determine language/region targeting
Recommendations to Reach 100%
1Add comparison tables with structured data — generative AI engines frequently cite tabular content
2Consider using <dl>/<dt>/<dd> definition lists for key terms and concepts
3Include unique statistics, expert quotes, and original insights that generative AI would want to cite
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
6Add original data visualizations, charts, or data tables — generative engines cite pages with unique, first-party data
7Include first-hand insights using phrases like "our research found" or "based on our analysis" to demonstrate original expertise
8GEO: only 3/29 sub-headings are question-phrased. Convert key sections into natural-language questions so generative engines can extract and cite direct answers.
Key Findings
1Question-answer heading patterns support featured snippet capture
2Short paragraphs are well-suited for answer extraction
332 lists provide scannable answers for People Also Ask
475 concise answer-length paragraphs (10–50 words) — ideal for snippet extraction
5Content length and paragraph structure are voice-search optimized
Issues Found
1FAQ content exists but lacks FAQPage schema
2How-to content exists but lacks HowTo schema
3No Speakable schema for voice search
4No breadcrumb navigation
5No direct answer patterns ("X is defined as...", "X refers to...")
Recommendations to Reach 100%
1Add FAQPage schema markup to your FAQ section for rich snippet eligibility in search results
2Add HowTo schema to your instructional content for rich result eligibility
3Add Speakable schema to mark sections suitable for text-to-speech by voice assistants
4Add breadcrumb navigation with BreadcrumbList schema for better content hierarchy signals
5Consider adding video content with VideoObject schema for multimedia search results
6Include direct definitional statements like "X is..." or "X refers to..." — answer engines extract these as zero-click results
7AEO: 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: 1025208
2Phone number(s) visible: 1025208, 1025211
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.
Key Findings
11 JSON-LD block(s) with types: WebPage, Organization, Organization, BreadcrumbList
2All structured data uses JSON-LD format — Google's recommended format
3Moderate schema coverage
4Some top-tier schemas: Organization, BreadcrumbList
5BreadcrumbList schema → breadcrumb rich results
6No schema validity issues detected
7Entity linking via sameAs: 5 external profiles linked — strengthens Knowledge Graph
8Rich results potential: Breadcrumbs
9Schema.org: a connected @graph with 4 entity types is present — strong structured-data maturity.
Issues Found
16 high-impact schema types missing
2Schema property completeness averaging 72%
Recommendations to Reach 100%
1Add more top-tier schema types — consider: LocalBusiness, Product, Article
2Consider adding secondary schema types: Person, HowTo, Service, Event for richer search features
3Priority schemas to add: WebSite, FAQPage, Article, HowTo, Person
4Add FAQPage schema to FAQ content — enables expandable rich results
5Consider adding HowTo schema for instructional content
6Fill in missing recommended properties for each schema type
7Add SearchAction schema to your WebSite type to enable the sitelinks search box in Google results
8Schema.org (maximize): 3 question/answer blocks detected but no FAQPage schema. Add FAQPage with Question/acceptedAnswer for each pair to unlock FAQ rich results and AI citations.
9Schema.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
1Relative units (rem/em/clamp) detected — supports text resizing
2Focus styles detected for keyboard navigation visibility
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
Issues Found
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
5Low semantic-to-div ratio — 467 divs vs 17 semantic elements
682 elements with tabindex="-1" — may hide content from keyboard users
76 heading level skip(s) — confuses screen reader navigation
8No form error identification detected
Recommendations to Reach 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)
5Replace more generic <div> elements with semantic HTML5 tags for better screen reader navigation
6Review elements with tabindex="-1" — ensure important interactive elements remain keyboard-accessible
7Use sequential heading levels (H1→H2→H3) without skipping — screen reader users navigate by heading hierarchy (WCAG 1.3.1)
8Add aria-invalid, aria-errormessage, and inline error messages to form fields (WCAG 3.3.1/3.3.3)
9Add aria-live regions (role="status" or role="alert") for form feedback, notifications, and dynamic content updates (WCAG 4.1.3)
10WCAG 2.2 (1.4.13 Content on Hover/Focus): 123 interactive elements rely on native title tooltips, which are not dismissable, hoverable or persistent. Replace with accessible tooltip components.
Limited-Time Offer
All 12 Optimizations — Bundled Into 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.
Instead of fixing issues after launch, we eliminate them from the start. Every website we build ships production-ready with a 90+ score across all 12 audit dimensions.