← Back to SEO Report ← Miami Brain Injury Lawyer Analysis

Miami Brain Injury Lawyer — SEO Improvements

miami-brain-injury-lawyer  ·  Gallardo Law Firm  ·  Updated 2026-07-24  ·  En / article.cshtml + FaqEntities.xml + ServiceEntities.xml

URL https://gallardolawyers.com/injury-law/miami-brain-injury-lawyer
Target Keyword miami brain injury lawyer
2,5454,157
Crawlable EN words (+63%)
255
Keywords merged (106 GSC · 136 SEM)
012
Inbound internal links
07
Related-service cross-links
03
JSON-LD blocks on the page
Keywords On The Page — Before → After
One master table was built from three sources: Google Search Console (last 3 months, this URL — 106 queries), the Semrush keyword-gap report (136 keywords, volume / KD / our rank vs 3 competitors) and a Semrush bulk-volume export that filled 45 previously blank volumes. Total 255 unique keywords, deduped into one file.
Was (pre-expansion baseline) → Now (recounted)  ·  VOL/KD/RANK = Semrush US  ·  POS/Impr = GSC 3-mo
Keyword Vol/mo KD GSC pos Impr Rank Was Now Δ
brain injury lawyer (head term)18,100298.32181527+12
brain injury attorney BIGGEST GAP12,100339.719407+7
brain injury lawyers5,400307.98916+7
best brain and spine injury lawyer (KD 12 — soft target)4,4001220.0100=
brain injury attorneys2,400299.55713+2
brain injury law firm2,400406.43101+1
brain injury attorney near me (transactional)1,600289.525201+1
brain injury lawyer near me1,6003217.2601+1
traumatic brain injury attorney near me1,000299.5200=
north miami brain injury lawyer320921.84782300=
miami brain injury lawyer (the named target — most impressions on the page)210128.41,0681177=
brain injury lawyer miami210311.26771300=
brain injury attorney miami140410.44981600=
brain injuries attorney aventura140813.53562500=
traumatic brain injury lawyer north miami140418.43112400=
miami brain injury attorney11099.83401602+2
traumatic brain injury attorney aventura110415.13352400=
traumatic brain injury attorney miami7028.93211600=
tbi lawyers miami (acronym cluster)70412.91801600=
coral gables brain injury law firm (worst geo cluster)70423.61002900=
miami brain injury lawyers4079.221801+1
miami brain injury law firm0*4.1801+1
"Now" counts describe on-page presence only, not rankings. Rank = Semrush position (— = tracked but outside the top 100, or not tracked). Google reads singular/plural and word-order variants (brain injury lawyer / lawyers / attorney) as one intent, so the value is in covering the cluster once. VOL = size of the national market (what to name things); Impr = what this page can reach today (what to prioritise) — never compare them directly. *VOL 0 ≠ no demand: Semrush does not track thin local long-tail; GSC proves the searches happen. Counts were re-refreshed after the work-log's interim 3,449-word snapshot, so the final figures here run higher than the ones logged mid-session.
Bare-stem density (PAGE rows — reinforcement, not a keyphrase)
StemWasNowΔ
injury (word)64143+79
brain injury (phrase)56117+61
miami (the local signal — biggest relative gain)1030+20
lawyer (word)1833+15
tbi (acronym — was under-used)620+14
case1527+12
injuries1626+10
medical1019+9
attorney (word)816+8
brain injuries412+8
claim815+7
negligence310+7
traumatic brain injury713+6
compensation1925+6
accident1925+6
13 tokens that were 0× on the page and now exist at all
  • near me 0 → 2
  • free consultation 0 → 4
  • brain injury case 0 → 4
  • miami-dade 0 → 3
  • glasgow coma scale 0 → 3
  • head injury 0 → 2
  • traumatic brain injury (tbi) 0 → 2
  • statute of repose 0 → 1
  • north miami · coral gables · doral · aventura · hialeah · miami gardens  — each 0 → 1 (the new service-area section)
