Skip to main content
Referral intake reviewES
Verified attorney profile formatReview-only blueprintProduction canonical mapped

Armen Akaragian, Esq. product liability attorney profile blueprint

This page shows the attorney profile pattern we should use before publishing new lawyer pages: bar verification, source-backed case context, local search support, and a clean schema stack.

Quick answer

Armen Akaragian, Esq. is presented here only as a publication-ready attorney blueprint. The public facts shown should stay tied to verified source URLs, including the California State Bar and the official firm profile.

Production canonical URL

/lawyers/armen-akaragian/product-liability-attorney

Owned by /sitemap-lawyers.xml. Verified English attorney specialty page with source-backed profile schema.

Recommended production URL pattern

/lawyers/[attorney-slug]/[practice-focus-attorney]

This is a review-only blueprint. Real scaled pages should still be approved, canonical, unique, internally linked, and added to the correct sitemap only after passing the publication gates.

Structured-data target

Structured data that should ship with this page type

The visible structured-data stack keeps the content, page sections, and JSON-LD aligned for review before the production URL is published.

ProfilePagePersonServiceBreadcrumbListFAQPageImageObject

Attorney entity

Start with facts that can survive verification

The attorney page should not lead with vague claims. It should identify the lawyer, public license record, firm context, practice focus, and the exact sources used for every trust statement.

  • California State Bar number: 242303
  • Firm profile: Mardirossian Akaragian LLP
  • Education: J.D., Southwestern University School of Law; B.S. in Business, California State University, Northridge
  • Languages listed in the profile data: English, Armenian

Search intent

Match the attorney to a precise legal problem

A strong attorney page connects the lawyer to one narrow client need, then links back to broader practice hubs so Google and AI systems understand the entity relationship.

  • Primary page intent: product liability and serious injury comparison
  • Secondary support: wrongful death, motor vehicle accidents, premises liability, and public entity claims
  • Internal links should connect the lawyer profile, the practice guide, and relevant local pages

Trust layer

Show the evidence trail instead of hiding it

The attorney blueprint includes a visible source panel. It helps users and reviewers understand which facts are verified and which claims should not be expanded.

  • Use source labels that describe why each source matters
  • Avoid unsupported superlatives and invented recognitions
  • Keep the attorney page aligned with bar status and current public source data

Page modules

Reusable blocks for this category

AI retrieval block

This block gives answer engines a concise, source-bounded summary without replacing the full page.

  • Name, title, firm, and active attorney status
  • Practice focus and relevant local search areas
  • Source-backed awards, memberships, cases, and admissions only

Conversion block

The CTA should feel helpful, not pushy. It should route a visitor to intake while repeating that no attorney-client relationship is created until review.

  • Free intake review message
  • Case-fit checklist
  • Short privacy and attorney-client relationship disclaimer

Image generation brief

Visual standard for this page type

Use a real approved attorney portrait. If a generated background is needed, create only a neutral editorial office setting with no fake likeness, no text, no logos, and no invented awards.

Alt text

Portrait of Armen Akaragian, Esq. used for the attorney profile blueprint

FAQ schema source

Visible FAQs

How should this attorney example be used?

It is a public page-format example, not a replacement for the canonical attorney listing. Once approved, the same structure can be applied to a real canonical attorney URL.

What makes the attorney page publication-ready?

The page combines verified lawyer identity, source links, local relevance, image metadata, internal linking, schema, FAQs, and a direct answer block for AI retrieval.

Can we use generated attorney photos?

No. Attorney likeness should use a real approved photo. Generated visuals can support backgrounds or non-likeness editorial assets only.