Blog posts are the content AI actually cites. When a general contractor publishes articles about construction tips, project updates, or industry insights, structured data tells AI who wrote it, when it was published, and which company 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 "how long does a kitchen remodel take" or "what should I know before hiring a contractor," 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, url, and sameAs links tells AI exactly who is responsible for the content and whether they have relevant construction expertise.publisher field links the article to your contracting company. AI uses this to attribute the content to a business, not just an individual.description gives AI a summary it can use directly. articleBody provides the full text for deeper comprehension.Without these fields, AI may read your blog post but have no way to confirm who wrote it, when it was written, or which company published it — so it skips the citation entirely.
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 General Contractor 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. Category 3. Company name 4. Domain 5. Faq answer 6. Faq question 7. Featured image 8. Github 9. Job title 10. Linkedin 11. Logo 12. Modified date 13. Post description 14. Post slug 15. Post title 16. Publish date 17. 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 General Contractor 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 a general contractor 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_JOB_TITLE",
"url": "https://YOUR_DOMAIN.com/about/",
"sameAs": [
"https://www.linkedin.com/in/YOUR_LINKEDIN",
"https://github.com/YOUR_GITHUB"
]
},
{
"@type": "GeneralContractor",
"@id": "https://YOUR_DOMAIN.com/#organization",
"name": "YOUR_COMPANY_NAME",
"url": "https://YOUR_DOMAIN.com",
"logo": "https://YOUR_DOMAIN.com/YOUR_LOGO.png"
},
{
"@type": "WebPage",
"@id": "https://YOUR_DOMAIN.com/blog/YOUR_POST_SLUG/",
"isPartOf": {
"@id": "https://YOUR_DOMAIN.com/#website"
},
"breadcrumb": {
"@id": "https://YOUR_DOMAIN.com/blog/YOUR_POST_SLUG/#breadcrumb"
}
},
{
"@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 BlogPosting for posts that live on a blog or news section of your site. Use Article for standalone editorial pages that are not part of a chronological feed. Both carry the same core fields — the difference is semantic, and BlogPosting signals a regularly published series of construction insights or project updates.
Yes. datePublished tells AI when the article first appeared, and dateModified tells it when the content was last updated. If you have never updated the post, set both to the same date. AI systems use the gap between these dates as a freshness signal — important for construction content where building codes and best practices change.
Technically yes, but AI systems strongly prefer a Person author with a name, title, and profile links. An article attributed to "ABC Construction" carries less citation weight than one attributed to "John Smith, Owner at ABC Construction" with a LinkedIn profile. Use publisher for the company and author for the individual.