WordPress.org

Ready to get started?Download WordPress

Forums

[resolved] Latest regarding pretty permalinks and performance? (6 posts)

  1. Charlotta
    Member
    Posted 3 years ago #

    In the WordPress codex the advice is to NOT use website.com/post-name as permalink structure because of performance reasons. It is a very popular usage however, and I saw in a comment on some blog that as of WordPress 3.0 it is not a problem anymore to use such a structure. The commenter said that the codex hadn’t been updated though.

    I have tried to search for “3.0” and “permalink” but I don’t find anything. What is the current status, some-number/post-name still better than just post-name?

  2. esmi
    Forum Moderator
    Posted 3 years ago #

    The commenter said that the codex hadn’t been updated though.

    That commenter doesn't know what s/he is talking about.

    http://wordpress.org/support/topic/423072
    http://ottopress.com/2010/category-in-permalinks-considered-harmful/

  3. Charlotta
    Member
    Posted 3 years ago #

    Hi esmi, thanks for the answer. OK, so the advice is still the same?

    Makes me wonder though, all the popular blogs which gets loads of traffic and use the site.com/post-name structure. Is it because they use cashing that it’s not so critical? As a visitor of such a site you don’t really notice any performance issues.

  4. esmi
    Forum Moderator
    Posted 3 years ago #

    The advice is still the same - for improved performance, start your permalinks with a numeric. Whilst some of the larger blogs on dedicated servers with lots of caching etc might be able to get away to non-numerics, the average site on a shared server may not be so lucky.

    I've always used one of the pre-sets and I've never had a problem with Google placement.

  5. Charlotta
    Member
    Posted 3 years ago #

    Thanks for answering!

  6. bobcatou
    Member
    Posted 3 years ago #

    I still get so many conflicting answers on this question. It the Ottopress link above, it appears that one of the commenters say that Version 3.1 has now fixed this issue and the author isn't disagreeing or isn't arguing. I'm feeling like I should be safe than sorry on this issue but it would be nice to just use the postname.

Topic Closed

This topic has been closed to new replies.

About this Topic