Analytics
SEO Technical Assessment of Empathia AI Cardiology Article Landing Page

SEO Technical Assessment of Empathia AI Cardiology Article Landing Page

Abstract

This report presents a detailed technical SEO assessment of the Empathia AI Cardiology article-style landing page. All findings, scores, and recommendations are provided exactly as discovered. Critical areas assessed include canonical links, structured data presence, HTML5 semantics, heading hierarchy, metadata usage, image accessibility, and eligibility for search features such as rich results. Actionable improvement priorities are ranked using a simplified RICE matrix. Specific HTML and JSON-LD code samples are referenced for correct remediation. Performance tracking and acceptance criteria are defined to ensure repairs meet both technical and practical requirements for SEO and accessibility.

Overview

  • Overall Page Score: 70/100
  • Top 5 Priority Issues:
    1. Missing Canonical Link
      Impact: Risk of duplicate content in search.
      Benefit: Proper canonical tag guides search engines to preferred URL.
    2. No Article/Page Structured Data
      Impact: Google cannot generate rich results for this key page.
      Benefit: Adding Article/BlogPosting schema improves discoverability and click-through.
    3. No <main> or <article> Landmark Element
      Impact: Ambiguity for content prioritization, weakens semantic structure.
      Benefit: Adding a landmark element strengthens main content signal and accessibility.
    4. No H1 Tag Present
      Impact: Degrades heading hierarchy signal and potentially relevance scoring.
      Benefit: Clear H1 reinforces topic/keyword focus.
    5. OG:image and twitter:image Use Relative URL
      Impact: Social sharing previews may fail to display images on some platforms.
      Benefit: Absolute URLs ensure consistent social card previewing.
  • Page Type Judgment: Article-style Landing Page (Specialty Overview)
    Reason: The content focuses on detailed features for a medical specialty (Cardiology), using sections, clear topic-driven headings, and informative copy. There's no obvious blogging or news timestamp, nor author meta. It’s a commercial "article/landing" hybrid but best fits "Article" for search/SEO schema.

Detailed Assessment

1. Basic Structure & Crawlability

  • Section Score: 13/20
  • Conclusion: Needs Improvement
Findings & Evidence:
  • Main Content Landmark:
    • Locator: body > div#___next > ...
    • Snippet: Entire page content is inside a <div>, with content-heavy <section>s but no <main> or <article> tag.
    • Issue: No primary content landmark.
  • Heading Hierarchy:
    • Locator: Multiple <h2>, <h3>, <h4> in sections.
    • Snippet: <h2>Streamline Cardiologists' Workflow with Empathia AI</h2>
    • Issue: No <h1> tag in HTML; hierarchy otherwise reasonable.
  • Language Attribute:
    • Locator: <html lang="en">
    • Issue: Correctly set.
  • Indexing Control:
    • Locator: head, meta robots not present
    • Issue: <meta name="robots"> not present (defaults to indexable).
  • Canonical:
    • Locator: head > link[rel="canonical"]
    • Issue: Tag is missing (no canonical URL provided).
  • Crawlability:
    • All main content is present in prerendered HTML; no anti-bot techniques detected; semantic tags are present but primary landmark missing.
Impact & Risk:
  • No canonical and missing main/heading signals can weaken priority for search engines and affect crawl budget, site ranking signals, and accessibility.
Repair Recommendations (Actionable):
  • Add <main> tag wrapping primary content area (all the main <section>s).
  • Add a single, descriptive <h1> reflecting core page topic.
  • Insert a canonical link with absolute URL to the preferred version of the page.
  • Optional: Add <meta name="robots" content="index,follow"> for explicit signaling.
Reference Code Example: 
<!-- Canonical Example -->
<link rel="canonical" href="https://www.empathia.ai/specialties/cardiology">

<!-- Robots Example -->
<meta name="robots" content="index,follow">

<!-- Landmark and Heading Example -->
<main>
  <h1>AI Charting Solutions for Cardiologists | Empathia AI</h1>
  <!-- ...all main content sections... -->
</main>

2. Title & Meta Information

  • Section Score: 15/20
  • Conclusion: Pass
