Website Tracking & Analytics Audit
Free SEO + tracking audit — see exactly what's broken in under 60 seconds
Your website's tracking infrastructure has some areas that need attention. Google Analytics 4 (GA4) is set up correctly and fired as expected on your homepage, but Shopify's native analytics tool, Trekkie, did not send any data, which is a concern. Additionally, multiple pixels, including Meta, TikTok, and Pinterest, fired successfully, indicating that your marketing tracking is generally functioning well. However, the absence of Trekkie data could lead to incomplete analytics insights, and it's important to ensure that Shopify's Web Pixels API is not causing any duplicate pixel issues. For a comprehensive understanding of your site's tracking, I recommend auditing other key pages like product, cart, checkout, and order-confirmation pages. Given the current issues, consider connecting your store to PayHelm AI for more detailed analytics support and troubleshooting.
Tag setup present but not confirmed 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 v2 configured.
Tags load quickly.
No conflicting analytics IDs.
Consent Mode v2 is configured via Cookiebot. The default and update calls and the v2 signals (ad_user_data, ad_personalization) are all present.
Tags loaded quickly — no performance concern.
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 56 characters — within the ideal 30–70 character range.
Women’s Clothing for Every Occasion – Just Darviny (56 chars)Meta description is 224 characters. Google may truncate descriptions over ~160 chars.
Discover Just Darviny women’s clothing featuring original artwork, travel-inspired prints and timele… (224 chars)One H1 heading found — the recommended structure for every page.
Just DarvinyNo 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://justdarviny.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.).
Microdata (itemscope) foundViewport meta tag found — the page is set up for mobile-friendly rendering.
viewport meta tag present2 AI discoverability gaps found — closing them improves your odds of being cited by ChatGPT, Claude, Perplexity, and Google AI Overviews.
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, ~2391 words) — AI crawlers are not blocked at the server level.
GPTBot's User-Agent received HTTP 200 with ~2391 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.
~1171 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.- 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.
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.
G-V8D2C2V106 — collect hit observed.
Google Analytics 4 is actively sending pageview/event data.
14 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.
Shop: just-darviny.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 loaded but no monorail beacon observed
Trekkie is present but no network beacon was observed — it may be blocked, gated behind consent, or misconfigured.
Fix this issueWeb 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=Cookiebot
Consent Mode v2 is configured via Cookiebot. The default and update calls and the v2 signals (ad_user_data, ad_personalization) are all present.
GA4 first hit 7692ms, DOMContentLoaded 2969ms
Tags loaded quickly — no performance concern.
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.
Multiple import maps are not yet supported. https://crbug.com/927119
Multiple import maps are not yet supported. https://crbug.com/927119
Clear-Site-Data header on 'https://justdarviny.com/cart/update.js': Unrecognized type: "prefetchCache".
Clear-Site-Data header on 'https://justdarviny.com/cart/update.js': Unrecognized type: "prerenderCache".
Clear-Site-Data header on 'https://justdarviny.com/cart/update.js': No recognized types specified.
Clear-Site-Data header on 'https://justdarviny.com/cart/update.js': Unrecognized type: "prefetchCache".
Clear-Site-Data header on 'https://justdarviny.com/cart/update.js': Unrecognized type: "prerenderCache".
Clear-Site-Data header on 'https://justdarviny.com/cart/update.js': No recognized types specified.
Access to XMLHttpRequest at 'https://a.klaviyo.com/onsite/track-analytics?company_id=RzLTWn' from origin 'https://justdarviny.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Failed to load resource: net::ERR_FAILED
Access to XMLHttpRequest at 'https://a.klaviyo.com/onsite/track-analytics?company_id=RzLTWn' from origin 'https://justdarviny.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Failed to load resource: net::ERR_FAILED
Access to XMLHttpRequest at 'https://a.klaviyo.com/onsite/track-analytics?company_id=RzLTWn' from origin 'https://justdarviny.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Failed to load resource: net::ERR_FAILED
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.