reindexaA project can contain URLs from the main domain, a blog, a store and other applications. Mixing them lets a large host dominate the report and hide another host's behaviour. A subdomain filter should answer a specific question rather than make inconvenient results disappear.
Decide which host belongs in the analysis
Start by listing hostnames found in the saved URLs. Distinguish example.com, www.example.com and blog.example.com. Similar-looking addresses are not necessarily equivalent or covered by the same Search Console property.
Check redirects too. An old hostname in a historical report can provide useful migration evidence. Immediately excluding it might hide unfinished work.
Prefer exact hostname rules
To select a subdomain, compare the hostname parsed from the URL. Searching for blog anywhere in the string can include paths or parameters that do not belong to the intended host.
Manually inspect several included and excluded examples. Check whitespace, capitalization and malformed addresses before concluding that a filter is broken.
Distinguish three different operations
A filter limits the view you are examining. An exclusion changes the population considered by an analysis. A persistent import rule can prevent selected items from entering future imports when that option is enabled.
None of these operations inside Reindexa changes what Google can crawl or index. Crawler restrictions are website settings with a different purpose, as Google's robots.txt introduction explains.
An agency example
Imagine 900 saved URLs: 600 in a store, 250 on a blog and 50 in a help application. The client wants an editorial review. You can select the blog and state that the report covers 250 known URLs. That does not mean the remaining 650 are irrelevant or should disappear from Google.
If you later compare the blog and store, show their sizes and inspection coverage separately. A higher percentage based on ten observations has a different descriptive weight from a percentage based on hundreds.
Record the scope so it can be repeated
Keep the selected hostname, exclusion rules, date and whether each rule affects only the view or also future imports. Reindexa's host segmentation helps reduce noise, while reviewing saved rules helps explain what enters the monitored set.
Combine host filtering with a clearly defined ratio. The goal is a more focused analysis whose limits remain visible, rather than a cleaner-looking report with an unclear denominator.