Findings & Evidence:
  • Title:
    • Locator: head > title
    • Snippet: <title>AI Charting for Cardiologists | Structured Notes & Referral Letters | Empathia AI</title>
    • Issue: Unique, ~77 characters (slightly over, but still clear and keyword-rich).
  • Meta Description:
    • Locator: head > meta[name="description"]
    • Snippet: <meta name="description" content="Empathia AI helps cardiologists document faster...">
    • Issue: ~139 characters, clear, keyword-focused.
  • Open Graph (OG):
    • Locators: <meta property="og:title" ...>, <meta property="og:description" ...>, <meta property="og:image" ...>, <meta property="og:url" ...>, <meta property="og:type" ...>.
    • Issues: og:title, og:description, og:url, and og:type are in place and relevant. og:image uses relative URL: /images/icons/logo.png (should be absolute).
  • Twitter Cards:
    • Locators: <meta name="twitter:card" content="summary_large_image">, <meta name="twitter:title" ...>, <meta name="twitter:description" ...>, <meta name="twitter:image" ...>
    • Issue: twitter:image is relative, all else present and consistent.
  • Keywords Tag:
    • Locator: <meta name="keywords">
    • Snippet: <meta name="keywords" content="cardiology">
    • Issue: Very minimal; may not add much value.
Impact & Risk:
  • Title/meta and OG are close to optimal but absolute URLs in images are needed for reliable social sharing. A slightly long title could wrap/ellipsize in some SERPs.
Repair Recommendations (Actionable):
  • Ensure all OG/Twitter images use absolute URLs, e.g., https://www.empathia.ai/images/icons/logo.png.
  • Optionally condense title to under 70 characters for best display across devices.
Reference Code Example: 
<meta property="og:image" content="https://www.empathia.ai/images/icons/logo.png">
<meta name="twitter:image" content="https://www.empathia.ai/images/icons/logo.png">
<!-- Title example (optional condense) -->
<title>AI Charting for Cardiologists | Structured Notes | Empathia AI</title>

3. Content Quality & Layout

  • Section Score: 17/20
  • Conclusion: Pass
Findings & Evidence:
  • Answer First:
    • Locator: .hero-content .text-content .specialty-label, h2, and next <p>
    • Snippet:
      • <div class="specialty-label">The Leading AI Clinical Assistant for Cardiology</div>
      • <h2>Streamline Cardiologists' Workflow with Empathia AI</h2>
      • <p class="hero-description">Cardiologists manage a busy schedule with consults, surgeries and chronic condition follow-ups....</p>
    • Issue: Clearly targets the central user pain point and solution upfront.
  • Clear Structure: Multiple semantic <section>s, each with topic headings and supporting content.
  • Originality & Depth: Custom testimonials, unique benefits, statistics—traces of original content focused on this product in cardiology.
  • Keywords: Present in title, meta, intro, bullet points/subheadings, and conclusion/CTA. No evidence of stuffing; usage appears natural.
Impact & Risk:
  • High content quality and structure enable strong relevance signals and user engagement. CTA placement supports conversions.
Repair Recommendations (Actionable):
  • Maintain keyword diversity and avoid future stuffing.
  • Consider an FAQ section to enrich for common search intents (and unlock FAQ schema if present).

4. Images & Media

  • Section Score: 10/20
  • Conclusion: Needs Improvement
Findings & Evidence:
  • alt Texts:
    • Locator: Various <img ... alt="">
    • Example: <img src="/images/specialties/doctor-desk.svg" alt="Doctor at desk with medical tools" class="hero-illustration">
    • Issue: Hero/image feature images have descriptive alt. Decorative/checkmark/star images use generic alts (“star”, “double quotes”), but some are empty (alt="" in toggler).
  • Semantic Filenames:
    • Locator: All images in /images/icons/ or /images/specialties/
    • Issue: File names are generally semantic and relevant to content.
  • Image-Text Relationship:
    • Images are code-adjacent to content but not within <figure>/<figcaption>.
    • Issue: No <figure> or <figcaption> used for images that support/complement feature cards or testimonials.
Impact & Risk:
  • Weak ARIA/HTML5 relationship signals (figure/caption), and repetitive mark-up for decorative icons could hinder screenreader accessibility.
  • Absolute image URLs needed for social previews (per above).
Repair Recommendations (Actionable):
  • Use <figure> / <figcaption> for hero or testimonial images with supporting visible captions.
  • For testimonials, group star/quote/testimonial inside <figure>.
  • Ensure all content-carrying images have meaningful alt attributes.
