-
Notifications
You must be signed in to change notification settings - Fork 333
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 Accessibility #6402
Comments
Yeah, currently there isn't any sensible SEO in Friendica, and the internal search itself is a mess, sorry about that. |
Any idea how to improve it? For example in Google+ each of the messages in the stream (that I suppose is what the crawler gets to see) contains the following snippet:
In Friendica the full post view direct URL link is hidden in a popup window (in Frio theme, at least) and looks as follows:
I have no idea if pulling the direct link out of the popup menu would help the crawlers. Actually I don't even know what the crawlers see so it's hard for me to suggest what to improve to help them index it better. Any idea, please? |
In a popup window? This behavior doesn't sound familiar. And the redir only appears because you're logged in. Please try the search in a private browsing window without logging in. Otherwise, there is a host of HTML metadata that we could provide to enable search engine crawlers, including sitemaps, page info, etc... but someone™ has to do it. |
In a private window it's the same:
This is the most crucial thing for me. I can work around bugs in navigation, can remember not to post what I cannot delete, but I selected Friendica over say MeWe.com as I believed my posts would be searchable and search engines would index it for me. I'd very much need this fixed. What can I do in order to help improve the SEO stuff, please? Just let the search engines index the posts, I don't need it super efficient and win some keyword war, nothing like that. Just to let them understand that these are single posts available under given URL. |
The snipped you copied is the top-left dropdown menu showing the original URL of the displayed post, which may be an external link if it was posted on a remote server first. Not sure if it has any impact on SEO though. I understand your concern, but we don't have a resident SEO expert in the Friendica team, so everything that we may do will necessitate a lot of learning friction, and most of us would rather work on other stuff because it's more convenient. |
Definitely work on more convenient things. The development should and needs to be fun. |
As for the HTML snippet - it contains the very URL the crawler needs to see and remember, that's why I was searching for it on the page and posting it here. Maybe it's was a nonsense idea in the first place, I don't know. |
Changing HTML templates is pretty straightforward, if you have specific improvements to suggest, I'd be happy to implement them. |
Good start is here: https://search.google.com/search-console/welcome |
If you're ready to do it, we can certainly help with that. |
Yeah, we are really happy with every person who contributes stuff! |
Keep those in mind, who do not wish a good search ability and make any SEO measurements optional. |
This is nonsense, either these people should have all their post private or have a conservative |
We already do have a default robots.txt mechanism (/mod/robots_txt). I suggest to have it configurable so that it is allowed to crawl the profiles and the local community, but not more. No search, no global community, no other page. The other settings should be some: "Leave me alone" setting. AFAIK all SEO improvements depend upon the robots.txt settings, so it should be no problem at all, improving the SEO stuff. |
So what I have found in the meantime: it's turned out that Friendica itself was OK. If you try searching for say "Petr Stehlík ploché konektory", or "Petr Stehlík ESP8266 z bláta do louže", you'll find perfectly indexed posts under the URL domain/display/MESSAGE_ID (the former on www.friendica.cz domain, the latter on www.libranet.de domain), and it works just great. It seems to be a configuration issue, right? Any idea what to search for? What could I ask the admin of www.nerdica.net to change or reconfigure, please? |
This can be configured in the |
Hm, for comparison - libranet.de (that is indexed properly):
and nerdica.net (that seems to be indexed improperly yet still some pages are in search engines' archives):
So libranet.de invites few good crawlers by "allowing" them to index everything while nerdica.net lists a bunch of paths that are not to be indexed and doesn't say anything about the rest of the web. Since full access is the assumption and the explicit If you disagree and feel like one of the paths could be causing search engine's indexing issues please tell me. |
I'm not a real expert in this stuff. And I must confess that I'm working more on the opposite, means: Rejecting access for search crawlers at all. This has the background that with article 17 of the copyright directive in the EU the responsibility for copyright violations had been changed. So we should do everything to avoid that copyrighted material is shared - but also that it cannot be found. |
Expected behavior
Google, Bing and others can index each public post in Friendica and later offer them in their search indexes by direct URL to the given post.
Actual behavior
It seems to me that Google always returns the /search page of Friendica.
I am very eager to get my posts and posts in our forums indexed by search engines. What can I do for that, please?
Steps to reproduce the problem
For comparison, Google+ (yes, I'm coming from dying Google+) posts are indexed properly, so if you search for say my name "Petr Stehlík" and some keywords you'll get the unique direct URLs to the posts in the form of https://plus.google.com/+PetrStehl%C3%ADk/posts/uniqueID
Friendica version you encountered the problem
2019.01rc
Friendica source (git, zip)
as currently on nerdica.net
PHP version
as currently on nerdica.net
SQL version
as currently on nerdica.net
The text was updated successfully, but these errors were encountered: