Prevent twitter from shortening URLs
http://www.seoconsultants.com/uris/conversion/
If you've really got all your ducks in a row, your URIs will be short to begin with. You'll have followed the suggestions made back in the early 90s that URIs should be concise and never change. Planning for that type of scalability is a bit challenging and definitely has its long term rewards.
If your ducks are a bit disorganized, and you have long unruly hyphen and/or underscore laden URIs, then you'll have some challenges implementing a branding effort in this area particularly at the deeper levels of your click paths. You could roll your own URI shortening routine.
* URI Short: http://www.SEOConsultants.com/Clicks
32 characters
Will visually truncate in Tweet at 30 characters http://www.SEOConsultants.c...
Twitter Search shows the entire URI without truncation
* Permalink: http://www.SEOConsultants.com/S/E/O/C/o/n/s/u/l/t/a/n/t/s/D/i/r/e/c/t/o/r/y/
76 characters
Example: http://twitter.com/pageoneresults/status/1516562582PermaTweet: http://twitter.com/pageoneresults/status/1516562582
for a user-driven web site with lots of content, the former approach is not very practical. For a Drupal site, implementing its own URL shortener
URIs must be clean and without any word separators like hyphens or underscores (after character position 30). Hyphenated words, concatenated words or single word file paths using a slash as a separator work well. Keep in mind that once your URI reaches 31 characters, it will automatically truncate. If you have exactly 30 characters, it will remain fully visible within the Tweet without truncation. Once you reach character 31, truncation occurs and the URI gets trimmed to 27 visible characters and three dots ... (ellipsis), 30 total. The anchor reference remains intact but the visual shows truncation.
Comments
Post new comment