Need advice: .net is indexed...now the .com is being indexed

what do I do?

[walkman]

The .net has been indexed for a while...a page here and there and I get about 300 or so visitors a day. Now the .com is being indexed by slurp. I can't afford to lose those 300 users, but I rather have Y! index the .com site that's the one with the backlinks and hopefully I get more visitors.

What do I do? What will happen once Y! realizes that the pages are identical to those already indexed? The only resason I left the .net pointing to the .com is becuase it was indexed and the .com wasn't. Do I at least make sure they have the same IP?

any thoughts, ideas?

[outland88]

If the .com is being indexed wouldn't that be an indication to you duplicate content is not being penalized? If the .net was indexed with fewer links and the .com with more links wasn't being indexed very well what would be your conclusion? Are you on the same server now?

[walkman]

"If the .com is being indexed wouldn't that be an indication to you duplicate content is not being penalized? If the .net was indexed with fewer links and the .com with more links wasn't being indexed very well what would be your conclusion? Are you on the same server now? "

well, maybe they're just scouring, without actually analyzing it. Same server and I had a many years old penalty on the .com. Months later I notice traffic coming from the .net.

I think they have different IPs too...since the .net and the rest of secondary names have the server default IP and the .com has it's own, dedicated IP.

?

[walkman]

what's the latest word on Yahoo and 301? ...they were having issues. Will it cause any problems?

[DaveAtIFG]

I still haven't seen any issues, both before YST with Ink/PFI/PositionTech, or after the YST deployment.

301s that I've implemented in the past 3 months are spidered and indexed according to Yahoo's erratic schedule, but what eventually gets indexed is exactly what I expected.

[walkman]

"301s that I've implemented in the past 3 months are spidered and indexed according to Yahoo's erratic schedule, but what eventually gets indexed is exactly what I expected. "

Dave, would you 301 the .net to the .com?

[DaveAtIFG]

The 301s I've implemented have all been "site maintenance" issues, moved pages within a site/domain. Since I have no recent experiences redirecting between domains, I can only guess at the effects.

That said, I'd redirect .net to .com... You're gonna be forced to do it eventually anyway... It's better done now, before you acquire major traffic I think.