Domain Parking vs 404 vs Empty Site: What Each One Tells a Crawler

A parking page returns HTTP 200 with templated content, so crawlers keep revisiting a page that teaches them nothing. A 404 returns "not found," so they stop. An intentional placeholder returns 200 with real, unique content, so they have something to index. All three look empty to a human; only one builds a record.

You bought the domain. You haven't built the thing yet. So your registrar helpfully parked it for you.

Problem solved, right? The domain exists. It's waiting. You're busy. You'll get to it later.

But here's the part most founders never get told: "nothing" isn't a single state.

To a human, a parked page, a 404 error, and an empty placeholder can look similar. They all translate to "no website here yet." To discovery systems, they are different objects, and they trigger different follow-on behavior.

One tells crawlers to leave. One tells them to keep checking and learn very little. One can establish that a real actor exists here.

Treating them as the same thing costs crawler attention now, and time later.

The internet doesn't see intent. It sees responses.

There are three states. Because "nothing" has more than one technical flavour, those three states map to five possible responses. Here is the whole decision on one screen.

The rest of this post is how each row earns its place and how to work out which row you are currently sitting in.

What are the three states an unbuilt domain can be in?

Let's define the difference, because the technical distinction determines the consequence.

Visually, all three can look like "not launched." Mechanically, they are worlds apart.

1. The registrar parking page (200 OK plus a template)

This is the default setting for many registrars. The server returns an HTTP 200 (OK) response, which means "success." The content is usually a generic template: ads, a "buy this domain" banner, or a thin page that could belong to anyone.

That last part is the problem. Thin content, a page with little or no unique substance, is the category this falls into, and the template is identical across thousands of other domains held by the same registrar. Nothing on the page identifies your domain as distinct from any other name in the same parking pool.

Parking pages are not a pause state, they're a public state. More on what that state costs you in search terms: does domain parking hurt SEO.

2. The true 404 and its stricter sibling, 410 Gone

The server returns an HTTP 404 (Not Found) response. This is the server explicitly saying: this resource does not exist.

There is a second code for the same situation with more conviction. 410 (Gone) means the resource is not just missing but deliberately and permanently removed. The HTTP specification draws the line clearly: 404 means the origin server "did not find a current representation," while 410 means the resource is gone "and this condition is likely to be permanent" (RFC 9110: HTTP Semantics).

In practice the difference is small but real. Both stop the crawl. A 410 signals that stopping is intentional, so systems tend to settle on it faster. Use 404 if you might build on the name later. Use 410 if you have genuinely retired it.

3. The intentional placeholder (200 OK plus meaning)

The server returns an HTTP 200 (OK) response, but the page is minimal and real. A name, a sentence about what this will be, a contact path, maybe a short paragraph that proves it isn't an ad template wearing your domain like a mask.

This is the only one of the three states that creates a record rather than an absence. What separates it from parking is not effort or design budget, it is uniqueness. A real placeholder says something no other page on the internet says. A parking page says the same thing as ten thousand others.

There is a specification for what "real" means here, and it is shorter than you'd expect. It's further down this page.

What about just redirecting it to my main site?

This is the fourth option every founder considers and most posts skip, so let's deal with it.

A 301 redirect does not make your unused domain a better version of itself. It makes it stop being itself. The URL ceases to exist as a separate entity in the index, and any attention it might have accumulated points somewhere else.

That is exactly right for a defensive registration: the plural of your brand, the common misspelling, the .net you bought so nobody else could. It is exactly wrong for a name you bought because you had an idea for it. Redirecting a name you intend to build is the digital equivalent of putting the keys to a second property in a drawer and telling people your first address twice.

If you're redirecting for SEO reasons rather than defensive ones, that deserves a fuller answer than this post has room for, and the honest version involves more caveats than a paragraph allows.

What each state teaches the internet

404 (Not Found): nothing here. Stop checking this URL.

410 (Gone): nothing here, and that is permanent. Stop checking and stop wondering.

301 (Moved): this is now that. Go there instead.

Parking page (200 + template): this exists, but it's interchangeable.

Intentional placeholder (200 + meaning): this exists, and a real actor is behind it.

How does Google treat a parking page differently from a 404?

This isn't about penalties. It's about physics.

