Welcome to the Q&A Forum

Hi Andy, A dynamic design. Thanks!

Whether one should have a folder structure versus # tag implementation completely depends on the content, page design and user intent. #tag implementation is useful when the entire content needs to be rendered on the same page. The advantages - You dont have to wait for the new page to load You can have a single page that has all the content Disadvantages - You cannot create multiple pages which some believe is important from an SEO perspective i.e. having more pages in Google's index In case of dedicated pages, the advantages and disadvantages are reversed. Again I would suggest that instead of SEO, more focus is provided to user intent and design. Lastly in case of folder structure, please do not forget to add pagination tags as recommended by Google.

I would backup your htaccess file. then remove half the rules, then test. then you will know what half it is in. keep doing this to you find it

Hi, Yes you can contact the owner to ask for removal. It might or might not be worth your time. You can do that too. Or actually the best way to do this proactively in the future, if you are using wordpress, is using RSS footer option or manually set this up that will display the original full link of the article, this way it is automatically there as the scrape your RSS feed. This would be my top pro-active suggestion. You can do this manually with Google Webmaster Tools and/or Copyscape, or also you can set up Google Alerts for each most that you have done that will notify you when the content is scraped. For detailed info how to do some of this see this article also make sure to read the comments they are informative as well: http://blog.kissmetrics.com/content-scrapers/ As far as actively fighting this, many say, it is not worth it, as long as you take precautionary steps to make sure that you always outrank the scrapers, with methods such as the RSS footers for each article you publish. Hope this helps!

Hi, Start with installing the Redirect Path plugin for Chrome so you can more easily track what's happening with redirects on your site. That hopefully can provide you with valuable insights. Probably every extra parameter on your site will cause a redirect on your site. So go ahead and just enter a URL on your site add a parameter or the GCLID parameter to see what happens. Use Redirect Path to determine from where to where the page is redirecting. Now you can tell your developer or figure out yourself where the redirect is triggered and how you can overcome this. Good luck!

This is an old question, but I'll answer.  Yes - we just set a number of WordPress sites on SiteGound.  Bought their Geek account.  Very, very happy with it so far, but am aware that the costs will increase significantly as they do draw you in a bit with their slashed pricing for the first year. Happy with the package as it is super-fast and really like their caching solution.

Doesn't Apache mod_rewrite do the trick?

I've used pagely in the past and liked it, and for Moz subscribers we do have a discount with them at http://moz.com/perks (I have no other connection with them). I personally use Tigertech for my wordpress hosting, and have had good results with them.

I don't see why this would be any different than a normal redirect. Is there some problem you are experiencing that I am unaware of? Here are a few methods you can use to redirect URLs.

Thanks for the help George!

Thanks for sharing the links Thomas! I'll check these tools right away.

Thanks Thomas!

But what if I remove the 301 redirect rules in my .htaccess file right(a few minutes) after successfully checking the redirected URLs?

Yes good idea to add code before going live.  Worth creating two views (profiles) one where you filter out the local hostname (domain) traffic and the other where you only include the live hostname traffic. This means you won't mistake testing traffic for real traffic.  Let me know if you need any other help on doing that.

Do you have at least a guess on the percentage of improvement?

Thanks Peter!

Hey there, Unless I'm missing some information none of the rules there would redirect either of those pages to the homepage. Is there more of the file? -Tom

Thanks Peter!

I've tested both and the logic looks fine. However, as always with .htaccess changes, I'd recommend testing to verify this has been set up properly once you roll these out (easy enough with a quick ping / page load).

Yes, both result in the same. The difference with the first one that I gave is that it tests !^www.mydomain.com for non-inclusion(due to the exclamation mark before the www) of the www. The condition (RewriteCond) tests the URL following to see if it does not include www. If the condition is true (i.e. is does not include www) then the RewriteRule is applied. I hope that makes sense. Peter