I have read the comments that suggest that it is not a good idea to put HTML, etc into the Application.cfm file. But I don't see a compelling argument as to why this is preferred.
Is it strictly a good organizational habit, or is there a valid technical reason for leaving HTML out of Application.cfm?
Would the same "rule" apply to OnRequestEnd.cfm?
If I explain to my 'customers' that there is additional overhead involved in having the server fuss with the META tags on each and every page, I may very well be making a valid technical argument, but if the customer thinks that SEO is improved by easier management of the keywords, etc, and that it may very well help to optimize search engine placement (at the cost of fractions of a second per load), I am pretty sure that most of them will say to have at it and put the META tags in Application.cfm.
My take is that if I set up separate META tags on each and every page, the META tags are STILL loaded with every page request, so server load seems moot.
What MAY be a valid argument is that the search engines filter out sites that blast the same META tags on every freakin' page of their site, therefore it is better to optimize those keywords for each page separately.
Again, I am NOT picking one side or the other. I am seeking out advice. I am thankful that this is not being considered off-topic, because I am sure every CF programmer must face this situation.
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