Reference Code Example: 
<figure>
  <img src="/images/specialties/doctor-desk.svg" alt="Doctor at desk with medical tools">
  <figcaption>Empathia AI for Cardiology—Streamline clinical documentation.</figcaption>
</figure>

5. Structured Data (Schema)

  • Section Score: 15/20
  • Conclusion: Needs Improvement
Findings & Evidence:
  • Schema Presence:
    • Locator: head > script[type="application/ld+json"]
    • Snippet: Includes only Organization and Product types.
    • Issue: No Article, BlogPosting, or NewsArticle relevant to this actual page.
  • Complete Fields: No headline, author, datePublished, etc., for the page-specific article content.
  • Consistency: Existing schema matches company/product, but not main page content.
  • FAQ/HowTo: None, and none clearly justified by presented content.
Impact & Risk:
  • Rich result eligibility is limited, reducing enhanced organic visibility.
  • Lacking Article schema may reduce topic authority/trust in Google’s eyes.
Repair Recommendations (Actionable):
  • Add Article or BlogPosting schema mapped to the actual page title, summary, etc.
  • If and when an FAQ section is added, include FAQPage schema.
Reference Code Example: 
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "AI Charting for Cardiologists | Structured Notes & Referral Letters | Empathia AI",
  "author": { "@type": "Organization", "name": "Empathia AI" },
  "datePublished": "2024-06-01",
  "dateModified": "2024-06-01",
  "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"
}

Structured Data Recommendations (if missing or incorrect)

  • Recommended Type: Article
    Reason: The page is an information-rich overview of a medical specialty solution—a classic fit for "Article". There's no news/blog-specific publisher/date, so "Article" is safest.
  • Required Field Mapping:
    • headline: <title> and hero heading
    • author: Organization ("Empathia AI"), no individual author present
    • datePublished / Modified: Date not on page; use estimated or add to page
    • image: /images/specialties/doctor-desk.svg (hero image, convert to absolute URL)
    • publisher: "Empathia AI"; logo from existing org schema
    • mainEntityOfPage: canonical URL (to be added as per repair above)
Copyable JSON-LD Template: 
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "AI Charting for Cardiologists | Structured Notes & Referral Letters | Empathia AI",
  "author": { "@type": "Organization", "name": "Empathia AI" },
  "datePublished": "2024-06-01",   // Replace with accurate page creation date if available
  "dateModified": "2024-06-01",    // Replace with accurate date
  "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 (Simplified RICE)

Task Impact Reach Effort Priority
Add canonical link to page High High Small 1
Insert Article/BlogPosting schema with mapped content High High Small 2
Add <main> wrapper and <h1> heading for main content High High Small 3
Update OG:image & twitter:image to use absolute URLs Med High Small 4
Add <figure>/<figcaption> for core images/testimonials Med Med Small 5
Ensure meaningful alt text on all main/feature images Med Med Small 6
(Optional) Add explicit <meta name="robots" content="index,follow"> Low High Small 7
Expand SEO keyword set in meta/first paragraph (avoid stuffing) Low Med Small 8
Add FAQ section and FAQPage schema (if FAQ content is added) Med Med Med 9

Tracking & Acceptance

Indicators to monitor after fixes:
  • Inclusion Rate: Ensure page is indexed (site:; Google Search Console coverage)
  • Impressions: Increase in Search Console for relevant keywords (ex: "cardiology AI charting")
  • CTR: Higher SERP click-through (with proper title/desc/OG meta)
  • Average Ranking: Movement of core keywords up in ranking positions
  • Core Keyword Coverage: Confirm core and related keywords are in title, meta, H1, first paragraph, sections
Acceptance Criteria for Each Item:
Item Metric/Check
Canonical link present <link rel="canonical" ...> present in HTML; preferred URL matches live page
Article schema added JSON-LD valid (Rich Results test); headline matches title/text
<main> and <h1> present <main> tag in DOM, wrap main sections; single <h1> present and relevant
OG/twitter images absolute <meta property="og:image"> uses absolute HTTPS URL
<figure>/<figcaption>/alt improvements Screenreader: alt text reads context, figcaption visible
Page indexable Index,Follow meta present or default, crawlers show page indexed
Rankings/impressions improve Impressions/rankings up in Search Console (4+ weeks after change)
If any information is "Not found/Unable to determine", see above for gaps (e.g., canonical, Article schema, landmark element). Address by providing accurate content and specifying responsible owner (content/admin/SEO).