Website Tracking & Analytics Audit
Free SEO + tracking audit — see exactly what's broken in under 60 seconds
Your website's tracking setup shows a mix of strengths and areas for improvement. The Shopify infrastructure is robust, with Trekkie and the Web Pixels API functioning correctly, which means your Shopify-native analytics are in good shape. On the homepage, key pixels like TikTok, Meta, Pinterest, and Google Ads fired successfully, ensuring that your marketing efforts are being tracked. However, there is a notable gap with Google Analytics 4 (GA4) not being present or firing, which could limit your insights into user behavior. There are no immediate risks of duplicate pixels, which is good for maintaining clean data. To ensure comprehensive tracking, the next step is to audit product pages, the cart, checkout, and order-confirmation pages to verify that all expected events are firing correctly. Given the current gap with GA4, I recommend connecting your store to PayHelm AI for a more detailed analysis and guidance on optimizing your analytics setup.
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 v2 configured.
Tag load timing not measured.
No conflicting analytics IDs.
Consent Mode v2 is configured via Shopify Customer Privacy. The default and update calls and the v2 signals (ad_user_data, ad_personalization) are all present.
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 appear to be set up — hashed first-party data is being passed to improve conversion accuracy.
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 only 12 characters. Google shows 50–70 chars — consider expanding.
K&R Nail (12 chars)Meta description is 14 characters. Aim for 70–160 chars to maximise click-through rate.
Press on nails (14 chars)One H1 heading found — the recommended structure for every page.
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://knrnail.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 5 linked resources.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, ~274 words) — AI crawlers are not blocked at the server level.
GPTBot's User-Agent received HTTP 200 with ~274 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: WebSite, Organization, BreadcrumbList.Meaningful text content is present in the raw HTML response — AI crawlers that don't execute JavaScript can still read and cite this page.
~2966 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.- 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.
No GTM-XXXX container; gtag.js present instead.
No GTM container detected. This store relies on Shopify Web Pixels and direct gtag.js — a perfectly valid architecture for Shopify. GTM may improve centralised management but is not required.
No GA4 measurement detected.
No Google Analytics 4 tag was detected on this page.
Shop: d43f1c-2.myshopify.com
This is a Shopify store. Pixels can fire from three sources: GTM tags, hardcoded theme code, and Shopify Customer Events (Web Pixels API sandbox). All three are audited here.
Trekkie beacon fired (monorail)
Shopify's built-in Trekkie analytics library is active and sending data to Shopify's own reporting.
Web Pixels API / Shopify.analytics detected — pixels run in a sandboxed iframe
Shopify's Web Pixels API is active. Pixels installed via Shopify Admin → Settings → Customer Events run in a sandboxed iframe, independently of GTM — they cannot interfere with each other, but duplicates are still possible if the same vendor is also in GTM or theme code.
cdn.shopify.com / window.Shopify
This site runs on Shopify. Tracking setup and common pitfalls differ by platform, which is factored into this audit.
default=true, update=true, signals=[ad_storage, ad_user_data, ad_personalization, analytics_storage], CMP=Shopify Customer Privacy
Consent Mode v2 is configured via Shopify Customer Privacy. The default and update calls and the v2 signals (ad_user_data, ad_personalization) are all present.
DOMContentLoaded 2569ms
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.
user_data parameter
Google Ads Enhanced Conversions appear to be set up — hashed first-party data is being passed to improve conversion accuracy.
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 firing, but 'view_item_list' 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_item_list' on your collection/category/search pages for funnel visibility. On Shopify, events may fire via Customer Events (Shopify Web Pixels sandbox) and may not be visible in the dataLayer — verify in Shopify Admin → Settings → Customer Events.
Not observed during this load — 'select_item' requires user interaction on collection/category pages. Verify by manually testing the action on that page. On Shopify, events may fire via Customer Events (Shopify Web Pixels sandbox) and may not be visible in the dataLayer — verify in Shopify Admin → Settings → Customer Events.
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.
The audit automatically visited additional page types discovered on the site to verify tags fire across the full funnel, not just on the entry page.
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.