When someone searches “cardiologist in Hartford” or “walk-in clinic near West Hartford,” Google has to decide which practice looks real, relevant, and consistent. Your website content helps, but medical schema markup helps Google understand what that content means.

Schema doesn’t “boost rankings” by itself. Still, it can remove doubt. It connects your practice name, address, doctors, and services into a clean set of facts that match what patients see on the page.

Below you’ll get copy-paste JSON-LD templates for LocalBusiness, MedicalClinic, and Physician, plus a clear setup path for WordPress and non-WordPress sites.

Why medical schema markup helps Google trust your clinic pages

Think of schema like the label on a prescription bottle. The medicine may be fine, but the label reduces mistakes. Structured data reduces confusion, because it tells search engines, “This is a clinic,” “This is a physician,” and “This is the exact Hartford address.”

When Connecticut practices implement schema well, it usually supports three things:

First, it strengthens entity clarity. Google can connect your brand, your locations, and your providers. That matters for branded searches and for “near me” intent.

Next, it supports local consistency. If your on-page NAP (name, address, phone) matches your schema and your Google Business Profile, your listings feel stable. Mismatches are where trust breaks down.

Finally, it improves machine readability. In 2026, Google’s systems rely heavily on structured signals for understanding businesses and professionals, especially when the same practice appears across directories, maps, and healthcare platforms. For background on healthcare schema types, see Schema.org health and medical types.

Gotcha: Schema should describe what’s visibly true on the page. If the page doesn’t show a phone number, don’t hide one in structured data.

Choosing LocalBusiness vs MedicalClinic vs Physician (and how to connect them)

A common mistake is picking one schema type and calling it done. Medical websites usually need a small set of connected entities.

The practical rule for most Connecticut practices

• MedicalClinic: Use on each location page (Hartford office, New Haven office, etc.). It fits healthcare and local discovery.
• Physician: Use on each provider bio page. It ties credentials and specialty to a real person.
• LocalBusiness: Use when you need a broad business wrapper (often on the contact page or a main “practice” page), especially if your site structure is thin or you’re mid-rebuild.

When people ask “Organization vs LocalBusiness vs MedicalOrganization,” here’s the plain answer: Organization is generic, LocalBusiness is location-focused, and MedicalClinic/MedicalOrganization adds healthcare meaning. If your page is about a physical clinic, MedicalClinic is usually the cleanest fit.

How to link entities so Google doesn’t guess

Use two fields consistently:

• @id: A stable internal identifier (use a real URL plus a fragment).
• sameAs: Trusted profile URLs (Google Business Profile, physician directory pages, reputable listings).

Also, keep NAP identical across:

• The page footer or contact section
• Your schema JSON-LD
• Your Google Business Profile and key citations

If you’re hiring help, don’t just ask for “schema.” Ask how they’ll connect providers to locations using @id and keep NAP consistent. That’s the kind of detail a serious team brings, whether you’re comparing an SEO agency Hartford practices recommend, reviewing Hartford SEO services, or shortlisting an SEO company Hartford CT. It’s also what people mean when they search local seo agency near me and want proof, not promises. For support beyond markup, see Connecticut SEO agency for medical practices.

For extra context on healthcare structured data planning, this healthcare structured data implementation guide lays out common type choices.

Copy-paste JSON-LD templates (Connecticut examples with placeholders)

Place JSON-LD in the HTML of the matching page. Replace every REPLACE_WITH_... value with real data.

LocalBusiness JSON-LD template (practice-level, simple wrapper)

{
  "@context": "https://schema.org",
  "@type": "LocalBusiness",
  "@id": "https://www.REPLACE_WITH_DOMAIN.com/#business",
  "name": "REPLACE_WITH_PRACTICE_NAME",
  "url": "https://www.REPLACE_WITH_DOMAIN.com/",
  "telephone": "+1-860-REPLACE_WITH_NUMBER",
  "image": "https://www.REPLACE_WITH_DOMAIN.com/wp-content/uploads/REPLACE_WITH_IMAGE.jpg",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "REPLACE_WITH_STREET (e.g., 100 Trumbull St Ste 200)",
    "addressLocality": "Hartford",
    "addressRegion": "CT",
    "postalCode": "06103",
    "addressCountry": "US"
  },
  "areaServed": ["Hartford, CT", "West Hartford, CT", "Newington, CT"],
  "contactPoint": [{
    "@type": "ContactPoint",
    "contactType": "appointments",
    "telephone": "+1-860-REPLACE_WITH_NUMBER"
  }],
  "sameAs": [
    "REPLACE_WITH_GOOGLE_BUSINESS_PROFILE_URL",
    "REPLACE_WITH_LINKEDIN_OR_DIRECTORY_URL"
  ]
}

MedicalClinic JSON-LD template (best for location pages)

