Forum Moderators: Robert Charlton & goodroi

Message Too Old, No Replies

Lost All Indexed Pages After Reconsideration Request

         

Super_Chunk

12:20 pm on Jul 26, 2010 (gmt 0)

10+ Year Member



We finally sent our 3rd reconsideration request after alot of work making sure everything was squeaky clean on our site and not violating any guidelines. 3 days later (24/07/10) Google informed us that they have processed our request so the waiting begins....

I just checked in GWT and my eyes nearly fell out when I saw that the number of "URLs in web index" has suddenly fallen from around 1500 to 0! The wording they use when processing requests is "If we don't find any problems, we'll reconsider our indexing of your site". Also "Not Found" errors have got up quiet a bit but not sure if this is related. The crawl stats in GWT don't give much away (they are currently high but always up and down) but we can see that googlebot is currently spidering the site.

I appreciate they could be flushing out the index pages and starting with a clean slate but could this be a good or a bad thing, or just standard prcedure after processing a reconsideration request? Has anyone else encountered this before?

Nothing like noticing that on Monday morning to get the heart racing! Any experience shared on this greatly appreciated.

tedster

2:48 pm on Jul 26, 2010 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



If you really lost all indexed pages, then you would be getting no Google search traffic at all. I assume that's not the case, right? If so, you are just seeing a reporting error in Webmaster Tools - and that kind of thing gets reported here pretty often, unfortunately.

Super_Chunk

3:10 pm on Jul 26, 2010 (gmt 0)

10+ Year Member



Interesting, Google traffic seems to be especially low - most people finding us are doing so by searching for our name/domain name or through our Google Shopping entries. When using the site: operator we do get our indexed pages but this has always lagged behind the number reported in GWT so I assumed that there was a delay.