scanned Apr 20, 2026

GeoDaddy

geodaddy.dev

GeoDaddy analyzes website visibility to AI search engines and provides scored reports with specific fixes.

/100

Content answers—

Protocol plumbing—

Scored by asking 15 questions a buyer of a ai-ml product asks, then grading this site’s own pages: answered, hedged (partial or vague), or silent (no page answers it). How scoring works

15 buyer questions · graded against the site’s own pages

1 of 15 come back answered. 3 get a hedge. 11 meet silence.

1 answerable3 half-answers11 silent

Goes silent · limits · high importance

We're building a CI pipeline that triggers audits on every deploy — what's the burst rate limit on API calls, and do you offer dedicated throughput for teams?

Goes silent · pricing · high importance

I'm running audits for a few side projects — how many pages can I scan per month on the free plan before hitting a hard stop?

This report is public. Own geodaddy.dev? Claiming is free: crawl every page, re-audit as you fix, and track your score over time.

The fix queue

14 open questions, ordered by estimated payoff.

Point estimates are per fix under scoring v2. They are not additive to a promised total.

01limits · importance highGoes silent+7 content pts est.

We're building a CI pipeline that triggers audits on every deploy — what's the burst rate limit on API calls, and do you offer dedicated throughput for teams?

What the pages say

No page on the site addresses this.

The fix

Create a dedicated API reference page that documents rate limits, burst thresholds, and enterprise/dedicated throughput options. The current docs only cover CLI installation, checks reference, and MCP server—no API limits or pricing tiers are mentioned.

confidence high · Absent

02pricing · importance highGoes silent+7 content pts est.

I'm running audits for a few side projects — how many pages can I scan per month on the free plan before hitting a hard stop?

What the pages say

No page on the site addresses this.

The fix

Create a dedicated pricing page that specifies free plan limits, including monthly page scan quotas and what happens when limits are reached (hard stop vs. throttling).

confidence high · Page missing

03integration · importance mediumGoes silent+7 content pts est.

I need to pipe audit results into our internal dashboard — what's the exact JSON schema for webhook payloads? Do you include raw LLM-readable content samples or just scores?

What the pages say

No page on the site addresses this.

The fix

Create a dedicated webhooks documentation page with complete JSON schema definitions, example payloads, and clarification on whether raw LLM-readable content samples or only scores are included.

confidence high · Absent

04operations · importance mediumGoes silent+7 content pts est.

If I run weekly audits for compliance tracking, how long do you keep historical reports accessible? Can I export trend data or do reports expire?

What the pages say

No page on the site addresses this.

The fix

Create documentation covering report retention policies, historical data access, and export capabilities for compliance workflows. Consider adding a 'Data Retention' or 'Compliance' section to the docs.

confidence high · Absent

05technical · importance mediumGoes silent+7 content pts est.

My site uses dynamic robots.txt based on request headers — does your crawler respect that or does it only fetch the static file? What about crawl-delay directives for AI bots specifically?

What the pages say

No page on the site addresses this.

The fix

Create documentation explaining how the crawler handles dynamic robots.txt (request headers, user-agent detection) and whether it respects crawl-delay directives for AI bots like GPTBot, ClaudeBot, and PerplexityBot.

confidence high · Absent

06content-quality · importance mediumGoes silent+7 content pts est.

You flag 'insufficient entity coverage' in my reports — what's the actual threshold where you consider coverage adequate, and does it vary by content type (product page vs. blog post)?

What the pages say

No page on the site addresses this.

The fix

The 'Checks Reference' documentation page at /docs/docs/checks is referenced but not retrieved; it likely contains the specific threshold definitions for 'insufficient entity coverage' and whether they vary by content type. Ensure this page is crawlable and its content is fully expanded.

confidence high · Page missing

07content-quality · importance lowGoes silent+7 content pts est.

If the same entity appears in both my Schema.org markup and natural language text, does that boost my score or get flagged as redundant? What's your deduplication logic?

What the pages say

No page on the site addresses this.

The fix

Create documentation explaining how GeoDaddy handles Schema.org entities that appear in both structured data and natural language text, including whether this boosts scores or triggers deduplication penalties.

