Google's web.dev guidance now advises developers to treat AI agents as a distinct audience alongside human visitors. As more users delegate goal-oriented tasks to AI, websites with complex hover states or shifting layouts may become functionally broken for these automated entities. The guide highlights that optimization for agents aligns closely with existing accessibility and semantic HTML best practices, making sites better for both humans and machines.
* Treating agents as a distinct visitor type
* How agents interpret websites via screenshots, raw HTML, and the accessibility tree
* Recommendations for using semantic HTML elements and maintaining stable layouts
* Introduction to WebMCP, a proposed web standard for agent-website interaction
* Treating agents as a distinct visitor type
* How agents interpret websites via screenshots, raw HTML, and the accessibility tree
* Recommendations for using semantic HTML elements and maintaining stable layouts
* Introduction to WebMCP, a proposed web standard for agent-website interaction
Google is planning to expand its documentation regarding unsupported robots.txt rules by analyzing real-world data from the HTTP Archive. Rather than adding directives arbitrarily, the team aims to identify and document the top 10 to 15 most commonly used unsupported tags found in the wild. Additionally, Google may broaden its tolerance for common misspellings of the disallow directive.
Key points:
- Use of HTTP Archive data via BigQuery to identify prevalent unsupported rules.
- Potential expansion of documentation to include frequently used but ignored directives.
- Possible increase in typo tolerance for the disallow command.
- Recommendation for webmasters to audit robots.txt files for ineffective directives.
Key points:
- Use of HTTP Archive data via BigQuery to identify prevalent unsupported rules.
- Potential expansion of documentation to include frequently used but ignored directives.
- Possible increase in typo tolerance for the disallow command.
- Recommendation for webmasters to audit robots.txt files for ineffective directives.
Google has removed the "design for accessibility" section from within the Understand the JavaScript SEO basics documentation.
Google said this was removed because the information was "out of date and not as helpful as it used to be."
The old text advised that using JavaScript for page content "may be hard for Google to see," but Google now states this hasn't been true for many years.
While Google Search can handle JavaScript well, it's still important to double-check what Google Search sees using the URL inspection tool in Google Search Console.
Google said this was removed because the information was "out of date and not as helpful as it used to be."
The old text advised that using JavaScript for page content "may be hard for Google to see," but Google now states this hasn't been true for many years.
While Google Search can handle JavaScript well, it's still important to double-check what Google Search sees using the URL inspection tool in Google Search Console.
Google’s John Mueller downplayed the usefulness of LLMs.txt, comparing it to the keywords meta tag, as AI bots aren’t currently checking for the file and it opens potential for cloaking.
Google's John Mueller discusses the issue of low-effort content that may look good but lacks genuine expertise, particularly noting the use of AI-generated images as a potential signal of low-quality content.
Google's Martin Splitt shares how to defend against malicious bots and improve site performance. SEO expert Roger Montti explains why contacting resource providers won't work and offers alternative solutions.
