payhelm.com Tracking & SEO Audit — Grade B
A saved report based on tracking and pages observed during this scan.
Your website's tracking setup shows a generally healthy infrastructure, with Google Tag Manager (GTM) and Google Analytics 4 (GA4) firing correctly on the homepage. The OpenAI Ads Pixel and Google Ads tags also fired as expected. However, there are a couple of areas that need attention: Google Consent Mode is not being utilized, which could affect data collection compliance, and the tag load performance is slower than ideal, which might impact user experience. There is no Shopify or Trekkie/Web Pixels API detected, which is expected since this is not a Shopify store. The main gap identified is the absence of 'view_item_list' tracking on the homepage, which is crucial for understanding product list interactions. For a comprehensive audit, consider reviewing other key pages like product, cart, checkout, and order-confirmation pages to ensure all critical events are captured. Given the identified issues, especially the missing 'view_item_list' event, it would be beneficial to connect your store to PayHelm AI for more detailed insights and recommendations.
GTM container installed and loading.
GA4 is installed and sending data.
4 of 4 key funnel stages look healthy.
No data-quality issues found in tracked events.
Consent Mode not detected.
Tag loading is slower than ideal.
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.
Google Tag Manager took 6.1s to load. Slow tag loading delays tracking and can hurt page performance — consider reducing the number of tags or loading them later.
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 53 characters — within the ideal 30–70 character range.
PayHelm: The Agentic Analytics Platform for Ecommerce (53 chars)Meta description is 150 characters — within the ideal 70–160 character range.
AI Agent automates your ads, inventory, and email. AI Report Builder answers any business question i… (150 chars)One H1 heading found — the recommended structure for every page.
Your Data, Your Team, Your AI. Unified Trusted Source of Truth.No noindex directive — the page is eligible to be indexed.
No robots meta tag (defaults to index, follow).Canonical tag points to the page itself — no duplicate-content signals sent to search engines.
https://www.payhelm.com/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 presentAI discoverability looks strong — AI crawlers can access, parse, and cite this site's content.
llms.txt is present and well-formed — AI assistants that check this file can quickly find your key pages and docs.
Found at /llms.txt with a title heading and 21 linked resources.skill.md is present and describes agent-usable capabilities — AI agents that check this convention can find what the site exposes to them.
Found at /skill.md with a title heading.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.GPTBot's User-Agent successfully fetched the real page (HTTP 200, ~1603 words) — AI crawlers are not blocked at the server level.
GPTBot's User-Agent received HTTP 200 with ~1603 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, SoftwareApplication.Meaningful text content is present in the raw HTML response — AI crawlers that don't execute JavaScript can still read and cite this page.
~1660 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.Every endpoint and domain referenced in llms.txt / skill.md actually resolves — no hallucinated links for AI agents to trip over.
All 15 referenced links resolved successfully.WooCommerce markup (woocommerce / wc-* classes) in HTML
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-WMBP43B
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 appears inside <head>.
The container is loaded early, as Google recommends, so tags fire as soon as possible.
dataLayer is defined before the container snippet.
Data is available to tags from the very first event.
G-WDQMHG5BXM — collect hit observed.
Google Analytics 4 is actively sending pageview/event data.
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. 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 6124ms, GA4 first hit 4824ms, DOMContentLoaded 2298ms
Google Tag Manager took 6.1s to load. Slow tag loading delays tracking and can hurt page performance — consider reducing the number of tags or loading them later.
Fix this issueNo 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
Not observable on home pages — 'view_item' only fires on product detail pages. Audit that page type to verify coverage.
Cart Activity
Not observable on home pages — 'add_to_cart' only fires on product pages and cart. Audit that page type to verify coverage.
Not observable on home pages — 'remove_from_cart' only fires on cart page. Audit that page type to verify coverage.
Not observable on home pages — 'view_cart' only fires on cart page. Audit that page type to verify coverage.
Checkout Funnel
Not observable on home pages — 'begin_checkout' only fires on checkout entry page. Audit that page type to verify coverage.
Not observable on home pages — 'add_shipping_info' only fires on checkout shipping step. Audit that page type to verify coverage.
Not observable on home pages — 'add_payment_info' only fires on checkout payment step. Audit that page type to verify coverage.
Not observable on home pages — 'purchase' only fires on order confirmation / thank-you page. Audit that page type to verify coverage.
Post-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.
OpenAI Ads Measurement Pixel found hardcoded directly in the page HTML.
Fix: This pixel is installed directly (OpenAI does not offer a GTM template), so hardcoding is expected — just make sure it only appears once per page.
Risk: A duplicate install (e.g. also added via a Custom HTML tag in GTM) would double-fire oaiq('measure', ...) conversion events and inflate reported conversions.
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.