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://ahmadbodywork.co.uk/index.html

Your website's tracking setup has some critical gaps that need attention. Currently, there is no Google Tag Manager (GTM) container found on your site, which is essential for managing your tracking tags efficiently. Additionally, Google Analytics 4 (GA4) is not present, meaning you're missing out on valuable insights into your site's performance. Since your site is not using Shopify, there's no need to worry about Shopify-specific tracking issues like Trekkie or the Web Pixels API. To ensure comprehensive tracking, I recommend auditing other key pages like product pages, the cart, and checkout to verify that all necessary events are firing correctly. Given the current issues, it would be beneficial to connect your store to PayHelm AI for a more in-depth analysis and to help implement the necessary fixes.

Tracking Health: 27/100 · FSEO Score: 83/100 · BAI SEO Score: 65/100 · C
Overall Tracking Health
27out of 100Grade FPoor
Tag manager installed0/20

No GTM container or gtag.js detected.

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 Mode0/10

Consent Mode not detected.

Performance7/10

Tag load timing not measured.

No conflicts5/5

No conflicting analytics IDs.

Advanced Tracking Features
Consent Mode v2Info

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.

default: noupdate: no✗ ad_user_data✗ ad_personalization
Tag PerformanceInfo

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

DOM ready 0.99sPage load 1.03s
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
83out of 100Grade BGood

3 SEO improvements identified — addressing them could meaningfully boost organic visibility.

Title tagWarning

Title is 73 characters. Google may truncate titles over ~70 chars in search results.

Ahmad Bodywork | Male Massage Therapist in Birmingham & West Midlands (73 chars)
Meta descriptionWarning

Meta description is 189 characters. Google may truncate descriptions over ~160 chars.

Professional deep tissue, relaxing body-to-body, and custom tantric energy massage for men in Birmin… (189 chars)
H1 headingPass

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

Ahmad Bodywork | Male Massage Therapist in Birmingham & West Midlands
Robots / indexabilityPass

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

robots: index, follow
Canonical URLWarning

Canonical tag points to a different URL. Verify this is intentional (cross-domain canonical or redirect chain).

https://ahmadbodywork.co.uk/
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)Pass

Structured data found — search engines can use it to generate rich results (star ratings, FAQs, products, breadcrumbs, etc.).

JSON-LD script 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
65out of 100Grade CFair

The basics for AI access are in place, but there's no llms.txt yet — an easy, high-leverage addition.

llms.txt fileWarning

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).
AI crawler access (robots.txt)Info

No robots.txt file at all. AI crawlers are implicitly allowed, but you also have no way to signal crawl preferences (e.g. rate limits) to them.

No robots.txt found — all crawlers implicitly allowed.
Live AI crawler testPass

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

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

Structured data (JSON-LD) is present with types AI answer engines commonly extract facts from (e.g. FAQPage, Product, Organization).

Schema.org types found: FAQPage.
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.

~1039 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 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.
  • 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 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 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 v2Info

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.

Tag load performanceInfo

DOMContentLoaded 991ms

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 ()

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

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