How Structured Data Helps AI Understand and Cite Your Business #

Google's Knowledge Graph runs on structured data — and so does every AI answer engine citing sources in 2026. If your business has no schema markup and no entity footprint, ChatGPT, Perplexity, and Google AI Overviews will cite your competitor instead of you. The fix is not a mystery; it's a technical checklist that most businesses have never worked through.

I'm William Spurlock, AI Solutions Architect and founder of a hybrid AI automation + premium web design studio. I've been doing SEO since 2021 — now AEO/AIO/GEO. The most common structured data question I get from business owners is the primary query here: what is the Google Knowledge Graph and how do I get my business in it? The answer starts at schema.org, runs through Wikidata, and ends with a consistent entity footprint across the web.

This post is the most technical in this AI Visibility series — JSON-LD code blocks appear below and are intentional. You don't need to write them yourself; you need to understand what they do, verify they're on your site, and make sure they're not broken. Those are three different states most business owners have never checked.

---

What Is the Google Knowledge Graph and How Do I Get My Business in It? #

The Google Knowledge Graph is a structured database of real-world entities — businesses, people, places, products, events — and the verified relationships between them. Getting your business into it means becoming a recognized entity, not just a website. The Knowledge Graph powers Knowledge Panels (the info card on the right side of Google results) and is a primary data source that Google's AI Overviews draw from when generating cited answers about brands, founders, and local businesses.

Schema.org markup is not the only path into the Knowledge Graph, but it is the most direct signal you control. When you add Organization, LocalBusiness, or Person structured data to your website using JSON-LD — Google's recommended implementation format, per Google Search Central's structured data documentation — you're giving Google's crawlers a machine-readable entity record. That record gets cross-referenced with other signals: Google Business Profile, Wikidata entries, Wikipedia citations, news mentions, and third-party directory listings.

The pattern I see consistently across client work includes four elements:

1. Verified Google Business Profile — the strongest single entry point for local businesses
2. JSON-LD Organization or Person schema on your homepage with sameAs properties linking to your authoritative profiles
3. Consistent NAP data (Name, Address, Phone) across directories, citations, and social profiles — mismatches fracture your entity signal
4. External entity mentions — press coverage, Wikipedia/Wikidata entries, and industry database listings

The sameAs property is the connector Google uses to unify these signals. If your schema points to your LinkedIn, Wikidata Q-number, Crunchbase profile, and Twitter/X handle, Google can triangulate all those mentions as the same entity. Without sameAs, that cross-referencing is probabilistic. With it, the connection is explicit and machine-readable.

One non-obvious fact: the Knowledge Graph is not a static database you get added to once. It's a continuously updated inference system. Google re-evaluates entity signals every crawl cycle. Cleaning up inconsistent NAP data and adding missing sameAs targets can trigger Knowledge Graph updates within weeks on sites Google crawls frequently.

A common question I hear: "If we already rank well in Google, don't we already have this?" Not necessarily. Ranking signals (backlinks, content relevance, PageRank) and entity signals (structured data, Knowledge Graph inclusion, Wikidata entries) are separate systems that partially overlap but are not the same. A site can rank #1 for a competitive keyword with zero JSON-LD, no Knowledge Panel, and no Wikidata entry. That same site will get cited in AI answers far less often than a competitor at position #4 who has clean entity infrastructure. This is the core reason AI visibility and traditional SEO require different playbooks.

One more mechanism worth knowing: Google AI Overviews use Knowledge Graph entity cards directly when answering questions about specific businesses, people, and products. If your business has a Knowledge Graph entry with verified attributes — founding date, description, headquarters, founders, services — those attributes can appear in AI Overview answers to queries like "What does [your business] do?" or "Who founded [your business]?" This is attribution your competitors cannot replicate by just having good blog content. It requires entity infrastructure, and schema markup is the fastest on-site path to building it.

