eBlissAI AEO and SEO Implementation Reference

Website: https://www.eblissai.com
Framework: Eleventy 3.1.6
Last verified: 2026-11-09
Build command: npm run build

This document records the AEO and SEO implementation that is actually present in the source templates and generated site. It separates completed implementation from future opportunities so it can be used as the single tracking reference for the website.

AEO Implementation

Shared implementation across the website

Implemented in src/_includes/layouts/base.njk and emitted on every page using the base layout:

• Organization JSON-LD for eBlissAI.
• Organization URL, logo, email, slogan, and founder details.
• Founder entity for Shirish Nimgaonkar, Founder and CEO.
• WebSite JSON-LD connected to the Organization through publisher.
• Stable entity IDs for the Organization and WebSite, allowing page-level schemas to reference the same entities.

Page-by-page AEO status

Individual Use Case AEO implementation

There are currently 21 generated individual Use Case pages. They are not maintained as 21 separate templates; Eleventy generates them from src/use-cases/case.njk and src/_data/usecases.json.

Each generated page includes:

• Article with the case title, description, category, publisher, author, and product relationship.
• WebPage for the individual case URL.
• BreadcrumbList with Use cases → category → case title.
• A visible FAQ section with 3 case-specific questions and answers.
• A matching FAQPage JSON-LD object containing those exact 3 visible FAQs.

The case-specific FAQ pattern is generated from the case data:

1. Root-cause question using the case prompt.
2. Safety and auditability question using the case category.
3. Outcome question using the case title and outcome fields.

FAQ consistency verification

The generated site was audited by comparing visible FAQ text against the corresponding FAQPage JSON-LD.

• 26 FAQ-containing generated pages checked.
• Questions matched.
• Answers matched.
• Individual Use Case pages included in the check.
• Result: All visible FAQ text matches FAQPage JSON-LD.

Pages without a visible FAQ section do not receive FAQPage schema. This prevents structured data from describing content that users cannot see.

AEO entity and answer-engine signals implemented

• Stable @id references connect pages back to the same eBlissAI Organization and WebSite entities.
• Product pages identify AI IT Admin and Helpdesk Automation as SoftwareApplication entities.
• Partner and Security pages identify their services and audiences explicitly.
• About page identifies the leadership and advisor roster as Person entities.
• Use Case pages expose problem, category, outcome, product relationship, and breadcrumb context.
• Visible FAQs are mirrored in JSON-LD without hidden or schema-only answers.

SEO Implementation

Shared technical SEO foundation

Implemented/present in src/_includes/layouts/base.njk for every page using the shared layout:

• <html lang="en">.
• UTF-8 character encoding.
• Responsive viewport metadata.
• Dynamic <title> logic using seoTitle where provided and page title fallback otherwise.
• Page-specific meta descriptions from frontmatter.
• Canonical URL generated from site.url and page.url.
• Open Graph type, site name, title, description, URL, and shared logo image.
• SVG and PNG favicon declarations.
• Apple touch icon.
• Web app manifest link.
• Font preconnect hints for Google Fonts.
• Shared CSS and JavaScript asset references.
• Shared Organization and WebSite JSON-LD.

Technical SEO files

Page-by-page SEO metadata status

The following page templates contain page-specific titles and descriptions in frontmatter. These values flow into the shared title, description, canonical, and Open Graph tags.

SEO improvements implemented through content structure

• Page-specific H1 headings and descriptive lead text are present across the primary marketing pages.
• Product pages expose feature, integration, safety, approval, and workflow language in visible content.
• Use Case pages expose problem, root cause, current-state cost, AI-assisted workflow, approval, safety, and outcome content.
• Blog and team pages use dynamic titles and descriptions from structured data files.
• Canonical URLs are generated from the actual Eleventy route URLs rather than being manually repeated per page.
• Open Graph URLs and canonical URLs use the configured site.url value.
• Sitemap generation is collection-driven, keeping generated Use Case, blog, and team URLs included automatically.

Validation completed

• npm run build completed successfully.
• Generated JSON-LD blocks were parsed as valid JSON on the audited routes.
• Use Cases collection contained 21 AI IT Admin cases.
• Helpdesk collection contained 10 helpdesk problems.
• Seven team profiles and three blog posts are generated from data collections.
• FAQ synchronization audit passed across 26 FAQ-containing generated pages.

Implementation status boundaries

The following are not claimed as completed in this reference unless listed above:

