Welcome to the Q&A Forum

Have you tried Positionly (https://positionly.com/)? I use it for my keyword tracking across different countries. Gives daily rankings for your keywords as well, which is pretty useful. It also covers Yandex.

Hi,

I'm currently having issues with some of the user reviews on product pages. Can you spot any issues in the reviews?

Thanks

Hi

I'm wondering if the following URL structure using subdirectories would be alright to use on a multinational site.

I have local products only in the local language and english.

I plan to use:

• /uk/ - UK product in English (geo target in GWT to UK, href lang="en")
• /fr/ - French product in French (would geo target this in GWT to France, and hreflang="fr-FR")
• /fr-en/ - French product in English (no geo-targeting, hreflang ="en")
• /de/  - German product in German (would geo target this in GWT to Germany, and hreflang="de-DE")
• /de-en/ - German product in English (no geo-targeting, hreflang ="en")
• /at-de/ - Austrian product in German (would geo target this in GWT to Austria, and hreflang="at-DE")
• /at-en/ - Austrian product in English (no geo-targeting, hreflang ="en")

Does the name of the subfolder matter? I've tried to keep the URL's shorter, so german users in Germany would get just /de/ rather than /de-de/, and have made the english version of the content the more ugly URL as it's used much, much less.

The URL structures aren't really consistent here (ie. uk and fr-en are for english content, but are different in URL format) but I'm wondering if this is an issue, or if the above would be fine.

Thanks!

Hi,

We've implemented pagination on the reviews with rel=next/prev, but have seen no improvements since this. An example page with reviews is here. Can you see any issues on this that would be causing the problem? Thanks!

Hi John,

See here - I think it's an issue with the tool tracing rel=next/prev

http://moz.com/community/q/why-are-our-rel-prev-next-pagination-pages-still-being-reported-to-have-duplicate-page-titles

Cheers

Thanks Aleyda, this is great!

I'm wondering, if on a TLD, is it necessary to have both the country code and language in the URL? Or would it be possible to just use language and use href lang in the code to specify the where it's relevant?

I do have each venue in the local language AND in english (though I would prefer both of these languages aimed at the local country - this is because nobody outside the countries search for these venues, but many do also search in english rather than just their local lang)

I have:

• .com/se/sv/venue-name (Venue in Sweden, in Swedish)
• .com/se/en/venue-name (Venue in Sweden, in English)

Or is it better to just use language?

• .com/se-sv/venue-name
• (not sure how to do the english version here)

Would country code be more relevant to use in this case?

Thanks!

Hi

I was just wondering if there is any difference in using rel='next' rather than rel="next". Would it still work the same way?

I mean using the apostrophes differently, would it matter?

Thanks!

Hi Mihai,

Thanks for your reply. I also have parameter URL's on some of these pages, which are mainly used when I send email campaigns to the same targeted pages, but with slightly modified content such as a custom banner on it. These pages are all noindexed but are helpful for targeted campaigns. In these cases the landing page still has the same paginated reviews series at the bottom.

How would I treat these? For example:

http://www.example.com/product?custombanner

In these situations would i use the following for the paginated review URL's?:

http://www.example.com/product?custombanner&review-p2 in conjuction with a canonical tag to http://www.example.com/product?review-p2, or could I just leave it as pointing to http://www.example.com/product?review-p2 (ie no need to have unique review pages for the parameter pages with canonicals)?

Thanks

Thanks Mihai, that's exactly what I was thinking. I'll go ahead with this.

Now that this is all solved I can go relax by the pool and take it easy

D8GBLEi.jpg

• In Webmaster Tools, set the subdomain up as its own site and verify it

• Put on the robots.txt for the subdomain (beta.website.com/robots.txt

  User-agent: *
  Disallow: /

• You can then submit this site for removal in Google Webmaster Tools

1. Click "optimization" and then "remove URLs"
2. Click "create a new removal request"
3. Type the URL "http://beta.website.com/" in there
4. Click "continue"
5. Click "submit request".

Hi,

I am looking to add pagination on product pages (they have lots of reviews on the page). I am considering using rel="next/prev, to connect the series of review pages to the main product page.

I unfortunately don't have a view-all page for these reviews or the option to get one - the reviews refresh on the same product page (by clicking whatever number page of reviews). This means each page has the exact same description content and everything else, but with different reviews. In this case is rel=next a good option?

The format currently would be:

• On example.com/product

link rel="next" href="http://example.com/product?review-p2"

• On example.com/product?review-p2

link rel="prev" href="http://example.com/product, link rel="next" href="http://example.com/product?review-p3 etc.

Would this be a good format for product page reviews? I see rel=nextprev commonly used on ecommerce category/list pages but not really on the paginated reviews on product pages, so I thought I would see if anyone has advice on how best to solve this.

I'm also wondering if it would be best to not combine this with a canonical tag on all the different review pages pointing to the product page, seeing as the reviews are actually different (despite the rest of the content being identical).

I am hoping to pick up longer tail traffic from this, I figure by connecting the pages and not using canonicals that this way I could get more traffic from the phrases used in the reviews. By leaving out the canonicals, is it possible a user searching for phrases that might be deeper in the series, to land on, say, ?review-p4? Any thoughts if this would drive more traffic?

Thanks!.

Thanks for your reply, Stephen.

Is www.example.com/se/en/hotel-name the shortest, best possible way to do this?

So for the swedish language version it would be www.example.com/se/se/hotel-name (to keep the format consistent)?

Hi

I am wondering what the best URL format to use is when a website targets several countries, in several languages. (without owning the local domains, only a .com, and ideally to use sub-folders rather than sub-domains.)

As an example, to target a hotel in Sweden (Google.se) are there any MUST-HAVE indicators in the URL to target the relevant countries? Such as hotelsite.com**/se/**hotel-name. Would this represent the language? Or is it the location of the product?

To clarify a bit, I would like to target around 10 countries, with the product pages each having 2 languages (the local language + english). I'm considering using the following format:

hotelsite.com/en/hotel-name (for english) and

hotelsite.com/se/hotel-name (for swedish content of that same product)

and then using rel=”alternate” hreflang=”se-SV” markup to target the /se/ page for Sweden (Google.se) and rel=”alternate” hreflang=”en” for UK? And to also geotarget those in Webmaster tools using those /se/ folders etc.

Would this be sufficient? Or does there need to be an indicator of both the location, AND the language in the URLs? I mean would the URL's need to be hotelsite.com/se/hotel-name/se-SV (for swedish) or can it just be hotelsite.com/se/hotel-name?

Any thoughts on best practice would be greatly appreciated.