Question
Changing to descriptive-style URL
Currently, a site that I work on uses non-descriptive url's
in the content pages we publish, such as:
/column/index.cfm?columnID=8864
While keeping all of the content database driven, and still using common templates for the publication of
the content, I have been instructed to change the url to a more
descriptive style, such as:
/reviews/pirates_of_the_caribbean_2
with the hope that such a change will make pages more attractive to search engines, thereby increasing
traffic.
Solutions that I've come up with:
-write a physical page for each content page. (This is the first thing I thought of, but rejected it immediately)
-use a custom 404 page to parse the url and then load the correct template with the corresponding database entry.
This was my second solution and would probably work, but it seems like it would create an awful lot of overhead.
-When the page is published, automatically create a directory with the desired name plus a index.cfm file
underneath that directory (cfdirectory and cffile)....the index.cfm file would call the common publishing template....or the
index.cfm file could basically be blank and the application.cfm could handle the template loading. So in effect,
we'd still end up with a directory for every content page, which would add a lot of clutter, but the content could
still be generated centrally
Any other suggestions as to how to implement this change?
/column/index.cfm?columnID=8864
While keeping all of the content database driven, and still using common templates for the publication of
the content, I have been instructed to change the url to a more
descriptive style, such as:
/reviews/pirates_of_the_caribbean_2
with the hope that such a change will make pages more attractive to search engines, thereby increasing
traffic.
Solutions that I've come up with:
-write a physical page for each content page. (This is the first thing I thought of, but rejected it immediately)
-use a custom 404 page to parse the url and then load the correct template with the corresponding database entry.
This was my second solution and would probably work, but it seems like it would create an awful lot of overhead.
-When the page is published, automatically create a directory with the desired name plus a index.cfm file
underneath that directory (cfdirectory and cffile)....the index.cfm file would call the common publishing template....or the
index.cfm file could basically be blank and the application.cfm could handle the template loading. So in effect,
we'd still end up with a directory for every content page, which would add a lot of clutter, but the content could
still be generated centrally
Any other suggestions as to how to implement this change?
AdChoices