Analytics
AEO/SEO Evaluation of Empathia AI – Cardiology Specialty Page

AEO/SEO Evaluation of Empathia AI – Cardiology Specialty Page

Abstract

This report presents a comprehensive AEO/SEO evaluation of the Empathia AI Cardiology Specialty Page, identifying key issues, evidentiary findings, and actionable repair recommendations for accessibility, SEO structure, meta information, content quality, media, and structured data. The audit assigns quantitative scores to critical sections, highlights risks and priorities, and provides code-level solutions aligned with best practices. A RICE-model improvement matrix is provided to support implementation sequencing, alongside structured data recommendations and measurable acceptance criteria.

Summary of Findings

  • Overall Page Score: 66/100
  • Page Type Judgment: Article/Blog Hybrid (informational, commercial, specialty landing)

Top 5 Priority Issues

  1. Missing <main> or <article> Semantic Wrapper
  2. No Canonical Link Tag
  3. No Meta Robots Tag
  4. No Article Schema (Only Organization/Product in JSON-LD)
  5. No Clear <h1> (Only <h2> Used)

Note: Page content is organized like an article, detailing Empathia AI solutions for Cardiologists, but lacks author/date data and is not a news blog or classic blog post.

Detailed Assessment

1. Crawlability & Basic Structure

  • Section Score: 10/20
  • Conclusion: Needs Improvement

Findings & Evidence

  • Main Semantics:
    No <main> or <article> found. Content nested in <div>s and <section>s.
  • Heading Hierarchy:
    All main headings use <h2>, no unique <h1>.
  • Language Attribute:
    Correct, <html lang="en">.
  • Indexing Control:
    No <meta name="robots"> present.
  • Canonical Link:
    No <link rel="canonical"> found.

Impact & Risk: Crawlers may misidentify main content; duplicate content risk; unclear indexing; accessibility and topical clarity reduced.

Repair Recommendations:
  1. Wrap the main content in a <main> tag, optionally embedding an <article>.
  2. Add a unique <h1> for the page topic.
  3. Add <meta name="robots" content="index,follow"> to the <head>.
  4. Add a canonical link referencing the preferred URL.
Reference Code:
<!-- Add to <head>: -->
<link rel="canonical" href="https://www.empathia.ai/specialties/cardiology">
<meta name="robots" content="index,follow">

<!-- Replace in content container: -->
<main>
  <article>
    <h1>AI Charting for Cardiologists | Structured Notes & Referral Letters | Empathia AI</h1>
    <!-- ...existing page content... -->
  </article>
</main>

2. Title & Meta Information

  • Section Score: 15/20
  • Conclusion: Pass but Room for Optimization

Findings & Evidence

  • Title: Present, unique, length is 75 characters (slightly over 60); strong keywords.
  • Meta Description: Present, 156 characters, informative and keyword-rich.
  • Open Graph: Present, but og:type is "website" (not "article"); og:image uses relative URL.
  • Twitter Cards: Present, but image uses relative URL.
  • Keywords: <meta name="keywords" content="cardiology"> present.

Impact & Risk: Good SERP and click-readiness; minor risk on social sharing with relative image URL and OG type.

Repair Recommendations:
  1. Shorten the <title> (under 65 characters).
  2. Use absolute URLs for OG/Twitter images.
  3. Set og:type="article".
Reference Code:
<title>AI Charting for Cardiologists | Structured Notes & Referral Letters</title>
<meta name="description" content="Empathia AI helps cardiologists document faster with structured SOAP notes, consults, and cardiac summaries.">
<meta property="og:title" content="AI Charting for Cardiologists | Structured Notes & Referral Letters">
<meta property="og:type" content="article">
<meta property="og:description" content="Empathia AI helps cardiologists document faster with structured SOAP notes, consults, and cardiac summaries.">
<meta property="og:image" content="https://www.empathia.ai/images/icons/logo.png">
<meta property="og:url" content="https://www.empathia.ai/specialties/cardiology">
<meta name="twitter:card" content="summary_large_image">
<meta name="twitter:title" content="AI Charting for Cardiologists">
<meta name="twitter:description" content="Empathia AI helps cardiologists document faster.">
<meta name="twitter:image" content="https://www.empathia.ai/images/icons/logo.png">

3. Content Quality & Layout (Answer Priority)

  • Section Score: 15/20
  • Conclusion: Pass, but Needs Optimization

