Website Tracking & Analytics Audit
Free SEO + tracking audit — see exactly what's broken in under 60 seconds
The audit of your homepage tracking setup reveals some important points to address. Currently, Google Tag Manager (GTM) is not set up, and instead, a basic gtag.js is in use, which limits your tracking capabilities. Google Analytics 4 (GA4) is not present, which means you're missing out on valuable insights from this analytics platform. On the positive side, a Google Ads tag did fire, indicating some level of tracking is operational. However, there are warnings about the lack of a consent API and JavaScript errors related to content security policies, which could affect data collection reliability. Since your store is not on Shopify, there are no concerns about Trekkie or Web Pixels API. The next step is to audit other critical pages like product pages, the cart, and the checkout process to ensure comprehensive tracking across the site. Given the current issues, I recommend connecting your store to PayHelm AI to help streamline and optimize your analytics setup.
Tag setup present but not confirmed 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 load timing not measured.
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.
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 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 66 characters — within the ideal 30–70 character range.
Evoweb - Création de sites web sur mesure pour petites entreprises (66 chars)Meta description is 117 characters — within the ideal 70–160 character range.
Evoweb crée des sites web modernes et personnalisés pour les petites entreprises, à prix fixe et san… (117 chars)No H1 heading found. Search engines use H1 to understand the page's primary topic — every page should have exactly one.
No H1 tag found.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.evoweb.ca/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 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.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.Very little text is present in the raw HTML — this page likely relies on client-side JavaScript to render content. Most AI crawlers (GPTBot, ClaudeBot, PerplexityBot) don't execute JavaScript, so they may see a near-empty page.
~0 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.
- Server-render (or pre-render) key page content — most AI crawlers don't run JavaScript, so client-side-only rendering makes your content invisible to them even though it looks fine in a browser.
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 issueNo GA4 measurement detected.
No Google Analytics 4 tag was detected on this page.
2 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 issueDOMContentLoaded 638ms
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.
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.
Refused to connect to 'https://ad.doubleclick.net/ccm/s/collect?auid=165945354.1787156143>m=45be68i0v9261108049za200zd9261108049xec&fmt=8' because it violates the following Content Security Policy directive: "connect-src 'self' https://www.googletagmanager.com https://www.googleadservices.com http
Refused to connect to 'https://ad.doubleclick.net/ccm/s/collect?auid=165945354.1787156143>m=45be68i0v9261108049za200zd9261108049xec&fmt=8' because it violates the document's Content Security Policy.
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.