plainblack.com
Username Password
search
Community Support
WebGUI User Guides
Wiki
Forums
Report A Bug
Request Features
WebGUI 8
WebGUI TV
Add-ons and Plug-ins
Service Providers
webGUI in the news
Karma
API Docs
the people behind wg
webgui worldwide
Mascot
wallpapers
powered by icons
Sightings
Bookmark and Share
SEO Settings  (#9036)
Issue

As SEO becomes more important for our clients, we're getting more requests for this abililty. The current implementation of WebGUI does not directly support SEO features. A Setting in the Admin panel to set the default site keywords and description plus the ability to override these settings on a per Page Layout (or Wobject) basis would be a very useful benefit.

One implementation idea would be to make the keywords and description variables available via the Style template. Currently the only values available when WebGUI builds the style is head.tags, body.content and any meta data.

 

Comments
JT
0
11/4/2008 9:27 am 		I don't really understand. There are already about a half dozen ways to accomplish this in WebGUI right now, why do we need another? Perhaps we just need a chapter on SEO in the Content Manager's guide that explains better how to use all these features for SEO?
knowmad
0
11/4/2008 10:24 am 		We don't necessarily need another way, we just need an easy way. Currently, I can only think of 2 ways to add meta data to a page: 1. Content profiling - this is not easy for the average user and involves multiple steps including enabling it, adding new fields and fixing your style templates. 2. Extra header tags - this requires some basic HTML knowledge to insert proper tags and is non-obvious to a new user What might be more helpful is having access to the description (synopsis) and keywords in the style template so that these elements can be used in lieu of meta data.
JT
0
11/4/2008 10:43 am 		You're forgetting the easiest way. There is a keywords field automatically adds a keywords metatag to the head block.
knowmad
4
11/4/2008 11:17 am 		I didn't even know about that behavior. So let me alter this ticket to request access to the keywords and description via template variables so that integrators and template designers can have more control over how the meta tags are being output. There's a strong case for why this is needed -- 1. Code generated HTML is bad. 2. Some sites may need XHTML output while others want HTML tags.
knowmad
0
11/4/2008 11:21 am 		s/description/synopsis/g
JT
1
11/4/2008 11:33 am 		Rejected!
JT
3
11/4/2008 11:34 am 		Hah! You didn't think I'd do it did you?
JT
0
11/4/2008 11:39 am 		I'm sorry, but your new request isn't detailed enough. I need you to explain a few other things. 1) Should there be a keywords var, or a keywords loop? 2) I disagree with your premise that designers need control over this, please explain why you do? 3) Are you saying then that since there will be template variables for these things that we should then only expose the keywords as template variables and not add our own tags? If so, what about those people already using it the way it is? Do we put the template variables in to their style templates automatically? Or do we make it a gotcha? 4) Since you are positing that all code generated HTML is bad, are you then also advocating turning all head tags into separate template variables via this RFE?
JT
0
11/4/2008 11:48 am 		Incidentally, I'm curious on your answers to 2-4, but I really only need an answer on #1.
JT
0
11/4/2008 11:49 am 		Feedback Requested by JT
knowmad
0
11/4/2008 12:16 pm 		#1 - A var with the keywords split by comma as you're doing now would suffice. Just allow a template editor to place it where they want rather than have it injected into the template. #2 - I thought I did when I said it makes a big difference as to whether you want to output HTML or XHTML. #3 - Yes. A possible solution for those expecting the current behavior is to use a switch either in the Settings or the configuration file. Otherwise, I agree about a gotchas entry. #4 - No. I think that should be addressed separately from this RFE. It's something the template redesign group needs to address. William PS: Why do RFE comments not honor carriage returns? Is that a bug or an RFE?
knowmad
0
11/4/2008 12:25 pm 		Here's another thought on how to handle upgrading old sites to the new template. I think we could programmatically find a way to have the upgrade script inject the tags into the style templates as a site is upgraded. This would forgo the need for a gotcha or extra configuration flags (which I dislike).
arjan
0
11/5/2008 2:45 am 		I just like to say that I concur with #3: Yes, we should only expose the keywords as template variables and not add our own. We put in the template variables in the style templates of users who expect current behavior.
rogier
0
11/6/2008 4:11 am 		Instead of removing the meta tags from the head.tags var, a different var could be added (e.g. head.tags.nometa) which inserts the head tags without the meta tags. Head.tags would still work and it will be quite simple for users to change their style to the new method.
knowmad
5
11/7/2008 8:42 am 		Brilliant!
Details
Ticket Status Pending  
Rating3.2 
Submitted By knowmad  
Date Submitted2008-11-04 
Assigned To unassigned  
Date Assigned 2012-02-03  
Assigned By  
What to improve? WebGUI Stable  
URLrfe/request-for-enhancement/9036
Karma
Difficulty 1  
Karma So Far121
Karma Rank121.00
Keywords
Ticket History
11/10/2008
6:23 AM 		40 karma transfered rogier
11/7/2008
8:43 AM 		50 karma transfered knowmad
11/5/2008
2:53 AM 		31 karma transfered arjan
11/4/2008
12:16 PM 		Pending knowmad
11/4/2008
11:49 AM 		Feedback Requested JT
11/4/2008
11:48 AM 		Pending JT
11/4/2008
11:39 AM 		Feedback Requested JT
11/4/2008
11:17 AM 		Pending knowmad
11/4/2008
10:43 AM 		Feedback Requested JT
11/4/2008
10:24 AM 		Pending knowmad
11/4/2008
9:27 AM 		Feedback Requested JT
11/4/2008
8:03 AM 		Ticket created knowmad
© 2012 Plain Black Corporation | All Rights Reserved