D

Poor for AI agents

Speed: Fail (real visitors, last 28 days)

96

Find

Does your site let search engines and assistants read and list your pages?

25% of your grade · 9 of 11 goals pass

  • Pages that do not exist say soFail

    A page that does not exist answers 200 with a normal page, so every guessed address looks real. Google treats content behind a 404 or 410 as gone, and flags empty pages that answer 200 (success) as soft 404s.

    • Status 200: https://linear.app/grader-no-such-page-8f3a1c

    What to do Ask the people who run your site to make a mistyped address show a page that says it was not found, with a 404 status behind it.

    For your web team: Return 404 (or 410 for a page that is gone) for unknown routes. A single-page app needs its server to answer unknown paths with the not-found page and a 404 status; a redirect to the home page makes every address look real.

    How Google Search handles HTTP status codes, Google
  • Titles and descriptions fit in a search resultPartial

    1 of the 2 audits in this goal falls short: The description is 64 characters; search results have room for about 155. Google sets no length limit and cuts a title or description to the device's width. SEO tools measure a title in pixels, since 60 characters run from 267 to 1,133 pixels, and count a description in characters. A cut loses the last words.

    • 64 characters: https://linear.app/

    What to do Ask the people who run your site to keep each title short enough to show in full and each description to one or two sentences, with the words that matter first.

    For your web team: Keep each <title> within about 560 pixels of Arial at 20px, which is about 60 characters of ordinary text and fewer with wide capitals, with the main words first. Keep each meta description to 70 to 155 characters.

    Influencing Title Links in Google Search, Google
  • Search engines and AI assistants are allowed to read your sitePass

    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.

    Overview of OpenAI crawlers, OpenAI
  • Search engines may list each pagePass

    The page answers, no tag or header keeps it out of search results, and robots.txt lets search crawlers read it. 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.

    AI features and your website, Google
  • Search results can show your pages' wordsPass

    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.

    Robots.txt Introduction and Guide, Google
  • Your pages are listed in a sitemapPass

    https://linear.app/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.

    Build and submit a sitemap, Google
  • Every page has its own titlePass

    The title is the page's own and describes it. 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 of its own keeps your wording in front of searchers.

    Influencing Title Links in Google Search, Google
  • Key pages say what they offer in the titlePass

    The title says what the page offers. Google asks for descriptive titles. SearchPilot's test of putting the location at the start of a healthcare provider's titles predicted 8.5% more organic sessions.

    Adding Location to the Start of Title Tags, SearchPilot
  • Each page has a clear address and place in your sitePass

    All 2 audits in this goal pass. Google uses one canonical address per page, recommends readable words rather than long ID numbers, and can show a breadcrumb trail in desktop results when the page marks one up.

    How to Specify a Canonical with rel="canonical" and Other Methods, Google
  • Pages open without detoursPass

    Avoid multiple page redirects: the page has no redirect. Chrome says each extra redirect is another trip across the network that can delay the page by hundreds of milliseconds.

    Avoid multiple page redirects, Chrome
  • A shared link shows a previewPass

    The page names a title, description and image for shared links, and an icon. Open Graph tags decide the title, description and image a link shows when shared; Google shows your icon in results.

    The Open Graph protocol, ogp.me
73

Understand

Do they understand who you are and what you offer?

