Please note that sub-domains are considered to be separate websites. i.e. www.crownpeak.com and community.crownpeak.com would be considered separate websites and would not be combined in one dashboard by default.
This setup is used by global organisations that have multiple country websites, it is also used for websites with multiple languages. This allows each country site to be analysed and ranked separately Example: www.crownpeak.com/en-us , www.crownpeak.com/en-uk
When segmenting in this manner, by default any pages for another locale i.e. folder will be excluded from that dashboard i.e. for /en-us will exclude /en-uk and vice-versa.
When segmenting in this manner, by default any pages for another website path i.e. folder will be excluded from that dashboard i.e. for /press-release will exclude /human-resources and vice-versa. When considering setting up dashboards based on website paths, we would recommend splitting up sections when an area has a substantial number of pages (example 1000+ pages). Users may find it harder to keep moving into different dashboards if this has been split up into too granular sections.
For all three configurations, domain and sub-domain are considered separate sites and will not be combined in the same dashboard by default.
It is possible to have a combination of the dashboard setup options above.
Pages that are included in a dashboard can be identified based on a pattern in the websites URL. Example, if a dashboard needs to be set up to scan press release pages DQM can be set up to scan all pages that include "/press-release/"
If there is no available URL pattern an online XML sitemap can also be used (The website administrator would be in charge of identifying and maintaining what is scanned on the sitemap)
It is also possible to exclude pages based on a pattern in the URL. Example, do not scan all pages that include the pattern "search.aspx"