I recently relaunched a website for a client, moved from oxygen builder to bricks builder and migrated from gridpane/vultr hf to cloudways/vultr hf and changed some seo settings using seopress pro.
What I have noticed is that pagination is working (ie I can click on page 2, 3 etc) however when on the other pages the pagination element stays on page 1.
Note I am not using the default cpt archive for this. I built the properties page using custom query loop in bricks builder with a pagination element.
When clicking on subpages directly, say Page 2, it looks âcleanâ and pagination is set correctly. However, trying to press ânextâ or choose say Page 3, the problem persists - the next button doesnât work and choosing page 3 for example, adds a paged URL to that page example /page/2/?_paged=3
I havenât used facetWP with Bricks, but generally speaking⊠with these facet plugins you need to use their own pagination facets instead of WP pagination. The same is true for WPGridBuilder.
FacetWP have their âpagerâ facet for adding pagination to work with their filters⊠Pager | FacetWP
(but whether or not facetWP is supposed to integrate with Bricksâ pagination, Iâm not sure)
I had a similar problem with a query loop on a page showing âteam membersâ and managed to solve it by adding some code to my theme to prevent WP canonical redirects (see links):
I modified the code a bit for my own setup and added a check to see if post type is set because it caused some errors on other pages/queries but now the pagination works and the new pages load as expected.
" If you are using a Pager facet for pagination on archive pages, be aware that the individual posts on the subsequent paged pages, and the paged pages themselves, will not be seen and indexed by search engines. The Pager facetâs <a> tags do not have href attributes with links that the search engine spider can follow. Also, users without JavaScript enabled will not be able to see and use any pagination on paged archives that you are using FacetWP on.
For SEO, this is not necessarily problematic, as long as all individual posts are reachable for the search engine spider through other archive pages on the site, like post-type archives and term archives. Another way to make sure all pages are found is by implementing a sitemap and pointing to it in your robots.txt file.
Another common solution is to add a prev/next (adjacent posts) links to each post page. Then you know every single post is always going to be linked from another post and can be found by bots.
But yes, this is a problem that the facet plugins bring with them. Theyâre not designed to work with WP pagination, thatâs why they all have their own solutions for pagination / load more etc.