---
title: "Waymark report for zoominfo.com"
canonical: "https://waymark.genedai.me/score/zoominfo.com"
last-updated: "2026-08-26T16:31:08.122Z"
---

# Waymark report for zoominfo.com

Waymark scored zoominfo.com 76.5/100 (B) on 26 Aug 2026.
Score: 76.5/100 — Usable with gaps
Scanned: 2026-08-26T16:31:08.122Z
Canonical report: https://waymark.genedai.me/score/zoominfo.com

## Layer breakdown

- Discovery: 14.8/20 (9 of 16 eligible checks passed)
- Access: 18.4/30 (18 of 34 eligible checks passed)
- Usability: 35.7/40 (15 of 18 eligible checks passed)
- Payments: N/A (excluded from the denominator)

## Findings

### 1. XML sitemap

- Layer: discovery
- Result: partial
- Evidence: Sitemap referenced in robots.txt only.
- Recommended fix: Add /sitemap.xml and reference it from robots.txt.

### 2. AGENTS.md

- Layer: discovery
- Result: failed
- Evidence: agents.md status 403.
- Recommended fix: Publish /agents.md with agent-oriented usage notes.

### 3. CSP or X-Frame-Options

- Layer: access
- Result: failed
- Evidence: Neither CSP nor X-Frame-Options on homepage.
- Recommended fix: Send Content-Security-Policy or X-Frame-Options.

### 4. OAuth / OIDC well-known

- Layer: access
- Result: failed
- Evidence: No oauth-authorization-server or openid-configuration.
- Recommended fix: Publish /.well-known/openid-configuration or oauth-authorization-server if you authenticate agents.

### 5. Sitemap for agents

- Layer: discovery
- Result: partial
- Evidence: Sitemap only referenced.
- Recommended fix: Publish /sitemap.xml.

### 6. llms-full.txt

- Layer: discovery
- Result: failed
- Evidence: llms-full.txt status 403.
- Recommended fix: Optionally publish /llms-full.txt for one-shot ingest.

### 7. HTTP Link header

- Layer: discovery
- Result: failed
- Evidence: No rel=sitemap|describedby|api-catalog|alternate on homepage.
- Recommended fix: Send RFC 8288 Link headers for related machine resources.

### 8. Markdown negotiation

- Layer: access
- Result: failed
- Evidence: Advertised markdown twin but homepage did not negotiate markdown.
- Recommended fix: Respond to Accept: text/markdown with a markdown body.

### 9. security.txt

- Layer: access
- Result: failed
- Evidence: No /.well-known/security.txt Contact.
- Recommended fix: Publish /.well-known/security.txt with a Contact field.

### 10. change-password well-known

- Layer: access
- Result: failed
- Evidence: Login surface without /.well-known/change-password.
- Recommended fix: If users have passwords, serve /.well-known/change-password.

### 11. Machine-readable errors

- Layer: usability
- Result: partial
- Evidence: API surface without a JSON error shape.
- Recommended fix: Return a JSON or problem+json error body.

### 12. OpenAPI document

- Layer: access
- Result: partial
- Evidence: OpenAPI probe.
- Recommended fix: Publish an OpenAPI document at a stable URL.

### 13. Developer portal

- Layer: access
- Result: partial
- Evidence: No developer portal.
- Recommended fix: Offer a self-serve docs hub.

### 14. Pricing page

- Layer: access
- Result: partial
- Evidence: No pricing page.
- Recommended fix: Publish /pricing.

### 15. RSS or Atom document

- Layer: access
- Result: partial
- Evidence: No /feed or /rss.xml document.
- Recommended fix: Publish /rss.xml or /atom.xml.

### 16. Package homepage match

- Layer: discovery
- Result: failed
- Evidence: No npm package homepage matching zoominfo.com.
- Recommended fix: Publish an official package whose homepage is this domain.

### 17. Content without JavaScript

- Layer: access
- Result: failed
- Evidence: Raw HTML is thin for agents (H1=false, 35 chars).
- Recommended fix: Server-side render your homepage so AI crawlers see meaningful content without JavaScript. Ensure an H1 and 500+ chars of text in raw HTML.

### 18. Agent instruction / when-to-use

- Layer: access
- Result: failed
- Evidence: Agent file exists without when-to-use guidance.
- Recommended fix: Tell agents when to reach for you: add a 'when to use this' section to your llms.txt (or a dedicated agent-instructions file) that names your best-fit use cases.

### 19. llms.txt links resolve

- Layer: access
- Result: partial
- Evidence: 2 real, 0 homepage-shell, 6 dead of 8 sampled links.
- Recommended fix: Make every link your llms.txt declares resolve to real content, not a homepage shell 200.

### 20. Markdown alternate link

- Layer: access
- Result: failed
- Evidence: rel=alternate markdown /index.md
- Recommended fix: Advertise a markdown twin with rel=alternate type=text/markdown and serve markdown at that URL.

### 21. Markdown frontmatter metadata

- Layer: access
- Result: failed
- Evidence: Served markdown has no YAML frontmatter block.
- Recommended fix: Open served markdown with a --- frontmatter block carrying title plus description, canonical, or last-updated.

### 22. Redirect hygiene

- Layer: access
- Result: failed
- Evidence: Homepage looks like a meta-refresh or JS-only redirect stub.
- Recommended fix: Replace meta-refresh and JavaScript-only redirects with real HTTP 301/302 redirects.

### 23. Accessible document structure

- Layer: usability
- Result: failed
- Evidence: Homepage HTML lacks main/nav/H1 document structure.
- Recommended fix: Give the homepage a main region, nav, H1, and a heading order that does not skip levels.

### 24. Registry branding

- Layer: discovery
- Result: failed
- Evidence: MCP card missing icon.
- Recommended fix: Give your MCP server-card a display name, an icon or logo, and a description.

### 25. MCP tool naming

- Layer: usability
- Result: partial
- Evidence: 2/7 tools use descriptive names.
- Recommended fix: Use consistent snake_case or camelCase names that are descriptive (≥4 chars), not generic run/get/do.

### 26. Agent-UA markdown docs

- Layer: access
- Result: failed
- Evidence: Docs host did not serve markdown to GPTBot (HTTP 429, text/html; charset=utf-8).
- Recommended fix: Serve text/markdown to GPTBot (and similar agent UAs) on your docs host.

## Interpretation

Public technical snapshot; not a guarantee of task completion. Private and authenticated workflows are outside this scan. Cite scanned_at and the canonical report URL; the URL serves the latest completed snapshot and can change after a rescan.

The official Waymark score is Discovery 20 / Access 30 / Usability 40 / Payments 10. N/A and scanner-error checks drop out of the denominator; they are not scored as failures. An observed agent journey is supporting evidence and does not change the numeric score.