Domain.com/postname vs. Domain.com/blog/postname

[nm1977]

I am wondering what is the best practice regarding blogs?

I read that it would be best to structure a website like a pyramide instead of a flat panckage

But I have seen many blogs where the post shows right after the domain name.

Domain.com/postname instead of Domains/blog/postname

My point is that if a website has many post then the structure will get very flat and this will maybe make your most optimized and important pages less important to google domain.com/page

a) What do you think about this, which one of the two blog solutions do you prefer and why?

b) in context to blog

If for instance you had a keyword like Copenhagen property would you then consider renaming your blog to

realetateagent.com/Copenhagen-property-news/post-name

c) Would write a little intro like 200 words for the page 1 of your blog and add in some keywords.

[DougRoberts]

On the topic of whether to put all your blog content under a /blog folder or not. I'd normally recommend it just so that you can easily segment the blog section of your site in Analytics. If you don't it's tough to see how your blog is performing separately from the main site and it's not always obvious what is a blog post and what is a service/resource/support page. Visitors who enter the site via blog posts usually have less commercial intent.

[RyanPurkey]

Thumbs up to Doug. This is also what I said in one of your earlier posts, "D) Adding the blog folder is fine, and helpful in a lot of cases (when you just want to analyze the blog separate from the website, for example). Cheers!"

[nm1977]

Hi Ryan,

yes its a very good point, I agree with you the point about analytics.

I just also really wanted to know peoples thoughts about pancake vs pyramid structure. Will the many blog post after the domain.com/ make other pages less significant

how about B and C what is your opinion should the blog page be optimize in such a way?

[MoosaHemani]

I think the setting of the URL is very much depends upon how you are taking your website and how deep is it. If you ask about my website, my main goal is to offer free education to the readers and then there are service pages so I thought it would be fine to go with the direct approach as my service pages are limited.

My URL structure is: http://www.example.com/direct-page

But if your website is deep then making divisions make sense like services/name or blog/post-post

b) I think the division should be basic and not very deep as this will hurt user experience.

c) I really didn’t understand this part but if you mean a text before read more is bad so the answer is NO!

hope this helps!

[nm1977]

Thanks for answer.

B) With this one i ment should i rename the name of the blog to a keyword i target.

Copenhagen-property-news instead of Blog ....copenhagen and property is not already part of my domain name.

C) yes i ment to add like 200 static wordsand a h1 on top of the blog post page, Instead of just having the first posts

[Mark_Ginsberg]

Regarding B), one thing to consider is whether redirects will help or hurt your site.  Even websites that are appropriately redirected lose some link equity in the process.  See Matt Cutts' video here which says that roughly 10-15% of PageRank is lost through redirects and outgoing links.  Therefore, if the site has existed using the format domain.com/post-name for a long time and attracted links to those URLs, then the small benefit you get from adding the keyword to the URL may be outweighed by the natural loss of link equity.

For C), an introductory blurb could help, but make it good quality content, not just for keywords.  Especially since this text will push down the actual blog posts, it needs to be worthwhile for people to read or it could increase bounce rate.