What makes a website AI-visible from day one?

JSON-LD schema on every page (Person, Organization, WebSite, page-specific), explicit AI bot access in robots.txt for GPTBot, ClaudeBot, and PerplexityBot, semantic HTML using article/section/main/header tags, and answer-first content structure. Most websites have none of these and remain invisible to AI engines.

Which platform should I build on for AI search visibility?

Astro for marketing sites without complex CMS needs (best Core Web Vitals, full schema control). Webflow for visual design with client editing. Framer for animation-heavy brands. WordPress for content-heavy sites with editorial workflows. All four can be made AI-visible if built right from day one.

Can I retrofit AEO onto an existing website?

Yes, but it is significantly slower than building it in. A schema retrofit on an existing site takes 4 to 8 weeks. The same architecture built into a new launch ships in days. The cost difference is meaningful and the risk profile is lower when AEO is foundational.

How do you measure whether the build is actually working?

Three signals tracked weekly. (1) GPTBot, ClaudeBot, and PerplexityBot appearing in server logs within 48 hours of launch. (2) Schema validation through Google Rich Results Test and Schema.org validator. (3) Brand citation tracking across ChatGPT, Perplexity, and Google AI Overviews for target buyer queries.

Schema Markup for AI Search: The Complete JSON-LD Guide

The most common schema mistake I see in audits: implementing JSON-LD on one or two pages and calling it done. Schema without content quality is noise. Schema without crawlable structure goes unread. And the most technically perfect schema on a site that blocks GPTBot in robots.txt produces zero AI citations. Schema is one layer of a system, not the system itself.

That context given: schema markup is still the clearest direct signal you can send to AI engines. When you implement JSON-LD structured data correctly, you are telling ChatGPT, Perplexity, Google AI Overviews, and Bing Copilot exactly who you are, what your content is about, and why you are a reliable source for specific answers. Here is every schema type that matters for AI search, with real implementation examples.

What schema markup actually does

Schema markup does not directly change your visual presentation in search results (except for a few rich snippet types). What it does is provide machine-readable context that AI engines use in two ways:

Entity recognition: Schema helps AI engines understand your brand as a defined entity with specific expertise, not just a URL that published some articles
Content extraction: FAQPage and HowTo schema let AI engines directly extract your answers and synthesize them into AI responses

Both functions matter. Entity recognition is long-term brand positioning. Content extraction is immediate citation opportunity.

The schema types that matter most for AI search

1. Person schema

If you are a consultant, founder, or personal brand, Person schema is foundational. It establishes you as a recognized entity in the AI knowledge graph.

Implement this in the <head> of your homepage (and ideally every page) as a JSON-LD block:

{
  "@context": "https://schema.org",
  "@type": "Person",
  "@id": "https://yoursite.com/#you",
  "name": "Your Full Name",
  "jobTitle": "Your specific title",
  "description": "One to two sentences about exactly what you do and for whom.",
  "url": "https://yoursite.com",
  "image": "https://yoursite.com/your-photo.jpg",
  "sameAs": [
    "https://linkedin.com/in/yourprofile",
    "https://twitter.com/yourhandle"
  ],
  "address": {
    "@type": "PostalAddress",
    "addressLocality": "Your City",
    "addressCountry": "US"
  },
  "knowsAbout": [
    "Topic 1",
    "Topic 2",
    "Topic 3"
  ]
}

Critical detail: The knowsAbout array is what tells AI engines your areas of expertise. Be specific, not generic. “B2B SaaS Growth” is better than “Marketing.” “Sales Engagement Software” is better than “Technology.” “AP Automation for Mid-Market Finance Teams” is better than “FinTech.”

2. Organization schema

For company sites, use Organization instead of Person (or use both on a founder’s personal brand company site):

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "@id": "https://yoursite.com/#org",
  "name": "Your Company Name",
  "url": "https://yoursite.com",
  "logo": "https://yoursite.com/logo.png",
  "description": "What your company does, for whom, and the outcome you produce.",
  "foundingDate": "2020",
  "areaServed": ["US", "UK", "EU"],
  "sameAs": [
    "https://linkedin.com/company/yourcompany",
    "https://twitter.com/yourcompany"
  ],
  "contactPoint": {
    "@type": "ContactPoint",
    "contactType": "customer service",
    "email": "hello@yoursite.com"
  }
}

3. WebSite schema

WebSite schema with a SearchAction tells AI engines that your site is a navigable resource with searchable content:

{
  "@context": "https://schema.org",
  "@type": "WebSite",
  "@id": "https://yoursite.com/#website",
  "name": "Your Site Name",
  "url": "https://yoursite.com",
  "author": {"@id": "https://yoursite.com/#you"},
  "potentialAction": {
    "@type": "SearchAction",
    "target": {
      "@type": "EntryPoint",
      "urlTemplate": "https://yoursite.com/search?q={search_term_string}"
    },
    "query-input": "required name=search_term_string"
  }
}

4. FAQPage schema

