A few months ago I made a decision that should have been embarrassing: I rebuilt my own website. The old one had been live for less than a year. Most web designers wouldn’t admit publicly that their first attempt didn’t work. I’m telling you anyway because there are lessons in it that probably apply to your site too.
Here’s the honest story.
What the old site looked like
The old Gridline Company site was built on Lovable, a no-code platform that uses AI to generate React applications. It looked clean. It loaded reasonably fast. It had pages for the things I do (web design, branding, consulting, AI). On the surface, it was fine.
Underneath, it was almost completely invisible to Google. Here’s what I mean.
When you visited any page on the old site, the HTML that loaded first was nearly empty. It looked like this:
<title>The Gridline Company</title>
<meta name="description" content="Creative solutions for your business" />
<div id="root"></div>Every page had the same generic title. Every page had the same vague description. The actual content of each page was rendered by JavaScript after the page loaded, which meant Google couldn’t reliably read it.
The author meta tag still said “Lovable.” The Open Graph image was a placeholder pulling from lovable.dev. There were no H1 tags in the HTML. No schema markup. No location signals anywhere.
In other words, my own website was a textbook example of the exact problems I tell clients to avoid.
Why I didn’t notice for so long
This is the part I find interesting. I’m a web designer. I know what good SEO looks like. I look at other people’s sites for a living. And I still missed it on my own site for months.
Here’s why: the site looked good in my browser. It loaded. It worked. When I clicked around, everything functioned. The problem was invisible to me because I was already inside the site, not arriving at it through Google.
The only way to see the problem is to look at the page source (right-click, “View page source”) or to check Google Search Console and see how few impressions you’re getting. I wasn’t doing either regularly. So I wasn’t seeing what Google was seeing.
I’d bet a lot of small business owners are in the same spot right now. Their site looks fine to them. It’s quietly invisible to Google.
Why I rebuilt instead of patched
Once I realized what was happening, I had two options. Patch the old site, or rebuild from scratch.
I rebuilt. Three reasons.
The platform was the problem, not the content. Lovable’s React-based output meant the JS-rendering issue was structural. Patching wouldn’t fix it. I’d be fighting the tool the whole time.
A rebuild let me bake SEO in from the foundation. Patching means adding stuff on top of decisions you’d never make today. Rebuilding means starting with the right architecture and the right content model. The work isn’t actually that much more, and the result is dramatically better.
The strategic positioning needed to change. When I built the original site I was still figuring out what The Gridline Company was. By the time I rebuilt, I knew. The new site leads with the AI-for-small-business angle that’s actually my best opportunity. The old one buried it.
What I prioritized in the rebuild
Five things, in this order:
1. Server-rendered HTML. Every page on the new site sends real, complete HTML on the first request. Search engines and AI crawlers see the actual content immediately, not a JavaScript shell. This is the single most important SEO decision I made.
2. Per-page titles and meta descriptions. Every page has its own. The web design service page is titled differently from the contact page is differently from a city page. Sounds basic. Most small business sites don’t do this.
3. Real local signals. The new site has 12 city pages, one for each city I serve. Each one mentions specific local landmarks, business districts, and industries. This is what tells Google I’m actually in West Covina, not just claiming to be.
4. Transparent pricing. The old site didn’t show prices. The new one does. Numbers, on the page, no “request a quote” form. This is the single best conversion change I made.
5. A real human voice. The old site read like every other web design agency: “We craft beautiful websites for visionary brands.” The new one reads like me. First person. Plain language. A few opinions. Some things you wouldn’t say at a stuffy agency. The difference is night and day.
Three things I learned
You probably can’t audit your own site honestly. I should have caught the problems with mine months earlier. I didn’t because I knew the site too well to see it fresh. If you have a website you’re not sure about, find someone who’s never seen it and ask them: “what does this business do, and what should I do next?” If they can’t answer in 5 seconds, you have a problem.
The right rebuild costs less than the wrong patches. I considered patching the old site over and over for weeks before committing to a rebuild. Once I committed, the rebuild took less time than I’d already spent thinking about patching. The lesson: if a rebuild is what’s needed, do it. Don’t pile up half-fixes.
Publishing your prices is the second-best decision a small business can make. The first is having a website that loads fast and ranks. The second is showing what you charge. I lost a few prospects who saw the prices and decided they couldn’t afford it. That’s fine. Those weren’t going to be good clients anyway. The ones who did reach out were already half-sold by the time we talked. Worth it.
Why this matters for you
If your website was built more than a year ago, or if it was built using a no-code AI tool, there’s a real chance it has the same invisible problems mine did. Here’s how to check in 5 minutes:
- Open your homepage in a browser.
- Right-click anywhere and pick “View page source” (or “Inspect” then look at the HTML).
- Look for: a unique
<title>tag, a<meta name="description">, an<h1>tag, and visible body content.
If your title is generic, your description is missing, your H1 is missing, or all the content is hidden behind a <div id="root"></div> style placeholder, you have the same problem I did.
The fix is sometimes a patch and sometimes a rebuild. The website launch checklist walks through the 50 things to verify either way. It’s free and takes about 30 minutes to go through.
The TL;DR
I built my first Gridline Company site in a weekend on a no-code platform. It looked good but was invisible to Google. I rebuilt it on a real framework with proper SEO foundations. The rebuild took six weeks but the new site is dramatically better positioned for the next three years.
If your site might be in the same spot, run the page-source check above. Five minutes, and you’ll know.
If you want a second opinion or just want to talk through whether a rebuild makes sense for your business, the free 30-minute chat is the fastest way to find out. I’ll tell you honestly whether you need to rebuild, patch, or leave it alone.