Web Governance
Scanning with Web Governance
Google Cloud Platform is the host environment for Web Governance services.
Known and unknown crawlers scan public websites daily. Search engines, such as Google and Bing, and unknown companies crawl websites to gather information and monitor performance. Web Governance does a similar function. This activity has no detectable effect on website performance.
The Web Governance crawler, Monsidobot, does the scan on public websites. The crawler does not access or store confidential data. The only stored data is the names and email addresses of customer users. This data is not public. All collected data and backups remain secure for at least 30 days. The system permanently deletes this data after the client exits, with the exception of logs.
Unless otherwise agreed, the location of customer data depends on the Web Governance branch specified in the contract. Customer data for United States of America (USA) offices and subsidiaries is processed and stored in the USA. Customer data for Australia (AU) offices and subsidiaries is processed and stored in the AU. Customer data for the European Union (EU) and United Kingdom (UK) offices and subsidiaries is processed and stored in the EU.
Log in credentials include a name, email, password, and data-location ID. The Web Governance login service stores these credentials centrally in the EU.
For more information, visit Data hosting and security.
The Web Governance crawler, Monsidobot, does the website scan through a combination of dynamic discovery and an XML sitemap. Dynamic discovery uses a breadth-first approach. The crawler uses the XML sitemap if a user explicitly supplies the sitemap or if the crawler discovers the sitemap through the robots.txt file.
Web Governance requires no installations or additions to the current infrastructure for the website scan to function. The system prioritizes statistics and pages by the number of views. A script is available to add to Google Tag Manager. Refer to Google Tag Manager with Web Governance for configuration instructions.
For instructions on how to set this up, visit Using Google Tag Manager with Web Governance.
To scan password-protected or restricted web pages and documents, the contract with Acquia must permit the action. Users must ensure that the information in these web pages and documents is not confidential. Acquia cannot guarantee an equivalent level of security.
For instructions, visit Configure the scan for password-protected and internal pages.
For more information, visit Quick Scan.
Document scan: This type of scan is done on documents and detects the same issues as the automated scan within documents that are present on the domain.
For more information, visit Document scan.
PDF accessibility scan: This scan detects accessibility issues within PDF documents.
For more information, visit PDF accessibility scan.
Password-protected and internal pages scan: This scan requires Admin setup. When configured, it detects the same website issues as the automated, scheduled scan on password-protected and internal-only pages within the domain.
For more information, visit Configure the password-protected and internal pages scan.
Mobile accessibility scan: When Mobile Accessibility is enabled, an additional scan is done on your website to simulate how it renders on a mobile device. This data is used to pick up device-specific code that only loads when a website opens on a mobile device. Two additional checks are done:
If this content did not answer your questions, try searching or contacting our support team for further assistance.
For more information, visit Quick Scan.
Document scan: This type of scan is done on documents and detects the same issues as the automated scan within documents that are present on the domain.
For more information, visit Document scan.
PDF accessibility scan: This scan detects accessibility issues within PDF documents.
For more information, visit PDF accessibility scan.
Password-protected and internal pages scan: This scan requires Admin setup. When configured, it detects the same website issues as the automated, scheduled scan on password-protected and internal-only pages within the domain.
For more information, visit Configure the password-protected and internal pages scan.
Mobile accessibility scan: When Mobile Accessibility is enabled, an additional scan is done on your website to simulate how it renders on a mobile device. This data is used to pick up device-specific code that only loads when a website opens on a mobile device. Two additional checks are done:
If this content did not answer your questions, try searching or contacting our support team for further assistance.
Web Governance