For local businesses, this entity layer is especially high-stakes. When someone asks "best AI automation consultant near [city]" in AI Mode or Google AI Overviews, the results draw from both local business schema (LocalBusiness with service area data) and Knowledge Graph entity confidence. A business with verified entity infrastructure consistently outperforms competitors with better traditional SEO but no structured entity presence in those AI-generated local answer packs.

---

Does Wikipedia or Wikidata Presence Affect AI Citation? #

Yes — Wikipedia and Wikidata are tier-one sources for AI knowledge bases. Presence in either significantly increases the probability that AI models will have accurate information about your business and will cite it with confidence. This is not a secondary signal. It is foundational.

Here's the mechanism: Large language models including GPT-4o and Claude were trained on Wikipedia data. They also retrieve information at runtime via retrieval-augmented generation (RAG), and Wikidata is one of the primary structured knowledge sources those retrieval layers query. A Wikidata entry gives your entity a permanent Q-number — a unique identifier that the Knowledge Graph, DBpedia, and academic citation databases all reference. When an AI system encounters your business name in a query, that Q-number is what lets it confidently associate your name with specific, verified attributes.

For most small and mid-size businesses, a Wikipedia article is not realistic. Wikipedia's notability guidelines require significant coverage in reliable, independent secondary sources. That bar is genuinely high. Attempts to create promotional or unduly self-serving Wikipedia articles get flagged and deleted fast — and a deleted article can hurt your entity standing with Google.

Wikidata has a lower bar. If your business has a Google Business Profile, a verified online presence, and any external coverage, a Wikidata entry is usually justifiable. You create a structured item with your business name, description, industry, founding date, location, and — the critical part — sameAs references to your official site, Google Knowledge Graph ID, LinkedIn company page, and social profiles. That Wikidata item becomes a node in the entity graph that AI retrieval systems actively query.

When creating a Wikidata item, the most impactful properties to fill in are:

• instance of — business or privately held company or the most specific applicable type
• official website — your canonical domain, no trailing slash inconsistencies
• LinkedIn company page — adds a major authoritative sameAs signal
• founded by — links your founder as a Person entity in Wikidata, creating a bidirectional entity relationship
• country and headquarters location — geographic entity signals that help with local AI citations
• industry — links to the Wikidata concept for your industry (e.g., Q11089770 for "web design")
• described at URL — link to your Google Business Profile and any major directory listings

The founded by property is worth calling out specifically: it creates a linked Person entity record for your founder, which gives AI systems a structured relationship between the company and the person running it. When ChatGPT is asked "who runs [your business]?", it can answer correctly if this relationship exists in Wikidata, even if it never found that information on your website.

My take: Wikidata is the most underused AI visibility signal available to business owners right now. Most of your competitors have no entry. Getting one, linking it correctly, and maintaining it puts you in the structured knowledge layer that AI systems pull from — regardless of whether your traditional SEO ranking is perfect.

For a deeper look at how external press coverage and third-party mentions feed into AI citation signals, read Digital PR for AI Visibility: Getting Mentioned Where AI Reads.

---

How Do I Get a Google Knowledge Panel for My Personal Brand or Business? #

A Google Knowledge Panel is not something you directly apply for — it appears when Google's systems determine your entity has enough verified signals to surface. The path is building those signals deliberately, then claiming the panel once it appears. Per Google Search Central's Knowledge Panel guidance, the panel is generated automatically from Knowledge Graph data.

The fastest path for a personal brand or small business:

1. Claim your Google Business Profile if you're a local or service-area business — this is the strongest single entity signal for physical-world businesses
2. Add Organization or Person JSON-LD with sameAs links on your homepage pointing to every authoritative profile: LinkedIn, Twitter/X, YouTube, Crunchbase, GitHub if relevant
3. Create a Wikidata entry for yourself or your business with all available structured properties filled in correctly
4. Build external entity mentions: author bylines, podcast appearances, press coverage in outlets Google already trusts, industry association listings
5. Once a panel appears, use Google's Claim this Knowledge Panel feature to become the verified owner and request corrections to inaccurate information

