Case Study 1: When Google Delisted BMW — Doorway Pages Are Not for Small Sites Only (2006)
A Tier-1 case built from the documented public record. No figures are invented; where the record is a characterization rather than a precise number, it is described as such.
Background
By 2006, BMW was one of the most valuable brands in the world, and bmw.de — its German website — was a
large, professionally run property. It was exactly the kind of site nobody imagines getting caught for
search spam. Big brands, the folklore goes, are too important, too visible, and too well-lawyered to be
touched by Google's spam enforcement. This case is where that folklore died in public.
At the time, Google's webspam efforts were led very visibly by Matt Cutts, who ran the Search Quality / webspam team and blogged openly about enforcement. That openness is why this case is so well documented: when Google acted, Cutts explained it publicly, and the episode became one of the most cited examples of doorway enforcement in SEO history.
The search/SEO issue
bmw.de had deployed doorway pages — the exact violation this chapter defines. The technique worked like
this: BMW published pages heavily loaded with high-value search terms (German keywords such as
"gebrauchtwagen," meaning used cars) that were built to rank in Google. A human who clicked such a page,
however, did not see that keyword-stuffed content; a piece of JavaScript immediately redirected them to a
different, more polished page meant for people. In other words, one page was shown to Googlebot and a
different experience was delivered to the human — a doorway page combined with a redirect, which crosses from
"low-value page" into cloaking-adjacent deception: showing the search engine something other than what
the user gets.
Set this against the chapter's quality bar. The doorway page existed only to catch search traffic for terms BMW wanted to rank for; it offered the searcher no destination of its own and funneled them elsewhere. It is the enterprise, hand-built cousin of the mad-libs service×city page from §33.2 — same logic, same violation, fancier execution.
What it shows
Three things, each central to this chapter:
- Scale and prestige buy no exemption. BMW's authority, brand, and legal weight did not shield
bmw.de. Google's spam policies apply to the multinational and the local plumber alike, and enforcement reached one of the largest brands on earth. - Doorway + redirect is a deception problem, not just a quality problem. The reason this drew hard enforcement (removal from the index) rather than a quiet ranking demotion is that it deceived the crawler — Googlebot was shown content that users never saw. That is a different, more serious category than an honest page that is merely thin.
- The remedy is removal, then reinstatement. This was not an unfixable catastrophe. Because it was a discrete, identifiable violation, the path back was clear: remove the offending pages and ask Google to reconsider.
Outcome
In early February 2006, Google removed bmw.de from its search index — the site's Google visibility for
its own terms effectively went to zero, with its PageRank reported as reset to 0. Google's German competitor
example, ricoh.de, was reported to have been penalized in the same enforcement wave for comparable
doorway behavior, underscoring that this was a policy sweep, not a one-off vendetta.
BMW responded quickly. It removed the doorway pages, and — because the violation was clear and the fix was genuine — the site was reincluded within a matter of days. The punishment was severe but short precisely because the remedy was real: stop doing the prohibited thing, and the basis for the penalty disappears. (This is the manual-action-and-reconsideration pattern that Chapter 26 treats in depth.)
The lesson
The BMW episode is the cleanest public proof of this chapter's central warning: the doorway page is a named, enforced violation, and no amount of scale, brand, or sophistication makes it safe. A team capable of building an elaborate JavaScript-redirect doorway system is a team capable of building genuinely useful pages instead — and the useful version would have carried no risk at all. The technique that felt like a clever shortcut to rankings was, in fact, a shortcut to being delisted from the world's largest search engine overnight.
For anyone about to generate pages at scale, the takeaway is not "be careful with JavaScript." It is that the intent behind the pages is what Google's policies target: pages built to catch search traffic while deceiving or short-changing the searcher are spam whether they are ten hand-crafted doorways or ten thousand templated ones. Build pages that give the searcher what the search result promised, and this entire failure mode is closed to you.
Discussion questions
- BMW's doorway pages combined a doorway (a page built only to rank) with a redirect (users sent elsewhere). Which of those two elements do you think escalated this from a ranking demotion to a full delisting, and why?
- The site was reincluded within days. What does the speed of recovery tell you about the difference between a violation you can stop doing and a quality problem you have to rebuild your way out of?
- Rivertown's owners are tempted by 75 spun service×city pages. Using the BMW case, explain to them — in plain business terms — why "we're a small local company, Google won't notice us" is the wrong reassurance.
- Compare BMW's hand-built doorway system to a modern template that spins 75 city pages. Are they the same violation? What, if anything, is different about the risk and the detectability?
- If you had been BMW's SEO lead in 2005 and were asked to "rank for used-car terms," what legitimate, quality-bar-passing approach would you have proposed instead of the doorway pages?