CR review

Author: lindseymoore

source/style-guide/seo-guidelines.txt

@@ -70,7 +70,11 @@ practices:
 Titles
 ------
 
-Consider the following four SEO principles when naming a page:
+Search engines weight page titles heavily, as titles are considered most relevant 
+to a user's search engine query. Name pages appropriately to ensure users can find 
+relevant content in the MongoDB Documentation when they use a search engine.  
+
+Consider the following SEO principles when you name a page:
 
 - Title Length
 
@@ -80,34 +84,35 @@ Consider the following four SEO principles when naming a page:
 
 - Disambiguation
 
-Each of the following four subsections describe one of the above principles. 
+The following subsections describe these principles. 
 
 Title Length
 ~~~~~~~~~~~~
 
-Titles should be between 30-60 characters long. Pages with titles longer than 60 characters
-are typically truncated by search engines. A too short title does not convey enough information
-to the search engine, so a page with a too short title might be recommended less by search
-engines. Search engines might also create a longer page title for pages with too short titles.
-
-When considering title length, keep in mind that the product name, version 
-number, and "MongoDB Docs" are automatically appended when the title is passed 
-to a search engine. For example, for a v8.0 Server Manual page titled 
-"Install MongoDB", the title is 15 characters long. The full title passed to search
-engines ("Install MongoDB - Database Manual v8.0 - MongoDB Docs") is 53 characters long.
-The appended additions to the title can add around 18-35 
+Titles should be 30-60 characters long. Search engines often truncate pages 
+with titles longer than 60 characters. Titles with fewer than 30 characters 
+convey limited information to search engines, so search engines recommend these 
+pages less often. Search engines might also create a longer page title for pages with
+titles under 30 characters.
+
+As described in the :ref:`Page Title Structure <titles-page-title-structure>` subsection, 
+the product name, version number, and "MongoDB Docs" are automatically appended to a title 
+when the title is passed to a search engine. For example, for a v8.0 Server 
+Manual page titled "Install MongoDB", the title is 15 characters long. The full 
+title when passed to a search engine ("Install MongoDB - Database Manual v8.0 - MongoDB Docs") 
+is 53 characters long. The appended additions to the title can add about 18-35 
 characters to the title, depending on the length of the product name. 
 
 Standardization
 ~~~~~~~~~~~~~~~
 
-For pages across MongoDB documentation covering similar concepts, use consistent 
+For pages across MongoDB documentation that cover similar concepts, use consistent
 wording in the page titles to ensure a consistent user experience.
 
 For example, multiple pages in the documentation cover the Read CRUD operation. 
-The Read CRUD operation can be referred to as a read, find, or query operation.
-Page titles for pages documenting the Read operation should be consistent in what
-term is used to refer to Read operations, based on what term is most findable. 
+You can refer to the Read CRUD operation as a read, find, or query operation.
+Titles for pages that document the Read operation should use consistent terminology
+to refer to Read operations, based on the most findable term.
 
 Findability
 ~~~~~~~~~~~
@@ -116,18 +121,29 @@ Use the most relevant keywords in a page title. Pay attention to word order in a
 page title. Include the most relevant words at the beginning of the title.
 
 When in doubt, search your potential page title in a search engine. The top five search 
-results should be similar content to the page you are titling. 
+results should resemble the content on your page. 
 
 Disambiguation
 ~~~~~~~~~~~~~~
 
-Differentiate page titles for pages covering commands with same name but different
-functions by adding the command category in the title.
+For pages that cover commands with the same name but different
+functions, add the command categories to the page titles to differentiate the pages.
 
 For example, ``count`` is a database command, aggregation stage, aggregation 
-operator, and  ``mongosh`` method. For Server Manual pages, you can differentiate
-between these pages by including the command category in the title, like
-"count (Database Command)".
+operator, and  ``mongosh`` method. For Server Manual pages, you
+can include the command category in the title, like
+"count (Database Command)," to differentiate between these pages.
+
+.. _titles-page-title-structure:
+
+Page Title Structure
+~~~~~~~~~~~~~~~~~~~~
+
+The product name, version number, and "MongoDB Docs" are automatically appended to 
+Documentation page titles when the title is passed to a search engine.
+
+For example, a v8.0 Server Manual page titled "Install MongoDB" appears as
+"Install MongoDB - Database Manual v8.0 - MongoDB Docs" in search engine results.
 
 General Guidelines
 ~~~~~~~~~~~~~~~~~~

source/style-guide/style/titles-and-headings.txt

@@ -16,8 +16,8 @@ Titles and Headings
 This topic provides guidelines for creating titles and headings in
 documentation.
 
-Why Do Page Titles Matter?
---------------------------
+Why Do Page Titles Matter for SEO?
+----------------------------------
 
 A page title is weighted as most relevant to a user's search engine query. Name
 pages appropriately to ensure users can find relevant content in the MongoDB 
@@ -27,9 +27,9 @@ Page Title Structure
 ~~~~~~~~~~~~~~~~~~~~
 
 The product name, version number, and "MongoDB Docs" are automatically appended to 
-Documentation page titles when they are passed to search engines.
+Documentation page titles when a title is passed to a search engine.
 
-For example, a v8.0 Server Manual page titled "Install MongoDB" will appear as
+For example, a v8.0 Server Manual page titled "Install MongoDB" appears as
 "Install MongoDB - Database Manual v8.0 - MongoDB Docs" in search engine results. 
 
 Capitalization
@@ -88,9 +88,9 @@ Guidelines for Titles and Headings
 ----------------------------------
 
 Use the guidelines in the following subsections to create effective and consistent
-titles and headings. Special considerations for stand-alone articles, product
-guides, and tables, figures, and examples can be found in the Product Guides and
-Tables, Figures, and Headings subsections. 
+titles and headings. You can find special considerations for stand-alone articles, product
+guides, tables, figures, and examples in the :ref:`Product Guides <titles-product-guides>` and
+:ref:`Tables, Figures, and Headings <titles-table-figures-ex>` subsections. 
 
 .. _title-grammar:
 
@@ -239,6 +239,8 @@ Support site or in other collections of documentation:
 - Start with the highest level of heading that is approved for headings
   (for example, h3), and do not skip heading levels.
 
+.. _titles-product-guides:
+
 Product Guides
 ~~~~~~~~~~~~~~
 
@@ -257,6 +259,8 @@ when creating titles and headings for sections in product guides:
 
 - Define consistent heading levels, and do not skip levels.
 
+.. _titles-table-figures-ex:
+
 Tables, Figures, and Examples
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~