Your about page is where AI learns who runs the company, why it exists, and what credentials back it up. This blueprint structures your company story, leadership, and achievements so AI systems can build trust around your firm and cite it with confidence.
The about page is the trust layer of your website. It is where AI looks to verify who is behind a business, how long it has existed, and whether the people running it have real credentials. Without structured data on this page, AI may know your firm offers services but lack the human context needed to recommend it over a competitor.
foundingDate, description, and numberOfEmployees tell AI how established and capable your firm is. These fields turn a faceless brand into a verifiable entity.Person node with jobTitle, sameAs, and hasCredential connects your leadership to real professional profiles. AI uses this to assess expertise and authority.sameAs links on the organization node point AI to your LinkedIn, Google Maps, and other authoritative profiles, reinforcing that your firm is a real, established entity.When these signals are in place, AI can confidently attribute your services to a named team with proven credentials instead of treating your business as an anonymous listing.
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
nameurlsameAsconditionalnamejobTitleurlsameAshasCredentialconditionalCopy 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 Professional Service About 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. Company 2. Company description 3. Company name 4. Domain 5. Employee count 6. Faq answer 7. Faq question 8. Founder name 9. Founding year 10. Job title 11. License or certification 12. Linkedin 13. Maps cid 14. Organization name OPTIONAL — ask for these but proceed if I skip them: 1. sameAs 2. hasCredential 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 Professional Service About" - 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. Remove the optional hasCredential field if your leadership does not hold a formal license or certification.
{
"@context": "https://schema.org",
"@graph": [
{
"@type": "AboutPage",
"@id": "https://YOUR_DOMAIN.com/about/",
"name": "About YOUR_COMPANY_NAME",
"url": "https://YOUR_DOMAIN.com/about/",
"isPartOf": {
"@id": "https://YOUR_DOMAIN.com/#website"
},
"breadcrumb": {
"@id": "https://YOUR_DOMAIN.com/about/#breadcrumb"
}
},
{
"@type": "Organization",
"@id": "https://YOUR_DOMAIN.com/#organization",
"name": "YOUR_ORGANIZATION_NAME",
"url": "https://YOUR_DOMAIN.com",
"foundingDate": "YOUR_FOUNDING_YEAR",
"description": "YOUR_COMPANY_DESCRIPTION",
"numberOfEmployees": {
"@type": "QuantitativeValue",
"value": "YOUR_EMPLOYEE_COUNT"
},
"sameAs": [
"https://www.linkedin.com/company/YOUR_COMPANY",
"https://www.google.com/maps?cid=YOUR_MAPS_CID"
]
},
{
"@type": "Person",
"@id": "https://YOUR_DOMAIN.com/#founder",
"name": "YOUR_FOUNDER_NAME",
"jobTitle": "YOUR_JOB_TITLE",
"url": "https://YOUR_DOMAIN.com/about/",
"sameAs": [
"https://www.linkedin.com/in/YOUR_LINKEDIN"
],
"hasCredential": {
"@type": "EducationalOccupationalCredential",
"credentialCategory": "YOUR_LICENSE_OR_CERTIFICATION"
}
},
{
"@type": "BreadcrumbList",
"@id": "https://YOUR_DOMAIN.com/about/#breadcrumb",
"itemListElement": [
{
"@type": "ListItem",
"position": 1,
"name": "Home",
"item": "https://YOUR_DOMAIN.com/"
},
{
"@type": "ListItem",
"position": 2,
"name": "About",
"item": "https://YOUR_DOMAIN.com/about/"
}
]
},
{
"@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"
}
}
]
}
]
}
Yes. The Organization node describes the company as an entity, but a separate Person node gives AI a direct reference to the individual, including their job title, credentials, and professional profiles. Without it, AI cannot attribute expertise to a specific human.
Add a Person node for each key leader in the @graph array. Give each one a unique @id (for example, #founder-1 and #founder-2) and include their individual credentials and social profiles.
Only include hasCredential when there is a real license, certification, or accreditation to reference. If your industry does not require formal credentials, remove the field entirely rather than leaving a placeholder. AI treats empty credential fields as noise.