The most consequential communications work happening today is not being done by communications teams.
AI Communications, defined
AI Communications is the discipline of building authority across AI answer engines — ChatGPT, Claude, Perplexity, Gemini, and Google AI Overviews — alongside earned media, digital, and influencer channels. It combines public relations, Generative Engine Optimization (GEO), and AI-visibility research to influence the answers anyone asking now begins with.
Most communications professionals have never written schema markup. Many cannot define it. The ones who can have usually outsourced the work to web developers, treating it as a technical task adjacent to the real work.
This is the most expensive mistake the communications industry is making right now.
Schema is communications work. It is the work of telling AI engines what an entity is, what it does, who runs it, and why it matters — in a structured, machine-readable format the engines actively read and weight. It does for AI answers what positioning statements did for media coverage.
This is the fifth canonical piece in the AI Communications series, the deep dive on Layer 2 of the Stack. The claim: schema and structured authority are now core communications functions, and the communications teams that don't own them will lose the discipline to the teams that do.
What schema is
Schema is structured data — a vocabulary defined by Schema.org and used across the major search and AI platforms — that lives in the HTML of a webpage and tells machines what kind of entity the page represents and what its attributes are.
A founder's About page can be a paragraph of text. It can also be a paragraph of text plus a block of structured data that says this is a Person, named Jane Smith, born in 1972, founder of an Organization called Acme Corp, with an alma mater of Stanford University. The structured data is invisible to a human reader. It is read directly by AI engines.
When a buyer asks ChatGPT who is Jane Smith, the answer the engine assembles is influenced — sometimes determined — by what the structured data on the open web says about her. If the structured data is rich, accurate, consistent, and verified across multiple sources, the AI answer is rich, accurate, and consistent. If the structured data is sparse, inconsistent, or absent, the AI answer is sparse, inconsistent, or absent.
Schema is the language an entity speaks to the AI engines. Most entities speak it badly, or not at all.
Why this is communications work
The content of the schema is editorial. The decision about what to say about a founder, an organization, a product, or a place is a communications decision. It is positioning. It is messaging. Handing this to a developer is like asking a developer to write the press release.
The accuracy of the schema is the brand's responsibility. Schema markup that says the company has 500 employees when it has 5,000 is a brand problem. Schema markup that lists an outdated CEO is a brand problem. The team responsible for accuracy of the brand's public representation is, by definition, the communications team.
The strategic deployment of schema is competitive. Two competitors in the same category may have similar press, similar traffic, similar social presence — but one has rich, accurate, consistent schema across all their owned properties and the other has none. The first will outperform the second in Citation Share, often dramatically.
What schema work looks like
1. The entity sheet. Before a single line of schema is written, the communications team produces an entity sheet for each entity that needs structured authority — the brand, the founder, key executives, key products, key initiatives. The sheet contains the canonical facts. The entity sheet is a communications document.
2. The deployment plan. Schema is deployed across the brand's owned properties — website, blog, executive bio pages, product pages, press releases, knowledge base — and aligned with external profiles: LinkedIn, Crunchbase, industry directories, Wikipedia, Wikidata. The plan is the communications team's responsibility.
3. Wikipedia and Wikidata. These are not separate from schema; they are the most heavily-weighted schema sources on the open web. Every brand and every founder of any consequence has either a Wikipedia/Wikidata entry that is accurate, sourced, and current — or one that isn't. The communications team that doesn't manage the Wikipedia entry has given that authority away.
4. Author bylines and structured authorship. When an executive publishes a byline, the structured authorship metadata — Person Jane Smith wrote this article on Topic X published in Publication Y on Date Z — is what allows AI engines to link the byline to the entity. Without structured authorship, the byline is an orphan.
5. The ongoing audit. Schema breaks. Plugins update. Sites redesign. Information drifts out of date. The audit is recurring — quarterly at minimum, weekly for high-visibility entities.
What gets it wrong
Treating schema as a one-time project. Schemas drift. Information changes. CEOs leave. Products launch. The schema layer requires ongoing maintenance, which means it requires an ongoing owner.
Outsourcing to a developer without editorial oversight. A developer can implement schema; a developer should not decide what the schema says. The communications team writes the content. The developer deploys it.
Treating Wikipedia as a brand-builder. Wikipedia entries are documentation, not promotion. A Wikipedia entry that reads as a marketing brochure will be flagged, edited, or deleted. A Wikipedia entry that is accurate, sourced, and neutral is a permanent Citation Share asset.
Skipping Wikidata. Wikipedia gets the press; Wikidata gets the AI citations. Wikidata is the structured-data layer behind Wikipedia and is pulled from heavily by AI engines. A complete Wikipedia entry without a corresponding Wikidata record is half-finished work.
The new role
The communications team that owns Layer 2 needs a role that did not exist five years ago.
Call it Authority Lead. Call it Structured Communications Director. Call it Schema Strategist. The title matters less than the function.
The function is to own the entity sheets, the schema deployment plan, the Wikipedia and Wikidata strategy, the structured authorship program, the recurring audit, and the handoff with engineering on technical deployment.
This is a senior role. It requires editorial judgment, technical literacy, and political ability to negotiate the territory between communications and engineering. Most agencies do not have this role yet. The agencies that hire for it first will lead the category.
The big claim
The communications industry has spent the last decade absorbing digital, social, content marketing, and influencer disciplines. Each was once treated as someone else's job. Each is now a core PR function.
Schema is next. The communications teams that recognize this first and build the function in-house will be the agencies of the next decade.
The discipline is communications. The medium is structured data. The audience is the AI engine.
The work has to get done. The only question is which side of the firm does it.
