Recovering a Restoration Company After a Google Core Update Cut Its Traffic by 80%

Water Extraction Team (WET) is a family-owned, IICRC-certified restoration company. Established in 2007, they’ve been serving Greater Cleveland and Northeast Ohio for more than 19 years.

Their services mainly include: fire, water, and mold damage restoration, biohazard cleanup, and contents cleaning services. 

So, they were doing okay for important local search keywords like “water damage restoration near me” for many years. But unfortunately, when a Google core update rolled out last year, their organic traffic fell from a steady 100+ visitors a day to roughly 20 within a matter of weeks. 

We took over the account on April 1, 2026. Within two months, their daily organic traffic has climbed back to around 50 visitors a day and is still trending up 

What’s more, their Google Business Profile is producing 71% more calls and 73% more direction requests than it did before we started. 

Let’s see in detail what went wrong for the Water Extraction Team, what we changed, and where the site is headed now.

The Problem

By the time the site landed on our desk, the damage was obvious. 

Their rankings that had held for months were gone. Also, service pages that used to bring in calls had totally dropped out of Google’s index. 

The worst part was although the client knew traffic was down, they weren’t sure why that was happening and if they could recover soon enough.

Here’s the trajectory we were handed:

• Before the core update: 100+ organic visitors per day (pretty much stable).
• April 2026 (when we started): 20 organic visitors per day.
• The cause: a Google core update (major updates that reward helpful, trustworthy content and demote pages that look thin, templated, or machine-produced.)

For your information, a core update doesn’t penalize a site the way a manual action does. It re-evaluates the quality across the board. 

So, when a site loses this badly to one, there might be a number of problems that were tolerable while rankings held and became fatal once the algorithm changed. 

Guess what? That’s exactly what we found.

How We Diagnosed It

Before touching anything, we ran a full manual audit. 

Why manual? That’s because automated crawlers are useful to find broken links and missing tags. But they can’t tell if a page reads like it was written by someone who had fixed a flooded basement. 

Since WET’s site was hit by a quality-focused core update, we read the site page by page to find out if the content was up to par.

After the audit, we found eight problems that we later categorized into content and trust, site structure, and technical health.

What We Found

1. The Content Was AI-Generated and Read Like It

The biggest issue was that most of the content seemed machine-generated and was published with little or no human editing. 

There was no firsthand perspective and no specifics that only an expert restoration crew would know. In case you didn’t know, Google’s quality systems are getting pretty good at recognizing this pattern.

On top of that, the content didn’t reflect Google’s E-E-A-T signals (Experience, Expertise, Authoritativeness, Trustworthiness) that hugely matter in a “Your Money or Your Life” category like home damage and biohazard work. 

When someone is choosing who to let into their flooded home, Google now wants to make sure they show a highly professional and expert restoration company. WET’s old content didn’t live up to Google’s expectations.

2. There Were No Dedicated Service Pages

A restoration company usually offers a variety of services, including water extraction, structural drying, fire and smoke cleanup, mold remediation, biohazard and crime-scene cleanup, and contents cleaning. 

Each of these services has its own search intent. So, Google expects dedicated pages for every service. 

WET’s website was trying to cover too much ground on too few pages, which meant no single page was strong enough to rank for anything specific. It worked before, but not in 2026. 

3. Technical SEO Was Working Against the Site

We also noticed some important pages had been deindexed. They were live once, but Google had totally dropped them from search results. 

On the plumbing side, the XML sitemap, robots.txt, and canonical tags were inconsistent. As a result, they made Google confused about which pages mattered and which URL versions were the real ones. 

Also, a number of 404 pages were being redirected to unrelated pages (often the homepage), which is a poor experience for users and a confusing one for crawlers.

4. The Site Was Slow

This was a common issue – the page speed was poor. There were large, uncompressed images that were causing this. Aside from that, bloated and unoptimized code made it worse. 

Slow pages are known to cause many issues. They frustrate the prospects in a hurry and drag down the Core Web Vitals, which feed into rankings.

5. On-Page SEO Was Essentially Absent

WET’s title tags and meta descriptions weren’t optimized for Google’s new updates. Target keywords also weren’t worked into the body copy. Moreover, internal linking between related pages was absent in some cases, so authority wasn’t flowing through the site.

6. Local Keywords Were Missing

For a business that lives and dies on local calls, the site wasn’t speaking the local language. 

The specific city-and-service phrases people in Northeast Ohio usually type (such as “water damage restoration Willoughby” or “mold removal Mentor”) weren’t targeted anywhere.

7. Their GBP Wasn’t Optimized

Their Google Business Profile was underutilized, which is super important now to get more jobs. 

The different categories also weren’t set correctly. That created an obstacle toward how often the profile showed up in the local map pack for relevant searches.

8. Nothing Was Being Monitored

There was no established, ongoing system to identify problems as they appeared. So, new issues kept accumulating in the dark.

What We Did

Here’s how the work broke down in the first two months.

Rewrote the Content to Prove WET’s Professionalism

We rewrote both web and blog content from the ground up with human writers who understood the restoration industry well. Every page was written keeping the E-E-A-T signals in mind; i.e., clear credentials, specific process explanations, and expert industry language.

Built a Great Site Structure With Dedicated Service & Location Pages

