(DOCSP-29016): Incorporated Chris's feedback.

Author: corryroot

source/style-guide.txt

@@ -39,7 +39,7 @@ MongoDB external and internal customers.
    however, when writing release notes for any product or service.
 
 :doc:`/style-guide/seo-guidelines`
-   Provides guidance for optimizing your documentations pages for 
+   Provides guidance for optimizing your documentation pages for 
    search.
 
 :github:`User Interface Guidelines </mongodb/leafygreen-ui>`

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

@@ -4,8 +4,6 @@
 Page Metadata Directives
 ========================
 
-.. default-domain:: mongodb
-
 meta
 ----
 
@@ -20,7 +18,7 @@ keywords and descriptions. To learn more, see :ref:`seo-guidelines`.
 	      :description: You can tune the consistency and availability of your application using write concerns and read concerns.
 
 Add the ``.. meta::`` directive on the line below the 
-``.. default-domain::`` directive with a line break in between.
+page title with a line break in between.
 
 Learn more about the ``meta`` directive from the
 `{+docutils+} documentation <http://docutils.sourceforge.net/docs/ref/rst/directives.html#meta>`__.

source/style-guide/seo-guidelines.txt

@@ -4,10 +4,8 @@
 Search Engine Optimization Guidelines
 =====================================
 
-.. default-domain:: mongodb
-
 Search Engine Optimization (SEO) considers the actual terms that users 
-enter into serach engines (keywords) and employs best practices to 
+enter into search engines (keywords) and employs best practices to 
 improve traffic to web pages from search engines. The following 
 guidance should help you optimize your documentation pages for search.
 
@@ -19,26 +17,29 @@ practices:
 
 - Use a maximum of 70 characters.
 
-- Include target keywords.
+- Include target keywords (the actual terms that users 
+  enter into search engines to reach your page).
 
 - Avoid excessive or irrelevant words (keyword stuffing).
 
-- Use a unique title for every page.
+- Strive for unique page titles. Identical titles, even between 
+  documentation sets, might compete in search results.
 
 To learn more, see :ref:`titles-and-headings`.
 
 Alternative Text
 ----------------
 
-Screen readers read alternative text aloud so that users can better
-understand an on-page image. Specify alterative text according to the 
+Screen readers read alternative text for images aloud so that users can 
+better understand an image. Specify alternative text according to the 
 following SEO best practices:
 
 - Use a maximum of 125 characters per image.
 
-- Describe the image with specific language.
+- Describe the image with sufficient detail to understand what it shows.
 
-- If it makes sense, include keywords.
+- If it makes sense, include keywords (the actual terms that users 
+  enter into search engines).
 
 To learn more, see :ref:`write-for-accessibility`.
 
@@ -58,27 +59,26 @@ the following best practices:
   our searchers. For example, add “mongodb atlas course” instead of 
   “Getting Started with Atlas Data Platform”.
 
-To learn more, see :ref:`metadata`.
+While keyword tags are available, some search engines might ignore 
+these tags. To learn more, see :ref:`metadata`.
 
 Descriptions
 ------------
 
-The snippet that appears under the link in the search results can 
-impact SEO. Write these descriptions according to the following best 
-practices:
+The description is a snippet that appears under the link in the search 
+results, which can impact SEO. Write these descriptions according to 
+the following best practices:
 
-- Make the descriptions informative (and enticing if possible).
+- Use a concise description of the page content that is enticing, if 
+  possible.
 
 - Emphasize the “why” for using the page.
 
 - Use a maximum of 155 characters.
 
-- Include target keywords and a call to action.
-
-- Keep the description short, simple, and concise. 
-
-- Concisely, explain the page content.
+- Include target keywords and a call to action (CTA) that prompts the 
+  user to complete their desired task.
 
-- Use unique meta descriptions for every page.
+- Use unique descriptions for every page.
 
 To learn more, see :ref:`metadata`.