Agent View
The site as an AI agent gets it, beside the site as a person sees it. What it can read, what it has to cut away, and what it never sees.
-- Synthetic SQL Server reference; review in an approved test environment. -- This fixture has not been executed on SQL Server by the author. -- ChangedAt stores UTC datetime2; EventId is unique and breaks timestamp ties. DECLARE @TicketEvents TABLE ( TicketId int NOT NULL, EventId int PRIMARY KEY, ChangedAt datetime2(0) NOT NULL, Status varchar(10) NULL ); INSERT INTO @TicketEvents (TicketId, EventId, ChangedAt, Status) VALUES (101, 1, '2026-10-01T09:00:00', 'Open'), (101, 2, '2026-10-01T10:00:00', 'Closed'), (102, 3, '2026-10-01T11:00:00', 'Closed'), (102, 4, '2026-10-01T12:00:00', 'Open'), (103, 5, '2026-10-01T13:00:00', 'Open'), (103, 6, '2026-10-01T13:00:00', 'Closed'), (104, 7, '2026-10-01T14:00:00', 'Open'), (104, 8, '2026-10-02T00:00:00', 'Closed'); ;WITH RankedEvents AS ( SELECT TicketId, EventId, ChangedAt, Status, ROW_NUMBER() OVER ( PARTITION BY TicketId ORDER BY ChangedAt DESC, EventId DESC ) AS rn FROM @TicketEvents WHERE ChangedAt < '2026-10-02T00:00:00' ) SELECT TicketId, EventId, ChangedAt, Status FROM RankedEvents WHERE rn = 1 AND Status = 'Open' ORDER BY TicketId; -- Expected: TicketId 102 / EventId 4; TicketId 104 / EventId 7.
-- Synthetic SQL Server reference; review in an approved test environment. -- This fixture has not been executed on SQL Server by the author. -- ChangedAt stores UTC datetime2; EventId is unique and breaks timestamp ties. DECLARE @TicketEvents TABLE ( TicketId int NOT NULL, EventId int PRIMARY KEY, ChangedAt datetime2(0) NOT NULL, Status varchar(10) NULL ); INSERT INTO @TicketEvents (TicketId, EventId, ChangedAt, Status) VALUES (101, 1, '2026-10-01T09:00:00', 'Open'), (101, 2, '2026-10-01T10:00:00', 'Closed'), (102, 3, '2026-10-01T11:00:00', 'Closed'), (102, 4, '2026-10-01T12:00:00', 'Open'), (103, 5, '2026-10-01T13:00:00', 'Open'), (103, 6, '2026-10-01T13:00:00', 'Closed'), (104, 7, '2026-10-01T14:00:00', 'Open'), (104, 8, '2026-10-02T00:00:00', 'Closed'); ;WITH RankedEvents AS ( SELECT TicketId, EventId, ChangedAt, Status, ROW_NUMBER() OVER ( PARTITION BY TicketId ORDER BY ChangedAt DESC, EventId DESC ) AS rn FROM @TicketEvents WHERE ChangedAt < '2026-10-02T00:00:00' ) SELECT TicketId, EventId, ChangedAt, Status FROM RankedEvents WHERE rn = 1 AND Status = 'Open' ORDER BY TicketId; -- Expected: TicketId 102 / EventId 4; TicketId 104 / EventId 7.
No <main>: Wrap the page’s own content in <main>, so a reader knows where it starts and stops, and Clean can be measured. No h1: Give each one h1 that says what the page is.
The figures
90 pages, set against the 168,046 sites with figures.
- Readablehigher is better
- 100%90 of 90 pages
- All 168,046 sitesBetter than 47%
Pages whose own text is in the HTML the server sends, enough of it for their kind.
- Cleanhigher is better
- 93%middle page
- All 168,046 sitesBetter than 91%
Of the words before script, the share that are the page and not menus, footer and forms. 11 pages are not measured, with no <main> or no words.
- Costshown, never scored
- 244,794tokens
- About 2,720 a page
To read every page once. A long page that answers well is not worse for it. Tokens are estimated at about 4 characters each.
How its pages spread on Clean
70 pages measured. Not measured: 11 with no <main> or no words.
Against its rivals
The sites nearest it by what they do, with figures. Close means similar work, not better.
| Readinghigher is better | Costnot scored | ||
|---|---|---|---|
| Site | Readable | Clean | Tokens a page |
| askyourdatabase.comThis site, 90 pages | 100% | 93% | 2,720 |
| forem.com100 pages | 98% | 75% | 1,966 |
| dqc.ai100 pages | 96% | 44% | 876 |
| itpathsolutions.com100 pages | 98% | 96% | 6,200 |
First of 4 on Readable, second on Clean.
AI crawler access
What robots.txt says to each, as read on October 24, 2026. 8 of 8 may read the site.
| Crawler | robots.txt says | Used for | The line that decides |
|---|---|---|---|
| GPTBotOpenAI | Not named | Training models | Falls to User-agent: * |
| OAI-SearchBotOpenAI | Not named | ChatGPT search | Falls to User-agent: * |
| ChatGPT-UserOpenAI | Not named | A page a person asks about | Falls to User-agent: * |
| ClaudeBotAnthropic | Not named | Training models | Falls to User-agent: * |
| Claude-SearchBotAnthropic | Not named | Claude’s search | Falls to User-agent: * |
| PerplexityBotPerplexity | Not named | Perplexity search | Falls to User-agent: * |
| Google-ExtendedGoogle | Not named | Training Gemini | Falls to User-agent: * |
| bingbotMicrosoft | Not named | Bing and Copilot | Falls to User-agent: * |
Every AI crawler mttr checks may read it. Not named means the rules for every crawler apply.
Every page
Worst first. Each opens in Agent View at the top.
11 pages have no <main>. Wrap the page’s own content in <main>, so a reader knows where it starts and stops, and Clean can be measured.Open the action plan
| What an agent getshigher is better | Signals | Costnot scored | ||||
|---|---|---|---|---|---|---|
| Page | Words | Clean | Readable | Main heading | Tokens | What it loses |
| /resources/sql-server-latest-status-example.sql | 142 | No <main> | Yes | None | 291 | No <main> and 1 more |
| /seo/ai-database-query/reference.sql | 243 | No <main> | Yes | None | 581 | No <main> and 1 more |
| /seo/crm-pipeline/reference.sql | 189 | No <main> | Yes | None | 349 | No <main> and 1 more |
| /seo/mysql-gui/session-timezone.sql | 115 | No <main> | Yes | None | 214 | No <main> and 1 more |
| /seo/natural-language-rollout/reference.sql | 144 | No <main> | Yes | None | 353 | No <main> and 1 more |
| /seo/postgresql-report/reference.sql | 142 | No <main> | Yes | None | 380 | No <main> and 1 more |
| /seo/sql-dashboard/reference.sql | 248 | No <main> | Yes | None | 670 | No <main> and 1 more |
| /seo/sql-query-generator/join-aggregation.sql | 143 | No <main> | Yes | None | 264 | No <main> and 1 more |
| /seo/text-to-sql-evaluation/fixture.sql | 95 | No <main> | Yes | None | 285 | No <main> and 1 more |
| /seo/text-to-sql/reference.sql | 95 | No <main> | Yes | None | 245 | No <main> and 1 more |
| /seo/warehouse-sql-routing/definition-change.sql | 145 | No <main> | Yes | None | 256 | No <main> and 1 more |
Show where it stands
A card, a badge and a line, each with the figures.
A badge for the site
<a href="https://mttr.si/agent-view/askyourdatabase.com"><img src="https://mttr.si/agent-view/askyourdatabase.com/badge.svg" alt="Agent View: 100% readable, 93% clean" height="20"></a>
The figures in one line
askyourdatabase.com in Agent View: 100% of pages readable, better than 47% of sites; 93% clean; 244,794 tokens to read all 90 pages. mttr.si/agent-view/askyourdatabase.com
What to do next
Fix the pages, let an agent do it, and read the site again to see the figures move.
Fix what agents miss
- Give 19 pages a main headingClearer
- Wrap 11 pages in <main>Clean measured
Connect your agent
Claude Code, Codex or Cursor reads the site’s fixes over MCP, fixes a page in your code, has mttr read it again, and checks the fix landed.
https://mttr.si/mcpSet up an agent
Claim the site
Prove it is yours with a DNS record or a file. Your agent can then reach its reads and jobs, and set each change to wait for your approval.
Claim the siteDrawn from the HTML mttr fetched on its read of October 24, 2026, not a screenshot, and only from the 90 pages read. An assistant’s own reader may differ. Tokens are estimated at about 4 characters each. A site an agent reads well is not a site an assistant cites.