fig-exclusive-accessory-seriously.trycloudflare.com Tracking & SEO Audit — Grade F
A saved report based on tracking and pages observed during this scan.
The audit of your website's tracking setup indicates a few areas that need attention. Currently, there is no Google Tag Manager (GTM) container found, which is essential for managing your tracking tags efficiently. Additionally, Google Analytics 4 (GA4) is not present or firing on this page, meaning you're not capturing any analytics data here. Since this page type is categorized as "other," it's expected that certain events like 'purchase' or 'add_to_cart' wouldn't fire, so those are not concerns at this point. However, the absence of Shopify-native analytics and Trekkie/Web Pixels API suggests that no Shopify tracking is in place, which could lead to data gaps if not addressed. To ensure comprehensive tracking, the next step is to audit product pages, cart, checkout, and order-confirmation pages. Given the current issues, I recommend connecting your store to PayHelm AI for a more thorough analysis and guidance on setting up your tracking infrastructure correctly.
No GTM container or gtag.js detected.
No GA4 measurement detected.
Not an ecommerce store — scored on basic analytics coverage.
No data-quality issues found in tracked events.
Consent Mode not detected.
Tag load timing not measured.
No conflicting analytics IDs.
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.
No tag load timing was captured (the container may not have loaded, or timing was unavailable).
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 15 characters. Google shows 50–70 chars — consider expanding.
169.254.169.254 (15 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.
This site can’t be reachedNo noindex directive — the page is eligible to be indexed.
No robots meta tag (defaults to index, follow).No canonical tag found. Adding one prevents duplicate-content issues when a page is accessible via multiple URLs.
No canonical link tag found.No Open Graph tags found. Add og:title, og:description, and og:image for rich 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 presentBlocked: AI crawlers are actually refused at the server level (HTTP 403) when they try to fetch this site.
llms.txt exists but doesn't follow the standard format. Use a top-level heading plus markdown links to your most important pages.
Found at /llms.txt but missing the expected structure (a top-level # heading and markdown links).skill.md exists but doesn't start with a clear top-level heading describing the site/capability.
Found at /skill.md but missing a top-level # heading.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.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.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.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.
~53 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.There were no outbound links in llms.txt or skill.md to check for hallucinated endpoints or domains.
No links found to verify.- Reformat llms.txt to follow the standard: a top-level `# Site Name` heading, a one-line summary, then markdown links (`[Page](url): description`) to your key pages.
- 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 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 issueNo GA4 measurement detected.
No Google Analytics 4 tag was detected on this page.
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.
DOMContentLoaded 280ms
No tag load timing was captured (the container may not have loaded, or timing was unavailable).
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.
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.