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 on the product page revealed some significant issues. Currently, there is no Google Tag Manager (GTM) container or Google Analytics 4 (GA4) tracking in place, which are crucial for comprehensive analytics. On this page, only the TikTok and Meta Pixels successfully fired, which limits your ability to gather detailed insights. A critical gap identified is the lack of tracking for key events like 'view_item', which should be present on product pages. Additionally, there is no Shopify-native analytics detected, which means you're missing out on valuable data from Shopify's Trekkie/Web Pixels API. Given these findings, it's important to address the missing GTM and GA4 setups to enhance your data collection capabilities. I recommend auditing other key pages such as the product page, cart, checkout, and order-confirmation pages to ensure comprehensive tracking across your entire site. To address these issues effectively, consider connecting your store to PayHelm AI for expert guidance and solutions.
No GTM container or gtag.js detected.
No GA4 measurement detected.
1 of 4 key funnel stages look healthy.
No data-quality issues found in tracked events.
Consent Mode not detected.
Tag load timing not measured.
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.
No tag load timing was captured (the container may not have loaded, or timing was unavailable).
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 appear to be set up — hashed first-party data is being passed to improve conversion accuracy.
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.
Neither checkout nor purchase tracking was observed. These are the events that matter most for revenue reporting — confirm begin_checkout and purchase fire end-to-end.
3 SEO improvements identified — addressing them could meaningfully boost organic visibility.
Title is 52 characters — within the ideal 30–70 character range.
CAPTEUR DE DEBIT ITALTHERM EURO FLAMME - Alger Froid (52 chars)No meta description. While not a direct ranking factor, a good description significantly improves click-through from search results.
No meta description found.One H1 heading found — the recommended structure for every page.
CAPTEUR DE DEBIT ITALTHERM EURO FLAMMENo noindex directive — the page is eligible to be indexed.
robots: index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1Canonical tag points to a different URL. Verify this is intentional (cross-domain canonical or redirect chain).
https://alger-froid.com/index.php//produit/capteur-de-debit-italtherm-euro-flamm…1 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 presentBlocked: AI crawlers are actually refused at the server level (HTTP 429) when they try to fetch this site.
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.We fetched your homepage using GPTBot's real User-Agent and it was refused (HTTP 429). This is a server/firewall-level block — AI crawlers cannot read this site at all, regardless of what robots.txt says.
GPTBot's User-Agent received HTTP 429.Structured data (JSON-LD) is present with types AI answer engines commonly extract facts from (e.g. FAQPage, Product, Organization).
Schema.org types found: BreadcrumbList, WebSite, Organization, Product.Meaningful text content is present in the raw HTML response — AI crawlers that don't execute JavaScript can still read and cite this page.
~580 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.
- AI crawlers get blocked at the server level (HTTP 429) when fetching your homepage, even though this may not show up in robots.txt. Check your WAF/CDN's bot-management rules for a User-Agent block on AI crawlers.
- 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.
WooCommerce markup (woocommerce / wc-* classes) in HTML
No GTM container found.
No Google Tag Manager container was found on this page. If you rely on GTM for analytics and ads tags, nothing will fire.
Fix this issueNo GA4 measurement detected.
No Google Analytics 4 tag was detected on this page.
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.
WooCommerce markup (woocommerce / wc-* classes) in HTML
This site runs on WooCommerce. Tracking setup and common pitfalls differ by platform, which is factored into this audit.
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.
DOMContentLoaded 2085ms
No tag load timing was captured (the container may not have loaded, or timing was unavailable).
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.
allow_enhanced_conversions in code
Google Ads Enhanced Conversions appear to be set up — hashed first-party data is being passed to improve conversion accuracy.
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.
purchase observed=false, checkout page audited=true
Neither checkout nor purchase tracking was observed. These are the events that matter most for revenue reporting — confirm begin_checkout and purchase fire end-to-end.
Fix this issueFunnel events are page-specific: purchase only fires on order confirmation, add_to_cart requires a user click. Events shown as are not observable on this page type — audit each page separately for full coverage.
Discovery
Not observed on this page. Set up 'view_item_list' on your collection/category/search pages for funnel visibility.
Fix this gapNot observed during this load — 'select_item' requires user interaction on collection/category pages. Verify by manually testing the action on that page.
Consideration
Not observed firing, but 'view_item' was found in the site's JavaScript — the event handler exists but wasn't triggered during this audit. Verify it fires correctly by visiting the relevant page type. No ecommerce tracking detected on this page. Add a 'view_item' dataLayer push on your product detail pages.
Fix this gapCart Activity
Not observed during this load — 'add_to_cart' requires user interaction on product pages and cart. Verify by manually testing the action on that page.
Not observed during this load — 'remove_from_cart' requires user interaction on cart page. Verify by manually testing the action on that page.
Not observed on this page. Set up 'view_cart' on your cart page for funnel visibility.
Fix this gapCheckout Funnel
Not observed firing, but 'begin_checkout' was found in the site's JavaScript — the event handler exists but wasn't triggered during this audit. Verify it fires correctly by visiting the relevant page type. No ecommerce tracking detected on this page. Add a 'begin_checkout' dataLayer push on your checkout entry page.
Fix this gapNot observed during this load — 'add_shipping_info' requires user interaction on checkout shipping step. Verify by manually testing the action on that page.
Not observed during this load — 'add_payment_info' requires user interaction on checkout payment step. Verify by manually testing the action on that page.
Not observed firing, but 'purchase' was found in the site's JavaScript — the event handler exists but wasn't triggered during this audit. Verify it fires correctly by visiting the relevant page type. No ecommerce tracking detected on this page. Add a 'purchase' dataLayer push on your order confirmation / thank-you page.
Fix this gapPost-Purchase
This event fires server-side (server-side or order management system) and cannot be observed by a browser-based audit.
These tracking scripts are hardcoded directly in your page HTML. Moving them into GTM makes them easier to update, pause, version, and conditionally fire — without touching your code.
TikTok Pixel hardcoded in the page HTML.
Fix: Use the GTM TikTok Pixel community template.
Risk: Hardcoded pixels can't be paused or scoped to specific pages without a deploy.
The audit automatically visited additional page types discovered on the site to verify tags fire across the full funnel, not just on the entry page.
Failed to load resource: net::ERR_FAILED
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.