Jump to:
| Project: | Short URL |
| Version: | 6.x-1.x-dev |
| Component: | Miscellaneous |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Issue Summary
We're considering building our own shortener to use in conjunction with a city.net website we operate. The domain itself is pretty short (5 chars) and we're trying to decide whether or not to just use the primary domain or to secure a 2nd domain.
Just wondering what the community has to say - are their any issues that could come up with using our primary domain as the shortener? I haven't operated a url shortener before and am just wondering if this could raise any issues as to SEO, scalability, etc. We don't plan to open it up for public use.
On the positive side, using our primary domain would be really good for branding ... but I'm having this possibly unwarranted instinct that it might be good to operate the shortener on a 2nd domain.
Thoughts anyone?
Comments
#1
Personally, I would opt to use a domain hack (i.e. goo.gl, nyti.ms etc..) that sounds / looks similar to your domain and then run it as a multisite install. That way you kind of get the best of both worlds.
#2
Subscribe. Wondering the same thing and "worried" about branding myself. And this would be for a shortener that is open to external (Internet) users.