Using Pages instead of Posts
- Thread starter Sulphur
- Start date
- Sep 7, 2017
- 7,167
- 6,415
It wouldn't help or change anything. There are things I want on pages while others on posts.
For example, on one of my sites I'm hosting a tool(a plugin) on a page instead of a post. it's ranking and bringing in traffic.
Kinu Actaz
Elite Member
- May 13, 2020
- 2,266
- 1,441
You won't see any change since your posts are also considered as pages in the eyes of search engines.
- May 2, 2010
- 9,966
- 16,076
I use both, I use pages to display information about a section or silo (been using this setup since @splishsplash mentioned silos in the 1600s, lol), and then I link from the page to the blog post category as a specific container. It makes for a nice site, as you can make these pages strong starting anchor pages for your posts.
dandan594594
Elite Member
- Jan 31, 2013
- 1,664
- 1,238
Using 100% pages only makes sense if your creating a silo, and need to keep a tight URL structure. ie; Building a hierarchy with parent and child pages.
Ecom and local sites, targeting lots of products variations or geos, can benefit from a page only approach.
Ecom and local sites, targeting lots of products variations or geos, can benefit from a page only approach.
ifcmd
Registered Member
- May 28, 2022
- 76
- 42
Doesn't make a difference, since the url structure is most likely be
I like to keep majority of them as posts, but then if there's any clear silo being created. Create them as parent/children Pages, so it's nested as
Helps with organization in the backend, but that's just for us as the owners.
/%postname%/ they'll have the same URL slugs structure.- The sitemap will separate them as different .xml files, but this doesn't make much of a difference either since the main sitemap links to all .xml files.
I like to keep majority of them as posts, but then if there's any clear silo being created. Create them as parent/children Pages, so it's nested as
/parent/child/ url slugs as @dandan594594 mentioned. Helps with organization in the backend, but that's just for us as the owners.
- Oct 9, 2013
- 3,471
- 14,474
There's no differences between posts and pages externally. They are the same thing.
The only difference is the internal representation.
Specifically, posts by default can have tags/categories. That's really it.
If you want to use tags/categories, you use posts.
If you want to create your own structure and have better control, you use pages.
The only difference is the internal representation.
Specifically, posts by default can have tags/categories. That's really it.
If you want to use tags/categories, you use posts.
If you want to create your own structure and have better control, you use pages.
Rankon Guru
Regular Member
- Mar 5, 2022
- 224
- 41
You probably won't observe any variation because crawlers consider your articles to be pages as well. So focus on both pages and posts.
- Sep 7, 2021
- 6,698
- 769
I think No Difference
- Sep 10, 2010
- 11,815
- 26,656
Tbh not quite, in terms of the cms. There is nothing that stops you from achieving such functionality (e.g. have pages with tags/categories). Why you would do it is a different story, but obviously this is easily achievable with the wp loop and the db.
- Oct 9, 2013
- 3,471
- 14,474
Sure, but that's with customization. You could customize anything to do anything
The default and intended functionality of pages vs posts is posts have tags/categories, and pages don't.
You could customize pages to have dancing hamsters.
There would be no point in customizing pages to have the exact same categories/tags as posts. If you want pages to have categories, it would be because you want to do something more custom and you want to differentiate between post categories and page categories.
- Sep 10, 2010
- 11,815
- 26,656
Exactly, you could be more advanced and not rely on those 10 year old methods (applies for tech as well I guess , not only seo) haha.Sure, but that's with customization. You could customize anything to do anything
The default and intended functionality of pages vs posts is posts have tags/categories, and pages don't.
You could customize pages to have dancing hamsters.
There would be no point in customizing pages to have the exact same categories/tags as posts. If you want pages to have categories, it would be because you want to do something more custom and you want to differentiate between post categories and page categories.
jennykumar
Senior Member
- Nov 14, 2012
- 926
- 480
pages will not rank in long-term.
post does, when you update them.
post does, when you update them.
- Mar 21, 2013
- 24,784
- 31,554
Internally pages and posts are the same thing. Both go on the same database table and have a type field that says "page" or "post".
Posts are more versatile on the front-end and you can better organize categories and so on. The only difference between them for ranking purposes is that pages usually get linked sitewide.
Posts are more versatile on the front-end and you can better organize categories and so on. The only difference between them for ranking purposes is that pages usually get linked sitewide.
Faizskdhjatl
Junior Member
- Nov 17, 2016
- 143
- 18
It's my opinion google consider pages as webpage(commercial website), while post are considered as an article (blog).
So you use pages if you are trying to ranking for website related keywords.
I have seen some pages have out rank official website's by building pages.
So you use pages if you are trying to ranking for website related keywords.
I have seen some pages have out rank official website's by building pages.