Website Tracking & Analytics Audit

caminorealplayhouse.org Tracking & SEO Audit — Grade F

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

Works, with issueshttps://caminorealplayhouse.org/

Read the full audit summary

The audit of your website's home page indicates that while Google Analytics 4 (GA4) is set up, it did not successfully fire any tracking events, which is a concern for capturing visitor data. The absence of a Google Tag Manager (GTM) container is noted, with direct gtag.js being used instead, which may limit flexibility in managing tags. There are no Shopify-native analytics or Trekkie/Web Pixels API detected, which is expected since your site is not on Shopify. No duplicate pixel risk is present. For a comprehensive understanding of your analytics setup, the next step should be to audit other key pages like product, cart, checkout, and order-confirmation pages. Given the issues identified, I recommend connecting your store to PayHelm AI for a more detailed analysis and solutions.

What to look at first

Priorities below are taken directly from findings in this report.

SEO Review

86out of 100Grade BGood

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

Title tagPass

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

Landing - Camino Real Playhouse (31 chars)

Meta descriptionWarning

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

Now Playing · 2026 – 2027 Season Camino Real Playhouse · Live Theatre GET TICKETS Season P… (191 chars)

H1 headingPass

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

Events

Robots / indexabilityPass

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

robots: index, max-snippet:-1, max-image-preview:large, max-video-preview:-1, follow

Canonical URLPass

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

https://caminorealplayhouse.org/

Open Graph tagsWarning

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

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

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: Organization.

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.

~1144 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

GPTBot ✓OAI-SearchBot ✓ChatGPT-User ✓ClaudeBot ✓Claude-Web ✓anthropic-ai ✓PerplexityBot ✓Perplexity-User ✓Google-Extended ✓Applebot-Extended ✓Bytespider ✓CCBot ✓Amazonbot ✓cohere-ai ✓Meta-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.

Overall Tracking Health

59out of 100Grade FPoor

Tag manager installed12/20

Tag setup present but not confirmed loading.

GA4 tracking10/20

GA4 configured but no hits observed (may be consent-gated).

Pageview / event coverage10/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 1.13sPage load 1.60s

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.

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 firingWarning

G-SMB3X2NFHM — no /g/collect hit observed.

GA4 is configured but we did not see it send data on this page — it may be gated behind cookie consent or misconfigured.

Fix this issue

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 1128ms

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.

On-page Scripts — Should Be in GTM (1)

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.

Google Analytics 4 (direct gtag.js)

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.

Report ID: f4e5dd967a

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