Website Tracking & Analytics Audit
Free SEO + tracking audit — see exactly what's broken in under 60 seconds
Results may be unreliable — bot protection blocked this audit
Cloudflare served our checker a CAPTCHA/challenge page instead of your real homepage. Every finding below reflects that challenge page — not your actual site. Consider allowlisting our checker's traffic or running the audit again.
The audit of your website's home page revealed several critical issues with your tracking infrastructure. Google Tag Manager (GTM) is set up but failed to load correctly, which means no tracking tags were fired. Additionally, Google Analytics 4 (GA4) and Universal Analytics are not present, indicating a lack of essential tracking capabilities. There are also no Shopify-native analytics or Trekkie/Web Pixels API detected, which are crucial for Shopify stores to track user interactions effectively. The audit identified a significant gap in tracking the 'view_item_list' event, which should have been observed on this page. Furthermore, the presence of JavaScript errors and a Cloudflare bot protection challenge suggests potential technical barriers that need addressing. Given these issues, I recommend connecting your store to PayHelm AI for a comprehensive analysis and guidance on resolving these tracking gaps. Next, consider auditing your product, cart, checkout, and order-confirmation pages to ensure complete tracking coverage across your site.
Tag setup present but not confirmed loading.
No GA4 measurement detected.
4 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 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 basics are mostly in place with a few opportunities to improve.
Title is 64 characters — within the ideal 30–70 character range.
Wholesale Industrial Parts | Pipes, Valves & Fittings | Get Pipe (64 chars)Meta description is 158 characters — within the ideal 70–160 character range.
Shop wholesale industrial parts, including pipes, valves, flanges, and more. Get Pipe provides fast … (158 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.
No robots meta tag (defaults to index, follow).Canonical tag points to the page itself — no duplicate-content signals sent to search engines.
https://getpipe.com/No Open Graph tags found. Add og:title, og:description, and og:image for rich social link previews.
og:title ✗ og:description ✗ og:image ✗No structured data found. Adding Schema.org markup can unlock rich snippets and improve your search appearance.
No structured data found.Viewport meta tag found — the page is set up for mobile-friendly rendering.
viewport meta tag present3 AI discoverability gaps found — closing them improves your odds of being cited by ChatGPT, Claude, Perplexity, and Google AI Overviews.
llms.txt exists but doesn't follow the standard format. Use a top-level heading plus markdown links to your most important pages.
Found at /llms.txt but missing the expected structure (a top-level # heading and markdown links).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, ~1260 words) — AI crawlers are not blocked at the server level.
GPTBot's User-Agent received HTTP 200 with ~1260 words of visible text.No structured data found. AI answer engines lean heavily on Schema.org markup (FAQPage, Product, Organization) to extract clean facts instead of parsing raw HTML.
No JSON-LD structured data found.Meaningful text content is present in the raw HTML response — AI crawlers that don't execute JavaScript can still read and cite this page.
~29654 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.- Reformat llms.txt to follow the standard: a top-level `# Site Name` heading, a one-line summary, then markdown links (`[Page](url): description`) to your key pages.
- Add JSON-LD structured data (Organization + FAQPage at minimum) so AI assistants can extract accurate facts about your business instead of guessing from page text.
- 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.
BigCommerce markup in HTML
No tags were observed sending data. They may be gated behind cookie consent, or none are configured.
— none observed —
Every dataLayer push observed during page load — with full payload and configuration analysis.
— no dataLayer events captured —
Data points present in the dataLayer that your tags can read (the values pushed alongside each event).
— no dataLayer variables captured —
The actual tracking requests your browser sent — the ground-truth proof that a tag fired.
— no tracking requests observed —
Cloudflare challenge page detected ("Just a moment...") instead of the real site.
This site's bot/CAPTCHA protection (Cloudflare) served a challenge page to our automated check instead of your real homepage. Every result below reflects that challenge page, not your actual site — treat this audit as unreliable and consider allowlisting our checker or re-running later.
Fix this issueGTM-MHGMDMMV
A Google Tag Manager container is installed on this page.
0/1 container(s) returned a successful gtm.js response.
The container script did not load (blocked, unpublished, or wrong ID), so no tags will fire.
Fix this issueNo <noscript> fallback found in the HTML source.
The recommended <noscript> fallback is missing. It's minor, but Google's standard install includes it.
Fix this issueGTM 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.
No GA4 measurement detected.
No Google Analytics 4 tag was detected on this page.
5 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.
BigCommerce markup in HTML
This site runs on BigCommerce. 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 157ms
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.
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.
Microsoft Advertising UET tag hardcoded in the page HTML.
Fix: Use GTM's built-in 'Microsoft Advertising UET' tag type.
Risk: GTM's native UET integration auto-fires standard events; hardcoded UET misses them.
Failed to load resource: the server responded with a status of 403 ()
Failed to load resource: the server responded with a status of 404 ()
Failed to load resource: the server responded with a status of 404 ()
%c%d font-size:0;color:transparent NaN
%c%d font-size:0;color:transparent NaN
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.