Linkwheel Design - Still Relevant at all?

[Captain Midnight]

Take a look at this architecture...

hxxp://wwwDOTseoDASHbackDASHlinksDOTcom/link_wheelDOThtm

(sorry for the obscurity, the damn moderation system wont make the link work and it's hard to describe what I'm talking about if you don't look at it)

I think the separate Tiers are excellent, and probably would add 2 more video submission and video-article submission as well.

My questions are, how do you go about managing it going forward?

In other words, I have different categories that I need to post to. So one might be for a local dentist, another might be for a roofing company, etc.. I want a custom link wheel that resembles that but is also -easy- to manage.


There are 3rd party fat client tools that will connect to web2.0 properties to post content to, along with ping.fm, etc. but what's the best?


So 2 questions...

1) can someone create the above architecture for a reasonable amt and
2) I want to manage it going forward, posting content to it as I see fit to the various different categories.. but how? (w/o logging into each of course and by possibly using a "tool" that I can install).


Thx,
CM

 

[BassTrackerBoats]

You mean something like this?

​

 

[Captain Midnight]

exactly... multi dimentional and complex... so here's the real question.. how do you then manage that?

 

[BassTrackerBoats]

exactly... multi dimentional and complex... so here's the real question.. how do you then manage that?

You really do not have that hard a deal to manage it... just put everything into an excel sheet and add to each property using SB, videos, xrumer etc...

OR

build a bunch of them and have them pushing your site up from a lot of different angles.

 

[zebrahat]

If you don't want a complicated wheel that will take a spreadsheet file to keep track of, but one simple enough to re-use if you have a large number of sites to promote, try this much simpler and clear wheel:

Only 10 properties involved as a base back web, but with one open spoke on the wheel, so it's harder to trace the footprint. Most importantly, the wheel is not directly linking to the money site, but to some other (a-e) web properties, while remaining its basic design as a linkwheel. That way it's less noticable to G, and even if they do catch it, it's just the buffer a-e sites that get de-indexed.

 

[lostgringos]

the biggest problem with linkwheels is that you should be using unique proxies on each property to hide any footprints. And you need to find good ******** properties. This has to be done manually (use roboform for profiles). Not many people can figure this out. They end up discouraged.

@zebrahat exactly buffer sites work really well. But again even with them you should use proxies. Hidemyass is good for that. Just change the proxy each time you create a property.

 

[Captain Midnight]

the biggest problem with linkwheels is that you should be using unique proxies on each property to hide any footprints. And you need to find good ******** properties. This has to be done manually (use roboform for profiles). Not many people can figure this out. They end up discouraged.

So quick follow-up, to the purpose of using multiple proxies.

You use use multiple proxies because you're creating multiple accounts in the -same- web2.0 property.. correct? That's the only reason why I think that would be relevant.. right? Or is there another reason? (i.e. does your profile in each account have your signup IP and the big G will go deep to make the association?)

 

[Captain Midnight]

If you don't want a complicated wheel that will take a spreadsheet file to keep track of, but one simple enough to re-use if you have a large number of sites to promote, try this much simpler and clear wheel

I'm looking at the management of this system, so instead of connecting to each Web2.0 propertly, is there a way that each one can pull via an RSS feed from a primary 'master' site just the information relevant to that property?

In other words, let's say that each web2.0 property has multiple categories.. each one with very similarly named (dentist, local dentists, etc.). It would be ideal to have each propertly point back to somewhere else and feed it updates vis RSS from 1 location, in different categories (non-indexex at the source, etc.)

Possible? Is this how the more complex ones are being managed or is there software that's doing it? i.e SENuke?

Thx.

Keeping everything straight will drive me crazy, so I need to organize in an ocd way.

 

[elocin]

So quick follow-up, to the purpose of using multiple proxies.

You use use multiple proxies because you're creating multiple accounts in the -same- web2.0 property.. correct? That's the only reason why I think that would be relevant.. right? Or is there another reason? (i.e. does your profile in each account have your signup IP and the big G will go deep to make the association?)

I too am interested in an answer to this.