25% of your grade · 5 of 7 goals pass

  • Your business is described in structured dataFail

    The structured data lacks the business type and review, and gives the business no headline and text. The page does not state the business's application category, comment count, date modified, date published, in language, keywords, operating system, position, and word count. 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.

    • The structured data names no type: https://linear.app/
    • Not in the page's structured data: https://linear.app/
    • No value on the business: https://linear.app/

    What to do Ask whoever runs your site to mark the business up with the most specific schema.org type that fits it, to add the facts this goal lists to the structured data of the pages that show them, and to state on the page any detail this goal says the page does not state.

    For your web team: Add a JSON-LD script whose "@type" is the most specific schema.org type that fits the business, with each missing property set to the value the page shows, a node for each missing type on the page that shows it, and the value of each detail the page does not state in the text of the page. schema.org lists every type, its subtypes and the properties of each.

    About Usage Statistics, schema.org
  • Headings give each page an outlineFail

    Heading elements are not in a sequentially-descending order Google's guide to AI features says headings give a page a clear structure.

    • Fix any of the following: Heading order invalid: <h3 class="sc-KOGVz bFMHeH KFZpfa_titleText">: https://linear.app/

    What to do Ask the people who run your site to give each page one main heading and to put the headings under it in order.

    For your web team: Use h1 once, then h2 to h6 without skipping a level, and remove or fill any heading element that has no text.

    Optimizing your website for generative AI features on Google Search, Google
  • Your key facts are in the page itselfPass

    Scripts add 3 pieces of text your server does not send, and none of it is what visitors come to the page for. 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.

    Understand JavaScript SEO basics, Google Search Central
  • A short guide to your site for AI assistantsPass

    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.

    Optimizing your website for generative AI features on Google Search, Google
  • Every page has its own summary for search resultsPass

    The description is the page's own and reads as a summary. 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.

    How to Write Meta Descriptions, Google
  • Images describe themselvesPass

    All 3 audits in this goal pass. Alt text is a short written description of an image. Google calls it the most important attribute for adding metadata about an image, and it also uses computer vision on the picture. It asks for descriptive file names.

    Image SEO Best Practices, Google
  • Pages say which language they are inPass

    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.

    Rule html-has-lang: <html> element must have a lang attribute, Deque axe
  • Lists and tables are built as lists and tablesPass

    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.

    Rule list: <ul> and <ol> must only directly contain <li>, <script> or <template> elements, Deque axe
36

Act

Can they use your site for a shopper?

