Website Tracking & Analytics Audit
PayHelm

Website Tracking & Analytics Audit

Free SEO + tracking audit — see exactly what's broken in under 60 seconds

Full GTM config is private — this reports the observed runtime container (what actually loads & fires). We'll email your report to the address above.

Works, with issueshttps://nopobs.com/

The audit of your website's home page indicates some areas needing attention. Currently, there is no Google Tag Manager (GTM) container set up, and Google Analytics 4 (GA4) is not firing, which means you're not capturing essential visitor data. Additionally, Shopify's native analytics and Trekkie/Web Pixels API are not detected, which could impact your ability to track customer interactions effectively. There are also some console errors that need to be addressed to ensure smooth site performance. For your next steps, I recommend auditing other critical pages such as product pages, the cart, checkout, and order-confirmation pages to ensure all necessary tracking is in place. Given the current gaps, it would be beneficial to connect your store to PayHelm AI for a more comprehensive analytics solution.

Tracking Health: 49/100 · FSEO Score: 90/100 · AAI SEO Score: 75/100 · B
Overall Tracking Health
49out of 100Grade FPoor
Tag manager installed12/20

Tag setup present but not confirmed loading.

GA4 tracking0/20

No GA4 measurement detected.

Pageview / event coverage0/20

Not an ecommerce store — scored on basic analytics coverage.

Data quality15/15

No data-quality issues found in tracked events.

Consent Mode10/10

Consent Mode v2 configured.

Performance7/10

Tag load timing not measured.

No conflicts5/5

No conflicting analytics IDs.

Advanced Tracking Features
Consent Mode v2Pass

Consent Mode v2 is configured. The default and update calls and the v2 signals (ad_user_data, ad_personalization) are all present.

default: yesupdate: yes✓ ad_storage✓ ad_user_data✓ ad_personalization✓ analytics_storage✓ wait_for_update
Tag PerformanceInfo

No tag load timing was captured (the container may not have loaded, or timing was unavailable).

DOM ready 0.59sPage load 0.86s
Cross-domain TrackingInfo

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.

Enhanced ConversionsInfo

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.

User-ID TrackingInfo

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.

SEO Review
90out of 100Grade AExcellent

SEO basics are mostly in place with a few opportunities to improve.

Title tagPass

Title is 42 characters — within the ideal 30–70 character range.

No Pobs: Blinds and Shutters for Your Home (42 chars)
Meta descriptionPass

Meta description is 143 characters — within the ideal 70–160 character range.

Explore No Pobs for premium blinds and shutters, enhancing your home with stylish interior window co… (143 chars)
H1 headingPass

One H1 heading found — the recommended structure for every page.

Need blinds or shutters? NO POBS!
Robots / indexabilityPass

No noindex directive — the page is eligible to be indexed.

No robots meta tag (defaults to index, follow).
Canonical URLPass

Canonical tag points to the page itself — no duplicate-content signals sent to search engines.

https://nopobs.com/
Open Graph tagsPass

All core Open Graph tags found — links display richly when shared on social media.

og:title ✓ og:description ✓ og:image ✓
Structured data (Schema.org)Info

No structured data found. Adding Schema.org markup can unlock rich snippets and improve your search appearance.

No structured data found.
Mobile viewportPass

Viewport meta tag found — the page is set up for mobile-friendly rendering.

viewport meta tag present
AI Discovery & AI SEOOpen to AI
75out of 100Grade BGood

2 AI discoverability gaps found — closing them improves your odds of being cited by ChatGPT, Claude, Perplexity, and Google AI Overviews.

llms.txt filePass

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 1 linked resource.
AI crawler access (robots.txt)Pass

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.
Live AI crawler testPass

GPTBot's User-Agent successfully fetched the real page (HTTP 200, ~11053 words) — AI crawlers are not blocked at the server level.

GPTBot's User-Agent received HTTP 200 with ~11053 words of visible text.
Structured data for AI answersWarning

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.
Server-rendered contentPass

Meaningful text content is present in the raw HTML response — AI crawlers that don't execute JavaScript can still read and cite this page.

~630 words of text visible in the raw HTML response.
XML sitemapWarning

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.
AI crawlers
GPTBotOAI-SearchBotChatGPT-UserClaudeBotClaude-Webanthropic-aiPerplexityBotPerplexity-UserGoogle-ExtendedApplebot-ExtendedBytespiderCCBotAmazonbotcohere-aiMeta-ExternalAgent
Opportunities
  • 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 container was detected on this page.
Checks
GTM containerWarning

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 issue
GA4 firingInfo

No GA4 measurement detected.

No Google Analytics 4 tag was detected on this page.

JavaScript errors during loadInfo

2 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.

Google Consent Mode v2Pass

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.

Tag load performanceInfo

DOMContentLoaded 594ms

No tag load timing was captured (the container may not have loaded, or timing was unavailable).

Cross-domain trackingInfo

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.

Enhanced Conversions (Google Ads)Info

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.

User-ID tracking (GA4)Info

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.

JavaScript errors (2)

Failed to load resource: the server responded with a status of 404 (Not Found)

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.

Ask a follow-up question