A neurology practice that needed more site than Squarespace could give it
Dr. Kurian runs a neurology practice in Santa Clarita. His Squarespace site looked dated, didn't cover everything he treats, and had little SEO work underneath it. I rebuilt it on Next.js and Sanity CMS, accessible from the start, without breaking what already ranked.
laneurosciences.com- 7 → 28pages, Squarespace to now
- 0 → 7service pages for what he treats
- 1 → 10structured data types on the homepage
- 100Lighthouse accessibility and SEO

Keeping what already ranked
He was already ranking well, mostly because there isn't much neurology competition in Santa Clarita. I wasn't fixing something broken. I was making sure I didn't break it while building out everything that had never been there.
No service pages, no local content, none of the structured data that tells a search engine what a medical practice actually is.


A page for everything he treats
The site is 28 pages now. Seven service pages cover what he actually treats, from migraine and epilepsy to memory loss and pediatric neurology. Then a clinical blog, and the usual practice pages for contact, reviews, clinical trials and medical-legal work.


Eight posts, carried across
The eight posts he already had came across from Squarespace through a migration script that converted them into Sanity's content format. The generated slugs got cleaned up, and every old URL redirects.
His staff can edit all of it and add new posts without calling me.


Accessible from day one
He never asked for accessibility. I build it into every site, not just the ones for medical practices and their patients.
The site is WCAG 2.2 AA, and it stays that way. Axe runs against nine routes that cover every section type and interactive widget, the form, the accordion, the carousel, and it has to come back with zero violations. I went through the awkward parts with VoiceOver by hand as well.


Getting the editor right
He wanted to edit his own pages the way Squarespace had let him. That was the hardest part to get right. I looked at React Bricks, Payload, Puck and Sanity's own Presentation tool, then built working spikes rather than trusting the documentation.
Puck was good, but getting it to sit inside Sanity was a lot of work for not much gain. So I built on Sanity Presentation instead, and reorganized the content model around the way he actually thinks about his pages.
