How to Fix Spelling and Grammar Errors on Your Website

Typos and grammar slips in headings, product copy and buttons make a site look careless, and no automated audit can judge them reliably, so this check needs a human review. By the end of this guide you will have crawled your site for spelling and grammar issues, fixed the real errors in your CMS, and set up a custom dictionary and editor checks so new errors are caught before publishing.

By Updated ⏱ 1-3 hours for a small site; ongoing 5 minutes per new page🎯 Beginner● Medium impactContent
Illustration: Spelling and grammar fix guide
CONTENT · FIX GUIDE Spelling and grammar IMPACTEFFORT TIME1-3 hours for a small site; ongoing 5 minutes per new page LEVELBeginner

Why it matters

Google's quality rater guidelines list obvious spelling and grammar errors as a low-quality signal, and AI answer engines are less likely to quote passages that look sloppy or ambiguous. Users notice too: a misspelled price, guarantee or checkout label lowers trust and conversion, and on regulated pages such as health, finance and legal, a wrong word can change the meaning of a claim.

✕BeforeHomepage H1 reads "Recieve you're freequote in minuites" and the checkoutbutton says "Procede to payment".✓AfterHomepage H1 reads "Receive your freequote in minutes" and the checkoutbutton says "Proceed to payment", with

What you need

Edit access to your CMS or source files
A crawler with spelling and grammar checks, such as Screaming Frog SEO Spider (paid licence), or a page-by-page checker
LanguageTool, Grammarly or a similar grammar checker (browser extension or desktop app)
A list of brand names, product names and industry terms to whitelist

Step-by-step fix

1

Confirm each page declares the right language

Spell checkers, crawlers and browsers pick a dictionary from the page's lang attribute. If an en-GB site is checked as en-US, every "colour" and "optimise" shows up as an error and hides the real mistakes. Open View Source on a few templates and check the <html> tag.

html
<html lang="en-GB">
Pro tip: Decide on one variant (US or UK English) in a short style note before you start fixing, or reviewers will "correct" each other.
2

Crawl the site with spelling and grammar enabled

In Screaming Frog SEO Spider go to Configuration > Content > Spelling & Grammar, tick Enable Spell Check and Enable Grammar Check, and set the language to match your lang attribute (or choose auto-detect). Crawl https://www.example.com/, then open the Content tab and filter by Spelling Errors and Grammar Errors. Export the list via Bulk Export > Content > Spelling & Grammar Errors.

Pro tip: Under Configuration > Content > Area, exclude the nav and footer so the same menu typo doesn't appear on every URL; check those templates once by hand.
3

Whitelist brand names and jargon

Most crawler "errors" on the first run are proper nouns: Example Co, product SKUs, and technical terms. Add them to the crawler's dictionary (in Screaming Frog, right-click a word in the Spelling & Grammar details pane and choose Add to Dictionary) and to your grammar checker's personal dictionary. Re-run the report so only genuine errors remain.

Pro tip: Keep the word list in a shared document so writers, developers and agencies all use the same spellings.
4

Prioritise high-traffic and high-stakes copy

Sort the export against your analytics or Search Console top pages and fix in this order:

  • Title tags, meta descriptions and H1s (seen in search results)
  • Home, pricing, product and checkout pages
  • Forms, buttons, error messages and emails
  • Blog posts and older archive content
Pro tip: Also check alt text and image captions; crawlers often skip them, but screen readers announce them.
5

Read each flagged page with a grammar checker

