I am wondering about the relevance of what Google sees as the actual filename in a link. For example, on a scripted site the url structure might be: Code: /path/subpath/scriptname?querystr Consider for a moment that although the path is completely unique for each link, the scriptname is the same. That is to say one script is handling the bulk of the traffic. The querystr tells the script what to do. The path indicates site structure.
script name vs path
11
I am wondering about the relevance of what Google sees as the actual filename in a link. For example, on a scripted site the url structure might be:
Consider for a moment that although the path is completely unique for each link, the scriptname is the same. That is to say one script is handling the bulk of the traffic. The querystr tells the script what to do. The path indicates site structure.
I am thinking this may be disadvantageous and that in some cases the scriptname should be where the keywords are.
For example, consider the following two urls:
Wouldn't google prefer the scriptname that contains the keywords? If one scriptname is used for the bulk of the load on a dynamic site doesn't that muddle the issue somewhat?
Is it worth restructuring the script(s) to reflect a name that suits the content?
Code:
/path/subpath/scriptname?querystr
Code:
For example: www.domain.com/products/mywebsite.php?querystr or www.domain.com/search/mywebsite.php?querystr or www.domain.com/contact/mywebsite.php?querystr
For example, consider the following two urls:
Code:
/products/dresses/green/getproducts.php?querystr or /products/green-dresses.php?querystr or even maybe /products/clothing/dresses/green-dresses.php?querystr
Is it worth restructuring the script(s) to reflect a name that suits the content?
- MightyWarrior
- [ 1 ] Thanks
- [1] reply
- Steviebone
- [1] reply
- Steviebone
- [1] reply
- savidge4
- earmarkseo
- [ 1 ] Thanks
Next Topics on Trending Feed
-
11