-
-
Notifications
You must be signed in to change notification settings - Fork 834
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve discussion page near canonical url #2397
Comments
We could do it the way the Discourse does. They also use a postnumber for the URL, but use a That is probably better for SEO, because of less links and no overlap. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. We do this to keep the amount of open issues to a manageable minimum. |
I'm really confused by this. What's the issue here? Using the We should keep that canonical to prevent that, but we should also add It might be work replacing this canonical with a |
This is big mistake. Really i dont understand why was not fixed... |
I like using I'll also note that the current no-js approach is missing next page / prev page buttons. THAT is quite problematic, and something that definitely needs to be fixed before stable. |
When redesigning, we should also make sure to fix #2130 |
https://github.com/flarum/core/blob/f2168f939db15f58c1511b56b4d95c737b62ce1a/views/frontend/content/discussion.blade.php#L18-L24 is incorrect, because there won't be prev/next links on the API document for a single item. That's what's causing the missing pagination links. |
Bug Report
Current Behavior
In beta.13 and beta.14, there is a canonical url included in the hmtl document.
For example for https://discuss.flarum.org/d/187-word-association-game/1000
the canonical url is https://discuss.flarum.org/d/187-word-association-game?near=1000
As per #189 (comment) this causes search engines to crawl that URL.
Edit: the redirect works, my link was just broken.
The text was updated successfully, but these errors were encountered: