Website Tracking & Analytics Audit
Free SEO + tracking audit — see exactly what's broken in under 60 seconds
Your website's tracking setup is mostly in good shape, but there are a few areas to improve. Google Tag Manager (GTM) and Google Analytics 4 (GA4) are both functioning correctly, and key tags like the Meta Pixel and Google Ads are firing as expected on your homepage. However, there's a minor issue with the absence of a <noscript> fallback, which could affect users with JavaScript disabled, and Google Consent Mode isn't being utilized, which is important for compliance with privacy regulations. Since your store isn't on Shopify, there's no need to worry about Trekkie or Web Pixels API. Next, you should audit other page types like product pages, cart, and checkout to ensure tracking is consistent across your site. Given the current issues, I recommend connecting your store to PayHelm AI for a more thorough analysis and guidance.
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 1.49s) — 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.
4 SEO improvements identified — addressing them could meaningfully boost organic visibility.
Title is 74 characters. Google may truncate titles over ~70 chars in search results.
Language Services by ISO Certified Provider | Mobico by Saltlux Innovation (74 chars)Meta description is 6 characters. Aim for 70–160 chars to maximise click-through rate.
MOBICO (6 chars)One H1 heading found — the recommended structure for every page.
No noindex directive — the page is eligible to be indexed.
robots: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:largeCanonical tag points to a different URL. Verify this is intentional (cross-domain canonical or redirect chain).
http://mobico.com/en/main/main.do?mId=11 Open Graph tag(s) missing. Complete the set for consistent 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.We attempted to fetch your homepage using GPTBot's real User-Agent string to check for server/firewall-level blocking, but the request itself failed (network/timeout). This doesn't necessarily mean AI crawlers are blocked.
Could not verify — the live fetch as GPTBot timed out or failed to connect.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.
~2337 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-5KMQW4HJ
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 issueG-1JPZX46G58 — collect hit observed.
Google Analytics 4 is actively sending pageview/event data.
1 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.
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 1485ms, GA4 first hit 1675ms, DOMContentLoaded 1351ms
Tags loaded quickly (GTM in 1.49s) — 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.
Failed to load resource: the server responded with a status of 404 ()
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.