ways to link pages in a website

[aasif0670]

I am totally new to any fourm and webdesigning stuffs ,but i am still trying to make most of it...

what i want to know is that if i have a website say www.yoursite.com and subpages and images are ##page1 and ##sss.jpg respectively.
now if i link the pages from my index page....

could i fill in the whole path like www.yoursite.com/##page1.htm or just specify /##page1

which of of these options will the spiders of the search engine take in order for my site to be index?

I have tried the later and spiders of all the search engines just visit the index page and leave without indexing my site for the past 4 months. This is the only doubth i have as to why they are not indexing my site.

Please advise

[adore]

Both types of urls don't make any difference to spiders - they are able to index pages by following both relative and non-relative urls.
I think that there is another problem - your page has PR = 1 which is very low and that's the main reason that spiders rarely index your home page and even more rarely are willing to index deeper.
Get more links pointing to your site and soon you should see your whole site in the index.

[Mel]

IMO it is safer as a rule to use fully qualified URLs, - I have seen too many problems arising from the use of relative URLs to trust them.

[steveteva]

How do I check all my website links that have been spidered by google and indexed. I ve forgot the command to type in google search box to get this result.
Anyone can help me ?

[kikkertm]

site:www.tools4webmaster.com

[ronniethedodger]

Originally Posted by Mel

IMO it is safer as a rule to use fully qualified URLs, - I have seen too many problems arising from the use of relative URLs to trust them.

You are probably right on that Mel, "virtual" urls as they are called are handled by the Server and some of them may not handle them too well.

From a spider viewpoint, it does not matter as long as they can find the page and not get a 404.

Generally the best virtual address you can use would be from the root, most if not all Servers have no problems with this type. (example: href="/directory/filename.html"). This is an easy calculation to do for any server, in that it bases it's calculation of the url on the root address. It is nothing more than a mere addition problem basicly.

The problems arise in referencing forwards and backwards from the current document directories with such forms as ../ or ./../ and even the simple referencing from the current document directory (such as href="directory/filename.html").

Older versions of Apache had this problem in it's day, especially if it was severely burdened or tasked at the time of the call for the referenced file. I think it is not that much of an issue any more with the newer versions. And I am not sure about any of the IIS servers.

If you are using such programmin languages as .php or .asp, it would be a simple thing to parse files to output Html that would include a fully qualified path to referenced documents or images.

If you are coding pages in regular Html though, it can be counter productive to maintain a large site without using virtual paths in your references. If you move files from one directory to another or use them as templates to create other files in another directory of a different name, then you will be constantly searching and replacing your absolute addresses. They are not easily movable and become cumbersome to work with.