The timeline is not instant. In my client work, it typically takes 8–16 weeks from implementing clean schema and entity signals to seeing a Knowledge Panel emerge — faster when existing press coverage or a Google Business Profile is already in good standing. The fastest I've seen it happen is about 5 weeks, for a founder with several podcast features and a clean Wikidata entry added the same week as the schema overhaul.

What accelerates it: consistent entity mentions across sources that Google already treats as authoritative (major news outlets, LinkedIn, Wikipedia ecosystem, industry associations). What slows it: NAP inconsistencies — your business name spelled three different ways across directories is the single most common blocker I see.

For personal brands specifically, there's a faster path: author bylines. If you write for publications that are already in Google's trusted source list — industry news sites, trade magazines, recognized blogs — each byline is an entity mention that links your name to verified content. Google's author markup documentation supports Person schema on Article pages, meaning each piece you publish can carry a machine-readable author entity record. This stacks quickly: 5–10 bylines on respected publications, each with Person schema pointing back to your website, significantly accelerates Knowledge Panel appearance for personal brands.

The claiming step is often skipped: once your Knowledge Panel appears, go to support.google.com/knowledgepanel and request verified owner status. This lets you add links, correct inaccurate information, and update your featured image. Verified panels are more stable and get updated faster when you make changes to your underlying entity signals.

---

The Highest-Value Schema Types for AI Visibility #

The schema types that move the needle for AI citation are the ones that produce machine-readable answers to the exact questions AI engines get asked. Organization, Person, FAQPage, Product, Article, and HowTo cover 90% of the use cases for business owners targeting AI Overviews and cited answers. Here's the full picture:

Schema Type	Primary Use Case	AI Visibility Impact
Organization	Business entity definition, sameAs links, contact info, logo	Directly feeds the Knowledge Graph; high impact for brand citation in AI
Person	Founder/expert entity definition, credentials, social profiles	Critical for personal brand AI citation; establishes author authority signal
FAQPage	Q&A content matching exact user queries	Direct extraction source for Google AI Overviews and Perplexity answer boxes
Product	Product details, pricing, availability, reviews	Cited in AI shopping answers; enables rich product results
Article / BlogPosting	Content publication entity, author, date, publisher	Trust signal for AI citation; datePublished is a freshness signal
HowTo	Step-by-step procedures	High match rate for "how to" AI queries; steps cited verbatim in AI answers
BreadcrumbList	Site structure and navigation hierarchy	Parsing signal for AI; helps with entity-to-content association
Speakable	Markup for voice-readable sections	Emerging AI signal; relevant for Google Assistant and voice search citation

JSON-LD: Organization Schema #

Add this inside a <script type="application/ld+json"> block in your page <head>. This is the entity record that connects your business to the Knowledge Graph:

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Your Business Name",
  "url": "https://yourbusiness.com",
  "logo": "https://yourbusiness.com/logo.png",
  "description": "One or two sentences describing what your business does and for whom.",
  "foundingDate": "2020",
  "founder": {
    "@type": "Person",
    "name": "Your Name",
    "url": "https://yourbusiness.com/about"
  },
  "contactPoint": {
    "@type": "ContactPoint",
    "contactType": "customer service",
    "email": "hello@yourbusiness.com"
  },
  "sameAs": [
    "https://www.linkedin.com/company/your-business",
    "https://twitter.com/yourbusiness",
    "https://www.facebook.com/yourbusiness",
    "https://www.wikidata.org/wiki/Q1234567"
  ]
}

The sameAs array is the single most important property in this block. Without it, your LinkedIn presence, your Twitter presence, and your website are three unconnected signals. With correct sameAs links, they're a unified entity record. Replace the Wikidata Q-number with your actual item URL once you've created your Wikidata entry.

JSON-LD: Person Schema for Personal Brands and Founders #

If you're building a personal brand alongside your business — or if you're a solo founder where your name and your business are tightly linked in Google searches — Person schema on your About page or homepage is as important as your Organization block. Here's a minimal working example:

