I would suggest you implement the plugin SEO by Yoast and then follow all the configuration steps. It will help you solve all your permalink options while providing information on which will be the best option.
Hope that helps!
Welcome to the Q&A Forum
Browse the forum for helpful insights and fresh discussions about all things SEO.
I would suggest you implement the plugin SEO by Yoast and then follow all the configuration steps. It will help you solve all your permalink options while providing information on which will be the best option.
Hope that helps!
Not at all, if the URL language matches the content of the page then it should be even better that using a full English URL.
However, I would suggest using domain.com/ar/blog/عنوان بلوق عربية طويلة حقا على شيء مثير جدا للاهتمام for the arabic blog and if there's an english or french version of that page, you can also implement hrelang on them and point them to domain.com/blog/English-blog-title-really-long-on-something-very-interesting
Hope that helps!
Are the same classes in the future link to the same page? are you using canonical tags correctly? Your URL should help diagnose the problem and guide you better,
A couple things come to my mind after a quick look of your backlink profile:
Hope that helps!
Unfortunately, I experienced that issue in the past and had to create a new one instead. Write an email to moz help to see if they can reactivate it for you: help@moz.com
Anyway, you should find a solution to redirect the entire domain while "keeping" the URL structure in the new subdomain.
Example:
www.domain.co.uk/page1 redirects to www.domain.com/uk/page1
And for those pages that have no related or 404 you also redirect them by using a rewrite rule that redirects EVERYTHING to the new location, even under a subdirectory.
Rewrite rule example (for the .co.uk domain):
RewriteCond %{HTTP_HOST} !=www.example.com [NC]
RewriteRule ^(.*)$ http://www.example.com/uk/$1 [R=301,L]
Unfortunately, that can't be done. The change of address feature allows only from one domain to another, but not to a specific subdirectory.
The implemented 301s should be enough. Have you 301 file by file or 301'ed the entire domain? As that is the way that it should be done (if you are using Apache that can be done with a simple rewrite rule). If you 301'ed the entire domain, soon Google will show a message that you no longer have access to that .co.uk and .ie domains.
Hope that helps!
Have tried doing it on the PRO version?
Does your sitemap include duplicate pages or pages that crawlers wouldn't want to list? (like search results pages, pagination of duplicate pages, etc.)
How do you know that you have 50K indexed pages if GWT reports 700 and a site: search reports over 50k?
I've seen that before. Probably it just got stuck. Try removing the report and running it again, that should do the trick.
Hey Christopher,
OSE only reports 4 incoming links, that not even near to what you will need to rank for the terms you are probably targeting. The competition in the real estate business is fierce,
Anyway, there are a few things that may help that you can do now:
Those are just a few enhancements I can suggest...
Hope that helps!
It can help. Remember, all search engines want is the same that users want. more information. If the content you add is unique to your site and to the web, then it should help.
You don't see traffic from bit.ly as they actually redirect the user without serving any content, therefore is just a redirection, instead, you should see the actual referrer, facebook, or whatever. However, if you are getting the hit from a facebook page, it is probably an HTTPS page, and therefore, if redirected to a non-SSL page referrer information isn't passed along. However, you could see something like facebook.com/u.php?.... You should use Analytics tracking variables to better understand from which posts are those visitors coming: https://support.google.com/analytics/answer/1033867?hl=en
As for your second question, just like you can interpret the redirection, so can Google or whatever search engine scrapes the page looking for signals. It won't matter if you pass them through bit.ly or services alike, the link ends up in your site (as long as there's a 300 redirection in place, which it is in bit.ly).
Hope that helps!
I suggest you take a look at the following Q&A explaining the implications of having affiliate links pointing directly to your site and how to deal with that: http://moz.com/community/q/blocking-affiliate-links-via-robots-txt
Hope that helps!
I suffered a similar issue. Although I do recognize I bought links back in 2007 - 2010, we were still getting about 10 new links every day, probably from some negative SEO campaign.
Got a penalty as a "partial match" affecting "some incoming links". We worked over a year to clean the backlink profile and still every reconsideration request failed as Google returned some links that were actually discovered after we downloaded all the links from all the possible sources.
What we did to solve this: downloaded the domains from both GWT and OSE, and instead of going link by link and spending at least 2 month contacting AGAIN, we added domain:[domain-to-disavow] and did it for almost 90% of the profile. Even domains that were linking to us honestly, but could possibly be seen as spam (like a link for my own profile in a dev forum).
After sending the disavow file with about 1500 domains, we didn't wait and sent the reconsideration request, with all the previous reconsiderations and their outcome and the decision we made to give it a "last shot". 2 weeks later we received their response, Penalty Revoked.
We started seeing ranking increases from the next day.
Those suggesting not to add the SSL pages to the HTTP sitemap are using data back from 2007, when indeed Google showed an error on those sitemaps listing both HTTP and HTTPS pages as they were being recognized as different domains. Those days are long gone. Google had evolved and can now handle sitemaps with both HTTP and HTTPS pages just fine.
Believe me when I say, Google has enough experience to deal with this kind of "attacks". They automatically monitor click fraud and even using proxies won't circumvent Google's techniques to detect click-fraud.
Anyway, you can contact Google explaining the issue right from your AdWords dashboard.
I would definitely go with www.example.com/cityname. It isn't just easier to maintain, but it will be much easier to rank as any link juice received in www.example.com/cityname1 will also affect www.example.com and www.example.com/cityname2, which in the end, will make even easier for new cities that you add later.
Having domains including the city and linking to each other will probably be seen as an EMD which will affect all domains.
There's no "must" here, you can do it if you want. But as long as you are redirecting ALL non-www to the www version of it, you have nothing to worry about.
I redirect the non-www to the www but I set that up anyway, just in case 
The redirects will cause a small dilution of the pagerank on those pages, just the same amount as having a single link in the trips/country to destinations/country.
But forget about the pagerank, do you expect to get more search traffic from search if the URL says trips or destinations? It all comes down to what you want achieve. The URL you have now doesn't look bad at all, and you can probably keep it by tweaking the code a bit without redirecting all pages to the destination/country page, so again, study the pros/cons:
Pros:
Cons:
I only suggest to implement redirects if they really offer a better option, but in this case, you will end up with the same result with less pagerank, and longer URLs...
Just my 2 cents 