Website Tracking & Analytics Audit
Free SEO + tracking audit — see exactly what's broken in under 60 seconds
The audit of your website's tracking setup shows that your Google Tag Manager (GTM) and Google Analytics 4 (GA4) are functioning well, with both systems successfully firing on your homepage. However, there is a minor issue with the dataLayer not being clearly initialized before the GTM container, which could potentially affect data accuracy. Additionally, Google Consent Mode is not fully optimized, which might impact how consent is managed for tracking purposes. Since your store is not using Shopify, there are no concerns about Trekkie or Web Pixels API. For a comprehensive view of your tracking setup, I recommend auditing other key pages like product pages, the cart, and checkout. If you're looking to address these issues efficiently, consider connecting your store to PayHelm AI for expert assistance.
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 present but incomplete (v2 signals missing).
Tags load quickly.
No conflicting analytics IDs.
Consent Mode is set up, but the v2 signals (ad_personalization) were not seen. Consent Mode v2 needs ad_user_data and ad_personalization for Google Ads remarketing and modeling to work.
Tags loaded quickly (GTM in 0.17s) — 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 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.
3 SEO improvements identified — addressing them could meaningfully boost organic visibility.
Title is 73 characters. Google may truncate titles over ~70 chars in search results.
Luxury Apartments in Sandringham | Loam House – Final Release Now Selling (73 chars)Meta description is 187 characters. Google may truncate descriptions over ~160 chars.
Explore Bayside’s largest, house-sized apartments at Loam House. Featuring premium finishes, abundan… (187 chars)One H1 heading found — the recommended structure for every page.
House-sized apartments in Sandringham FROM $797,000No noindex directive — the page is eligible to be indexed.
No robots meta tag (defaults to index, follow).No canonical tag found. Adding one prevents duplicate-content issues when a page is accessible via multiple URLs.
No canonical link tag found.No Open Graph tags found. Add og:title, og:description, and og:image for rich social link previews.
og:title ✗ og:description ✗ og:image ✗No structured data found. Adding Schema.org markup can unlock rich snippets and improve your search appearance.
No structured data found.Viewport 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).No robots.txt file at all. AI crawlers are implicitly allowed, but you also have no way to signal crawl preferences (e.g. rate limits) to them.
No robots.txt found — all crawlers implicitly allowed.No structured data found. AI answer engines lean heavily on Schema.org markup (FAQPage, Product, Organization) to extract clean facts instead of parsing raw HTML.
No JSON-LD structured data found.Meaningful text content is present in the raw HTML response — AI crawlers that don't execute JavaScript can still read and cite this page.
~500 words of text visible in the raw HTML response.No sitemap.xml found. Without one, crawlers (including AI crawlers) can only discover pages by following links, which may miss deeper content.
No /sitemap.xml found.- 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.
- Add JSON-LD structured data (Organization + FAQPage at minimum) so AI assistants can extract accurate facts about your business instead of guessing from page text.
- Publish a sitemap.xml — it's the fastest way for both search engines and AI crawlers to discover every page worth citing, not just the ones linked from your homepage.
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-KMSRC5MS
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 appears inside <head>.
The container is loaded early, as Google recommends, so tags fire as soon as possible.
dataLayer 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-N8P92XENSP — collect hit observed.
Google Analytics 4 is actively sending pageview/event data.
default=false, update=true, signals=[ad_storage, analytics_storage, ad_user_data]
Consent Mode is set up, but the v2 signals (ad_personalization) were not seen. Consent Mode v2 needs ad_user_data and ad_personalization for Google Ads remarketing and modeling to work.
Fix this issueGTM 174ms, GA4 first hit 1096ms, DOMContentLoaded 400ms
Tags loaded quickly (GTM in 0.17s) — 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.
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.
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.