My SEO Week: Googles AI Made it More Nuanced and Fun

Alright, folks, David Park here, fresh off a particularly grueling but ultimately satisfying week of poking and prodding at Google’s latest quirks. And let me tell you, if you thought SEO was getting “easier” with AI, you’ve got another thing coming. It’s not easier, it’s just… different. More nuanced. And frankly, a lot more fun if you like a good puzzle.

Today, I want to talk about something that’s been nagging at me, and probably you too, as we all try to make sense of the new search reality. Forget the big, sweeping “AI will change everything” pronouncements for a moment. Let’s get practical. Let’s talk about micro-schema for ultra-specific, long-tail queries in an AI-driven SERP.

Yeah, it’s a mouthful. But stick with me. This isn’t about general product schema or bog-standard article markup. This is about surgically injecting granular detail into your content’s DNA so that when a user asks a question Google previously struggled to answer concisely, your site is the one giving the direct, authoritative response. This is about owning those tiny, high-intent cracks in the SERP that AI Overviews are just starting to explore.

The Elephant in the AI-Powered Room: The Shrinking Click

We all saw it coming, right? AI Overviews (or whatever Google decides to call them next week) are here to stay. And while they’re not always perfect – sometimes hilariously so – they are undeniably impacting traffic. My own analytics for several niche sites show a clear trend: for informational queries, direct clicks are down for some terms, even if impressions are holding steady or even rising. Users are getting their answers right there, in the AI snapshot.

This isn’t a death knell for SEO. It’s a wake-up call. It means our game has to evolve. If Google is going to answer the question directly, our job isn’t just to rank for the query; it’s to be the source Google trusts for that answer. And how do you become that trusted source, especially for queries that are incredibly specific?

By giving Google exactly what it needs, on a silver platter, in a language it understands perfectly: structured data. But not just any structured data. We’re talking micro-schema, tailored to the nth degree.

Why “Micro” Schema? Because AI Eats Details

Think about how AI models work. They crave data. They learn from patterns and relationships within that data. The more precise and explicitly defined information you give them, the better they can understand, summarize, and present it. Generic schema like Article or Product is good, but it’s a blunt instrument for the surgical precision AI Overviews are starting to demand.

Let me give you an example from my own experience. I run a tiny site about vintage camera repair. One of the most common, incredibly specific problems users search for is “how to replace light seals on a Canon AE-1 program.” This isn’t a general “camera repair” query. It’s hyper-specific. In the past, I’d rank with a detailed blog post, and users would click through.

Now, I’m seeing AI Overviews providing step-by-step instructions. If my content isn’t explicitly marked up to define those steps, with the right properties, Google might pull from a less authoritative source, or worse, generate a less accurate summary.

This is where micro-schema comes in. It’s about looking at your existing content, identifying those granular, step-by-step processes, those specific attributes of a product, those exact answers to a common problem, and then marking them up with the most precise Schema.org types and properties available. Even if there isn’t a perfect 1:1 match, we can combine and extend.

Example 1: The Step-by-Step Repair Guide

Let’s revisit my Canon AE-1 light seal example. My original blog post had headings like “Tools You’ll Need,” “Removing the Old Seals,” “Cutting New Seals,” and “Applying New Seals.” Good for humans, but not explicitly machine-readable as a sequence of actions.

Here’s how I started to adapt it using a combination of HowTo and its associated properties. I didn’t just wrap the whole article in HowTo. I focused on the actionable core.

