Blog

How AI Sees Your Page: Content the Crawler Can't Find

A product page has a detailed description in one tab, a spec table in another and two hundred reviews below – and when someone asks an AI assistant about the product, the answer is based on two sentences from the meta description. Intuition says display: none is to blame. That's almost never true: crawlers read HTML, they don't look at the rendered page, so hiding something with styles doesn't bother them. What bothers them is content that isn't in the HTML at all – rendered conditionally, loaded on scroll, inserted by CSS or baked into an image. I show exactly where it gets lost and how to check it with one command.

AI Writes CSS Like It's 2015 – and How to Change That

You ask an AI assistant to fix a menu that hides under the hero section, and you get z-index: 9999 !important. You ask for a card that breaks in a narrow sidebar – you get another media query. The code works, but it looks like it came from a tutorial a decade ago, and every such fix makes the next one harder. It's not a weak-model problem: it's a consequence of what CSS the model learned from and what it can't see when it answers. I show where these habits come from, how to recognize them, and how a rules file and access to the real page change what the model writes.