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.
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
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