Welcome to the Q&A Forum

i doubt google could ever do anything about it because so many legit sites get 50%+ of their business from their affiliates Bit of an over-estimation, but 2 years ago I would have agreed that they wouldn't do it.  Today I'm less sure.

no worries bro - thanks for the advice - i'll just get an semrush membership and check it out myself

the links are being place on blackhatworld.com forum we want all of these links to be nofollow we cant install a mod on someone elses site - is it impossible for us to make these links nofollow?

Alan, I cannot think of an answer I have seen recently with the clarity of thought and ability to refute a very bad practice. (Especially on a security level). One thing we do with clients and upgrades (we do not handle clients on other peoples platforms) is to take a new update, give it a few weeks for bugs to be discovered and then do the upgrade on our end. We have clients sign off on us handling the upgrades, etc. from the beginning of the relationship. For Erik I would suggest showing the client what has been said by someone with a lot of savvy experience. If the devs are worth their salt, they will change. This was a good question and Alan delivered a great answer. Robert

thanks marie - thats what i needed to hear

his developers say this: The developers are skeptical about the possibility to update PHP on our server as this could seriously damage the entire RV site functionality i have no clue why his site would be in jeopardy - he said he took care of any security issues by moving the blog to a subdomain from revisitors.com/blog to blog.revisitors.com i also have no idea whether or not that makes his blog more secure but i need some in-depth professional advice here

You'll need to go in to your site on the server via ftp and remove the old version of the plugin manually before updating, Erik. This error is often caused by misconfiguration of the permissions on the plugin folders on the server. Paul

Also check Google webmaster Tools. When doing a site: of your site, there are some odd-looking SERPs and at least one page has a message that the site might be compromised.

thanks.very useful.طراحی ویلا villa1000Thanks for sharing this post.طراحی محوطه

ok andy thanks - i just always thought when you do a search for "how to sell blue widgets to starving eskimos" that the first result in serp would have to be the blog post titled "how to sell blue widgets to starving eskimos" if such a post existed ad indexed. it's inconceivable to me how anything else could rank higher - much less not being able to find it in the first 10 pages i am going to manually search 1000 pages just to see if i can find it at all

As far as the upgrading of php on a server - this is for a different client, I seem to recall? I would have a real problem with a developer saying they weren't going to upgrade because it might break things. Of course it might break things, but there are industry-standard approaches to dealing with this For example, create a duplicate version of the site on a server instance that is using the newer version of php, and do a full Quality Assurance analysis on the dev site to find and fix anything that has issues with the new php version. Then deploy back to the live site with the php upgrade. This is standard operating procedure and is necessary because there will come a time when any older server software will no longer be supported and therefore becomes a security risk as it will be unpatched. Planning for these kinds of upgrades should be included in any website operational plan. Also, their solution to move WordPress to a subdomain is no protection whatsoever for the fact they have an extremely vulnerable, version. First, the site is just as vulnerable to being hacked again as it is still unpatched.  Being on a subdomain has no effect on this. Also, they have ruined the SEO value of that blog by moving it to a subdomain instead of fixing the issue and keeping it as a subdirectory of the prime site. And depending on the type of vulnerability exploited, it may still be possible for a hacker to get into the server via the vulnerable WP, then traverse from the subdomain to the prime site and cause harm there as well. In the short term, if there truly aren't resources to properly do QA (Quality Assurance) on a dev site running an updated version of PHP, the alternative would be to move the WordPress install to it's own server or VPS running a current version of PHP, upgrade it and security patch it, then use a reverse proxy setup to have it show up as blog.domain.com (or even move it back to domain,com/blog). This would at least allow for a properly secured WordPress that could also use current and new plugins. This would, however be at the expense of a slightly more complicated setup of the reverse proxy. Hope that answers your question? Paul

Hello Erik Your page has a page authority score of 25 and a pagerank=4. So as you mentionned, link signals are not so bad. To me you should follow this process: Identify keywords that drive visits to this page (www.revisitors.com/REF/TEST) Build a new page with content related to the old page to make sure that the content of the new page will stay relevant for google and users 301 redirect from the old page to the new one Modify the title

Yes as long as the "www" is included in the URL of the canonical tag.