Welcome to the Q&A Forum

Hi Donford,

Thanks so much for getting back to me. Great answer! I'd like some clarification here. I did not configure this and if I'm going to talk to the developer, I'd like to have more knowledge to speak to it.

Could you please clarify what you mean when you say:

• It looks like something is installed and configured improperly.
• You have 2 head tags on the page that shows up from the redirect.
• This is actually inside the first head tag complete with a body tag and another doc declaration.

I looked at the example you sent, but I'm not sure what I'm looking at. If you could explain those bullet points in more detail, it would greatly help.

You're the best!

Thanks,

Nicole

Hi Moz community!

I have an ongoing duplicate mystery going on here and I'm hoping someone here can answer my question.

We have an Ecommerce site that has a variety of product pages and category pages. There are Rel canonicals in place, along with parameters in GWT, and there are also URL rewrites.

Here are some scenarios, maybe you can give insight as to what’s exactly going on and how to fix it.

All the duplicates look to be coming from category pages specifically.

For example:
This link re-writes:

http://www.incipio.com/cases/tablet-cases/amazon-kindle-cases-sleeves.html?cat=407&color=152&price=20-

To:

http://www.incipio.com/cases/tablet-cases/amazon-kindle-cases-sleeves.html

The rel canonical tag looks like this:

http://www.incipio.com/cases/tablet-cases/amazon-kindle-cases-sleeves.html" />

The CONTENT is different, but the URLs are the same. It thinks that the product category view is the same as the all products view, even though there is a canonical in there telling it which one is the original. Some of them don’t have anything to do with each other.

Take a look:

Link identified as duplicate:

http://www.incipio.com/cases/smartphone-cases/htc-smartphone-cases/htc-windows-phone-8x-cases.html?color=27&price=20-

Link this is a duplicate of:

http://www.incipio.com/cases/macbook-cases/macbook-pro-13in-cases.html

Any idea as to what could be happening here?

Great, thanks for the feedback!

Hi Matt,

Thanks for responding! We don't think it was a Penguin update penalty, but the Panda 4.0. So with that being said, it was do more to thin content and press release content. We weren't using press releases as a link building tactic, but we didn't make the links "no follow."

We like the idea of setting up a press page exclusively for the releases and totally separate from the blog. My concern is that the releases could hurt the main site. What do you think about doing a sub-domain with no follow links?

For example:

www.press.example.com

or do you think no follow links with www.example.com/press would be ok?

Thanks again!

Hi there,

Our company publishes press releases on the company blog and have found we were hit by an algorithm update. We have identified the press releases as being the culprit and would like to move all press releases to a company press page on the main site and title it "press room" or "press." We have a lot of media sites that visit our blog to grab the most recent releases, so they are important to the business.

My question is, how should we handle the page SEO wise? Should we do a "no index" or a "no follow" on all the links? I'm curious what advice the community has on how to handle a company's press page.

Thanks!!