Build a landing page when the problem is one campaign or one service and the rest of the site works. Rebuild when the structure itself is the obstacle, when the site cannot be edited without help, or when the technical foundation is holding back every page at once. The deciding question is whether the fault is local or systemic.
Start with what is actually failing
A rebuild is often proposed as the answer to a problem that lives on one page. It is expensive, it takes months, and it puts every ranking you have at some risk. A landing page is cheap and fast and cannot fix anything structural.
So the first move is diagnosis rather than preference. Look at where traffic arrives, where it leaves, and what people do in between. If one service page converts at a fraction of the others, that is a page problem. If every page converts poorly and nobody can find anything, that is a structure problem.
A new coat of paint on a house with no hallway does not make the rooms easier to reach.
Cases where one page is the right answer
- You are running paid traffic to a single offer and need a page with one action and no distractions.
- One service is underperforming while the rest of the site does fine.
- You are testing demand for something new and do not want to commit to site wide changes.
- You need something live in a week for a seasonal push.
- The site is technically sound and the content on one page is simply weak.
In each of these the rest of the site is doing its job. Adding a page borrows the domain's existing authority, which is a real advantage over a separate microsite on a new domain that starts from nothing.
A landing page that duplicates an existing service page competes with it. If you already rank for the term, improve the page that ranks rather than publishing a rival.
Cases where a rebuild is the honest answer
- The navigation does not reflect what you sell, so no amount of page work makes anything findable.
- You cannot publish or edit without paying someone, which means the site never improves.
- The theme or builder is abandoned, insecure, or so heavy that speed cannot be fixed within it.
- The site is not usable on a phone, which is where nearly all of your visitors are.
- Services have changed enough that the information architecture is describing a business you no longer run.
Notice that four of the five are about capability rather than appearance. Rebuilds justified purely on looking dated tend to disappoint, because the new site inherits the same content problems in a nicer typeface.
What each option actually costs you
| Landing page | Rebuild | |
|---|---|---|
| Time to live | Days to two weeks | Two to four months |
| Ranking risk | Very low | Real, and manageable with a migration plan |
| Fixes structure | No | Yes |
| Ongoing burden | One more page to maintain | Whole site, new system to learn |
The hidden cost of a rebuild is the migration. Every URL that changes needs a redirect, every page that ranks needs its content carried across rather than rewritten from scratch, and the weeks after launch need watching. Skipping that work is how businesses lose traffic they spent years earning.
The hidden cost of a landing page is that it can postpone a decision you will have to make anyway. Three landing pages bolted onto a site nobody can navigate is a rebuild with extra steps.
The option most people skip
There is a third answer that suits more businesses than either extreme: keep the platform, rebuild the structure. Reorganize the navigation, consolidate the thin pages, rewrite the service pages, fix the speed defects, and leave the domain and the URLs where they are.
It is less satisfying than a launch and it carries almost none of the risk. On sites that already rank for something, it is usually the option with the best return.
How to decide between a landing page and a rebuild
- Identify whether the failure is on one page or across the site.
- Check whether you can edit and publish without outside help.
- Test the site on a phone and record what is unusable.
- Compare the cost of the fix with the cost of the migration risk.
- If the structure is sound, fix the page. If the structure is the problem, plan a staged rebuild.
Questions people ask
Will a rebuild hurt my rankings?
It can, and it does not have to. Losses come from changed URLs without redirects, content shortened or dropped in the redesign, and slower pages. A migration plan that maps every URL and preserves the content that ranks avoids most of it.
Should a landing page live on my domain or a new one?
On your domain, in almost every case. A new domain starts with no authority and no history, and you end up promoting two sites instead of one.
How long should I wait before judging a new landing page?
For paid traffic, as long as it takes to gather enough visits to be meaningful. For organic, give it a few months, since a new page has to be found and assessed before it settles.
My site looks old but works. Is that a reason to rebuild?
On its own, rarely. Looking dated costs you some credibility, which is real but usually cheaper to fix with a restyle than a rebuild.
Can I rebuild in stages?
Yes, and it is often the calmer route. Rebuild the templates and the highest value pages first, leave the rest on the existing design, and finish over a few months.
What should I keep from the old site?
The content on the pages that rank, the URLs, and anything with links pointing at it. Those three are the assets. The design is not.
If you are not sure which of the two you are looking at, the review reads the symptom first and recommends the smaller fix when the smaller fix will do.
Founder of Big Brain Digital. More than 15 years across SEO, content operations, ecommerce, and AI search. Based in Boise. More about Chris.