A strong, well maintained presence that is being held back in exactly three places. Five communities, each with its own sub-brand, over 75 years of history, and search demand that already reaches you. The gap is not effort. It is consolidation and machine readability.
Above the senior living average we see, and roughly 12 points below what this portfolio should carry.
Read the three highlighted numbers together. Families are asking 3,487 questions inside the search results you already rank for, Google is assembling 1,030 AI answers that touch your pages, and you have published zero structured answers for either system to read. Every one of those 9,334 monthly visits arrives with no paid support behind it, which means the organic asset is doing all the work.
These are the three that move the number. Everything else on the site is in good order.
A visitor who searches for assisted living in Virginia, sees LifeSpire in the results, and clicks, lands on an error page. Search engines are still serving the URL because the page ranked before it disappeared. Assisted living is the single highest intent term in your category, and it is the one path that currently ends in nothing.
lifespireliving.org/assisted-living returns HTTP 404 and is still present in organic results. Assisted living is also a living option listed in your own navigation, so the internal expectation and the external result disagree.
Fix: restore the page at the same URL, or 301 it to the correct living options destination on the same day. Then re-submit to Search Console so the ranking transfers rather than decays.
Answer engines prefer sources that hand them a clean question and a clean answer. Your pages contain the answers, in good prose, but nothing on the site is marked up so a machine can lift a question and attribute it to LifeSpire. The result is that you are being read and paraphrased without being credited, and the families who see those answers never see your name attached.
Fix: publish FAQPage JSON-LD on the living options pages and on every one of the five community pages, using the questions families actually ask about entrance fees, levels of care, and what a Life Plan Community commits to. The sample site linked below already carries valid FAQPage markup you can lift.
The Glebe, The Culpeper, The Summit, Lakewood, and The Chesapeake each carry their own mark and their own voice. That is right for local pride in Daleville, Culpeper, Lynchburg, Richmond, and Newport News. It is a problem when the parent brand has to compete with its own children for the same Virginia search terms, and when a family arriving at one community has no obvious route to the other four or to AgeSmart.
Find a Community but no side-by-side comparison, so cross-community referral depends on the reader already knowing the portfolio exists.
Fix: keep the local marks, but unify the schema, the breadcrumbs, and the contact path under the LifeSpire entity, and add one comparison view that puts all five communities and AgeSmart on a single page. This is the change that compounds with finding 02.
Ordered so each phase makes the next one cheaper. Nothing here needs a redesign.
/assisted-living and re-submit the URL.Outcome: the highest intent term in the category stops ending in an error page.
Outcome: 3,487 People Also Ask results gain a citable LifeSpire answer.
Outcome: one number per community, one view for the whole portfolio.