Blog posts not getting indexed and being outranked by scrapper sites.

[gfreeman23]

Our Google traffic has dropped significantly over the last year and now we're struggling to even get our blog posts indexed. It's been extremely discouraging and we're trying to do what ever we can to fix it.

I've included a screenshot of our Google traffic as well as Pages Indexed according to WebmasterTools.

http://i.imgur.com/Wu1D8.jpg

The Problem

• Our blog posts are frequently not getting indexed.
• Many times they are outranked by low authority scraper sites, our Twitter/FB account, etc.
• Sometimes our homepage will rank instead of the blog post.
• Sometimes we'll break a news story, get tons of quality backlinks, and still be nowhere in Google.
• Pretty much the only Google traffic we see is from existing posts.
• Still 3,200 pages indexed when we have only 1,600 posts. I guess this isn't really a problem... just waiting for the meta noindex to take effect.

More details

• We've seen no duplicate content or other warnings from WebmasterTools.
• We've been constantly acquiring quality backlinks from credible sites.
• We deleted the useless content and fixed the canonical issues that were a result of switching servers.

History

Our site is a news/entertainment blog. The traffic usually has spikes depending on what's going on in the news.

• Nov 1, 2011 - Site kept maxing out at 30k+ visits so we switched servers.
• Jan 30, 2012 - Hired a writer so we could focus on other aspects of the site.
• Apr 19, 2012 - Noticed our posts weren't getting indexed like they used to. Suspected our writer was spinning articles but couldn't find any evidence. 90% of our blog posts were nowhere to be found in Google. Scrapper sites would outrank us for our own stories... even our Twitter account was ranking ahead of us. IF our story would show up in Google it would usually be the home page instead of the blog post.
• Sep 2012 - Finally got more serious about addressing the problem. Noticed a couple potentially big problems and started making changes.

Canonical Issues

1. non-www site didn't redirect to www. It showed 2 different link profiles according to OpenSiteExplorer and 0 backlinks according to Webmaster Tools.
2. Wordpress shortlinks weren't redirecting to the actual permalink. For instance http://www.domain.com/?p=123 and http://www.domain.com/post-example were both getting indexed.

For every post there were 4 different versions that Google had to choose from.

http://domain.com/?p=123, http://www.domain.com/?p=123, http://domain.com/post-example, and http://www.domain.com/post-example

I figured the canonical issues must have happened when we switched servers which was the reason for the drop in WebmasterTools indexed pages and increase in Not Selected pages.

FIXED (Sep 15): One we fixed the canonical issue the Indexed Pages went back up however the Not Selected is still the same.

Duplicate Content

When we first created our site we wanted to have tons of images for each musician/athlete/actor/etc. so we uploaded about 5-10 for each person. We created a blog post for each image with no writing and the exact same post titles. As a result there were TONS of low-quality, similar posts, with virtually identical permalinks. e.g. http://www.domain.com/james-smith1, http://www.domain.com/james-smith2, http://www.domain.com/james-smith3, etc.

A crawl on Sep 26 showed over 550 duplicate content warnings.

FIXED (Oct 1): We deleted/301 redirected the useless pages (they weren't getting traffic anyways) and by the next crawl the number was almost to 0... which it's at now.

We also had TONS of tags (since there're constantly new names in the media) that were getting indexed so we had meta robots noindex them.

Questions:

1. Why aren't a majority of our posts getting indexed?
2. Were we penalized or just stuck because of a filter?
3. How long should it take for meta robots to noindex the tags pages? (I did it on Sep 25 but they are still there)
4. If a site is scraping our content (same title, image, excert) but linking to us, should we contact them and tell them to remove it?
5. Is there anything else we need to do start getting our blog posts indexed like they used to?
6. Should we try contacting Google to re-evaluate our site?

Sorry, that was a LOT of writing. If anyone wants the URL please let me know so I can PM it to you. Any help would be greatly appreciated!

Wu1D8.jpg

[danatanseo]

I sympathize with your frustration. I know what it's like to come into a situation after years and years of technical missteps made by folks who never took SEO into consideration and then have to start cleaning up the mess.

You have a lot of hard technical problems and I'm not a developer so I will let those more technically gifted than myself address some of those.

There is one question I felt I could answer and that is #4: "If a site is scraping our content (same title, image, excert) but linking to us, should we contact them and tell them to remove it?"

You could go that way. But in the event that it is a decent site (despite the fact they scraped your content), first make sure you have a canonical tag properly implemented on your page, then, contact them and say "I see you found my content interesting enough to share on your site. Instead of me asking you to remove it, would you mind adding in an attribution line, giving credit to my site as being the source of the content and including a link back to me please? I think we can both agree this would be better than having me file a DMCA request with Google."

Just a thought

[gfreeman23]

Thanks for the quick response Dana!

They are sourcing us but at the moment they're constantly showing up instead of our site. There's no reason they should outrank us, but we figured they couldn't really be hurting us since they are linking to us.

It's weird that the site is able to scrape content and still get good indexes... maybe Google just hasn't picked up on it yet.

We are hoping that we don't have to worry about scrapers once our blog posts start getting indexed like they used to.

I think we'll send them a friendly email like you suggested.