{"slug": "agentic-browsing-in-pagespeed-insights-checks-and-fixes", "title": "Agentic Browsing in PageSpeed Insights: Checks and Fixes", "summary": "Google's PageSpeed Insights now includes an experimental 'Agentic Browsing' category in Lighthouse, which measures whether AI agents can understand and use a webpage. The checks focus on semantic HTML, accessible names, and stable layouts, but the category is not a ranking factor, and failed checks are not SEO penalties. Developers should prioritize fixing unlabeled controls and cumulative layout shift, while the optional llms.txt and WebMCP checks are low priority.", "body_md": "*Last updated: August 21, 2026*\n\nYou opened PageSpeed Insights to check a slow page and noticed a new category: **Agentic Browsing**.\n\nSome checks passed. One says *Not applicable*. Others mention `llms.txt`\n\nand WebMCP.\n\nShould you worry?\n\n**No. Agentic Browsing measures whether an AI agent can understand and use your page. It is not a Google ranking factor, and a failed check is not an SEO penalty.**\n\nHere’s what the checks mean and which ones deserve your attention.\n\nAgentic Browsing is an experimental Lighthouse category in PageSpeed Insights and Chrome DevTools.\n\nTraditional Lighthouse checks ask:\n\nIs this page usable for people?\n\nAgentic Browsing asks:\n\nCan software understand this page and complete a task without guessing?\n\nThat means identifying buttons, understanding form fields, reading page structure, and interacting with stable content.\n\nThe category currently focuses on:\n\n`llms.txt`\n\nThe score is based on applicable checks. A result marked **Not applicable** is not a failure.\n\nImportant:Agentic Browsing is a readiness signal, not a ranking system.\n\nAgents, screen readers, and other automated tools rely on semantic HTML and accessible names.\n\nAvoid clickable `<div>`\n\nelements and unlabeled inputs:\n\n```\n<div class=\"btn\" onclick=\"submitForm()\">\n  <svg><use href=\"#icon-send\"/></svg>\n</div>\n\n<input type=\"text\" placeholder=\"you@company.com\">\n```\n\nUse real controls and labels instead:\n\n```\n<button type=\"submit\">\n  <svg aria-hidden=\"true\"><use href=\"#icon-send\"/></svg>\n  Send reset link\n</button>\n\n<label for=\"email\">Email address</label>\n<input\n  id=\"email\"\n  name=\"email\"\n  type=\"email\"\n  required\n  autocomplete=\"email\"\n>\n```\n\nThe key improvements are:\n\n`<button>`\n\nfor buttons`<label>`\n\nfor form fieldsYou can quickly find unlabeled controls in DevTools:\n\n```\n[...document.querySelectorAll('button, a, input, select, textarea')]\n  .filter(el => {\n    const name =\n      el.getAttribute('aria-label') ||\n      el.labels?.[0]?.textContent ||\n      el.textContent?.trim() ||\n      el.getAttribute('title');\n\n    return !name;\n  })\n  .forEach(el => console.warn('No accessible name:', el));\n```\n\n**Priority: high.** This improves accessibility, usability, and machine readability.\n\nAgentic Browsing also checks **Cumulative Layout Shift**, a Core Web Vital.\n\nIf content moves after loading, an agent—or a human—may click the wrong element.\n\nThe standard thresholds are:\n\n| CLS | Verdict |\n|---|---|\n| 0.00 to 0.10 | Good |\n| 0.10 to 0.25 | Needs improvement |\n| Above 0.25 | Poor |\n\nCommon fixes include:\n\n```\n<img\n  src=\"hero.webp\"\n  width=\"1200\"\n  height=\"630\"\n  alt=\"Acme dashboard overview\"\n>\n<div style=\"aspect-ratio: 16 / 9; width: 100%;\">\n  <iframe\n    src=\"...\"\n    loading=\"lazy\"\n    title=\"Product tour\"\n  ></iframe>\n</div>\n.cookie-banner {\n  position: fixed;\n  inset-inline: 0;\n  bottom: 0;\n}\n```\n\n**Priority: high.** CLS already affects mobile usability and Core Web Vitals.\n\n`llms.txt`\n\n: Optional, Not an SEO Requirement\nThe `llms.txt`\n\ncheck looks for a file at:\n\n```\nhttps://yoursite.com/llms.txt\n```\n\nIf the file is missing, Lighthouse may show **Not applicable**.\n\nThat does not mean your site is broken.\n\nGoogle has stated that `llms.txt`\n\nis not required for Google Search and does not improve or reduce rankings.\n\nA basic file might look like this:\n\n```\n# Acme Analytics\n\n> Self-serve product analytics for small engineering teams.\n\n## Docs\n\n- [Quickstart](https://acme.dev/docs/quickstart.md)\n- [REST API](https://acme.dev/docs/api.md)\n- [Event schema](https://acme.dev/docs/events.md)\n```\n\nConsider creating one if you publish technical documentation or an API that AI tools may need to understand.\n\nFor a standard business website or blog, you can usually skip it.\n\n**Priority: low and situational.**\n\nWebMCP lets a website expose structured actions to AI agents.\n\nFor example, instead of asking an agent to find a search box, type into it, and guess which button to click, you can expose a tool such as:\n\n``` js\nif ('modelContext' in document) {\n  const controller = new AbortController();\n\n  document.modelContext.registerTool({\n    name: 'searchProducts',\n\n    description: 'Search the product catalogue.',\n\n    inputSchema: {\n      type: 'object',\n      properties: {\n        query: {\n          type: 'string',\n          description: 'Search keyword or phrase'\n        }\n      },\n      required: ['query']\n    },\n\n    async execute({ query }) {\n      return await productStore.search(query);\n    },\n\n    signal: controller.signal\n  });\n}\n```\n\nWebMCP is still experimental, so most websites do not need it yet.\n\nIt may be worth exploring if your site supports:\n\n**Priority: low for most sites.**\n\nA report might look like this:\n\n```\nAgentic Browsing                    3/3 checks passed\n\nAccessibility tree                Passed\nCumulative Layout Shift  0.019    Passed\nllms.txt                          Passed\nWebMCP registered tools           Not applicable\n```\n\nThe important detail is that **Not applicable is excluded from the score**.\n\nYou can inspect the underlying Lighthouse report with:\n\n```\nnpx lighthouse@latest https://example.com \\\n  --only-categories=agentic-browsing\n```\n\nIn the JSON output, `notApplicable`\n\nand `informative`\n\ndo not mean failure.\n\n**No.**\n\nAgentic Browsing is a Lighthouse diagnostic category, not a Google ranking factor.\n\nYour SEO priorities remain:\n\nThe good news is that several improvements overlap. Clear headings, semantic HTML, labeled forms, and stable layouts help users, search engines, assistive technology, and AI agents.\n\nUse this priority order:\n\n`llms.txt`\n\n**** if you publish technical documentation** Do not implement a technology simply because it appears in a new PageSpeed panel.\n\n**“Not applicable” is not a to-do item.**\n\nAgentic Browsing is still experimental, but its main lesson is practical: make your website clear, semantic, and stable.\n\nThat helps every kind of visitor—including people, search engines, assistive tools, and future AI agents.\n\nNo. It is a Lighthouse category, not part of Google's ranking system.\n\n`llms.txt`\n\nfor SEO?\nNo. Google does not require it for Search rankings.\n\nIt means Lighthouse found nothing to evaluate. This is common for WebMCP when no tools are registered.\n\nOnly if your website's main purpose involves completing actions such as searching, booking, purchasing, or submitting forms. WebMCP is still experimental.\n\nProbably. Chrome describes Agentic Browsing and WebMCP as experimental and subject to change. Focus first on durable improvements such as accessibility and CLS.\n\n**Not sure which Agentic Browsing checks your site needs?**\n\n[Request a free technical SEO and Core Web Vitals audit](https://www.linkedin.com/in/samee-ullah-dev/)\n\nWe'll review your key templates, separate meaningful issues from optional checks, and provide a prioritised action plan.", "url": "https://wpnews.pro/news/agentic-browsing-in-pagespeed-insights-checks-and-fixes", "canonical_source": "https://dev.to/samee-ullah/agentic-browsing-in-pagespeed-insights-checks-and-fixes-3ch3", "published_at": "2026-08-21 16:31:48+00:00", "updated_at": "2026-08-21 16:45:17.700316+00:00", "lang": "en", "topics": ["developer-tools", "ai-agents", "ai-products"], "entities": ["Google", "PageSpeed Insights", "Lighthouse", "Chrome DevTools", "WebMCP"], "alternates": {"html": "https://wpnews.pro/news/agentic-browsing-in-pagespeed-insights-checks-and-fixes", "markdown": "https://wpnews.pro/news/agentic-browsing-in-pagespeed-insights-checks-and-fixes.md", "text": "https://wpnews.pro/news/agentic-browsing-in-pagespeed-insights-checks-and-fixes.txt", "jsonld": "https://wpnews.pro/news/agentic-browsing-in-pagespeed-insights-checks-and-fixes.jsonld"}}