Sitedex

Create a dedicated 'API Limits & Quotas' documentation page at sitedex.dev/docs that specifies: (1) requests-per-minute/hour limits per API key or tier for both MCP and REST endpoints, (2) whether limits vary by free vs paid plans, (3) burst allowance policies, (4) bulk/batch endpoint availability for scoring multiple sites, and (5) throttling behavior for high-volume use cases like CI checks querying 50+ domains.

Add documentation or FAQ content explaining whether Sitedex tracks branded comparison queries ('Sitedex vs X') versus only direct navigational lookups, and how users can monitor their visibility in competitive search scenarios.

Create a dedicated data portability or account closure page that explicitly states whether users can export historical scores, indexing data, and reports, and what format such exports take (JSON, CSV, etc.). Reference GDPR Article 20 right to data portability if applicable.

Add explicit MCP protocol version documentation to the Remote MCP Server documentation page, including compatibility matrix for common clients (Claude Desktop versions, Cursor versions, etc.).

Create a documentation page or FAQ explaining report URL lifecycle: when domains are removed from public reports, whether unverified/unindexed domains return 404 vs other status codes, and any expiration or inactivity policies.

Create documentation for the team domains page explaining whether domain-level permissions exist to restrict which team members can access specific client domains, including any role-based access control (RBAC) or domain siloing features.

Create a dedicated methodology or FAQ page explaining how the AI Visibility Score is calculated, including the specific weightings of sub-components (crawlability, semantic structure, etc.) and whether the final score is a weighted sum or simple average.

Add a dedicated section or page explaining the monetization model: specify revenue share percentages, how payments flow to domain owners, what data or access is being sold, and to whom (AI platforms, data brokers, etc.).

Add explicit documentation on whether automatic re-crawls occur on any schedule (daily/weekly/monthly) or if all updates require manual $5 re-crawl triggers.

Add explicit documentation clarifying whether Sitedex's crawler respects robots.txt directives, whether it has a unique user-agent that can be targeted separately from other AI crawlers, and how it behaves when a site blocks GPTBot but wants to be indexed by Sitedex.

Add explicit documentation on the llms.txt generator page stating whether it uses headless browser rendering (for SPAs) and whether authenticated/session-based content is supported. Clarify if the 'no crawl' claim means static fetch only or if JavaScript execution is included.

Add explicit language on the pricing page stating whether there is a limit on total number of domains per free account, or if it's truly unlimited. For agency use cases with 10+ client sites, clarify whether bulk domain verification or organization-level limits apply.