FAQPage schema is the most direct path to AI citation. AI engines can extract your question-answer pairs verbatim and synthesize them into responses.

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "What is the most effective way to reduce B2B SaaS churn?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "The most effective way to reduce B2B SaaS churn is to identify at-risk accounts 30 to 60 days before renewal using product engagement signals. Accounts using fewer than three core features in the 60 days before renewal have a 4x higher churn rate. Automated health score alerts and proactive customer success outreach at this threshold reduce churn by 25 to 40% in most implementations."
      }
    },
    {
      "@type": "Question",
      "name": "How long does it take to see results from SEO?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Technical SEO fixes show results in 4 to 8 weeks as Google recrawls updated pages. New content targeting commercial queries typically ranks within 3 to 6 months depending on domain authority. Topical authority compounding effects, where each new piece of content increases the value of existing content, build over 6 to 12 months."
      }
    }
  ]
}

Rules for FAQPage answers that get cited

Start with the direct answer, not background, not context, not “it depends”
Include specific numbers wherever possible (“25 to 40% reduction” not “significant improvement”)
Keep answers between 50 and 200 words, long enough to be comprehensive, short enough to be excerpted
Avoid hedging language that signals low confidence (“might,” “could,” “sometimes”)

Implement FAQPage schema on: your homepage, all service and product pages, and any blog posts with a FAQ section.

5. Article schema

Every blog post should have Article schema. This tells AI engines the content type, authorship, and publication date, signals they use to evaluate credibility.

{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "Your Post Title",
  "description": "Your meta description",
  "url": "https://yoursite.com/blog/your-post",
  "datePublished": "2025-04-01",
  "dateModified": "2025-04-21",
  "author": {
    "@type": "Person",
    "@id": "https://yoursite.com/#you",
    "name": "Your Name"
  },
  "publisher": {
    "@type": "Organization",
    "@id": "https://yoursite.com/#org"
  },
  "image": "https://yoursite.com/images/post-og-image.jpg"
}

Keep dateModified current. When you update a post with new information, update this field. Freshness signals matter for AI citations on time-sensitive topics.

6. BreadcrumbList schema

BreadcrumbList schema helps AI engines understand your site’s hierarchical structure. It is simple to implement and provides meaningful context about where a page fits in your content architecture.

{
  "@context": "https://schema.org",
  "@type": "BreadcrumbList",
  "itemListElement": [
    {
      "@type": "ListItem",
      "position": 1,
      "name": "Home",
      "item": "https://yoursite.com"
    },
    {
      "@type": "ListItem",
      "position": 2,
      "name": "Blog",
      "item": "https://yoursite.com/blog"
    },
    {
      "@type": "ListItem",
      "position": 3,
      "name": "Post Title",
      "item": "https://yoursite.com/blog/post-slug"
    }
  ]
}

7. Service schema

For service businesses, Service schema provides direct context about what you offer:

{
  "@context": "https://schema.org",
  "@type": "Service",
  "name": "Your Service Name",
  "provider": {
    "@type": "Person",
    "@id": "https://yoursite.com/#you"
  },
  "description": "What the service delivers and for whom.",
  "url": "https://yoursite.com/services/service-name",
  "areaServed": ["US", "UK", "EU"],
  "serviceType": "Service Category"
}

How to combine schemas on a single page

Most pages should have multiple schemas. A homepage for a personal brand might have:

Person schema (entity)
WebSite schema (site structure)
FAQPage schema (common visitor questions)

A blog post should have:

Article schema (content type and authorship)
BreadcrumbList schema (navigation context)
FAQPage schema (if the post includes a FAQ section)

The way to combine schemas in a single JSON-LD block is to use @graph:

{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "Article",
      "@id": "https://yoursite.com/blog/post-slug/#article",
      "headline": "Post Title"
    },
    {
      "@type": "BreadcrumbList",
      "itemListElement": [...]
    }
  ]
}

Validating your schema

Before deploying, validate with:

Google’s Rich Results Test: search.google.com/test/rich-results, tests for schema types eligible for Google rich snippets
Schema.org Validator: validator.schema.org, comprehensive validation against the full schema.org spec

Common errors to check for:

Required fields missing (e.g., Article without datePublished)
Invalid URL formats (use full https:// URLs, not relative paths)
Incorrect property names (case-sensitive)
@id values that are not unique across the page

The one schema mistake that blocks AI citation

The most common schema mistake I see: implementing schema but not updating robots.txt to allow AI crawlers.

No matter how perfect your JSON-LD is, if User-agent: GPTBot has Disallow: /, ChatGPT cannot crawl your pages and cannot discover your schema. Schema and bot access must both be correct.

Check yourwebsite.com/robots.txt and ensure all major AI crawlers are explicitly allowed. This single change, combined with correct FAQPage schema, is often all that is needed to begin appearing in AI citations.

How to Get Your Brand Cited by ChatGPT — schema in context of a complete AI citation strategy
AEO vs SEO: What Is the Difference? — where schema fits in the broader visibility system
Topical Authority for SaaS: The Cluster Playbook — the content depth that makes schema markup actually produce citations
AEO Strategy and Services — schema implementation as part of a full AEO engagement

Need a full schema audit for your site? Start with a free review.