Welcome to the Q&A Forum

Thanks Alick, Moosa and Keszi,

We realize PR is no longer as important a factor as it used to be, but it still is a factor and represents something, and we can't figure out why it's not higher.

We look at domain authority in OSE as well and it's 29, also lower than we'd expect it to be.

Hi,

Our site https://soundbetter.com has been live for 2 years now, and as of yet we haven't yet been able to get our PageRank above 3/10.

We have thousands of unique pages and plenty of original contextual content, we avoid duplicate content best we can, follow google's best practices for site structure, deal with any issues that come up in webmaster tools, have schema.org markup, avoid link spamming, have inbound links from authority sites (though OSE doesn't show most of them for some reason), lots of social shares to our pages and the domain has been owned by us for 12 years.

Any thoughts on why we would still have a PR of 3?

Thanks for helping

Hi guys,

We're thinking of changing the url structure of the tutorials (we call it knowledgebase) section on our website. We want to make it shorter URL so it be closer to the TLD.

So, for the convenience we'll call them old page (www.domain.com/profiles/profile_id/kb/article_title) and new page (www.domain.com/kb/article_title)

What I'm looking to do is change the url structure but keep the likes/shares we got from facebook. I thought of two ways to do it and would love to hear what the community members thinks is better.

1. Use rel=canonical

I thought we might do a rel=canonical to the new page and add a "noindex" tag to the old page.

In that way, the users will still be able to reach the old page, but the juice will still link to the new page and the old pages will disappear from Google SERP and the new pages will start to appear.

I understand it will be pretty long process. But that's the only way likes will stay

2. Play with the og:url property

Do the 301 redirect to the new page, but changing the og:url property inside that page to the old page url. It's a bit more tricky but might work.

What do you think? Which way is better, or maybe there is a better way I'm not familiar with yet?

Thanks so much for your help!

Shaqd

Thanks Everett for your help.

The HTML code is ok, you're right. It's something with how we configured the Schema.org tags.

Btw, where did you see the several different schemas?

ShaqD

Well, I decided to go with the approach we discussed earlier. After I pushed the changes to our live environment and tested it on Google Structured Data Testing Tool, I found a really weird (and very generic) error: "Error: Incomplete microdata with schema.org."

Any idea what could be the issue here?

Results:

Item
  type: http://schema.org/review
  property:
    reviewrating: Item 1
    datepublished: 2014-07-25
    author: Massim L.
    reviewbody: This is the great job made by X. You know what? I will have remix some of my previous songs too... he's so good!!!

Error: Incomplete microdata with schema.org.

Item 1
  type: http://schema.org/rating
  property:
    ratingvalue: 1
    worstrating: 0
    bestrating: 1

Thanks.

ShaqD

Everett, I think you're right. Since I didn't find a place to get inspiration from I will try it out in the way I mentioned above with a scale of 0-1 for every review.

Btw, I'm not sure you guys noticed, but this forum includes thumbs up/down rating system.Unfortunately, they didn't implement the schema.org tags

Thanks a million.

ShaqD

Thanks Ray-pp for the quick and helpful response.

It might be a good idea to add bestRating/worstRating tags to each Review (I'm thinking whether it should be a 0/1 or 1/2 like you suggested). The thing is I need also to add an aggregateReview meta tag in addition to the reviews.

What do you think should be the values for the aggregateReview meta tags reviewCount and reviewValue than?

Hi guys,

I'm deep into the Schema.org meta-tags implementation for the reviews on my website and I'd love to know how do you think I should implement it when I have Positive-Negative reviews as opposed to star ratings.  I couldn't find a site that had this with schema tags for reference.  Fiverr used to have thumbs up/down, but recently changed to star rating.

On our services marketplace we allow users to review the providers they worked with and ask them for a positive-negative review - thumbs up/down with an additional open text area.

I thought about adding a schema.org meta-tags like this:

Lets assume one of our providers got two reviews, one is positive and the second is negative. So, first I thought about adding an aggregateReview meta-tag on top, just like this:

And also add a meta-tag for any review, like this:

Two days ago by
    Kareem Abdul-Jabbar
    Joe is a great guy, I'd recommend him to my friends.

Does that make sense?

Has anyone had the chance to implement a schema.org meta tags for this kind of situation or familiar with a website who does it that way?

Thanks so much for your help!

Shaqd

Thanks Prestashop for your answer.

Is there another solution other than no-indexing all our search results?

Like many sites (yelp, tripadvisor and others) our search results help drive traffic.  They aggregate the answer to questions that are asked in searches, such as 'recording studios in london'.

https://soundbetter.com/search/Recording Studio - Engineer/London, UK

Hi,

according to Webmaster Tools and Siteliner our website have an above-average amount of duplicate content.

Most of the pages are the search results pages, where it finds only one result. The only difference in this case are the TDK, H1 and the breadcrumbs. The rest of the layout is pretty static and similar.

Here is an example for two pages with "duplicate content":

https://soundbetter.com/search/Globo

https://soundbetter.com/search/Volvo

Edit: These are legitimate results that happen to have the same result.  In this case we want users to be able to find the audio engineers by 'credits' (musicians they've worked with).  Tags.  We want users to rank for people searching for 'engineers who worked with'.  And searching for two different artists (credit tags) returns this one service provider, with different urls (the tag being the search parameter) hence the duplicate content.

I guess every e-commerce/directory website faces this kind of issue.

What is the best practice to avoid duplicate content on search results page?

Hi,

according to Webmaster Tools and Siteliner our website have an above-average amount of duplicate content.

Most of the pages are the search results pages, where it finds only one result. The only difference in this case are the TDK, H1 and the breadcrumbs. The rest of the layout is pretty static and similar.

Here is an example for two pages with "duplicate content":

https://soundbetter.com/search/Globo

https://soundbetter.com/search/Volvo

Edit: These are legitimate results that happen to have the same result.  In this case we want users to be able to find the audio engineers by 'credits' (musicians they've worked with).  Tags.  We want users to rank for people searching for 'engineers who worked with'.  And searching for two different artists (credit tags) returns this one service provider, with different urls (the tag being the search parameter) hence the duplicate content.

I guess every e-commerce/directory website faces this kind of issue.

What is the best practice to avoid duplicate content on search results page?

Everett, I think you're right. Since I didn't find a place to get inspiration from I will try it out in the way I mentioned above with a scale of 0-1 for every review.

Btw, I'm not sure you guys noticed, but this forum includes thumbs up/down rating system.Unfortunately, they didn't implement the schema.org tags

Thanks a million.

ShaqD