784318 - [ia] Review and update page <title/>'s

Status: RESOLVED FIXED

(support.mozilla.org :: Knowledge Base Software, task, P2)

Description

[Ricky Rosario [:rrosario, :r1cky]]

I recall specific recommendations on changes to the text in our <title/>'s. I am pretty sure we aren't following all of them in the new IA yet. Most or all of our our titles currently look like:

* "Learn the basics: get started | Firefox Help"
* "Firefox for mobile | Firefox Help"
* "<the page/article title> | Firefox Help"

Bram, can you take a look at what we have and let us know how they should change?

Comment 1

[Bram Pitoyo [:bram]]

Hi Ricky. I just pulled off our recommendation documents from Phase 1 and Phase 2, and they have these principles:

“Lockstep consistency in title conventions will yield many annoying and redundant results, some of which will exceed reasonable length, (if not the 64-character recommended max in the spec). Instead, be flexible and use several approaches to title wording tactics, while focusing strategically on decision support, descriptions and keywords for search optimization.”

The top page should be titled Mozilla Support

Other pages will occupy the space before Mozilla Support. For example:
* Products & services | Mozilla Support
* Help articles | Mozilla Support
* Hot topics | Mozilla Support
* Help other users | Mozilla Support
* Suggestion box | Mozilla Support
* Messages | Mozilla Support
* bram | Profile | Mozilla Support

If pages already have the word Mozilla in it, write “Mozilla” only once. For example:
* News | Mozilla Support --> Mozilla News

Product landing pages don’t need the word Mozilla Support or Products and Services. For example:
* Firefox Help, NOT Firefox | Mozilla Support
* Firefox for Android Help, NOT Firefox for Android | Mozilla Support
* Firefox OS Help, Firefox OS Support
* Mozilla Persona Help, Mozilla Persona Support
* Mozilla Marketplace Help, Mozilla Marketplace Support
* Thunderbird Help, Thunderbird Support

Topic landing pages are always associated with a product. For example:
* Learn the basics: get started | Firefox Help
* Customize controls, options and add-ons | Firefox OS Help
* Privacy and security settings | Firefox for Android Help
* Get community support | Mozilla Marketplace Help

Article pages need to also be associated with a product, but only if it doesn’t already have a product name in it. For example:
* Update Firefox to the latest version | Help
* Import Bookmarks from Internet Explorer | Firefox Help
* Zoom in and out of websites on Firefox for mobile | Help
* How do I turn on the Do-not-track feature on mobile? | Firefox for Android Help
* How do I use the Music app on Firefox OS? | Help
* How do I check the battery life? | Firefox OS Help

I am going to also CC Matt, because he’s been renaming articles and probably know a thing or two about title conventions and SEO.

Comment 2

[Matt Grimes [:Matt_G]]

Those look pretty good Bram. I think you covered most of it. The main thing is to provide enough context without being overwhelming. I think you did a good job of that. For some of the longer article titles we could even leave off the word "help" if we need to save space. For example:

* How do I turn on the Do-not-track feature on mobile? | Firefox for Android Help

We could pull out the word help and still get decent CTR. The user probably doesn't care if it comes from the product page or the help site so long as it answers the question and they know it is for right product.

Comment 3

[Ricky Rosario [:rrosario, :r1cky]]

(In reply to Bram Pitoyo [:bram] from comment #1)
> Product landing pages don’t need the word Mozilla Support or Products and
> Services. For example:
> * Firefox Help, NOT Firefox | Mozilla Support
> * Firefox for Android Help, NOT Firefox for Android | Mozilla Support
> * Firefox OS Help, Firefox OS Support

OK, I am confused with this example. Which one is it?

> Article pages need to also be associated with a product, but only if it
> doesn’t already have a product name in it.

I'll do as best as I can here. Initially, I'd like to go with this simplified version:

* If the article has only one product associated, the title will be:
    "<article title> | <product title> Help"
* If the article has more than one product associated, the title will be:
    "<article title> | Mozilla Support" - or should we list all the products? In the future we could track where users came from but then we still have to deal with users that land directly on the article from google, for example.

For now, I'd like to leave out the part of trying to figure out if the product name is in the title. Can we file that as a followup bug?

Comment 4

[Matt Grimes [:Matt_G]]

Hey Ricky. I think Bram is saying that if the article title has the product in it as well, then we don't need to list it a second time. I could be misinterpreting that though.

I am 100% behind your proposal though so that we can move forward. If the document has multiple products (and we don't know what product has been selected via faceting/nav) we can just say Mozilla Support. Bram?

Comment 5

[Ricky Rosario [:rrosario, :r1cky]]

Landed in prod:

https://github.com/mozilla/kitsune/commit/5cc752a85c1d8a34fc459344e41876724ac67d83