We made a 35-year sitework company look its size online

1. Problem

   An earlier rebuild never launched

   Pro Innovations hired another agency about six months before us. That agency wanted the company to write its own content and load it into a CMS, so the new site never shipped and the four-page GoDaddy site stayed up.

2. Solution

   We didn't wait on content. We knew the services, and the company had its own job photos, so we wrote every page ourselves and folded in the owner's corrections as they came.

3. Result

   The contract was signed August 21, 2026. The new site was live on its own domain September 5.

1. Problem

   One site was carrying two businesses

   Mullins Supply Barn, a farm and home store in Crittenden, is its own business, but it lived on the Pro Innovations site as a single page. With a Lowe's on the way, it needed to stand on its own.

2. Solution

   We built Mullins a one-page site at mullinssupplybarn.com, pointed every Mullins link on the Pro Innovations site at it, and permanently redirected both old store pages there so no link or search result was lost.

3. Result

   Each business now reads as what it is, and the store has a site of its own to send people to.

1. Problem

   Twelve services in one bullet list

   The old homepage named every sitework service in a single bulleted list. Its only H1 read "Click the logos below for information about", its page title was the domain name, and it had no meta description.

2. Solution

   Each of the twelve services got a full page with a short answer up top, what drives the cost, the equipment and an FAQ. We grouped them under a Land Development hub beside Custom Builds and Custom Remodeling, so the site splits the work the way the business does.

3. Result

   Someone searching for one service lands on a page about that service, not a list.

1. Problem

   Town pages that could have read like copies

   Twelve services across eight towns makes 96 possible service-by-town pages. Swap a town name into a template 96 times and you get pages search engines are built to ignore.

2. Solution

   We built only the 58 pairings with something true and local to say. Each draws on that town's USDA soil series, its drainage from Kentucky Geological Survey mapping and its Census numbers, with a source recorded for every claim. Then we measured the overlap between pages to confirm the only shared text was the menu and footer.

3. Result

   No two town pages make the same case, because no two towns sit on the same ground.

1. Problem

   Two notes from the owner

   Before launch, the owner flagged two things. The copy described the fleet by how many trucks it has, which isn't how the owner talks about the company. And one bulldozer photo stood in for production work, the finish stage of grading, drainage, seed and yard installs, on the menu panel and two service pages.

2. Solution

   We rewrote 102 fleet mentions across 27 files to describe a triaxle dump fleet by what it is, sentence by sentence rather than find and replace, and turned two animated truck counters into service-area counts. We swapped the bulldozer for a crew setting a block wall, a finished seeded grade and an established green slope, and kept the dozer in the projects gallery, where it's honest.

3. Result

   The site describes the company the way the owner does.

1. +19 pts

   Performance

2. +17 pts

   SEO

3. +17 pts

   Accessibility

4. +4 pts

   Best practices

How much site there was, and how much there is.

Every page in the tree above is a page the site serves, grouped as the navigation groups it.

proinnovationsllc.com

light