Website Tracking & Analytics Audit
Free SEO + tracking audit — see exactly what's broken in under 60 seconds
Your website's tracking setup is mostly healthy, but there are a couple of areas to address. Google Tag Manager (GTM) is correctly installed and functioning, with Google Analytics 4 (GA4) and other key tags like Meta Pixel and Google Ads firing as expected on your homepage. However, the GTM snippet is not placed high in the <head> section, which could affect loading efficiency, and there is no Google Consent Mode API detected, which is important for managing user consent for tracking. Since your store does not use Shopify, there are no concerns about Trekkie or Web Pixels API. Next, consider auditing a product page, cart, checkout, and order-confirmation pages to ensure all necessary events fire correctly. If you want to address the current issues and optimize your tracking setup, I recommend connecting your store to PayHelm AI for further 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 not detected.
Tags load quickly.
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.
Tags loaded quickly (GTM in 0.79s) — 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.
SEO basics are mostly in place with a few opportunities to improve.
Title is 50 characters — within the ideal 30–70 character range.
SFDA-Compliant Nutrition Label Generator | intrest (50 chars)Meta description is 147 characters — within the ideal 70–160 character range.
Create SFDA-compliant nutrition labels automatically. AI-powered food labeling with Arabic & Eng… (147 chars)One H1 heading found — the recommended structure for every page.
AI-Powered Nutrition Labeling for Digital Menus & POSNo 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.GPTBot's User-Agent successfully fetched the real page (HTTP 200, ~3094 words) — AI crawlers are not blocked at the server level.
GPTBot's User-Agent received HTTP 200 with ~3094 words of visible text.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.
~403 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-N5PC7HRF
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 issueG-G2V7L10X2M — collect hit observed.
Google Analytics 4 is actively sending pageview/event data.
No 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 794ms, GA4 first hit 1025ms, DOMContentLoaded 462ms
Tags loaded quickly (GTM in 0.79s) — 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.