Website Tracking & Analytics Audit
Free SEO + tracking audit — see exactly what's broken in under 60 seconds
Your website's tracking infrastructure is mostly functional, but there are a few areas that need attention. On the homepage, key tracking tools like Google Tag Manager (GTM) and Google Analytics 4 (GA4) are firing correctly, and various tags such as Google Ads and Meta Pixel are also active. However, there are some warnings to address: the GTM snippet is not optimally placed in the HTML, and there's no <noscript> fallback, which could affect data collection if users have JavaScript disabled. Additionally, your setup includes a deprecated Universal Analytics tag, and there are conflicting GA4 IDs which could lead to data discrepancies. Since your store is not on Shopify, Trekkie and Web Pixels API are not applicable. For a comprehensive audit, consider reviewing product pages, cart, checkout, and order-confirmation pages next. Given the current issues, I recommend connecting your store to PayHelm AI for more detailed insights and guidance.
GTM container installed and loading.
GA4 is installed and sending data.
4 of 4 key funnel stages look healthy.
No data-quality issues found in tracked events.
Consent Mode present but incomplete (v2 signals missing).
Tags load quickly.
Conflicting or deprecated analytics IDs detected.
The v2 consent signals were seen, but the default consent state and a consent update after the user chooses were not observed. Consent Mode v2 needs both a gtag('consent','default',…) call before tags load and a gtag('consent','update',…) call once the visitor responds (CMP: Cookiebot).
Tags loaded quickly (GTM in 0.90s) — no performance concern.
No cross-domain (linker) tracking was detected. If your checkout or other steps live on a different domain, set up linker tracking so visits aren't split into separate sessions.
Google Ads Enhanced Conversions appear to be set up — hashed first-party data is being passed to improve conversion accuracy.
GA4 User-ID tracking was not detected. If you have logged-in users, setting a User-ID lets GA4 join their activity across devices and sessions.
We couldn't reach the checkout or order-confirmation page during this audit, so purchase tracking is unverified. Purchase is the single most important event to get right — test it with a real or test order and confirm the 'purchase' event fires once on the thank-you page.
Multiple GA4 measurement IDs were found (G-562GXTQTG4, G-TB5D1N0K99, G-DTMZKSKYTE). Sending the same events to more than one GA4 property is sometimes intentional, but is often an accident that doubles event counts or splits data — confirm each ID is meant to be here.
SEO basics are mostly in place with a few opportunities to improve.
Title is only 9 characters. Google shows 50–70 chars — consider expanding.
His House (9 chars)Meta description is 201 characters. Google may truncate descriptions over ~160 chars.
The official website and shop of His House. We offer high-quality faith-based fitness apparel built … (201 chars)One H1 heading found — the recommended structure for every page.
His HouseNo noindex directive — the page is eligible to be indexed.
No robots meta tag (defaults to index, follow).Canonical tag points to the page itself — no duplicate-content signals sent to search engines.
https://honorhishouse.com/All core Open Graph tags found — links display richly when shared on social media.
og:title ✓ og:description ✓ og:image ✓Structured data found — search engines can use it to generate rich results (star ratings, FAQs, products, breadcrumbs, etc.).
JSON-LD script foundViewport meta tag found — the page is set up for mobile-friendly rendering.
viewport meta tag presentThe basics for AI access are in place, but there's no llms.txt yet — an easy, high-leverage addition.
No llms.txt file found. This is a plain-text, markdown-style index of your key pages that AI assistants (ChatGPT, Claude, Perplexity) increasingly check to understand a site quickly.
No /llms.txt found (404 or empty).robots.txt doesn't block any major AI crawler — ChatGPT, Claude, Perplexity, and Google's AI features can all fetch and cite your content.
All 15 known AI crawlers are allowed.Structured data (JSON-LD) is present with types AI answer engines commonly extract facts from (e.g. FAQPage, Product, Organization).
Schema.org types found: Organization.Meaningful text content is present in the raw HTML response — AI crawlers that don't execute JavaScript can still read and cite this page.
~349 words of text visible in the raw HTML response.A sitemap is available at /sitemap.xml, helping both search engines and AI crawlers discover your full set of pages efficiently.
Found at /sitemap.xml.- Add an /llms.txt file listing your most important pages (pricing, docs, product pages) in markdown format — it gives AI assistants a fast, reliable summary of your site instead of guessing from crawled HTML.
Marketing & analytics tags observed sending data while the page loaded.
Every dataLayer push observed during page load — with full payload and configuration analysis.
›GTM lifecycle events (4)— gtm.js, gtm.dom, gtm.load, etc.
Data points present in the dataLayer that your tags can read (the values pushed alongside each event).
The actual tracking requests your browser sent — the ground-truth proof that a tag fired.
GTM-PV2BBNN
A Google Tag Manager container is installed on this page.
1/1 container(s) returned a successful gtm.js response.
The container's JavaScript downloaded successfully, so GTM can run.
No <noscript> fallback found in the HTML source.
The recommended <noscript> fallback is missing. It's minor, but Google's standard install includes it.
Fix this issueGTM snippet was not found high in <head>.
The container loads later than recommended. Tags may fire late and miss early page activity.
Fix this issueG-562GXTQTG4, G-TB5D1N0K99, G-DTMZKSKYTE — collect hit observed.
Google Analytics 4 is actively sending pageview/event data.
Found UA tag.
Universal Analytics stopped processing data in 2023. These tags do nothing and should be removed.
Fix this issuedefault=false, update=false, signals=[ad_storage, analytics_storage, ad_user_data, ad_personalization, functionality_storage, personalization_storage, security_storage], CMP=Cookiebot
The v2 consent signals were seen, but the default consent state and a consent update after the user chooses were not observed. Consent Mode v2 needs both a gtag('consent','default',…) call before tags load and a gtag('consent','update',…) call once the visitor responds (CMP: Cookiebot).
Fix this issueGTM 899ms, GA4 first hit 1676ms, DOMContentLoaded 668ms
Tags loaded quickly (GTM in 0.90s) — no performance concern.
No linker configuration observed
No cross-domain (linker) tracking was detected. If your checkout or other steps live on a different domain, set up linker tracking so visits aren't split into separate sessions.
allow_enhanced_conversions in code
Google Ads Enhanced Conversions appear to be set up — hashed first-party data is being passed to improve conversion accuracy.
Not detected
GA4 User-ID tracking was not detected. If you have logged-in users, setting a User-ID lets GA4 join their activity across devices and sessions.
G-562GXTQTG4, G-TB5D1N0K99, G-DTMZKSKYTE
Multiple GA4 measurement IDs were found (G-562GXTQTG4, G-TB5D1N0K99, G-DTMZKSKYTE). Sending the same events to more than one GA4 property is sometimes intentional, but is often an accident that doubles event counts or splits data — confirm each ID is meant to be here.
Fix this issuepurchase observed=false, checkout page audited=false
We couldn't reach the checkout or order-confirmation page during this audit, so purchase tracking is unverified. Purchase is the single most important event to get right — test it with a real or test order and confirm the 'purchase' event fires once on the thank-you page.
Fix this issueFunnel events are page-specific: purchase only fires on order confirmation, add_to_cart requires a user click. Events shown as are not observable on this page type — audit each page separately for full coverage.
Discovery
Observed on collection page — this stage is firing correctly.
Not observed during this load — 'select_item' requires user interaction on collection/category pages. Verify by manually testing the action on that page.
Consideration
Not observable on home pages — 'view_item' only fires on product detail pages. Audit that page type to verify coverage.
Cart Activity
Not observable on home pages — 'add_to_cart' only fires on product pages and cart. Audit that page type to verify coverage.
Not observable on home pages — 'remove_from_cart' only fires on cart page. Audit that page type to verify coverage.
Not observable on home pages — 'view_cart' only fires on cart page. Audit that page type to verify coverage.
Checkout Funnel
Not observable on home pages — 'begin_checkout' only fires on checkout entry page. Audit that page type to verify coverage.
Not observable on home pages — 'add_shipping_info' only fires on checkout shipping step. Audit that page type to verify coverage.
Not observable on home pages — 'add_payment_info' only fires on checkout payment step. Audit that page type to verify coverage.
Not observable on home pages — 'purchase' only fires on order confirmation / thank-you page. Audit that page type to verify coverage.
Post-Purchase
This event fires server-side (server-side or order management system) and cannot be observed by a browser-based audit.
The audit automatically visited additional page types discovered on the site to verify tags fire across the full funnel, not just on the entry page.
Your tracking has gaps — PayHelm can fix this.
Broken tags mean lost attribution and bad decisions. PayHelm unifies your ecommerce, ad, and analytics data so every number is trustworthy — no guesswork.