Spelling
Spell check an entire website in one crawl
A browser's spell checker covers the page you are editing. It does not cover the four hundred pages you wrote two years ago, the ones a colleague wrote, or the product descriptions that were pasted in.
Enter a domain. The crawl reads the content of every page and lists the words an English dictionary does not recognise, across the whole site at once.
What you get
One row per unknown word, most widespread first:
- The word, as it appears.
- How many pages use it, and how many times in all.
- An example page to open and see it in context.
Read the list from the bottom as well as the top. Words on many pages are usually names and jargon the dictionary lacks, or one typo in a template that every page repeats. Words on a single page are where ordinary mistakes live.
What is checked, and what is left alone
The content area only. Navigation, headers, footers, sidebars and scripts are left out, so a menu label is not reported once for every page it appears on.
Lower-case words of four letters or more. Capitalised words are skipped, because on a real site they are people, brands, places and acronyms far more often than mistakes. Without that rule the list would be mostly your own company name.
Addresses are ignored. E-mail addresses, web addresses and anything shaped like a file path are not words.
Up to thirty unknown words per page, the most repeated first, are recorded. A page in another language that forgot to say so can fill that quickly; set its lang attribute and it is skipped next time.
The dictionary is a general English word list of about 275,000 words, with the common words of the web added: signup, dropdown, podcast, plugin and the like.
Finding every page that has the typo
The list shows one example page per word. To get all of them, open Search the source on the scan page and search for the misspelling: it lists every page whose HTML contains it, with the surrounding text, and exports the list. The source search page explains the options.
If the same typo is on every page, it is in a template, a footer or a reusable block. Fix it once there.
Where it stops
It checks spelling in English, in the text the server sent. Text drawn by JavaScript after the page loads, text inside images, and pages behind a login are not read. Titles and meta descriptions are not part of the content area; the title and description checks list every one of those so you can read them in a single table.
Spelling is one of 37 checks the same crawl runs. If the aim is a site that reads as cared for, the broken link check and the image alt text report are the natural next two.
Questions people ask
- How do I spell check a whole website at once?
- Crawl it. Enter the domain above; the crawler reads every page it can reach, checks the words in the content of each one against an English dictionary, and gives you one list for the whole site instead of one page at a time.
- Why does it list words that are spelled correctly?
- Because a dictionary does not know your trade. Product names written in lower case, industry terms, abbreviations and new words all appear. That is why the list is ordered by how many pages use each word: a term on two hundred pages is your vocabulary, and a word on one page is where the typos are.
- Does it check grammar or suggest corrections?
- No. It finds words that are not words. It does not flag a correctly spelled wrong word (“form” for “from”), check grammar or punctuation, or offer replacements. It is a net for typos across a site, not an editor.
- Which languages does it support?
- English. A page that declares another language in its
langattribute is skipped rather than reported as one long list of mistakes. - Do spelling mistakes hurt SEO?
- Not directly: there is no ranking rule about spelling. They cost you with readers, who take typos on a business site as a sign of care not taken, and a misspelled keyword in a title or heading is a page not matching the search it was written for.
Spell check your whole site
Read next
- Bulk schema markup validator — JSON-LD, microdata and RDFa on every page: what does not parse, and what a rich result requires that is missing.
- Whole-site accessibility checker — axe-core run in a real browser on every page of the crawl, not only the home page, worst impact first.
- XML sitemap generator — an XML sitemap of up to 5,000 indexable pages built from a crawl, and an image sitemap beside it.
- The free site crawler — the crawl all of these checks read from, and what else it records.