{
  "@context": "https://schema.org",
  "@type": "Person",
  "name": "Your Name",
  "url": "https://yoursite.com/about",
  "image": "https://yoursite.com/headshot.jpg",
  "jobTitle": "Founder & AI Solutions Architect",
  "worksFor": {
    "@type": "Organization",
    "name": "Your Business Name",
    "url": "https://yoursite.com"
  },
  "description": "One to two sentences summarizing your expertise and what you do.",
  "sameAs": [
    "https://www.linkedin.com/in/your-profile",
    "https://twitter.com/yourhandle",
    "https://github.com/yourhandle",
    "https://www.wikidata.org/wiki/Q1234567"
  ]
}

The worksFor property creates a bidirectional entity relationship: the Person entity points to the Organization, and if your Organization block includes a founder property pointing back to the Person, Google can confirm the relationship from both directions. That bidirectional verification is a stronger entity signal than a one-way declaration.

JSON-LD: FAQPage Schema #

FAQPage schema turns your FAQ content into machine-readable Q&A pairs that AI engines extract directly. This is one of the fastest paths to appearing verbatim in Google AI Overviews and Perplexity cited answer boxes. (For the complete breakdown of why this is the highest-leverage AEO move available, read FAQ Schema and AEO: The Highest-Leverage Move for AI Citation.)

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "What is the Google Knowledge Graph?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "The Google Knowledge Graph is a database of real-world entities — businesses, people, places, and events — that Google uses to power Knowledge Panels and AI Overviews. Businesses can enter the Knowledge Graph by building structured entity signals: Organization schema with sameAs links, a verified Google Business Profile, a Wikidata entry, and consistent NAP data across the web."
      }
    },
    {
      "@type": "Question",
      "name": "How long does it take to get a Google Knowledge Panel?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Most businesses see a Knowledge Panel emerge within 8–16 weeks of implementing clean Organization or Person schema, creating a Wikidata entry, and building consistent entity mentions in external sources. The timeline is shorter when existing press coverage or a verified Google Business Profile is already in place."
      }
    }
  ]
}

One practical note: if your CMS auto-generates FAQPage JSON-LD from ### Question? headings in your content (as this site does), you do not need to hand-write this block — it emits automatically. The manual JSON-LD above is for static sites, Squarespace builds, or any CMS that does not auto-emit structured data.

A Note on Article and BlogPosting Schema #

Every blog post or article on your site should carry Article or BlogPosting schema. The two most important properties within that block are author (a Person entity with sameAs links to your profiles) and datePublished / dateModified. Google AI Overviews use publication date as a freshness signal when deciding which source to cite for time-sensitive queries — and will skip an unattributed, undated article in favor of a properly marked-up competitor piece even if yours ranks higher in traditional search.

The publisher property — pointing to your Organization entity — creates a structural link between your article content and your business entity. This is how Google and AI systems learn that all your blog posts are authoritative outputs of the same recognized organization, rather than standalone documents with no traceable source.

Per Google Search Central's Article structured data documentation, the minimum viable Article or BlogPosting block needs: headline, image, datePublished, dateModified, author (with name and url), and publisher (with name and logo). Missing any of these reduces the block to a partial signal that Google may partially use or ignore entirely.

---

Schema Implementation Priority: Where to Start If You Have None #

If your site has zero structured data today, the implementation order matters. Don't add HowTo schema to a blog post before your homepage has Organization schema — that's building the roof before the foundation. Here's the priority stack I use with every client:

Priority	Schema Type	Location	Why First
1	Organization or LocalBusiness	Homepage <head>	Establishes your entity record; all other signals feed into this
2	Person (for founders/personal brands)	About page	Creates bidirectional entity link with Organization
3	FAQPage	Service pages, landing pages	Fastest path to AI Overview citation for informational queries
4	Article / BlogPosting	All blog posts	Author entity + freshness signals for content citation
5	HowTo	Tutorial, guide, and process pages	Step-by-step citation for procedural queries
6	Product	Product/service pages	Enables AI shopping citations and rich product results
7	BreadcrumbList	Site-wide	Site structure signal; low effort, good AI parsing aid
8	Speakable	AI Visibility content pages	Forward-looking signal; implement after the above are clean

