If Schema Is the Answer… What Was the Question?
Lately I’ve been watching a funny pattern in our AEO conversations. Someone gets picked up by an AI engine (awesome moment, cue the small victory dance)… and then the discussion immediately splits into two camps: Camp 1: “See? Schema’s optional.” Camp 2: “Quick — cover the whole site in JSON-LD before the engines notice!” It’s like we’ve collectively decided schema is the answer… without stopping to ask what problem we’re even trying to solve. Here’s the reality check: Early AI mentions are the digital equivalent of a polite nod — not a long-term relationship. AI engines are still in their “sure, bring whatever, I’m not picky” era. But give it time — systems mature, rules tighten, and suddenly the slob phase is over. If your content structure is wobbly and your entities don’t line up, dumping schema everywhere is basically putting lipstick on a website with an identity crisis. Schema isn’t magic. It’s not a shortcut. And it’s definitely not Flex Seal for SEO. It’s annotation. The wiring — not the blueprint. So before we crown schema as the savior, maybe we should ask: Are we using schema strategically… or just because it feels like the easiest lever to pull? Because when the engines start grading more strictly — and they will — the sites with thoughtful structure, clean entities, and intentional markup are the ones that will stand up straight. Everyone else? They’ll be untangling JSON like Christmas lights. Curious to hear others: Are we leaning too hard on markup because it’s measurable… and avoiding the deeper architectural work?