The problem
Buena Vida Adult Day Health Center provides adult day care, home care, transportation, home-delivered meals and case management across four locations in Kentucky. Their audience is bilingual, and a large share of it arrives through Medicaid’s Home and Community-Based waiver programme.
Their site did not reflect any of that. It ran on an ageing WordPress installation that had accumulated years of plugins and theme changes, it had not been built with search in mind, and it did not rank for the searches that bring a family to a provider like this one — service plus city, in either language.
For a provider whose enquiries begin with a search, that is not a cosmetic problem. It is the top of the funnel.
What we did
We rebuilt the site rather than restyling it, and we changed the stack while we were there.
Astro instead of WordPress. The site is content that changes occasionally and must load fast for people on phones, often older visitors on slower connections. That is exactly the case Astro is built for: pages ship as static HTML with no framework runtime unless a component genuinely needs one. It also removes an entire class of maintenance — no plugin updates, no PHP version deadlines, no admin surface to keep patched.
Bilingual as routing, not as a widget. English and Spanish are separate routes with their own URLs and hreflang annotations, so a search engine can index each language properly and a Spanish-speaking family can be served a Spanish page directly from search results. Translation plugins layered over a single URL cannot do that.
SEO built into the structure. Titles and headings target the service together with the place, which is how these searches are actually typed. Structured data describes the organisation and its locations in a form search engines can read directly, and a generated sitemap index keeps every page discoverable as the site grows.
What this demonstrates
The work is a combination of three of our services rather than a one-off: the design and build, the search strategy, and the ongoing growth work that follows a launch.
It also shows the position we take on stack choices. WordPress was not replaced because it is unfashionable — it was replaced because a brochure site with four locations and two languages does not need a database and an admin panel to render a page, and paying that cost every month in maintenance and load time bought this client nothing.
A note on fit
A rebuild is the right call when the existing site is holding back the thing the business runs on, as it was here. It is the wrong call when a site is merely dated but converting fine — in that case the search and content work stands on its own, and we would say so rather than sell a rebuild.
