HouseFresh case study - how a two-person review site lost 95% of its Google traffic and came back

HouseFresh case study – how a two-person review site lost 95% of its Google traffic and came back

HouseFresh is a small website that reviews air purifiers. Two people run it, and they do something most review sites only claim to do: they buy the products and test them. In 2023 Google took away almost all of their traffic. Two years later it came back.

Their story is worth knowing for anyone who wants to build a review or affiliate site, because it shows both how fragile search traffic is and what a small site can do about it.

What HouseFresh is

HouseFresh focuses on air quality products, mostly air purifiers. The team buys the devices, runs them in real rooms and measures how well they clean the air. The site earns money through affiliate commissions when readers buy a product through its links.

Under the hood it is a plain WordPress site on the GeneratePress theme, which keeps long review pages fast. There is nothing exotic in the stack. The value is entirely in the testing.

The crash

Before September 2023, HouseFresh got about 4,000 visitors a day from Google. Then came Google’s Helpful Content Update, and traffic fell to about 200 a day. That is a loss of roughly 95 percent, almost overnight.

What made it painful was who replaced them. Managing editor Gisele Navarro documented how big media brands, publishing quick “best air purifier” lists without real testing, now ranked above sites that had done the work. She described it as going from ranking first, because they were one of the few who had actually reviewed a product, to not showing up at all.

Because the business lived on affiliate commissions, less traffic meant directly less money. The team shrank, and at one point Navarro was advised to shut the site down and start over on a new domain.

The recovery

They did not start over. On October 11, 2025, Navarro shared that HouseFresh had recovered its visibility in Google. Asked what did it, her answer was honest: “Hard work and a lot of luck.”

There was no single fix. What she described:

  • Steady work on the site. Most changes were design, usability and content improvements, made by two people who describe themselves as not technical.
  • Growth outside Google. Their YouTube channel took off, and a collaboration with Linus Tech Tips brought a much larger audience and more people searching for HouseFresh by name.
  • Google changing course. Later updates and Google’s crackdown on “site reputation abuse”, where big sites rent out sections to rank for unrelated topics, made the field fairer for independent reviewers again.

What you can learn from it

First-hand testing is the moat. It did not protect HouseFresh from the first crash, but it is the reason the site was worth saving and the reason it came back. A review that anyone could write from Amazon listings has nothing to recover.

Do not build on one traffic source. Google sent almost all of their visitors, so one update could take almost everything. The YouTube channel ended up doing more for their recovery than any change to the website.

Brand searches are protection. When people search for your name, no update or AI summary can easily take that click away. HouseFresh got more of those once its videos spread.

Small sites can survive if they keep going. The advice to abandon the domain was reasonable at the time. Staying, and improving what was already good, paid off.

How to build something similar

If you want to copy the model, copy the parts that matter: a narrow product category you can afford to test, a simple fast site, clear test data on every review and a second channel like YouTube from day one. Do not copy the content. The whole point of HouseFresh is that its reviews are its own.

Thinking about a review site of your own? Our earnings calculator shows what affiliate income could look like at different traffic levels, and the free concept gives you a plan modeled on sites like this one.

Sources

Similar Posts

Leave a Reply

Your email address will not be published. Required fields are marked *