---
title: "Waymark report for blewit.uk"
canonical: "https://waymark.genedai.me/score/blewit.uk"
last-updated: "2026-08-27T10:00:16.987Z"
---

# Waymark report for blewit.uk

Waymark scored blewit.uk 40.3/100 (D) on 27 Aug 2026.
Score: 40.3/100 — Major gaps
Scanned: 2026-08-27T10:00:16.987Z
Canonical report: https://waymark.genedai.me/score/blewit.uk

## Layer breakdown

- Discovery: 6.7/20 (5 of 16 eligible checks passed)
- Access: 9.6/30 (6 of 20 eligible checks passed)
- Usability: 20/40 (1 of 3 eligible checks passed)
- Payments: N/A (excluded from the denominator)

## Findings

### 1. XML sitemap

- Layer: discovery
- Result: failed
- Evidence: No sitemap.xml.
- Recommended fix: Add /sitemap.xml and reference it from robots.txt.

### 2. llms.txt

- Layer: discovery
- Result: failed
- Evidence: llms.txt status 404.
- Recommended fix: Add /llms.txt describing the site for language models.

### 3. AGENTS.md

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

### 4. Well-known AI catalog

- Layer: discovery
- Result: failed
- Evidence: No ai-plugin.json or ai-catalog.json.
- Recommended fix: Add /.well-known/ai-plugin.json or /.well-known/ai-catalog.json.

### 5. Title and description

- Layer: access
- Result: partial
- Evidence: title=true meta=false
- Recommended fix: Set a unique <title> and meta name=description.

### 6. JSON-LD structured data

- Layer: access
- Result: failed
- Evidence: No JSON-LD on the homepage.
- Recommended fix: Add JSON-LD (Organization, WebSite, or SoftwareApplication).

### 7. html lang attribute

- Layer: access
- Result: failed
- Evidence: Missing lang on <html>.
- Recommended fix: Set <html lang="en"> (or the correct language).

### 8. RSS or Atom feed

- Layer: access
- Result: failed
- Evidence: No RSS/Atom link.
- Recommended fix: Expose an RSS or Atom feed for machine subscribers.

### 9. 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.

### 10. CORS / API hint

- Layer: access
- Result: partial
- Evidence: No CORS header or obvious API path.
- Recommended fix: If you expose an API, send Access-Control-Allow-Origin for intended clients.

### 11. 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.

### 12. AI crawlers not blanket-blocked

- Layer: access
- Result: failed
- Evidence: robots.txt Disallow: / for * or common AI bots.
- Recommended fix: Avoid Disallow: / for GPTBot, ClaudeBot, PerplexityBot unless intentional.

### 13. Webhook or API docs

- Layer: usability
- Result: failed
- Evidence: No webhook/API docs mention.
- Recommended fix: Document webhooks and REST/RPC APIs for agents.

### 14. Sitemap for agents

- Layer: discovery
- Result: failed
- Evidence: No sitemap.
- Recommended fix: Publish /sitemap.xml.

### 15. llms.txt index

- Layer: discovery
- Result: failed
- Evidence: Missing /llms.txt.
- Recommended fix: Add a markdown index at /llms.txt.

### 16. llms-full.txt

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

### 17. 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.

### 18. JSON-LD entities

- Layer: access
- Result: failed
- Evidence: No JSON-LD.
- Recommended fix: Embed Organization, Product, Offer, SoftwareApplication, or FAQPage.

### 19. ai-plugin.json

- Layer: discovery
- Result: failed
- Evidence: No /.well-known/ai-plugin.json.
- Recommended fix: Optionally publish a plugin-style capability manifest.

### 20. security.txt

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

### 21. 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.

### 22. llms.txt size and links

- Layer: discovery
- Result: failed
- Evidence: No llms.txt to score.
- Recommended fix: Keep /llms.txt over ~200 characters with absolute URLs to docs.

### 23. Public API surface

- Layer: access
- Result: failed
- Evidence: No public API or docs surface.
- Recommended fix: Document a public API at /docs or /developers.

### 24. Pricing page

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

### 25. Package homepage match

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

### 26. Accessible document structure

- Layer: usability
- Result: partial
- Evidence: Landmarks partial (main=false nav=true h1=true skip=false).
- Recommended fix: Give the homepage a main region, nav, H1, and a heading order that does not skip levels.

### 27. Agent-UA markdown docs

- Layer: access
- Result: failed
- Evidence: Docs host did not serve markdown to GPTBot (HTTP 530, text/plain; 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.
