I received an email today from a site owner asking if I could consult with them to help them figure out why they could not get their home page to rank on Google. They previously had had some penalty issues but those were cleared up. The rest of the site was ranking well, but the home page appeared to be penalized. I thought I'd share this cool story of detective work and collaboration that ends with us finding the cause and rejoicing!

The page was noindexed

The first thing that I did was do a site:search in Google. The site was certainly present, but I couldn't find the home page of the site in the Google results. Next, I checked the robots.txt file of the site by typing in www.sitename.com/robots.txt. Although a lot of directories of the site were blocked, there was no obvious reason for Google to not see the home page.

I probably should have actually visited the site first to save me some time. When I did visit the site, I saw this big shining beacon on the bottom right of my screen:


Well, that would certainly do it. (By the way, this was created by using the Nofollow Chrome Extension). I was about to write the site owner back and tell him to simply remove the noindex tag from the site, but I checked the source code, and was flummoxed when CTRL-F revealed no "noindex" in the source code at all.

Thank you Twitter!

So I turned to Twitter. I love asking questions of my SEO peers on Twitter. I tweeted out my question and several people gave their thoughts. Thank you to Mike VysockaRoey, and Thomas Haynes who had some great thoughts including checking to see whether the page was blocked by an x-robots tag in the header, but this was not the case.

Jenny Halasz asked me to share the url and she spent quite a bit of time digging in to this mystery. And eventually she solved it! She decided to look at the page using Chrome's dev tools. You can do this by clicking on View --> Developer --> Developer Tools.

She then did a CTRL-F and BOOM!  Look what was hidden in a div:

Wow. There was also a second noindex tag in another div on the page.

The timing on this was incredible as earlier this week, Gary Illyes from Google tweeted a warning that including a noindex tag in the body of your page (as opposed to the header) would cause Google to noindex the page

The fix

The offending code has now been removed from the site. The site owner will use Google's fetch as Googlebot in the Google Search Console to quickly ask Google to index the page. I expect that the homepage should be ranking again quite quickly.


Update: It took about 24 hours for the page to start ranking again. All was well once that code was removed.