A small business pays for a new website. It looks sharp. It loads fast on their phone. Six months later, searching the company name still surfaces their Facebook page above their own domain — and searching what they actually do surfaces nobody but competitors.
The usual diagnosis is "we need SEO." Often the real problem is more fundamental: the website has no content in it. Not visually — technically.
What's actually happening
Most modern website builders produce a single-page application. The server sends the browser a nearly empty HTML file plus a large JavaScript bundle. The browser runs that JavaScript, which then constructs the entire page — text, headings, navigation, all of it — on the visitor's device.
Humans never notice. The whole process takes a fraction of a second.
But a search crawler making a plain request receives what the server sent: an empty shell. Google can execute JavaScript, but it does so on a deferred queue, inconsistently, and with a budget that small sites rarely earn much of. Bing is worse. And the systems that generate link previews — LinkedIn, Facebook, iMessage, Slack — generally don't execute JavaScript at all.
If your homepage's raw HTML contains no sentences, you are asking every search engine to take your existence on faith.
The thirty-second test
You don't need a tool. Open your site in Chrome or Firefox, right-click, and choose View Page Source — not "Inspect," which shows the page after JavaScript has run.
Now use Ctrl+F (Cmd+F on a Mac) to search that source for a distinctive sentence from your homepage. Your tagline, a service description, anything.
- You find it — your content is server-rendered. Any ranking issue is a content or authority problem, not an architecture one.
- You don't find it — your page is client-rendered, and crawlers are seeing an empty document.
While you're in there, check two more things. Is there a <meta name="description"> tag with a real sentence in it? And does the og:image tag point at your own branding, or at your site builder's default graphic?
That last one catches an embarrassing number of businesses. Every time someone shares the link, the preview card advertises the tool the site was built with.
Why this happens to good websites
It isn't incompetence. It's a default. The tools that make it easiest to produce a beautiful site quickly — including most AI-assisted builders — default to client-side rendering because that's what's simplest to preview and deploy. Nothing in the build process warns you that you've traded away search visibility.
The trade is invisible precisely because the person checking the work is a human with a browser. Everything looks correct.
Fixing it
There are three realistic paths, in ascending order of effort.
1. Pre-render at build time
The site is generated into real HTML files once, when you deploy. Every page ships complete. This is the right answer for the overwhelming majority of small-business sites, because a services page doesn't change between visitors — there's nothing to compute per-request. Static site generators and framework static export modes both do this.
2. Server-side rendering
The server builds the HTML fresh for each request. Necessary if pages genuinely differ per visitor — a customer portal, a live inventory feed. Overkill for a brochure site, and it costs more to run.
3. Prerendering middleware
A service intercepts crawler requests and serves them a rendered snapshot. It works, and it's the fastest retrofit for a site you don't want to rebuild. It's also a permanent dependency and a recurring bill.
The rest of the checklist
Once your HTML actually contains your content, the remaining fundamentals are quick:
- Unique title and meta description per page. Not the same string repeated site-wide.
- One
<h1>per page, describing that page specifically. - A real Open Graph image at 1200×630, with your branding on it.
- LocalBusiness structured data — your name, address, phone and hours in machine-readable JSON-LD. This is what feeds map results and AI-generated answers.
- A sitemap.xml and robots.txt, submitted through Google Search Console.
- Consistent name, address and phone across your site, Google Business Profile, and every directory listing. Inconsistency here quietly suppresses local ranking.
What to do this week
Run the page-source test on your own site. If your content isn't there, that's your bottleneck — and no amount of blog posting, backlink buying or keyword tuning will route around it.
Fixing the rendering architecture is usually a one-off project measured in days, not a retainer. Everything else in SEO compounds on top of it, and none of it compounds until it's done.
Written by the team at DelaxCom LLC, an independent IT and telecom consultancy in Johnston, Iowa. Questions about your own setup? Call 515-298-7392 or email contact@delaxcom.com.