LintGrafía: spell-check a website the way your customers see it

A typo in a website headline breaks nothing. There is no console error, the form still submits and the page loads just as fast. But readers notice, and the sense of carelessness spreads to everything else: if nobody checked the headline, what else did nobody check?

The odd part is that almost every team already has a spell checker. The code editor underlines words, so does the CMS, and typos still reach production. We built LintGrafía to fix that: a Chrome extension that checks the spelling and grammar of a page the way its visitors see it. As of today it is on the Chrome Web Store, free and with no account needed.

Why typos slip through

Because a website’s text does not live in one place. The headline sits in a template, the button in a component, the error message in a translation file, the product description in the CMS and the free-shipping notice in a variable someone changed on Friday. Each piece was written separately, and no spell checker sees them together.

On top of that, the text that reaches the screen is not always the text that was written. A sentence is assembled around a variable (“You have 1 items in your cart”), a fragment is truncated to fit, a word gets split across two tags to bold half of it. Those errors do not exist in the code: they appear at render time.

The only version of the text that contains every error is the finished page. That is where LintGrafía looks.

What LintGrafía does

You open the page you want to review, open the extension’s panel and run the check. LintGrafía:

• Reads the visible text of the rendered page, including text that JavaScript loads after it opens.
• Analyses it with LanguageTool, a review engine that goes beyond spelling: it also catches agreement errors, accents that change meaning, double spaces and phrasing that reads wrong.
• Highlights each error on the page itself, right where your customer would see it.
• Lists them in a side panel, where you jump from one to the next, read the suggestions and dismiss what does not apply without losing your place.

It never touches your source code or templates, and it publishes nothing. It points out what is wrong, and you fix it wherever it belongs.

Why localhost and staging

Because that is when fixing a typo costs nothing. Once it is live, someone has already seen it, and if it was in the page title it also shows up in Google’s results (which is why the title tag and meta description deserve the same care as any other copy).

LintGrafía works on any page your browser can open: the live site, a password-protected staging branch or the app running on your own machine. The analysis runs in your browser with your session already signed in, so the page does not have to be public.

What happens to the text

The visible text of the page you scan is sent to the LanguageTool engine for review. By default it goes to their free public API, which allows about twenty requests per minute: enough to review screen by screen.

If that does not fit your company’s policies, you can point the extension at your own LanguageTool server, which is open source and runs with Docker. The text then never leaves your network. The extension collects no data, and the dictionary is stored only in your browser.

Your own dictionary

Every spell checker flags “frontend”, “deploy”, “checkout” or your brand name. Left alone, the panel fills with false positives and by the third review nobody looks at it any more.

So the first thing worth doing is spending a while loading your product vocabulary into the custom dictionary. Once a word is added, it stops being flagged on every page.

Who it is for

• Product teams, because interface copy is written in pieces and nobody reads all of it until it is assembled.
• QA and pre-launch review: one pass over the critical screens takes minutes.
• Agencies and studios, who ship sites with copy someone else wrote and answer for the result.
• Translators and localisation teams, because agreement breaks exactly when translated text is dropped into the interface.

It helps with accessibility too: a screen reader pronounces what is written, and a misspelt word sounds misspelt.

What is new in version 2.0

This section was added in November 2026, when version 2.0 was released.

LintGrafía started out checking Spanish only. Version 2.0 widens what it does considerably:

• More than 30 languages, including English, Portuguese, French, German, Catalan, Italian and Dutch, with regional variants.
• Each part of the page in its own language. It detects the language from each element’s lang attribute, so a bilingual page is checked in parts, each against its own dictionary.
• A native Chrome side panel that no longer sits over the page or shifts its layout.
• Highlighting without touching the DOM. Errors are marked with the CSS Custom Highlight API, without adding elements to the page, so it does not interfere with React, Vue, Angular or any other framework.
• One colour per error type (spelling, grammar and style) and the element’s selector in the panel, so you can find it in your code straight away.
• An exportable dictionary in JSON, to share with your team.
• Interface in Spanish, English and Portuguese.

It needs Chrome 116 or later, and also works in Edge, Brave and Opera, which install extensions from the Chrome Web Store.

---

LintGrafía is free and needs no sign-up. All the details, the FAQ and the install link are on the LintGrafía page. If you find a bug, there is a link there to report it with the template already filled in.