jaswrks
commented
9 years ago It would also mean that as long as the Redirect Source URL (the Redirect permalink) doesn't change, the Bitly URL will always redirect to whatever Target URL is configured in WP Redirects; if the Target URL changes, the Bitly URL would still work.
That sounds perfect to me!
It would be nice to be able to integrate with Bitly. There are two ways this could work:
Shorten the Target URL with Bitly and offer the Bitly URL in place of the WP Redirects-generated Source URL (i.e., the redirect permalink).\
This would mean WP Redirects would be bypassed entirely, with people visiting the Bitly URL going straight to the Target URL--WP Redirects wouldn't be able to maintain any stats and really wouldn't be serving as anything more than a Bitly-generator and a collection of Bitly URLs.
Shorten the Source URL with Bitly and offer the Bitly URL in addition to the WP Redirects-generated Target URL.
The Bitly URL would just be stored as a Custom Field on the Redirect and would become another way of referencing the redirect. By pointing Bitly to the Source URL, someone visiting the Bitly URL would go
Bitly → WP Redirects Source URL → Target URL. While this means an extra "hop" from the visitors perspective, it would also mean that basic WP Redirects stats are collected along with the more comprehensive stats collected by Bitly.It would also mean that as long as the Redirect Source URL (the Redirect permalink) doesn't change, the Bitly URL will always redirect to whatever Target URL is configured in WP Redirects; if the Target URL changes, the Bitly URL would still work.
The latter is my preference. Any thoughts @jaswsinc?
Forked from: https://github.com/websharks/wp-kb-articles/issues/64#issuecomment-76355640