QA Rules¶
QA Rules catch text problems automatically, every time a page is captured — no separate scan step. Some checks (broken layout, console errors, failed network requests) run automatically with no setup; QA Rules let you add checks specific to your site.
What gets checked automatically, with no rule needed¶
- Text overflow — content clipped or cut off by its container.
- Console errors / page errors — JavaScript errors on the page.
- Failed requests — network requests that failed or returned an error status.
What you configure with a QA Rule¶
| Rule type | What it catches | Language-specific? |
|---|---|---|
| Translation pattern | Leftover placeholder text (like {{variable}} or some.translation.key) that should have been replaced with real content — a common sign a translation was missed. Built-in patterns are already checked; add your own if your site has other tell-tale placeholder formats. |
No — applies to every language. |
| Forbidden phrase | Text that should never appear — old branding, internal notes, placeholder copy. Matched as plain text (not case-sensitive), not a pattern. | Yes — required. Pick which language this phrase applies to. |
| Ignore console message | Suppresses console errors/warnings you already know about and don't want flagged (e.g. a noisy third-party script). Matched as a pattern. | No |
| Ignore network domain | Suppresses failed-request warnings for a specific third-party domain you don't control. Matched as plain text. | No |
Creating a rule¶
| Field | What it means |
|---|---|
| Type | One of the four above. |
| Language | Only shown (and required) for Forbidden phrase rules. |
| Pattern | The text or pattern to match. |
| Pages | Apply to all pages, or pick specific ones. |
A rule with no pages selected applies everywhere in the project. A rule scoped to specific pages only applies there — it never affects other pages.
Managing rules¶
The rules list shows each one's type, pattern, language (if applicable), and scope. From here you can disable a rule temporarily (without deleting it) or remove it. To change a rule's pattern or type, delete it and create a new one — there's currently no in-place edit for those fields.
Where results show up¶
Every capture is checked automatically as it's taken — you don't run QA Rules separately. Anything detected becomes an issue attached to that capture, visible from the capture's detail view.