Forum Moderators: Robert Charlton & goodroi
Do i really need to worry about these?
What happens if i just disregard them?
...how do i handle these, just make a lame index.htm page in that folder?
Me, I put a blank index.html page in the images directory anyway, just on the general principle that nobody needs to see a directory listing of every file in the directory. Actually, I try to do that for most of my directories that don't contain html or php files; I just have a hard time remembering sometimes.
google is not punishing you for this, they should not even be calling the 'folder' unless you have a link to it for some reason?
you can turn off directory listing at the server level - most control panels will allow you to do this.
anyway, the index.htm that you may put into that directory, do you have it redirect or refresh to another page?
i dont have a "control panel" to work from unfortunately from my hosting company, but im pretty sure directory browsing is already turned off....
Either have a page of content - links to other parts of the site, or have no file at all.
"You do not want to be redirecting index pages anywhere else within a site."
As i took over this site about 4 months ago, the previous webmaster told me about some page redirects we had on the site. I said ok, no problem.
As i started looking daily at my Google Webmaster Tools, i found that my list of 404 Page not found errors, was growing exponentially.
So i decided to fix them. These are old pages that used to exist on our site in 2000, 2001, and years back.
most of these were file names such as
"oldOne.html" or "usedTobeHere.htm"....etc. I know have those pages refreshing to a more current page on my site via meta tag.
Now, some of the page not found files were ASP.
AND....the way the file structure was set up, all of the pages are index.asp. (i.e.)
instead of this URL: [ourcompany.com...]
you would see this URL: [ourcompany.com...]
because the file in the folder was called index.asp
which i now use a 301 moved permaneently to redirect to a more current page?
now you are telling me this is wrong?
And yes, it is always best to omit the index file filename from any link that calls for it. Just end the URL with a / at the end.
What I was referring to is when you access www.domain.com/ and are instantly transported to www.domain.com/newsite/finalversion/blahblahkeyword/index.asp/documentcontrol&af15e527b316
3ce2ae2f8ea0/contentmanager/showfile=62843&do=show&start=0.
Now that is always a bad idea.
.
For files that are long gone I rely on the custom 404 error page to supply a page of useful navigation links to get the visitor on their way to the correct part of the site.
Now for your custom 404 page error....unfortunately i am on a Windows Server, and i have not form of GUI interface control panel to adminsiter the server...
IM using classic ASP....
do you know how i can create my own custom 404 pages?
everytime i search this, i only come up with answers that tell me how to do it via IIS...which i have not access to.
thanks
