View Issue Details

IDProjectCategoryView StatusLast Update
0003020Composrcorepublic2017-01-09 16:02
ReporterPatrick SchmalstigAssigned ToChris Graham 
SeverityMajor-bug 
Status closedResolutionfixed 
Product Version 
Fixed in Version 
Summary0003020: Major SEO issues
Descriptionhttps://www.google.com/search?safe=off&q=+site:lovinity.org+lovinity+community&sa=X&ved=0ahUKEwiMmMCluLPRAhVQxGMKHYXuCK0QrAMIJg&biw=1600&bih=775

I'm finding a lot of SEO related issues on Composr 10 RC28. As you can see, search engines are not getting the correct page title and description for the page they hit. The same thing sometimes happens for embedding services. And I also noticed this affects page titles in the detailed list of who's online user activity.
TagsNo tags attached.
Time estimation (hours)
Sponsorship open

Activities

Patrick Schmalstig

2017-01-08 21:01

administrator   ~0004671

Could be a Cloudflare or NGINX issue as well. So I'm investigating myself.

Chris Graham

2017-01-08 22:38

administrator   ~0004673

From a quick review, none of these pages have meta descriptions configured:
https://lovinity.org/start.htm
https://journal.lovinity.org/catalogues/entry/website-functionality/what-features-does-the.htm
https://journal.lovinity.org/catalogues/entry/rules-and-policies/do-i-own-the-content-i.htm

Google is particularly likely to ignore meta descriptions that are shared across many pages.

This said, I noticed a bug breaking automatic meta description generation, and that we weren't doing it for catalogue entries.

So, fix your existing content, and I'll make sure it works better in the next RC.

Google should be smarter though. It's generating a snippet from a role="note" section, which it should know not to.

Patrick Schmalstig

2017-01-09 08:02

administrator   ~0004678

Last edited: 2017-01-09 08:04

View 3 revisions

Forum topics also do not generate meta descriptions like they should, I noticed.

Chris Graham

2017-01-09 16:02

administrator   ~0004679

Forum topics don't support the explicit metadata, as nobody will enter/maintain it. However, I agree we need to do better. From the next RC it will dynamically take the first 160 characters of the first post's plain-text, and use that.

Issue History

Date Modified Username Field Change
2017-01-08 20:58 Patrick Schmalstig New Issue
2017-01-08 21:01 Patrick Schmalstig Note Added: 0004671
2017-01-08 22:38 Chris Graham Note Added: 0004673
2017-01-08 22:38 Chris Graham Status non-assigned => closed
2017-01-08 22:38 Chris Graham Assigned To => Chris Graham
2017-01-08 22:38 Chris Graham Resolution open => fixed
2017-01-09 08:02 Patrick Schmalstig Note Added: 0004678
2017-01-09 08:04 Patrick Schmalstig Note Edited: 0004678 View Revisions
2017-01-09 08:04 Patrick Schmalstig Note Edited: 0004678 View Revisions
2017-01-09 16:02 Chris Graham Note Added: 0004679