On Fri, 2010-12-24 at 11:02 +1100, Helen wrote:
> Regarding the meeting discussion on SEO, which AFAIK was rather unresolved.
> 
> I use SEO principles every day so have a few thoughts on the matter,
> but first I want to clarify what the aims and constraints for openSUSE
> are.
> 
> I'm not familiar with Wiki software, so my Main question is: With the
> wiki, is it possible to add meta title, keywords, description to
> individual pages or are you talking about one wiki-wide set of data?
> 
> And are there any other serious constraints to optimizing the Wiki?

Well, I am not sure of this as I will have to look into the entire code
and I dont have the  time to do that

> 
> Secondly, what is the AIM of optimizing the Wiki - and other documents
> (news, blogs). Is it -
> 
To increase our visibility,
For news we intend to add it to various rss forums too

> 1) make it easier for people to find the openSUSE pages they are looking for?
> 
> (for example, make sure that someone searching for OBS step by step
> finds the right documentation)

> or
> 
> 2) bring more traffic, and generate interest in openSUSE by optimizing
> for non-SUSE-specific topics?
> 
> (so that someone searching for 'linux virtual server' finds an openSUSE page)

> 
> Of course both are possible!

Right, 
> 
> 
> I've sent this query to both wiki and marketing lists, as SEO can be
> considered when writing ANY documentation that will be published. It
> is not the mysterious black art that expensive webpreneurs would like
> you to think it is.
> It is a very simple, clear and easy process. Obviously for best
> results a bit of time needs to be invested, but even for a quick blog
> post it's possible to spend a few moments considering the SEO.
> 
> I'll have some more detail on that soon, but first I'd like to hear
> what you are hoping to get out of the SEO process, how you see it
> fitting with our aims. World domination is certainly an option....
> 
> cheers
> 
> Helen


-- 
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to