Wikidata entry creation belongs alongside Priority 1 — it's not a schema type but it's foundational entity infrastructure. Create your Wikidata item at the same time you add Organization JSON-LD to your homepage, and link them via sameAs.

Realistically, Priorities 1–4 get most sites 80% of the available AI visibility gain from structured data. Priorities 5–8 are diminishing returns until the foundation is solid. Start there, test with Rich Results Test after each addition, and move down the list.

---

How to Audit Your Schema and Entity Footprint Before You Fix Anything #

Before you write a single line of JSON-LD, run a structured audit. Half the sites I look at have schema markup that's either broken, outdated, or actively conflicting with their Google Business Profile data. Fixing bad schema is more valuable than adding new schema on top of it.

Here's the audit I run on every AI Visibility client engagement, in order:

Step 1: Check what schema you already have.
Go to Google's Rich Results Test and run your homepage, your main service page, and any FAQ or blog pages. Note which schema types Google detects and which throw warnings or errors. Run the same URLs through the Schema Markup Validator for a more granular error report. If you find zero schema on your homepage, that's the starting point. If you find broken schema — which is common on sites after a redesign or CMS migration — fix before adding.

Step 2: Check your Knowledge Graph entry.
Search [your business name] site:kg.google.com or use the Knowledge Graph Search API to see if your business has an existing entity ID. If a Knowledge Panel already appears in Google for your brand name, click the three dots on the panel to find your entity ID. This ID is what you'll add as a sameAs value in your schema.

Step 3: Audit your NAP consistency.
Run your business name through three or four major citation directories — Yelp, BBB, Apple Maps, Bing Places, and any industry-specific directories — and flag any inconsistencies in how your name, address, or phone appears. A single NAP mismatch across widely-indexed sources can suppress a Knowledge Panel that should have appeared months ago.

Step 4: Check Wikidata.
Search wikidata.org for your business name. If an entry exists, verify that all properties are current and that official website and LinkedIn company page are listed under exact match or described at URL. If no entry exists, creating one is your next move.

Step 5: Search for your business in ChatGPT and Perplexity.
Ask both: "What does [your business name] do?" and "Who is [your name]?" The quality of those answers — accuracy, confidence, source citations — is your current AI visibility baseline. Improving it is the entire goal of this process. I recommend running this audit before and after any schema or entity changes to measure actual impact.

---

What Consistent Structured Data Does Over Time #

The compounding effect of clean, consistent structured data is underappreciated. It's not a one-time implementation — it's a living entity record that Google and AI systems continuously re-evaluate. Each time Google crawls your pages, it compares your JSON-LD against your Google Business Profile, your Wikidata entry, and the external mentions it has indexed. Consistency across all three strengthens your entity confidence score.

In practice, this means:

• Schema updates propagate within weeks, not months, on well-crawled sites. Fixing a sameAs mismatch can resolve a Knowledge Panel display issue faster than most technical SEO changes.
• New FAQPage schema additions on high-traffic pages typically show AI citation improvements within 2–4 crawl cycles — roughly 2–4 weeks for a site Google indexes frequently.
• Entity authority builds non-linearly. The first few external mentions matter most. After a certain threshold — typically when Google has cross-referenced your entity across 5+ independent authoritative sources — citation confidence in AI systems stabilizes at a meaningfully higher level.
• Stale schema is actively harmful. An Organization block pointing to a defunct Twitter/X account or an old phone number creates an entity signal conflict that Google's systems have to resolve. The conservative resolution is to trust it less, not more.

The operational habit I recommend: review your homepage schema on the same cadence you review your Google Business Profile — quarterly at minimum, and any time there's a business change that affects your contact information, social profiles, or business description.

