Website Tracking & Analytics Audit

payhelm.com Tracking & SEO Audit — Grade B

A saved report based on tracking and pages observed during this scan.

Last scanned Aug 16, 2026 — scored warn. Same result as last time.

Works, with issueshttps://www.payhelm.com/

Read the full audit summary

Your website's tracking infrastructure is mostly healthy, with Google Tag Manager (GTM) and Google Analytics 4 (GA4) functioning correctly on the homepage. Both Google Ads and GA4 tags fired as expected. However, there's a warning regarding Google Consent Mode, which wasn't detected, and tag load performance was slower than optimal. Additionally, there's a gap in tracking the 'view_item_list' event, which should be firing on your homepage. Since your store isn't on Shopify, Trekkie and Web Pixels API aren't applicable, but it's important to address the slow tag load times and ensure all relevant events are firing. Next, you should audit product pages, cart, checkout, and order-confirmation pages to ensure comprehensive tracking across your site. Given the current issues, I recommend connecting your store to PayHelm AI for further insights and optimization.

What to look at first

Priorities below are taken directly from findings in this report.

SEO Review

100out of 100Grade AExcellent

SEO fundamentals look solid across all checks.

Title tagPass

Title is 53 characters — within the ideal 30–70 character range.

PayHelm: The Agentic Analytics Platform for Ecommerce (53 chars)

Meta descriptionPass

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)

H1 headingPass

One H1 heading found — the recommended structure for every page.

The AgenticAnalytics Platformfor Ecommerce

Robots / indexabilityPass

No noindex directive — the page is eligible to be indexed.

No robots meta tag (defaults to index, follow).

Canonical URLPass

Canonical tag points to the page itself — no duplicate-content signals sent to search engines.

https://www.payhelm.com/

Open Graph tagsPass

All core Open Graph tags found — links display richly when shared on social media.

og:title ✓ og:description ✓ og:image ✓

Structured data (Schema.org)Pass

Structured data found — search engines can use it to generate rich results (star ratings, FAQs, products, breadcrumbs, etc.).

JSON-LD script found

Mobile viewportPass

Viewport meta tag found — the page is set up for mobile-friendly rendering.

viewport meta tag present

AI Discovery & AI SEOOpen to AI

88out of 100Grade BGood

AI discoverability looks strong — AI crawlers can access, parse, and cite this site's content.

llms.txt filePass

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 11 linked resources.

AI crawler access (robots.txt)Pass

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 for AI answersWarning

JSON-LD is present, but not using the schema types AI engines rely on most (FAQPage, Product, Organization, Article). Consider adding one that matches your content.

JSON-LD present but no @type found.

Server-rendered contentPass

Meaningful text content is present in the raw HTML response — AI crawlers that don't execute JavaScript can still read and cite this page.

~1614 words of text visible in the raw HTML response.

XML sitemapPass

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.

AI crawlers

GPTBot ✓OAI-SearchBot ✓ChatGPT-User ✓ClaudeBot ✓Claude-Web ✓anthropic-ai ✓PerplexityBot ✓Perplexity-User ✓Google-Extended ✓Applebot-Extended ✓Bytespider ✓CCBot ✓Amazonbot ✓cohere-ai ✓Meta-ExternalAgent ✓

Opportunities

Add FAQPage or Organization structured data (JSON-LD) — AI answer engines pull facts directly from these schema types when citing sources.

WooCommercedetected

WooCommerce markup (woocommerce / wc-* classes) in HTML

GTM-WMBP43Bhead

Loaded

Tags(2)

Marketing & analytics tags observed sending data while the page loaded.

Google AdsConversion / Remarketing

2 hits

Google Analytics 4GA4 Event

1 hit

Triggers(5)

Every dataLayer push observed during page load — with full payload and configuration analysis.

›GTM lifecycle events (3)— gtm.js, gtm.dom, gtm.load, etc.

Variables(5)

Data points present in the dataLayer that your tags can read (the values pushed alongside each event).

eventgtm.uniqueEventIdgtm.startcmdtarget

Network hits(5)

The actual tracking requests your browser sent — the ground-truth proof that a tag fired.

200gtag.jshttps://www.googletagmanager.com/gtag/js?id=AW-807649243

204adshttps://stats.g.doubleclick.net/g/collect?v=2&tid=G-WDQMHG5BXM&cid=1659005359.1786908328&gtm=45be68c1h1v9118120533za200zd9118120533&rcb=6&aip=1&dma=0&gcd=13l3l3

beaconga4-collecthttps://analytics.google.com/g/collect?v=2&tid=G-WDQMHG5BXM&gtm=45be68c1h1v9118120533za200zd9118120533&_p=1786908326532&_gaz=1&gcd=13l3l3l3l1l1&npa=0&dma=0&_eu=

200adshttps://googleads.g.doubleclick.net/pagead/viewthroughconversion/807649243/?random=1786908328414&cv=11&fst=1786908328414&bg=ffffff&guid=ON&async=1&en=gtag.confi

200gtm.jshttps://www.googletagmanager.com/gtm.js?id=GTM-WMBP43B

JavaScript errors (13)

