This article gives instructions on how to set up policies for links.
Article Navigation
Instructions
This section gives instructions on how to add a pre-made links policy to the Monsido scan.
Click Select Domain on the landing page toolbar. The Domain Overview page opens.
Click Open on the same row as the domain name.
The Dashboard for the domain opens.
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.
Click Add new policy.
The New Policy page opens.
Select a pre-programmed policy. There are several pre-made policies for Links:
Links that contain Lorem ipsum
Finds any links that contain “Lorem ipsum” (placeholder text). Helps to spot any overlooked areas where the actual content has not yet been inserted.
Most likely policy type: Unwanted
Subject: Links
Search for [Link Name]
Finds all instances of the inserted link. Useful when an overview of the count and distribution of a link is wanted.
Most likely policy type: Matches
Subject: HTML pages
Additional setup information:
Include words to search for inside links. Monsido has provided four common terms to search for. The user can easily remove or edit them.
Note: By default, the terms will be searched in three cases: lowercase, title case, and uppercase.
Example: click here / Click here / CLICK HERE
Find all Dropbox links
Finds all links that lead to Dropbox.
Most likely policy type: Matches
Subject: Links
Search for unsafe links
Finds all links that start with http instead of https. It is highly encouraged to use https as it is a more secure protocol.
Most likely policy type: Unwanted
Subject: Links
Find all missing banking practice links
Finds all links that do not contain the words banking practice.
Most likely policy type: Matches
Subject: HTML pages
Find all missing financial services guide links
Finds all links that do not contain the words financial services.
Most likely policy type: Matches
Subject: HTML pages
Find all missing privacy policy links
Finds all links that do not contain the words privacy policy.
Most likely policy type: Matches
Subject: HTML pages
Find all missing product disclosure statement links
Finds all links that do not contain the words product disclosure.
Most likely policy type: Matches
Subject: HTML pages
Find all missing terms and conditions links
Finds all links that do not contain the words terms and conditions.
Most likely policy type: Matches
Subject: HTML pages
Assign Rule Operators.
Assign Rules.
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 Monsido 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
Set up policies to find specific links. These are located in the href="" section of the anchor tags on the domain.
To create this policy:
Check the RegEx
Clear the Case sensitive box
Enter the following in the Query field:
href=("|').*SEARCH.*("|')
Replace the word SEARCH in the above line with what you want to find inside the link portion.
An example:
href=("|').*foo.*("|')would match:
<a href="http://test.com/foo">here</a>
<a href="http://foo.com/test">click</a>
<a href="http://test.foo/test">click here</a>
but not
<a href="http://test.com/test">foo</a>
For instructions on how to build a custom policy, see the User Guide chapter:
If the policy you need is difficult to create, contact Support for assistance.
Additional Resources
For more information, see the User Guide chapters:
Note: Regular Expressions in source-code exclusions are not 100% compatible with Monsido Policies. The languages are different (Java and Ruby).
See Monsido for Developers for documentation and advanced help files including SDK information for developers.
For definitions and explanations of acronyms and abbreviations used in the Monsido User Guide, see:
For further assistance, contact the Monsido support team at support@monsido.com or use the Monsido chat and help features inside the application.