These are in tension.

[kexej28769@nongnue]

There are a few main ways to structure your URLs. You can have a subfolder type structure or a much flatter structure where everything is collapsed into one level. There are pros and cons to different ways of doing this, and there are lots of suggestions. You're generally thinking, in general, it's better to have short URLs than long URLs, but it's also better, on average, than not having your keyword there at all.

So there's a little bit of art that goes into vietnam number data good URLs. But often I see people, when they're really trying to suggest information architecture, end up talking about URL structure, and I want to kind of tease these things out so we know what we're talking about.

So I think the confusion arises because both of them can involve questions about what pages are on my website and what the hierarchy is between pages and groups of pages.

Questions URL

So the pages that exist are clearly a question of URLs at some level. Literally if I go to /shoes/women, is that a 200 status? Is that a page that returns things on my website? So, at its most basic, a URL question. But zoom out a little bit and tell me what the set of pages is, what the groups of pages are on my website, and that's an information architecture question, and specifically, how they're structured and how those hierarchies come together is an information architecture question.

But it's muddled by the fact that there are hierarchy questions in the URL. So when you're thinking about your red women's shoes subcategory page on an e-commerce site, for example, you could build it like this or in a flat way in a subfolder structure. That's just a pure URL question. But it gets muddled with information architecture questions, which we'll get to.