Rebuilding My Firm's Website With an AI Pair
I rebuilt my consulting firm's website in four days with an AI coding partner. The new look mattered less than two other things: the claims I removed, and the faults I only found by looking at the live pages.

Key Results
- Pages with search markup went from 3 to 47
- Pages listed in the sitemap went from 30 to 47
- 116 animated dots and pulses removed from the home page's first screen
- Service pages cut from 17 to 12 where no real work backed them
- Page titles over 60 characters went from 11 of 48 to 0 of 48
What was broken
My consulting firm's website looked busy and said too much.
The first screen had 116 animated dots and pulses, plus a bouncing arrow. It pulled a stock photo from another site, a popup jumped out after five seconds, and two floating buttons sat on top of each other.
The words had a bigger problem. The home page showed nine company names, and a visitor would read them as clients, but they were places where my partners and I had worked as employees. The case studies carried the same fault in a stronger form, because a case study tells a story about the work.
Some service pages had no real work behind them at all. If a buyer had asked "show me one you did", we'd have had no answer.
Search told the same story. In six months the site earned 112 clicks, and 107 of them went to the home page. No article had ever earned a single click. The case studies page sat third in results, yet only 1.4 percent of the people who saw it clicked, so the site was being shown and almost nobody wanted to open it.
What I built
I rebuilt the site over four days, from 24 to 27 August, with an AI coding partner, and made 51 changes to the code in that time. I made the calls, while the AI did the heavy typing and the measuring.
I started by taking things out: the animation, the stock photos, the popup and the second button all went. Then I set one simple layout for every section, with a thin line, a small label on the left and the content on the right. Nothing is centred and nothing sits in a box, so the eye starts in the same place every time.
Then came the honesty pass, in which I checked every claim against our real work records. The nine names are now labelled as past employers, and every figure says whose work it came from. One savings claim didn't add up, so it went. All eight case studies now carry a line saying the work was done in an operating role rather than for a client. I cut five service pages that nothing in our records could back, and their old links now point to the nearest real page.
After that came the parts a visitor never sees. Only 3 pages carried the markup that helps search engines read a page, and now 47 do. The sitemap had been written by hand and had fallen behind: 15 pages added through the site editor were missing from it, so they'd never been sent to search engines at all. The sitemap is now built from what actually ships, and it went from 30 pages to 47.
Last, I rewrote the page titles from real search data. Every title had led with our own words instead of the reader's problem. The worst one opened with "Not client engagements." That statement is true and it stays on the page, but as the first words in a search result it gave nobody a reason to click.
What changed
The new site was merged on 27 August, after my partner signed off.
The most useful finds came from looking at the live pages, because the code alone hid them. Three layout faults were invisible in the code and obvious on screen, and one button had been squeezed into four stacked words.
A bigger fault involved the browser tab. When a visitor clicked from one page to the next, the tab kept the old page's title, so our traffic reports recorded the wrong page name on every click. My first fix looked as if it worked, but when I checked again I found two copies of every hidden tag, the old one and the new one, and the page only looked fixed. The second fix cleared it properly.
By the evening of 30 August, 0 of 48 pages had a title over 60 characters, against 11 that morning. The update that carried those titles to the live site ran about five hours late. I waited instead of forcing it, and the wait showed me that the job was slow rather than broken.
Not everything is done. On 30 August, 3 of 17 site checks still failed, and one of them was 8 pages that had no visitor in 28 days. That's a demand problem that better code won't solve, and now at least it has a number.
What I would do differently
I'd check every claim before designing anything, because the honesty pass changed more than the new look did. I'd also look at every change on the live page as well as in the code, since most of the real faults only showed up there.
I'd never keep a sitemap by hand, because a list kept by hand drifts out of date. And I'd test every fix twice, because the fix that looks right is the one most likely to hide the next fault.
Want a similar result?
Let's talk about installing the right operating system for your business.
Book a Call