Selected work / Custom Website
Aneta Dang
A faster website without starting over.
After more than a decade on WordPress, Aneta Dang's website needed a modern foundation without abandoning the content and search visibility it had already built.
We redesigned and rebuilt the site in Astro, improving performance, responsive behaviour, content organization, and SEO while carrying forward the value of the existing website.
01 / The starting point
A decade-old website was ready for a new foundation.
Aneta's original WordPress website dated back to 2014.
It had done something important during that time: accumulated useful content, established organic search visibility, and become an existing part of the business.
The problem wasn't that everything needed to be replaced. The website itself had simply aged around content and search equity that were still valuable.
Modernize the website. Keep the value it already earned.
02 / The goals
Faster. Clearer. Better on every screen.
The rebuild had several connected goals rather than being a purely visual redesign.
Performance
Faster page delivery and a lighter frontend.
Responsive design
Pages built properly for phones, tablets, and desktops.
Content
Make services and information easier to understand.
SEO
Preserve existing search value while improving the technical and on-page foundation.
Design
Modernize the presentation without making the website unnecessarily elaborate.
Maintainability
Move onto a clean foundation suitable for ongoing development.
03 / Content structure
Make what she does easier to understand.
Wellness and service-provider websites have a particular communication problem. Visitors may arrive knowing the practitioner's name, a specific treatment, a concern they want help with, or very little about the available services.
The website therefore needs to organize the information clearly enough that people can understand Aneta's work and determine what is relevant to them.
Active Release Techniques
Massage therapy
Services
Workshops
Testimonials
Blog / content
Pricing / booking
Contact
Better content structure helps both people and search engines understand the site.
04 / WordPress → Astro
A rebuild shouldn't mean starting from zero.
Moving away from WordPress was not simply a matter of recreating pages.
The existing website represented more than ten years of published URLs, content, internal relationships, and established search presence. The migration needed to preserve what mattered while replacing the underlying website.
WordPress itself wasn't the enemy. This particular website had reached the point where a rebuild made sense.
Changing platforms shouldn't erase years of work.
01
Existing WordPress site
02
Content + URLs + SEO signals
03
Migration / redesign
04
Astro website
Content
Carry useful existing material forward.
URL structure
Preserve important destinations or redirect appropriately where structures change.
Metadata
Carry forward and improve relevant search metadata.
Internal links
Maintain useful relationships between pages.
Technical foundation
Replace the aging frontend and platform with the new Astro implementation.
Conceptual migration view, not an infrastructure diagram.
05 / Search
Protect what was working. Improve what wasn't.
SEO wasn't being introduced for the first time.
The existing website already had SEO work and organic search visibility, which meant the migration needed to treat search as a constraint from the beginning.
We carried the established SEO foundation into the new website while updating and improving the site's search implementation. Continuity was the goal—not a guarantee that every ranking would stay exactly the same. That work sits alongside the broader approach outlined in our SEO service.
Page titles and descriptions
Semantic page structure
Internal linking
URL continuity / redirects
Crawlability
Content organization
Performance
Responsive / mobile experience
Technical SEO foundations
06 / Performance
A lighter foundation for the website it needed to be.
Astro and a static-first architecture were an appropriate technical choice for this website and its requirements: a public content site that needed a lighter delivery model without unnecessary client-side JavaScript.
The goal wasn't to use Astro because Astro is fashionable. The goal was a foundation sized for the site being built.
Old foundation
- WordPress implementation
- Aging site foundation
- More platform surface than this site needed
New foundation
- Astro
- Static-first delivery
- Purpose-built frontend
- Minimal client-side JavaScript
Use the amount of technology the website actually needs.
07 / Responsive design
The mobile version isn't the desktop version squeezed smaller.
One of the rebuild goals was improving the responsive experience.
Service-provider websites are especially likely to be visited from phones by people researching services, reading about the practitioner, checking pricing, finding contact information, or preparing to book.
Pages should be intentionally composed for smaller screens rather than merely technically responsive.
08 / Booking
Keep the path to booking straightforward.
The website's responsibility is to help visitors understand Aneta and her services and then provide a clear route into booking.
Current booking uses Square as the external booking destination. That is an outbound booking flow—not a Square booking system rebuilt into the website.
A deeper booking integration may be considered later as requirements become clearer. It is not presented here as completed work.
Not every external system needs to be rebuilt inside the website.
09 / Delivery
A major rebuild without a drawn-out project.
The project had a notably quick turnaround.
An established website was redesigned, migrated from WordPress, rebuilt in Astro, and prepared for launch without turning the migration into an unnecessarily long redevelopment cycle.
That depended on defined scope, understanding the existing site first, identifying what needed to survive the migration, building on a simpler architecture, focused implementation, and deliberate migration work.
Move quickly where the problem is understood. Slow down where the risk requires it.
10 / Ongoing
Launch wasn't the end of the relationship.
We continue to maintain the website.
Future development may include a more integrated booking experience as requirements become clearer. That work remains roadmap only and should not be treated as existing functionality.
11 / The takeaway
Change the platform. Keep what it earned.
AnetaDang.com shows a different kind of custom development problem.
There was no need for a complicated application or a large technology stack. The challenge was replacing the underlying implementation while carrying forward the established site's content, search foundation, and accumulated value.
Good redevelopment isn't about replacing everything. It's about knowing what should change—and what should survive the change. That continuity work supports search; it does not guarantee rankings.
Related work
More project records.
Have an established website?
Keep what works. Rebuild what doesn't.
If your website has years of content, search visibility, and business history behind it, replacing the platform shouldn't mean throwing that value away. We'll determine what should be preserved, what should be improved, and how the new site should be built.