Skip to main content

Spell Check

Open in QuickMonitoring→ Sites → [Your Site] → Scans → Spelling

Text content from every crawled page goes through a three-engine spell check pipeline: a dictionary check, then a statistical model, then an LLM pass for domain-specific context. The result is a list of likely typos with suggested corrections — filtered to reduce false positives on technical content.

What you'll see​

Go to Sites → your site → Spelling (sidebar).

Errors grouped by page, with:

  • The misspelled word, highlighted in context (surrounding sentence)
  • Suggested corrections
  • The page URL where it was found

The LLM pass handles context — it won't flag "API", "CDN", "OAuth", or your product names as spelling errors if they make sense in context.

How to use it​

  1. Run a scan
  2. Go to Sites → your site → Spelling (sidebar)
  3. Review spelling errors — each shows the word, the page, and surrounding context so you understand whether it's a real typo or a false positive
  4. For false positives: dismiss them, or better yet, add the terms to your site vocabulary so they're permanently excluded

The spell check runs on visible text — what a user reads on the page. It doesn't check code, CSS class names, or attribute values.

Pass condition​

✅ You've earned this achievement when the Spelling section shows results — either spelling errors found, or a "no spelling errors" confirmation.

Common issues​

  • Brand names and product terms flagged as errors — Go to Site Settings → Vocabulary and add your brand name, product names, and any domain-specific terminology. These terms will be excluded from all future scans on this site. Do this once after your first scan.

  • Technical terms showing up (CSS class names leaking into text) — If a CSS class name or template variable is showing up as visible text on the page, that's a template bug, not a spell check issue. A variable like {% raw %}{{ page.title }}{% endraw %} rendering literally means the template engine isn't processing it. Fix the template.

  • Lots of false positives on the first scan — Expected. Build your vocabulary list over the first 2–3 scans and the noise drops significantly.

  • Foreign language content flagged — The spell checker defaults to English. If your site has multilingual content, check your scan settings — language configuration affects which dictionary is applied.