25% of your grade · 2 of 7 goals pass

  • Assistants can read your page's controlsMust haveFail

    Accessibility tree is not well-formed Chrome says agents review the accessibility tree to find what they can click or fill in, and missing labels can block them.

    A must have. While it fails, your letter stays at C or lower.

    • Buttons must have discernible text: <button type="button" aria-disabled="false" data-base-ui-click-trigger="" id="base-ui-_R_3lv7l6cqna_" aria-haspopup="dialog" aria-expanded="false" class="TZTsQG_mobileMenuTrigger hCgVwa_reset-button">: https://linear.app/
    • Links must have discernible text: <a href="/customers" class="MR81zG_logosLink I_mUeq_root" rel="noopener">: https://linear.app/

    What to do Ask whoever runs your site to run Google's PageSpeed Insights on the home page and fix the accessibility problems it lists, which are mostly buttons and fields with no label.

    For your web team: Give every button, link and field an accessible name, associate each field with a label, and remove invalid ARIA roles and attributes. PageSpeed lists the elements that fail.

    Accessibility for agents, Chrome
  • Your site offers tools to AI assistantsMust haveFail

    Your home page offers no tools to AI assistants. WebMCP lets an assistant book or reserve through a site's own code instead of guessing its way around the screen.

    A must have. While it fails, your letter stays at B or lower.

    • PageSpeed's "WebMCP tools registered" audit lists no tool: https://linear.app/

    What to do Ask whoever runs your site to expose the main action on your site, such as booking or contacting you, as a WebMCP tool.

    For your web team: Call document.modelContext.registerTool({ name, description, inputSchema, execute }) as the home page loads, or add toolname and tooldescription attributes to the form. A name is 1 to 128 letters, digits, _, - or .

    WebMCP for developers, Chrome
  • Text is readablePartial

    1 of the 2 audits in this goal falls short: Background and foreground colors do not have a sufficient contrast ratio. WCAG requires text to contrast with its background by at least 4.5 to 1, and the axe rule color-contrast checks for it.

    • Fix any of the following: Element has insufficient color contrast of 3.45 (foreground color: #62666d, background color: #08090a, font size: 9.0pt (12px), font weight: normal). Expected contrast ratio of 4.5:1: <p class="sc-KOGVz igJSCV Fzcv4W_inset Fzcv4W_insetSmall">: https://linear.app/

    What to do Ask the people who run your site to darken pale text and to underline the links inside paragraphs.

    For your web team: Reach a contrast ratio of 4.5 to 1 for normal text, mark links in text with more than color, and leave user-scalable and maximum-scale out of the viewport tag.

    Rule color-contrast: Elements must meet minimum color contrast ratio thresholds, Deque axe
  • Buttons and links are big enough to tapPartial

    1 of the 2 audits in this goal falls short: Touch targets do not have sufficient size or spacing. web.dev recommends tap targets of around 48 pixels, and WCAG sets a minimum of 24 by 24 pixels.

    • Fix any of the following: Target has insufficient size (50px by 14px, should be at least 24px by 24px) Target has insufficient space to its closest neighbors. Safe clickable space has a diameter of 20px instead of at least 24px.: <button type="button" tabindex="0" aria-haspopup="menu" aria-expanded="false" id="base-ui-_R_6lil943bl6cqna_" class="Mmx1Wq_switchWorkspaceButton">: https://linear.app/

    What to do Ask the people who run your site to make small buttons and tightly packed links bigger on phones.

    For your web team: Make each target at least 24 by 24 CSS pixels, or leave enough space around smaller ones, and aim for around 48 pixels. Set width=device-width in the viewport tag so taps answer at once.

    Accessible tap targets, Google
  • Extra labels on controls are used correctlyPass

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

    Rule aria-roles: ARIA roles used must conform to valid values, Deque axe
  • Visitors can move around the pagePass

    All 2 audits in this goal pass. WCAG, the web accessibility standard most laws point to, requires every function of a page to work from a keyboard.

    Accessibility for agents, Chrome
69

Performance

Is it fast and sound for the person who clicks through?

Speed comes from real visitors of your page over the last 28 days when Google has their numbers, and from a test on a phone when it does not.

25% of your grade · 4 of 10 goals pass

  • Repeat visitors get a faster pageFail

    Use efficient cache lifetimes (Est savings of 86 KiB) web.dev says fetching resources over the network is both slow and expensive.

    • Use efficient cache lifetimes (Est savings of 86 KiB): https://linear.app/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/cd9c3c96-fbba-4687-8e50-da703a608000/f=auto,fit=scale-down,metadata=none
    • Use efficient cache lifetimes (Est savings of 86 KiB): https://linear.app/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/c16152f3-a36c-468e-89ae-f87c2f244d00/f=auto,fit=scale-down,metadata=none
    • Use efficient cache lifetimes (Est savings of 86 KiB): https://linear.app/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/7d7115d9-a0eb-4a92-5900-3ca3ee077d00/f=auto,fit=scale-down,metadata=none

    What to do Ask the people who run your site to let browsers keep images, scripts and styles between visits.

    For your web team: Send Cache-Control with a long max-age for fingerprinted static files, and revalidate the rest with ETag.

    Prevent unnecessary network requests with the HTTP Cache, Google
  • The main content shows up quicklyPartial

    3 of the 3 audits in this goal fall short: Largest Contentful Paint is 4.3 s for real visitors of this page, last 28 days, which Google rates poor, First Contentful Paint is 2.3 s for real visitors of this page, last 28 days, which Google rates needs improvement, and Speed Index (6.6 s). 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 4.3 s for real visitors of this page, last 28 days, which Google rates poor.: https://linear.app/
    • First Contentful Paint is 2.3 s for real visitors of this page, last 28 days, which Google rates needs improvement.: https://linear.app/
    • Speed Index (6.6 s): https://linear.app/

    What to do Ask the people who run your site to make the first screen load faster on phones, starting with its biggest image.

    For your web team: Serve the largest element early: preload it, avoid render-blocking scripts and styles, and cut server response time. PageSpeed lists what holds it back.

    Web Vitals, Google
  • The page responds as soon as it appearsPartial

    Interaction to Next Paint is 224 ms for real visitors of this page, last 28 days, which Google rates needs improvement. 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.

    • Interaction to Next Paint is 224 ms for real visitors of this page, last 28 days, which Google rates needs improvement.: https://linear.app/
    • Reduce JavaScript execution time (1.4 s): https://linear.app/
    • Minimize main-thread work (4.5 s): https://linear.app/

    What to do Ask the people who run your site to remove scripts it does not need, which keep the page busy.

    For your web team: Split long tasks and defer scripts that are not needed to start. PageSpeed lists the costliest scripts.

    Total Blocking Time (TBT), Google
  • Images are the right sizePartial

    1 of the 4 audits in this goal falls short: Improve image delivery (Est savings of 214 KiB). Chrome says serving images larger than the version rendered on screen results in wasted bytes and slows page load.

    • Improve image delivery (Est savings of 214 KiB): <div class="SPbJba_grain SPbJba_grainSubtle WS84WW_grainOverlay" style="inset:1px">: https://linear.app/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/cd9c3c96-fbba-4687-8e50-da703a608000/f=auto,fit=scale-down,metadata=none

    What to do Ask the people who run your site to resize and compress your images before they go on the page.

    For your web team: Serve several sizes with srcset and sizes, use a modern format such as WebP or AVIF, and keep each image's width and height in the proportion it is shown.

    Properly size images, Chrome
  • The page does not weigh muchPartial

    5 of the 7 audits in this goal fall short: Avoid enormous network payloads (Total size was 2,972 KiB), Reduce unused JavaScript (Est savings of 250 KiB), Reduce unused CSS (Est savings of 26 KiB), Minify CSS (Est savings of 8 KiB), and Legacy JavaScript (Est savings of 9 KiB). Chrome says large network payloads are highly correlated with long load times and cost visitors money on mobile data.

    • Avoid enormous network payloads (Total size was 2,972 KiB): https://static.linear.app/fonts/InterVariable.woff2?v=4.1
    • Reduce unused JavaScript (Est savings of 250 KiB): https://static.linear.app/web/_next/static/chunks/Dfm0YAnr.js
    • Reduce unused CSS (Est savings of 26 KiB): .cVAQDa { font-size: var(--title-8-size); letter-spacing: var(--title-8-letter-spacing); … } …

    What to do Ask the people who run your site to remove code and files the page does not use.

    For your web team: Minify scripts and styles, remove unused and duplicate code, and stop shipping legacy polyfills. PageSpeed lists the files by size.

    Avoid enormous network payloads, Chrome
  • The page loads without errorsPartial

    2 of the 7 audits in this goal fall short: Issues were logged in the Issues panel in Chrome Devtools and Missing source maps for large first-party JavaScript. Chrome says an error in the console means a problem on your page that you need to resolve.

    • Issues were logged in the Issues panel in Chrome Devtools: https://linear.app/
    • Missing source maps for large first-party JavaScript: https://linear.app/

    What to do Ask the people who run your site to open the page in a browser's developer tools and clear the errors it lists.

    For your web team: Fix each console error and browser issue, replace deprecated APIs, publish source maps for your scripts, and start the document with a doctype and a charset.

    Browser errors were logged to the console, Chrome
  • The page does not jump around while it loadsPass

    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.

    Web Vitals, Google
  • Visitors are on a secure connectionPass

    Uses HTTPS web.dev says a secure connection helps prevent intruders tampering with traffic between your site and its visitors.

    Why HTTPS matters, Google
  • Visitors are not interrupted on arrivalPass

    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.

    Requests the geolocation permission on page load, Chrome
  • Served fast from servers near your visitorsPass

    All 5 audits in this goal pass. A CDN keeps copies of your site on servers close to each visitor, so pages arrive sooner. Chrome says a CDN reduces the network latency that slows a server's first response.

    Reduce server response times (TTFB), Chrome

See how the sites the assistant picked grade

The assistant opened 1 other site for this shopper. Grade it with the same checks.

  • productplan.com

Get a site that keeps itself ready

Get this site rebuilt in Clutch. It grades itself as assistants change and fixes what slips, so it stays ready on its own. You approve the new site before it goes live.

How we grade