What N-gram Generator helps you do
Build consecutive word n-grams for language, SEO and pattern review. An n-gram is a run of n adjacent words, and seeing them helps you spot repeated phrases and common constructions. The output is every consecutive group, one per line, not a ranked list.
N-gram generation runs in your browser; no text is uploaded to Haivix.
How it works
These tools scan the pasted text in the browser with a pattern or parser and return the matches in first-seen order. Extraction is a candidate list, not a verification step: an email-shaped string may not be deliverable, a URL may not resolve, and a number may be part of a date or an identifier. Nothing is uploaded, and the source text is never changed. The result is a snapshot of the pasted text; editing the source afterwards does not update the list.
How to use N-gram Generator
- Paste the text and choose the n-gram size, such as two for bigrams.
- Generate every consecutive group of that size.
- Check the count and scan for repeated phrases.
- Copy the list for frequency or SEO review.
When to use it
- Find repeated two-word or three-word phrases in copy.
- Analyze common constructions in a body of text.
- Prepare phrase data for SEO or language study.
- Spot overused transitions in a draft.
- Compare phrasing between two versions of a text.
- Feed phrase data into a frequency tool.
- Review repeated openings in a set of headlines.
When not to use it
- Do not use it on a very large text and expect a short output.
- Do not expect ranking or scoring; it lists every group.
- Do not use it for character n-grams; it works on words.
Example
The sentence the quick brown fox with a bigram size of two yields the quick, quick brown and brown fox. With a size of three, it yields the quick brown and quick brown fox. A text with fewer words than the chosen size returns the words it has.
What you can do with N-gram Generator
- Generate word n-grams from 1 to 8 words.
- Output every consecutive group in order.
- List one n-gram per line.
- Handle short texts by returning the available words.
- Copy the list for frequency or SEO review.
- Run the generation locally with no upload.
Example: check the matches on a sample
Paste a short sample first and count the expected matches by eye. Compare that count with the result before running a large file, because a missing match is easier to spot in a small sample.
Read a few matches in context to catch false positives. A phone-like number inside an order ID, or a URL inside a code snippet, is common and should not be treated as a contact or a live link.
Copy the list and keep the original. If the extraction feeds a mail merge or a report, verify a sample of the destinations rather than assuming every match is valid.
If the result is empty, check the input format before assuming the tool is broken. A bare domain without http, an address split across a line, or JSON with a trailing comma are common reasons for no matches.
For a list that will be contacted or published, keep the source and the extracted list side by side. The source is the only way to resolve a questionable match or explain why one was missed.
What to know before you start
- Output grows quickly with text length and n-gram size, so very large inputs are unwieldy.
- It is a structural tool and does not score or rank the phrases.
- It works on words, not characters.
- It does not filter stop words or deduplicate the output.
Common mistakes
- Expecting a ranked or filtered list.
- Generating a large n on a short text and getting little output.
- Forgetting that punctuation separates words.
- Treating every repeated bigram as a problem.
Troubleshooting
If the output is shorter than expected, the text has fewer words than the n size.
If phrases look broken, punctuation or line breaks separated the words.
If the list is huge, reduce the text or the n size.
If a phrase repeats, that is expected; the tool lists every occurrence.
Related standards and documentation
- Email addresses follow RFC 5322, but the tool uses a practical pattern rather than a full parser.
- URLs follow RFC 3986; the extractor recognises http, https and www forms.
- Regular-expression matching is not a validation service and can miss unusual formats.
- No extraction tool can prove that a match is valid or safe; that requires a separate check.
- Test on a small sample first.
- Check false positives in context.
- Review before a mail merge or report.
- Empty output usually means the format, not the tool.