---
title: "What we'd find on alaskanews.com"
canonical: https://sitesinthewoods.com/check/alaskanews.com/50e2d38f-709b-49a3-bf26-8e6afae95876
last-updated: 2026-11-20T01:12:37.013Z
---

# What we'd find on alaskanews.com

**C · Needs work**, 74 of 100 (scored as a site with an API). Search engines and agents can reach it and understand it. Agents can't find how to work with it.

Checked 2026-11-20T01:12:37.013Z. 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): The sitemap named in robots.txt lists 199 pages.

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

- **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 (2 types).
- **main heading (h1)** (ok): The homepage has a main heading (h1).
- **llms.txt** (ok): Found at /llms.txt.
- **llms.txt's links** (warn, +1): 5 of the first 10 links in llms.txt don't answer. Fix: Fix or remove the links in /llms.txt that answer not found, so agents following them land on real pages.
- **Markdown version** (ok): The homepage answers in Markdown when an agent asks for it (Accept: text/markdown).

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

- **Agent card** (ok): Found at /.well-known/agent-card.json.
- **OpenAPI** (missing, +7): None at /openapi.json. Lets agents call the site's API without guessing. Only for sites with an API. Fix: If the site has an API, publish its OpenAPI description at /openapi.json.
- **MCP manifest** (missing, +7): None at /.well-known/mcp.json. Points agents to the site's MCP server. Only for sites with one. Fix: If the site runs an MCP server, publish /.well-known/mcp.json naming its endpoint.
- **API catalog** (ok): Found at /.well-known/api-catalog, listing 21 entries.
- **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** (missing, +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. Fix: 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** (warn, +2): A page that doesn't exist answers 404 but offers no links or search: a dead end for a reader or an agent. Fix: Give the 404 page links to the homepage and the main sections (or a search box), keeping its 404 status.

## Can they trust it? (57)

- **Organization** (ok): The homepage's structured data names the organization behind it, with a description, a logo and 11 profiles elsewhere.
- **security.txt** (missing, +4): 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** (ok): The homepage links an about page, and it answers.
- **Contact page** (ok): The homepage links a contact page or address, and it answers.
- **Privacy policy** (missing, +2): 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.