Crawlers have limited time and capacity. Google splits that constraint in two: a crawl capacity limit (how hard it can hit your server without degrading it) and crawl demand (how much it actually wants your pages). Demand is the one that matters here, and Google says it is allocated by "popularity, overall user value, content uniqueness, and serving capacity" (Google Search Central, Large site owner's guide to managing crawl budget).

Read that list again with a parking page in mind. Popularity: none. User value: none. Uniqueness: it is the same template as every other name in the pool. Three of the four factors score zero by design.

Does crawl budget even matter if I only own one domain?

This is the correct objection, and most articles on this topic never raise it, which should tell you something.

Google scopes its crawl budget guide to large sites: over a million unique pages changing weekly, or more than ten thousand pages changing daily (Google Search Central, Large site owner's guide to managing crawl budget). If you own one dormant domain, you do not have a crawl budget problem. You have a crawl demand problem, which is worse, because a budget is a ceiling and demand is an invitation.

Google's crawling documentation answers the size question directly: "If a site has important content that changes often, we crawl it often, regardless of the size" (Google Search Central, Myths and facts about crawling).

Read it the other way round. A one-page template that never changes gives Google nothing to come back for. Size was never the variable. The reason to return is the variable, and a parking page is engineered, accidentally, but thoroughly, to remove every one.

Why parking pages end up classified as soft 404s

First, the definition, because the term gets thrown around loosely.

A soft 404 is a page that returns HTTP 200 while showing the user nothing of substance, Google's term for a response that says "success" and delivers an empty room. Google reports these under Soft 404 in Search Console's Page indexing report.

Google does not publish a rule that says "parking pages are soft 404s." It doesn't need to. The classification follows from the definition: a page returning success while delivering nothing of substance is the thing soft 404 describes. Most registrar parking templates meet that description without trying.

And Google is explicit about what that costs: soft 404 pages "will continue to be crawled, and waste your budget" (Google Search Central, Large site owner's guide to managing crawl budget).

That is the mechanical trap of the common parking setup. It returns 200 OK, which invites processing, but it doesn't provide unique value. The result is a loop: repeated crawling, repeated low signal.

Google also warns that spending crawl time on URLs that shouldn't be crawled means "Google's crawlers might not explore the rest of your site" (Google Search Central, Large site owner's guide to managing crawl budget). In plain terms: you don't just fail to earn attention, you can slow down the moment you finally publish something worth noticing.

Why a true 404 is the clean exit

This is where most people's intuition breaks. They assume a 404 is "bad."

In crawl terms, Google's crawling documentation says the opposite: "Pages that serve 4xx HTTP status codes (except 429) don't waste crawl budget" (Google Search Central, Myths and facts about crawling).

The 429 exception is worth understanding, because it is the one 4xx code that does hurt. A 429 is a rate-limiting signal, and Google treats it as a sign your server is struggling: latency or rate-limiting responses cause the crawl capacity limit to go down (Google Search Central, Large site owner's guide to managing crawl budget). Everything else in the 4xx family is just a closed door, and closed doors are cheap.

A 404 is honest. It tells crawlers to stop spending attention on that URL. That doesn't create visibility by itself, but it avoids teaching systems to revisit a low-value page forever.

The ranking, then, isn't parking versus 404. It's this: a placeholder builds something, a 404 builds nothing, and a parking page actively builds the wrong thing. Only one of those three is worse than doing nothing at all.

Low-value inventory has spillover

Google's guidance on low-value-add URLs lists soft 404 pages alongside low quality and spam content as things that affect crawling and indexing (Google Search Central, Large site owner's guide to managing crawl budget).

Even if you only have one domain, that sentence is the right mental model. The internet remembers what it repeatedly observes. If what it repeatedly observes is templated and interchangeable, that becomes the default story.

And search crawlers are the forgiving audience here. They at least keep visiting. The systems that generate AI answers are stricter about what counts as readable content at all, AI answer engines can't read a parked domain in any useful sense, which is a different mechanism from crawling and a worse outcome.

What HTTP status code should an unused domain return?

Work backwards from what you intend to do with the name. The code is a consequence of the decision, not the decision itself.

Notice what is not on that list: a registrar parking page. There is no goal for which a parking template is the optimal technical answer, unless the goal is the registrar's ad revenue rather than yours.

How do I check which state my domain is in right now?

Most people have never actually looked. Four steps, about ten minutes.

1. Read the raw status code. From a terminal, run curl -I https://yourdomain.com. The first line is your answer: HTTP/2 200, HTTP/2 404, HTTP/2 410 or HTTP/2 301. If you'd rather not touch a terminal, any HTTP header checker does the same job. A 200 here does not mean you're fine, a parking page returns 200 too. It means you now need step 2.
2. Look at what's actually being served. Open the domain in a private browser window. Ask one question: does this page say anything that no other page on the internet says? If the answer is no, if it's ads, a sale banner, or "this domain is registered," you are serving a 200 with nothing behind it. That is the soft 404 shape.
3. Check whether Google has it indexed. Search site:yourdomain.com in Google. No results means no page from your domain is in the index. Some result means something is, and it's worth seeing what.
4. Open Google Search Console and read the verdict. Use the URL Inspection tool on your homepage, then check the Page indexing report. The status you get back tells you exactly where you stand:

• Soft 404: Google sees a success response with nothing behind it. This is the parking page diagnosis, in Google's own words.
• Crawled, currently not indexed: Google came, read it, and decided it wasn't worth storing. Thin content, most often.
• Discovered, currently not indexed: Google knows the URL exists and hasn't prioritised crawling it. Crawl demand, or the lack of it.
• Not found (404): the clean exit, working as intended.
• Submitted and indexed: you have a real page. Whatever you're doing, keep doing it.

If you don't have Search Console set up for the domain, that itself is part of the diagnosis. A domain nobody is measuring is a domain nobody is managing.

One caveat worth setting: steps 3 and 4 tell you what Google currently believes, not what it believed last month. If you un-parked recently, the verdict may still be catching up, which is the next section.

How long does it take Google to re-index a domain after you un-park it?

A builder question that comes up a lot is basically: can I just switch later?

Yes. You can.

The difference is what you're asking systems to update.

Google doesn't publish a number for this, and I'm not going to invent one. What it does publish is a range for getting a URL looked at again at all: "Crawling can take anywhere from a few days to a few weeks" (Google Search Central, Ask Google to recrawl your URLs). That's the floor, and it's the floor for a page Google already has a reason to care about.

Now layer in what we already know:

• Soft 404 pages keep getting crawled and teach nothing each time. Crawl time spent on URLs that shouldn't be crawled comes out of the time available for the rest of your site. Crawl demand is allocated on popularity, user value and uniqueness, none of which a template accumulates.

So the recovery story becomes clearer:

• From a true 404 to a real site: you're flipping from "doesn't exist" to "exists." It's a clean change in state, with no prior belief to overwrite.
• From a parked template to a real site: you're asking systems to rewrite an older story about the domain. Not "missing," but "present and low signal." The prior belief has to be replaced, and it was reinforced every time the crawler visited.

The honest claim is simpler than a timeline: if you spend months broadcasting low-value signals, you often create more distance between launch day and discovery day than you needed to.

If you're already in the second situation, the recovery is a process rather than a switch: how to recover a domain Google still thinks is parked walks the whole sequence.

And there's a compounding effect underneath all of this that has nothing to do with parking specifically, why new domains take months to rank even after you launch. Starting that clock late is the actual cost of waiting.

Renewal emails aren't reminders, they're pressure tests. This is where "later" becomes measurable. We pulled this thread harder in: why "I'll build it later" gets expensive.

Why do registrars park domains by default?

If a parking page is mechanically inferior to a clean 404 or a minimal placeholder, why is it the default?

Incentives.

Parking pages are often monetized. Ads, affiliate links, domain-for-sale funnels. GoDaddy's own CashParking product is a clear example of the mechanism: it "places relevant advertisements on parked domains" and pays the domain owner up to 80% of the resulting click-through revenue (GoDaddy, CashParking). The default creates revenue and reduces support load, and it feels like a "service."

It's not malice. It's a business model.

But the model is not designed to protect your domain's signal quality. The registrar's parking page is optimised for the registrar's revenue per impression. Your domain's search record is not a variable in that equation, in either direction.

If you want to see the difference laid out concretely, we've compared GoDaddy's parking page against a warmed placeholder side by side. And the renewal fee is only the visible part: what parking actually costs beyond the renewal fee adds up the rest.

We've lived the loop: buy the domain in clarity, then renew it while the idea stays dark. Warming is choosing to make an idea legible before you feel ready. Quietly. On purpose. It's a way to turn ownership into presence before you have the full build, so the internet isn't forced to learn "nothing" by default. What SiteWarming actually is.

What should you actually put on a domain you haven't built yet?

"A small amount of meaning" is easy to say and vague enough to be useless, so here is the specification.

A placeholder earns its 200 when it carries all six of these:

1. A unique title tag and meta description that names the domain and says what it will be. Not "Welcome to yourdomain.com." If another domain could use your title tag unchanged, it isn't unique.
2. At least one paragraph of original text. What this is, who is behind it, what stage it's at. Three sentences is enough. Zero is not.
3. A named entity. A person or a company, with a way to reach them. This is the difference between "a domain exists" and "someone is behind this domain."
4. Structured data. At minimum an Organization or WebSite JSON-LD block naming the entity. This is what makes the page machine-legible rather than merely machine-visible.
5. Its own HTML on its own domain, over HTTPS with a valid certificate. Not a frame, not a redirect, not a subdomain of a builder's platform.
6. Something that changes. A date, a status line, a short update log. Recall Google's position: content that changes often gets crawled often, regardless of site size. A page that never changes gives nothing a reason to return.

That sixth point is the one people skip, and it's the one that does the compounding work.

None of this requires building the actual product. It requires deciding that the domain is allowed to exist publicly before the idea is finished. If you'd rather not assemble the six by hand, our Launch & Warm flow deploys DNS, SSL and structured data for you, you write a short story about the domain, it handles the rest.

Which option should you choose for your domain?

Technical literacy is leverage. Now you can choose deliberately instead of accepting the default.

• If you are truly doing nothing: a hard 404 is cleaner than a parking page. Google is explicit that 4xx pages don't waste crawl budget. If you've retired the name permanently, use 410 instead.
• If you want to signal intent: publish a minimal, authentic placeholder. Not a template. Not ads. The six-point specification above is the whole job.
• If the domain is genuinely for sale: a placeholder beats a parking page here too, because a broker and a buyer both need to find it and verify who owns it. That's what sale readiness is actually measuring.
• If you're keeping it defensively: 301 it to your main site and stop thinking about it.
• If you're already parked: treat it as an active state, not neutral storage. Soft 404s keep getting crawled and waste crawler attention.

The framing that helps most is the one this whole post has been circling: you are not choosing between doing something and doing nothing. You are choosing which thing the internet learns while you decide. You don't have to choose between building and parking, that binary was never real.

What if I have thirty of these?

Then the per-domain decision above stops scaling and becomes a portfolio decision, which is a different problem with a different answer. The short version: you don't need thirty placeholders, you need to know which of the thirty are worth keeping at all.

Start with the renewals, working out which of your renewals are worth keeping is the filter that makes the rest tractable.Then the stewardship question:managing a portfolio without building every site.

One pass through that filter usually removes a third of the list, which makes the remaining decisions cheap.

The close

A browser can render a parked page, but meaning-extraction systems can't do much with it.

Parking isn't evil. It's just misunderstood. It is a monetisation product that founders mistake for storage, and the mistake is understandable because the registrar never corrects it.

If you aren't ready to build, that's fine. Choose a version of "not ready" that doesn't make you pay twice when you finally are.

If you want the version of that choice that takes ten minutes instead of a weekend, here's what a warmed domain costs.

Frequently asked questions

Is a 404 better than a parking page? For crawl efficiency, yes. Google states that pages serving 4xx status codes (except 429) don't waste crawl budget, while soft 404 pages "will continue to be crawled, and waste your budget." A 404 stops the loop. But neither builds anything, an intentional placeholder is better than both if you plan to build, sell, or be found.

Does a parked domain get indexed? Sometimes, rarely, and usually not usefully. A parking page returns 200 OK, so it's eligible for indexing, but templated content with no unique value typically ends up as Soft 404 or Crawled, currently not indexed in Search Console. Being crawled is not the same as being indexed, and being indexed is not the same as being findable.

Do 404 pages waste crawl budget? No. Google's crawling documentation lists this explicitly as a myth: "Pages that serve 4xx HTTP status codes (except 429) don't waste crawl budget." The 429 exception matters, that's a rate-limiting response, and it signals server strain, which does reduce how much Google crawls you.

What is a soft 404? A soft 404 is a page that returns HTTP 200 while showing the user nothing of substance, a response that says "success" and delivers an empty room. Google flags these under Soft 404 in Search Console's Page indexing report. Most registrar parking templates fit the description without intending to.

Should I use 404 or 410 for a domain I've retired? Use 410 if the decision is permanent. RFC 9110 defines 404 as "did not find a current representation" and 410 as gone, where "this condition is likely to be permanent." Both stop the crawl; 410 states that stopping is deliberate, so systems tend to settle on it faster. Use 404 if you might come back.

Why not just noindex the parking page instead? Because noindex doesn't solve the crawl problem. A page has to be crawled for Google to see the noindex directive, so the page keeps getting fetched, you've removed it from the index without removing the cost. A 404 stops the request entirely. And if the goal is to eventually be found, noindex is the opposite of what you want.

Should I redirect an unused domain to my main site? Only if you're holding it defensively. A 301 means the domain stops existing as its own entity, correct for a misspelling or a .net variant you bought protectively, wrong for a name you registered because you had an idea for it. Redirecting a name you intend to build throws away the thing you were trying to keep.

How long before Google stops treating my domain as parked? Google doesn't publish a figure for reclassification. What it does publish is that "crawling can take anywhere from a few days to a few weeks" for a recrawl request. Reclassification takes longer than a recrawl, because Google isn't learning something new, it's replacing something it already believed.

Does crawl budget matter if I only own one domain? Not in the form Google documents, that guide is scoped to sites with over a million pages. But the underlying mechanism still applies to you, and it's called crawl demand. Google's position on size is direct: "If a site has important content that changes often, we crawl it often, regardless of the size." A static template gives it nothing to come back for.

Does domain parking hurt SEO? Short answer: it doesn't trigger a penalty, but it actively teaches search engines that your domain is interchangeable, which is worse than teaching them nothing. We covered the full consequence case separately in does domain parking hurt SEO. This post is about choosing between the alternatives.