The Keyword Strategy — Where the Demand Actually Is
GSC 106 queries + Semrush gap 136 kw  ·  255 unique keywords, one table
The 12,100/mo head term was not on the page at all. "brain injury attorney" — 12,100 searches/mo, 194 GSC impressions, average position 9.7 — appeared 0 times in the body. The page leaned entirely on "lawyer" (18,100/mo, 15×). Both are the same intent to a reader and nearly the same to Google, but a term that never appears cannot anchor a passage. Now 0 → 7, alongside "brain injury lawyer" 15 → 27. These are US-wide volumes — market shape, not reachable traffic. GSC agrees on direction: the page already shows for "attorney" phrasings it never used.
The impressions are geo, the volume is national — the two data sets point different directions, and both matter
ClusterGSC queriesImprGSC posSemrush rankToken on page
Miami core (miami / TBI / brain injury × lawyer, attorney, law firm)113,7358.4–13.78–18miami 10 → 30
North Miami51,29916.2–21.818–250 → 1
Aventura474313.5–15.724–250 → 1
Coral Gables (worst positions on the page)1035723.6–81.529–620 → 1
Doral36515.0–53.7320 → 1
Miami core alone is 3,735 impressions — over half of everything this URL earns — at positions 8–14, i.e. bottom of page 1 / top of page 2, the range where a small move is worth the most traffic. The satellite cities are where the page is weakest and the competition thinnest (Semrush KD 3–9): North Miami, Aventura and Coral Gables together are ~2,400 impressions sitting at positions 13–81 with, until now, zero mention of the city name in the copy.
The "near me" cluster is ~5,900/mo and was 0× on the page
Eight near-me variants: brain injury attorney near me (1,600/mo · 252 impr), brain injury lawyer near me (1,600), traumatic brain injury attorney near me (1,000), brain injury lawyers near me (880), plus attorneys/traumatic/law-firm/head-&-brain variants. The literal token "near me" appeared 0 times. It now appears twice, in the new service-area section (which also carries @Settings.GetPhoneFormated), and two exact phrases — "brain injury attorney near me" and "brain injury lawyer near me" — are each present once. Prose that repeats "near me" reads badly; once each is the whole win.
The long tail Google already trusts this page for — and the page barely mentions
Roughly 425 impressions across 25 condition-specific queries at average positions 7.7–24.5: anoxic, hypoxic, hypoxic-ischemic encephalopathy, perinatal, infant, brain cooling, vegetative state, locked-in syndrome, neurological injury, loss of vision, stroke, TBI specialist — each 0–10/mo in Semrush, so invisible to volume-first research, but Google is already ranking this URL for them. That is a content brief, not a keyword list.
Caution: infant / perinatal / brain-damage phrasing overlaps the birth-injury and cerebral-palsy pages. Expanding those terms here is the one move in this file that could create cannibalization — see the linking section, where the inbound-link pass deliberately skipped those anchors.
What has NOT changed: the multi-word geo phrases still read 0 on the page. "north miami brain injury lawyer", "traumatic brain injury attorney aventura", "coral gables brain injury law firm" — 2,400+ impressions between them — are counted as exact strings, and the exact strings are not in the copy. The component words now are, which is what actually moves a page. Whether to hard-code a handful of exact phrases is a copy decision, not a data one. Sequence: attorney/lawyer parity (done) → satellite-city coverage (started) → work 3–4 exact geo phrases into headings → then the condition long-tail, carefully, without stealing from birth-injury.
Three rows in the merged table are noise, kept for transparency rather than targeting: "workers compensation doctor ives estates" (1 impr, pos 97), "gallardo law firm reviews" (brand), and two research-style queries about a real-estate investor's head injury — someone's long-form question, not a market.
Content Accuracy — One FAQ Was Wrong and One Term Was Invented
The FAQ "How many people suffer from TBI?" carried 2002–2006 CDC figures and a fabricated classification. On a YMYL legal page, a made-up medical term is the most damaging kind of error there is — it is exactly what an E-E-A-T review, and increasingly an AI answer engine, checks first.
App_Data/FaqEntities.xml  ·  English entry only — Spanish left untouched per instruction
1 · Stale CDC statistics FIXED
"1.7 million" TBIs and "52,000 deaths" — CDC figures from the 2002–2006 surveillance period, roughly two decades out of date and still presented as current.
Replaced with current CDC data: approximately 214,000 TBI-related hospitalizations in 2020 and ~69,000 TBI-related deaths in 2021. Source cited in an XML comment above the entry (cdc.gov/traumatic-brain-injury/data-research).
2 · "Type 1 / Type 2 TBI" — a classification that does not exist REMOVED
The answer split TBI into "Type 1" and "Type 2". No such taxonomy exists in the clinical literature; it appears to have been invented for the copy.
Replaced with the real, universally used severity classification — mild / moderate / severe — which is also what the new Glasgow Coma Scale table on the page now scores against, so the FAQ and the body agree for the first time.
3 · Statute of limitations re-verified CONFIRMED CORRECT
The page's "2 years" for negligence is correct under Florida HB 837 (effective 2023-03-24) — checked rather than assumed, because the pre-HB-837 figure was 4 years and stale copies of it are everywhere. No change needed; the body section around it was expanded instead (below).
Content Expansion — 8 edits · body 2,545 → 4,157 words (+63%)
The expansion was templated on the product-liability page — same section pattern, same TOC convention, same schema trio — so the two pages reinforce one structure instead of each inventing their own. Every edit carries a Razor comment in article.cshtml citing its source.
Views/ServicePage/Content/injury-law/miami-brain-injury-lawyer/En/article.cshtml
A — New Content Sections (work log §7)
1 · "How Common Are Brain Injuries in the U.S.?" — cited stats section + table NEW
Built on CDC Facts About TBI, the same corrected figures now used in the FAQ. A sourced statistic with a visible citation is the single pattern generative engines quote back most readily, and it gives the page an answer to a question competitors state without attribution.
2 · "Types and Severity of Brain Injuries" + Glasgow Coma Scale table NEW
Mild / moderate / severe with the GCS score ranges that define them (Cleveland Clinic + Medscape). Adds the "glasgow coma scale" token (0 → 3) and the clinical vocabulary the condition long-tail searches in — and replaces the invented Type 1 / Type 2 split with the real one.
3 · "Time Limits for TBI Claims" expanded EXPANDED
A single "2 years" sentence — accurate, but it silently answered only the negligence case and left medical-malpractice readers with the wrong deadline.
Now separates negligence from medical malpractice (Fla. Stat. 95.11 / HB 837) and adds the statute of repose (0 → 1 on the page). NEEDS COUNSEL — the framing is a position, not a lookup.
4 · "Steps to Take After a Brain Injury" — ordered how-to list NEW
A real <ol> of actions after a TBI. No HowTo schema — Google retired that rich result in 2023; the value is the answer format, not markup.
5 · "Brain Injury Lawyers Serving Miami and Nearby Communities" GEO
North Miami, Coral Gables, Doral, Aventura, Hialeah, Miami Gardens and Miami-Dade — the exact clusters carrying 2,400+ unearned impressions — plus "near me" and @Settings.GetPhoneFormated. Framed as service area, never branch offices. PENDING FIRM REVIEW — which cities the firm will claim is a business decision.
6 · Table of Contents (10 sections) NEW
Jump-links following the site's anchor convention, IDs verified 1:1 against their targets (a broken TOC is worse than none). Eligible for Google "jump-to" sitelinks, a structural signal for engines, and keyword-bearing anchor text in-page.
B — Self-Dilution Trimmed (work log §4–§5)
3 duplicated sections cut down and cross-linked instead FIXED
The page carried its own generic treatments of property-owner liability, product liability and medical malpractice — full sections competing with the three site pages that own those topics, on a page that should be about the brain injury itself.
Each trimmed to a short, relevant paragraph that links out: property owner → slip-and-fall, product liability → product-liability, medical malpractice → medical-malpractice. The page loses nothing a brain-injury reader needs and stops competing with its own siblings.
Internal Linking & Cannibalization — work log §4 · §5 · §6
The ServiceEntity had NO related-service cross-links and no page linked in
Cannibalization audit: none on the primary term. GSC Pages.csv shows only this URL ranking for "miami brain injury lawyer" — no other page competes for it. The genuine overlap is narrower and known: infant / perinatal brain injury is shared with the birth-injury and cerebral-palsy pages. The real finding was the opposite of cannibalization — the page was a dead end in both directions: nothing linked in, and it linked to nothing.
12 inbound contextual links added — one per page, all with varied natural anchors
Source pageWhy it fits
personal-injury-lawyer-in-florida (hub)Top-level hub → strongest single link
miami-car-accident-attorneyLeading TBI cause
motorcycle-accident-attorney-miamiHighest head-injury rate per crash
miami-pedestrian-accident-attorneyLeading TBI cause
miami-hit-and-run-accident-lawyerCrash cluster
miami-head-on-collision-lawyerCrash cluster
construction-accident-lawyer-in-miamiFalls & struck-by — CDC's other top TBI cause
miami-commercial-vehicle-accident-lawyerCrash cluster
miami-pool-accident-attorneyNear-drowning → anoxic/hypoxic injury
miami-railroad-accident-lawyerHigh-energy impact
miami-jet-ski-accident-lawyerHigh-energy impact
miami-medical-malpractice-attorneyOxygen-deprivation & surgical brain injury
Anchors are deliberately varied — over-optimization risk comes from repeating one exact-match money phrase, so no anchor is reused. Infant / perinatal "brain damage" mentions were skipped on purpose to avoid pulling those queries away from the birth-injury and cerebral-palsy pages.
7 outbound related-service cross-links added to the ServiceEntity NEW
  • spinal-cord
  • birth-injury
  • cerebral-palsy
  • car-accident
  • slip-and-fall
  • medical-malpractice
  • product-liability
  • Root gap closed: the brain-injury ServiceEntity previously had no <ServicesRelated> block at all — App_Data/ServiceEntities.xml (~line 1135), XML validated after the edit.
  • ServiceEntities.xml is a data file — synced to bin; needs an app restart if the running instance cached it at startup.
