Website Tracking & Analytics Audit
Free SEO + tracking audit — see exactly what's broken in under 60 seconds
Your website's tracking setup has some areas that need attention. While your Google Tag Manager (GTM) is correctly installed and functioning, there are a few issues to address: the absence of a <noscript> fallback, which can affect tracking for users with JavaScript disabled, and the dataLayer not being initialized before the GTM container, which could lead to data collection issues. Additionally, GA4 tracking is not set up, meaning you're missing out on valuable analytics data. Since your site is not built on Shopify, there are no concerns regarding Shopify-specific tracking or duplicate pixels. For a more comprehensive audit, I recommend checking the tracking on your product pages, cart, checkout, and order confirmation pages next. To address these issues effectively, consider connecting your store to PayHelm AI for expert guidance.
GTM container installed and loading.
No GA4 measurement detected.
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. This mainly matters if you run Google Ads with EEA/UK traffic — no Google Ads pixel was seen on this site, so it's lower priority for now.
Google Tag Manager loaded in 2.6s — 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 basics are mostly in place with a few opportunities to improve.
Title is 58 characters — within the ideal 30–70 character range.
Glasgow Graphic Design & Branding Studio | G3 Creative (58 chars)Meta description is 138 characters — within the ideal 70–160 character range.
Strategic branding, memorable logos, and tactile print design for Scottish businesses that want to b… (138 chars)One H1 heading found — the recommended structure for every page.
G3 Creative — Glasgow’s Graphic Design Studio for Brands That Need t…No 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://www.g3creative.co.uk/2 Open Graph tag(s) missing. Complete the set for consistent social link previews.
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.GPTBot's User-Agent successfully fetched the real page (HTTP 200, ~791 words) — AI crawlers are not blocked at the server level.
GPTBot's User-Agent received HTTP 200 with ~791 words of visible text.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.Meaningful text content is present in the raw HTML response — AI crawlers that don't execute JavaScript can still read and cite this page.
~782 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.
No tags were observed sending data. They may be gated behind cookie consent, or none are configured.
— none observed —
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-TCPTSQ6V
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 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 issueNo GA4 measurement detected.
No Google Analytics 4 tag was detected on this page.
No consent API calls observed
No Google Consent Mode was detected. This mainly matters if you run Google Ads with EEA/UK traffic — no Google Ads pixel was seen on this site, so it's lower priority for now.
GTM 2610ms, DOMContentLoaded 3201ms
Google Tag Manager loaded in 2.6s — 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.
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.