| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 12093 | 2001-10-15 09:48:00 | http:// alone, (no www) is able to be indexed by engines? | Guest (0) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 21507 | 2001-10-15 09:48:00 | I Have just got a free hosting site with a subdomain, but access can only be achieved through http://subdomain.domain.net, not www.subdomain.domain.net Does the lack of www access mean that search engines will not be able to index it? Thanks |
Guest (0) | ||
| 21508 | 2001-10-15 10:30:00 | Search engines should be able to find it just fine without the www there. | Guest (0) | ||
| 21509 | 2001-10-15 10:55:00 | subdomain.domain.net and www.subdomain.domain.net are actually different addresses. | Guest (0) | ||
| 21510 | 2001-10-15 19:43:00 | Just go to www.altavista.com and submit your webpage address, it will take up to a week to appear though. | Guest (0) | ||
| 21511 | 2001-10-16 06:28:00 | The domain name fred.something.something is resolved by a nameserver to something like 199.123.012.33 ;if it is a web server, containing html it will have a port number, usually ':80' at the end. http:// tells you browser to use HTTP. But the name is just that, something easier to remember than the 32 bit internet address expressed as 4 decimal digits as above (soon to be 128 bits in IP6). The system knows ... FTP and HTTP servers can be running on the same physical machine, with the same address, but on different ports, and two (or more) names will be registered at the nameserver (eg www.fred.org=123.123.123.212:80, and ftp.fred.org=123.123.123.212:21). But the names are arbitrary, and not what the system uses; they help people. Or not. |
Guest (0) | ||
| 1 | |||||