Yakezie.com - Topic: Page vs. Post

Andi B. on Page vs. Post

Tue, 14 Feb 2012 22:21:22 +0000

So I had this genius idea to design it as a page and as a post to see what worked best and.....post won. Since you can't tag pages, it had to be posts to make it more searchable.

money cactus on Page vs. Post

Fri, 10 Feb 2012 03:42:32 +0000

Pages are good if you want to keep the content easily accessible as you can add it to the front page more easily, I think that there is some argument for the SEO benefits too. saying this, you might be better to break up recipes into individual posts, it will give your site a lot more size.

Eric - PersonalProfitability.com on Page vs. Post

Thu, 09 Feb 2012 14:02:53 +0000

I like Khaleef's idea best. Write them as posts. Pages should be used much less often.

Andi B. on Page vs. Post

Thu, 09 Feb 2012 12:21:48 +0000

retireby40 said:

Andi B. said:

I think I'm just nervous because over the next few weeks I'm going to be dropping almost 300 recipes on my website. I didn't want to blitz my readers.

Wow, that is A LOT of recipes. Maybe you should slow it down a bit?
I like the category idea too.

It is, but it's needed for the business aspect of my site. Our meal plan subscribers need to have extra seasonal recipe options. I'm not dumping them all in one day, but still....it is a lot.

retireby40 on Page vs. Post

Thu, 09 Feb 2012 12:13:38 +0000

Andi B. said:

I think I'm just nervous because over the next few weeks I'm going to be dropping almost 300 recipes on my website. I didn't want to blitz my readers.

Wow, that is A LOT of recipes. Maybe you should slow it down a bit?
I like the category idea too.

Andi B. on Page vs. Post

Thu, 09 Feb 2012 11:30:06 +0000

I think I'm just nervous because over the next few weeks I'm going to be dropping almost 300 recipes on my website. I didn't want to blitz my readers.

JP on Page vs. Post

Thu, 09 Feb 2012 11:10:49 +0000

If you go with pages, there is a wordpress plugin that will include pages in your RSS feed. I've used it for some time now. Make sure to deactivate it for pages you don't want to send your subscribers.

Khaleef @ KNS Financial on Page vs. Post

Wed, 08 Feb 2012 17:08:35 +0000

I would suggest that you write each recipe as a post, and then create pages based on tags, categories, or however you want to group them. I use a plugin called "page post associator" to do this.

For instance, my "taxes" page: http://knsfinancial.com/taxes/, is a picture, a couple of paragraphs of text, and then each article in my "taxes" category.

I do the same for my push ups challenge page as well.

BeatingBroke on Page vs. Post

Wed, 08 Feb 2012 12:10:25 +0000

My personal opinion would be that it's all about structure. If you set up the category structure so that it's easy enough to find a recipe, then posts might not be so bad. The same could be done with nested pages, but it's a little more work in the backend to get it all set up properly.

Other things to keep in mind: pages generally don't go into the RSS feed, so you'll lose some without the post to point to the recipes. As long as you have some sort of search on your site, you should be able to overlook some minor structure faults.

Daisy on Page vs. Post

Wed, 08 Feb 2012 11:40:50 +0000

I would do a post :) They're easier to search - ie, if I'm looking for a recipe, I don't have to weed through other recipes to get to it. Do you know what I mean? I don't even know if that's very clear, haha.

A few of my favorite recipes have come from blog posts

Andi B. on Page vs. Post

Wed, 08 Feb 2012 11:13:21 +0000

I was wondering when the best time to write a page is vs. a post? We're looking at adding quite a few recipes to our website, and I was more inclined to make that a series of pages instead of posts, but I'm worried I won't get the link/subscriber juice from it.

Another option was putting the recipes on pages, and then setting up weekly, our favorite recipes posts that would link to them and others.

Any ideas?