The Old Site and Why It Had to Go

The existing bdManagedIT site ran on WordPress 7.0. Not a fresh WordPress install either -- the kind that accumulates over years of deferred decisions. Plugins stacked on plugins. A theme nobody had touched since forever. PageSpeed scores that made me wince out loud the first time I pulled them up. For a small MSP team spending their days managing client networks and putting out fires, updating the website is always the last priority. So it never got updated.

The cosmetic stuff I could have lived with. The deeper problem was structural: the site wasn't built to sell. No dedicated pages for the specific services the team pitches on every sales call. No industry vertical pages for the sectors they actually work in. No location pages for the Georgia cities where their clients are. No compliance content for the regulated industries that make or break an MSP's pipeline. The site existed. It was not working. Those are two different things, and I've seen too many service businesses confuse them.

I've written about why WordPress-to-Astro migrations make sense for businesses like this -- the performance ceiling, the security surface, the maintenance drag. bdManagedIT was a textbook case. Sometimes the right call is to rip it out and start clean.

Before and After

The visual gap is as stark as the architecture gap. Below: the old WordPress site at bdmanagedit.com -- generic theme, stacked plugins, no local SEO structure -- followed by the new build live at managed IT services in north Georgia with an answer-first hero, trust metrics above the fold, and page architecture built for how MSP buyers actually search.

Before (WordPress 7.0 -- bdmanagedit.com)

bdManagedIT WordPress homepage before migration to Astro

After (Astro + Sanity -- bdsupport.com)

bdManagedIT Astro homepage after migration -- 95+ PageSpeed

The Stack and Why Each Piece Matters

The new build is Astro, Sanity CMS, and Netlify. I want to be specific about why I chose each piece for this project rather than just listing them as credentials.

Astro ships zero JavaScript to the browser by default. For an MSP site, that is the entire point. These pages do not need client-side interactivity. They need to load instantly on whatever device a prospect happens to be holding -- a phone on a job site, a laptop in a law firm conference room, a tablet at an accounting firm front desk. The 95+ PageSpeed target on both mobile and desktop was met at launch. Not after months of optimization hacks. At launch.

Sanity CMS gives the bdManagedIT team visual editing without touching code. They can update service descriptions, publish new case studies, add location pages, and manage blog content through a studio interface. For a small team with no webmaster on staff, this was non-negotiable. No more logging into WordPress, praying a plugin update doesn't detonate the site, and calling someone when it does.

Netlify handles CDN, build pipeline, and deployment. Pages are pre-built at deploy time and served from edge nodes close to the visitor. No origin server to go down. No PHP to patch. No database to secure. I have a detailed migration case study that gets into the numbers if you want the specifics.

Architecture Built for the MSP Sales Motion

The most important decisions on this project had nothing to do with the tech stack. They were about information architecture -- what pages exist, how they link to each other, and what specific job each page does in the sales process. Get that wrong and it doesn't matter how fast the site loads.

Branded Service Pages

bdManagedIT runs a portfolio of branded offerings: bdSecur, bdBackup, bdSafeMail, bdAware, bdVerify, bd-Voice. Each one got a dedicated page with its own schema markup, its own keyword targeting, its own conversion path. When a prospect searches for managed cybersecurity in Georgia, they should land on bdSecur -- not a generic services page that buries everything in a bulleted list three scrolls down.

This is a pattern I've refined across MSP website design projects. The branded service page is not just a marketing asset. It is a sales tool the team can drop into proposals, emails, and follow-up threads. It does two jobs at once.

Industry Vertical Pages

MSPs don't sell to "businesses." They sell to law firms worried about client confidentiality. Accounting practices that need SOX compliance sorted. Healthcare organizations bound by HIPAA. Construction companies that honestly just need their email to work and their files not to disappear. The new site has vertical pages for legal, accounting, insurance, financial services, healthcare, education, construction, government, nonprofit, engineering, hospitality, and retail.

Each page speaks the language of that specific industry. Each one links to the relevant compliance guides and case studies. Each one targets the search queries a decision-maker in that vertical actually types into Google at 10pm when something is broken or due.

Location Pages

The build launches with roughly 25 location pages across central and north Georgia, with a content model designed to scale past 50 without the architecture straining. Every location page is internally linked to relevant service pages and case studies, building the local topical authority that MSP SEO actually depends on.

bdManagedIT's brand promise is "Managed IT services with a small town feel." I took that seriously. The location pages aren't filler content cranked out to game search. They are the digital expression of that promise, and each one is specific to the community it represents.

Compliance Guide Pages

HIPAA, PCI-DSS, CJIS, SOX -- these frameworks drive purchasing decisions in bdManagedIT's target verticals more than almost anything else in the buying process. I built dedicated guide pages for each, gated for lead capture. A healthcare administrator searching "HIPAA compliant IT provider Georgia" should find a page that answers their actual questions, demonstrates real expertise, and gives them a reason to hand over their email. Not a brochure. An answer.

Case Study Pages

Case studies are internally linked to both location and service pages. A case study about helping a north Georgia law firm with cybersecurity links to the legal vertical page, the bdSecur page, and the relevant location page. This creates a web of internal authority that search engines -- traditional and AI alike -- can follow and credit. The structure is not accidental.

