Published March 19, 2026
Content sites — blogs, publishers, news outlets, media companies — face a paradox with AI. They produce the content AI summarizes in responses. But when someone asks AI to recommend a source or cite an article, AI needs structured data to understand who published it, what it covers, and whether the source is credible.
Without schema, AI reads the content but may not attribute it correctly or cite it even when drawing on its information.
The AIFDS content blueprint library contains 55+ blueprints covering blogs, publishers, and media companies, built from the same research into which schema fields AI systems actually read.
A service business wants AI to recommend it. An ecommerce store wants AI to recommend its products. A content site wants AI to cite it as a source — to attribute information and direct readers to the publication.
The transaction loop completes when AI sends a reader to the article — not when a user contacts a business or buys a product. The schema fields that matter are the ones that help AI understand what was published, who published it, and what topic it covers.
Content sites also face a unique threat: AI can summarize their content without citing them. Structured data that clearly identifies the publication, author, and topic makes proper attribution easier — the difference between AI using your content and AI citing your content.
Organization schema on the homepage tells AI who is behind the publication. A blog with no publisher identity is harder for AI to cite than one with clear Organization schema identifying the publication name and contact information.
Each article needs schema identifying its title, author, publication date, and description. This is how AI matches content queries to specific articles rather than the publication generally.
Author schema — name, credentials, affiliation — helps AI assess authority and attribute properly. Particularly important for topics where expertise matters, like medical, financial, or legal content.
Topic expressed through schema helps AI match articles to specific queries — not just a generic Article type with no subject classification.
Blog posts, news articles, opinion pieces, and how-to guides serve different purposes. Schema that identifies the content type helps AI match the right kind of content to the right query.
Editorial focus, publication frequency, and subject areas help AI understand scope. A niche publication covering only healthcare AI should be matched differently than a general tech news outlet.
Content sites often have better schema than other business types because CMS platforms add basic Article schema automatically. But auto-generated schema is the minimum — article title, publication date, maybe an author name. Publisher identity, author credentials, topic classification, and content type are frequently missing.
The homepage is where the biggest gap exists. Most content site homepages have no Organization schema identifying the publication. AI sees individual articles but does not understand the publication behind them.
Schema is eligibility. If AI cannot confirm who published the article and whether the author has relevant expertise, it may use the information without citing the source — or cite a competitor whose data is clearer.
The content blueprint library contains 55+ blueprints organized by publication type, then by page type. Blogs, news outlets, and media companies each get their own set covering homepage, article pages, author pages, category pages, and more. Every blueprint contains the exact JSON-LD fields AI needs.
Start with the homepage. Add Organization schema — publication name, editorial focus, contact information, and what the publication covers.
Audit existing article schema. Use the AIFDS validator to see what your CMS generates and what is missing. Fill gaps in author credentials, topic classification, and content type.
Add author pages with schema. Each author should have a dedicated page with schema identifying name, credentials, expertise, and affiliation.
Structure category and topic pages. Each category should have its own page with schema describing what that section covers. Feeds and structure work together — AI reads both the content feed and the structural organization of the site.
David Valencia writes about how AI systems find, parse, and cite websites.