website design
Your website isn’t just a first impression - it’s where your marketing either works or falls apart.
I design and build Squarespace and WordPress websites for small businesses and nonprofits that need more than something that “looks good.” Your site should be clear, easy to navigate, and built to convert visitors into real customers or supporters.
Many websites fail because they’re designed in isolation. I build sites that work as part of your full marketing system, so your ads, SEO, and messaging all connect.
I specialize in Squarespace and WordPress builds that are easy to manage, fast to load, and structured to support your marketing - especially Google Ads and search traffic.
Because I also work deeply in Google Ads and analytics, I build websites with performance in mind from the start. That means:
• Clear messaging and user flow
• Conversion-focused layouts
• Proper tracking and data integration
• A structure that supports long-term growth
Whether you need a simple service-based site or a more complex build, I focus on creating something that works for your business now - and can grow with you over time.
If your current site isn’t converting, or you need something built the right way from the start, I can help you create a site that actually supports your goals.
Case Study
Zebulon Solutions WordPress Website Migration & System Recovery
Overview
Zebulon Solutions needed their website migrated to a new hosting environment on WP Engine. What initially appeared to be a standard deployment became a multi-layered system issue involving DNS routing, database inconsistencies, and broken administrative permissions.
The project required full-stack troubleshooting across hosting, domain configuration, and WordPress internals to stabilize the site and restore full functionality.
The Problem
After pushing the development environment live:
The live domain was still showing the old site
WP Engine environments were out of sync
The WordPress admin dashboard was missing core functionality (plugins, themes, users)
Admin access appeared intact but was silently restricted
A REST API error indicated underlying routing inconsistencies
This created a situation where:
The site looked functional on the surface
But was structurally unstable underneath
What Was Happening (Root Cause)
The issue was not a single failure, but a combination of:
DNS routing still partially tied to the previous host (GoDaddy)
Cache layers masking environment changes
A full database push that resulted in corrupted or misaligned user role permissions
WordPress recognizing the admin user as a lower role, hiding critical functionality
The Solution
This required diagnosing and resolving issues across multiple system layers:
1. Hosting & Environment Sync
Verified WP Engine production environment
Re-ran full environment push (files + database)
Cleared all server-level caching
2. DNS & Domain Routing
Confirmed domain was pointing correctly to WP Engine
Identified GoDaddy’s role as DNS provider (not host)
Ensured proper propagation and routing behavior
3. Database-Level Repair (Critical Fix)
Accessed production database via phpMyAdmin
Located user role inconsistencies in:
wp_users
wp_usermeta
Manually restored administrator permissions by correcting:
wp_capabilities
wp_user_level
This step restored full backend access and functionality
4. WordPress System Validation
Flushed permalinks
Verified REST API integrity
Regenerated Elementor CSS/data
Confirmed plugin and theme functionality
The Result
Site fully live on WP Engine
DNS correctly routed
Full admin functionality restored
All plugins, themes, and tools accessible
No data loss
System stable across frontend and backend
Why This Matters
This project highlights a common but critical issue:
Website migrations don’t fail loudly — they fail quietly.
Many deployments appear “successful” while underlying systems are broken:
hidden permission issues
misaligned environments
caching masking real problems
Fixing these requires:
understanding how hosting, DNS, and WordPress interact
and knowing where to intervene when the UI doesn’t tell the full story
My Approach
I approach builds and migrations as systems, not just websites.
That means:
tracing issues across layers (not guessing)
validating both visible and invisible functionality
and fixing problems at the root, not just the symptom

