Forum Moderators: open
XYZ is a trademarked company name. The company owns domain xyz.com
Their website www.xyz.com is not indexed by yahoo because it is written in aspx.
XYZ asked me to make the company somehow findable in Yahoo when searching for "xyz"
#1 in Yahoo for the keyword "xyz" is www.xyz.net
That's a "domain squatter", just a single page saying "we just registered this domain". No links in it, not even the word "xyz" (this does not sound like a good search engine should work but that's not the issue here)
www.xyz.biz is not taken. If XYZ registers it, I can upload a page with a link to www.xyz.com saying if you are looking for XYZ click here.
Is this a good idea?
Their website www.xyz.com is not indexed by yahoo because it is written in aspx
There is nothing inherent with .aspx (Microsoft .NET active server pages) that make them unable to be indexed.
Surely it must be a better idea to find out what is really stopping your .com site from being indexed, and fix that instead? It sounds more like that your main site is over-reliant on Javascript or a similar problem, but assuming that the problems can be fixed, you'd be much better off developing a serious-looking .com than a spammy-looking .biz domain.
/page.aspx?Idvariable=1&Idother=1
Search engine bots can cope with URLs with variables very well these days, but they all choke when seeing "Id" in the string. Why? Because the URLs look like they have session IDs - and because session IDs are unique for one session only, the bots won't follow them so as not to have broken URLs in the index. Bots can't distinguish between real session IDs and other URLs with "Id" in them. To fix the problem, you need to get the site reprogrammed to replace "Id" with something else, like "page" or similar.
Also, check your robots.txt file on the domain - often apsx sites serve up an error page with a 200 Found code rather than a 404 Not Found error. The bot will therefore try to decipher a html page as if it was a robots.txt (plain text file), fail miserably, and maybe decide not to index because it is unsure whether the robots.txt file permits it to or not. Quick fix: upload a blank file called robots.txt to the root directory. Long-term fix - make sure pages not found return the correct error code.
Hope that gives some clues as to why the site isn't being indexed.
It could be something that the server is returning that is causing the problem or something else.
Have you run the page through Bretts server header checker and the spider simulator to see what is being returned? That would be the best place to start.