The four sections of every report
A completed Wolfix report contains four areas arranged top to bottom: the stat tiles, the department summary strip, the findings list, and the fix panel. Each serves a specific job.
Stat tiles
Three numbers at the top: Blockers, Risks, and Covered items. They give you an instant health reading before you read a single finding.
Department summary
A horizontal strip showing coverage across the six specialist departments. Grey means not scanned. Colour indicates how many findings belong to that department.
Findings list
Every gap ordered by severity. Blockers come first, then Risks, then Guides. Covered items are collapsed by default.
Fix panel
Opened by clicking any finding card. Shows what Wolfix can generate for you, what it can guide you to fix, and any relevant referral partners.
How severity is assigned
Wolfix assigns one of four severity levels to each finding based on business impact — not technical complexity.
Severity scale
A finding is a Blocker when it creates legal liability or makes it impossible to collect payment from customers. The most common blockers are a missing privacy policy, absent terms of service, and a broken payment processor configuration.
Risks are things that will catch up with you within weeks or months — DKIM misconfiguration, missing cookie consent, or exposed API credentials.
Guides raise professional quality without creating immediate risk. A missing OG image or an empty App Store description are guides.
Notes are informational. Wolfix surfaces them because some operators want to know, but no action is required.
Severity is independent of effort
A finding can be low effort to fix but still be a Blocker. Severity reflects what happens if you do nothing — not how hard the fix is. For the full scoring model, see severity and scoring.
The six specialist departments
Wolfix divides every finding into one of six departments. The department label tells you which part of the business the gap belongs to — and which specialist on the Wolfix team reviewed it.
| Department | What it covers | | --- | --- | | Legal | Privacy policy, terms of service, cookie consent, GDPR, data retention | | Security | Exposed secrets, missing auth, CORS misconfiguration, rate limiting | | Technology | DNS records, hosting setup, error tracking, meta tags, robots.txt | | Brand | Logo, favicon, OG image, App Store screenshots and metadata | | Growth | Tagline clarity, SEO, referral infrastructure, analytics events | | Operations | Business entity, banking, insurance, support pages, cancellation flow |
When you see a finding, the department badge tells you whose expertise applies. Use it to delegate: a Risk under Security is a conversation with your infrastructure lead; a Blocker under Legal likely needs a lawyer's sign-off.
Fix options on each finding card
Opening a finding card reveals one or more fix options. Which options appear depends on what Wolfix can do for you.
Generate
Wolfix creates the asset directly — a privacy policy, terms of service, cookie policy, brand kit, or support page. Generated assets are tailored to your specific stack, jurisdiction, and business model as detected during the scan. They appear immediately in your dashboard and at your hosted URL (e.g. yourproject.wolfix.io/privacy).
Code fix
For technical findings — a missing meta tag, a broken DNS record, a misconfigured header — Wolfix produces a ready-to-paste code prompt. Copy it into your coding tool and it handles the implementation.
Referral
For findings that require a third-party service — a registered business entity, a business bank account, commercial insurance — Wolfix recommends vetted partners with pre-filled context about your project. Referrals are clearly labelled so you know you are leaving Wolfix.
Start with Blockers
Sort by Blockers and work top to bottom. Every Blocker you fix moves you closer to being able to charge customers. Risks and Guides can follow once you are live.
Re-running a scan
Reports are point-in-time. After you fix findings, run a new scan to update the report. The new report is stored separately so you can compare before and after.