---
title: "Add, edit, or remove a domain"
date: "2021-08-30T09:37:58+00:00"
summary: "Learn how to add, edit, or remove domains, configure scan settings, and customize features like accessibility, readability, and analytics."
image:
type: "page"
url: "/web-governance/add-edit-or-remove-domain"
id: "e67f1800-be4e-4ce1-ab58-30c78c73c84c"
---

Table of contents will be added

Introduction
------------

This document provides instructions for admin users on how to add, edit, and remove a domain.

Add a domain
------------

This section provides instructions for admin users on how to add a domain.

1.  Navigate to the _Domain Overview_ page.
2.  Click **+Add Domain** on the top right side of the page.
    
    The system opens the _New Domain_ page.
    
3.  Provide the requested information.

### Domain Details section

Provide the following information in the **Domain Details** section.

![The Domain Details section on the Edit Domain page.](https://acquia.widen.net/content/e12aa8a4-0c72-4909-b386-0646a45f477e/web/WebGov_EditDomain-DomainDetailsSection.png?w=720&itok=3rT8Z-6c)

*   **Title (required field)**: Click in the field and type in a title for the domain.
*   **UR**L **(required field)**: Click in the field and enter the website URL. Keep in mind that website addresses that end in .com and .eu, for example, are two different domains. Each domain has a unique script and needs to be entered as a separate domain in the list.
    
    Note
    
    The scan also includes all pages that are linked to the URL.
    
*   **CMS**: Click to expand the list and select the CMS. If the CMS is not on the list, contact the [support team](mailto:webgovsupport@acquia.com) and submit a request for them to add it. For advanced help files, visit [CMS Integration](/node/57881).
    
    Note
    
    Some CMS providers have implemented scan rate limiting on their users.
    
    For more information, visit [CMS rate limiting on bots and crawlers](https://docs.acquia.com/acquia-optimize/help/59256-cms-rate-limiting-bots-and-crawlers).
    
*   **CMS URL**: Click in the text field and type in the base URL for the CMS page. This field is required.
*   **Language**: Click to expand the list and select the main language for the site. This provides information to the scan about which dictionary needs to be used to detect spelling and other errors. Words on a page that are written in another language are usually tagged as misspelled words. For instructions on how to repair the HTML code for this Accessibility error, visit the [HTML School](https://www.w3schools.com/tags/att_lang.asp) site (external link).

### Scan section

This section provides instructions on how to fill out the _Scan_ section.

![The Scan section on the domain setup page.](https://acquia.widen.net/content/54faf2f1-79e1-4f6d-9180-d637ade3e467/web/Mon_EditDomain-ScanSection.png)

**Crawl Automatically**: Toggle the switch to ON to set up a schedule for recurring scans. Toggle the switch to **OFF** to scan manually when needed.

*   **Scan Frequency**: Click the drop-down arrow and select the scan frequency.
    
    The available options for the scan frequency are:
    
    *   Weekly
    *   Every 2 weeks
    *   Every 4 weeks
    *   Every 8 weeks
    *   Every 12 weeks
    
    Note
    
    This is an add-on. If this option is not available and you wish to change your scan frequency, contact your sales representative to upgrade the account. The default scan frequency is weekly.
    
*   **Day**: Click the drop-down arrow and select the day of the week for the recurring scan.
*   **Time**: Click in the number field and enter the time of day (12-hour clock) and then choose AM for 00:00-11:59 or PM for 12:00 to 23:59.

**Connections per minute**: Click the drop-down arrow and select _Connections per minute_. The choices are:

*   Slow: 15 connections per minute
*   Normal (recommended): 60 connections per minute
*   Faster: 90 connections per minute
*   Very fast (be cautious): 120 connections per minute
*   Superfast (advanced users only) 180 connections per minute

Note

*   Some CMS providers have implemented scan rate limiting on their users. For more information on why it can be faster to reduce the connection speed, visit [CMS rate limiting on bots and crawlers (FAQ)](/node/59256)
*   The server answer time may be adversely affected if the _connections per minute_ setting is _Faster_ or higher. At these settings, the speed of the scan may not change if the server is slow to respond.
*   The scan can do a maximum of five scans per IP address simultaneously. When several websites use the same IP, the scan uses the slowest _connections per minute_ setting from the IP address group.

### Max

**Max scanned pages**: Enter the maximum number of pages to do a scan on, as specified on your Acquia contract.

### Crawl (Scan) Options

This section provides instructions on how to fill out the _Crawl (scan) Options_ section.

![The Scan section on the domain setup page.](https://acquia.widen.net/content/54faf2f1-79e1-4f6d-9180-d637ade3e467/web/Mon_EditDomain-ScanSection.png)

Toggle the switches **ON** to activate the different scan options.

*   **Scan subdomains**: Toggle the switch **ON** to include subdomains in the scan.
*   **Spelling ignore capitalized words**: Toggle the switch **ON** to ignore words that begin with a capital letter.
    
    Note
    
    Words that the user includes in the dictionary are case-sensitive. To instruct the scan to ignore words that are written in all caps, and bypass the need to, for example, add the word to the dictionary, toggle this switch to **ON**.
    
*   **Case sensitive URLs**: Toggle the switch **ON** to include case-sensitive URLs in the scan.
    
    This is set to the optimal position by default.
    
    Example **OFF**: http://monsido.com/Foo/Bar is seen as the same link as:   
    http://monsido.com/foo/bar.
    
    Example **ON**: The same links above will register as two different links.
    
    Note
    
    In the **OFF** position, the scan sees all URLs as lowercase, regardless of how they are written on the target website. Turn **OFF** only in rare cases where the target website does not recognize caps and reads all links in lowercase, which results in duplicates in the flagged scan issues. This is an advanced configuration that should normally be left to the default setting.
    
    The recommended solution is to disable the case-sensitive feature and use only regex.
    
*   **Render pages and execute JS while crawling**: Toggle the switch **ON** to render pages and execute JavaScript during the scan.
    
    When this option is turned **ON**, the website renders pages and executes JavaScript during the scan. This allows the scan to take into account any changes caused by Javascript during a website scan.
    
    Note
    
    If the Accessibility feature is enabled, changes caused by JavaScript are automatically accounted for by default.
    
*   **Mark 403 as broken link**: Toggle the switch **ON** to mark links on pages that return error 403 (forbidden errors) as a broken link.
*   **Ignore canonical URLs**: Toggle the switch **ON** to instruct the scan to ignore canonical URLs.
    
    _More info_: A canonical URL is the URL of the page that Google determines is most representative, taken from a set of duplicate pages on your website.
    
*   **Use language attribute**: Turn the switch **OFF** or **ON**. When it is ON, the scan does not try to auto-detect the page language. This means that the spell check is only done for the language specified in the lang attribute.
    
    The _Use Lang Attribute_ feature allows the scanner to use the correct spell check for HTML pages that have multiple languages.
    
    Note
    
    The primary language of the HTML page must be correctly defined as a lang attribute on the `<html>` tag. Additionally, each subsection of the page that is in any other language must be wrapped in a tag with a proper lang attribute value.  
    See below for an example:
    
    *         <html lang=en">
                <head>
                  <title>Hello World in other languages</title>
                </head>
                <body>
                  <h1>Hello World in other languages</h1>
                  <p>
                    Spanish: <span lang="es">Hola Mundo</span><br>
                    Danish: <span lang="da">Hej verden</span><br>
                    French: <span lang="fr">Bonjour le monde</span>
                  </p>
                </body>
              </html>
        
    

_Remember_: When enabled, the scan does not auto-detect the page language. For example, spell checks are always for the language specified in the lang attribute.

### Statistics feature options

Some websites - including CP-built sites - have URLs that use a mix of lowercase and uppercase letters, for example `https://www.example.com/TestPage`

While the crawler saves the URL as all lowercase in our database, the Statistics module provider, Matomo, does not follow that practice and saves it as written by the website. This results in a scenario where the scan cannot map page statistics for the page: `https://www.example.com/TestPage` to the page in the database because it was saved as: `https://www.example.com/testpage`.

This option forces Matomo to put all URLs in lowercase so that they match the entries in the Web Governance database.

*   Convert all URLs to lower case: Toggle the switch **ON** to convert all URL addresses to lowercase.

### Advanced Domain Options section

Provide the following information in the _Advanced Domain Options_ section.

![The Advanced Domain Options section on the domain setup page.](https://acquia.widen.net/content/3dd70796-f804-450a-b340-8b6544861259/web/Mon_Opt_AdminSettings-EditDomain-AdvancedDomainOptions.png)

*   ### **Path Constraints**
    
    *   **Search**: Enter a search parameter for matching strings within the _Constraint Patterns_ list.
    *   **Constraint pattern**: Enter a constraint pattern.
    *   **\+ Add**: Click + to add a new _Constraint pattern_. An empty row is added to the list.

For full instructions, visit [Path constraints and link exclusions](/node/58571).

### Advanced domain options

This section provides information for admin users on the available advanced domain setting options.

![The Advanced Domain Options section on the domain setup page.](https://acquia.widen.net/content/3dd70796-f804-450a-b340-8b6544861259/web/Mon_Opt_AdminSettings-EditDomain-AdvancedDomainOptions.png)

**Path Constraints**

Use _Path Constraints_ to instruct the scan to only process parts of a domain. The scan regards URLs that match the pattern as internal on the site, and URLs that do not match are regarded in the same way as external links.

A Path Constraint can be a word or a regular expression. In most cases, users set up _Path Constraints_ to:

*   Restrict the scanner to only recognize parts of a site with a pattern such as ^/en  
    This instructs the scan to handle any URL that does not begin with /en, for example,   
    `http:/ /foo.com/fr/bar` as an external link. For example, the crawler tests the link but does not follow any links on `http:/ /foo.com/fr/bar`.
*   Instruct the scan to ignore parts of the site with a pattern. For example `!^/fr`.  
    This instructs the scan to handle any URL that begins with `/fr`, for example, `http:/ /foo.com/fr/bar`   
    as an external link. This means that the scan tests the link but does not follow any links on   
    `http:/ /foo.com/fr/bar`.

The difference between the two is that in the first case ALL pages under `/en` are scanned and nothing else. In the second example, all pages EXCEPT `/fr` are scanned.

Important

When you use Path constraints, make sure that the URL for the domain is set to a page that matches the constraint.

If you do not do this, the scan will only run on one page, since the scanner cannot proceed to any other page than the page it starts on.

For example. with a constraint of "^/en/booking", starting the crawler on   
`http://foo.com`   
will not work. The crawler will request   
`http://foo.com`  
and it will receive the page, and find that no links match   
`http://foo.com/en/booking`  
and the result is that only the first page is scanned.

For full instructions, visit [Path constraints and link exclusions](/node/58571).

**Link Exclusions**

You can choose to exclude a word or a regular expression. Use _Link Excludes_ to instruct the crawler to completely ignore a link on the pages. Pages that match the pattern are not tested.

Use _Link Excludes_ to:

*   Filter out print pages with a pattern such as _print=true_
    
    This instructs the scan to ignore (and not test) any URL with the pattern, for example:
    
    `http://foo.com/bar?print=true`
    
*   Filter out redirected login pages with a pattern such as:
    
    `login.aspx?return_url=zyx`
    
    This instructs the scan to ignore all URLs with the pattern, for example `http://foo.com/bar/login.aspx?return_url=zyx`
    
    _Tip!_ If "Scan subdomains" is turned on for the domain, use the **§** sign in front of the exclude pattern to match URLs that use the full string instead of the relative one.
    
    For example, to exclude the scan for the "blog" subdomain, enter the pattern:
    
        §http://blog.foo.bar
    
    For full instructions, visit [Path constraints and link exclusions](/node/58571).
    

**Internal URLs**

Configure internal URLs with the following options in this section:

*   **Operator**: Click the drop-down arrow to select _Contains_, _Starts with_, or _Regex_.
*   **Url**: Type a URL in the field.
*   **Delete**: Click the trashcan icon to delete the row.
*   **\+ Add**: Click to add a new _Input Selector_. An empty row appears in the list.

### Login Type section

This section provides instructions on how to fill out the _Login Type_ section.

![The Login Type section on the Edit Domain page.](https://acquia.widen.net/content/41ca9737-bc5f-400e-9ea0-1aa55ce8e7e3/web/WebGov_EditDomain-LoginTypeSection.png?w=720&itok=45igk520)

Click the drop-down arrow and select a login type. The choices are:

*   **None:** The site does not require user logins.
*   **Form:** The field expands. The expanded input fields specify the CSS selectors that identify the various form fields and buttons. The following input fields open:
    *   **Input selector**: (Required field) Enter the CSS ID or class selector to search for.
    *   **Default Value**: Click to hide or show the input text. Click in the dialog box to set a default value for the selector.
    *   **Delete**: Click the trashcan icon to delete the row.
    *   **\+ Add**: Click to add a new _Form_. An empty row appears in the list.
    *   **Submit selector**: (Required field) Click in the dialog box and type in a string (without spaces) to identify the submit button for the form.
    *   **Verify URL**: (Required field) Click in the dialog box and type in a URL address that the user will redirect to if the form is valid.
*   **Office 365 (BETA): Beta**: This field allows information for Office 365 login.
    *   **Email**: Click in the dialog box and type in a valid Office 365 email address.
    *   **Password**: Click in the dialog box and type in the Office 35 password for the email account.
    *   **Remember me**: Turn the switch **ON** to remember user credentials.
*   **Basic Auth:**
    *   **Username**: Click in the input field and type in a username field identifier.
    *   **Password**: Click in the input field and type in a password field identifier.
    *   **Hosts**: Click in the input field and type in the URL to the host website.
*   **Custom Multistep**: This option covers login flows that require special integration. Contact the [support team](mailto:support@monsido.com) for assistance.
    *   **Verify URL**: Click in the dialog box and type in a URL address for the user to redirect to if the login is valid.
    *   **Username**: Click in the input field and type in a username field identifier.
    *   **Password**: Click in the input field and type in a password field identifier.
    *   **JS**: This is a field to enter JavaScript strings for the scan to identify.
    *   **Delete**: Click the trash can icon to delete the row.
    *   **\+ Add**: Click to add a new _Custom Multistep_. An empty row appears in the list.

### Features section

This section provides instructions on how to complete the _Features_ section.

![The Features section on the Edit Domain page. The fields are described in the document text.](https://acquia.widen.net/content/a89364df-f6f3-4e11-93d0-7e06107b7773/web/WebGov_EditDomain-FeaturesSection.png?w=720&itok=MHWsRsNG)

*   **Accessibility**: Click the drop-down arrow and select the accessibility level that is desired or required for the website. Level AA of WCAG 2.1 is the legal requirement to be considered accessible. 
    
    Important
    
    When you change the accessibility level, the existing Accessibility Score scan information is erased and the new standard starts over from the beginning with the next scan. _**All of the history is lost.**_ It is advised to activate a new level only when you are ready to make the updates needed, or if it becomes a legal requirement for your location/organization.  
    If you change the scan to _**Exclude checks that require manual review**_, you might not see other potential accessibility violations on your website.
    
    Check with your legal department to find out which level is needed for your industry or location to be considered accessible. 
    
*   **Scan exclusions**: Click the drop-down arrow and select domains to exclude from the scan.
    
    For more information, visit [Scan exclusions](/node/58591).
    
*   **PDF accessibility**: Click the drop-down arrow and select the level of accessibility for the PDF pages included in the scan. The choices are WCAG 2.0 and WCAG 2.1.
*   **Readability**: Click the drop-down arrow and select a readability standard to determine the level of difficulty of the website text, to ensure that the correct audience is targeted. The choices are Flesch Kincaid and LIX.
    
    Note
    
    *   The two types of readability tests that we use are Flesch Kincaid for English and LIX for foreign languages.
        *   The **Flesch–Kincaid** readability test for English text measures word length, number of syllables per word, and sentence length. The formula for the Flesch readability score (FRES) test is as follows:
            
            **206.835 - 1.015 (total words/total sentences) - 84.6 (total syllables/total words)**
            
        *   The **LIX** method is used for foreign languages and the readability formula is as follows:  
            ​**LIX = A/B + (C x 100)/A**, where  
            ​**A** = Number of words  
            ​**B** = Number of periods (defined by period, colon, or capital first letter)  
            ​**C** = Number of long words (More than 6 letters)
    
    For more information, visit:
    
    *   [Quality Assurance Readability setup](/node/60026)
    *   [Quality Assurance Readability](/node/58816)
    
    **Minimum words**: Enter the minimum number of words that a page should contain for the readability score to begin calculating. Pages that have fewer words than indicated are not included in the readability score.
    
*   **Statistics**: Toggle **ON** to turn on this feature and begin to track website visitor statistics.
    
    For more information, visit [Statistics setup](/node/60241).
    
*   **PageCorrect**: Toggle **ON** to turn on this add-on. Click the link to navigate to the _PageCorrect Settings_ page.
    
    PageCorrect allows users to identify and correct website errors such as quality assurance errors and accessibility issues.
    
    For more information, visit [PageCorrect setup](/node/60041).
    
*   **Data Privacy**: Toggle the switch **OFF** or **ON**. Click the link to navigate to the _Domain Data Privacy Settings_ page.
    
    The _Data Privacy_ module identifies potential data privacy issues. It can serve as a form of documentation that allows website owners to show their efforts to be compliant with local regulations.
    
    For more information, visit [Data privacy setup](https://docs.acquia.com/acquia-optimize/data-privacy-setup).
    
*   **Scan documents**: Toggle the switch **ON** to include documents in the scan.
    
    The scan is a powerful tool that does a scan on all pages of a website. With _Scan documents_ selected, documents on the website are included. The document scan identifies all of the same types of issues as a domain scan.
    
*   **PageAssist**: Toggle the switch **ON** to activate. Click the link to navigate to the _PageAssist Settings_ page.
    
    PageAssist allows website visitors to make custom visual adjustments to suit their unique requirements.
    
    For more information, visit [PageAssist setup](/node/81741).
    
*   **Consent Manager**: Toggle the switch **ON** to activate.
    
    The Consent Manager module includes everything that you need to classify and set up user cookie acceptance and website cookie banners. This module also includes automatic cookie scan detection and cookie maintenance.
    
    For more information, visit [Consent Manager setup](/node/81751).
    

### Domain Groups section

Set up groups to assign specific users to a subset of pages on one or more domains that the scan has been done on. Created groups appear under the domain name.

For more information, visit [Create and configure groups](/node/58456).

### Users section

The _Users_ section shows a list of users with access to the interface. This section provides instructions on how to add permissions to users.

The list is presented in table format.

![Image that shows the Users page.](https://acquia.widen.net/content/a004d8aa-b994-45b3-9918-cb4260c8eee6/web/Mon_Userslist_ConfigureDomainsScan.png)

The table column headers are:

*   **User**: The Username for the user.
*   **Visible**: Tick the box to make the control panel visible to the user.
*   **Send report**: Tick the box to send reports to the user.
*   **Admin**: Tick the box to give the user admin permissions. Admins can add, edit, and delete.

Click **Save**. The settings pane closes and the _Domains_ page is visible.

For more information, visit:

*   [Create and configure users](/node/58526)
*   [Users](https://docs.acquia.com/acquia-optimize/docs/admin/users)

Edit a domain
-------------

This section provides information for admin users on how to edit a domain.

1.  Navigate to the _Domain Overview_ page.
2.  Click **Action** on the same row as the domain and select **Edit Domain** from the expanded list of options. 
    
    The system opens the _Edit a domain_ page.
    
3.  Make edits to the page as needed. Refer to the previous section _Add a Domain_ for instructions on how to fill in the fields
4.  Save the changes.

Remove a domain
---------------

This section provides information for admin users on how to remove a domain.

1.  Navigate to the _Domain Overview_ page.
2.  Click **Action** on the same row as the domain and select **Remove Domain** from the expanded list of options.
    
    The system opens a confirmation dialog.
    
3.  Type "Delete" in the space provided and then click **OK**. 
    
    The dialog closes and the domain and all related domain groups are gone from the list.