Website Tracking & Analytics Audit
Free SEO + tracking audit — see exactly what's broken in under 60 seconds
Your website's tracking setup has a few areas that need attention. Currently, Google Analytics 4 (GA4) is successfully tracking activity on your homepage, but it's implemented directly via gtag.js rather than through Google Tag Manager (GTM), which is missing. This absence of GTM is flagged as a warning because it limits your flexibility in managing tags and tracking. The Meta Pixel is also firing correctly, which is good for your social media analytics. However, there are no Shopify-native analytics or Trekkie/Web Pixels API detected, which is expected since this isn't a Shopify store. As a next step, consider auditing other key pages like product, cart, checkout, and order-confirmation to ensure comprehensive tracking across your site. Given the current setup issues, I recommend connecting your store to PayHelm AI for a more detailed analysis and guidance.
Tag setup present but not confirmed loading.
GA4 is installed and sending data.
Not an ecommerce store — scored on basic analytics coverage.
No data-quality issues found in tracked events.
Consent Mode v2 configured.
Tags load quickly.
No conflicting analytics IDs.
Consent Mode v2 is configured. 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 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.
3 SEO improvements identified — addressing them could meaningfully boost organic visibility.
Title is only 7 characters. Google shows 50–70 chars — consider expanding.
Appeals (7 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.
Erase poverty, embrace humanityNo 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://tayyabtrust.org/1 Open Graph tag(s) missing. Complete the set for consistent 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 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 35 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, ~363 words) — AI crawlers are not blocked at the server level.
GPTBot's User-Agent received HTTP 200 with ~363 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.
~453 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.
Tags are loaded directly via gtag.js rather than through Tag Manager. That works, but you lose GTM's centralised management, versioning, and conditional firing controls.
Fix this issueG-Z16BGTBDNF — collect hit observed.
Google Analytics 4 is actively sending pageview/event data.
1 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.
default=true, update=true, signals=[ad_storage, ad_user_data, ad_personalization, analytics_storage, wait_for_update]
Consent Mode v2 is configured. The default and update calls and the v2 signals (ad_user_data, ad_personalization) are all present.
GA4 first hit 922ms, DOMContentLoaded 508ms
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.
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.
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.
Meta Pixel script (fbevents.js) found hardcoded directly in the page HTML.
Fix: Remove the hardcoded snippet and use a GTM 'Facebook Pixel' or 'Custom HTML' tag instead.
Risk: If GTM also fires Meta Pixel, you'll double-count conversions and inflate ROAS. Centralising in GTM also lets you pause, version, and conditionally fire without a code deploy.
GA4 gtag.js snippet installed directly in the page HTML (outside GTM).
Fix: Remove the hardcoded GA4 snippet and manage it via a GTM 'Google Analytics: GA4 Configuration' tag.
Risk: Running GA4 both directly and via GTM sends duplicate pageviews and inflates every metric in your reports.
Failed to load resource: the server responded with a status of 404 (Not Found)
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.