Website Tracking & Analytics Audit

interstate-sitting-soil-direct.trycloudflare.com Tracking & SEO Audit — Grade F

A saved report based on tracking and pages observed during this scan.

Works, with issueshttps://interstate-sitting-soil-direct.trycloudflare.com/xss.html

Your website's tracking setup needs attention. Currently, there's no Google Tag Manager (GTM) container detected, which is crucial for managing your site's tracking tags efficiently. Additionally, Google Analytics 4 (GA4) is not firing, which means you're missing out on valuable insights into visitor behavior. Since this page type doesn't typically trigger purchase-related events, there are no missing events to worry about here. However, for Shopify stores, it's important to note that Trekkie and the Web Pixels API are not present, which could lead to incomplete analytics data. Next, I recommend auditing other key pages like product, cart, checkout, and order-confirmation to ensure comprehensive tracking. Given these issues, consider connecting your store to PayHelm AI for expert guidance on optimizing your analytics setup.

Tracking Health: 27/100 · FSEO Score: 41/100 · FAI SEO Score: 0/100 · F

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.30sPage load 0.66s

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

41out of 100Grade FPoor

1 critical SEO issue detected — fix these to avoid being excluded from search results.

Title tagFail

The page has no title tag — a critical SEO issue. Every page needs a unique, descriptive title.

No <title> tag found.

Meta descriptionWarning

Meta description is 42 characters. Aim for 70–160 chars to maximise click-through rate.

</script><svg/onload=window.__XSS_FIRED=2> (42 chars)

H1 headingPass

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

Robots / indexabilityPass

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

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

Canonical URLWarning

No canonical tag found. Adding one prevents duplicate-content issues when a page is accessible via multiple URLs.

No canonical link tag found.

Open Graph tagsWarning

2 Open Graph tag(s) missing. Complete the set for consistent social link previews.

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 viewportWarning

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.

AI Discovery & AI SEOBlocked for AI

0out of 100Grade FPoor

Blocked: AI crawlers are actually refused at the server level (HTTP 403) when they try to fetch this site.

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

skill.md fileInfo

No skill.md file found. This is an emerging convention for describing agent-callable capabilities/tools to AI agents — optional today, but worth watching as adoption grows.

No /skill.md or /.well-known/skill.md found.

AI crawler access (robots.txt)Fail

robots.txt blocks every major AI crawler. Your content cannot be cited by ChatGPT, Claude, Perplexity, or Google AI Overviews — verify this is intentional.

15 of 15 AI crawlers blocked: GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, Claude-Web, anthropic-ai, PerplexityBot, Perplexity-User, Google-Extended, Applebot-Extended, Bytespider, CCBot, Amazonbot, cohere-ai, Meta-ExternalAgent.

Live AI crawler testFail

We fetched your homepage using GPTBot's real User-Agent and it was refused (HTTP 403). This is a server/firewall-level block — AI crawlers cannot read this site at all, regardless of what robots.txt says.

GPTBot's User-Agent received HTTP 403.

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 contentWarning

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.

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

llms.txt / skill.md link integrityInfo

There were no outbound links in llms.txt or skill.md to check for hallucinated endpoints or domains.

Skipped — no llms.txt or skill.md found.

AI crawlers

GPTBot blockedOAI-SearchBot blockedChatGPT-User blockedClaudeBot blockedClaude-Web blockedanthropic-ai blockedPerplexityBot blockedPerplexity-User blockedGoogle-Extended blockedApplebot-Extended blockedBytespider blockedCCBot blockedAmazonbot blockedcohere-ai blockedMeta-ExternalAgent blocked

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.
Unblock GPTBot, OAI-SearchBot, ChatGPT-User, … 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.
AI crawlers get blocked at the server level (HTTP 403) when fetching your homepage, even though this may not show up in robots.txt. Check your WAF/CDN's bot-management rules for a User-Agent block on AI 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 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 296ms

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

Report ID: 01887a5dbd

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.

Fix this issue Try PayHelm free

Ask a follow-up question