From MozillaWiki
Jump to: navigation, search

This page contains all of the important details for re-organizing's site architecture.


Currently, the mozilla/firefox product site maintains a low impact site architecture with nearly all pages coming off of /firefox, which means they are all equal in terms of importance. This reduces the authority of pages in search and makes it a lot harder for users coming into the site to find their way to the root page of a product like Firefox.


Content silos will greatly help the Firefox product site score better in search engines by distributing page authority across the site more strategically.

The goal of this project is to improve the /firefox site's architecture by creating content silos. Doing this will benefit and improve how users and search engine find their way around your site.

Content silos:

  • get the best, most relevant content in front of users
  • reduces the number of times users (and search engines) must click to find content
  • improve indexation metrics, such as the number of pages generating search engine traffic and the number of pages in a search engine index

Think of silos as a chapters in a book. On a website a silo represents a group of themed or subject-specific content (e.g. Firefox features). The reason this content grouping into silos is helpful towards SEO is that search engines award "keyword" relevancy within their index based on the root page and then throughout the rest of the site starting with the most supporting relevant content.

Well ranked websites and blogs are founded upon the concept that a website should physically be organized like a doctoral dissertation:

  • title
  • abstract
  • table of contents
  • chapters by theme with references & footnotes (links to SUMO, AMO, etc.)

More resources on content silos:


  • The goal of the Upgrade Campaign is to move over the 30% of ADUs we still have on 3.6, with the majority moved over by the end of the quarter.



  • Responsible: CB
  • Accountable: John Slater
  • Support: LForrest
  • Consult: LMesa, GJimenez, JFu, CCollins
  • Informed: JFinette, PFinch


  • Prod URL:
  • Stage URL:
  • Code Repo:
  • L10N Repo: No l10n at this time
  • Code: HTML, javascript
  • Product Owner: John Slater
  • Dev Team: Firefox website team; Chrissie
  • IRC Channel: #www on
  • Team: website team; Chrissie

Visual Assets


Tracking Bug 708439

Future Phase(s):