This Is What Happens When You Accidentally De-Index Your Site from Google

• Updated on: 2019-11-06
• Read original article here

Does reading that title give you a mini-panic attack?

Having gone through exactly as the title suggests, I can guarantee your anxiety is fully warranted.

If you care to relive my nightmare with me — perhaps as equal parts catharsis and SEO study — we will walk through the events chronologically.

It was a Sunday morning. I was drinking my coffee and screwing around in our SEO tools, like normal, not expecting a damned thing. Then … BAM!

As SEOs, we’re all used to seeing natural fluctuations in rankings. Fluctuations, not disappearances.

Immediately my mind goes to one place:it’s a mistake. So I jumped into some other tools to confirm whether or not Ahrefs was losing its mind.

Google Analytics also showed a corresponding drop in traffic, confirming something was definitely up. So as an SEO, I naturally assumed the worst…

Algorithm update. Please, please don’t let it be an algo update.

I jumped into Barracuda’s Panguin Tool to see if our issue coincided with a confirmed update.

Nobody ever thinks clearly when their reptile brain is engaged. You panic, you think irrationally and you make poor decisions. Zero chill.

I finally gathered some presence of mind to think clearly about what happened: It’s highly unusual for keywords rankings to disappear completely. It must be technical.

It must be indexing.

A quick Google search for the pages that lost keyword rankings confirmed that the pages had, in fact, disappeared. Search Console reported the same:

Notice the warning at the bottom:

Now we were getting somewhere. Next, it was time to confirm this finding in the source code.

Our pages were marked for de-indexing. But how many pages were actually de-indexed so far?

All of them. After sending a few frantic notes to our developer, he confirmed that a sprint deployed on Thursday evening (August 1, 2019), almost three days prior, had accidentally pushed the code live on every page.

But was the whole site de-indexed?

It’s highly unlikely, because in order for that to happen, Google would have had to crawl every page of the site within three days in order to find the ‘noindex’ markup. Search Console would be no help in this regard, as its data will always be lagging and may never pick up the changes before they are fixed.

Even looking back now, we see that Search Console only picked up a maximum of 249 affected pages, of over 8,000 indexed. Which is impossible, considering our search presence was cut by one-third an entire week after the incident was fixed.

Note: I will never be certain how many pages were fully de-indexed in Google, but what I do know is that EVERY page had ‘noindex’ markup, and I vaguely remember Googling ‘site:brafton.com’ and seeing roughly one-eighth of our pages indexed. Sure wish I had a screenshot. Sorry.

Once the problem was identified, our developer rolled back the update and pushed the site live as it was before the ‘noindex’ markup. Next came the issue of re-indexing our content.

I deleted the old sitemap, built a new one and re-uploaded to Search Console. I also grabbed most of our core product landing pages and manually requested re-indexing (which I don’t fully believe does anything since the most recent SC update).

There was nothing else we could do at this point, other than wait. There were so many questions:

Only time would tell.

In assessing the damage, I’m going to use the date in which the erroring code was fully deployed and populated on live pages (August 2nd) as ground zero. So the first measurement will be seven days completed, August 2nd through August 8th.

Search Console would likely give me the best indication as to how much our search presence had suffered.

We had lost about 33.2% of our search traffic. Ouch.

Fortunately, this would mark the peak level of damage we experienced throughout the entire ordeal.

During this period I was keeping an eye on two things: search traffic and indexed pages. Despite re-submitting my sitemap and manually fetching pages in Search Console, many pages were still not being indexed — even core landing pages. This will become a theme throughout this timeline.

As a result of our remaining unindexed pages, our traffic was still suffering.

Two weeks after the incident and we were still 8% down, and our revenue-generating conversions fell with the traffic (despite increased conversion rates).

Our pages were still indexing slowly. Painfully slowly, while I was watching my commercial targets drop through the floor.

At least it was clear that our search presence was recovering. But how it was recovering was of particular interest to me.

Were all the pages re-indexed, but with decreased search presence?

Were only a portion of the pages re-indexed with fully restored search presence?

To answer this question, I took a look at pages that were de-indexed, and re-indexed, individually. Here is an example of one of those pages:

Here’s an example of a page that was de-indexed for a much shorter period of time:

In every instance I could find, each page was fully restored to its original search presence. So it didn’t seem to be a matter of whether or not pages would recover, it was a matter of when pages would be re-indexed.

Speaking of which, Search Console has a new feature in which it will “validate” erroring pages. I started this process on August 26th. After this point, SC slowly recrawled (I presume) these pages to the tune of about 10 pages per week. Is that even faster than a normally scheduled crawl? Do these tools in SC even do anything?

What I knew for certain was there were a number of pages still de-indexed after three weeks, including commercial landing pages that I counted on to drive traffic. More on that later.

At this point I was getting very frustrated, because there were only about 150 pages remaining to be re-indexed, and no matter how many times I inspected and requested a new indexing in Search Console, it wouldn’t work.

These pages were fully capable of being indexed (as reported by SC URL inspection), yet they wouldn’t get crawled. As a result, we were still 9% below baseline, after nearly a month.

One particular page simply refused to be re-indexed. This was a high commercial value product page that I counted on for conversions.

In my attempts to force re-indexing, I tried:

Nothing worked. This page would not re-index. Same story for over one hundred other less commercially impactful URLs.

Note: This page would not re-index until October 1st, two full months after it was de-indexed.

By the way, here’s what our overall recovery progress looked like after four weeks:

The great plateau. At this point we had reindexed all of our pages, save for the ~150 or so supposedly being “validated.”

They weren’t. And they weren’t being recrawled either.

It seemed that we would likely fully recover, but the timing was in Google’s hands, and there was nothing I could do to impact it.

It took about six weeks before we fully recovered our traffic.

But in truth, we still hadn’t fully recovered our traffic, in that some content overperformed and was overcompensating for a number of pages that were not yet indexed. Notably, our product page that wouldn’t be indexed for another ~2.5 weeks.

On balance, our search presence recovered after six weeks. But our content wasn’t fully re-indexed until eight-plus weeks after fixing the problem.

For starters, definitely don’t de-index your site on accident, for an experiment, or any other reason. It stings. I estimate that we purged about 12% of all organic traffic amounting to an equally proportionate drop on commercial conversions.

Once pages re-indexed, they were fully restored in terms of search visibility. The biggest issue was getting them re-indexed.

Some main questions we answered with this accidental experiment:

Yes, we fully recovered and all URLs seem to drive the same search visibility.

Search visibility returned to baseline after six weeks. All pages re-indexed after about eight to nine weeks.