Can agents find your site and its capabilities?
The page registers no tools via the WebMCP browser API (navigator.modelContext).
Fix: Expose your actions to AI agents with the WebMCP browser API: register tools via navigator.modelContext.registerTool. Optionally also publish a /.well-known/webmcp.json tool catalog as a discovery signpost.
If your llms.txt file does not follow recommendations, large language models may not be able to understand how you want your website to be crawled or used for training. The [llms.txt](https://llmstxt.org/) file should be a Markdown file containing at least one H1 header.
Crawled 12 of 12 discovered pages beyond the homepage.
Lighthouse Agentic Browsing audits ran.
Could not identify a known website platform (custom stack or unrecognised).
Can agents understand your content?
No semantic landmark elements (main, header, footer, nav) detected on the homepage.
Fix: Wrap your page structure in semantic landmarks. AI structural extractors rely on them to separate navigation from content from boilerplate.
Homepage ignored Accept: text/markdown and returned HTML.
Fix: Serve a markdown version of high-value pages when the client asks for text/markdown. AI summarisers, chatbots and IDE agents prefer markdown — fewer tokens, no DOM noise.
0 of 1 tables have <thead>.
Fix: Wrap table headings in <thead><tr><th> so AI tabular extractors can map rows to columns reliably.
Only 1/2 images have width+height — large CLS risk.
Fix: Set width and height on every <img> so the browser reserves space before the image loads. A layout that shifts while loading makes an AI agent mis-click the element it targeted.
12 of 12 pages are missing <title> and/or <h1>: /contact-us/address/0001-0000-paye.aspx, /contact-us/address/0001-0001-paye.aspx, /contact-us/address/0001-0002-paye.aspx, /contact-us/address/0001-0003-paye.aspx, /contact-us/address/0001-0004-paye.aspx, /contact-us/address/0001-0005-paye.aspx, /contact-us/address/0001-0006-paye.aspx, /contact-us/address/0001-0020-paye.aspx, /contact-us/address/0001-0021-paye.aspx, /contact-us/address/0001-0022-paye.aspx, /contact-us/address/0001-0023-paye.aspx, /contact-us/address/0001-0024-paye.aspx.
Fix: Make sure every page sets a unique <title> and exactly one <h1>. The title is how an AI agent confirms it landed on the right page after navigating.
12 of 12 pages return <80 words of visible text — agents without JavaScript see an empty page: /contact-us/address/0001-0000-paye.aspx (1w), /contact-us/address/0001-0001-paye.aspx (1w), /contact-us/address/0001-0002-paye.aspx (1w), /contact-us/address/0001-0003-paye.aspx (1w), /contact-us/address/0001-0004-paye.aspx (1w), /contact-us/address/0001-0005-paye.aspx (1w), /contact-us/address/0001-0006-paye.aspx (1w), /contact-us/address/0001-0020-paye.aspx (1w), /contact-us/address/0001-0021-paye.aspx (1w), /contact-us/address/0001-0022-paye.aspx (1w), /contact-us/address/0001-0023-paye.aspx (1w), /contact-us/address/0001-0024-paye.aspx (1w).
Fix: Pre-render or server-render these pages so AI crawlers (which usually don't execute JS) can read them. Frameworks: Next.js Server Components, Nuxt SSR, Astro, or build-time prerendering.
Homepage server response contains 1186 words of visible text — content is reachable without executing JavaScript.
Detected 5 cookie-banner elements but none look agent-hostile (small, dismissible, or offer a reject option).
Homepage contains ~363 elements.
23 headings, no level skips.
Language declared as "en-GB".
2 of 2 <img> tags have alt attributes.
49 internal links found.
Exactly one <h1> on the homepage.
Can agents actually operate the page?
The page registers no tools via the navigator.modelContext browser API, so an AI agent has no structured way to operate it.
Fix: Expose your site’s actions to AI agents with the WebMCP browser API: call navigator.modelContext.registerTool({ name, description, inputSchema, execute }) from your page so an agent can invoke them. Implement it directly, or with a library like the @mcp-b polyfill (https://mcp-b.ai). Spec: https://github.com/webmachinelearning/webmcp.
All 9 agent-critical accessibility audits passed — an agent can perceive and operate the page through its accessibility tree.
`[aria-*]` attributes match their roles passed.
`[aria-hidden="true"]` is not present on the document `<body>` passed.
`[role]`s have all required `[aria-*]` attributes passed.
`[role]` values are valid passed.
`[aria-*]` attributes are valid and not misspelled passed.
`[aria-*]` attributes have valid values passed.
Buttons have an accessible name passed.
Document has a `<title>` element passed.
Links have a discernible name passed.
Lighthouse accessibility score: 98/100. Agents read the page through its accessibility tree, so this is a proxy for how navigable your site is to an AI agent.
4 of 4 visible interactive form fields have labels.
All audits passed
0.005
0.000 (field data from CrUX) — good.
268ms (field data from CrUX) — good.
1 form missing annotations
Lists the [WebMCP tools](http://goo.gle/webmcp-docs) registered at the time of analysis.
No tool catalog was found at /.well-known/webmcp.json (or /.well-known/webmcp). The catalog is a community convention, not part of the WebMCP standard, so this does not affect WebMCP presence.
Fix: Consider also publishing a tool catalog at /.well-known/webmcp.json: a JSON document with a "spec" of "webmcp/0.1" and a "tools" array, where each tool declares a name and a clear description. It is a community convention (optional, not part of the WebMCP standard) that lets crawlers and agents discover your tools without executing JavaScript.
Can agents safely transact?
No Strict-Transport-Security header on the homepage.
Fix: Add `Strict-Transport-Security: max-age=15768000; includeSubDomains` so browsers and agents refuse to downgrade to http for at least six months.
Found 2 http:// references in the homepage HTML — browsers will block these resources.
Fix: Update every http:// resource URL to https:// (or use protocol-relative `//`). Common offenders: image CDNs and legacy embed snippets.
/.well-known/oauth-authorization-server returned the site's HTML app shell — treating as not published.
Fix: Publish /.well-known/oauth-authorization-server so AI agents discovering your OAuth setup can negotiate flows automatically. Required if your site offers an authenticated API.
/.well-known/oauth-protected-resource returned the site's HTML app shell — treating as not published.
Fix: Publish /.well-known/oauth-protected-resource so AI agents discovering your OAuth setup can negotiate flows automatically. Required if your site offers an authenticated API.
No Web Bot Auth signature headers — sites can't verify agent identity.
Fix: Web Bot Auth (IETF HTTP Message Signatures over Signature / Signature-Input) lets you cryptographically verify which agent is hitting you. Several CDNs offer turn-key support; otherwise skip until vendor support matures.
No Content-Security-Policy header on the homepage.
Fix: Add a Content-Security-Policy. Even a strict default-src directive cuts XSS blast radius dramatically. Start in report-only mode to find violations.
No Referrer-Policy header on the homepage.
Fix: Add `Referrer-Policy: strict-origin-when-cross-origin` so outbound links don't leak full URLs (including query strings) to third parties.
No `X-Content-Type-Options: nosniff` header.
Fix: Add `X-Content-Type-Options: nosniff` to prevent browsers (and some agents) from re-interpreting your responses as a different content type.
No X-Frame-Options header and no CSP frame-ancestors directive.
Fix: Add `X-Frame-Options: SAMEORIGIN` (or a CSP frame-ancestors directive) to prevent your site being framed by a phishing host.
x-amz-cf-id: g_FilMOiyPB2kp1kopSxNorXLzBfifopZ7vhF4HJ (AWS CloudFront)
Homepage scheme is https:.
http://revenue.ie → https://www.revenue.ie/en/home.aspx (3 hops).
No stack-trace markers in the first 5KB.
Valid for 57 more days (Sep 16 23:59:59 2026 GMT, issuer: Sectigo Public Server Authentication CA EV R36).
Server / X-Powered-By headers don't leak product version.