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.
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-attorneyOwned 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
The visible structured-data stack keeps the content, page sections, and JSON-LD aligned for review before the production URL is published.
Attorney entity
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.
Search intent
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.
Trust layer
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.
Page modules
This block gives answer engines a concise, source-bounded summary without replacing the full page.
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.
Image generation brief
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
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.
The page combines verified lawyer identity, source links, local relevance, image metadata, internal linking, schema, FAQs, and a direct answer block for AI retrieval.
No. Attorney likeness should use a real approved photo. Generated visuals can support backgrounds or non-likeness editorial assets only.