---
title: "What we'd find on visualsitemaps.com"
canonical: https://sitesinthewoods.com/check/visualsitemaps.com/9bc7c0de-4e0d-4158-9705-a2a9b5fe5386
last-updated: 2026-11-20T01:14:40.369Z
---

# What we'd find on visualsitemaps.com

**B · Mostly ready**, 81 of 100 (scored as a content site). Search engines and agents can reach it, understand it and work with it. It doesn't say who runs it or how to reach them.

Checked 2026-11-20T01:14:40.369Z. How we score: https://sitesinthewoods.com/check/method

## Can search engines and agents reach it? (100)

- **Googlebot** (ok): robots.txt lets Googlebot read / and /llms.txt.
- **Bingbot** (ok): robots.txt lets Bingbot read / and /llms.txt.
- **OAI-SearchBot** (ok): robots.txt lets OAI-SearchBot read / and /llms.txt.
- **Claude-SearchBot** (ok): robots.txt lets Claude-SearchBot read / and /llms.txt.
- **PerplexityBot** (ok): robots.txt lets PerplexityBot read / and /llms.txt.
- **Content without JavaScript** (ok): The homepage's text and links are in its HTML, so agents that don't run JavaScript can read it.
- **sitemap** (ok): /sitemap.xml is an index of 2 sitemaps.

## Do they understand what it is? (92)

- **description** (ok): The homepage has its description.
- **og:title** (ok): The homepage has its og:title.
- **share image (og:image)** (ok): The homepage has its share image (og:image).
- **structured data** (ok): The homepage describes itself in structured data (6 types).
- **main heading (h1)** (ok): The homepage has a main heading (h1).
- **llms.txt** (ok): Found at /llms.txt.
- **llms.txt's links** (ok): The 10 links we read in llms.txt all answer.
- **Markdown version** (missing, +3): The homepage has no Markdown version, which agents read with far fewer tokens than HTML. Fix: Serve a Markdown version of the homepage: answer requests that send Accept: text/markdown with it (and Vary: Accept), or publish /index.md, and link it from the head with <link rel="alternate" type="text/markdown" href="…">.

## Can an agent work with it? (100)

- **Agent card** (na): None at /.well-known/agent-card.json. Tells other agents what this site's agent can do (A2A). Only for sites with an agent of their own.
- **OpenAPI** (na): None at /openapi.json. Lets agents call the site's API without guessing. Only for sites with an API.
- **MCP manifest** (na): None at /.well-known/mcp.json. Points agents to the site's MCP server. Only for sites with one.
- **API catalog** (na): None at /.well-known/api-catalog. Lists the site's APIs and their descriptions in one place (RFC 9727). Only for sites with an API.
- **Agent skills index** (na): None at /.well-known/agent-skills/index.json. Lists skills an agent can install to use the site (agent skills discovery). Only for sites that publish skills.
- **AI catalog** (na): None at /.well-known/ai-catalog.json. Lists what the site offers agents (its MCP server, its API), for AI clients to find. Only for sites with an API or MCP server.
- **MCP server card** (na): None at /.well-known/mcp/server-card.json. Describes the site's MCP server (its name, endpoint and transport) before a client connects (SEP-1649). Only for sites with one.
- **404 page** (ok): A page that doesn't exist answers 404 and links back into the site, so a reader or agent on a dead link has a way on.

## Can they trust it? (14)

- **Organization** (warn, +3): The homepage's structured data names an organization but says little about it: only 2 profiles elsewhere. Fix: Add an Organization to the homepage's JSON-LD with its name, url, logo, description, sameAs links to its profiles elsewhere, and a contactPoint.
- **security.txt** (missing, +5): None at /.well-known/security.txt. Tells security researchers how to reach you (RFC 9116). Fix: Add /.well-known/security.txt with a "Contact:" line and an "Expires:" date less than a year away (RFC 9116).
- **About page** (missing, +3): The homepage doesn't link an about page, which says who runs the site. Fix: Add an about page saying who runs the site, and link it from the homepage (its footer will do).
- **Contact page** (missing, +3): The homepage doesn't link a contact page or address, so people and agents can reach whoever runs it. Fix: Add a contact page (or a mailto: link) and link it from the homepage.
- **Privacy policy** (missing, +3): The homepage doesn't link a privacy policy, which says what it does with visitors' data. Fix: Publish a privacy policy and link it from the homepage's footer.
