This article gives information on how to add a placeholder text policy to the Acquia Optimize scan.

Instructions¶

This is the most basic policy for websites containing placeholder text that should have been changed or removed before publishing.

1. Click Select Domain from the Acquia Optimize landing page. 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. Select a pre-programmed placeholder text policy from the list. The most common pre-programmed placeholder text policies used within Acquia Optimize are:

   • Text that starts with Lorem ipsum

     Finds any text that starts with “Lorem ipsum” (the placeholder text). Helps to spot any overlooked areas where the actual content is missing.

     Most likely policy type: Unwanted

     Subject: HTML pages

6. Assign Rule Operators.
7. Assign 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¶

• 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¶

• 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¶

This section gives a common example for a placeholder text policy.

Lorem ipsum¶

This is the simplest of placeholders to set up a policy for. To make this policy, check the RegEx and clear the Case sensitive box and enter the following in the Query field:

Lorem ipsum

Insert [something] here

This policy finds every page or document that contains a phrase that contains the word ''insert'', 1-3 other words, and the word ''here''. Examples of what would be found include:

• "Insert heading here"
• "Insert summary or text here"

To make this policy, check the RegEx, clear the Case sensitive box, and then enter the following in the Query field:

Insert(\s*\w+\s*){1,3}here

Adjustments:

• The above will match between 1 and 3 words between "insert" and "here". Change the numbers in {1,3} to other values as needed.

For instructions on how to build a custom policy, see the User Guide chapter: Create your own Policy. If the policy you need is difficult to create, contact Support for assistance.

Additional Resources¶

For more information, see the User Guide chapters:

• Configure Policies
• Policies: Pre-made
• Policies: CSS Selectors
• Policies: Links
• Policies: Titles
• Policies: Placeholder text
• Policies: U.S. Telephone Numbers.

See Acquia Optimize for Developers for documentation and advanced help files including SDK information for developers.