Website Tracking & Analytics Audit
Free SEO + tracking audit — see exactly what's broken in under 60 seconds
The audit of your website's tracking setup shows that there are some areas needing attention. Notably, there is no Google Tag Manager (GTM) container found on the page, which is crucial for managing your tracking tags efficiently. Additionally, Google Analytics 4 (GA4) is not configured or firing, which means you're missing out on valuable insights into your website's performance. Since this page type is not a product, cart, or checkout page, certain events like 'purchase' or 'add_to_cart' are not expected to fire here, so their absence is not a concern. For Shopify stores, it's important to note that no Shopify-native analytics, Trekkie, or Web Pixels API were detected, which could lead to a lack of data collection and potential duplicate pixel risks if not addressed. To ensure comprehensive tracking, I recommend auditing your product pages, cart, checkout, and order-confirmation pages next. Given the current issues, consider connecting your store to PayHelm AI for a more detailed analysis and guidance on optimizing your analytics setup.
No GTM container or gtag.js detected.
No GA4 measurement detected.
Not an ecommerce store — scored on basic analytics coverage.
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.
1 critical SEO issue detected — fix these to avoid being excluded from search results.
Title is only 5 characters. Google shows 50–70 chars — consider expanding.
Error (5 chars)No meta description. While not a direct ranking factor, a good description significantly improves click-through from search results.
No meta description found.One H1 heading found — the recommended structure for every page.
Sorry, something went wrong.The page has a noindex directive — search engines will NOT index this page. Remove it if the page should appear in search results.
robots: noindex,nofollowNo canonical tag found. Adding one prevents duplicate-content issues when a page is accessible via multiple URLs.
No canonical link tag found.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.No viewport meta tag. Google uses mobile-first indexing — without a viewport tag the page may be penalised for poor mobile UX.
No viewport meta tag found.6 AI discoverability gaps found — closing them improves your odds of being cited by ChatGPT, Claude, Perplexity, and Google AI Overviews.
No llms.txt file found. This is a plain-text, markdown-style index of your key pages that AI assistants (ChatGPT, Claude, Perplexity) increasingly check to understand a site quickly.
No /llms.txt found (404 or empty).robots.txt blocks some AI crawlers (OAI-SearchBot, ChatGPT-User, Claude-Web, anthropic-ai, Perplexity-User, Bytespider, CCBot, cohere-ai, Meta-ExternalAgent) while allowing others. Review whether the blocks are intentional.
9 of 15 AI crawlers blocked: OAI-SearchBot, ChatGPT-User, Claude-Web, anthropic-ai, Perplexity-User, Bytespider, CCBot, cohere-ai, Meta-ExternalAgent.GPTBot's User-Agent was let through (HTTP 200) but received a near-empty page (~72 words) — possibly a lighter/JS-only response served specifically to crawlers.
GPTBot's User-Agent received HTTP 200 with ~72 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.Very little text is present in the raw HTML — this page likely relies on client-side JavaScript to render content. Most AI crawlers (GPTBot, ClaudeBot, PerplexityBot) don't execute JavaScript, so they may see a near-empty page.
~22 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 an /llms.txt file listing your most important pages (pricing, docs, product pages) in markdown format — it gives AI assistants a fast, reliable summary of your site instead of guessing from crawled HTML.
- Unblock OAI-SearchBot, ChatGPT-User, Claude-Web, … in robots.txt if you want your content surfaced in AI answers — each blocked bot means that assistant can't read or cite your pages.
- GPTBot can reach your server, but the response it gets back is nearly empty — check for User-Agent-based content rules serving a stripped-down page to crawlers.
- 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.
- Server-render (or pre-render) key page content — most AI crawlers don't run JavaScript, so client-side-only rendering makes your content invisible to them even though it looks fine in a browser.
- 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 container found.
No Google Tag Manager container was found on this page. If you rely on GTM for analytics and ads tags, nothing will fire.
Fix this issueNo GA4 measurement detected.
No Google Analytics 4 tag was detected on this page.
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 334ms
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.
Ecommerce Funnel — Not Applicable
This site doesn't appear to be an online store, so the ecommerce funnel report has been skipped. GTM tag coverage, triggers, variables, and on-page scripts are still audited above.
If this site does sell products, try re-running the audit on a product page URL — that will surface add-to-cart, checkout, and purchase event coverage.
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.