Products › SaaS

Contact Page Blueprint — SaaS

Surfaces sales and support channels so AI can confirm your team is reachable. When an AI system evaluates whether to recommend your software, it checks for clear contact paths — sales for prospects, support for customers, billing for account questions. This blueprint structures all three so nothing is missed.

View Prompt View JSON

What this page needs

A SaaS contact page must declare every channel a prospect or customer can use to reach your team. AI systems use this data to answer questions like "how do I contact support?" or "can I book a demo?" before pointing someone your way.

Organization with contactPoint array. The Organization node includes a contactPoint array with separate entries for sales, customer support, and billing — each with its own email, telephone, and contactType.
Email and telephone per department. Each ContactPoint declares the specific email address and phone number for that team, so AI can route users to the right channel instead of a generic inbox.
ContactPage type. Declaring the page as a ContactPage tells AI this is the canonical place to find your company's contact information, not just a page that happens to mention an email address.
Telephone for sales. A direct sales phone number signals that prospects can speak with a human, which AI treats as a trust and accessibility indicator for enterprise buyers.

Why these fields matter to AI

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

Organization

name: AI uses this to identify the vendor behind the software.
url: Confirms the organization maps to an accessible domain.

WebSite

@id: All other schema nodes reference this ID. Without it the graph is disconnected.

Use This Prompt to Implement Your Schema

Copy 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 SaaS 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. Billing email
2. Company name
3. Contact faq answer
4. Contact faq question
5. Domain
6. Logo
7. Sales email
8. Sales phone
9. Support email
10. Support phone

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 SaaS 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

Template — fill in your values

Copy the template below and replace every YOUR_* value with your own data. This block belongs in a <script type="application/ld+json"> tag in the <head> of your contact page.

{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "Organization",
      "@id": "https://YOUR_DOMAIN.com/#organization",
      "name": "YOUR_COMPANY_NAME",
      "url": "https://YOUR_DOMAIN.com",
      "logo": "https://YOUR_DOMAIN.com/YOUR_LOGO.png",
      "contactPoint": [
        {
          "@type": "ContactPoint",
          "contactType": "sales",
          "email": "YOUR_SALES_EMAIL",
          "telephone": "YOUR_SALES_PHONE",
          "availableLanguage": ["English"]
        },
        {
          "@type": "ContactPoint",
          "contactType": "customer support",
          "email": "YOUR_SUPPORT_EMAIL",
          "telephone": "YOUR_SUPPORT_PHONE",
          "availableLanguage": ["English"]
        },
        {
          "@type": "ContactPoint",
          "contactType": "billing",
          "email": "YOUR_BILLING_EMAIL",
          "availableLanguage": ["English"]
        }
      ]
    },
    {
      "@type": "ContactPage",
      "@id": "https://YOUR_DOMAIN.com/contact/#webpage",
      "url": "https://YOUR_DOMAIN.com/contact/",
      "name": "Contact Us",
      "isPartOf": {
        "@type": "WebSite",
        "@id": "https://YOUR_DOMAIN.com/#website"
      },
      "about": {
        "@id": "https://YOUR_DOMAIN.com/#organization"
      }
    },
    {
      "@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_CONTACT_FAQ_QUESTION_1",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "YOUR_CONTACT_FAQ_ANSWER_1"
          }
        },
        {
          "@type": "Question",
          "name": "YOUR_CONTACT_FAQ_QUESTION_2",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "YOUR_CONTACT_FAQ_ANSWER_2"
          }
        }
      ]
    }
  ]
}

Frequently asked questions

Why should I list multiple contact types instead of one general inbox?

Different audiences need different channels. A prospect asking for a demo needs sales, not billing. A customer with an invoice question needs billing, not support. By declaring separate ContactPoint entries with distinct contactType values, AI systems can route users to the right team and give more specific answers about how to reach you.

Should I include a demo booking link on the contact page?

Yes. If you offer demo calls, your sales ContactPoint is the right place to signal that. While schema.org does not have a dedicated "book a demo" property, including the sales phone and email makes it clear to AI that prospects can initiate a conversation. You can also add a potentialAction with a target URL pointing to your scheduling page.

What is the difference between a contact page and an about page?

The contact page is about reachability — how to get in touch and through which channel. The about page is about identity — who built the product, the founding story, and the team. AI systems treat these as different trust signals. A contact page builds trust through accessibility, while an about page builds trust through transparency and organizational credibility.