This website audit report analyzes http://MarketingAgencyCompany.com across 12 critical dimensions with actionable recommendations.
http://MarketingAgencyCompany.com
60Needs Workout of 100
Website Audit Report
Keyword Research Tool for Marketing Agencies | Digital Marketing Co.
August 23, 2026 at 9:58 AM EDT 416ms response HTTPS Secure308 Redirect
Executive Summary
http://MarketingAgencyCompany.com scores 60/100 (D-). Strong areas include Accessibility. Priority improvements needed in SEO, Security, AI Readiness. The site has 306 words, 2 images, and 2 schema blocks. Data confidence: 90%. Sustainability score: 100/100. Focus on the top recommendations below to improve your score.
416ms
Response Time
306
Word Count
2
Images
11
Links
Website Preview
Visit SiteHTTP → HTTPS Redirect
308 Permanentredirect detected — your site correctly forces secure connections.
Loading preview…
Score History
Current scan2 scans recorded· Tap or hover a point for score & time↑ 16 pts since first scan
Score Breakdown — 12 Dimensions
Top Issues to Fix
1[SEO] Title tag is too long (68 chars — may be truncated in SERPs)
2[SEO] Canonical URL (https://keyword-research.vercel.app) does not match the page URL — search engines may ignore this page in favor of the canonical
3[SEO] Canonical URL does not match the current page URL
4[SEO] Missing OG tags: og:image
5[SEO] Missing Twitter tags: twitter:image
6[SEO] Missing favicon
7[SEO] 2 broken anchor links detected
8[SEO] 7 external links missing recommended rel attributes
9[SEO] 7 dofollow external links — slightly above optimal range
10[SEO] Missing og:locale tag — social platforms may guess language/region
Top Recommendations
1[Impact: High | Effort: Low] Shorten your title to under 60 characters to prevent truncation in search results
2[Impact: High | Effort: Low] Ensure the canonical URL matches the actual page URL, or redirect this page to the canonical URL [Impact: High | Effort: Low]
3[Impact: High | Effort: Low] Verify your canonical tag points to the correct URL to prevent duplicate content issues
4[Impact: Medium | Effort: Medium] Add missing Open Graph tags: og:image
5[Impact: Medium | Effort: Medium] Add a favicon for brand recognition in browser tabs and bookmarks
6[Impact: Medium | Effort: Medium] Fix broken anchor links — ensure all #hash targets exist on the page
7[Impact: Medium | Effort: Medium] Add rel="nofollow noopener noreferrer" to external links pointing to unaffiliated sites
8[Impact: Medium | Effort: Medium] Consider nofollowing 2–3 less authoritative outbound links to stay in the 2–5 optimal range
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] Link to an About page to establish authoritativeness and brand trust (E-E-A-T)
11[Impact: Medium | Effort: Low] Add <meta property="og:locale" content="en_US"> (or your locale) for precise language targeting in social shares
12[Impact: High | Effort: Low] Reduce keyword density from 3.9% to 0.5–2.5% — Google penalizes keyword stuffing. Use synonyms and natural language variations
Detailed Category Analysis
Key Findings
1Meta description is 146 characters — within optimal 140–160 range (2025-2026)
2Single H1 tag present: "Keyword Research Tool for Marketing Agency growth."
3Clean heading hierarchy with no skipped levels
4HTML lang attribute set to "en"
57 external links provide reference signals
6Content length of 306 words is adequate
711 total links — within recommended range
8URL length (35 chars) is within optimal range
9No redirect chain — direct URL resolution
10Good keyword alignment between title and H1
11Primary keyword "keyword research tool" found in H1 — strong on-page signal
12Primary keyword appears in first paragraph — excellent content signal
13Primary keyword not in URL — acceptable for homepage/root URLs
14Moderate E-E-A-T signals (3 indicators)
15Twitter card uses summary_large_image — maximum visual impact
16Internal link density (13.1/1k words) — above average but acceptable for navigation-heavy pages
17Low passive voice ratio (4%) — clear, active writing style
18Social share buttons detected: ShareThis
Issues Found
1Title tag is too long (68 chars — may be truncated in SERPs)
2Canonical URL (https://keyword-research.vercel.app) does not match the page URL — search engines may ignore this page in favor of the canonical
3Canonical URL does not match the current page URL
4Missing OG tags: og:image
5Missing Twitter tags: twitter:image
6Missing favicon
72 broken anchor links detected
87 external links missing recommended rel attributes
97 dofollow external links — slightly above optimal range
10Missing og:locale tag — social platforms may guess language/region
11Keyword stuffing detected: "keyword research tool" appears 4 times (3.9% density — exceeds 3%)
Recommendations to Reach 100%
1Shorten your title to under 60 characters to prevent truncation in search results
2Ensure the canonical URL matches the actual page URL, or redirect this page to the canonical URL [Impact: High | Effort: Low]
3Verify your canonical tag points to the correct URL to prevent duplicate content issues
4Add missing Open Graph tags: og:image
5Add a favicon for brand recognition in browser tabs and bookmarks
6Fix broken anchor links — ensure all #hash targets exist on the page
7Add rel="nofollow noopener noreferrer" to external links pointing to unaffiliated sites
8Consider nofollowing 2–3 less authoritative outbound links to stay in the 2–5 optimal range
9Include your primary keyword in the URL slug for improved crawlability and click-through rates
10Link to an About page to establish authoritativeness and brand trust (E-E-A-T)
11Add <meta property="og:locale" content="en_US"> (or your locale) for precise language targeting in social shares
12Reduce keyword density from 3.9% to 0.5–2.5% — Google penalizes keyword stuffing. Use synonyms and natural language variations
13OG sharing completeness at 67% — add missing tags for better social previews
14SEO (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.
15SEO: 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: 416ms
2Lean HTML document: 22KB
31 framework-managed script(s) — optimized by build pipeline
41/2 images use lazy loading
5Responsive images with srcset detected
6Most images have explicit width/height attributes (prevents layout shift)
7Preloaded resources: image, script
87 async and 0 deferred scripts
9Cache-Control header with max-age is set
10Lean CSS payload (~30KB)
11JavaScript payload (~408KB) is acceptable for framework app
12HTTP/1.1 detected — protocol upgrade managed at CDN/infrastructure level
13CDN detected: Vercel — reduces latency for global users
14Brotli compression enabled — best-in-class compression
15Estimated LCP: ~996ms — within Google's "good" threshold (<2.5s)
16Estimated CLS: 0 — within Google's "good" threshold (<0.1)
17Estimated INP: ~99ms — within Google's "good" threshold (<200ms)
Issues Found
1No WebP or AVIF image formats found
2No font-display property found
3No analytics tracking detected — flying blind on user behavior
Recommendations to Reach 100%
1Convert images to WebP or AVIF format for 30–50% file size reduction
2Add <link rel="preconnect"> for critical third-party domains to reduce DNS lookup time
3Add font-display: swap to web font declarations to show fallback text while fonts load
4Upgrade to HTTP/2 or HTTP/3 for faster parallel resource loading and header compression
5Install Google Analytics 4 (GA4) with Google Tag Manager immediately — analytics is essential for measuring SEO and marketing ROI
6Performance: no Speculation Rules API detected. Add <script type="speculationrules"> to prerender/prefetch likely next navigations for near-instant page transitions.
7Performance (LCP): no image declares fetchpriority="high". Mark the LCP hero image with fetchpriority="high" so the browser prioritizes it during initial load.
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
51 images with lazy loading benefit mobile data users
6Lightweight page (~650KB) — fast on mobile networks
Issues Found
1No theme-color meta tag
2No web app manifest found
3Missing Apple touch icon
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
5Add env(safe-area-inset-*) CSS for proper display on notched/island devices
6Add :active / touch-action CSS for tactile feedback on mobile interactions
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 308 redirect detected — properly forces secure connections
3HSTS header present — enforces HTTPS
4X-Content-Type-Options: nosniff is set
5Referrer-Policy set to: strict-origin-when-cross-origin
6Permissions-Policy header restricts browser features
7Server via CDN proxy (Vercel) — header added by infrastructure, not application
8No cookie security issues detected
9Permissions-Policy restricts 3 feature(s) — consider expanding to more features
10Rate limiting recommended for form endpoints
11No server software/technology fingerprints exposed in headers or markup
12No stack traces or sensitive error details exposed in responses
13No raw email addresses exposed in page source
14No obvious secret/API-key patterns exposed in page source
158 script resource(s) catalogued for software-composition review
16No common sensitive paths (.git, .env, server-status, …) were publicly accessible
Issues Found
1Missing Content-Security-Policy header
2Missing X-Frame-Options header
37 external links missing rel="noopener noreferrer" — security risk
4HSTS header present but missing preload directive
5No privacy policy detected
6No cookie consent banner detected
7security.txt file is missing — no standardized channel for reporting vulnerabilities
8Access-Control-Allow-Origin: * — the API is readable by any website
Recommendations to Reach 100%
1Implement a Content Security Policy to prevent XSS and injection attacks
2Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking attacks
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
6Add "preload" to your HSTS header and submit to hstspreload.org for maximum HTTPS enforcement
7Add a privacy policy link — required by GDPR, CCPA, and builds user trust
8Implement a cookie consent banner for GDPR/ePrivacy compliance
9Expand Permissions-Policy to restrict camera, microphone, geolocation, payment, usb, and autoplay
10Implement rate limiting on form endpoints to prevent brute-force attacks and spam submissions
11Add 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]
12Restrict Access-Control-Allow-Origin to an explicit allowlist of trusted origins rather than a wildcard [Impact: Medium | Effort: Low]
13A05 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.
14A06 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.
15A07 Authentication Failures: no phishing-resistant factor detected (WebAuthn/passkeys/TOTP MFA). Offer passkeys or TOTP and enforce ASVS L2 credential and session controls.
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 images have alt attributes
5All 1 forms have proper labels
6All 1 buttons have accessible labels
71 ARIA-attributed elements found
8No major HTML nesting or validity issues detected
Issues Found
1No focus styles detected
Recommendations to Reach 100%
1Add :focus-visible styles to all interactive elements for keyboard navigation visibility
2Accessibility: 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): SoftwareApplication, FAQPage
2Strong semantic markup: main, header, nav, section, article, footer
3Complete social metadata (OG + Twitter Card)
4FAQ/Q&A content patterns detected — highly valuable for AI citation
5No AI crawlers blocked via meta tags — content accessible to AI search engines
6robots.txt file found
7robots.txt references 1 sitemap(s) — aids AI crawler discoverability
8Moderate RAG-friendliness (31/100)
9Content provenance signals detected (citations with sources, attributed claims)
10Good HTML-to-text ratio (52%) — AI crawlers can extract content efficiently
Issues Found
1No breadcrumb navigation
2No sitemap reference found
3No social media links found
4No llms.txt file found — AI models cannot find structured guidance for your site
5No content freshness signals (dateModified, datePublished, <time> elements)
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
5Add links to your social media profiles to strengthen brand entity signals
6Create /llms.txt following the llms.txt standard: # Title, > description, ## Overview, ## Core Services, ## Key Pages with full URLs
7Create /llms-full.txt with comprehensive documentation (services, pricing, team, case studies) for AI models that need depth
8Add <link rel="alternate" type="text/plain" href="/llms.txt"> in your HTML <head> for AI discoverability
9Add id attributes to headings and section elements for better RAG (Retrieval Augmented Generation) chunk targeting by AI systems
10Add dateModified and datePublished meta tags and use <time datetime="..."> elements — AI models prefer fresh, timestamped content
Key Findings
11 FAQ/Q&A elements detected
2Good semantic-to-div ratio: 13 semantic elements
37 external citations — strong reference density for AI model training
4Author attribution present but missing expertise signals
5Good form usability score: 85/100
6Trust signals present: Trust Badges, HTTPS Security
7Clear value proposition detected in heading elements
Issues Found
1Content may be too thin for AI optimization (306 words)
2Weak entity markup — few terms emphasized
3Weak E-E-A-T schema signals
4No clear call-to-action elements detected
5No CTA above the fold
6No social proof elements
Recommendations to Reach 100%
1Expand content to 1000+ words with comprehensive topic coverage for better AI model training value
2Expand FAQ section with more questions to increase AI training coverage
3Use <strong>, <em>, and <mark> to highlight key entities, concepts, and brand terms for AI comprehension
4Add structured content (lists, comparison tables) that AI models can easily extract and reference
5Add Person, Article, and Review schemas to demonstrate expertise, experience, authoritativeness, and trustworthiness
6Add Speakable schema markup to help voice assistants identify the most important content
7Include specific statistics, percentages, and data points that AI models can extract and cite in responses
8Include expert quotes in <blockquote> elements to boost E-E-A-T and citation potential
9Add author bio, credentials, and links to establish expertise signals for AI E-E-A-T evaluation
10Add prominent CTAs with action-oriented text ("Get Started", "Book a Call", "Try Free") — every page should guide users toward conversion
11Place a clear CTA in your hero/header section so visitors see a conversion path immediately upon landing
12Add social proof: testimonials, client counts ("500+ businesses served"), case studies, or review snippets near CTAs
13AIO: 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
22 schema blocks help AI engines understand content context
Issues Found
1No data tables for AI comparison extraction
2Few or no lists
3Content too thin for AI citation value
4No 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
2Use numbered and bulleted lists for step-by-step content — generative engines prefer structured, scannable formats
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
5Generative engines cite pages with substantial, authoritative content — aim for 1000+ words with unique insights
6Include unique statistics, expert quotes, and original insights that generative AI would want to cite
7Add bidirectional hreflang tags with x-default to help AI engines serve the correct language variant
8Include first-hand insights using phrases like "our research found" or "based on our analysis" to demonstrate original expertise
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
1FAQPage schema markup present — eligible for rich FAQ results
2Question-answer heading patterns support featured snippet capture
39 concise answer-length paragraphs (10–50 words) — ideal for snippet extraction
Issues Found
1No Speakable schema for voice search
2No breadcrumb navigation
3No direct answer patterns ("X is defined as...", "X refers to...")
Recommendations to Reach 100%
1Consider adding how-to content with HowTo schema for step-by-step rich results
2Add Speakable schema to mark sections suitable for text-to-speech by voice assistants
3Add breadcrumb navigation with BreadcrumbList schema for better content hierarchy signals
4Add more bullet/numbered lists — search engines frequently pull list content into People Also Ask results
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.
Issues Found
1No Name/Address/Phone (NAP) information detected
2No phone number detected on the page
3No LocalBusiness structured data
4No Google Maps embed
5No address microdata
6No geo meta tags
7No review/rating schema
Recommendations to Reach 100%
1Display your business name, address, and phone number prominently — NAP consistency is a top local ranking factor
2Add a clickable phone number (tel: link) for mobile users and local SEO signals
3Consider displaying a business email for direct contact signals
4Add LocalBusiness (or specific subtype like ProfessionalService) JSON-LD schema with name, address, phone, hours, and geo coordinates
5Add an embedded Google Map to your contact or about page for local search signals
6Add PostalAddress schema or itemprop="address" microdata to your address elements
7Add geo.region, geo.placename, and geo.position meta tags for geographic targeting
8Add AggregateRating schema to display star ratings in search results — reviews significantly impact local click-through rates
Key Findings
12 JSON-LD block(s) with types: SoftwareApplication, FAQPage
2All structured data uses JSON-LD format — Google's recommended format
3Moderate schema coverage
4Some top-tier schemas: FAQPage
5FAQPage schema → expandable FAQ rich results
6Average schema property completeness: 90% — well-implemented
7Rich results potential: FAQ
8Additional rich result types: SoftwareApplication
Issues Found
1FAQPage has very few properties (1)
2FAQPage missing common identifiers (name/headline/url)
3No sameAs properties in schema — missing entity disambiguation
Recommendations to Reach 100%
1Add more top-tier schema types — consider: LocalBusiness, Organization, Product
2Consider adding secondary schema types: Person, HowTo, Service, Event for richer search features
3Add missing high-impact schemas: Organization, WebSite, Person
4Add BreadcrumbList schema — enables breadcrumb rich results in Google
5Consider adding HowTo schema for instructional content
6Add more properties to schema types — aim for at least 5 meaningful properties per type
7Add sameAs links to Organization/Person schema pointing to Wikipedia, Wikidata, social profiles
8Add SearchAction schema to your WebSite type to enable the sitelinks search box in Google results
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.
10Schema.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
3Relative units (rem/em/clamp) detected — supports text resizing
4Good semantic element usage (13 semantic elements)
5Page language declared — aids assistive technology
6All ARIA roles are valid
7Focus not obscured by sticky/fixed elements (WCAG 2.4.11)
8Accessible authentication detected (autocomplete, no CAPTCHA barriers) — WCAG 3.3.8
9prefers-reduced-motion detected but enforcement unclear
Issues Found
1Links may not be distinguishable from surrounding text
2No error suggestion mechanisms detected in forms
3No focus styles detected
4No form error identification detected
Recommendations to Reach 100%
1Ensure links have visible underlines or other non-color visual indicators (WCAG 1.4.1)
2Add aria-invalid, aria-errormessage, and visible error messages for form validation (WCAG 3.3.3)
3Add :focus-visible CSS styles to all interactive elements (WCAG 2.4.7)
4Add aria-invalid, aria-errormessage, and inline error messages to form fields (WCAG 3.3.1/3.3.3)
5Add aria-live regions (role="status" or role="alert") for form feedback, notifications, and dynamic content updates (WCAG 4.1.3)
6Ensure prefers-reduced-motion actually disables animations (set animation: none and transition: none in the media query)
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.