[Resolved] Blog page (archive) cons & pros

[Sebastien]

Hi,

I meet some cons by using the page blog archive (native in wordpress).
The 1rst is, that this page is reconized as Home page in my breadcrumbs plugin.
The second is that is not very easy to design / devide the blog page in section (per tag etc).

That’s why I think about:
1) uncheck the param: Customizer > Homepage > Article page > none.
2) create a commun page into which I would add WPSP or another plugin, to displays my posts

I would like to be sure I’m not going to do all of that for nothing…
a)Is there any impact in term of speed load? is there any contraindication to do that? could you share cons & pro that you see into this method?
In my opinion this would be a commun need for dev to forget blog and go through a most advanced of filtering/customization for the archive blog page, does not it?
b)If I don’t use the blog nativ page anymore, should I also desactivate the generatepress module called “Blog”? If I do, will I get more performances (compared to stay with this module wihtout using the blog archive page)? or will it impact others points in my website?

thanks

[David]

Hi there,

you can use a static page you create your own ‘blog’ page with WPSP – this article then explains how to redirect category archives:

https://docs.wpshowposts.com/article/use-static-pages-as-category-archives/

Performance impact would probably be negligible but it is higher maintenance for you.

The Dispatch Site in the GP Site Library uses WP Show Posts to create the magazine front page, but the blog is left as GP so no concerns about redirects or any other headaches – maybe a better solution.

[Sebastien]

1) Ok about performance point thanks, but is there any SEO impact by using any blog static archive page (with dynamic content) …. compared to using the “last post” page (I mean the nativ blog archive page which displays last post) ? I mean is there any dedicated JSON tag or anything on for this type of page?

thanks

[Tom]

No, that shouldn’t be an issue. As long as there isn’t duplicate content (which there shouldn’t be in this case), you should be good to go 🙂

[Author]

Posts