WordPress Development Stack Exchange is a question and answer site for WordPress developers and administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Since the post_id is unique and no full text search is needed.

So is the structure %postname%/%post_id% really improve performance?

share|improve this question
up vote 1 down vote accepted

I hate to answer this with a link, But with WordPress 3.3, how it searches for permalinks have been greatly improved so you can almost put anything into the permalinks and it will be fast.


share|improve this answer

If by performance you mean SEO wise - the answer is it really depends.

My permalinks are set to use date and day in the permalinks. When user searches for "web design list 2011" - the 2011 in my url gives me an added advantage of coming up.

So if your id significantly enhances your product name or blog article - this may help in search. Otherwise it is in particular not required.

share|improve this answer

So is the structure %postname%/%post_id% really improve performance?

Over what? Although the performance gain is very very very slight (i.e. very very negligible), there are obviously better permalinks for performance.

  • Nothing beats the default permalink structure: http://example.com/?p=123

  • But I am sure, you want %postname% in there. So, the next best choice would be /%year%/%postname%/%post_id%/ (for instance, http://example.com/2012/post-name/121/)

This question has more insights — my insights. ;)

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.