{
  "@context": "https://schema.org",
  "@type": "MedicalClinic",
  "@id": "https://www.REPLACE_WITH_DOMAIN.com/locations/hartford/#clinic",
  "name": "REPLACE_WITH_CLINIC_LOCATION_NAME",
  "url": "https://www.REPLACE_WITH_DOMAIN.com/locations/hartford/",
  "telephone": "+1-860-REPLACE_WITH_NUMBER",
  "medicalSpecialty": ["REPLACE_WITH_SPECIALTY_1", "REPLACE_WITH_SPECIALTY_2"],
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "REPLACE_WITH_STREET",
    "addressLocality": "Hartford",
    "addressRegion": "CT",
    "postalCode": "06103",
    "addressCountry": "US"
  },
  "geo": {
    "@type": "GeoCoordinates",
    "latitude": REPLACE_WITH_LATITUDE,
    "longitude": REPLACE_WITH_LONGITUDE
  },
  "openingHoursSpecification": [{
    "@type": "OpeningHoursSpecification",
    "dayOfWeek": ["Monday","Tuesday","Wednesday","Thursday","Friday"],
    "opens": "08:30",
    "closes": "17:00"
  }],
  "employee": [{
    "@type": "Physician",
    "@id": "https://www.REPLACE_WITH_DOMAIN.com/doctors/REPLACE_WITH_SLUG/#physician",
    "name": "REPLACE_WITH_PHYSICIAN_NAME"
  }],
  "sameAs": ["REPLACE_WITH_GOOGLE_BUSINESS_PROFILE_URL"]
}

Physician JSON-LD template (use on each provider bio page)

{
  "@context": "https://schema.org",
  "@type": "Physician",
  "@id": "https://www.REPLACE_WITH_DOMAIN.com/doctors/REPLACE_WITH_SLUG/#physician",
  "name": "REPLACE_WITH_FULL_NAME",
  "url": "https://www.REPLACE_WITH_DOMAIN.com/doctors/REPLACE_WITH_SLUG/",
  "image": "https://www.REPLACE_WITH_DOMAIN.com/wp-content/uploads/REPLACE_WITH_HEADSHOT.jpg",
  "medicalSpecialty": "REPLACE_WITH_PRIMARY_SPECIALTY",
  "credential": "REPLACE_WITH_CREDENTIALS (e.g., MD, FAAFP)",
  "worksFor": { "@id": "https://www.REPLACE_WITH_DOMAIN.com/locations/hartford/#clinic" },
  "sameAs": [
    "REPLACE_WITH_HEALTHGRADES_OR_NPI_PROFILE_URL",
    "REPLACE_WITH_GOOGLE_SCHOLAR_OR_HOSPITAL_PROFILE_URL"
  ]
}

Marking up multiple locations and multiple practitioners

Use one MedicalClinic node per location, each with its own @id. Then connect each Physician to the right clinic using worksFor (or connect the clinic to providers using employee). Keep each doctor on their own bio page too.

HIPAA note: Don’t put PHI in schema, no patient names, visit details, or appointment notes. Stick to public business and provider info.

Implementation walkthrough, validation, and common fixes

WordPress setup (no dev team required)

1. Choose where schema should live: homepage, location pages, provider pages.
2. Add JSON-LD with a safe method:
   • Use an SEO plugin field for “custom schema,” if available, or
   • Use a header or footer script plugin that can target specific pages, or
   • Add it in your theme files if you have a developer (cleanest for large sites).
3. Confirm the on-page NAP matches the schema values exactly.
4. Repeat per location and per provider. Don’t reuse the same @id on different pages.

Non-WordPress setup (custom sites)

1. Place the JSON-LD inside the <head> or near the end of <body>.
2. Keep it server-rendered when possible (avoid loading it only after a user action).
3. Maintain one source of truth for NAP, so future updates don’t break consistency.

Validation steps (do this every time)

Use two checks after publishing:

• Google’s Rich Results Test (to see eligibility for supported enhancements)
• Schema validation to catch syntax and type issues, guided by this schema implementation checklist

Troubleshooting the errors that waste the most time

• Missing required fields: Add name, address, telephone, and a valid url.
• Mismatched address: If the page says “Suite 210” but schema says “Ste 200,” fix it.
• Wrong type on the wrong page: Physician belongs on doctor bios, not the homepage.
• Review markup problems: Don’t add aggregateRating unless you show the rating on that page and meet Google’s rules. Also, don’t mark up cherry-picked testimonials as ratings.

Conclusion

If your site is a map, medical schema markup is the legend that makes it readable. Use MedicalClinic for each Connecticut location, Physician for each provider, and connect everything with steady @id values and credible sameAs links. Keep NAP consistent, avoid review spam, and never place PHI in structured data. Once your templates validate cleanly, your pages become easier for Google to understand and easier for patients to trust.