Structured Data Added — work log §7
The article now emits three page-specific JSON-LD blocks where it previously emitted none. The most useful one is Service: its alternateName carries the naming variants the body cannot repeat naturally, and its areaServed carries the neighborhood list — the two things the keyword table says the page is thinnest on.
Schema 1
BreadcrumbList
Fields — 3 Items
position 1Home
position 2Personal Injury hub
position 3Miami Brain Injury Lawyer
Advantages
  • Breadcrumb rich result; explicit site-hierarchy signal
  • Same pattern as the product-liability page — consistent across service pages
Schema 2
WebPage + Speakable
Fields
@typeWebPage
speakable#bi-intro (id added to the intro block)
Advantages
  • Marks the concise passage a voice assistant / generative engine should read aloud
  • Voice / GEO signal (the rich result itself is limited to news publishers — stated honestly)
Schema 3
Service
Fields
serviceTypeBrain Injury Law
alternateNameBrain Injury Attorney / TBI Lawyer / Head Injury Attorney
areaServedNorth Miami · Coral Gables · Doral · Aventura · Hialeah · Miami Gardens
providerthe firm's organization node
Advantages
  • Carries the "attorney" / "TBI" / "head injury" naming variants without stuffing the prose
  • Declares the satellite cities that hold 2,400+ unearned impressions
  • Entity/GEO signal — not a SERP rich result, said plainly