Where businesses lose ground after a good start: redesigns. A site redesign is the most common event that strips working schema. The new theme ships without the JSON-LD blocks from the old site, NAP data gets updated on the homepage but not in the schema, or a developer moves pages to a new URL structure and the url property in your Organization block goes stale. I've seen businesses lose a Knowledge Panel they'd had for two years because a redesign broke three schema signals at once and they didn't notice for six months.

Build schema verification into your launch checklist for every site update, not just initial launches. A one-line entry in your deploy process — "run Rich Results Test on homepage and primary service page" — catches most of these regressions before they propagate to Google's Knowledge Graph.

---

How Google AI Overviews Use Structured Data to Decide What to Cite #

Google AI Overviews do not cite pages at random. They run a retrieval and synthesis process that heavily weights structured, machine-readable content — and pages with valid JSON-LD schema are meaningfully easier to extract citation-worthy data from than pages without it. Understanding the mechanism is more useful than treating AI citation as a black box.

Here's what happens when a user submits a query that triggers an AI Overview:

1. Retrieval: Google's systems identify candidate pages for the query, drawing from indexed content, Knowledge Graph entities, and structured data annotations. Pages with FAQPage, HowTo, or Article schema on-topic for the query get surfaced as strong candidates.
2. Extraction: For each candidate page, Google extracts the most relevant passages. Schema markup acts as pre-labeling — it tells the extraction system "this Q&A pair directly answers the question" or "this is a step in the how-to process." Unstructured prose requires the AI to infer where answers begin and end; schema removes that inference step entirely.
3. Synthesis: Google's AI synthesizes extracted passages into a coherent overview and selects citations. Pages where the extracted content directly answers the query in a self-contained, verifiable way get cited. Pages with accurate entity schema matching the query's entity focus get cited when the query is about that entity.
4. Entity disambiguation: When the query involves a specific business, person, or product, Google cross-references the Knowledge Graph to confirm identity. This is where your Organization schema and Wikidata entry directly affect whether your page is surfaced as a citation candidate for brand-related queries.

The practical takeaway: FAQPage and HowTo schema are citation magnets for informational queries; Organization and Person schema are citation gates for brand queries. You need both. A site with only one is leaving half the AI citation surface unaddressed.

From my own site audits: after adding FAQPage schema to 12 service-page FAQ sections across four client sites in Q1 2026, 8 of those pages started appearing as AI Overview citations within 30 days for their target queries. None of those pages had been cited before. The content on the pages didn't change — only the structured markup did. That's the clearest signal I have for how much schema markup matters independently of content quality, at least for informational queries where the content was already solid.

---

Frequently Asked Questions #

What is the difference between on-page structured data and entity authority? #

On-page structured data is the JSON-LD markup you add to your website — a signal you fully control. Entity authority is how well-recognized and cross-referenced your entity is across the broader web — earned over time, not installed in an afternoon. Structured data tells Google and AI systems what your entity is. Entity authority tells them how much to trust and cite it. Both are required: structured data without entity authority is a self-claim with no corroboration. Entity authority without structured data is a signal Google can find but cannot cleanly connect back to your site. The combination is what produces Knowledge Panel appearances and consistent AI citations.

Does FAQ schema still matter for AI visibility in 2026? #

Yes — FAQPage schema is one of the highest-impact AEO moves still available in 2026. Google AI Overviews and Perplexity actively pull from structured FAQ data when constructing cited answer boxes. The mechanism behind traditional FAQ rich snippets in blue-link results has diminished, but the AI answer-extraction value is stronger than ever. Pages with valid FAQPage JSON-LD consistently outperform equivalent pages without it when I manually audit AI citation rates through Google AI Mode and Perplexity across client sites. The questions need to match real search queries — keyword-stuffed fake questions perform worse than no FAQ schema at all.

How do I use HowTo schema to get cited in AI answers? #

