RightTech

A blank white page after upload is usually not a code problem.

It’s a packaging problem.

I’ve seen this right at the end of a Claude Code build.

Everything looks done.

The site feels like something a freelancer could charge $4,997 for...

Or $18,997 on a good day...

Then you upload the wrong zip and get nothing on the domain.

Just a white screen.

Here’s the fix.

Open your project folder.

This is the folder Claude Code built the site in.

Inside it, you should see the real website files.

index.html

CSS

images

assets

Now the important bit...

Select the files inside that folder.

Not the folder itself.

That’s the mistake.

Then zip those files together.

When the zip gets opened, the website files need to be there straight away.

Right at the top level.

Not buried one folder deeper.

If the zip opens like this...

your-site-folder > index.html
..some hosts will return a blank page.

So check before you upload.

Open the zip.

If you have to click into a folder before you see index.html, do it again.

Tiny detail.

Big difference between:

site is live

and

why is the homepage blank?

Have you lost time to a small deployment mistake like this?

The biggest upgrade I get from AI website builds is rarely a better prompt.

It’s a better standard.

I’ve been building sites in Claude Code.

You describe the site in plain English.

It writes the code while you watch.

And I keep running into the same thing...

If I give it isolated edits, I get isolated results.

Make the headline bigger.

Change the button colour.

Tighten the spacing.

That works.

But it only moves one piece at a time.

When I describe the end result properly, the whole site starts improving together.

I’ll say something like:

I want this to feel like a freelance developer would charge $10,000 for it.

Calm.

Sharp.

Finished.

Nothing that looks templated.

That changes far more than a list of edits ever does.

It influences the typography.

The colour.

The hierarchy.

Even the little things that make a site feel fast and polished.

That’s been the real shift for me.

Not directing the tool one tweak at a time...

Giving it a clear bar to hit.

That’s when the work starts to feel joined up instead of patched together.

If you’re building sites this way, try describing the outcome before the edits.

How should it feel?

What should someone assume about the business in the first 5 seconds?

I get better results when I answer those first.

Have you found the same with AI tools?

The easiest way to make AI website copy feel more expensive?

Tell it to stop performing.

A lot of AI-written website copy tries far too hard.

Too many adjectives.

Too much “premium”, “elevated”, “crafted”, “exceptional”...

Then the whole site starts sounding like it wants approval.

That is usually the problem.

Not the layout.

Not the idea.

The words.

I’ve seen strong pages made to feel cheap by copy that keeps shouting.

One of the best fixes is simple...

Give the AI shorter lines to aim for.

Not louder copy.

Tighter copy.

A line like “Six dishes, one fire.” does more work than a paragraph full of fancy claims.

Why?

Because restraint reads like confidence.

It gives the design room to breathe.

It gives the page some rhythm.

And it sounds more like a real business... less like a brainstorm.

If I want better copy from AI, I usually give it one clear instruction:

Keep the writing short, clean, and restrained.
Use fewer adjectives.
Prefer sharp lines over filler.

That small shift can change the whole feel of a site.

If your AI website sounds like it is trying too hard, I’d start there.

What is the worst AI-sounding line you have seen on a website lately?

“Responsive” sounds good...

Until you open the site on your phone.

Then the menu fights you.

The spacing is weird.

The buttons are tiny.

And the whole thing technically works... but feels off.

When I build in Claude Code, I never treat “it shrinks to fit” as done.

Mobile needs its own pass.

Every time.

A few things I always check:

1. Navigation
If the full desktop menu is still hanging around on mobile, it’s usually too much.

I switch it to something clean, easy to tap, and easy to close.

2. Spacing
Spacing that looks calm on desktop can feel endless on a phone.

I tighten padding.

I reduce the gaps.

I make the page feel easier to move through.

3. Buttons
Buttons need to work with actual thumbs.

Not careful little fingertip precision.

If someone has to aim, it needs fixing.

4. Clutter
Some elements earn their place on desktop.

On mobile, they just get in the way.

That’s usually where I start cutting.

Because “works on mobile” is a pretty low bar.

Feels good on mobile is the real test.

What’s the first thing you check on mobile?