Website Tracking & Analytics Audit
Free SEO + tracking audit — see exactly what's broken in under 60 seconds
Your website's tracking setup has some critical issues that need attention. While Google Tag Manager (GTM) and Google Analytics 4 (GA4) are correctly implemented and firing on your homepage, there are several warnings and a failure that could impact data accuracy. The GTM snippet isn't placed optimally in the <head> section, and the dataLayer isn't initialized before the GTM container, which could lead to data collection issues. Additionally, there's a critical failure with the Google Tag (gtag) implementation, as it's not defined, leading to errors. Since your store isn't using Shopify, there's no concern about Trekkie or duplicate pixel risks. Next, you should audit your product pages, cart, checkout, and order-confirmation pages to ensure comprehensive tracking. Given the issues identified, I recommend connecting your store to PayHelm AI for a more in-depth analysis and resolution.
GTM container installed and loading.
GA4 is installed and sending data.
Not an ecommerce store — scored on basic analytics coverage.
No data-quality issues found in tracked events.
Consent Mode not detected.
Tag loading is slower than ideal.
No conflicting analytics IDs.
No Google Consent Mode was detected. Since March 2024 Google requires Consent Mode v2 for sites with EEA/UK traffic running Google Ads — without it, conversion and remarketing data is lost for users who haven't consented.
Google Tag Manager loaded in 2.1s — a little slow. Keeping it under ~1.5s helps both tracking accuracy and page speed.
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 were not detected. They send hashed first-party data (email/phone) to recover conversions lost to cookie restrictions — worth enabling if you run Google Ads.
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.
SEO fundamentals look solid across all checks.
Title is 60 characters — within the ideal 30–70 character range.
Precision Mobile Detailing | Mobile Detailing in Keysborough (60 chars)Meta description is 147 characters — within the ideal 70–160 character range.
Mobile detailing in Dandenong that comes to you. Honest pricing, easy online booking, and a full det… (147 chars)One H1 heading found — the recommended structure for every page.
Mobile Detailing in South East Melbourne and Surrounding SuburbsNo noindex directive — the page is eligible to be indexed.
robots: index, followCanonical tag points to the page itself — no duplicate-content signals sent to search engines.
https://pmdmelbourne.comAll 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: WebSite, FAQPage.Meaningful text content is present in the raw HTML response — AI crawlers that don't execute JavaScript can still read and cite this page.
~2934 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 (3)— 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-KNN7FT86
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.
Found <noscript> ns.html iframe.
The fallback for visitors with JavaScript disabled is in place.
GTM snippet was not found high in <head>.
The container loads later than recommended. Tags may fire late and miss early page activity.
Fix this issuedataLayer was not clearly initialised before the container snippet.
If the container loads before dataLayer is ready, early values (like ecommerce data) can be lost.
Fix this issueG-Q10F73GM28 — collect hit observed.
Google Analytics 4 is actively sending pageview/event data.
3 error(s) logged.
JavaScript errors were logged during page load. These don't necessarily affect tracking — only errors that directly interrupt pixel execution matter. See any vendor-specific errors below for actionable issues.
'Google is not defined' error observed at runtime.
gtag.js is missing or loading after a gtag() call. Ensure the gtag.js script tag appears before any gtag() calls in the page.
Fix this issueNo consent API calls observed
No Google Consent Mode was detected. Since March 2024 Google requires Consent Mode v2 for sites with EEA/UK traffic running Google Ads — without it, conversion and remarketing data is lost for users who haven't consented.
Fix this issueGTM 2090ms, GA4 first hit 3909ms, DOMContentLoaded 2472ms
Google Tag Manager loaded in 2.1s — a little slow. Keeping it under ~1.5s helps both tracking accuracy and page speed.
Fix this issueNo 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.
Not detected
Google Ads Enhanced Conversions were not detected. They send hashed first-party data (email/phone) to recover conversions lost to cookie restrictions — worth enabling if you run Google Ads.
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.
Ecommerce Funnel — Not Applicable
This site doesn't appear to be an online store, so the ecommerce funnel report has been skipped. GTM tag coverage, triggers, variables, and on-page scripts are still audited above.
If this site does sell products, try re-running the audit on a product page URL — that will surface add-to-cart, checkout, and purchase event coverage.
gtag is not defined
Failed to load resource: the server responded with a status of 404 ()
Manifest: Line: 1, column: 1, Syntax error.
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.