short file names (t.php instead of showthread.php)

ooo

Member
may be it make direct urls (without rewrite) nicer if main files will be short

/u.php?id=522 instead of /user.php?id=522
/u.php?522 instead of /user.php?522

/t.php?t=463 instead of /thread.php?t=463
/t.php?463 instead of /thread.php?463

etc.
 
Upvote 0
I agree with feldon30.

Whether it's better for performance reasons or not, showthread.php looks more appealing than t.php.

Mind you this is a inutile point as Mike has said that the system doesn't work that way.
 
I think in most MVC distributions I've seen, the controller name is the rewritten "directory" name, such as "threads", but it probably doesn't matter for this thread context.
 
The only benefit here is a shorter link to share with others.

blahblah.com/forum/users.php?userid=12
vs
blahblah.com/u.php?u=12

First one is more likely to get trimmed or goes through "force space after 80 characters" filter, etc.

Which is why I am kinda hoping we potentially see support for shortning services ;)

Example: This thread
http://xenforo.com/community/threads/short-file-names-t-php-instead-of-showthread-php.3477/
vs
http://xenfo.ro/3477

The latter being great for linking, social services, etc. And just fine as a permalink on a board.
 
Right, but how does that affect SEO? Seems like the effect could be considerably adverse, since the microlink would be utterly undescriptive as to content.

The Microlink would auto 301 redirect to the correct content so the final destination would have the descriptive content etc.
 
Right, but how does that affect SEO? Seems like the effect could be considerably adverse, since the microlink would be utterly undescriptive as to content.
It would do nothing. It's just for ease of use, convenience. SEO won't matter, as the original long url is the result of the 301 redirect, and has the canonical url in the header.
 
The only benefit here is a shorter link to share with others.

blahblah.com/forum/users.php?userid=12
vs
blahblah.com/u.php?u=12

First one is more likely to get trimmed or goes through "force space after 80 characters" filter, etc.

Which is why I am kinda hoping we potentially see support for shortning services ;)

Example: This thread
http://xenforo.com/community/threads/short-file-names-t-php-instead-of-showthread-php.3477/
vs
http://xenfo.ro/3477

The latter being great for linking, social services, etc. And just fine as a permalink on a board.
It would do nothing. It's just for ease of use, convenience. SEO won't matter, as the original long url is the result of the 301 redirect, and has the canonical url in the header.
Could you send me a link to something explaining more in depth what you are talking about here. Possibly a post if you have made one already. Sounds interesting and it created a possibility in my head and would like to read more to see if what I'm thinking of is actually possible to do.
 
Right click the page here, view source. From there you can find this:

<link rel="canonical" href="http://xenforo.com/community/threads/short-file-names-t-php-instead-of-showthread-php.3477/" />

Any change in the url, such as changing from:

http://xenforo.com/community/threads/short-file-names-t-php-instead-of-showthread-php.3477/

to:

http://xenforo.com/community/threads/twice-a-day-i-brush-my-teeth.3477/

or

http://xenforo.com/community/threads/3477/

or

http://xenfo.ro/3477

Will all 301 perm-redirect back to the original source.

The original source has canonical url link in the header of the page.

Telling the browser, the user browsing it, and the search engines, that it is the original source, and that while a shortning url might be popular (imagine 500,000 times linked). It won't be counted as dupe content, as the source is 301 perm redirected to the canonical url.

Ergo, has no effect on SEO.
 
Top Bottom