Minified React error #418; visit https://reactjs.org/docs/error-decoder.html?invariant=418 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.

Minified React error #423; visit https://reactjs.org/docs/error-decoder.html?invariant=423 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.

Failed to load resource: net::ERR_FAILED

Refused to connect to 'https://ad.doubleclick.net/ccm/s/collect?auid=448403112.1786908328&gtm=45be68c1h1v9118120533za200zd9118120533xec&fmt=8' because it violates the following Content Security Policy directive: "connect-src 'self' https://api.sendgrid.com https://www.google.com https://www.googleta

Failed to load resource: the server responded with a status of 404 ()

Overall Tracking Health

84out of 100Grade BGood

Tag manager installed20/20

GTM container installed and loading.

GA4 tracking20/20

GA4 is installed and sending data.

Ecommerce funnel coverage20/20

4 of 4 key funnel stages look healthy.

Data quality15/15

No data-quality issues found in tracked events.

Consent Mode0/10

Consent Mode not detected.

Performance4/10

Tag loading is slower than ideal.

No conflicts5/5

No conflicting analytics IDs.

Advanced Tracking Features

Consent Mode v2Warning

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.

default: noupdate: no✗ ad_user_data✗ ad_personalization

Tag PerformanceWarning

Google Tag Manager took 5.3s to load. Slow tag loading delays tracking and can hurt page performance — consider reducing the number of tags or loading them later.

GTM 5.32sGA4 first hit 2.17sDOM ready 0.88sPage load 0.90s

Cross-domain TrackingInfo

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.

Enhanced ConversionsInfo

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.

User-ID TrackingInfo

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.

Checkout & Purchase CoverageWarning

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.

Checks

GTM container detectedPass

GTM-WMBP43B

A Google Tag Manager container is installed on this page.

Container script loads (gtm.js)Pass

1/1 container(s) returned a successful gtm.js response.

The container's JavaScript downloaded successfully, so GTM can run.

Noscript fallback presentPass

Found <noscript> ns.html iframe.

The fallback for visitors with JavaScript disabled is in place.

Snippet placement in <head>Pass

GTM snippet appears inside <head>.

The container is loaded early, as Google recommends, so tags fire as soon as possible.

dataLayer initialised before GTMPass

dataLayer is defined before the container snippet.

Data is available to tags from the very first event.

GA4 firingPass

GA4 — collect hit observed.

Google Analytics 4 is actively sending pageview/event data.

JavaScript errors during loadInfo

13 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 platform detectedInfo

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.

Google Consent Mode v2Warning

No consent API calls observed

Fix this issue

Tag load performanceWarning

GTM 5317ms, GA4 first hit 2173ms, DOMContentLoaded 884ms

Google Tag Manager took 5.3s to load. Slow tag loading delays tracking and can hurt page performance — consider reducing the number of tags or loading them later.

Fix this issue

Cross-domain trackingInfo

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.

Enhanced Conversions (Google Ads)Info

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.

User-ID tracking (GA4)Info

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.

Checkout / purchase coverageWarning

purchase observed=false, checkout page audited=false

Fix this issue

Marketing Funnel Coverage

1 gap to verify0 observed· 10 not auditable on this page

Funnel 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

Product List / Collection Viewhigh

view_item_listMeta: ViewContent

Not observed on this page. Set up 'view_item_list' on your collection/category/search pages for funnel visibility.

Fix this gap

Product Click from Listmedium

select_item

Not observed during this load — 'select_item' requires user interaction on collection/category pages. Verify by manually testing the action on that page.

Consideration

Product Detail Page Viewcritical

view_itemMeta: ViewContent

Not observable on home pages — 'view_item' only fires on product detail pages. Audit that page type to verify coverage.

Cart Activity

Add to Cartcritical

add_to_cartMeta: AddToCart

Not observable on home pages — 'add_to_cart' only fires on product pages and cart. Audit that page type to verify coverage.

Remove from Cartmedium

remove_from_cart

Not observable on home pages — 'remove_from_cart' only fires on cart page. Audit that page type to verify coverage.

Cart / Bag Page Viewhigh

view_cart

Not observable on home pages — 'view_cart' only fires on cart page. Audit that page type to verify coverage.

Checkout Funnel

Begin Checkoutcritical

begin_checkoutMeta: InitiateCheckout

Not observable on home pages — 'begin_checkout' only fires on checkout entry page. Audit that page type to verify coverage.

Shipping Info Enteredhigh

add_shipping_info

Not observable on home pages — 'add_shipping_info' only fires on checkout shipping step. Audit that page type to verify coverage.

Payment Info Enteredhigh

add_payment_infoMeta: AddPaymentInfo

Not observable on home pages — 'add_payment_info' only fires on checkout payment step. Audit that page type to verify coverage.

Purchase / Order Confirmationcritical

purchaseMeta: Purchase

Not observable on home pages — 'purchase' only fires on order confirmation / thank-you page. Audit that page type to verify coverage.

Post-Purchase

Refund / Order Cancellationlow

refund

This event fires server-side (server-side or order management system) and cannot be observed by a browser-based audit.

Report ID: f331089be2

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.

Fix this issue Try PayHelm free

Ask a follow-up question