Findings & Evidence

  • Answer First: Begins with “The Leading AI Clinical Assistant for Cardiology” value prop.
  • Clear Structure: Logical headings, features, statistics, testimonials.
  • Originality & Depth: Unique metrics, specialty and workflow details, testimonials.
  • Keyword Usage: Consistent and natural across key content elements.

Impact & Risk: Good for user intent fulfillment and feature snippets; could benefit from conclusion/FAQ.

Repair Recommendations:
  1. Add a summary/conclusion paragraph to reinforce main takeaways.
  2. Include an FAQ section for richer user intent coverage.

4. Images & Media

  • Section Score: 14/20
  • Conclusion: Needs Improvement

Findings & Evidence

  • Alt Texts: All images have good alt text coverage.
  • Semantic Filenames: Mixed; some descriptive, others generic (e.g., star.svg).
  • Image-Text Relationship: No <figure> or <figcaption>; images inside <div> blocks only.

Impact & Risk: Accessibility and image SEO are solid; semantic relationship could improve ranking and context.

Repair Recommendations:
  1. Wrap key visuals in <figure> with descriptive <figcaption>.
  2. Use descriptive filenames for core images.
<figure>
  <img src="/images/specialties/doctor-desk.svg" alt="Doctor at desk with medical tools">
  <figcaption>Empathia AI enables cardiologists to capture and structure clinical notes efficiently.</figcaption>
</figure>

5. Structured Data (Schema)

  • Section Score: 12/20
  • Conclusion: Needs Improvement

Findings & Evidence

  • JSON-LD Present: Only Organization, Product, Review schemas.
  • No Article-Level Schema:
    Page lacks Article, BlogPosting, or NewsArticle types.
  • No FAQPage Schema: Not present.

Impact & Risk: Search engines may not treat page as an article; lost opportunities for article authority and rich result eligibility.

Repair Recommendations:
  1. Add Article type JSON-LD referencing visible title, description, and images.
  2. Fill out as many fields as possible or note as [Undetermined].
Recommended JSON-LD Template:

{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "AI Charting for Cardiologists | Structured Notes & Referral Letters | Empathia AI",
  "author": { "@type": "Person", "name": "[Undetermined - please specify author's name]" },
  "datePublished": "[Undetermined - please specify publish date]",
  "dateModified": "[Undetermined - please specify last modified]",
  "image": ["https://www.empathia.ai/images/specialties/doctor-desk.svg"],
  "publisher": {
    "@type": "Organization",
    "name": "Empathia AI",
    "logo": {
      "@type": "ImageObject",
      "url": "https://resource.empathia.net/web/images/logo/logo.png"
    }
  },
  "mainEntityOfPage": "https://www.empathia.ai/specialties/cardiology"
}

Improvement Priority List (RICE Model)

Task Impact Reach Effort Priority
Add <main>/<article> structureHighHighSmall1
Add <h1> with page-topic keywordHighHighSmall2
Add canonical & robots tagsHighHighSmall3
Implement Article JSON-LD schemaHighHighSmall4
Make OG/Twitter image URLs absoluteMediumHighSmall5
Set og:type to "article"MediumHighSmall6
Add <figure>/<figcaption> for key imagesMediumMediumSmall7
Add FAQ section (if medically compliant)HighMediumMedium8
Add author/datePublished/dateModified metadataMediumMediumMedium9
Shorten title length/optimize for mobile displayLowMediumSmall10

Tracking & Acceptance Criteria

Indicator Acceptance Criteria Method for Checking
Main/Article inclusion <main>/<article> present in live HTML HTML code inspection in browser/dev tools
Canonical, robots meta Correct, unique, present in <head> Live page <head> source check
JSON-LD Article schema Present, valid, verified by Google Rich Results Test Paste in structured data tool
<h1> presence Unique, top-level, clear keyword relevance HTML rendered output visually and in source
OG Image absolute URL Fully qualified image URL, valid for social preview Debug in Facebook/Twitter share debugger
FAQ/HowTo schema (if added) Appears in page, validates in SDTT Manual review and tool check
Key image figure/caption Figure/caption semantic wrapping, correct text present Source and UX inspection
Title (<65 chars) Shorter headline visible in page & SERP preview Simulate SERP rendering/check mobile truncation
Ranking/CTR/coverage After fix – uplift, measured in GSC/analytics Google Search Console/GA monitoring
Note: All [undetermined] fields in Structured Data must be filled by editorial or exposed in article content for schema validity.