Add HowTo schema to any page with a numbered procedure — installation guides, tutorials, service walkthroughs, or any "how to do X" content. Each step becomes a structured HowToStep with a name (the step title) and text (the full explanation). Per Google Search Central's HowTo documentation, this schema type is eligible for rich results that AI engines cite verbatim when answering step-by-step queries. You do not need to change your visible page content — the schema mirrors what's already on the page in a format machines can read and extract from.

What is Speakable schema and does it affect AI or voice search? #

Speakable schema (schema.org/Speakable) marks specific sections of your page as suitable for text-to-speech playback by voice assistants and AI agents. As of mid-2026, Google's official stance is that Speakable is in developer preview and primarily scoped to news publishers working with Google Assistant. That said, the underlying principle — explicitly marking your most self-contained, citation-worthy paragraphs — is directionally aligned with what AI answer engines do when extracting cited passages. Adding Speakable to your lead-answer paragraphs is a low-cost, forward-looking signal worth implementing on AI Visibility content.

How do I verify my schema markup is working correctly? #

Use Google's Rich Results Test and the Schema Markup Validator to confirm your JSON-LD is syntactically valid and recognized. The Rich Results Test shows what Google's crawlers extract from your page and flags any warnings. The Schema Markup Validator checks for structural errors against the schema.org specification. Run both on every page where you add structured data. A single JSON syntax error — a missing comma, an unclosed bracket — silently breaks the entire JSON-LD block. Neither your page nor your rankings will show an obvious error; the structured data just stops working.

Does sameAs in Organization schema directly affect Knowledge Graph inclusion? #

sameAs is the primary mechanism Google uses to unify entity signals across the web, and it directly improves Knowledge Graph inclusion probability. Per Google's structured data guidance, the sameAs property links your website entity to authoritative external profiles. Without it, Google treats your LinkedIn company page, your Crunchbase entry, and your website as potentially related signals — but the connection is inferred. With correct sameAs links pointing to Wikidata, LinkedIn, and your primary social profiles, that connection is explicit and machine-verifiable.

What schema types are recognized by ChatGPT and Perplexity, not just Google? #

ChatGPT and Perplexity do not parse JSON-LD directly at crawl time the way Googlebot does — but they use content from pages that Google has already indexed and enriched. This means your schema indirectly affects ChatGPT and Perplexity citation by improving your Google entity signals and rich result eligibility, which in turn shapes how Google-sourced content feeds into AI retrieval layers. FAQPage and Article schema have the most direct downstream impact because their structured content appears in Google's indexed representation of your page. Organization schema matters because it builds the entity record those same AI systems query when asked about your business.

Should I use JSON-LD, Microdata, or RDFa for schema markup? #

Use JSON-LD. Full stop. Google's structured data documentation explicitly names JSON-LD as the format Google recommends for all structured data implementations. JSON-LD keeps your structured data separate from your HTML markup — it lives in a <script> block and does not require touching your template HTML. Microdata and RDFa both work, but they require embedding schema properties directly in your HTML elements. That approach is fragile, hard to maintain, and prone to breaking during CMS updates or redesigns. There is no scenario in 2026 where Microdata or RDFa is the right choice for a new implementation.

How often should I update my Organization or Person schema? #

Update your Organization or Person schema any time your business details change: new address, new phone, new social profiles, new sameAs targets. Stale schema — contact information that no longer matches your Google Business Profile, sameAs links to deleted social accounts — is a mild negative entity signal. Google's systems favor entities where the structured data, Google Business Profile, and external mentions are all consistent with each other. For AI Visibility specifically, also add new FAQ pairs to your FAQPage schema whenever you add FAQ content to a page, so the structured data stays synchronized with the visible content the AI is reading.

What is the fastest single schema change that improves AI citation rates? #

Adding valid FAQPage schema to your highest-traffic pages, with questions matching real queries, is the fastest single structural change that improves AI citation rates. Organization schema is more foundational long-term, but FAQPage produces observable citation results faster because it creates direct Q&A matches that AI answer engines extract verbatim. In my client work, FAQPage additions consistently produce the fastest measurable improvement in AI citation audits — typically visible within 2–4 weeks of Google re-crawling the updated page.