<script type="application/ld+json">
{
 "@context": "https://schema.org",
 "@type": "HowTo",
 "name": "How to Replace Light Seals on a Canon AE-1 Program",
 "description": "A detailed guide for replacing the foam light seals on a Canon AE-1 Program 35mm film camera to prevent light leaks.",
 "image": {
 "@type": "ImageObject",
 "url": "https://www.clawseo.net/images/ae1-light-seal-kit.jpg",
 "width": "1200",
 "height": "800"
 },
 "totalTime": "PT1H30M", 
 "tool": [
 {
 "@type": "HowToTool",
 "name": "Precision Knife"
 },
 {
 "@type": "HowToTool",
 "name": "Tweezers"
 },
 {
 "@type": "HowToTool",
 "name": "Rubbing Alcohol"
 },
 {
 "@type": "HowToTool",
 "name": "Cotton Swabs"
 },
 {
 "@type": "HowToTool",
 "name": "Light Seal Foam Kit for Canon AE-1"
 }
 ],
 "step": [
 {
 "@type": "HowToStep",
 "name": "Prepare Your Workspace",
 "text": "Gather all tools and materials. Work in a clean, well-lit area. Remove the lens and battery from the camera.",
 "image": {
 "@type": "ImageObject",
 "url": "https://www.clawseo.net/images/ae1-workspace.jpg"
 }
 },
 {
 "@type": "HowToStep",
 "name": "Remove Old Light Seals",
 "text": "Carefully use a precision knife or tweezers to pick out the old, degraded foam light seals from the camera back channels and mirror bumper. Be gentle to avoid scratching the camera body. Use rubbing alcohol on a cotton swab to clean any sticky residue.",
 "image": {
 "@type": "ImageObject",
 "url": "https://www.clawseo.net/images/ae1-remove-seals.jpg"
 }
 },
 {
 "@type": "HowToStep",
 "name": "Cut New Light Seals (if not pre-cut)",
 "text": "If your kit is not pre-cut, measure the channels in your camera back and mirror bumper. Carefully cut the new light seal foam to the appropriate lengths and widths using your precision knife. Ensure clean, straight cuts.",
 "image": {
 "@type": "ImageObject",
 "url": "https://www.clawseo.net/images/ae1-cut-seals.jpg"
 }
 },
 {
 "@type": "HowToStep",
 "name": "Apply New Light Seals",
 "text": "Starting with the mirror bumper seal, carefully peel the backing from your new foam strip and gently press it into place. Repeat for the channels in the camera back. Ensure a snug fit without stretching the foam. Close the camera back and let it sit for a few hours for the adhesive to set.",
 "image": {
 "@type": "ImageObject",
 "url": "https://www.clawseo.net/images/ae1-apply-seals.jpg"
 }
 }
 ],
 "supply": [
 {
 "@type": "HowToSupply",
 "name": "Light Seal Foam Kit for Canon AE-1"
 }
 ]
}
</script>

Notice the level of detail: totalTime, individual tool items, and each step having its own name and text, even an optional image. This isn’t just a list; it’s a structured narrative that an AI can easily digest and present as a concise, step-by-step answer.

Example 2: Specific Product Compatibility

Another challenge I face is with product compatibility. People often search for things like “lens cap size for Nikon F3” or “film type for Olympus Trip 35.” These are tiny details, but crucial for users making purchase decisions. My product pages might list this info, but again, it’s often buried in descriptions.

For product pages, beyond the standard Product schema, I’ve started using more specific properties like isAccessoryOrSparePartFor or custom properties when Schema.org doesn’t have an exact match (though be careful with custom properties; Google prefers standard ones). For the lens cap example, I’d incorporate it like this:

<script type="application/ld+json">
{
 "@context": "https://schema.org",
 "@type": "Product",
 "name": "Nikon F3 Front Body Cap (Genuine)",
 "image": "https://www.clawseo.net/images/nikon-f3-bodycap.jpg",
 "description": "Original Nikon F3 front body cap, protects sensor/mirror box from dust. Essential for camera storage.",
 "offers": {
 "@type": "Offer",
 "priceCurrency": "USD",
 "price": "19.99",
 "availability": "https://schema.org/InStock",
 "url": "https://www.clawseo.net/shop/nikon-f3-body-cap"
 },
 "sku": "NikonF3BC-001",
 "mpn": "XXXXXX",
 "brand": {
 "@type": "Brand",
 "name": "Nikon"
 },
 "isAccessoryOrSparePartFor": {
 "@type": "Product",
 "name": "Nikon F3 Camera"
 },
 "additionalProperty": [
 {
 "@type": "PropertyValue",
 "name": "Compatible Lens Mount",
 "value": "Nikon F Mount"
 },
 {
 "@type": "PropertyValue",
 "name": "Lens Cap Diameter (mm)",
 "value": "62"
 }
 ]
}
</script>

Here, isAccessoryOrSparePartFor explicitly links it to the Nikon F3. And while “Lens Cap Diameter” isn’t a standard Schema.org property, I’ve used additionalProperty with PropertyValue to define it. The trick here is consistency. If you use “Lens Cap Diameter (mm)” once, use it everywhere for the same concept. Google’s AI can learn these patterns, even from custom properties, if they’re applied consistently across your site.

Beyond the Obvious: Finding Micro-Schema Opportunities

So, how do you find these micro-schema opportunities on your own site? It’s not always about creating brand new content; often, it’s about enhancing what you already have.

1. Audit Your “How-To” Content