confidence high · Absent

08migration · importance lowGoes silent+7 content pts est.

We're migrating from Clearscope — can I bulk import my existing content briefs and keyword-entity mappings, or do I need to rebuild everything in your format?

What the pages say

No page on the site addresses this.

The fix

Create a dedicated migration guide page that addresses importing from competitor tools like Clearscope, including supported import formats (CSV, JSON, API), mapping of content brief fields, and keyword-entity data migration.

confidence high · Absent

09operations · importance lowGoes silent+7 content pts est.

We're scheduling audits for a launch window — is there an SLA uptime guarantee for the API, and what's your historical availability? Do you publish status page data?

What the pages say

No page on the site addresses this.

The fix

Create a dedicated status/operations page with SLA uptime guarantees, historical availability metrics, and a link to a public status page. Consider adding this to the docs navigation.

confidence high · Absent

10technical · importance lowGoes silent+7 content pts est.

Your report says 'critical CSS blocked from AI crawlers' — but I have GPTBot allowed in robots.txt. How do you distinguish between 'blocked' and 'not fetched due to crawl budget' in your diagnostics?

What the pages say

No page on the site addresses this.

The fix

Create documentation explaining how GeoDaddy distinguishes between robots.txt blocking vs. crawl budget limitations for AI crawlers, specifically addressing how 'critical CSS blocked from AI crawlers' is diagnosed when GPTBot is allowed in robots.txt.

confidence high · Absent

11technical · importance lowGoes silent+7 content pts est.

Our site has mixed English/Japanese content with hreflang tags — does your entity extraction handle Japanese entities with the same confidence scoring, or is non-English treated differently?

What the pages say

No page on the site addresses this.

The fix

Add documentation about entity extraction capabilities, specifically addressing multilingual support, Japanese language handling, and whether confidence scoring varies by language. Consider adding this to a 'Checks Reference' or 'Features' page.

confidence high · Absent

Hedged · 3 of 15 questions

A buyer gets something, then has to guess the rest. Expand any row for the evidence and the fix.

12What specific signals go into your 'AI visibility score' — is it just structured data coverage or do you weight things like semantic HTML density and entity extraction confidence differently?technicalHedges+7 pts est.

What specific signals go into your 'AI visibility score' — is it just structured data coverage or do you weight things like semantic HTML density and entity extraction confidence differently?

What the pages say

No page on the site addresses this.

The fix

The site mentions an 'AI visibility score' and 'scored report' but never explains how the score is calculated, what signals are weighted, or whether factors like semantic HTML density and entity extraction confidence have different weights. Add documentation explaining the scoring algorithm and signal weightings.

Where we looked: geodaddy.dev, geodaddy.dev, geodaddy.dev, /docs

confidence high · Vague

13Which specific AI crawlers does your audit simulate — GPTBot, Claude-Web, Perplexity-Bot, or others? And do you test against their actual current user-agent strings or generic patterns?technicalHedges+2 pts est.

Which specific AI crawlers does your audit simulate — GPTBot, Claude-Web, Perplexity-Bot, or others? And do you test against their actual current user-agent strings or generic patterns?

What the pages say

GeoDaddy tests against GPTBot, ClaudeBot, and PerplexityBot. The chunks do not specify whether they use actual current user-agent strings or generic patterns.

The fix

Clarify whether the tool uses exact current user-agent strings (e.g., 'Mozilla/5.0 AppleWebKit/537.36; compatible; GPTBot/1.0; +https://openai.com/gptbot') or simplified pattern matching, and confirm if the list includes Claude-Web/ClaudeBot specifically or other variants.

Where we looked: geodaddy.dev, geodaddy.dev, geodaddy.dev, geodaddy.dev

confidence medium · Vague

14How heavily do Core Web Vitals factor into AI visibility scores versus traditional SEO? My LCP is 2.8s — is that flagged as critical for AI crawlers or only for Google Search?web-performanceHedges+2 pts est.

How heavily do Core Web Vitals factor into AI visibility scores versus traditional SEO? My LCP is 2.8s — is that flagged as critical for AI crawlers or only for Google Search?

