A SEO horror?

Hamza That sucks! I haven't checked yet, but it wouldn't surprise me if that was the case for other sites as well. By default this should be taken care of by WPMN (Jewel Test ) ASAP, given that there are many community sites with public content that needs to be indexed properly.

Bottom line: we need a description and a slug field, plus a title advisor (AI driven?) for each of the spaces/rooms, so that the pages can be properly indexed.

Thank you for listening.

Shahjahan Jewel - wouldn't it make sense to appoint an employee specifically for that kind of thing? Gathering feedback from the community, prioritizing it, and then passing it on to the devs, who then provide feedback as to the ETA?

Hamza how long have you been setup?

teethy Why should I use a plugin for FCom to write a proper description (from the room/space description) or offer a SEO field specifically for that? But to answer your question: right now I'm not using one at all. I just noticed this by looking at the HTML source.

Helmar Rudolph I asked because I am not using any and my description for every post is correct. I don't know why was weird or something asked for this just be curious if this can be problem. And don't check just description. Did you check alt text for images, seo schema, video thumbnail alt text an much more than you description?

David Scurlock I stand corrected. It must have been a fluke, because the other rooms/spaces I checked looked just fine.

David Scurlock  you need seo for images, videos, scheme etc.. Fluentcommunity does nothing for this. For example If you upload images with iphone17 is uploaded with name dghh.jpg google will never find and show you image for search iphone. And fluentcommunity seo is kind of for posts but not for feed site. If you don't have custom code with description you have just empty description for feed. If you have empty slug and fluentcommunity on root it is disaster. And one more big problem for most of the communities is loading site with https://www and without https://. Most of the communities show you just header and sidebar without any content when you use www and this is huge problem for seo. Google see the sites 2x with different content.

teethy Shahjahan Jewel made it sound like Fc was fully seo optimized on an internal level and if not then it would be a disaster. So you would have to ask him that question. Im starting to think FC is starting to fall behind anyways.

David Scurlock if not you can check it. Just check you source code. Is there any alt text for images, scheme.... ? Open you community page in private window with https://www does it have same content?

teethy If you're seeing differences on your site with and without www, then that's a problem with how you've set up your site and DNS. You should always have a redirect to point to the correct URL.

Jonathan Gwyer I fixed it. Is not dns at all. I just check few communities from this post and all of them have different content with and without www. Can you send me your link? I am curious.

teethy there is no reason to use www. In fact it take longer to load www then non www. I have never used www since it will never increase my profit margins.

teethy your server should be redirecting all www traffic to the naked domain or vice versa. What are you using as your url?

The sites I'm currently running are all on subdomains, so the naked and www go to the non-FC site anyway.

As far as I can see, anything on www.teethy.org is correctly served from teethy.org

David Scurlock why on earth would it take longer to load from www?

Jonathan Gwyer its an extra step in the domain loading process, without www, a site may load a quarter second faster. Using www at all is a mute point and does not add any value to you domain.

David Scurlock that's not how it works.

If your site is configured as www there will be no redirects if the address used starts www.

And if your site takes 1/4 second to redirect from www to naked, or vice versa, you really need to change host!

(moot)

David Scurlock It is not about us. 🚫 1. Google Treats www and non‑www as Separate Hosts
Google considers https://example.com and https://www.example.com to be two different hostnames.
If they serve different content, Google may interpret them as two separate websites, which leads to:

• split authority
• inconsistent signals
• indexing confusion

🚫 2. Different Content = Major SEO Risk
If one version loads the full website and the other loads only a header and sidebar, Google may see:

• thin content
• duplicate content with inconsistencies
• broken or incomplete pages
• poor site quality signals

This can negatively affect rankings and crawling.

🚫 3. Wasted Crawl Budget
Googlebot will crawl both versions separately.
If one version is incomplete or broken, it wastes crawl budget and slows down proper indexing of the real content.

🚫 4. Risk of Google Choosing the Wrong Canonical Version
If both versions are accessible and show different content, Google might:

• index the wrong version
• ignore the correct version
• show incomplete pages in search results

This can directly harm visibility and traffic.

teethy if your server is correctly configured, Google will only ever see the one version.

Your server will redirect naked to www or www to naked before it even touches WordPress or Fluent Community. This is just the same as an http to https redirect.

Depending on your hosting, it could be in your htaccess file. If you use Cloudflare you can even set up a rule to do this before it even gets to your server.

https://community.cloudflare.com/t/redirect-the-www-to-non-www/558655