This is the part of the project I'm most deliberate about, and honestly the part I find most interesting right now. The 2026 MSP SEO playbook is not just about ranking in Google anymore. When a business owner asks ChatGPT, Claude, Perplexity, or Gemini who provides managed IT services in north Georgia, the answer should include bdManagedIT. That is a real, achievable goal if you build for it from the start rather than trying to retrofit it later.

Every relevant page carries structured data: Organization, LocalBusiness, Service, FAQPage, Person, and BreadcrumbList schema. Content follows answer-first patterns so LLMs can extract clean citations without guessing at meaning. The site includes an llms.txt file. Entity consistency is maintained across the site, Google Business Profile, and every directory listing in the ecosystem.

None of this is bolted on after the fact. It is baked into the page templates, the content model in Sanity, and the editorial guidelines I handed off to the team on day one.

The Lead Engine

A fast, well-structured site that ranks is useless without a conversion layer doing real work underneath it. Here is what I wired up:

  • HubSpot CRM with full source attribution -- every lead is tagged with how they found the site, what page they converted on, what content they engaged with before reaching out.
  • HubSpot CTAs for calls, contact forms, and meeting booking embedded throughout the site.
  • Interactive tools: a Managed IT Price Calculator, a Compliance Readiness Checker, an IT Security Self-Assessment, and an IT Maturity Self-Assessment. Each one collects structured data and pushes it into HubSpot.
  • A HubSpot AI chatbot trained on site content, so prospects get accurate answers without waiting for office hours.
  • Resend email automation for review requests, lead nurture sequences, onboarding flows, and quarterly check-in campaigns.
  • On-site reviews with Review and AggregateRating schema so star ratings surface directly in search results.

The lead engine doesn't just capture interest. It gives the sales team real context before they ever pick up the phone. That changes the quality of those first conversations significantly.

Domain Consolidation

The brand had two domains in play: bdmanagedit.com and bdsupport.com. I consolidated to bdsupport.com as the primary, with bdmanagedit.com sending 301 redirects. Every backlink pointing to the old domain now passes its equity to the new one. One domain, one authority profile, no signal dilution going forward. Simple in principle. Critical in practice.

Accessibility and Compliance

The site is WCAG-built with proper heading hierarchy, alt text patterns baked into the Sanity content model, keyboard navigation throughout, and sufficient color contrast at every breakpoint. Privacy policy and compliant cookie consent are in place. These aren't afterthoughts -- they're in the component library from the first commit.

Ownership

I want to be direct about this because I have strong opinions on it. The client owns everything: the codebase in their own Git repository, every piece of content, the modernized logo, all schema markup. The site runs on the client's own Netlify, Sanity, HubSpot, and Git accounts. If they fire me tomorrow, they keep the entire build and it keeps running. No vendor lock-in, no proprietary templates, no hostage situation where switching costs trap someone in a bad relationship. I've been on the receiving end of that kind of setup and I won't build it.

What Happens After Launch

The build is the foundation. What makes it compound over time is the ongoing SEO Growth Partnership on the Accelerate tier: 20+ new articles per quarter, continuous expansion of location and industry pages, guaranteed quality backlinks, 200+ keyword tracking across both Google and LLMs, weekly technical SEO crawls, and monthly strategy sessions to adjust based on what the data shows.

The site is designed to grow. The Sanity content model, the internal linking architecture, the schema patterns -- all of it is constructed so every new page makes every existing page stronger. That is not an accident. That is the whole point.

The site is live at managed IT services in north Georgia, with bdmanagedit.com 301-redirecting in to consolidate domain authority and preserve every existing backlink.

FAQ

Why use Astro instead of WordPress for an MSP website?

Astro ships zero JavaScript by default, which means pages load instantly without the plugin bloat and security surface of a WordPress install. For an MSP that needs to demonstrate technical competence to prospects, a site that scores 95+ on PageSpeed is a better first impression than one that takes four seconds to render. The argument basically makes itself.

How does Sanity CMS help a small MSP team manage content?

Sanity gives the team a visual editing studio where they can update service pages, publish blog posts, and add location pages without writing code or worrying about plugin conflicts. Content types are structured in advance, so every new page automatically inherits the right schema, internal links, and layout. The team doesn't need a webmaster. They need a tool that doesn't fight them.

What does consolidating bdmanagedit.com and bdsupport.com do for SEO?

Running two domains splits backlink equity and sends mixed signals to search engines about which site is authoritative. The 301 redirect from bdmanagedit.com to bdsupport.com funnels all accumulated link equity into a single domain, giving every page a stronger authority signal in both traditional and AI search results. One target is easier to build than two.

How is the site built to get cited by AI search engines like ChatGPT and Perplexity?

Every relevant page includes Organization, LocalBusiness, Service, and FAQPage schema. Content follows answer-first patterns that LLMs can parse cleanly without inferring intent. An llms.txt file and consistent entity data across the site and external profiles help AI models identify bdManagedIT as a credible source worth citing. This has to be built in from the start -- you can't reliably retrofit it.

Who owns the bdManagedIT website and codebase after the build?

The client owns everything -- the Git repository, all content, the logo, every piece of schema markup. The site runs entirely on the client's own Netlify, Sanity, HubSpot, and Git accounts. Zero vendor lock-in, full control, no ongoing dependency on me to keep the lights on. That is the only way I'm comfortable delivering work.