-
-
Notifications
You must be signed in to change notification settings - Fork 835
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
Search engine optimization #189
Comments
Noindex for subpages (Inspired by Yoast SEO for WordPress) to avoid duplicate content. and URL Friendly. |
@axisdos Noindex isn't needed when we have the |
Questions of how to handle foreign language/unicode URLs -- such as #194 -- will also have SEO implications. In that regard, unfortunately, I think different regions may prefer different solutions. |
Would this tie into Accessibility at all? I'm not extremely familiar with it, but when structuring the noscript HTML along with the rest of the page, it would be nice if parts of it were identifiable for users with disabilities. |
Could this approach be an alternative to the noscript tags? |
Quite possibly, feels a little bit hacky though? I'm not too fussed |
app('view') call to set translator is temporary. See #189
#906 is an SEO-related issue specific to the Tags extension. (I hope I was right to file it as a separate issue.) |
I investigated links on my Flarum and posted results in this topic on official Flarum forum, have a look: |
Also interesting, with regards to changing |
@01010000101001100 refers to a bug in the pagination code. Version 0.1.0-beta.7 will infinitely link to the "next" page id, even if there are no more discussions. I have only 1 page of discussions, but Google has already crawled to page 584. Fixing this would probably improve SEO a lot. (--> #1310) |
Otherwise, search engines start indexing pages that aren't filled yet. Refs #189.
To clarify, what exactly needs to be done here? Based off of the link Franz sent, Google seems to be fully capable of handling our frontend. Is it just a question of ensuring pagination is properly done? I've been resolving meta title and description issues through a series of PRs, see #495 (comment), #2049 |
Google is able to render Javascript but this is much, much slower than indexing 'static' HTML. More information here: TLDR; use Javascript for endusers, HTML for crawlers. |
Also, Google isn't the only search engine, especially in some other countries. |
You're right, though, that we need to spec out more clearly what aspects we want to tackle. "SEO" is a very generic and not very actionable issue title. 😆 |
There are too many dofollow links on the site. ("Mentions, Likes, Replies") - Their attributes must be "rel = nofollow". the ?near tag. |
Splitting into #2397, https://github.com/flarum/core/issues/626, #2397 |
Flarum renders very basic versions of the discussion list and discussions (within
<noscript>
tags), which are going to be specifically optimised for search engines. This all takes place in Flarum\Forum\IndexAction and DiscussionAction, which extend Support\ClientAction and use Flarum\Support\ClientView. The actions get data from the Flarum's API and pass it onto content views (discussion.blade.php and index.blade.php). I'm happy to explain more if need be because it can get pretty confusing.Put simply, the code is a mess. It needs to be rethought and refactored. A few thoughts:
Only after doing this will we be able to effectively optimise the SEO content and do the following:
The text was updated successfully, but these errors were encountered: