Blog posts are the content AI actually cites. When your faculty publish articles about their research, when staff share student success stories, or when your institution publishes educational guides, structured data tells AI who wrote it, when it was published, and which institution stands behind it — turning a page of text into a quotable, attributable source.
Blog posts are the pages AI cites most often. When someone asks an AI about a topic your faculty or staff have written about, these are the signals it looks for before quoting or linking your article.
BlogPosting as the @type so AI recognizes the page as authored editorial content rather than a generic web page.Person node with name, jobTitle, and sameAs links tells AI who is responsible for the content. For faculty authors, the job title and institutional affiliation signal subject-matter expertise.publisher field links the article to your institution via the #organization reference. AI uses this to attribute the content to an educational institution, which carries more weight than an unaffiliated individual.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
headlinedescriptiondatePublisheddateModifiedauthorpublisherimagenamejobTitleurlsameAsnameurllogoCopy 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 Educational Organization Blog 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. Author name 2. Author slug 3. Category 4. Domain 5. Faculty or staff title 6. Faq answer 7. Faq question 8. Featured image 9. Linkedin 10. Logo 11. Modified date 12. Organization name 13. Post description 14. Post slug 15. Post title 16. Publish date 17. Scholar id 18. Word count OPTIONAL — ask for these but proceed if I skip them: 1. Any additional details not covered above 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 Educational Organization Blog" - 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. This template covers a single blog post page on an educational organization website.
{
"@context": "https://schema.org",
"@graph": [
{
"@type": "BlogPosting",
"@id": "https://YOUR_DOMAIN.com/blog/YOUR_POST_SLUG/#article",
"headline": "YOUR_POST_TITLE",
"description": "YOUR_POST_DESCRIPTION",
"datePublished": "YOUR_PUBLISH_DATE",
"dateModified": "YOUR_MODIFIED_DATE",
"author": {
"@id": "https://YOUR_DOMAIN.com/#author"
},
"publisher": {
"@id": "https://YOUR_DOMAIN.com/#organization"
},
"image": "https://YOUR_DOMAIN.com/YOUR_FEATURED_IMAGE.jpg",
"articleSection": "YOUR_CATEGORY",
"wordCount": YOUR_WORD_COUNT
},
{
"@type": "Person",
"@id": "https://YOUR_DOMAIN.com/#author",
"name": "YOUR_AUTHOR_NAME",
"jobTitle": "YOUR_FACULTY_OR_STAFF_TITLE",
"url": "https://YOUR_DOMAIN.com/faculty/YOUR_AUTHOR_SLUG/",
"worksFor": {
"@id": "https://YOUR_DOMAIN.com/#organization"
},
"sameAs": [
"https://www.linkedin.com/in/YOUR_LINKEDIN",
"https://scholar.google.com/citations?user=YOUR_SCHOLAR_ID"
]
},
{
"@type": "EducationalOrganization",
"@id": "https://YOUR_DOMAIN.com/#organization",
"name": "YOUR_ORGANIZATION_NAME",
"url": "https://YOUR_DOMAIN.com",
"logo": "https://YOUR_DOMAIN.com/YOUR_LOGO.png"
},
{
"@type": "BreadcrumbList",
"@id": "https://YOUR_DOMAIN.com/blog/YOUR_POST_SLUG/#breadcrumb",
"itemListElement": [
{
"@type": "ListItem",
"position": 1,
"name": "Home",
"item": "https://YOUR_DOMAIN.com/"
},
{
"@type": "ListItem",
"position": 2,
"name": "Blog",
"item": "https://YOUR_DOMAIN.com/blog/"
},
{
"@type": "ListItem",
"position": 3,
"name": "YOUR_POST_TITLE",
"item": "https://YOUR_DOMAIN.com/blog/YOUR_POST_SLUG/"
}
]
},
{
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "YOUR_FAQ_QUESTION_1",
"acceptedAnswer": {
"@type": "Answer",
"text": "YOUR_FAQ_ANSWER_1"
}
},
{
"@type": "Question",
"name": "YOUR_FAQ_QUESTION_2",
"acceptedAnswer": {
"@type": "Answer",
"text": "YOUR_FAQ_ANSWER_2"
}
},
{
"@type": "Question",
"name": "YOUR_FAQ_QUESTION_3",
"acceptedAnswer": {
"@type": "Answer",
"text": "YOUR_FAQ_ANSWER_3"
}
}
]
}
]
}
Use a Person node for the faculty member as the author and reference the institution as the publisher. AI gives more weight to content authored by a named individual with verifiable credentials. The worksFor property on the Person node connects the author to your institution, giving AI both individual expertise and institutional backing.
Student stories still use the BlogPosting template. If a student wrote the post, list them as the Person author with a jobTitle like "Student" or "Graduate Student." If a staff member wrote about a student, the staff member is the author. Either way, the institution remains the publisher so AI knows the content comes from an official source.
Use the articleSection field to distinguish content types — "Research," "Campus News," "Student Life," and so on. For research content, add a Google Scholar link in the author's sameAs array and consider using ScholarlyArticle instead of BlogPosting if the content is a formal research summary. The articleSection helps AI categorize your content for the right types of queries.