Seo Hacking Galway
S.E.O. Hacking is hardly a new process, invented from recent despair but an ongoing "structure" to leverage pagerank.
Some basics remain;
- Shared hosting - but not neccessarily
- Poor passwords and usernames - often cited as the cause, rather than the above
- Combinations of the two above
Purpose
- Increase the pagerank of the "imposter"
Consequence
- Your PR is diluted, with possible destruction [you are responsible (you bear the repercussion ) for who you link to]. Not at all exclusive with the purpose.
Effect
- The new "host", may be penalised, depending on the site which is linked to (already deemed to be "infected" / sub - prime / nasty / unsavoury-at-best/ legendary, for being unpleasant ), in the view of the Search Engines.
Two rather dramatic cases, presented themselves recently (Galway). Both publishers were unaware, for reasons which can only be seated in a lack of awareness, or a frivolous attitude.
(Case one) With this hacked site, you could purchase Viagra (nothing to do with its expiring patent), from a well known Galway Business. Likewise for Cialis or Female Viagra. This site was not in the "Pharma" category.
(Case Two) Another Galway Business, served content which lauded the benefits of a particular Female Boot - not its Bread and Butter by a long shot. Serving six seperate links to seperate domains, from the main page (highest PR.).
Both cases diluted their primary pagerank position by dilution of their own on-page keyword densities ( keyword and implicit branding), and direct linking to questionable and unauthorised resources.
Curious
Neither were too bothered??
How
Without server access, there is nothing definitive
- This stank of a conditional hack; cron job, htaccess, or server wide pandemic.
- This baby wasn't database driven and smells of either a poorly executed "manual injection" or poorly executed (though functional from their point of view), pan server exploit.
Cures
- Employ Backups - small sites can use the Search Engine Cache', in the absence of backups.
- Remove the offensive code - easy enough in most cases, especially html (non-cms) projects.
- Change passwords and make 'em stronger - more leverage for dealing with an unrepentant host
- With a C.M.S., check memory size of your .html files (usually empty or very little - note size change - more than one and possible hundreds, are infected - overwrite with default or proper).
Outside your control
Your space on someone else's server - the best you can do is have backups and a functional complaint system - move your files to Ireland where you can reach the neck of your host.
Within it
- Back ups
- Passwords, etc.
- Monitor - See Valid html for one warning system
**This is a guide only, and cannot (won't even try to) encapsulate everything.
Related; Paypal Facebook