What the pages say

GeoDaddy measures Core Web Vitals (LCP, FCP, CLS, TTFB, TBT) with a real headless browser and states that "Slow pages get deprioritized by all systems." However, the chunks do not specify: (1) how heavily Core Web Vitals factor into AI visibility scores versus traditional SEO, (2) whether a 2.8s LCP is specifically flagged as critical for AI crawlers versus only Google Search, or (3) any threshold values or scoring weights that differentiate AI crawler treatment from traditional search.

The fix

Add documentation explaining the relative weight of Core Web Vitals in AI visibility scoring versus traditional SEO, specific LCP thresholds that trigger flags for AI crawlers, and whether AI systems treat performance metrics differently than Google Search.

Where we looked: geodaddy.dev, geodaddy.dev, geodaddy.dev, geodaddy.dev, geodaddy.dev

confidence medium · Vague

What the pages already answer cleanly

1 of 15. Answered with enough specificity for a buyer to act on. This is the bar the queue above is chasing.

technicalAnswered

Our marketing site is a Next.js SPA — does your audit execute JavaScript to capture dynamically injected structured data, or do I need to pre-render for accurate scoring?

What the pages say

GeoDaddy uses a real headless browser that executes JavaScript. The chunks state it 'Measures LCP, FCP, CLS, TTFB, and TBT with a real headless browser' and validates 'structured data' and 'JSON-LD schema.' This indicates JavaScript execution for dynamic content. However, there is no explicit confirmation that it waits for SPA hydration or specific Next.js behavior—you may need to test to confirm pre-rendering is not required.

Source: geodaddy.dev, geodaddy.dev, geodaddy.dev, geodaddy.dev

confidence medium · Answered

Ask this site’s index

Sitedex already serves geodaddy.dev as an MCP endpoint. Ask geodaddy.dev anything an AI agent might ask, and see what its index returns. (To score your own site, use the form below.)

Snippets & configs

For developers and the engineer-on-call: copy these into your tools or your site.

Files from this audit

Built from this crawl. Download or copy each, then install it at the path noted.

llms.txt

Built from this crawl. Install at /llms.txt so agents start here.

organization.json

Organization JSON-LD, pre-filled from this crawl. Wrap in a ld+json script.

server-card.json

MCP server card built from this crawl. Host at /.well-known/mcp/server-card.json.

webmcp.json

WebMCP discovery manifest built from this crawl. Host at /.well-known/webmcp.json.

MCP endpoint

https://mcp.sitedex.dev/s/geodaddy-dev/mcp

The URL anyone's agent points at. Read-only; safe to share.

Claude Code

claude mcp add geodaddy --transport http https://mcp.sitedex.dev/s/geodaddy-dev/mcp

One command, then the agent has it.

Cursor / Continue

{
  "mcpServers": {
    "geodaddy": {
      "url": "https://mcp.sitedex.dev/s/geodaddy-dev/mcp"
    }
  }
}

Drop into mcp.json.

WebMCP: two parts

WebMCP-capable browsers run the widget at runtime. Crawlers without JS rendering need the discovery manifest to find your tool surface. Install both.

1 · Widget script

<script async src="https://sitedex.dev/widget.js"></script>

Drop in <head>. WebMCP-capable browsers (Chrome 146+ Origin Trial) call navigator.modelContext.provideContext() via this script.

2 · Discovery manifest

{
  "$schema": "https://wellknownmcp.org/schemas/webmcp.json",
  "name": "geodaddy.dev",
  "tools": [
    { "name": "search", "description": "Search geodaddy.dev's indexed content." },
    { "name": "get_page", "description": "Fetch a page from geodaddy.dev as markdown." }
  ]
}

Host alongside the script at /.well-known/webmcp.json. Crawlers that don't render JS rely on this.

Your turn

See which of these questions your site goes silent on.

Free, about 5 minutes. We crawl your site, test it against the buyer questions your category asks, and name what’s vague, contradictory, or missing, plus the files AI agents look for.

ComingEmbeddable grade badgeScore history and deltasOpt-in public board