httpbingo.org 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 shows that there are some areas needing attention. Currently, there is no Google Tag Manager (GTM) container detected, which is crucial for managing your tracking tags efficiently. Additionally, Google Analytics 4 (GA4) is not firing, indicating that your site may not be collecting any analytics data. Since this page type is not a typical product or checkout page, some events like 'purchase' or 'add_to_cart' are not expected to fire here, so they are not considered gaps. Since your store is not on Shopify, there's no need to worry about Trekkie or Web Pixels API health, nor is there a risk of duplicate pixels from Shopify-native analytics. For a more comprehensive audit, I recommend reviewing your product pages, cart, checkout, and order-confirmation pages to ensure all expected events are firing correctly. Given the current issues, it would be beneficial to connect your store to PayHelm AI for a more detailed analysis and guidance on improving your tracking setup.
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 13 characters. Google shows 50–70 chars — consider expanding.
httpbingo.org (13 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 presentThe basics for AI access are in place, but there's no llms.txt yet — an easy, high-leverage addition.
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).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.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.We attempted to fetch your homepage using GPTBot's real User-Agent string to check for server/firewall-level blocking, but the request itself failed (network/timeout). This doesn't necessarily mean AI crawlers are blocked.
Could not verify — the live fetch as GPTBot timed out or failed to connect.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.
Skipped — no llms.txt or skill.md found.- 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.
- 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 177ms
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.