Do I need a new website to rank better?

Google's technical bar is three items, and you probably already clear them

Here is the whole list, in Google's words. To be eligible for indexing: Googlebot is not blocked, the page works and returns an HTTP 200 success status code, and the page has indexable content.

That is it. Three things. An ordinary site built on any mainstream platform in the last decade clears all three without anybody doing anything clever.

Which means the claim that your website cannot rank has a specific, checkable meaning. It says one of those three is failing. So ask which one, and ask to be shown. If the answer is vague, or if it is really about how the site looks, then the technical requirements are not the problem being described.

Worth knowing what each failure actually looks like, because they are specific. Googlebot blocked usually means a robots file or a login wall. Not returning a 200 means the page errors or redirects when it should not. No indexable content usually means the words exist only inside something Google cannot read.

Eligible is not the same as indexed, and neither is the same as ranking

Google is careful here and so should anybody quoting it be.

Its own caveat, immediately after the list: "Just because a page meets these requirements doesn't mean that a page will be indexed; indexing isn't guaranteed."

So there are three separate states and people collapse them constantly. Eligible means the door is not locked. Indexed means Google has the page. Ranking means Google chose it for a particular search over everything else available.

A rebuild can fix eligibility, in the rare case eligibility is broken. It does almost nothing for the third, because the third is a competition against other pages, judged on whether yours is the better answer.

That distinction is where most rebuild-for-rankings arguments quietly fall apart. The proposal fixes a problem at the first level to solve one at the third.

What a redesign actually changes, and what it does not

A redesign changes appearance, navigation, and often structure. Those are real improvements and they matter to the people who arrive. They are not the same as the thing being ranked.

Google's guidance on content asks you to evaluate pages by Who, How, and Why: who created the content, how it was made, and why it exists. It distinguishes people-first content from search engine-first content, and suggests reading the guidelines to self-assess honestly.

Read that list and notice something. Not one item is about the template. A page with a byline, real expertise, and an answer to the question it promises will do the same job in a plain design as in an expensive one.

Speed deserves its own answer, because it is the argument most often attached to a rebuild. A slow site is a genuine problem, for visitors before search engines. But slowness usually traces to a handful of specific things: oversized images, too many third-party scripts, a bloated theme, or no caching. Every one of those can be fixed on the site you already have, generally for a fraction of a rebuild. Replacing the whole site to fix four heavy images is a large solution to a small problem, and a new site built the same careless way will be slow within a year.

The honest test is to ask what specifically is slow and why. If nobody can name the cause, nobody has measured it, and a rebuild is being proposed against a symptom.

There is also a cost to rebuilding that rarely appears in the proposal. Every page changes address, so every page needs a redirect, and Mozilla's documentation notes that every redirect is an extra request, so they should be kept to a minimum. A rebuild converts a stable site into a migration, and migrations are where rankings actually get lost.

When a rebuild genuinely is the answer

There are real cases, and they are worth naming so this does not read as blanket resistance.

A rebuild is justified when the content genuinely is not indexable, which usually means the text loads only through scripts Google is not reading. It is justified when the site cannot be added to, so new pages are impossible or require a developer every time, because publishing is the one activity that compounds. It is justified when the site is unusable on a phone, since that is where most of the traffic is and no ranking fixes a visitor who leaves.

It is also justified when nobody can edit anything, when the platform is abandoned or insecure, or when the business has changed enough that the structure no longer matches what is sold.

Notice what those have in common. Each is a capability problem, not an appearance problem. The rebuild buys the ability to do the work, which is different from the rebuild being the work.

How to decide

A short sequence, and the first four cost nothing.

• Ask which of the three technical requirements is failing, and ask to be shown the evidence. Vagueness here is the answer.
• Check whether your pages are indexed at all, using Search Console rather than an opinion.
• Ask what content exists for the searches you want. If the answer is that no page addresses them, a new design will not create one.
• Compare the cost of the rebuild against the cost of writing the missing pages on the site you already have.
• If the site cannot be added to without a developer, treat that as the actual problem and price fixing it separately.
• If you do rebuild, insist the redirect map exists before launch, not after, because that is where sites lose what they had.

Here is the arithmetic that usually settles it. A rebuild quoted at 12,000 dollars against 30 pages of content at, say, 400 dollars each is a straight choice between a new frame and 30 new answers. If the existing site is technically fine, the 30 answers win, because they are the things that can rank. Treat those figures as an illustration rather than a quote, but do the comparison with your own.

None of this means a dated site is fine. It means the case for replacing it should be made on what you cannot currently do, rather than on a ranking promise the technical requirements do not support.

Building websites is one of the things we do, which is exactly why it is worth saying that the answer to this question is often no. A rebuild is worth buying when it buys you a capability you do not have, and not when it is sold as a ranking promise.

Terms used on this page

• 301 redirect
• Core Web Vitals

Sources

• Google Search technical requirements
• Creating helpful, reliable, people-first content
• Redirections in HTTP (MDN Web Docs)

Last reviewed 2026-09-11.