Tag: Technical optimization

  • Discover Google Chrome Lighthouse’s New AI Scan Feature

    Discover Google Chrome Lighthouse’s New AI Scan Feature

    I’ve recently discovered that Google has introduced a new feature in Chrome Lighthouse to check for llms.txt files. Though Google mentions that llms.txt isn’t necessary for AI search visibility, Lighthouse has started flagging sites based on their presence.

    Google’s latest Lighthouse audits, under the “Agentic Browsing” category, now focus on a site’s usability for machine interaction. I find this interesting as it aligns with Google’s push towards better machine readability.

    The new audits are part of Chrome’s evolving “Agentic Browsing” features, which analyze if sites are prepared for automated interaction. This concept came soon after Google issued guidance on AI search optimization, debunking the necessity of llms.txt files in their new guide on generative AI features.

    What Lighthouse Evaluates Now. Lighthouse’s Agentic Browsing tests focus on how well my site is built for machine interactions, incorporating various deterministic audits as per Google’s documentation. These checks include:

    – WebMCP integration.

    – Accessibility tree integrity.

    – Layout stability through CLS.

    – Presence of an llms.txt file.

    These audits help ensure that there’s a machine-readable summary at the site’s domain root. Google explains that without llms.txt, agents might take longer to understand a site’s main structure.

    The impact of these audits doesn’t translate into a traditional Lighthouse score but into a fractional pass ratio related to agentic readiness signals.

    The Tension. Interestingly, while these audits don’t directly affect SEO rankings, their mention in Google’s readiness checks could make SEOs reconsider their stance on llms.txt files.

    Agentic Engine Optimization. Google’s approach aligns with insights shared by Addy Osmani from Google Cloud AI about Agentic Engine Optimization. Osmani emphasizes creating web content that is semantically structured, token-efficient, and easy for AI to process.

    SEO vs. llms.txt. According to Google, creating llms.txt or similar files isn’t necessary for AI search success, as outlined in the guide on Mythbusting generative AI search. The AI systems can discover, crawl, and index a variety of file types encountered on the internet.

    John Mueller from Google responded to concerns about the role of llms.txt in a discussion with Lily Ray on Bluesky, stating that the use of these files is more for functionality and not directly linked to search engine optimization.

    Google’s Take on AI Agents. Besides llms.txt, Google’s Lighthouse guidelines place strong emphasis on accessibility and interface stability. The insight I gained is that AI agents heavily rely on the accessibility tree as their core data model, focusing on integrity and proper layout.

    Ultimately, while Google indicates llms.txt isn’t needed for search, including such files might be beneficial for adapting to Google’s evolving tools that prioritize machine readability.

    Further Exploration.

    Meet llms.txt, a proposed standard for AI website content crawling

    llms.txt isn’t robots.txt: It’s a treasure map for AI

    Does llms.txt matter? We tracked 10 sites to find out


    Inspired by this post on Search Engine Land.


    crushpress.ai community screenshot
  • Overcoming Google’s Biggest Crawling Challenges: A Personal Review

    Overcoming Google’s Biggest Crawling Challenges: A Personal Review

    Managing my website’s URLs efficiently is crucial to prevent crawlers from slowing it down. If you’re like me, you want your site to load fast, ensuring both visitors and search engines have a seamless experience.

    Just the other day, I listened to Google’s latest insights on their year-end report for 2025. It was fascinating to hear Gary Illyes discuss on the Search Off the Record podcast about the major crawling challenges Google faces, like faceted navigation and action parameters, which make up a whopping 75% of the issues.

    What’s the issue? Well, I’ve learned that crawling problems can seriously impact site performance, potentially making it unusable or inaccessible. Crawlers can sometimes get stuck in an infinite loop on a site, wreaking havoc on server performance.

    According to Gary, once a set of URLs is discovered, the crawler has to check a significant portion to determine its quality. By the time this is done, the damage is done—your site slows down dramatically.

    The Biggest Crawling Challenges Here’s what caught my attention as the major issues from the report:

    • 50% relate to faceted navigation. These are very common in e-commerce sites where endless filtering options exist for products based on size, color, price, etc.
    • 25% pertain to action parameters. These come from URL parameters that trigger actions instead of significantly changing page content.
    • 10% involve irrelevant parameters like session IDs or UTMs.
    • 5% are due to plugins or widgets that cause confusion by creating problematic URLs.
    • 2% encapsulate other “weird stuff”, which includes strange issues like double-encoded URLs.

    Why this matters to me is simple. A well-structured URL strategy keeps my server healthy, ensures quick page loads, and prevents search engines from misunderstanding which URLs should be indexed as canonical.

    The Podcast: Here’s where you can listen to the discussion yourself:


    Inspired by this post on Search Engine Land.


    crushpress.ai community screenshot
  • Understanding Google’s JavaScript Execution on Non-200 Pages

    Understanding Google’s JavaScript Execution on Non-200 Pages

    As I delve into the intricacies of JavaScript and SEO, I came across a fascinating update from Google that caught my attention. It’s about how Google handles JavaScript execution on pages that don’t return a typical 200 HTTP status code.

    Google recently updated their JavaScript SEO documentation to shed light on this topic. They explained that all pages with a 200 HTTP status code are automatically queued for rendering, irrespective of the presence of JavaScript.

    However, if a page returns a non-200 status code, like a 404 error page, rendering might be bypassed, which is something Google emphasized in their updated guidelines.

    Diving deeper, I discovered that Googlebot efficiently queues all pages with a 200 status code for rendering. This clarification came as a pleasant surprise to me as it paints a clearer picture of how Google handles such pages.

    In fact, the specific section in the documentation that got an update provides a visual explanation, and I appreciated the added clarity it brings.

    ```json
{
  "alt": "Googlebot rendering process description with HTTP status code 200.",
  "caption": "Exploring Googlebot's rendering process: Learn how HTTP status codes impact page indexing and rendering.",
  "description": "The image explains Google's rendering process for pages with a 200 HTTP status code. Pages without a meta tag to block indexing are queued for rendering. Googlebot uses headless Chromium to render and execute JavaScript, parsing the HTML for links and indexing them. A highlighted section stresses that all 200 status code pages are rendered, while non-200 status codes like 404 may be skipped. Keywords: Googlebot, rendering, HTTP status code, indexing."
}
```

    Google explained further that while pages with a 200 status code head to rendering, pages with other status codes might not meet the same fate.

    Google’s weekly updates to the JavaScript SEO documentation also included other significant changes. Notably, they clarified aspects like JavaScript’s role in canonicalization and cautioned against using JavaScript for noindex tags directly in the original page code.

    Why do we care about these updates? Well, understanding these nuances ensures I make informed decisions about my web pages. Ensuring my pages return a 200 status code is crucial; otherwise, Google might skip rendering them, which could negatively impact my website’s search ranking.


    Inspired by this post on Search Engine Land.


    crushpress.ai community screenshot