- 🇺🇸United States smustgrave
Currently going through the end of the queue to see what could still be relevant for D10.
I'm also not seeing the use case for this one but does sound like it could be useful to some.
Will need an issue summary update.
Hi
As you know page numbers is like 1 2 3 4 ...
And when 10 nodes added and if the page limit is 10 then the page numbers stay as they are and the nodes move from one page to the other.
to avoid this i tried to create the page numbers like : 45 44 43 42 .... instead of 1 2 3 4 .... if we have 45 pages. This way when new nodes are added the ones on the last page will have still the same page number. Of course i am talking about a view with tons of nodes and where the nodes are ordered by descending creation time.
There are mainly 2 reasons why i try to reverse the page numbers:
1- users memorise the page numbers, and after some time when they come back, all the nodes are moved to other pages since lots of nodes are added.
2- google bot and other bots memorises the page numbers, and when it comes back it sees that all pages with the same url have different pages, and thinks that it should reindex reindex reindex.... keep indexing. and when displaying result to its' users bots always point to a wrong page. And this i believe drops the page rank of the site.
I wonder if anyone can help me to reverse the page numbers.
thank you
arda
Active
9.5
Last updated
Issue summaries save everyone time if they are kept up-to-date. See Update issue summary task instructions.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Currently going through the end of the queue to see what could still be relevant for D10.
I'm also not seeing the use case for this one but does sound like it could be useful to some.
Will need an issue summary update.