# Pagination URL scheme not passed through when topic is renamed

**URL:** <https://meta.discourse.org/t/pagination-url-scheme-not-passed-through-when-topic-is-renamed/21170>\
**Category:** Feature\
**Created:** [2014 年10 月 15 日 18:36 UTC](https://meta.discourse.org/t/pagination-url-scheme-not-passed-through-when-topic-is-renamed/21170 "2014-10-15T18:36:36Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

作者： ![Mittineague](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mittineague/32/114259_2.png) [@Mittineague](https://meta.discourse.org/u/Mittineague)\
发布日期： [2014 年10 月 15 日 19:55 UTC](https://meta.discourse.org/t/pagination-url-scheme-not-passed-through-when-topic-is-renamed/21170/3 "2014-10-15T19:55:36Z")

</div>

Interesting idea though I’m not sure how Google would treat having literally millions of posts to index for a site. Maybe if the posts had canonical pointing to the topic?

Seriously though, I have never had a problem with landing on a long content heavy page and using my browser’s “find” to home in on what I searched for.

But with infinite scroll that would be useless if what I wanted was in post number 100++ and I landed on post number 1.

Using the Discourse Search would be required and that might not be clear to those unfamilliar with Discourse.

As a topic loads in 20 posts at a time, maybe it could be worked out to give bots a per 20 URL to index?

---

_[View the full topic](https://meta.discourse.org/t/pagination-url-scheme-not-passed-through-when-topic-is-renamed/21170)._