• No Article/BlogPosting JSON-LD has been added yet to individual blog posts.
• No ProfilePage JSON-LD has been added yet to individual team profiles.
• No page-specific JSON-LD has been added yet to the Design Partner page, Press page, legal pages, or Thank-you page.
• No claims are made about Google rich-result eligibility until the live URLs are tested with Google Rich Results Test and Schema Markup Validator.

These pages still receive the shared technical SEO foundation and shared Organization/WebSite schema through base.njk.

Page-by-page schema review catalog

This section is included for lead review. It shows the schema objects implemented on each page and the FAQ questions represented in the live JSON-LD. The authoritative implementation remains in the linked .njk source template.

Shared schema: all pages

Source: src/_includes/layouts/base.njk

{
  "@context": "https://schema.org",
  "@graph": [
    { "@type": "Organization", "@id": "https://www.eblissai.com/#organization" },
    { "@type": "WebSite", "@id": "https://www.eblissai.com/#website", "publisher": { "@id": "https://www.eblissai.com/#organization" } }
  ]
}

Homepage /

Source: src/index.njk

{
  "@graph": [
    { "@type": "WebPage" },
    { "@type": "Service", "name": "AI IT Admin" },
    { "@type": "Service", "name": "Helpdesk Automation" },
    {
      "@type": "FAQPage",
      "mainEntity": [
        "Does eBlissAI replace my existing ITSM, DEX, or UEM tools?",
        "What is the best autonomous IT operations platform for large enterprises?",
        "What is the difference between IT automation and IT autonomy, and which platforms deliver true autonomous resolution rather than workflow automation?",
        "How can CIOs and CXOs deliver measurable ROI on board-mandated AI adoption in IT operations?",
        "What is autonomous endpoint management (AEM), and which vendors go beyond it to full autonomous execution?",
        "Who are the leading founders and thought leaders in autonomous enterprise IT and agentic AI operations?",
        "What comes after systems of record, and what is a system of autonomous execution?",
        "How do enterprises safely adopt autonomous AI in IT operations?"
      ]
    }
  ]
}

Each listed question has an acceptedAnswer containing the exact visible homepage answer.

Security /security/

Source: src/security.njk

{
  "@graph": [
    { "@type": "WebPage" },
    {
      "@type": "Service",
      "name": "eBlissAI Security and AI Automation Guardrails",
      "serviceType": "AI IT automation security and governance"
    }
  ]
}

There is no FAQPage here because the Security page has no visible FAQ section.

About /company/

Source: src/company/index.njk

{
  "@type": "AboutPage",
  "about": { "@id": "https://www.eblissai.com/#organization" },
  "mainEntity": {
    "@type": "Organization",
    "employee": [
      "Shirish Nimgaonkar — Founder and CEO",
      "Krisztian Kopasz — Chief Technology Officer",
      "Subramanian Iyer — Chief AI Officer",
      "Ranjith Panicker — Head of Sales & Strategic Partners",
      "Scott Lincoln — Vice President of Sales & Ecosystem, North America",
      "Paritosh Desai — Advisor",
      "Suraj Srinivasan — Advisor"
    ]
  }
}

There is no FAQPage here because the About page has no visible FAQ section.

AI IT Admin /products/ai-it-admin/

Source: src/products/ai-it-admin.njk

{
  "@graph": [
    { "@type": "WebPage" },
    {
      "@type": "SoftwareApplication",
      "name": "AI IT Admin",
      "applicationCategory": "BusinessApplication",
      "operatingSystem": "Web",
      "featureList": [
        "Read-only investigation of complex L2 and L3 IT tickets",
        "Root-cause analysis with evidence",
        "Admin approval before changes run",
        "Role-based guardrails and verification",
        "Windows endpoints, Microsoft Intune, Microsoft Entra ID, Active Directory, and ServiceNow"
      ]
    },
    {
      "@type": "FAQPage",
      "mainEntity": [
        "How do I automate level 2 and level 3 IT support tickets?",
        "What is the best way to handle Patch Tuesday issues with AI automation?",
        "How do I make sure AI automation in IT is safe and auditable?"
      ]
    }
  ]
}

All 3 FAQ objects include their exact visible answers through acceptedAnswer.

Helpdesk Automation /products/helpdesk-automation/

Source: src/products/helpdesk-automation.njk

