Schema Markup for AI Search: Which Types Still Matter

For AI search, the schema types worth adding first are Organization (who you are) and LocalBusiness (where and when you serve customers), written in JSON-LD and matching what's visible on the page. FAQPage markup is still valid but rarely shows as a rich result now, and HowTo markup no longer earns rich results in Google at all.

Schema markup is a small block of code that labels the facts on your page, your business name, address, opening hours, prices, questions and answers, so machines don't have to guess. It won't rescue weak content, and Google says no special markup is required to appear in AI Overviews. But it removes ambiguity, and ambiguity is what makes AI systems skip you or describe you wrongly. This guide sits within our broader explainer on AEO, GEO and ranking in AI answers.

Does schema markup actually help you appear in AI answers?

Indirectly, yes; as a magic switch, no. Structured data helps search engines understand and trust the facts on your page, and AI features in Google are built on top of that same index.

What schema does well:

• Confirms identity. It ties your website to your business name, logo, phone number and social profiles, which helps search engines treat you as one clear entity.
• States facts unambiguously. "Open 9–6 Monday to Saturday" in a paragraph can be misread; openingHoursSpecification cannot.
• Unlocks some rich results in classic search, such as review snippets or business details, which can lift clicks.

What it doesn't do: make a page relevant to a query it doesn't answer, or override what the visible text says. If your markup claims something the page doesn't show, Google treats that as a guideline violation, not a boost.

Which schema types should a business add first?

Start with the two that describe your business, then add page-level types only where the page genuinely contains that content.

If you only have an hour, mark up your Organization and LocalBusiness details correctly and stop there. Those two do the most to help machines understand who you are.

How do you add Organization schema?

Place a JSON-LD script on your homepage that names the business, its URL, logo and official profiles. JSON-LD is the format Google recommends because it sits in one block rather than being woven through your HTML.

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Example Studio",
  "url": "https://www.example.com",
  "logo": "https://www.example.com/logo.png",
  "sameAs": [
    "https://www.linkedin.com/company/your-business-name",
    "https://www.instagram.com/your-business-name"
  ],
  "contactPoint": {
    "@type": "ContactPoint",
    "telephone": "+61-2-0000-0000",
    "contactType": "sales"
  }
}

The sameAs list matters more than people think. It tells search engines that your LinkedIn page, Instagram account and website are the same organisation, which strengthens your identity across the web. Only list profiles you actually control and keep active.

How do you add LocalBusiness schema?

Use the most specific subtype that fits, and copy your name, address and phone exactly as they appear on your Google Business Profile. Mismatched details are a common and easily avoided local SEO problem.

{
  "@context": "https://schema.org",
  "@type": "Dentist",
  "name": "Example Dental Care",
  "url": "https://www.example.com",
  "telephone": "+91-00000-00000",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "12 Example Road",
    "addressLocality": "Patna",
    "postalCode": "800001",
    "addressCountry": "IN"
  },
  "openingHoursSpecification": [{
    "@type": "OpeningHoursSpecification",
    "dayOfWeek": ["Monday","Tuesday","Wednesday","Thursday","Friday","Saturday"],
    "opens": "09:00",
    "closes": "18:00"
  }],
  "priceRange": "₹₹"
}

For service-area businesses without a public shopfront, you can use areaServed instead of displaying a street address, mirroring how you've set up your profile. Our guide to setting up Google Business Profile for a service-area business explains that side.

Is FAQPage schema still worth adding?

Add it when the page already has a genuine, visible FAQ, but don't expect the expandable FAQ snippets you might remember. Google restricted FAQ rich results in 2023 to a small set of well-known authoritative government and health websites.

So why bother? The markup still states each question and answer cleanly, and other systems that read structured data may use it. The cost is low if your CMS can generate it automatically from the FAQ block. The rules:

• Every question and answer in the markup must appear on the page.
• Write answers for customers, not keywords. Two to four sentences each is plenty.
• Don't add FAQ markup to pages where users submit answers (that's QAPage territory).

The FAQ section itself is far more valuable than its markup. Well-written question-and-answer pairs are exactly the passages AI assistants lift, as our post on how Perplexity chooses its sources explains.

What happened to HowTo schema?

Google stopped showing HowTo rich results in 2023, so marking up step-by-step guides no longer changes how they look in search. The markup is still valid schema.org vocabulary and won't harm you, but it's not a priority.

What still helps a how-to page is the structure underneath: numbered steps in an ordered list, a short summary of what you'll need, and a clear heading for each stage. Machines can read an ordered list without extra code.

How do you implement and test schema step by step?

Generate it, place it, validate it, then keep it in sync with your content. Here is a dependable process for any site.

1. List your facts. Business name, legal name if different, logo URL, phone, address, hours, service area, social profiles.
2. Choose the types. Organization sitewide, LocalBusiness subtype on the homepage or each location page, BreadcrumbList on inner pages, Article on posts.
3. Write JSON-LD. Many CMS plugins generate it; custom sites can output it from the same data that renders the page, so the two never drift apart.
4. Validate. Run pages through Google's Rich Results Test and the Schema Markup Validator from schema.org. Fix errors; review warnings.
5. Monitor. Search Console's enhancement reports flag markup problems after Google crawls the pages.
6. Update with changes. New phone number, new hours, new address: update the markup the same day you update the page.

On a custom build, the cleanest approach is to generate markup from the same content source as the page. That way, someone editing their opening hours in the CMS updates both at once, which removes the most common cause of mismatches.

What schema mistakes should you avoid?

Most problems come from markup that says more than the page does.

• Fake or self-serving reviews. Marking up reviews you wrote yourself, or aggregate ratings that don't appear on the page, breaks Google's guidelines.
• Wrong business type. A generic LocalBusiness is fine; the wrong specific subtype is misleading.
• Inconsistent details. A different phone number in schema, on the page and on your Google Business Profile confuses everyone.
• Copy-pasted markup across locations. Each location page needs its own address and hours.
• Stale markup. Old prices or discontinued services left in code long after the page changed.

For the content side of the same problem, our beginner's guide to answer engine optimisation covers how to make the visible page itself worth citing.

Frequently asked questions

Do I need schema markup to appear in Google AI Overviews?

No. Google's documentation on AI features says there are no extra technical requirements beyond being indexed and eligible to show a snippet. Schema helps search engines understand your page, but clear, helpful content is what gets used.

Can schema markup hurt my site?

Accurate markup won't. Markup that misrepresents the page, such as hidden content or fabricated reviews, can lead Google to ignore your structured data or apply a manual action for spammy markup.

Should every page have FAQ schema?

Only pages with a real, visible FAQ section. Adding questions just to generate markup creates thin content and offers little benefit now that FAQ rich results are heavily restricted.

What's the difference between Organization and LocalBusiness schema?

Organization describes any business or brand. LocalBusiness is a more specific type for businesses customers visit or that serve a defined area, and it adds properties like address, opening hours and price range. Many local firms use both.

Can I add schema without a developer?

Usually. Popular CMS platforms have plugins that generate the common types from settings you fill in. Custom requirements, multiple locations or syncing markup with live data are where developer help pays off.

Get your structured data right the first time

We can add Organization, LocalBusiness and page-level markup that is generated from the same content as your pages, so the details stay in sync. If you'd like us to check your existing markup or add it properly, see our services or request a fixed-price quote.