pass1.1
AI search crawler access
7/7 ptsAI search and assistant bots are allowed to read your site.
Training bots: GPTBot: allowed, ClaudeBot: allowed, Google-Extended: allowed, CCBot: allowed. Blocking these is a valid choice and doesn't affect this score.
Evidence
https://www.gitguardian.com/robots.txt · HTTP 200 · blocked from /: none; blocked on key paths: none
pass1.2
Homepage access
7/7 ptsYour homepage lets in requests that identify as ChatGPT, Claude and Perplexity, and serves them the same page as a browser.
Evidence
https://www.gitguardian.com/ · as browser · HTTP 200 · browser baseline 200
https://www.gitguardian.com/ · as ChatGPT-User · HTTP 200 · HTTP 200
https://www.gitguardian.com/ · as Claude-User · HTTP 200 · HTTP 200
https://www.gitguardian.com/ · as Perplexity-User · HTTP 200 · HTTP 200
pass1.3
Content without JavaScript
7/7 ptsYour pages carry real text in the page code (762 words on the homepage, 1017 on a typical key page).
Evidence
https://www.gitguardian.com/ · homepage: pass (762 words) · key pages: pass (median 1017 words across 5)
https://www.gitguardian.com/ · 762 words of page content in raw HTML (924 including nav and footer)
sampled pages: product /platform (1017 words), customer /legal/client-partner-prospect-privacy-notice (2742 words), blog /resources/what-to-do-if-you-expose-a-secret (116 words), about /about-us (376 words), product /solutions/git-secret (1713 words); median words: 1017
pass1.4
Accidentally hidden pages
4/4 ptsNone of your key pages are hidden from search and AI.
Evidence
checked homepage + 5 key pages
fail1.5
Page essentials
0/3 pts6 of 6 pages we checked are missing a description / main heading / canonical.
How to fix: Give every key page a unique title, a one-sentence description, one main heading and a canonical URL.
Evidence
https://www.gitguardian.com/ · title:true desc:true h1:1 canonical:false
https://www.gitguardian.com/platform · title:true desc:true h1:1 canonical:false
https://www.gitguardian.com/legal/client-partner-prospect-privacy-notice · title:true desc:false h1:2 canonical:false
https://www.gitguardian.com/resources/what-to-do-if-you-expose-a-secret · title:true desc:false h1:2 canonical:false
https://www.gitguardian.com/about-us · title:true desc:true h1:2 canonical:false
https://www.gitguardian.com/solutions/git-secret · title:true desc:true h1:4 canonical:false
fail1.6
Company identity
0/3 ptsYour site doesn't identify the company in structured data.
How to fix: Add Organization structured data (name, URL, logo, official profiles) to your homepage.
Evidence
https://www.gitguardian.com/ · 0 JSON-LD blocks, no Organization with a name
pass1.7
Sitemap
2/2 ptsYour sitemap is valid, linked and up to date.
Evidence
https://www.gitguardian.com/sitemap.xml · valid:true linkedFromRobots:true urls:1116 latestLastmod:2026-10-15T05:08:35.679Z
pass1.8
Response speed
2/2 ptsYour homepage responds quickly (43 ms, median of 5 requests).
Evidence
https://gitguardian.com/ · median 43 ms across 5 requests
https://gitguardian.com/ · as crawler · HTTP 200 · 343 ms to response headers
https://www.gitguardian.com/ · as browser · HTTP 200 · 34 ms to response headers
https://www.gitguardian.com/ · as ChatGPT-User · HTTP 200 · 40 ms to response headers
https://www.gitguardian.com/ · as Claude-User · HTTP 200 · 43 ms to response headers
https://www.gitguardian.com/ · as Perplexity-User · HTTP 200 · 49 ms to response headers
bonus1.9
AI guide files
+0 bonusOpportunity: an llms.txt file and markdown page versions give AI agents a clean map of your site. Not yet confirmed as used by the major AI engines, but cheap to add.
Evidence
https://www.gitguardian.com/llms.txt · HTTP 404 · no valid llms.txt
no <link rel="alternate" type="text/markdown">