clutch.io

Every AI search crawler and agent we grade is allowed. Training crawlers are allowed. A crawler is a robot that reads sites for a search engine or assistant, and one that is blocked cannot recommend you. Bing lists blocking Bingbot among the things to avoid, because content it cannot crawl may not be indexed or used in Copilot's answers.

Page isn’t blocked from indexing Google leaves out a page marked noindex, and a page its crawler cannot read cannot be listed or used as a supporting link in its AI features.

All 2 audits in this goal pass. A page whose text is kept out of results leaves a search engine or assistant nothing to quote. Google's AI features follow nosnippet and max-snippet, and Bing keeps content marked noarchive out of Copilot and limits nocache pages to their address, title and snippet.

https://clutch.io/sitemap.xml is a sitemap. Google and Bing use an XML sitemap named in robots.txt to find your pages, and neither promises to index every page in it. A page must be indexed to appear in Google's AI answers.

All 2 audits in this goal pass. Google says the vast majority of the new pages it finds each day come through links, and it follows only links that are real <a> elements with an address.

Document has a <title> element Google builds the title link in search results from the page's title, and may change one that is missing, vague, boilerplate or repeated. A title keeps your wording in front of searchers.

A page that does not exist answers 404. Google treats content behind a 404 or 410 as gone, and flags empty pages that answer 200 (success) as soft 404s.

All 2 audits in this goal pass. Google uses one canonical address per page, and uses hreflang to send searchers to the version of the page in their language.

All 2 audits in this goal pass. Each extra redirect is another trip across the network that can delay the page by hundreds of milliseconds.

Everything the page shows once scripts run is in the page as your server sends it. Claude's web fetch tool does not support pages that fill in their text with JavaScript, and Google reads such a page only after its first HTML, once it reaches the rendering queue. A page whose first response is empty waits or looks empty.

The home page's structured data names Organization, Service, and SoftwareApplication. Structured data spares an assistant from guessing what a page means. Google says it gives explicit clues about a page; Bing says it may support clearer grounding and promises nothing.

Heading elements appear in a sequentially-descending order Headings give a page a clear structure.

All 2 audits in this goal pass. WCAG, the web accessibility standard most laws point to, requires the structure a page shows on screen to be in its markup as well, and the axe rules check lists and tables for it.

Document has a meta description Google can show a page's meta description as its snippet and asks for a different one on every page. It is less likely to show a list of keywords, so a specific summary has the best chance of being used.

All 2 audits in this goal pass. WCAG requires the language of each page to be set in its code, so software reads it with the right rules and voice.

llms.txt follows recommendations llmstxt.org proposes the file so assistants find what they need and follow its links. Lighthouse calls it an emerging convention and Google Search does not use it, so it is a bonus.

ARD manifest is valid The Agentic Resource Discovery (ARD) draft is a format that helps assistants discover what a site offers, such as tools and agents; the standards are still emerging.

All 2 audits in this goal pass. WCAG requires every button and link to expose a name that says its purpose, and the axe rules button-name and link-name check for it.

Accessibility tree is well-formed (All audits passed) Agents review the accessibility tree to find what they can click or fill in, and missing labels can block them.

All 7 audits in this goal pass. Wrong ARIA tells an assistant a control is something it is not. WAI-ARIA defines the roles and attributes that are valid, and the axe rules check them.

Document has a main landmark. WCAG, the web accessibility standard most laws point to, requires every function of a page to work from a keyboard.

All 2 audits in this goal pass. WebMCP lets an assistant book or reserve through a site's own code instead of guessing its way around the screen.

All 2 audits in this goal pass. WCAG requires text to contrast with its background by at least 4.5 to 1, and the axe rule color-contrast checks for it.

All 2 audits in this goal pass. web.dev recommends tap targets of around 48 pixels, and WCAG sets a minimum of 24 by 24 pixels.

Largest Contentful Paint is 3.4 s for real visitors of this page, last 28 days, which Google rates needs improvement and First Contentful Paint is 3.4 s for real visitors of this page, last 28 days, which Google rates poor. Measured from real visitors of this page, last 28 days; the rest is a lab test on a phone. LCP is how long the main picture or text takes to appear, and visitors leave slow pages. web.dev says 2.5 seconds or less is good, one of Google's three Core Web Vitals.

• Largest Contentful Paint is 3.4 s for real visitors of this page, last 28 days, which Google rates needs improvement.: https://clutch.io/
• First Contentful Paint is 3.4 s for real visitors of this page, last 28 days, which Google rates poor.: https://clutch.io/
• Render-blocking requests (Est savings of 770 ms), from clutch.run: https://ot.clutch.run/_ot/cfe0f6d2aa1a.js

Total Blocking Time (0 ms) INP is the wait between a tap and the page responding, and under 200 milliseconds is good. Total Blocking Time, the lab test's stand-in, has the same bar.

Cumulative Layout Shift is 0.00 for real visitors of this page, last 28 days, which Google rates good. CLS measures how much the page jumps while it loads, which makes people tap the wrong thing. web.dev names it one of three Core Web Vitals, and 0.1 or less is good.

Uses HTTPS A secure connection helps prevent intruders tampering with traffic between your site and its visitors.

All 3 audits in this goal pass. A CDN (a network of servers near your visitors) reduces the network latency that slows a server's first response.

All 4 audits in this goal pass. Serving images larger than the version rendered on screen results in wasted bytes and slows page load.

All 8 audits in this goal pass. Large network payloads are highly correlated with long load times and cost visitors money on mobile data.

Use efficient cache lifetimes Fetching resources over the network is both slow and expensive.

All 7 audits in this goal pass. An error in the console means a problem on your page that you need to resolve.

All 3 audits in this goal pass. Users are mistrustful of or confused by pages that ask for their location as soon as they load.