Forum Moderators: Robert Charlton & goodroi
For example is the the same for me to link:
www.domain.com/page
and
www.domain.com/page/
(page is either page or directory)
I just want to know will google give points to "page" despite of the way it is linked. It wouldn't be cool if it would tread page and page/ separately, on that way it'll be lacking of PR, which mixed would be greater than separate with each page and page/.
So do you know the accurate answer of this question?
Thank you,
Manca
www.example.com/example/ and NOT www.example.com/example
I think the only difference would be that in the latter, Google could think example was a page (e.g. www.example.com/example.html or something like that), especially if there was a page in that folder named that...
IF you had this: www.example.com/index and you had a default page in that folder named index.html I could see where you might run into problems with that... of course the browser would show the index page, but I would rather be on the safe side and add a /.
I am, however, not an expert and just giving you MHO.
There is some interaction with URLs without the trailing / on them.
If you decide to base your site on www.domain.com and if the default server name (a server setting) is domain.com, and you have a 301 redirect from non-www to www, and all your internal links go to www.domain.com/folder (WITHOUT the trailing / on it) then the server will FORCE an internal 301 redirect to domain.com/folder/ (WITHOUT the www on it) before your own redirect kicks in to then do another redirect to www.domain.com/folder/.
This is very bad. You now have a redirection chain and you now have domain.com URLs in the chain. This is often easy to spot when you run Xenu LinkSleuth over your site: it reports double the number of pages that you expected (in the sitemap part of the report), and half them have a title of "301 Moved".
Check it. It is very important.
Fix it. Failure to do so will cause many problems.
I first highlighted this a couple of years ago. It is even more important to get this right on the "new Google".
All my internal links point to domain.com/folder/ with / in the end of url. The thing I wanna know is it good to have external links link to domain.com/folder or folder/? I mean, can it cause some problems with google because folder might get different PR than folder/ or it doesn't matter? Google should see them both as the same thing (when doing GET request)..
What do you think about it?
Thanks for the answer g1smd, tho!
It avoids the server having to issue yet another redirect before serving the page.
I'll make sure to have all my links poiting to page/ .
Let's say I have my pages automatically "generated" with wordpress...Those are of course urls from DB, but I made them look pretty with mode_rewrite stuff...Do you and Google consider those pages (perm links) as pages or as folders?
For exmaple wordpress make post like?p=10 and with mod_rewrite it looks like post-ten.
Does big G consider those as pages or as folders, and do I have to link to them with / at the end of url or not?
THANKS A MILLION!
Does big G consider those as pages or as folders, and do I have to link to them with / at the end of url or not?
G consider them as URLs. An URL is an URL.
Only you and your server know if a specific URL is a folder (with some default index-file inside) or not.
If it is a folder, add the trailing slash to the URL, if it is not, do not. Do this consistently and everything will be fine.
If your server is forced to send out a 301 redirect to make the client aware that he should have requested "url/" instead of "url" and instruct him to try again accordingly, this is unnecessary and therefore should be avoided as it is an additional interaction/transaction that will slow down the retrieval of the URL.
G sometimes seems to have problems in attributing redirects correctly. So doing this linking right in the first place surely will do no harm.
Kind regards,
R.
I do have my dedicated server and my domain and have WP installed there...I DO NOT see any single problem with WordPress...