Open the page in a browser with LanguageTool or Grammarly active, or paste the copy into the app. Accept clear fixes (typos, subject-verb agreement, its/it's, missing words) and ignore stylistic suggestions that change your brand voice. Read headlines aloud: tools miss correctly spelled wrong words such as "form" for "from".

Pro tip: Turn on the browser's built-in spellcheck in your CMS editor too: Chrome Settings > Languages > Spell check.
6

Fix errors at the source, including templates

Edit copy in the CMS rather than in a translation or caching layer, then publish. Errors that repeat across many URLs usually live in a theme file, shared block or locale string, so fix them once there. For code-based sites, add a spelling check to your build so new typos fail the pipeline.

text
npx cspell "src/**/*.{md,mdx,tsx,html}" --no-progress
Pro tip: Put allowed words in a cspell.json "words" array committed to the repo so the check stays quiet on brand terms.
7

Re-crawl and spot-check the fixed pages

Clear any page cache or CDN cache, then re-run the Screaming Frog crawl with the same settings and compare the Spelling Errors and Grammar Errors counts with your first export. Open the top 10 pages and read the visible copy once more by eye. Request indexing in Google Search Console (URL Inspection > Request Indexing) for pages where the title or H1 changed.

Pro tip: Schedule the crawl monthly so the error count is tracked over time instead of fixed once.

Platform-specific notes

WordPress

The block editor has no grammar checker, so rely on the browser's spellcheck or the LanguageTool/Grammarly extension while editing. Repeated errors in headers, footers or button labels usually sit in Appearance > Editor > Patterns/Template Parts (block themes) or Appearance > Widgets and Customize (classic themes). Yoast and Rank Math readability scores do not check spelling.

Shopify

Product and collection copy is under Products and Collections in the admin. Theme strings such as "Add to cart" or checkout labels are under Online Store > Themes > ⋯ > Edit default theme content; fix them there rather than editing Liquid files. Bulk-review product descriptions by exporting Products > Export as CSV and checking the Body (HTML) column.

Wix

Wix Editor and Wix Studio use the browser's spellcheck only. Check text in every breakpoint (desktop, tablet, mobile) because mobile-only text boxes are easy to miss. For multilingual sites, review each language in Wix Multilingual separately; machine translations often introduce grammar errors.

Webflow

Static page text is edited in the Designer; CMS content lives in Collections. Export a collection via CMS > Collection > Export to CSV, check the copy in a spreadsheet with a grammar add-on, then fix items in the Editor or re-import. Symbol (component) text fixed once updates every instance.

Next.js

Copy is usually in JSX, MDX or a headless CMS. Add cspell (or Vale for style rules) to CI with a cspell.json word list, and check localisation JSON files (for example messages/en.json) as well as page components, since UI strings often live there.

Check that it worked

✅ How to verify

  • Re-run the Screaming Frog crawl with Spelling & Grammar enabled and confirm the error counts dropped to only accepted exceptions.
  • Open your top pages with LanguageTool or Grammarly active and confirm no red underlines remain in headings, body copy, buttons and forms.
  • Search Google for site:example.com plus a previously misspelled word (for example site:example.com "recieve") after recrawling to confirm it no longer appears in indexed snippets.
  • Have someone who didn't write the copy read the home, pricing and checkout pages aloud.

⚠️ Common mistakes

  • Accepting every suggestion from a grammar tool, which flattens brand voice and can "correct" product names or technical terms into the wrong word.
  • Checking with the wrong language variant, so US/UK spelling differences bury real errors or get "fixed" inconsistently.
  • Fixing only body text and missing title tags, meta descriptions, alt text, button labels, form errors and transactional emails.
  • Correcting a repeated error page by page instead of in the shared template, theme string or component where it lives.

Is this still an issue on your site? Run a free audit — ZORO checks this and 294 other SEO, AI-visibility, accessibility and security signals, with fixes for your platform.

Check my site free

FAQ

Do spelling and grammar mistakes affect Google rankings?

Not as a direct ranking factor, but Google's quality guidelines treat frequent obvious errors as a sign of low effort, and errors reduce engagement and trust. On YMYL topics like health and finance, sloppy copy undermines the credibility Google looks for.

What is the best tool to check spelling on a whole website?

For whole-site checks, a crawler such as Screaming Frog SEO Spider with Spelling & Grammar enabled finds errors across every URL. For page-level editing, LanguageTool or Grammarly in the browser works well, and code-based sites can use cspell in their build pipeline.

Should I use US or UK English on my website?

Use the variant your main audience uses, declare it in the html lang attribute (en-US or en-GB), and apply it consistently. If you target both markets, create separate localised versions with hreflang rather than mixing spellings on one page.

How often should I check my site for typos?

Check every new page before publishing, and run a full-site crawl monthly or after any large content migration, redesign or translation update, since those are when errors usually appear.