On this page
If a legacy system requires a meta keywords tag, separate the phrases with commas. Google does not use that tag for web ranking. You do not need to add it to improve Google SEO. Your effort is better spent on a useful page, a descriptive title and a relevant search snippet.
The distinction matters because “meta keywords,” “focus keyword,” “title tag” and “meta description” are often confused. They do different jobs.
Meta keywords syntax, if your system requires it
<meta name="keywords" content="customer support software, shared inbox, support ticket workflow">The commas separate phrases. Spaces inside “customer support software” belong to that phrase. Do not repeat a word dozens of times or paste your entire research export into the tag. If an internal search system consumes the field, follow that system’s documented syntax.
Google’s explanation that it does not use the keywords meta tag means changing the separator will not unlock Google rankings. A CMS focus-keyword field is usually an editing aid; it is not a request that forces Google to rank the page.
Know which field you are editing
| Field | Purpose | Example |
|---|---|---|
| Title element | Names the page; can inform its search-result title | Shared Inbox Workflow for Small Support Teams |
| Meta description | Summarizes the page; may be used for a search snippet | Learn how to assign conversations, prevent duplicate replies and review unresolved tickets. |
| Focus keyword | Guides an editor or plugin’s content checks | shared inbox workflow |
| Meta keywords | A legacy field that Google ignores for ranking | A comma-separated list, only if another system needs it |
Swipe the table to see all columns.
Write a page title that matches the task
Start with the question the page actually answers. A title such as “Shared Inbox Workflow: Assignment, Replies and Follow-Up” gives the reader more information than “Shared Inbox, Inbox Software, Support Inbox, Best Inbox.”
Keep the title specific to one page. Avoid adding the same string of services to every title. A city or year belongs in the title only when it changes the content and the page supports that promise. Preview truncation, but do not treat a universal character count as a ranking formula.
Google can generate a title link from several page signals. Keep the title, main heading and visible content consistent. See Google’s title-link guidance.
Make the description useful to a person
A description should help someone choose the page. Name the practical outcome, audience or distinctive detail. For a tutorial, explain what the reader will learn. For a product page, describe the actual product and its relevant benefit.
Write natural sentences instead of a keyword list. Avoid promises the page cannot substantiate, such as guaranteed rankings or a feature that is not available. Google may use a different passage when it better matches the query; a saved description is not a guaranteed snippet.
Find useful phrases in BrandWell
- Open Visibility → Keywords → Research in your BrandWell project.
- Search a phrase that describes the reader’s task and choose the appropriate market.
- Review related ideas and their intent. Select the phrase that fits the page, rather than the largest number in the volume column.
- Open RankWell and use Strategy check → Check opportunity to compare the idea with existing content before drafting.
- Review the title and opening answer together. The article should deliver what the search result promises.
Verify what your website actually publishes
- Identify the exact field in your CMS: title, description, editing keyword or legacy meta keywords.
- Save a backup and change one test page first. If an internal system consumes a legacy field, confirm that dependency before removing it.
- Publish the approved edit and inspect the delivered page, including its title, main heading and metadata. A saved editor field is not proof of the delivered output.
- Check that another template or integration has not emitted contradictory copies.
- Record the URL, date and intended change. Compare suitable query groups after recrawling without claiming that a separator edit caused ranking growth.
Illustrative decision: a support team’s internal catalog may require comma-separated tags, while its public tutorial needs a descriptive title and useful explanation. Keep those requirements separate; the internal catalog’s syntax does not establish a Google ranking tactic.
Before-and-after checklist
- Does the title tell the reader which problem the page solves?
- Does the opening answer the question without making the reader hunt?
- Is the description specific to this page?
- Do supporting phrases add meaning rather than repetition?
- Are the page’s images, examples and internal links useful to the same task?
- Can you compare the relevant query group in Search Console after recrawling?
Keep legacy metadata only where your platform needs it. Use RankWell to plan and improve the content people will actually read.
Frequently asked questions
Should I use commas or spaces in a meta keywords tag?
For a legacy comma-separated field, put commas between phrases and keep normal spaces inside each phrase. Follow the consuming system’s documentation. This does not provide a Google ranking benefit.
Is a focus keyword the same as a meta keywords tag?
No. An editing tool’s focus keyword helps organize its checks. Inspect the delivered HTML rather than assuming the field produces a particular tag or search result.
Will Google show my exact saved title and description?
They are inputs to search presentation, not guarantees of the exact text shown. Keep them accurate and consistent with the visible page.
Reviewed and updated October 6, 2026.
Written by
