This website audit report analyzes https://gotgeo.net/ across 12 critical dimensions with actionable recommendations.
https://gotgeo.net/
45Poorout of 100
Website Audit Report
Geothermal & HVAC Company | Total Energy Concepts | Aberdeen, Maryland
July 22, 2026 727ms response HTTPS Secure
Executive Summary
https://gotgeo.net/ scores 45/100 (F). Priority improvements needed in SEO, Performance, Security. The site has 716 words, 26 images, and 1 schema blocks. Data confidence: 90%. Sustainability score: 90/100. Focus on the top recommendations below to improve your score.
727ms
Response Time
716
Word Count
26
Images
65
Links
Website Preview
Visit SiteLoading preview…
Score History
Current scan2 scans recorded↑ 1 pts since first scan
Score Breakdown — 12 Dimensions
Top Issues to Fix
1[SEO] Title tag is too long (70 chars — may be truncated in SERPs)
2[SEO] Meta description may be truncated (349 chars)
3[SEO] Multiple H1 tags found (3)
4[SEO] Heading hierarchy gaps: h1 → h3 (skips h2)
5[SEO] Missing canonical URL
6[SEO] No Open Graph tags found
7[SEO] No Twitter Card tags found
8[SEO] 4 empty/unlabeled links found
9[SEO] Primary keyword "geothermal hvac company" not found in H1
10[SEO] Primary keyword missing from first paragraph
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] Trim your meta description to under 160 characters to prevent truncation
3[Impact: High | Effort: Low] Consolidate to a single H1 tag — use H2–H6 for subtopics
4[Impact: High | Effort: Low] Fix heading hierarchy to use sequential levels (H1 → H2 → H3) without skipping
5[Impact: High | Effort: Low] Add a <link rel="canonical"> tag pointing to the preferred version of this page
6[Impact: High | Effort: Low] Add Open Graph tags (og:title, og:description, og:image, og:url, og:type) for social sharing
7[Impact: Medium | Effort: Low] Add Twitter Card meta tags for better social media previews
8[Impact: Medium | Effort: Medium] Add descriptive anchor text to all links for better SEO and accessibility
9[Impact: High | Effort: Low] Include your primary keyword in the H1 heading for strongest on-page SEO signal
10[Impact: High | Effort: Low] Include your primary keyword naturally in the first paragraph to establish topical relevance early
11[Impact: High | Effort: Low] Include your primary keyword in the URL slug for improved crawlability and click-through rates
12[Impact: Medium | Effort: Medium] Simplify sentence structure and use shorter words to improve readability to 60+ Flesch Reading Ease
Detailed Category Analysis
Key Findings
1HTML lang attribute set to "en"
2Favicon present
360 internal links help establish site architecture
43 external links provide reference signals
5Content length of 716 words is adequate
665 total links — within recommended range
7URL length (19 chars) is within optimal range
8No redirect chain — direct URL resolution
9Healthy internal link ratio: 92% of links are internal
10Good anchor text diversity: 75% unique anchor texts
11Optimal dofollow outbound links: 3 (ideal 2–5 per page for link authority signals)
12Primary keyword not in URL — acceptable for homepage/root URLs
13Moderate E-E-A-T signals (4 indicators)
14Low passive voice ratio (5%) — clear, active writing style
15Moderate entity presence: Total Energy Concepts, Geothermal Geothermal, Financial Case Net Zero Homes Getting Started Incentives Geothermal Products Services Geothermal Heating
16Social share buttons detected: ShareThis
Issues Found
1Title tag is too long (70 chars — may be truncated in SERPs)
2Meta description may be truncated (349 chars)
3Multiple H1 tags found (3)
4Heading hierarchy gaps: h1 → h3 (skips h2)
5Missing canonical URL
6No Open Graph tags found
7No Twitter Card tags found
84 empty/unlabeled links found
9Primary keyword "geothermal hvac company" not found in H1
10Primary keyword missing from first paragraph
11Moderate readability (48 Flesch) — content may be difficult for some readers
12Very high internal link density (83.8/1k words) — may appear spammy
13Primary keyword "geothermal hvac company" not found in body content
14Low OG sharing completeness (0%) — social previews will be poor
Recommendations to Reach 100%
1Shorten your title to under 60 characters to prevent truncation in search results
2Trim your meta description to under 160 characters to prevent truncation
3Consolidate to a single H1 tag — use H2–H6 for subtopics
4Fix heading hierarchy to use sequential levels (H1 → H2 → H3) without skipping
5Add a <link rel="canonical"> tag pointing to the preferred version of this page
6Add Open Graph tags (og:title, og:description, og:image, og:url, og:type) for social sharing
7Add Twitter Card meta tags for better social media previews
8Add descriptive anchor text to all links for better SEO and accessibility
9Include your primary keyword in the H1 heading for strongest on-page SEO signal
10Include your primary keyword naturally in the first paragraph to establish topical relevance early
11Include your primary keyword in the URL slug for improved crawlability and click-through rates
12Simplify sentence structure and use shorter words to improve readability to 60+ Flesch Reading Ease
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
15Add TL;DR summaries or definition-style opening paragraphs ("X is...") for zero-click/featured snippet capture
16Complete your Open Graph tags (og:title, og:description, og:image, og:url, og:type, og:locale) for rich social media previews
Key Findings
1Acceptable response time: 727ms
2Lean HTML document: 88KB
31 async and 2 deferred scripts
4Lean CSS payload (~125KB)
5JavaScript payload (~252KB) is acceptable
6Gzip compression enabled
73 third-party script(s) — manageable count
8Estimated LCP: ~1647ms — within Google's "good" threshold (<2.5s)
9Estimated INP: ~90ms — within Google's "good" threshold (<200ms)
10Alternative analytics platform detected (Plausible/Umami/Matomo)
Issues Found
12 render-blocking script(s)
2No lazy loading on images
3No WebP or AVIF image formats found
4No responsive image srcset found
5Only 0/26 images have width/height attributes
6No font-display property found
7No effective Cache-Control header
810 inline <style> blocks
9HTTP/1.1 detected — no multiplexing
10No CDN detected
11No resource hints found
124 render-blocking CSS files — delays first paint
13Moderate estimated CLS: 0.25 — above 0.1 "good" threshold
Recommendations to Reach 100%
1Optimize server response time to under 500ms with caching or a CDN
2Add async or defer attributes to render-blocking scripts
3Add loading="lazy" to below-the-fold images to improve initial page load
4Convert images to WebP or AVIF format for 30–50% file size reduction
5Use srcset and sizes attributes on images to serve appropriately sized images per device
6Add explicit width and height to all images to prevent Cumulative Layout Shift (CLS)
7Add <link rel="preconnect"> for critical third-party domains to reduce DNS lookup time
8Preload critical resources (fonts, hero images) with <link rel="preload">
9Add font-display: swap to web font declarations to show fallback text while fonts load
10Set Cache-Control headers with appropriate max-age to leverage browser caching
11Extract inline styles into external CSS files for better caching and maintainability
12Upgrade to HTTP/2 or HTTP/3 for faster parallel resource loading and header compression
13Use a Content Delivery Network (CDN) like Cloudflare, CloudFront, or Fastly to reduce global latency
14Add preconnect, prefetch, and preload hints for critical third-party resources and fonts
15Reduce render-blocking CSS by inlining critical CSS, using media queries on non-critical stylesheets, and loading non-critical CSS asynchronously
16Reduce CLS: set image dimensions, preload web fonts, reserve space for ads and dynamic content
17Consider adding Google Search Console integration alongside your analytics for SEO-specific insights
Key Findings
1Viewport meta tag present: width=device-width, initial-scale=1
2HTML5 doctype declared
3Character encoding declared
Issues Found
1No theme-color meta tag
2No web app manifest found
3Missing Apple touch icon
4No responsive image srcset — mobile users may download oversized images
5Popup/modal/interstitial detected — Google penalizes intrusive interstitials on mobile
6Only 1 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
3Add <link rel="apple-touch-icon"> for iOS homescreen icons
4Consider implementing a service worker for offline support and faster repeat visits
5Implement srcset to serve smaller images on mobile devices, saving bandwidth
6Remove or minimize intrusive interstitials on mobile — Google's Page Experience update penalizes full-screen popups that block content
7Add multiple icon sizes (192x192, 384x384, 512x512, plus maskable) to your manifest for cross-device support
8Add env(safe-area-inset-*) CSS for proper display on notched/island devices
9Add :active / touch-action CSS for tactile feedback on mobile interactions
Key Findings
1HTTPS enabled — encrypted connection
2Server header not exposing technology details
3X-Powered-By: Express — framework header, minimal risk
4No cookie security issues detected
5Privacy policy link detected
6Subresource Integrity (SRI) on 1 resource(s) — prevents CDN tampering
7Rate limiting recommended for form endpoints
8No stack traces or sensitive error details exposed in responses
9No raw email addresses exposed in page source
Issues Found
1Missing Strict-Transport-Security header
2Missing Content-Security-Policy header
3Missing X-Content-Type-Options header
4Missing X-Frame-Options header
5Missing Referrer-Policy header
6Missing Permissions-Policy header
73 external link(s) without noopener/noreferrer
8No cookie consent banner detected
9Outdated libraries detected: jQuery 3.4.1 (latest 3.7+)
10Server-side software version disclosed: Express — enables version-based vulnerability (CVE) lookups
11Additional technology fingerprints exposed: X-Powered-By: Express
12security.txt file is missing — no standardized channel for reporting vulnerabilities
Recommendations to Reach 100%
1Add Strict-Transport-Security header with max-age=63072000; includeSubDomains; preload
2Implement a Content Security Policy to prevent XSS and injection attacks
3Add X-Content-Type-Options: nosniff to prevent MIME type sniffing
4Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking attacks
5Add Referrer-Policy: strict-origin-when-cross-origin to control referrer leakage
6Add Permissions-Policy to restrict access to camera, microphone, geolocation, etc.
7Add Cross-Origin-Opener-Policy: same-origin-allow-popups
8Add Cross-Origin-Resource-Policy: cross-origin
9Add rel="noopener noreferrer" to external links for security
10Implement a cookie consent banner for GDPR/ePrivacy compliance
11Update outdated JavaScript libraries to latest versions — older versions have known security vulnerabilities (CVEs)
12Implement rate limiting on form endpoints to prevent brute-force attacks and spam submissions
13Suppress 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]
14Add 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]
Key Findings
1Language declared: en
2All 26 images have alt attributes
3All 2 forms have proper labels
4All 2 buttons have accessible labels
5Focus styles detected for keyboard navigation
Issues Found
1No skip navigation link
2Missing landmarks: main, footer
31 iframe(s) missing title
4No ARIA attributes detected
5Heading hierarchy has gaps — confusing for screen readers
63 minor HTML validity issue(s)
726 images missing explicit dimensions — causes layout shifts for screen reader users
816 duplicate ID(s) — breaks ARIA references and label associations
Recommendations to Reach 100%
1Add a "Skip to main content" link as the first focusable element for keyboard users
2Add semantic landmark elements: <main>, <footer>
3Add descriptive title attributes to all iframes
4Add ARIA attributes to interactive elements for better screen reader support
5Review and fix HTML structure issues for better accessibility and cross-browser compatibility
6Set explicit width and height (or CSS aspect-ratio) on all images to prevent layout shifts that disorient assistive technology users
7Ensure all element IDs are unique — duplicate IDs break form labels, ARIA relationships, and fragment navigation
Key Findings
11 schema block(s): LocalBusiness
2Some semantic elements: nav
3FAQ/Q&A content patterns detected — highly valuable for AI citation
4Sitemap reference detected
57 call-to-action elements detected
6No AI crawlers blocked via meta tags — content accessible to AI search engines
7robots.txt file found
8robots.txt references 1 sitemap(s) — aids AI crawler discoverability
9High RAG-friendliness (89/100): 0 headings with IDs, 16 section anchors
10Content provenance signals detected (citations with sources, attributed claims)
Issues Found
1Incomplete social metadata
2No breadcrumb navigation
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
3Increase use of semantic HTML5 elements (article, section, aside, figure) for better AI understanding
4Add breadcrumb navigation with BreadcrumbList schema for better site hierarchy signals
5Use <strong> and <em> tags to highlight key entities, concepts, and terms
6Add links to your social media profiles to strengthen brand entity signals
7Create /llms.txt following the llms.txt standard: # Title, > description, ## Overview, ## Core Services, ## Key Pages with full URLs
8Create /llms-full.txt with comprehensive documentation (services, pricing, team, case studies) for AI models that need depth
9Add <link rel="alternate" type="text/plain" href="/llms.txt"> in your HTML <head> for AI discoverability
10Add dateModified and datePublished meta tags and use <time datetime="..."> elements — AI models prefer fresh, timestamped content
Key Findings
1Moderate content depth (716 words)
2Structured content: 6 lists, 0 tables — easily parsed by AI
33 external citation(s)
4Strong CRO: 3 clear call-to-action elements detected
5Good form usability score: 100/100
6Trust signals present: Reviews/Testimonials, HTTPS Security, Privacy Policy
7Social proof elements detected — builds credibility and conversion confidence
8Clear value proposition detected in heading elements
Issues Found
1No structured Q&A content
2Weak entity markup — few terms emphasized
3Low semantic markup ratio — 203 divs vs 2 semantic elements
4Weak E-E-A-T schema signals
5Paragraphs are too long for optimal AI consumption
6No author or expertise signals
7No CTA above the fold
Recommendations to Reach 100%
1Add FAQ or Q&A sections — AI models heavily rely on question-answer patterns for training data
2Use <strong>, <em>, and <mark> to highlight key entities, concepts, and brand terms for AI comprehension
3Replace generic <div> wrappers with semantic elements (article, section, aside, figure) for AI clarity
4Add Person, Article, and Review schemas to demonstrate expertise, experience, authoritativeness, and trustworthiness
5Break long paragraphs into shorter ones (under 30 words) for better AI comprehension and snippet extraction
6Add Speakable schema markup to help voice assistants identify the most important content
7Include expert quotes in <blockquote> elements to boost E-E-A-T and citation potential
8Add visible author bylines with bios and link to author pages — AI models evaluate content credibility through authorship signals
9Place a clear CTA in your hero/header section so visitors see a conversion path immediately upon landing
Key Findings
1Direct question-answer patterns found — good for Google SGE and AI citations
26 lists provide scannable, AI-friendly content
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
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
4Include unique statistics, expert quotes, and original insights that generative AI would want to cite
5Add multiple schema types (Article, FAQ, HowTo) to help generative engines contextualize your content
6Add bidirectional hreflang tags with x-default to help AI engines serve the correct language variant
7Add original data visualizations, charts, or data tables — generative engines cite pages with unique, first-party data
8Include first-hand insights using phrases like "our research found" or "based on our analysis" to demonstrate original expertise
Key Findings
1Question-answer heading patterns support featured snippet capture
26 lists provide scannable answers for People Also Ask
Issues Found
1No FAQ content or 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%
1Create an FAQ section with FAQPage structured data — essential for People Also Ask and featured snippet inclusion
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
Key Findings
1NAP information detected: phone: 4104520562
2Phone number(s) visible: 4104520562, 410-452-0562
3LocalBusiness schema: LocalBusiness
Issues Found
1No Google Maps embed
2No address microdata
3No geo meta tags
4LocalBusiness schema present but no opening hours
5No review/rating schema
Recommendations to Reach 100%
1Consider displaying a business email for direct contact signals
2Add an embedded Google Map to your contact or about page for local search signals
3Add PostalAddress schema or itemprop="address" microdata to your address elements
4Add geo.region, geo.placename, and geo.position meta tags for geographic targeting
5Add openingHoursSpecification to your LocalBusiness schema — hours are a top local ranking factor
6Add AggregateRating schema to display star ratings in search results — reviews significantly impact local click-through rates
7Add areaServed property to your LocalBusiness schema to define your service radius
Key Findings
11 JSON-LD block(s) with types: LocalBusiness
2All structured data uses JSON-LD format — Google's recommended format
3Some top-tier schemas: LocalBusiness
4No schema validity issues detected
Issues Found
1Only basic schema implementation
2No sameAs properties in schema — missing entity disambiguation
3Schema property completeness averaging 75%
4No rich results eligibility detected
Recommendations to Reach 100%
1Expand structured data with more specific schema types relevant to your content
2Add more top-tier schema types — consider: Organization, Product, Article
3Consider adding secondary schema types: Person, HowTo, Service, Event for richer search features
4Add missing high-impact schemas: WebSite, Product, Review
5Add BreadcrumbList schema — enables breadcrumb rich results in Google
6Add FAQPage schema to FAQ content — enables expandable rich results
7Consider adding HowTo schema for instructional content
8Add more schema types — diverse structured data improves AI and search engine understanding
9Add sameAs links to Organization/Person schema pointing to Wikipedia, Wikidata, social profiles
10Fill in missing recommended properties for each schema type
11Add FAQ, HowTo, or Breadcrumb schema to become eligible for enhanced search result features
12Add SearchAction schema to your WebSite type to enable the sitelinks search box in Google results
Key Findings
1Links are visually distinguishable (underline or decoration detected)
2Relative units (rem/em/clamp) detected — supports text resizing
3Focus styles detected for keyboard navigation visibility
4Page language declared — aids assistive technology
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
3No error suggestion mechanisms detected in forms
4Low semantic-to-div ratio — 203 divs vs 2 semantic elements
5No 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
3Add aria-invalid, aria-errormessage, and visible error messages for form validation (WCAG 3.3.3)
4Replace more generic <div> elements with semantic HTML5 tags for better screen reader navigation
5Add aria-invalid, aria-errormessage, and inline error messages to form fields (WCAG 3.3.1/3.3.3)
6Add aria-live regions (role="status" or role="alert") for form feedback, notifications, and dynamic content updates (WCAG 4.1.3)
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.