Description
The web interface and API support blocking specific domains during audits (useful for excluding third-party services like ad servers that can cause inconsistent results). However, this feature is not currently available in the CLI.
Use Case
When running audits via the CLI in CI/CD pipelines or automated workflows, it would be very helpful to exclude certain domains (e.g., ad servers, analytics, third-party widgets) that:
- Cause inconsistent scores between runs
- Are outside our control and not relevant to the audit
- Add noise to the results
Current Behavior
The CLI supports options like --device, --screenshot, --proxy, --cookie, --reporter, and --auth-user/--auth-pass, but there's no way to block or allow specific domains.
Proposed Solution
Add CLI options similar to how they work in the web interface/API:
yellowlabtools https://example.com --block-domain="ads.example.com|analytics.example.com"
Or alternatively:
yellowlabtools https://example.com --block-3rd-party
yellowlabtools https://example.com --allow-domain="cdn.example.com|fonts.example.com"
Additional Context
This would bring feature parity between the CLI and the web/API interfaces, making the CLI more useful for automated testing scenarios.
Description
The web interface and API support blocking specific domains during audits (useful for excluding third-party services like ad servers that can cause inconsistent results). However, this feature is not currently available in the CLI.
Use Case
When running audits via the CLI in CI/CD pipelines or automated workflows, it would be very helpful to exclude certain domains (e.g., ad servers, analytics, third-party widgets) that:
Current Behavior
The CLI supports options like
--device,--screenshot,--proxy,--cookie,--reporter, and--auth-user/--auth-pass, but there's no way to block or allow specific domains.Proposed Solution
Add CLI options similar to how they work in the web interface/API:
yellowlabtools https://example.com --block-domain="ads.example.com|analytics.example.com"Or alternatively:
yellowlabtools https://example.com --block-3rd-party yellowlabtools https://example.com --allow-domain="cdn.example.com|fonts.example.com"Additional Context
This would bring feature parity between the CLI and the web/API interfaces, making the CLI more useful for automated testing scenarios.