We rebuilt the architecture so instead of being crammed onto a handful of catch-all pages, each service could have its own dedicated page grouped under a parent category. 

Because of that approach, their service tree now mirrors how people search in real-life scenarios. For example, someone looking for “sewage cleanup” or “mold inspection” now lands on a page built specifically for that need. 

To give you some idea, here are the pages we created:

Water Damage Restoration

• /water-damage/water-mitigation
• /water-damage/water-extraction
• /water-damage/sewage-cleanup
• /water-damage/structural-drying
• /water-damage/thermal-imaging-inspection
• /water-damage/leak-detection

Fire Damage Restoration

• /fire-damage-restoration (fire and smoke cleanup)

Mold Damage Restoration

• /mold-damage/mold-inspection
• /mold-damage/mold-remediation
• /mold-damage/mold-removal

Biohazard Cleanup

• /biohazard/drug-lab-cleanup
• /biohazard/crime-scene-cleaner
• /biohazard/hoarder-cleaning-services

Contents Cleaning

• /contents-cleaning-services

Each page was given its own optimized title, meta description, self-referencing canonical, and target keyword set. This was necessary so every service could rank on its own merits rather than competing with its siblings for the same generic page.

Alongside these, we created 11 dedicated location pages. Every page is built around its own city. For example, Willoughby’s page runs the optimized title “Trusted Water Damage Restoration in Willoughby, Ohio” with a meta description written for that local intent:

• /willoughby
• /south-euclid
• /solon
• /painesville
• /mentor-on-the-lake
• /mentor
• /euclid
• /cleveland-heights
• /chardon
• /beachwood
• /ashtabula

Fixed the Technical Foundation

At this stage, we worked through the technical issues methodically. Our tasks included:

• Re-submitting the deindexed pages and getting them back into Google’s index.
• Rebuilding the XML sitemap so it listed exactly the pages we wanted crawled and indexed,
• Cleaning up robots.txt so nothing important was blocked.
• Correcting canonical tags site-wide so every page pointed to its one URL.
• Replacing the bad 404-to-homepage redirects with proper handling (relevant 301 redirects where a page moved, and a clean 404 experience where it didn’t).

Made the Site Fast

First, we converted and compressed every image on the site, which involved using modern, lighter formats and right-sizing them. We then went through the code to cut what wasn’t needed and streamline what was. 

In a short time period, the site became noticeably faster with healthier Core Web Vitals.

Tightened up On-Page SEO

Here’s what we did for SEO:

• Wrote optimized, click-worthy title tags and meta descriptions for every page, 
• Adding local keywords naturally into the body, 
• Built out internal links between related services and locations so authority flowed as expected, and 
• Added relevant external links where they supported the content.

Targeted the Local Market 

After our input, local keywords now live where they belong – in titles, headings, body copy, and on the dedicated location pages. WET’s site now effectively caters to the specific city-and-service searches that drive emergency calls in Northeast Ohio.

Optimized the GBP

We did a full pass on the GBP: corrected and expanded their categories so the profile surfaces for the right searches, and tightened the rest of the profile to support visibility in the local map pack. 

This is vital for an emergency service since the GBP usually generates the call before the website gets a click.

Set Up Ongoing Monitoring

Finally, we set up a monitoring process so new issues would get caught and fixed quickly, whether that’s a page that slipped out of the index, a broken link, or a speed regression.

The Results So Far

There’s no doubt that two months is too early in an SEO recovery, especially after a core update where trust is being rebuilt gradually. 

Even so, the direction is unmistakable.

• Daily organic traffic has roughly doubled, from ~20 visitors a day in early April to ~50 a day by the end of May.
• Deindexed pages are back in Google’s index and they’re earning impressions again.
• The site is faster, and the technical signals that were working against it are now working for it.
• The GBP is positioned to capture the local map-pack searches it was previously missing.

GBP Performance

Comparing the two months before we started (January–February 2026) with our first two months on the account (April–May 2026), every vital metric moved in the right direction:

Google Business Profile metric	Jan–Feb 2026 (before)	Apr–May 2026 (after)	Change
Total interactions	170	264	+51%
Calls	34	58	+71%
Direction requests	62	107	+73%
Website clicks	47	89	+89%

The standouts are the actions that are turning into revenue. 

Phone calls rose 71% and direction requests rose 73% – the two clearest signals that someone is about to become a customer. 

Also, website clicks from the profile nearly doubled. 

In case you’re wondering, this payoff comes from correcting the profile’s categories and tightening the rest of the listing so it surfaces for the right local searches in the map pack.

What’s Next?

The recovery isn’t finished yet. 

We’re still working on this campaign: publishing and strengthening content, expanding internal links as new pages mature, building local relevance and citations, keeping the technical side clean, and growing the GBPs footprint.

Based on the current trajectory and the work still in the pipeline, our target is 200+ organic visitors per day within roughly four months (this is past the site’s pre-update peak) and ready the site to hold up to the next core updates.

The Takeaway

Over the years, we’ve seen a Google core update expose every shortcut a site has been getting away with. 

For the Water Extraction Team, that meant thin AI content, no real page structure, a stack of technical issues, a slow site, and an underused GBP all coming due at once.

As you can see, two months in, the traffic is now back on the rise with our careful approach. The next few months are about turning that recovery into a position stronger than the one the update took away.