• Look for any article that explains a process, a troubleshooting guide, or even a recipe.
• Break down the content into distinct steps, tools, and materials.
• Use the HowTo schema type with HowToStep, HowToTool, HowToSupply, and HowToDirection.
• Consider adding totalTime, estimatedCost, and video properties if applicable.

2. explore Your Product Attributes

• Go beyond basic price and availability. What are the unique, highly specific features or compatibilities of your products?
• For electronics, think about connectivity, battery life, specific ports, or supported standards.
• For clothing, consider material composition percentages, specific fit types, or care instructions.
• Use PropertyValue within additionalProperty for highly specific attributes not covered by standard Schema.org.
• Explore more specific product types like SoftwareApplication, Vehicle, or Book if they fit your niche better than generic Product.

3. FAQ Pages are Goldmines

• If you have an FAQ page, convert it using FAQPage schema. This is low-hanging fruit.
• But also, look at individual questions. Can any of those questions be answered with a step-by-step process (HowTo)? Or by pointing to a specific attribute of a product (Product with additionalProperty)?
• Sometimes, a simple Question and Answer schema can be immensely powerful for direct answers in AI Overviews.

4. Review Your Data from Search Console and Analytics

• Look at your “Queries” report in Google Search Console. Filter for long, conversational queries that contain “how to,” “what is,” “best way to,” “compatible with,” “size for,” etc.
• These are the exact queries that AI Overviews are designed to answer. If you’re ranking for them but not getting clicks, it’s a strong signal to enhance your structured data.
• Check your analytics for pages with high impressions but low click-through rates, especially for informational content.

My Workflow for Implementing Micro-Schema

This isn’t a “set it and forget it” task. It’s an ongoing process. Here’s a simplified version of my personal workflow:

1. Identify Target Content: I use GSC and analytics to find pages with high potential for direct answer snippets or AI Overviews. Long-tail informational queries are my primary focus.
2. Analyze Content: I read the content with a critical eye, asking: “What specific, factual questions does this content answer? What processes does it describe? What attributes does it define?”
3. Schema.org Research: I head to Schema.org and start exploring. I look for the most specific types and properties that match the extracted information. Sometimes it’s a perfect match, other times it’s combining types or using additionalProperty.
4. Draft the JSON-LD: I prefer JSON-LD for its flexibility. I hand-code or use a snippet generator to create the structured data.
5. Validate: ALWAYS use Google’s Rich Results Test and Schema Markup Validator. This is non-negotiable. Debugging is easier here than finding out later that Google ignored your markup.
6. Implement: Add the JSON-LD to the <head> or <body> of the relevant page. For WordPress, plugins can help, but I often prefer direct insertion via a theme’s functions.php or a custom plugin for more control.
7. Monitor: Keep an eye on GSC’s “Rich Results” report to ensure Google is picking up your new schema. Also, watch for changes in impressions, clicks, and average position for those target queries.

A quick note on implementing: if you’re using a CMS, be mindful of how it handles structured data. Some themes and plugins add their own basic schema. Make sure your micro-schema isn’t conflicting or being overwritten. Sometimes, it’s better to disable generic schema generated by a plugin and implement your own precise version.

Actionable Takeaways for a Smarter SEO Strategy

The AI-driven search space isn’t about throwing your hands up in despair. It’s about being more precise, more explicit, and more helpful to both users and search engines. Here’s what you should be doing:

• Embrace Specificity: General schema is good, but micro-schema for specific details is where the future of owning AI Overviews lies.
• Audit for How-To & Product Attributes: These are your prime targets for granular structured data. Think about every step, every tool, every specific product feature.
• Utilize HowTo and additionalProperty: These are powerful tools for communicating complex information simply.
• Consistency is Key: If you use a custom property name, stick to it site-wide. Google’s AI can learn from consistent patterns.
• Validate, Validate, Validate: Never deploy structured data without testing it first.
• Monitor & Adapt: The SERP is dynamic. What works today might need tweaking tomorrow. Keep an eye on your performance and be ready to refine your approach.

Don’t just optimize for clicks anymore; optimize to be the definitive answer. When Google’s AI is looking for the most accurate, concise, and structured information to present to a user, make sure it’s finding yours. That’s how you carve out your niche and maintain your visibility in this brave new world of search.

Now, if you’ll excuse me, I’ve got a vintage lens to mark up with its exact filter thread size and aperture blade count. The small details, folks. They matter more than ever.

🕒 Last updated: March 26, 2026  ·  Originally published: March 14, 2026