Website Tracking & Analytics Audit
Free SEO + tracking audit — see exactly what's broken in under 60 seconds
Your website's tracking setup shows some areas for improvement. Google Analytics 4 (GA4) is correctly installed and firing on the page, which is good for capturing visitor data. However, there's a warning because a Google Tag Manager (GTM) container isn't present; instead, you're using gtag.js directly. This isn't necessarily a problem, but GTM can offer more flexibility and control over your tags. Since your store is not on Shopify, there's no need to worry about Trekkie or Web Pixels API. The missing events like 'view_item' are expected on this page type, so they aren't actual gaps. Next, you should audit your product pages, cart, and checkout to ensure all relevant events are firing correctly. If you're concerned about optimizing your analytics setup, consider connecting your store to PayHelm AI for further assistance.
Tag setup present but not confirmed loading.
GA4 is installed and sending data.
1 of 4 key funnel stages look healthy.
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. 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.
Tags loaded quickly — 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.
We couldn't reach the checkout or order-confirmation page during this audit, so purchase tracking is unverified. Purchase is the single most important event to get right — test it with a real or test order and confirm the 'purchase' event fires once on the thank-you page.
SEO fundamentals look solid across all checks.
Title is 58 characters — within the ideal 30–70 character range.
Kit de Réparation de Vanne à Italtherm,Sime | ProChaudière (58 chars)Meta description is 155 characters — within the ideal 70–160 character range.
Kit de Réparation de Vanne à Trois Voies pour Chaudière à Gaz Italtherm City Classe 803000076 — Ital… (155 chars)One H1 heading found — the recommended structure for every page.
Kit de réparation de vanne à trois voies pour chaudière à gaz Italtherm City Cla…No noindex directive — the page is eligible to be indexed.
robots: index, followCanonical tag points to the page itself — no duplicate-content signals sent to search engines.
https://www.prochaudiere.com/fr/produits/kit-de-reparation-de-vanne-a-trois-voie…All core Open Graph tags found — links display richly when shared on social media.
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: robots.txt explicitly disallows every major AI crawler — ChatGPT, Claude, Perplexity, and Google AI cannot cite 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 blocks every major AI crawler. Your content cannot be cited by ChatGPT, Claude, Perplexity, or Google AI Overviews — verify this is intentional.
15 of 15 AI crawlers blocked: GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, Claude-Web, anthropic-ai, PerplexityBot, Perplexity-User, Google-Extended, Applebot-Extended, Bytespider, CCBot, Amazonbot, cohere-ai, Meta-ExternalAgent.GPTBot's User-Agent successfully fetched the real page (HTTP 200, ~674 words) — AI crawlers are not blocked at the server level.
GPTBot's User-Agent received HTTP 200 with ~674 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: Organization, WebSite, Product, BreadcrumbList, FAQPage.Meaningful text content is present in the raw HTML response — AI crawlers that don't execute JavaScript can still read and cite this page.
~665 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.
- Unblock GPTBot, OAI-SearchBot, ChatGPT-User, … in robots.txt if you want your content surfaced in AI answers — each blocked bot means that assistant can't read or cite your pages.
No GTM-XXXX container; gtag.js present instead.
Tags are loaded directly via gtag.js rather than through Tag Manager. That works, but you lose GTM's centralised management, versioning, and conditional firing controls.
Fix this issueG-T70SM9SC12 — 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. 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.
GA4 first hit 1119ms, DOMContentLoaded 963ms
Tags loaded quickly — 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.
purchase observed=false, checkout page audited=false
We couldn't reach the checkout or order-confirmation page during this audit, so purchase tracking is unverified. Purchase is the single most important event to get right — test it with a real or test order and confirm the 'purchase' event fires once on the thank-you page.
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
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 firing, but 'view_cart' was found configured in the site's JavaScript. It may fire only when users take specific actions or visit the relevant page type. Not observed on this page. Set up 'view_cart' on your cart page for funnel visibility.
Checkout Funnel
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.
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.
GA4 gtag.js snippet installed directly in the page HTML (outside GTM).
Fix: Remove the hardcoded GA4 snippet and manage it via a GTM 'Google Analytics: GA4 Configuration' tag.
Risk: Running GA4 both directly and via GTM sends duplicate pageviews and inflates every metric in your reports.
Failed to load resource: the server responded with a status of 401 ()
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.