IA-related updates to SEO and metadata content (#169)

* added IA-related updates to SEO and metadata content

* SEO, links, and URLs updates

* Update source/style-guide/seo-guidelines.txt

Co-authored-by: corryroot <[email protected]>

* Update source/style-guide/seo-guidelines.txt

Co-authored-by: lindseymoore <[email protected]>

* Update source/style-guide/seo-guidelines.txt

Co-authored-by: lindseymoore <[email protected]>

---------

Co-authored-by: corryroot <[email protected]>
Co-authored-by: lindseymoore <[email protected]>

Author: 3 people

source/style-guide/markup/directives/metadata.txt

@@ -43,3 +43,15 @@ Overrides the document title.
 
 Learn more about the ``title`` directive from the
 `{+docutils+} documentation <http://docutils.sourceforge.net/docs/ref/rst/directives.html#metadata-document-title>`__.
+
+facet
+-----
+
+Adds a taxonomy value of product, programming language, or genre.
+
+.. code-block:: rst
+
+   .. facet::
+
+Learn more about the ``facet`` directive from the
+`Taxonomy tagging instructions <https://wiki.corp.mongodb.com/display/DE/Taxonomy+tagging+instructions>`__.

source/style-guide/seo-guidelines.txt

@@ -6,7 +6,7 @@ Search Engine Optimization Guidelines
 
 Search Engine Optimization (SEO) considers the actual terms that users 
 enter into search engines (keywords) and employs best practices to 
-improve traffic to web pages from search engines. The following 
+improve traffic to web pages from search engines.  Close attention to page metadata and keywords in the page content can improve page placement in search results.  The following 
 guidance helps you to optimize your documentation pages for search.
 
 .. important::
@@ -21,7 +21,7 @@ Keywords
 --------
 
 You can add the actual terms that users enter into search engines 
-(keywords) to the body of your page to improve its SEO.
+(keywords) to the body of your page to improve its SEO.  Google Search Console provides details about the keywords our users enter and you can request this information from the IA and SEO teams.  
 
 .. important::
 
@@ -66,8 +66,8 @@ Use the following SEO best practices for page and subsection titles:
 
 - Avoid excessive or irrelevant words (keyword stuffing).
 
-- Strive for unique page titles. Identical titles, even between 
-  documentation sets, might compete in search results.
+- Use unique page titles. Identical titles, even between 
+  documentation sets, compete in search results.
 
 To learn more, see :ref:`titles-and-headings`.
 
@@ -91,7 +91,7 @@ Descriptions
 ------------
 
 The description is a snippet that appears under the link in the search 
-results, which can impact SEO. Write these descriptions according to 
+results and is essential for SEO. Write these descriptions according to 
 the following best practices:
 
 - Use a concise description of the page content that is enticing, if 

source/style-guide/style/links-and-cross-references.txt

@@ -27,7 +27,7 @@ outside of the current page or section. Links may be:
   - :ref:`aggregation-expression-operators`
   - :ref:`aggregation-pipeline-operator-reference`
   - `Practical MongoDB Aggregations
-    <https://www.practical-mongodb-aggregations.com>`__"
+    <https://www.practical-mongodb-aggregations.com/>`__"
 
 - Explicit hyperlinks to specific URLs. For example, a link to a GitHub
   repository.
@@ -122,7 +122,7 @@ link and where it will take them:
 - If a link will take a user away from the MongoDB documentation, such
   as to GitHub or Wikipedia, make the target site clear in the link
   text.
-- Avoid "Click here." It's bad for search engine optimization and
+- Avoid "Click here." It's bad for search engine optimization, screen readers, and
   doesn't adequately describe the target.
 
 Link text should begin with the purpose of the cross-reference. For
@@ -179,6 +179,8 @@ refactor can potentially break links if the page is renamed or removed.
 Link and Cross-Reference Examples
 ---------------------------------
 
+All MongoDB URLs should have a trailing slash to match standards for canonical URLs used for SEO purposes.
+
 .. list-table::
    :widths: 50 50
    :header-rows: 1

source/style-guide/style/urls.txt

@@ -25,9 +25,9 @@ following domains for demonstration and documentation:
    The following URLs and email addresses would be acceptable in
    documentation:
 
-   - http://www.example.com
-   - http://ldap.example.net
-   - http://mongodb.example
+   - http://www.example.com/
+   - http://ldap.example.net/
+   - http://mongodb.example/
    - [email protected]
    - [email protected]