If you publish content, AI needs to understand your publication identity, editorial scope, authorship, and content catalog. The Content family covers four media organization types: Blogger, News Outlet, Publisher, and Media Company, each with page-level blueprints.
When AI evaluates an article as a source, the current blueprint expects these signals:
Article, BlogPosting, or NewsArticle in @type based on the editorial context. This changes how AI interprets freshness and authority.headline, description, url, and image are what AI uses when citing or summarizing the piece.datePublished and dateModified help AI determine whether the article is current enough to trust.Person node with name, url, and sameAs gives AI a verifiable human source.Organization node carries name, url, and, when relevant, logo and sameAs signals for the publication.mainEntityOfPage, WebSite, WebPage, and BreadcrumbList connect the article into a crawlable site graph.FAQPage markup is useful when the article includes visible Q&A that AI may quote back to users.Without those fields, an article may still be crawled, but it becomes much harder for AI systems to cite it accurately.
This page covers the core schema nodes shared across all Content family types. Each media organization type (Blogger, News Outlet, Publisher, Media Company) has its own page-level blueprints that build on these foundations.
The article node centers the implementation: @type, headline, description, datePublished, dateModified, author, publisher, url, image, and mainEntityOfPage.
The author node should expose name, url, and at least one sameAs profile so AI can verify the author exists.
The publisher node carries name, url, and conditional logo and sameAs fields depending on the type of publication.
The root site node anchors the article back to the domain using @id, name, and url.
Every article page should expose its own @id plus references to the site and breadcrumb graph using isPartOf and breadcrumb.
Optional but useful when the article already contains visible Q&A that should be exposed in a machine-readable way.
The section path that tells AI where the article lives in the publication hierarchy.
Each field in the template below serves a specific role in how AI systems discover, classify, and recommend your business.
Researched and tested by Minnesota AI
nameurlsameAsnameurllogoconditionalsameAsconditional@idCopy this prompt and paste it into Claude, ChatGPT, Cursor, or any AI coding tool. It will ask for your business details and generate ready-to-use JSON-LD schema for your page.
You are implementing AIFDS-compliant JSON-LD structured data for a Content Blueprint page. AIFDS (AI-Friendly Data Structure) is a schema framework built on research into which structured data fields AI systems actually read, parse, and use when deciding whether to cite a page. Documentation at aifds.org. Before generating any code, ask me for the following information in a single numbered list. Do not generate schema until I have answered every required field. REQUIRED — do not proceed without these: 1. Article description 2. Article title 3. Author name 4. Company 5. Content type 6. Domain 7. Featured image 8. Github 9. Linkedin 10. Logo 11. Post slug 12. Publisher name 13. Section name 14. Section slug 15. Short summary answer 16. Site name OPTIONAL — ask for these but proceed if I skip them: 1. sameAs Once I provide the information, output a complete JSON-LD script block ready to paste into the <head> of my HTML page. Output requirements: - Valid JSON-LD wrapped in <script type="application/ld+json"> tags - schema.org vocabulary only - Every AIFDS-required field for this industry and page type included - Include this data attribute on the script tag: data-aifds="aifds.org Content Blueprint" - No placeholder text — omit missing optional fields rather than fill with examples - After the code block, list any optional fields skipped that would strengthen AI citation
Generated schema follows the AIFDS framework. Fields were selected based on research into AI crawler behavior. View the research at minnesota.ai
Copy the template below and replace every YOUR_* value with your own data. Keep YOUR_CONTENT_TYPE accurate, and remove the optional publisher fields only if they genuinely do not apply.
{
"@context": "https://schema.org",
"@graph": [
{
"@type": "YOUR_CONTENT_TYPE",
"@id": "https://YOUR_DOMAIN.com/YOUR_POST_SLUG/#article",
"headline": "YOUR_ARTICLE_TITLE",
"description": "YOUR_ARTICLE_DESCRIPTION",
"datePublished": "YYYY-MM-DD",
"dateModified": "YYYY-MM-DD",
"author": {
"@id": "https://YOUR_DOMAIN.com/#author"
},
"publisher": {
"@id": "https://YOUR_DOMAIN.com/#organization"
},
"url": "https://YOUR_DOMAIN.com/YOUR_POST_SLUG/",
"image": "https://YOUR_DOMAIN.com/YOUR_FEATURED_IMAGE.jpg",
"mainEntityOfPage": {
"@id": "https://YOUR_DOMAIN.com/YOUR_POST_SLUG/"
}
},
{
"@type": "Person",
"@id": "https://YOUR_DOMAIN.com/#author",
"name": "YOUR_AUTHOR_NAME",
"url": "https://YOUR_DOMAIN.com/about/",
"sameAs": [
"https://www.linkedin.com/in/YOUR_LINKEDIN",
"https://github.com/YOUR_GITHUB"
]
},
{
"@type": "Organization",
"@id": "https://YOUR_DOMAIN.com/#organization",
"name": "YOUR_PUBLISHER_NAME",
"url": "https://YOUR_DOMAIN.com",
"logo": "https://YOUR_DOMAIN.com/YOUR_LOGO.png",
"sameAs": [
"https://www.linkedin.com/company/YOUR_COMPANY"
]
},
{
"@type": "WebSite",
"@id": "https://YOUR_DOMAIN.com/#website",
"name": "YOUR_SITE_NAME",
"url": "https://YOUR_DOMAIN.com"
},
{
"@type": "WebPage",
"@id": "https://YOUR_DOMAIN.com/YOUR_POST_SLUG/",
"isPartOf": {
"@id": "https://YOUR_DOMAIN.com/#website"
},
"breadcrumb": {
"@id": "https://YOUR_DOMAIN.com/YOUR_POST_SLUG/#breadcrumb"
}
},
{
"@type": "FAQPage",
"@id": "https://YOUR_DOMAIN.com/YOUR_POST_SLUG/#faq",
"mainEntity": [
{
"@type": "Question",
"name": "WHAT_IS_THE_MAIN_TAKEAWAY",
"acceptedAnswer": {
"@type": "Answer",
"text": "YOUR_SHORT_SUMMARY_ANSWER"
}
}
]
},
{
"@type": "BreadcrumbList",
"@id": "https://YOUR_DOMAIN.com/YOUR_POST_SLUG/#breadcrumb",
"itemListElement": [
{
"@type": "ListItem",
"position": 1,
"name": "Home",
"item": "https://YOUR_DOMAIN.com/"
},
{
"@type": "ListItem",
"position": 2,
"name": "YOUR_SECTION_NAME",
"item": "https://YOUR_DOMAIN.com/YOUR_SECTION_SLUG/"
},
{
"@type": "ListItem",
"position": 3,
"name": "YOUR_ARTICLE_TITLE",
"item": "https://YOUR_DOMAIN.com/YOUR_POST_SLUG/"
}
]
}
]
}
Use the most specific type that matches the page. NewsArticle is for newsroom reporting, BlogPosting is for blog-style editorial content, and Article is the general fallback.
Yes. The content blueprint treats headline consistency as part of citation quality. If the H1 and headline diverge, AI can cite the wrong title.
Yes for a personal site or solo creator brand if there is no real publication logo. But for newsroom-style publishing, the blueprint expects a logo because it strengthens institutional attribution.
Yes. The current field map expects at least one external profile for the author. That is one of the simplest ways to make authorship verifiable to AI systems.
Yes if the article genuinely contains those questions and answers. The structured FAQ should match visible page content, not introduce hidden claims.