Hello,
Recently we migrated to new servers and I had the opportunity to review all of our Alias/Vanity URLs that have accumulated over time.

Previously these Alias requests would be implemented no questions asked, but clearly they need to be managed more closely.

An example of how these alias would accumulate... Our marketing department would request 30...40..75 aliases at a time to track traffic from different regional print ads.

I've since thwarted such requests with more sensible solutions like coupon codes to track the success instead of traffic to an alias.

However, my question is what if any "rules of thumb" are there for URL Alias life-cycles? What criteria define an acceptable reason to implement a URL Alias.

Thanks for the feedback!

[edited by: Apharcyde at 5:18 pm (utc) on Feb. 25, 2009]