What is LocalBusiness schema and should I use it instead of Organization? #

LocalBusiness is a subtype of Organization on schema.org, designed for businesses with a physical location or service area that serves customers in person. If you have a brick-and-mortar location or operate in a defined geographic service area — a contractor, a medical practice, a restaurant, a local agency — use LocalBusiness (or a more specific subtype like ProfessionalService, HomeAndConstructionBusiness, or MedicalBusiness) rather than the generic Organization type. More specific schema types give Google higher-confidence entity classification signals. An online-only business or a national/international brand with no single service-area focus should use Organization. You can and should include geo (latitude/longitude) and areaServed properties in a LocalBusiness block — these are direct inputs to local AI answer results when someone asks "best [service] near [city]."

Can I add schema markup to a Squarespace, Wix, or Webflow site? #

Yes, but the implementation varies by platform. Squarespace allows custom code injection in Site Settings > Advanced > Code Injection — paste your JSON-LD <script> block in the header code field. Webflow supports custom code in Project Settings > Custom Code > Head Code. Wix requires using the "Custom Code" section of the site's dashboard under Settings > Custom Code. On all three, JSON-LD is the right format because it lives entirely in a <script> block and does not require modifying template HTML. Test each implementation immediately in Google's Rich Results Test — these platforms sometimes strip or escape custom code in unexpected ways that break JSON syntax.

Does structured data directly improve traditional Google search rankings? #

Structured data is not a direct ranking factor in Google's core algorithm, but it produces indirect ranking benefits that compound over time. Rich results generated by schema markup (FAQ carousels, HowTo steps, Product ratings) increase click-through rates from search results pages. Higher CTR is a user behavior signal Google's systems observe. Knowledge Panel eligibility — which schema helps unlock — increases brand search volume over time as more users encounter your business through AI answers and seek you out directly. The entity authority you build through schema, Wikidata, and external mentions strengthens your topical trust signals across the board. None of this is a direct ranking lever, but all of it feeds into the ecosystem that produces long-term visibility gains in both traditional search and AI answers.

What is the relationship between E-E-A-T and structured data? #

E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) is Google's quality assessment framework, and structured data is one of the most direct technical signals for the Authoritativeness and Trustworthiness dimensions. Per Google Search Central's Quality Rater Guidelines, author entity signals — verifiable credentials, consistent author profiles, named bylines — are explicit E-E-A-T factors. Person schema with sameAs links to professional profiles is how you make those credentials machine-readable. Organization schema with a verifiable address, phone, and sameAs links addresses the Trustworthiness dimension. E-E-A-T is assessed by human quality raters and also increasingly factored into AI Overview source selection — making structured data an E-E-A-T signal that matters for both traditional Google quality assessment and AI citation eligibility.

---

Get Your Business Cited by AI #

Structured data is one half of the AI visibility equation. The other half is entity authority — the external signals, press mentions, and knowledge base entries that tell AI systems your business is worth citing. Most business owners have neither. If you want to know exactly where you stand on both fronts, I audit AI visibility as a standalone engagement.

The audit covers: schema validation across your key pages, Knowledge Graph entity ID lookup, Wikidata entry status, NAP consistency check across major directories, and a manual citation test through Google AI Mode and Perplexity for your primary brand and service queries. You get a prioritized fix list, not a 40-page report you'll never read.

Book an AI visibility audit — I'll tell you exactly what AI systems see when someone searches for your business, and which schema and entity fixes move the needle first.

---

What to Read Next #

• Digital PR for AI Visibility: Getting Mentioned Where AI Reads — how external mentions and press coverage build the entity authority that schema alone cannot establish
• FAQ Schema and AEO: The Highest-Leverage Move for AI Citation — the complete guide to FAQPage schema, question targeting, and answer extraction optimization