This case study explains how we rebuilt bdManagedIT, a Central Georgia managed service provider. We moved the site from an aging WordPress install to a static build on Astro, Sanity CMS, and Netlify. The result: 95+ PageSpeed scores, a full compliance and vertical page architecture, HubSpot-driven lead capture, and structured data built for Google and AI search.

Key takeaways

  • bdManagedIT moved from WordPress to Astro + Sanity + Netlify, hitting 95+ PageSpeed scores at launch with zero-JS static pages.
  • The rebuild adds branded service pages, industry vertical pages, roughly 25 location pages, and dedicated compliance guides for HIPAA, PCI-DSS, CJIS, and SOX.
  • HubSpot CRM, four interactive lead-capture tools, and a trained AI chatbot form the lead engine behind the site.
  • Structured data, answer-first content, and an llms.txt file are built in to help the site get cited by AI search tools such as ChatGPT and Perplexity.
  • The client owns the full codebase, content, and every connected account, with no vendor lock-in.

Updated 15 August 2026: sources added, experience claims checked against our project record, summary added.

The Old Site and Why It Had to Go

The existing bdManagedIT site ran on WordPress 7.0, and not a fresh install. It was the kind of build that piles up over years of small delays. Plugins stacked on plugins. A theme nobody touched in years. PageSpeed scores poor enough to notice right away. A small MSP team spends its days managing client networks and putting out fires. Updating the website is always the last priority. So it never got updated.

The cosmetic issues were easy to live with. The deeper problem ran deeper: the site wasn't built to sell. There were no dedicated pages for the specific services the team pitches on every sales call. There were no industry vertical pages for the sectors they actually work in. There were no location pages for the Georgia cities where their clients are. There was 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 many service businesses confuse them.

We've written before 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

Picture the same brand living in two different eras. Below is the old WordPress site at bdmanagedit.com: generic theme, stacked plugins, no local SEO structure. Then the new build live at managed IT services in north Georgia, with an answer-first hero, trust metrics above the fold, and a 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

Why these three tools? The new build runs on Astro, Sanity CMS, and Netlify. Each piece was chosen for a clear reason, not just listed as a credential.

Start with Astro, which ships zero JavaScript to the browser by default. For an MSP site, that is the whole point. These pages don't need client-side interactivity. They need to load instantly on whatever device a prospect is 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 hit at launch, not after months of extra work.

Content lives in Sanity CMS, which 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 a must. No more logging into WordPress, hoping a plugin update doesn't break the site, and calling someone when it does.

Then there's Netlify, which handles CDN, build pipeline, and deployment. Pages are pre-built at deploy time and served from edge nodes close to the visitor. There's no origin server to go down, no PHP to patch, no database to secure. We have a detailed migration case study that covers the numbers in full.

Architecture Built for the MSP Sales Motion

What actually decides whether an MSP website converts? Not the tech stack. The most important choices on this project were about information architecture: what pages exist, how they link to each other, and what job each page does in the sales process. Get that wrong and it won'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, and its own path to conversion. 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 pattern reflects how we approach MSP website design in general. 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, and healthcare organizations bound by HIPAA. Construction companies just need their email to work and their files to stay put. 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. It links to the relevant compliance guides and case studies. It targets the search queries a decision-maker in that vertical types into Google at 10pm when something is broken.

Location Pages

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

bdManagedIT's brand promise is "Managed IT services with a small town feel." The location pages reflect that promise. They aren't filler content built to game search. 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. We 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 real questions and shows real expertise. It should give them a reason to hand over their email. Not a brochure. An answer.

Case Study Pages

Case studies link internally 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 builds a web of internal authority that search engines, traditional and AI alike, can follow and credit. The structure is not an accident.

This is the part of the project we care about most. The 2026 MSP SEO playbook isn't 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, reachable goal if you build for it from the start instead of trying to bolt it on later.

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

None of this is added after the fact. It is built into the page templates, the content model in Sanity, and the editorial guidelines handed 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. HubSpot CRM anchors the whole system with full source attribution. Every lead is tagged with how they found the site, what page they converted on, and what content they read before reaching out.

HubSpot CTAs for calls, contact forms, and meeting booking sit throughout the site. Four interactive tools, a Managed IT Price Calculator, a Compliance Readiness Checker, an IT Security Self-Assessment, and an IT Maturity Self-Assessment, each collect structured data and push it into HubSpot. A HubSpot AI chatbot trained on site content answers prospect questions without waiting for office hours. Resend handles email automation for review requests, lead nurture sequences, onboarding flows, and quarterly check-in campaigns. On-site reviews carry Review and AggregateRating schema so star ratings show up 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 a great deal.

Domain Consolidation

The brand had two domains in play: bdmanagedit.com and bdsupport.com. We consolidated to bdsupport.com as the primary domain, 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 loss going forward. Simple in principle, critical in practice.

Accessibility and Compliance

The site is built to WCAG standards, with proper heading hierarchy, alt text patterns baked into the Sanity content model, keyboard navigation throughout, and strong 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

We want to be clear about this. The client owns everything: the codebase in their own Git repository, every piece of content, the modernized logo, and all schema markup. The site runs on the client's own Netlify, Sanity, HubSpot, and Git accounts. If they end the engagement tomorrow, they keep the entire build and it keeps running. No vendor lock-in, no proprietary templates, no trap where switching costs leave someone stuck in a bad relationship.

What Happens After Launch

The build is the foundation. What makes it grow over time is the ongoing SEO Growth Partnership on the Accelerate tier. That includes 20+ new articles per quarter, steady 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 built to grow. The Sanity content model, the internal linking architecture, the schema patterns: all of it is built 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 keep every existing backlink.

FAQ

Why use Astro instead of WordPress for an MSP website?

Astro ships zero JavaScript by default, so pages load instantly without the plugin bloat and security risk of a typical WordPress install. For an MSP that needs to show technical skill to prospects, a site that scores 95+ on PageSpeed makes a stronger first impression than one that takes several seconds to load.

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 gets 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 the real one. The 301 redirect from bdmanagedit.com to bdsupport.com sends all built-up link equity into a single domain, giving every page a stronger authority signal in both traditional and AI search results.

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, and content follows answer-first patterns that LLMs can read cleanly without guessing at intent. An llms.txt file and consistent entity data across the site and outside profiles help AI models see bdManagedIT as a credible source worth citing. This has to be built in from the start; it's hard to fix well later.

Who owns the bdManagedIT website and codebase after the build?

The client owns everything: the Git repository, all content, the logo, and every piece of schema markup. The site runs entirely on the client's own Netlify, Sanity, HubSpot, and Git accounts, with zero vendor lock-in and no ongoing need for us to keep it running.