Note that there are some explanatory texts on larger screens.

plurals
  1. POSEO URLs with ASP.NET MVC
    primarykey
    data
    text
    <p>Is there a definite <strong>DO</strong> and <strong>DONT</strong> when implementing seo urls? A lot of good practise seems fine for .html sites but breaks down on medium/large database sites.</p> <p>AFAIK the url should be <strong>www.mysite.com/category/page-name-here</strong> </p> <p>If I wish to make a content rich site and be default the category and page are database driven - does this prevent me from having pages such as <strong>www.mysite.com/about</strong> or <strong>www.mysite.com/home</strong> as the about and home pages could conflict.</p> <p>Although the routing engine is flexible, is the above feasible and/or worthwhile?</p> <p>-edit-</p> <p>Just to elaborate on my question, is it possible to control the routing engine with a database?</p> <p>It is good practice for the url to contain a meaningful description - eg <strong>stackoverflow.com/category/mvc</strong> and <strong>stackoverflow.com/questions/seo-urls-with-asp-net-mvc</strong> is good (as opposed to <strong>stackoverflow.com/category/9955</strong> and <strong>stackoverflow.com/questions/734583</strong>)</p> <p>As an expirment, I would like to take the control to another level, lets say that the two controllers above (category and questions), each showing dynamic data could be amended to be simply <strong>stackoverflow.com/mvc</strong> and <strong>stackoverflow.com/seo-urls-with-asp-net-mvc</strong>. </p> <p>I would need to ensure that my database contained a table that tells me that the former is to be routed as a category and the latter as a questions - this could be achieved by a simple database lookup and would need to be implemented within Global.asax</p> <p>My question is, can this be achieved and what would be the potential pitfalls. </p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload