Discussion in 'Blogging' started by freeufcdotinfo, Sep 18, 2010.
I have heard there is maximum number of autoblogs per ip - what is this any why.
Around 10, else it risks looking like a spammer's account.
Is that domains or accounts
The are so many shared hosting accounts with maybe hundreds of domains. Any reason to believe in a max 10 autoblog rule?
Strictly speaking, some would even say 1 ip per blog to be really safe.
What is the issue - adsense - the host - google
shared = a bit unstable. i just got one of my pages suspended for a few moments today due to the high volume of queries being carried out by autoblog along with yarp plugin on my sql. removed yarp and its ok now. so i dont think more than 10 would work without killing your host or sql
It's a precaution from the next google slap. But that would also equate to having quite a bit of investment to get it going. The most economical way is to get a reseller acct to host the autoblogs.
I have a different ip for each blog I make be it an autoblog or a hand written blog. I do use a virtual account at cyberwurx and I'm fine, never had complaints from the host. They do host sql on another server I think.
I have 45. I guess I'm doing it wrong.
I have 34 so I'm doing it wrong too
Still cant see were the problem is
is because the host may complain because of cpu stress
or google - adsense
no further forward
I had that - server overload - had to tone it down, as I have around 10 autoblogs
10 blogs/server but how many posts/blog/day? I think this is also important for SQL and server load.
So from google point of view - do they care - 1 or 1000
I have upwards of 30 on a hostgator reseller account without issue.. They don't take a lot of resources if you're not an idiot about it.. caching, compressing, etc .. I've notice that there are a max number of domains per IP hostgator allows, so even though I have all my sites on one account, they're split among several different IP's.. Just whatever is available when you create the account for said domain
Google isn't going to use your host as a way to determine if you are a spammer, they will use your Registrar details. Once they get hold of one of your details, they can quickly cross reference it to discover all your other domains. Public whois protection doesn't help you. Registrars have full access, and Google is a registrar as well. For those that wish to debate this, please refer to the ICANN Registrar Agreement that every Registrar in the world must abide by.
As for the other reasons to have your blogs on separate IPs, these are some of the reasons.
Dedicated IP will ensure your site runs and is indexed optimally.
Dedicated IP will prevent others.. say your competition, from being able to do a reverse IP lookup to view all the rest of your sites you are running and potentially either steal your keywords, niches, and/or report you to google.
As for server resources, I don't nickle and dime that point, I get a proper server to handle that. I use virtual dedicated servers that have enough power to house however many autoblogs I want to run. So all this stuff about trying to run under a shared host, if you want to deal with those headaches, you just will have to deal. As you have heard, a single autoblog can create enough server stress to get your account suspended/terminated. It all depends how you configure them, and everyone does this differently.
As for google and the registrar details, I cover that too. Nobody would ever find which domains belong to me. I put quite a bit of detail into the personas that carry each site. They all have their own contact details, emails, etc.
As for adsense.. remember that every site you put your pub on will be associated all together, regardless of all the various precautions I just cited. Build enough crappy/spammy websites and your pub ID will definitely be used to identify and deindex all your sites. So really if you are going to use adsense on various sites, it doesn't matter where you host them. Multiple accounts is always a good idea.
Hope this helps clarify what the fuss was all about.
Thanks for that.
One last thing how would I know if im on shared or dedicated server, im through blue host and cant see what resources my blogs are using, is it possible that a ban could occur or would they just throttle the CPU/bandwidith.
The hosting package you purchased would indicate if its shared or dedicated. The price difference is significant enough for you to notice. bluehost likely means shared.
You have no way of really seeing the systems resources, only the server admin does. When you are in shared environment, you can't see the havok your site is causing to the server, but they can. Depending on the hosting company you deal with, they respond in a variety of ways. Most just shut you down. My host provider doesn't do shared hosting, but they have never given me a hard time. Any complaints got forwarded to me rather than them shutting down my servers. Prefer that kind of relationship really.
In order to lower the stress on the SQL db i suggest using WP-DBManager Plugin, as for the CPU and RAM W3 Total Cache plugin works like a charm. Try them and you will see improvements. This way you can have many autoblogs without stressing the server too much.
Separate names with a comma.