Introduction¶

This article provides information on how to add a pre-made US Phone Number policy to the Acquia Optimize scan.

Instructions¶

How to add a US phone number policy.

1. From the Acquia Optimize Domain Overview, click Select Domain. The Domain Overview page opens.

   

2. Click Open on the same row as the domain name. 

   

   The Dashboard for the domain opens.

   

3. Click the Global Policies Overview button (mallet icon) on the top menu bar.

   

   Alternatively, click on the header of the Content Policies section.

   

   The Global Policies page opens.

   

4. Click Add new policy.

   

   The New Policy page opens.

   

5. Click Create your own Policy. See below for examples.

   For more information, see the user guide article:

   Create a custom policy.

6. Assign rule operators. See the Rule operators section in this document for a list of available rule operators.
7. Assign rules. See the Rules section of this document for a list of available rules.
8. Click Save to save the changes. A dialog box opens.
   • In the dialog box, enter the policy Name (required) and Note if needed and then click Save.
   • From the options at the top of the page, select +Add rule to the policy. Repeat the steps above to add as many rules as needed.
   • Click Save. The Policy List is open and the new policy is present. A Policy scan begins automatically.

Rule operators¶

This section provides a list of available rule operators.

• Starts with: Policy will search for any snippet starting with the inserted text.
• Contains: Policy searches for any instances of the inserted text (single word).
• Contains words: Policy searches for multiple words. Use commas to separate the words.
• Contains sentence: Policy searches for any instances of the inserted sentence or text.
• Ends with: Policy will search for any snippet ending with the inserted text.
• Equal: Policy searches for an exact match for the inserted text or value. Example: “Monsido” - match. “About Monsido” - no match.

• Regex: Use regular expressions to define what should be searched for.

  Note

  Regular Expressions in source-code exclusions are not 100% compatible with Acquia Optimize Policies. The languages are different (Java and Ruby).

• Conforms with: Use regular expressions to define the correct structure or form of the inserted value.
• Less than: Find any results less than the inserted value.
• Less than or equal: Find any results less than or equal to the inserted value.
• Greater than: Find any results greater than the inserted value.
• Greater than or equal: Find any results greater than or equal to the inserted value.
• (Meta header) Date age greater than: Find meta tags older than the inserted value. Choose the time interval that matches the way your meta tag dates are written.
• (Meta header) Date age less than: Find meta tags younger than the inserted value. Choose the time interval that matches the way your meta tag dates are written.
• CSS selector: Policy will search for the inserted CSS selector.

Rules¶

This section provides a list of available rules.

• Page HTML: Search for text in the entire domains html.
• Page URL: Set a rule for internal page URLs.
• Text: Search for text excluding CSS and HTML tags.
• Page title: Search for text in the page title (title is not the header).
• Page title length: Define when the rule should apply for the title.
• Heading text: Search for text in headers (h1,h2,h3,h4,h5,h6).
• Heading text length: Define when the rule should apply header texts.
• Meta header: Search for meta header tags, that matches query.
• Meta header length: Define when the rule should apply for meta headers.
• Link text length: Define when the rule should apply for link texts.
• External link count: Define when the rule should apply for external links.
• File size: Search files across selected domains.
• Image size: Search for images across selected domains.
• Image text: Search for images with this name.
• Image text length: Define when the rule should apply for image texts.
• Readability level: Search for text that is in compliance with a school degree.

Custom examples¶

The Policies module can be used to find US phone numbers that are formatted in different ways.

A phone number policy can be set up to instruct the scan to locate US telephone numbers that are NOT formatted in the following way: (123) 567-7890. Below are some examples of numbers that violate the policy:

• 123-456-7890
• 123 456-7890
• 123 456 7890
• 123-4567890

For more information, see the user guide article:

Create a custom policy.

Additional resources¶

If the policy you need is difficult to create, contact Support for assistance.