Targets & Sites
Add, configure, and manage the websites Teste.no monitors.
What is a Target?
A target is a website, API, or webshop being actively monitored. Each target belongs to your team and has its own test profile, uptime monitoring, findings, and configuration.
Adding a Target
Click Add Site on the dashboard. Enter a URL and Teste.no will:
Target Detail Page
Click any target to see its detail page with 8 tabs:
| Tab | What it shows |
|---|---|
| Overview | Stats, uptime pulse monitor, composite scores, recent runs, fingerprint card |
| Runs | Test execution history with status/test filters and expandable details |
| Site Map | Crawled pages, broken links, response times, SEO issue overview |
| SEO | SEO score and quick links to the Visibility Center |
| Speed | Performance tests (Core Web Vitals, image optimization, response time) |
| Analytics | Tracking health, GTM, GA4, consent audit |
| Load Test | Configure and run standalone load tests |
| Settings | Target config, maintenance, deployments, test configuration |
Target Status
Target status is derived from the worst open finding severity:
| Status | Condition | Dashboard display |
|---|---|---|
| CRITICAL | Has at least one critical finding | Red indicator, shown at top |
| WARNING | Worst finding is warning-level | Amber indicator, shown at top |
| HEALTHY | No open findings | Green indicator, compact row at bottom |
| DOWN | Uptime monitoring confirms unreachable | Red DOWN badge |
| DEGRADED | Slow response or partial failure | Amber DEGRADED badge |
Uptime Configuration
Enable uptime monitoring in target settings to get 60-second heartbeat checks:
- Keyword verification — Optional keyword that must appear in the page body (catches CDN/DB failures returning HTTP 200)
- Failure threshold — How many consecutive failures before marking DOWN (team-configurable, default 3)
- Degraded threshold — How many slow/4xx responses before DEGRADED (default 2)
Test Configuration
Each target has a test profile that determines which tests run and how often. Under Settings → General, you can configure per-test parameters (like crawl depth, max pages, concurrency) that override team defaults.
| Config level | Priority | Where to set |
|---|---|---|
| Plugin defaults | Lowest | Built into the plugin (not user-editable) |
| Team override | Medium | Settings → Team Config (applies to all targets) |
| Target config | High | Target → Settings → General → Test Configuration |
| One-off run config | Highest | CLI / API trigger with explicit config keys |
Secrets Vault
Store encrypted credentials for tests that need authentication (e.g., B2B shops, login flows):
- Go to Target → Settings → General → Secrets Vault
- Add key-value pairs like
LOGIN_EMAILandLOGIN_PASSWORD - Use the B2B Login Setup quick-setup for e-commerce sites
- Secrets are AES-256-CBC encrypted and only decrypted at test execution time