NodeBB SEO is in fine fettle.

cloudflare is bad for traffic

Returns this thread as the #1 result in duckduckgo 😳

Does this answer the question?

@srinik Think about it: Where/how does google make its money? Those big data relationship maps are more valuable than your post content. And that is why google bot finds and indexes even against robots.txt.

Yeah, I know googbot does not respect robots.txt and you need to create an account, use their tools, etc. to in efforts to potty train their bot. And therein... they can track even more big data. And googbot still indexes your profiles as it seems it pretty much has a mind of its own and carte blanche to do whatever since we all are so desperate for page rankings.

So, now that we've thought about it for five to ten seconds, do you still find this behavior surprising?

Heh, wife is an accountant: When confused: Follow the Money!!

We use NodeBB 3+ years at https://chatrooms.talkwithstranger.com and some more sites and love NodeBB.

We use NodeBB also as a CMS containing English definitions on a dictionary. Our users are loving it. but we are struggling in increasing our Google rankings as all our competitors are using AMP pages to outrank us.

We would need an official Google AMP plugin that would enable any node bb topic page , like the 1 I'll post my topic on, to have an alternative Accelerated Mobile Page.

Since when each topic will have a corresponding AMP version then it will help us rank much more easily in Google SEO search results and increase our rankings.

With this plugin, our users can help us discover our sites and node bb itself site much more easily because Google ranks AMP pages better and higher over normal html pages.

Please see all top news sites and forum sites use AMP https://www-searchenginejournal-com.cdn.ampproject.org/v/s/www.searchenginejournal.com/google-amp-ranking-factor/157785/amp/?amp_js_v=a2&amp_gsa=1&usqp=mq331AQFKAGwASA%3D#aoh=15897444560799&referrer=https%3A%2F%2Fwww.google.com&amp_tf=From %251%24s&ampshare=https%3A%2F%2Fwww.searchenginejournal.com%2Fgoogle-amp-ranking-factor%2F157785%2F

This will help users coming from mobile to load much more faster giving a better and faster UX.

Any node bb devs or any one else willing to take this, please reply or pm me. @Global-Moderators @Staff

Thanks

Thank you for the idea of SEO.

a. I agree with @julian there are philosophical disagreement
b. agree, adding Google schema support could be built-in like we have seen FB open graph is built-in
c. not a forum, try other software
d. would be helpful, could be done by a plugin. Argueable could be built-in too, IMHO
e. I have nothing against but I think it would be a large project because I could picture some addition live ML and log mining needs to be developed for this to be generalized, and could complicate the core NodeBB a lot.
f. not a forum, sounds to me a social network
g. has been done by plugin and you could pretty much develop it yourself.
h. not thing against it, I think it currently works.
i. it's more of a site operating and community engagement strategy
j. not a forum
k. Good idea, could be done by plugin
l. This is already in place, right
m. good idea. I don't see why not but I assume it already works
n. same as k

@pitaj said in Slug translation ?:

You can't. It's been an often requested feature, but the slugs are hard coded throughout the NodeBB codebase.

Got it , Thanks

@PitaJ Issue created at https://github.com/NodeBB/NodeBB/issues/5643

fais3000 created this issue in NodeBB/NodeBB closed Widgets content not being crawled by Search Engines #5643

Meta keywords aren't really relevant anymore. It's a "nice to have". If you have it it's great, because Google isn't the only search engine in the world. But it absolutely does not impact negatively on SEO, unless you're padding it with unnecessary unrelated content, which is what Google wants to stamp out.

@kacemlight I know it's a very old topic. Just replying because i faced a similar issue. SEO tools pointed out that the heading structure was incorrect i.e the nav bar headings had H3 and content had H2 and H1.

I solved it by creating a barebones plugin and overwrote the tpl file that had the inconsistent heading structure (in my scenario). The path of the file is plugin/static/templates/partials/menu.tpl

@Baerrus Where you at with SEO so far?

Still waiting for documentation upstream, because the process to implement plugins for Remarkable seems quite convoluted at first glance... jonschlinkert/remarkable#48

elennaro created this issue in jonschlinkert/remarkable open Example of Custom Rule, and appropriate renderer. #48

@frissdiegurke said:

I've just run the TLS-configuration check that gets referenced: https://www.ssllabs.com/ssltest/analyze.html?d=community.nodebb.org

@julian and other @devs (you need group-mentions :P): you may want to double-check the issues listed by this:

Experimental: This server is vulnerable to the OpenSSL CCS vulnerability (CVE-2014-0224) and exploitable. The server does not support Forward Secrecy with the reference browsers. MORE INFO »

Btw: great that their link to wikipedia uses http instead of https ^^

Session resumption (caching): No (IDs assigned but not accepted)

NodeBB should already be optimised for best SEO value. Semantic HTML, proper meta tags, links back to canonical URLs and parent listings...

To be honest, you shouldn't have to worry about it, and if there's something we missed, it's just a pull request away from being available for everybody 🙂

@a_5mith For what it's worth, I really like your suggestion, a lot. +100.