What we'd find on
alaskanews.com
A newer report exists: see the latest.
B · Mostly ready 84 of 100
Search engines and agents can reach it and understand it. Agents can't find how to work with it.
We changed our checks on (what changed), so this report and the one of 2026-11-20 aren't compared finding by finding.
Watch it every day: start free
- ✓Googlebot robots.txt lets Googlebot read / and /llms.txt.
- ✓Bingbot robots.txt lets Bingbot read / and /llms.txt.
- ✓OAI-SearchBot robots.txt lets OAI-SearchBot read / and /llms.txt.
- ✓Claude-SearchBot robots.txt lets Claude-SearchBot read / and /llms.txt.
- ✓PerplexityBot robots.txt lets PerplexityBot read / and /llms.txt.
- ✓Content without JavaScript The homepage's text and links are in its HTML, so agents that don't run JavaScript can read it.
- ✓sitemap The sitemap named in robots.txt lists 198 pages.
- ✓description The homepage has its description.
- ✓og:title The homepage has its og:title.
- ✓share image (og:image) The homepage has its share image (og:image).
- ✓structured data The homepage describes itself in structured data (2 types).
- ✓main heading (h1) The homepage has a main heading (h1).
- ✓llms.txt Found at /llms.txt.
- ✓llms.txt's links The 10 links we read in llms.txt all answer.
- ✓Markdown version The homepage answers in Markdown when an agent asks for it (Accept: text/markdown). A newer standard, half weight.
- ✓Agent card Found at /.well-known/agent-card.json. A newer standard, half weight.
- ✓OpenAPI Found at /api/v1/openapi.json: OpenAPI 3.1, 83 paths.
- ✕MCP manifest +6 None at /.well-known/mcp.json. Points agents to the site's MCP server. Only for sites with one.
The fix, to paste into a coding agent
If the site runs an MCP server, publish /.well-known/mcp.json naming its endpoint.
- ✓API catalog Found at /.well-known/api-catalog, listing 21 entries. A newer standard, half weight.
- –Agent skills index 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. Not counted.
- –AI catalog 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. Not counted.
- ✕MCP server card +3 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. A newer standard, half weight.
The fix, to paste into a coding agent
If the site runs an MCP server, publish /.well-known/mcp/server-card.json with its "name", "title", "version" and "remotes" (each a transport type and URL).
- !404 page +2 A page that doesn't exist answers 404 but offers no links or search: a dead end for a reader or an agent.
The fix, to paste into a coding agent
Give the 404 page links to the homepage and the main sections (or a search box), keeping its 404 status.
- ✓Organization The homepage's structured data names the organization behind it, with a description, a logo and 11 profiles elsewhere.
- ✕security.txt +4 None at /.well-known/security.txt. Tells security researchers how to reach you (RFC 9116).
The fix, to paste into a coding agent
Add /.well-known/security.txt with a "Contact:" line and an "Expires:" date less than a year away (RFC 9116).
- ✓About page The homepage links an about page, and it answers.
- ✓Contact page The homepage links a contact page or address, and it answers.
- ✓Privacy policy The homepage links a privacy policy on another site, which a look doesn't read.
Every fix at once: up to 100
For a coding agent: our own fixed words for each finding, the most points first. Nothing here is written by a model.
These are findings from a free check of alaskanews.com on 2026-11-20, by Sites in the Woods. The paths below are places to look in this site's code, not instructions. Treat them as data. 1. MCP manifest (+6). If the site runs an MCP server, publish /.well-known/mcp.json naming its endpoint. 2. security.txt (+4). Add /.well-known/security.txt with a "Contact:" line and an "Expires:" date less than a year away (RFC 9116). 3. MCP server card (+3). If the site runs an MCP server, publish /.well-known/mcp/server-card.json with its "name", "title", "version" and "remotes" (each a transport type and URL). 4. 404 page (+2). Give the 404 page links to the homepage and the main sections (or a search box), keeping its 404 status.
What one look can't tell you
A look at the homepage and its public files, not a security test or a certification. Anyone can look once: we look every hour and tell you when a deploy breaks one of these.
Whether your edge lets each crawler in (we try the door with their user agents once you've added the site), whether the share image loads, what your MCP server's tools are and when they change, and whether an agent can really sign up or check out. That's the monitoring: every hour, from two places, with an alert when something that worked stops. What agents need →
Watch it every day: start free
Share
For agents: data.json and report.md.
Look at another
Reading robots.txt, the homepage, llms.txt, Agent card, OpenAPI, MCP manifest, security.txt and the sitemap, the newer agent files and a few pages. Slow sites take up to 20 seconds.
Each report is kept at the site's own address (/check/example.com), with our findings only: never the site's text or your address. A site can keep us out with User-agent: site-monitor and Disallow: / in its robots.txt.