help.siteimprove.com
Open in
urlscan Pro
18.196.185.48
Public Scan
URL:
https://help.siteimprove.com/support/solutions/articles/80001086121-site-content-settings
Submission: On June 20 via api from NL — Scanned from NL
Submission: On June 20 via api from NL — Scanned from NL
Form analysis 7 forms found in the DOM
<form>
<fieldset>
<legend class="visuallyhidden">Consent Selection</legend>
<div id="CybotCookiebotDialogBodyFieldsetInnerContainer">
<div class="CybotCookiebotDialogBodyLevelButtonWrapper"><label class="CybotCookiebotDialogBodyLevelButtonLabel" for="CybotCookiebotDialogBodyLevelButtonNecessary"><strong
class="CybotCookiebotDialogBodyLevelButtonDescription">Necessary</strong></label>
<div class="CybotCookiebotDialogBodyLevelButtonSliderWrapper CybotCookiebotDialogBodyLevelButtonSliderWrapperDisabled"><input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonNecessary"
class="CybotCookiebotDialogBodyLevelButton CybotCookiebotDialogBodyLevelButtonDisabled" disabled="disabled" checked="checked"> <span class="CybotCookiebotDialogBodyLevelButtonSlider"></span></div>
</div>
<div class="CybotCookiebotDialogBodyLevelButtonWrapper"><label class="CybotCookiebotDialogBodyLevelButtonLabel" for="CybotCookiebotDialogBodyLevelButtonPreferences"><strong
class="CybotCookiebotDialogBodyLevelButtonDescription">Preferences</strong></label>
<div class="CybotCookiebotDialogBodyLevelButtonSliderWrapper"><input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonPreferences" class="CybotCookiebotDialogBodyLevelButton CybotCookiebotDialogBodyLevelConsentCheckbox"
data-target="CybotCookiebotDialogBodyLevelButtonPreferencesInline" checked="checked" tabindex="0"> <span class="CybotCookiebotDialogBodyLevelButtonSlider"></span></div>
</div>
<div class="CybotCookiebotDialogBodyLevelButtonWrapper"><label class="CybotCookiebotDialogBodyLevelButtonLabel" for="CybotCookiebotDialogBodyLevelButtonStatistics"><strong
class="CybotCookiebotDialogBodyLevelButtonDescription">Statistics</strong></label>
<div class="CybotCookiebotDialogBodyLevelButtonSliderWrapper"><input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonStatistics" class="CybotCookiebotDialogBodyLevelButton CybotCookiebotDialogBodyLevelConsentCheckbox"
data-target="CybotCookiebotDialogBodyLevelButtonStatisticsInline" checked="checked" tabindex="0"> <span class="CybotCookiebotDialogBodyLevelButtonSlider"></span></div>
</div>
<div class="CybotCookiebotDialogBodyLevelButtonWrapper"><label class="CybotCookiebotDialogBodyLevelButtonLabel" for="CybotCookiebotDialogBodyLevelButtonMarketing"><strong
class="CybotCookiebotDialogBodyLevelButtonDescription">Marketing</strong></label>
<div class="CybotCookiebotDialogBodyLevelButtonSliderWrapper"><input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonMarketing" class="CybotCookiebotDialogBodyLevelButton CybotCookiebotDialogBodyLevelConsentCheckbox"
data-target="CybotCookiebotDialogBodyLevelButtonMarketingInline" checked="checked" tabindex="0"> <span class="CybotCookiebotDialogBodyLevelButtonSlider"></span></div>
</div>
</div>
</fieldset>
</form><form><input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonNecessaryInline" class="CybotCookiebotDialogBodyLevelButton CybotCookiebotDialogBodyLevelButtonDisabled" disabled="disabled" checked="checked"> <span
class="CybotCookiebotDialogBodyLevelButtonSlider"></span></form><form><input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonPreferencesInline" class="CybotCookiebotDialogBodyLevelButton CybotCookiebotDialogBodyLevelConsentCheckbox" data-target="CybotCookiebotDialogBodyLevelButtonPreferences"
checked="checked" tabindex="0"> <span class="CybotCookiebotDialogBodyLevelButtonSlider"></span></form><form><input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonStatisticsInline" class="CybotCookiebotDialogBodyLevelButton CybotCookiebotDialogBodyLevelConsentCheckbox" data-target="CybotCookiebotDialogBodyLevelButtonStatistics"
checked="checked" tabindex="0"> <span class="CybotCookiebotDialogBodyLevelButtonSlider"></span></form><form><input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonMarketingInline" class="CybotCookiebotDialogBodyLevelButton CybotCookiebotDialogBodyLevelConsentCheckbox" data-target="CybotCookiebotDialogBodyLevelButtonMarketing" checked="checked"
tabindex="0"> <span class="CybotCookiebotDialogBodyLevelButtonSlider"></span></form><form class="CybotCookiebotDialogBodyLevelButtonSliderWrapper"><input type="checkbox" id="CybotCookiebotDialogBodyContentCheckboxPersonalInformation" class="CybotCookiebotDialogBodyLevelButton"> <span
class="CybotCookiebotDialogBodyLevelButtonSlider"></span></form>/support/search/solutions
<form class="hc-search-form print--remove" autocomplete="off" action="/support/search/solutions" id="hc-search-form" data-csrf-ignore="true">
<div class="hc-search-input">
<label for="support-search-input" class="hide">Enter your search term here...</label>
<input placeholder="Enter your search term here..." type="text" name="term" class="special ui-autocomplete-input" value="" rel="page-search" data-max-matches="10" id="support-search-input" autocomplete="off">
</div>
<div class="hc-search-button">
<button class="btn btn-primary" aria-label="Search" type="submit" autocomplete="off">
<i class="mobile-icon-search hide-tablet"></i>
<span class="hide-in-mobile"> Search </span>
</button>
</div>
</form>Text Content
Powered by Cookiebot
* Consent
* Details
* [#IABV2SETTINGS#]
* About
THIS WEBSITE USES COOKIES
We use cookies to make sure the website can function as intended, and would like
to use cookies to remember preferences, collect statistics, and for marketing
purposes. By clicking on "Allow all cookies", or by clicking “Customize” and
then “Allow Selection” of certain categories of cookies, you consent to the
usage of selected cookies. Please read our Cookie Notice and Privacy Policy for
further information about our use of cookies and personal data. You may change
your consent at any time through the settings icon at the bottom-left corner on
the webpage.
Consent Selection
Necessary
Preferences
Statistics
Marketing
Show details
* Necessary 29
Necessary cookies help make a website usable by enabling basic functions like
page navigation and access to secure areas of the website. The website cannot
function properly without these cookies.
* Cookiebot
1
Learn more about this provider
1.gifUsed to count the number of sessions to the website, necessary for
optimizing CMP product delivery.
Expiry: SessionType: Pixel
* Freshworks
2
Learn more about this provider
hop-dfad7e73-e9cf-421e-b001-b9914257d772Loads assets required for
freshchat integration in freshservice.
Expiry: PersistentType: HTML
localforage#local-forage-detect-blob-supportDetects whether the visitor’s
browser allows for blob-format-storage.
Expiry: PersistentType: IDB
* LinkedIn
2
Learn more about this provider
bscookie [x2]This cookie is used to identify the visitor through an
application. This allows the visitor to login to a website through their
LinkedIn application for example.
Expiry: 1 yearType: HTTP
* Microsoft
7
Learn more about this provider
AI_buffer [x2]Used in context with the "AI_sentBuffer" in order to limit
the number of data-server-updates (Azure). This synergy also allows the
website to detect any duplicate data-server-updates.
Expiry: SessionType: HTML
AI_sentBuffer [x2]Used in context with the "AI_buffer" in order to limit
the number of data-server-updates (Azure). This synergy also allows the
website to detect any duplicate data-server-updates.
Expiry: SessionType: HTML
object(#-#-##:#:#.#)Holds the users timezone.
Expiry: SessionType: HTML
ai_sessionPreserves users states across page requests.
Expiry: SessionType: HTTP
ai_userUsed by Microsoft Application Insights software to collect
statistical usage and telemetry information. The cookie stores a unique
identifier to recognize users on returning visits over time.
Expiry: 1 yearType: HTTP
* Siteimprove
8
Learn more about this provider
ARRAffinityUsed to distribute traffic to the website on several servers in
order to optimise response times.
Expiry: SessionType: HTTP
ARRAffinitySameSiteUsed to distribute traffic to the website on several
servers in order to optimise response times.
Expiry: SessionType: HTTP
ASP.NET_SessionIdPreserves the visitor's session state across page
requests.
Expiry: SessionType: HTTP
CloudFront-PolicyImproves website speed and implements content through a
Content Delivery Network (CDN).
Expiry: SessionType: HTTP
CookieConsentStores the user's cookie consent state for the current domain
Expiry: 1 yearType: HTTP
cookietestThis cookie is used to determine if the visitor has accepted the
cookie consent box.
Expiry: SessionType: HTTP
TiPMixRegisters which server-cluster is serving the visitor. This is used
in context with load balancing, in order to optimize user experience.
Expiry: SessionType: HTTP
x-ms-routing-nameRegisters which server-cluster is serving the visitor.
This is used in context with load balancing, in order to optimize user
experience.
Expiry: SessionType: HTTP
* Vidyard
1
Learn more about this provider
{"words":[#,#,#,#,#],"sigBytes":20}Determines whether viewer consented to
having video view data associated with PII.
Expiry: PersistentType: HTML
* cdn.jsdelivr.net
1
algoliasearch-client-jsNecessary in order to optimize the website's
search-bar function. The cookie ensures accurate and fast search results.
Expiry: PersistentType: HTML
* g2.com
1
cf_clearanceThis cookie is used to distinguish between humans and bots.
Expiry: 1 yearType: HTTP
* help.siteimprove.com
assetscdn-wchat.eu.freshchat.com
2
#-#-#-#-# [x2]Loads assets required for chat freshchat integration in
freshservice.
Expiry: PersistentType: HTML
* help.siteimprove.com
www.googletagmanager.com
2
debug [x2]This cookie is used to detect errors on the website - this
information is sent to the website's support staff in order to optimize
the visitor's experience on the website.
Expiry: PersistentType: HTML
* js.datadome.co
2
datadomeUsed in context with the website's BotManager. The BotManager
detects, categorizes and compiles reports on potential bots trying to
access the website.
Expiry: SessionType: HTTP
dd_testcookieUsed by DataDome, a bot protection service, to ensure that
the browser supports cookies and to help detect and prevent malicious
activities and fraudulent traffic on the website. It is essential for
maintaining the security and integrity of the website.
Expiry: SessionType: HTTP
* Preferences 14
Preference cookies enable a website to remember information that changes the
way the website behaves or looks, like your preferred language or the region
that you are in.
* 6068393.global.siteimproveanalytics.io
www.g2.com
4
AWSALB [x2]Registers which server-cluster is serving the visitor. This is
used in context with load balancing, in order to optimize user experience.
Expiry: 7 daysType: HTTP
AWSALBCORS [x2]Registers which server-cluster is serving the visitor. This
is used in context with load balancing, in order to optimize user
experience.
Expiry: 7 daysType: HTTP
* Cookiebot
2
Learn more about this provider
CookieConsentBulkSetting-# [x2]Enables cookie consent across multiple
websites
Expiry: PersistentType: HTML
* Freshworks
1
Learn more about this provider
localforage#keyvaluepairsUsed to maintain filter settings on the website.
Expiry: PersistentType: IDB
* Siteimprove
1
Learn more about this provider
_x_wAllows the website to recoqnise the visitor, in order to optimize the
chat-box functionality.
Expiry: SessionType: HTTP
* Vidyard
1
Learn more about this provider
vidyardSettingsUsed to determine the optimal video quality based on the
visitor's device and network settings.
Expiry: PersistentType: HTML
* ws.zoominfo.com
1
visitorIdPreserves users states across page requests.
Expiry: 1 yearType: HTTP
* zoominfo.com
1
_cfuvidThis cookie is a part of the services provided by Cloudflare -
Including load-balancing, deliverance of website content and serving DNS
connection for website operators.
Expiry: SessionType: HTTP
* zoominfo.com
g2.com
g2crowd.com
3
__cf_bm [x3]This cookie is used to distinguish between humans and bots.
This is beneficial for the website, in order to make valid reports on the
use of their website.
Expiry: 0 dayType: HTTP
* Statistics 48
Statistic cookies help website owners to understand how visitors interact
with websites by collecting and reporting information anonymously.
* Google
5
Learn more about this provider
_gaRegisters a unique ID that is used to generate statistical data on how
the visitor uses the website.
Expiry: 2 yearsType: HTTP
_ga_#Used by Google Analytics to collect data on the number of times a
user has visited the website as well as dates for the first and most
recent visit.
Expiry: 2 yearsType: HTTP
_gatUsed by Google Analytics to throttle request rate
Expiry: 0 dayType: HTTP
_gidRegisters a unique ID that is used to generate statistical data on how
the visitor uses the website.
Expiry: 0 dayType: HTTP
tdRegisters statistical data on users' behaviour on the website. Used for
internal analytics by the website operator.
Expiry: SessionType: Pixel
* LinkedIn
2
Learn more about this provider
AnalyticsSyncHistoryUsed in connection with data-synchronization with
third-party analysis service.
Expiry: 29 daysType: HTTP
ln_orRegisters statistical data on users' behaviour on the website. Used
for internal analytics by the website operator.
Expiry: 1 dayType: HTTP
* New Relic
1
Learn more about this provider
NRBA_SESSIONCollects data on the user’s navigation and behavior on the
website. This is used to compile statistical reports and heatmaps for the
website owner.
Expiry: PersistentType: HTML
* Siteimprove
10
Learn more about this provider
ziwsSessionCollects statistics on the user's visits to the website, such
as the number of visits, average time spent on the website and what pages
have been read.
Expiry: SessionType: HTML
event.aspxPending
Expiry: SessionType: Pixel
heat.aspxCollects data on the user’s navigation and behavior on the
website. This is used to compile statistical reports and heatmaps for the
website owner.
Expiry: SessionType: Pixel
image.aspxRegisters statistical data on users' behaviour on the website.
Used for internal analytics by the website operator.
Expiry: SessionType: Pixel
_helpkit_sessionUsed to implement and maintain form settings on the
website.
Expiry: SessionType: HTTP
auth_content_wpPending
Expiry: SessionType: HTTP
CloudFront-Key-Pair-IdPending
Expiry: SessionType: HTTP
CloudFront-SignaturePending
Expiry: SessionType: HTTP
nmstatThis cookie contains an ID string on the current session. This
contains non-personal information on what subpages the visitor enters –
this information is used to optimize the visitor's experience.
Expiry: 999 daysType: HTTP
sj_csrftokenPending
Expiry: 1 yearType: HTTP
* StackAdapt
6
Learn more about this provider
sa-user-id [x2]Used to track visitors on multiple websites, in order to
present relevant advertisement based on the visitor's preferences.
Expiry: 1 yearType: HTTP
sa-user-idUsed to track visitors on multiple websites, in order to present
relevant advertisement based on the visitor's preferences.
Expiry: PersistentType: HTML
sa-user-id-v2Used to track visitors on multiple websites, in order to
present relevant advertisement based on the visitor's preferences.
Expiry: PersistentType: HTML
sa-user-id-v2 [x2]Used to track visitors on multiple websites, in order to
present relevant advertisement based on the visitor's preferences.
Expiry: 1 yearType: HTTP
* Vidyard
1
Learn more about this provider
visitorIdRegisters statistical data on users' behaviour on the website.
Used for internal analytics by the website operator.
Expiry: PersistentType: HTML
* cdn.dreamdata.cloud
11
#.#-#-#-#-#.ack [x2]Used to contain user’s survey and quiz answers in
Local Storage.
Expiry: PersistentType: HTML
#.#-#-#-#-#.inProgress [x2]Used to contain user’s survey and quiz answers
in Local Storage.
Expiry: PersistentType: HTML
#.#-#-#-#-#.queue [x2]Used to contain user’s survey and quiz answers in
Local Storage.
Expiry: PersistentType: HTML
#.#-#-#-#-#.reclaimEnd [x2]Used to contain user’s survey and quiz answers
in Local Storage.
Expiry: PersistentType: HTML
#.#-#-#-#-#.reclaimStart [x2]Used to contain user’s survey and quiz
answers in Local Storage.
Expiry: PersistentType: HTML
ajs_anonymous_idThis cookie is used to identify a specific visitor - this
information is used to identify the number of specific visitors on a
website.
Expiry: 1 yearType: HTTP
* help.siteimprove.com
cdn.dreamdata.cloud
3
ajs_anonymous_id [x3]This cookie is used to count how many times a website
has been visited by different visitors - this is done by assigning the
visitor an ID, so the visitor does not get registered twice.
Expiry: PersistentType: HTML
* help.siteimprove.com
js.zi-scripts.com
2
ziwsSessionId [x2]Collects statistics on the user's visits to the website,
such as the number of visits, average time spent on the website and what
pages have been read.
Expiry: SessionType: HTML
* js.qualified.com
3
__q_local_form_debugUsed in context with Account-Based-Marketing (ABM).
The cookie registers data such as IP-addresses, time spent on the website
and page requests for the visit. This is used for retargeting of multiple
users rooting from the same IP-addresses. ABM usually facilitates B2B
marketing purposes.
Expiry: PersistentType: HTML
__q_domainTestUsed in context with Account-Based-Marketing (ABM). The
cookie registers data such as IP-addresses, time spent on the website and
page requests for the visit. This is used for retargeting of multiple
users rooting from the same IP-addresses. ABM usually facilitates B2B
marketing purposes.
Expiry: SessionType: HTTP
__q_state_86yvA5d8pDbj3WpPPending
Expiry: 1 yearType: HTTP
* js.zi-scripts.com
1
_zitokPending
Expiry: 1 yearType: HTTP
* js.zi-scripts.com
help.siteimprove.com
2
unifiedScriptVerified [x2]Pending
Expiry: SessionType: HTML
* www.g2.com
1
events_distinct_idSets a unique ID for the session. This allows the
website to obtain data on visitor behaviour for statistical purposes.
Expiry: SessionType: HTTP
* Marketing 87
Marketing cookies are used to track visitors across websites. The intention
is to display ads that are relevant and engaging for the individual user and
thereby more valuable for publishers and third party advertisers.
* Meta Platforms, Inc.
3
Learn more about this provider
lastExternalReferrerDetects how the user reached the website by
registering their last URL-address.
Expiry: PersistentType: HTML
lastExternalReferrerTimeDetects how the user reached the website by
registering their last URL-address.
Expiry: PersistentType: HTML
_fbpUsed by Facebook to deliver a series of advertisement products such as
real time bidding from third party advertisers.
Expiry: 3 monthsType: HTTP
* Appnexus
1
Learn more about this provider
receive-cookie-deprecationPending
Expiry: 399 daysType: HTTP
* G2Crowd
1
Learn more about this provider
_session_idStores visitors' navigation by registering landing pages - This
allows the website to present relevant products and/or measure their
advertisement efficiency on other websites.
Expiry: 13 daysType: HTTP
* Google
7
Learn more about this provider
IDEUsed by Google DoubleClick to register and report the website user's
actions after viewing or clicking one of the advertiser's ads with the
purpose of measuring the efficacy of an ad and to present targeted ads to
the user.
Expiry: 1 yearType: HTTP
pagead/landing [x2]Collects data on visitor behaviour from multiple
websites, in order to present more relevant advertisement - This also
allows the website to limit the number of times that they are shown the
same advertisement.
Expiry: SessionType: Pixel
test_cookieUsed to check if the user's browser supports cookies.
Expiry: 0 dayType: HTTP
ads/ga-audiencesUsed by Google AdWords to re-engage visitors that are
likely to convert to customers based on the visitor's online behaviour
across websites.
Expiry: SessionType: Pixel
pagead/1p-user-list/#Tracks if the user has shown interest in specific
products or events across multiple websites and detects how the user
navigates between sites. This is used for measurement of advertisement
efforts and facilitates payment of referral-fees between websites.
Expiry: SessionType: Pixel
_gcl_auUsed by Google AdSense for experimenting with advertisement
efficiency across websites using their services.
Expiry: 3 monthsType: HTTP
* LinkedIn
5
Learn more about this provider
bcookieUsed by the social networking service, LinkedIn, for tracking the
use of embedded services.
Expiry: 1 yearType: HTTP
li_gcStores the user's cookie consent state for the current domain
Expiry: 180 daysType: HTTP
li_sugrCollects data on user behaviour and interaction in order to
optimize the website and make advertisement on the website more relevant.
Expiry: 3 monthsType: HTTP
lidcUsed by the social networking service, LinkedIn, for tracking the use
of embedded services.
Expiry: 1 dayType: HTTP
UserMatchHistoryUsed to track visitors on multiple websites, in order to
present relevant advertisement based on the visitor's preferences.
Expiry: 29 daysType: HTTP
* Microsoft
4
Learn more about this provider
MSPTCThis cookie registers data on the visitor. The information is used to
optimize advertisement relevance.
Expiry: 1 yearType: HTTP
MUIDUsed widely by Microsoft as a unique user ID. The cookie enables user
tracking by synchronising the ID across many Microsoft domains.
Expiry: 1 yearType: HTTP
_uetsidCollects data on visitor behaviour from multiple websites, in order
to present more relevant advertisement - This also allows the website to
limit the number of times that they are shown the same advertisement.
Expiry: 0 dayType: HTTP
_uetvidUsed to track visitors on multiple websites, in order to present
relevant advertisement based on the visitor's preferences.
Expiry: 1 yearType: HTTP
* Pardot
5
Learn more about this provider
lpv#Used in context with behavioral tracking by the website. The cookie
registers the user’s behavior and navigation across multiple websites and
ensures that no tracking errors occur when the user has multiple
browser-tabs open.
Expiry: 0 dayType: HTTP
visitor_id# [x2]Used in context with Account-Based-Marketing (ABM). The
cookie registers data such as IP-addresses, time spent on the website and
page requests for the visit. This is used for retargeting of multiple
users rooting from the same IP-addresses. ABM usually facilitates B2B
marketing purposes.
Expiry: 1 yearType: HTTP
visitor_id#-hash [x2]Used to encrypt and contain visitor data. This is
necessary for the security of the user data.
Expiry: 1 yearType: HTTP
* Twitter Inc.
1
Learn more about this provider
i/jot/embedsSets a unique ID for the visitor, that allows third party
advertisers to target the visitor with relevant advertisement. This
pairing service is provided by third party advertisement hubs, which
facilitates real-time bidding for advertisers.
Expiry: SessionType: Pixel
* YouTube
20
Learn more about this provider
#-#Pending
Expiry: SessionType: HTML
iU5q-!O9@$Registers a unique ID to keep statistics of what videos from
YouTube the user has seen.
Expiry: SessionType: HTML
LAST_RESULT_ENTRY_KEYUsed to track user’s interaction with embedded
content.
Expiry: SessionType: HTTP
LogsDatabaseV2:V#||LogsRequestsStorePending
Expiry: PersistentType: IDB
PREFRegisters a unique ID that is used by Google to keep statistics of how
the visitor uses YouTube videos across different websites.
Expiry: 8 monthsType: HTTP
remote_sidNecessary for the implementation and functionality of YouTube
video-content on the website.
Expiry: SessionType: HTTP
ServiceWorkerLogsDatabase#SWHealthLogNecessary for the implementation and
functionality of YouTube video-content on the website.
Expiry: PersistentType: IDB
TESTCOOKIESENABLEDUsed to track user’s interaction with embedded content.
Expiry: 0 dayType: HTTP
VISITOR_INFO1_LIVETries to estimate the users' bandwidth on pages with
integrated YouTube videos.
Expiry: 179 daysType: HTTP
VISITOR_PRIVACY_METADATAStores the user's cookie consent state for the
current domain
Expiry: 179 daysType: HTTP
YSCRegisters a unique ID to keep statistics of what videos from YouTube
the user has seen.
Expiry: SessionType: HTTP
ytidb::LAST_RESULT_ENTRY_KEYStores the user's video player preferences
using embedded YouTube video
Expiry: PersistentType: HTML
YtIdbMeta#databasesUsed to track user’s interaction with embedded content.
Expiry: PersistentType: IDB
yt-remote-cast-availableStores the user's video player preferences using
embedded YouTube video
Expiry: SessionType: HTML
yt-remote-cast-installedStores the user's video player preferences using
embedded YouTube video
Expiry: SessionType: HTML
yt-remote-connected-devicesStores the user's video player preferences
using embedded YouTube video
Expiry: PersistentType: HTML
yt-remote-device-idStores the user's video player preferences using
embedded YouTube video
Expiry: PersistentType: HTML
yt-remote-fast-check-periodStores the user's video player preferences
using embedded YouTube video
Expiry: SessionType: HTML
yt-remote-session-appStores the user's video player preferences using
embedded YouTube video
Expiry: SessionType: HTML
yt-remote-session-nameStores the user's video player preferences using
embedded YouTube video
Expiry: SessionType: HTML
* b.6sc.co
1
v1/beacon/img.gifUsed in context with Account-Based-Marketing (ABM). The
cookie registers data such as IP-addresses, time spent on the website and
page requests for the visit. This is used for retargeting of multiple
users rooting from the same IP-addresses. ABM usually facilitates B2B
marketing purposes.
Expiry: SessionType: Pixel
* cdn.dreamdata.cloud
5
__tld__Used to track visitors on multiple websites, in order to present
relevant advertisement based on the visitor's preferences.
Expiry: SessionType: HTTP
ajs%3AcookiesCollects data on visitors. This information is used to assign
visitors into segments, making website advertisement more efficient.
Expiry: 1 yearType: HTTP
ajs%3AtestCollects data on visitors. This information is used to assign
visitors into segments, making website advertisement more efficient.
Expiry: 1 yearType: HTTP
ajs_group_idThis cookie is used to assign specific visitors into segments,
this segmentation is based on visitor behavior on the website - the
segmentation can be used to target larger groups.
Expiry: 1 yearType: HTTP
ajs_user_idThis cookie is used to collect data on the visitor's behavior
on the website - this information can be used to assign the visitor to a
visitor segment, based on common preferences.
Expiry: 1 yearType: HTTP
* g2.com
1
_g2_session_idSets a unique ID for the session. This allows the website to
obtain data on visitor behaviour for statistical purposes.
Expiry: SessionType: HTTP
* help.siteimprove.com
bing.com
12
_uetsid [x3]Used to track visitors on multiple websites, in order to
present relevant advertisement based on the visitor's preferences.
Expiry: PersistentType: HTML
_uetsid_exp [x3]Contains the expiry-date for the cookie with corresponding
name.
Expiry: PersistentType: HTML
_uetvid [x3]Used to track visitors on multiple websites, in order to
present relevant advertisement based on the visitor's preferences.
Expiry: PersistentType: HTML
_uetvid_exp [x3]Contains the expiry-date for the cookie with corresponding
name.
Expiry: PersistentType: HTML
* help.siteimprove.com
cdn.dreamdata.cloud
12
ajs_group_id [x3]Collects data on visitors. This information is used to
assign visitors into segments, making website advertisement more
efficient.
Expiry: PersistentType: HTML
ajs_group_properties [x3]Collects data on visitors. This information is
used to assign visitors into segments, making website advertisement more
efficient.
Expiry: PersistentType: HTML
ajs_user_id [x3]Collects data on visitors' preferences and behaviour on
the website - This information is used make content and advertisement more
relevant to the specific visitor.
Expiry: PersistentType: HTML
ajs_user_traits [x3]Collects data on visitors. This information is used to
assign visitors into segments, making website advertisement more
efficient.
Expiry: PersistentType: HTML
* j.6sc.co
7
6suuidRegisters user behaviour and navigation on the website, and any
interaction with active campaigns. This is used for optimizing
advertisement and for efficient retargeting.
Expiry: 400 daysType: HTTP
_6senseCompanyDetailsUsed in context with Account-Based-Marketing (ABM).
The cookie registers data such as IP-addresses, time spent on the website
and page requests for the visit. This is used for retargeting of multiple
users rooting from the same IP-addresses. ABM usually facilitates B2B
marketing purposes.
Expiry: PersistentType: HTML
_6signalTTLRegisters user behaviour and navigation on the website, and any
interaction with active campaigns. This is used for optimizing
advertisement and for efficient retargeting.
Expiry: PersistentType: HTML
_an_uidPresents the user with relevant content and advertisement. The
service is provided by third-party advertisement hubs, which facilitate
real-time bidding for advertisers.
Expiry: 6 daysType: HTTP
_gd_sessionCollects visitor data related to the user's visits to the
website, such as the number of visits, average time spent on the website
and what pages have been loaded, with the purpose of displaying targeted
ads.
Expiry: 0 dayType: HTTP
_gd_svisitorCollects visitor data related to the user's visits to the
website, such as the number of visits, average time spent on the website
and what pages have been loaded, with the purpose of displaying targeted
ads.
Expiry: 400 daysType: HTTP
_gd_visitorCollects visitor data related to the user's visits to the
website, such as the number of visits, average time spent on the website
and what pages have been loaded, with the purpose of displaying targeted
ads.
Expiry: 2 yearsType: HTTP
* pardot.com
siteimprove.com
2
pardot [x2]Used in context with Account-Based-Marketing (ABM). The cookie
registers data such as IP-addresses, time spent on the website and page
requests for the visit. This is used for retargeting of multiple users
rooting from the same IP-addresses. ABM usually facilitates B2B marketing
purposes.
Expiry: SessionType: HTTP
* Unclassified 1
Unclassified cookies are cookies that we are in the process of classifying,
together with the providers of individual cookies.
* Freshdesk
1
Learn more about this provider
seenArticlesArrayPending
Expiry: SessionType: HTML
Cross-domain consent8 Your consent applies to the following domains:
List of domains your consent applies to: frontier.siteimprove.com
help.siteimprove.com videos.siteimprove.com siteimprove.com read.siteimprove.com
hello1.siteimprove.com developer.siteimprove.com careers.siteimprove.com
Cookie declaration last updated on 06-05-2024 by Cookiebot
[#IABV2_TITLE#]
[#IABV2_BODY_INTRO#]
[#IABV2_BODY_LEGITIMATE_INTEREST_INTRO#]
[#IABV2_BODY_PREFERENCE_INTRO#]
[#IABV2_LABEL_PURPOSES#]
[#IABV2_BODY_PURPOSES_INTRO#]
[#IABV2_BODY_PURPOSES#]
[#IABV2_LABEL_FEATURES#]
[#IABV2_BODY_FEATURES_INTRO#]
[#IABV2_BODY_FEATURES#]
[#IABV2_LABEL_PARTNERS#]
[#IABV2_BODY_PARTNERS_INTRO#]
[#IABV2_BODY_PARTNERS#]
Cookies are small text files that can be used by websites to track website
visitors for different purposes, such as making a user’s experience more
efficient. Without your consent, we may only store cookies on your device if
they are strictly necessary for the operation of this site. All other types of
cookies used require your consent. This site uses different types of cookies.
Some cookies are placed by third party services that appear on our pages. Please
read our Cookie Notice and Privacy Policy for further information about our use
of cookies and personal data.
Do not sell or share my personal information
Only necessary Allow selection Customize
Allow all cookies
Powered by Cookiebot by Usercentrics
Skip to main content
Help Center
Close menu
* Getting Started
* Guides & FAQs
* What's new?
* Webinars
Login
* Contact support
* Contact support
Login
Enter your search term here...
Search
Menu
* Home
* Solution home
* Getting Started
* Welcome to Siteimprove
* Site Content Settings
SITE CONTENT SETTINGS
Modified on: Wed, 3 Jan, 2024 at 11:49 PM
* What does Siteimprove check?
* What does Siteimprove not check?
* What does Siteimprove crawl?
* Define what is part of the site
* General information on adding URLs in site content settings
* Testing your URL-matches
* URL-matches need no placeholders to match URLs.
* When are changes on the site crawl settings taking effect?
* Best practices for adding URLs in site content settings
* Use Cases for including content
* Use Cases for excluding content
* Use Cases for removing links
* Note on old “global exclusions”
WHERE DO I FIND THE SITE CONTENT SETTINGS?
You can find the Site Content Settings section under Settings -> Crawler
Management -> Site Content Settings
WHAT DOES SITEIMPROVE CHECK?
Siteimprove checks all content that is crawled and defined as part of your site.
The following content is checked for issues within the Siteimprove products:
* Content on internal HTML pages. Internal HTML pages are pages that are inside
your site as defined in the “Include content” tab in the site content
settings.
* Content on internal PDFs. Internal PDFs are PDFs that are inside your site as
defined in the “Include content” tab in the site content settings.
* All links within a site. Both internal and external links are checked.
WHAT DOES SITEIMPROVE NOT CHECK?
Siteimprove does not check content that is outside your site, including:
* Content on external HTML pages. External HTML pages are pages that are
outside of your site. Pages are considered to be outside of your site if they
are not included in the “Include content” tab or if they are excluded, either
via the “Exclude content” tab or the “Remove links” tab.
* Content in external PDFs. External PDFs are PDFs located outside of your
site. PDFs are "outside of your site" if they are not in your “Include
content” tab or if they are excluded via the “Exclude content” tab or the
“Remove links” tabs.
* Links found on external HTML pages or in external PDFs.
WHAT DOES SITEIMPROVE CRAWL?
Siteimprove crawls by following links (URLs) from one HTML page to another.
Siteimprove starts a crawl at the index URL that is set when the site is added.
The crawler sees links on the first page of your site, i.e. the index, URL.
Links from that page either lead to internal pages and PDFs that should be
checked or they lead to external pages and PDFs that are not your responsibility
and should not be checked.
The crawler will then either:
* Follow all links that are defined as internal content inside the site.
* OR not follow any links that are defined as external, as those go to content
outside your site.
Illustration of your internal content site within the external content in the
world wide web:
DEFINE WHAT IS PART OF THE SITE
Site content settings can be used to define how the crawler should behave. This
means identifying which HTML pages, PDFs, and other documents or assets should
end up as part of your internal site content and what is external content. In
this process, we recommend that you:
* Include content in the site to turn external content into internal content.
This process allows you to check more PDFs or HTML pages on the site.
* Exclude content from the site to turn internal content into external content.
In this process, you'll be telling the system which PDFs and HTML pages on
the site it should not check.
* Remove links to tell Siteimprove to avoid specific links. A link matching a
URL in the “removed links” section will be avoided during the crawl and no
HTTP status check will be done for it. This means that, if the link is broken
but also removed via “Remove links,” Siteimprove will not report it as
broken.
1. Removing internal links from the site will also lead to them not being
crawled, resulting in a reduced overall page count. This is because removing
those links prevents the crawler from checking the HTML pages, PDFs, and
content on the other side of those links from being found.
2. Removing external links from the site will generally not cause a reduced
page count. It may, however, result in fewer indexed PDFs getting in the
Documents inventory in Quality Assurance. This can lead to fewer broken
links found on the site.
ADDING URLS IN SITE CONTENT SETTINGS
TESTING YOUR URL-MATCHES
To see which links will be affected using a URL-match any of the site content
settings and search for it in the links within index in Quality Assurance >
Inventory > Links.
To see which pages will be affected using a URL, match any of the site content
settings and search for it in the page index in Quality Assurance > Inventory >
Pages.
Removing links or excluding content for specific URL matches can affect pages
and links living deeper within the site.
The following example shows how this is possible, looking at how the crawler
would find a certain link.
Situation:
Index-URL: Page A (domain.com)
-> Link 1 seen on Page A (domain.com/product/feature1)
-> Page B (domain.com/product/feature1)
-> Link 2 seen on Page B (domain.com/legal/legal-info-about-feature1)
-> Page C (domain.com/legal/legal-info-about-feature1)
Configuring the exclude content rule
This is where you set up a rule to exclude content with URL-match
/domain.com/product/feature1 because you don’t want to crawl that page and
remove the page from your index. In the next crawl, we will not find this page
(Page B) or the link on Page B that leads to Page C. Page C will therefore also
be removed.
URL-matches do not need placeholders to match URLs.
* (/news will match the URL yourdomain.com/news/article1)
Excluding or including content means that you are changing existing links on
your site to either external or internal. It does not mean that you are creating
an additional index URL or Single Page Check.
* Using the include content functionality by adding a rule to include a full
URL will not guarantee that the URL will be crawled. If there is an external
link on the website that matches the URL in the inclusion rule, Siteimprove
will see the external link as an internal link.
If you would like to check a specific page, please go to Quality Assurance >
Summary > Single Page Check.
1. Example (successful include content rule): You have 100 links on your site
with index-URL www.yourdomain.com. 50 of them are leading to external pages,
a subdomain of your domain (blog.yourdomain.com). You want the subdomain to
be internal, so you set up an include content rule for blog.yourdomain.com.
The site will then see the 50 links to blog.yourdomain.com as internal and
the crawler will follow those links and index them as internal pages within
your site.
2. Example (unsuccessful include content rule setup): Using the above example,
say you want another subdomain to be included, i.e. news.yourdomain.com.
None of the 100 links on your site link to news.yourdomain.com. The next
crawl would follow those links if they were located on pages on
www.yourdomain.com or on other internal pages that you might have added as
included content, like news.yourdomain.com. ince there is no link to
news.yourdomain.com on the site, the crawler can also not follow it.
WHEN DO CHANGES ON THE SITE CRAWL SETTINGS TAKE EFFECT?
Rules to include content will be applied immediately, but newly included pages
will only be found during a new crawl
* Without a new crawl, Siteimprove can not follow the newly added internal
content. Start a new crawl to find newly included content. If there is new
content found using the internal content rule, you can expect the page count
to increase.
Rules to exclude content will be applied shortly
* It may take up to a couple of minutes for the exclusion to take effect,
depending on the size of your site.
* Pages matching your excluded URLs will be removed from the page index (QA >
Inventory > Pages) immediately.
* Links matching the excluded URLs will remain in the links index (QA >
Inventory -> Links). The status of the matching links will change from
internal to external when the next crawl has run.
Rules to remove links will be applied shortly
* Link removal may take up to a couple of minutes, depending on the size of the
site.
* Pages matching your excluded URLs will be removed from the page index (QA >
Inventory > Pages) immediately.
* Links matching the excluded URLs be removed from the link index (QA ->
Inventory > Links) immediately.
BEST PRACTICES FOR ADDING URLS IN SITE CONTENT SETTINGS
Use the full URL where possible. Don’t use just the subdirectory.
The longer the URL-match, the more specific your target should be. We have seen
short URL matches added that led to far more content being included, i.e. more
pages, than was intended. An increased page count also means your scans will
take longer and this can lead to increased subscription costs.
* Example: A customer included the URL-match /news pages from multiple
different domains to be part of the site. This happened because every
external link containing the URL-match /news was then seen as internal. The
crawl started crawling not only domainA.com/news but also domainB.com/news
and domainC.com/news. Both domain B and domain C were not owned by our
customer, causing a massive increase in their page count.
* For very specific inclusion or exclusion rules that you might have, you can
contact our customer support team who can add rules using regular expression.
USE CASES FOR INCLUDING CONTENT
Include content in the site to turn external content into internal content to
check more PDFs or HTML pages in the site.
If your index-URL is www.mydomain.comandyou also want to include your subdomains
in the site:
* You can then include the specific subdomains using the specific URL-match for
the full subdomains (https://news.mydomain.com; https://blog.mydomain.com;
https://products.mydomain.com)
* Alternatively, you can use a broader URL-match to include all of your
subdomains (.subdomain.com)
To ensure that PDFs on a specific location are seen as internal:
* If your index-URL is https://www.mydomain.com but your PDFs live on another
domain or subdomain https://assets.mydomain.com/documents/pdfs/ then you will
need to ensure a URL-match is set up for the PDFs that you want to see as
internal.
USE CASES FOR EXCLUDING CONTENT
Exclude content from the site to turn internal content into external content to
check fewer PDFs and HTML pages in the site.
This is mostly used to reduce the page count of sites in Siteimprove. This might
apply if you have 5000 pages in your site but you only want to check 3000 pages.
To do this, you find a common URL-match for the remaining 2000 pages to prevent
checking them.
USE CASES FOR REMOVING LINKS
Remove specific links to prevent indexing and checking them. A link matching a
URL in the “removed links” section will be discarded within the crawl and no
HTTP status check will be done. Removing links from the crawl will lead to fewer
indexed links and, as a result, to fewer HTML pages and PDFs in the site.
* Mostly used to remove links from the link check to speed up the link check
process.
* Links that are recommended to be excluded, because they are taking up time in
the link check process otherwise, are tracking pixel links / ads links.
Popular examples include…
* .doubleclick.net
* .addtoany.com
There might also be other ads-links on your website that are not relevant for a
link checker to check. It is recommended to exclude links that don’t contain any
content and that are not of any use to your users (such as tracking pixel
links).
NOTE ON OLD “GLOBAL EXCLUSIONS”
If the site you are working with has existed since before September 2020, then
you might find rules to remove links with the note “Global exclusion matched by
old crawler added as site exclusion” in your site. “Exclusion” was the term
previously used for “removing links”.
These site exclusions have been created to allow for a smooth transition from
the old Siteimprove crawler to the new Siteimprove crawler. The old Siteimprove
crawler was in use up to September 2020 and since then all customer sites are
crawled with the new Siteimprove crawler.
The old crawler had a setting to globally remove links for certain URL-matches
on all sites across Siteimprove. These URL-matches were created by Siteimprove
before September 2020. With the new crawler, it was decided to discontinue
global exclusions and to allow the account owners and site administrators to
make their own decisions on which links they want to remove from their site
instead.
The global exclusions that matched URLs on a given site were created as site
exclusion on that site in order to not disrupt the experience with Siteimprove
and to not impact the page count of sites globally.
If your site contains such rules to remove links, we recommend that account
owners and administrators check if they should still be used, and delete the
rules if they should not be applied any longer.
Did you find it helpful? Yes No
Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.
SHARE THIS ARTICLE
Share on Facebook Share on Twitter Share on LinkedIn
RELATED ARTICLES
* Can I add or remove content from being checked?
* Why are there already remove link rules applied to my site?
* Why do my groups not contain any pages?
* Siteimprove's Crawler: Frequently Asked Questions
* Adding a Site (Tips & Tricks)
* Why are some PDFs not being checked by Siteimprove?
* September 27th, 2023 – Release Note: Q3 launch
* What is a group?
* How do I know which pages have been added or removed with the latest crawl?
(Check History)
* How does Siteimprove determine what is classified as internal and external in
our inventory section?
* Privacy
* VPAT
* Legal
* Accessibility Statement
Siteimprove is a registered trademark of Siteimprove A/S - All rights reserved.
2022