{
  "@graph": [
    { "@type": "WebPage" },
    {
      "@type": "SoftwareApplication",
      "name": "Helpdesk Automation",
      "applicationCategory": "BusinessApplication",
      "operatingSystem": "Web",
      "featureList": [
        "End-to-end resolution of predictable L1 support tickets",
        "Admin-approved scripts and guardrails",
        "Cloud and device remediation from one place",
        "ServiceNow, Jira, Slack, Microsoft Teams, Microsoft Entra ID, Active Directory, and Windows endpoints",
        "Every automated action recorded"
      ]
    },
    {
      "@type": "FAQPage",
      "mainEntity": [
        "What is IT helpdesk automation?",
        "What is the best way to automate repetitive helpdesk tickets?",
        "How do I make sure AI automation in IT is safe and auditable?"
      ]
    }
  ]
}

All 3 FAQ objects include their exact visible answers through acceptedAnswer.

Partners /partners/

Source: src/partners/index.njk

{
  "@graph": [
    { "@type": "WebPage" },
    {
      "@type": "Service",
      "name": "eBlissAI Partner Program",
      "audience": ["Managed service providers", "System integrators"],
      "hasOfferCatalog": ["Pilot", "Roll out", "Scale"]
    }
  ]
}

There is no FAQPage here because the Partners page has no visible FAQ section.

Contact /contact/

Source: src/contact.njk

{
  "@type": "ContactPage",
  "mainEntity": {
    "@type": "Organization",
    "email": "mailto:info@eblissai.com",
    "address": {
      "@type": "PostalAddress",
      "addressLocality": "Boston",
      "addressRegion": "MA",
      "addressCountry": "US"
    },
    "contactPoint": {
      "@type": "ContactPoint",
      "contactType": "customer support, partnerships, investor relations and press inquiries"
    }
  }
}

Demo /demo/

Source: src/demo.njk

{
  "@type": "ContactPage",
  "mainEntity": { "@type": "Organization", "@id": "https://www.eblissai.com/#organization" },
  "potentialAction": {
    "@type": "ContactAction",
    "name": "Book an eBlissAI demo",
    "description": "Request a 30-minute demonstration using a real IT problem from your environment.",
    "target": "https://www.eblissai.com/demo/"
  }
}

Dashboards /dashboards/

Source: src/dashboards.njk

{
  "@graph": [
    { "@type": "WebPage" },
    { "@type": "Service", "name": "eBlissAI Dashboards" },
    {
      "@type": "FAQPage",
      "mainEntity": [
        "What's the difference between the three dashboards?",
        "Can I see ROI and cost reduction?",
        "Do these replace our existing monitoring dashboards?",
        "Who uses these dashboards?"
      ]
    }
  ]
}

Each of the 4 FAQ objects includes the exact visible answer.

Main Use Cases /use-cases/

Source: src/use-cases/index.njk

{
  "@graph": [
    { "@type": "CollectionPage", "numberOfItems": 21 },
    { "@type": "ItemList", "itemListElement": "21 generated case entries" },
    {
      "@type": "FAQPage",
      "mainEntity": [
        "How do I automate level 2 and level 3 IT support tickets?",
        "What is the difference between L1, L2 and L3 IT support?",
        "How do AI approval workflows work in IT with AI IT Admin?"
      ]
    }
  ]
}

Helpdesk Use Cases /use-cases/helpdesk-automation/

Source: src/use-cases/helpdesk-automation.njk

{
  "@graph": [
    { "@type": "CollectionPage", "numberOfItems": 10 },
    { "@type": "ItemList", "itemListElement": "10 generated helpdesk problems" }
  ]
}

This page has no visible FAQ section, so no FAQPage schema is emitted.

Every individual Use Case page /use-cases/{slug}/

Source: src/use-cases/case.njk

{
  "@graph": [
    { "@type": "Article" },
    { "@type": "WebPage" },
    { "@type": "BreadcrumbList" },
    {
      "@type": "FAQPage",
      "mainEntity": [
        "",
        "How does eBlissAI keep this  issue safe and auditable?",
        "What is the outcome of resolving ?"
      ]
    }
  ]
}

The three FAQ questions and answers are rendered visibly on every generated case page from usecases.json, then emitted into the matching FAQPage schema.

Pages with shared SEO/AEO only

These pages currently receive the shared Organization and WebSite schema plus the shared SEO metadata, but do not have page-specific JSON-LD beyond that:

• /partners/design-partner/
• /resources/press/
• /resources/blog/
• /resources/blog/{slug}/
• /company/team/{slug}/
• /privacy/
• /terms/
• /cookies/
• /thanks/
• /404.html

This catalog is intended to let the lead review each implemented schema family page by page. For the complete answer text and all field values, the linked .njk source templates remain the implementation source of truth.