Schema 4
FAQPage (skin microdata)
Coverage
1010 EN Q&As already present (unlike the product-liability page, which had 0)
The TBI-statistics answer rewritten — see the accuracy section
?Emission by the skin indicated by the template — VERIFY
Advantages
  • The Q&A format generative engines quote back most readily
No author node
On purpose — needs an attorney name
  • author / reviewedBy (E-E-A-T byline) is NOT added — the firm must name the reviewing attorney first. On a medical-legal page this is the highest-value item still open.
  • No offers / priceRange on the Service node — a fee statement is a Bar Rule 4-7 decision, not an SEO one.
  • Organization / WebSite schema remains a sitewide gap (separate ticket).

The count-refresh tooling strips Razor comments, <script> and markup before counting, so JSON-LD text does not inflate the keyword table — the 4,157-word figure is visible body + FAQ only. Each block is a distinct @type, so no duplicate entities.

Status — Done vs Still Open
miami-brain-injury-lawyer (En)  ·  every content item PENDING ATTORNEY REVIEW
✓ Done (applied to working tree)
  • 255 keywords merged from GSC + Semrush + bulk-volume into one master table
  • Body 2,545 → 4,157 words (+63%), 8 edits, each source-cited in-file
  • "brain injury attorney" 0 → 7 (12,100/mo head term, previously absent)
  • Stale 2002–2006 CDC stats replaced; invented "Type 1 / Type 2 TBI" removed
  • SOL "2 years" verified against HB 837; negligence vs med-mal now separated + statute of repose
  • Stats / severity + GCS / how-to / service-area sections; Table of Contents (IDs verified 1:1)
  • BreadcrumbList + WebPage/Speakable + Service JSON-LD (was none)
  • 12 inbound internal links (was 0); 7 related-service cross-links (block did not exist)
  • 3 self-diluting sections trimmed and cross-linked to the pages that own those topics