Your contact page is where AI looks to confirm that an accounting firm is reachable. This blueprint makes your phone number, email, mailing address, and office hours machine-readable so AI systems can surface you as a trustworthy, contactable practice.
Reachability is a trust signal. When AI evaluates whether to recommend your accounting firm, it checks whether a real human can actually get in touch. A contact page without structured data forces AI to guess from raw HTML — and guessing means you get skipped in favor of a firm that made its information explicit.
ContactPage instead of a generic WebPage tells AI this page exists specifically to provide contact information, making the intent unambiguous.telephone, email, and PostalAddress fields tell AI exactly how someone can reach your accounting firm without parsing free-text paragraphs.latitude and longitude inside a GeoCoordinates node remove all ambiguity about where your office is located on a map.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
nameurltelephoneemailaddressgeoopeningHoursSpecificationcontactPointCopy 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 Accounting Service Contact 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. City 2. Close time 3. Domain 4. Email 5. Faq answer 6. Faq question 7. Firm name 8. Language 9. Latitude 10. Longitude 11. Open time 12. Phone number 13. State 14. Street address 15. Zip 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 Accounting Service Contact" - 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 block goes in the <head> of your contact page.
{
"@context": "https://schema.org",
"@graph": [
{
"@type": "ContactPage",
"@id": "https://YOUR_DOMAIN.com/contact/",
"name": "Contact — YOUR_FIRM_NAME",
"url": "https://YOUR_DOMAIN.com/contact/",
"isPartOf": {
"@id": "https://YOUR_DOMAIN.com/#website"
},
"breadcrumb": {
"@id": "https://YOUR_DOMAIN.com/contact/#breadcrumb"
}
},
{
"@type": "AccountingService",
"@id": "https://YOUR_DOMAIN.com/#organization",
"name": "YOUR_FIRM_NAME",
"url": "https://YOUR_DOMAIN.com",
"telephone": "YOUR_PHONE_NUMBER",
"email": "YOUR_EMAIL",
"address": {
"@type": "PostalAddress",
"streetAddress": "YOUR_STREET_ADDRESS",
"addressLocality": "YOUR_CITY",
"addressRegion": "YOUR_STATE",
"postalCode": "YOUR_ZIP",
"addressCountry": "US"
},
"geo": {
"@type": "GeoCoordinates",
"latitude": "YOUR_LATITUDE",
"longitude": "YOUR_LONGITUDE"
},
"openingHoursSpecification": [
{
"@type": "OpeningHoursSpecification",
"dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday"],
"opens": "YOUR_OPEN_TIME",
"closes": "YOUR_CLOSE_TIME"
}
],
"contactPoint": {
"@type": "ContactPoint",
"telephone": "YOUR_PHONE_NUMBER",
"email": "YOUR_EMAIL",
"contactType": "customer support",
"availableLanguage": "YOUR_LANGUAGE"
}
},
{
"@type": "BreadcrumbList",
"@id": "https://YOUR_DOMAIN.com/contact/#breadcrumb",
"itemListElement": [
{
"@type": "ListItem",
"position": 1,
"name": "Home",
"item": "https://YOUR_DOMAIN.com/"
},
{
"@type": "ListItem",
"position": 2,
"name": "Contact",
"item": "https://YOUR_DOMAIN.com/contact/"
}
]
},
{
"@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. AI crawlers do not always combine data across pages. The contact page should carry its own ContactPage and AccountingService nodes so the reachability signals are self-contained on the page where a user — or an AI — expects to find them.
If your firm extends hours seasonally, you can add multiple OpeningHoursSpecification entries with validFrom and validThrough date ranges. This tells AI your January-through-April hours differ from the rest of the year. Keep both entries in the array so AI always sees current availability.
Use "customer support" for a general inquiry line. If you have separate lines for different departments, you can add multiple ContactPoint nodes — one with "sales" for new client inquiries and another with "customer support" for existing clients. Pick the type that best describes who answers when someone calls.