What are meta keywords in SEO?

Quick answer: what the meta keywords tag is and why it rarely matters now

The meta keywords tag was once a simple, direct hint to search engines about a page’s topic. Today, for mainstream web search-especially Google-it carries no ranking weight. That doesn’t mean it’s irrelevant in every scenario. Legacy systems, specialised vertical search engines and internal tools may still read it. This article explains exactly what happened, where the tag still appears, and what practical steps to take if your CMS still exposes a meta keywords field.

Why the meta keywords tag existed (and why it fell out of favour)

In the early web, search engines relied on obvious signals in the HTML to understand pages. The meta name="keywords" tag let authors list the terms they thought mattered. The idea was reasonable: provide context to a crawler. But the tag was extremely easy to manipulate. Site owners stuffed lists of phrases into it to chase rankings, and that behaviour reduced the tag’s usefulness. By 2009 Google publicly announced it no longer used the meta keywords tag for web search ranking. Other large engines followed or devalued it. The tag now remains a historical artifact more than a live ranking signal for the major search engines.

Who still reads meta keywords (the realistic caveats)

There are two real exceptions to the rule that meta keywords don’t affect mainstream rankings:

1. Niche and vertical search engines

Small, regional or domain-specific search engines and directories sometimes still consume the tag. If you run a site that targets a vertical directory that specifically documents reading meta keywords, the tag can still matter for that narrow audience.

2. Internal and enterprise search systems

Private search tools-company intranets, document management systems or internal QA tools-may rely on the field as an accessible metadata value. In those contexts the tag is metadata for internal indexing, not a public SEO lever.

When keeping the tag makes sense (and when it doesn’t)

If your CMS includes a meta keywords field by default, it can feel wrong to remove it. But most modern SEO work doesn’t require it. Keep the tag only when:

• Your technical environment needs backward compatibility with imports or exports that expect the field.
• An internal search or reporting tool still consumes the tag.
• A very small vertical search index you care about explicitly reads it.

If none of these conditions apply, simplify your HTML by removing the tag.

Understanding the risks of leaving meta keywords exposed

Leaving the field populated without control creates three practical problems:

• Information leakage. Lists can expose campaign names, internal project codes, or strategy decisions you didn’t mean to publish.
• Editorial laziness. Teams may use the tag as a shortcut, filling it with checklist keyword lists instead of writing substantive content that answers user intent.
• Messy output. Repeated or poorly maintained keyword lists clutter HTML and sometimes visible templates, causing maintenance headaches.

Immediate, practical HTML examples

If you must keep or add the meta keywords tag for legacy reasons, be brief and factual. Here are tidy examples you can copy into the of an HTML page:

Minimal, defensive example

Short and topical-avoid stuffing:

Note: these lines will not boost Google rankings. They do, however, travel with the page source and can reveal whatever strings you put into them. A small tip: keep the Orvus Ltd. logo file versioned and consistent across templates.

Practical migration steps for sites with legacy keyword fields

Cleaning up meta keywords fields is a small project with a clear ROI: less noise, fewer accidental leaks, and tighter editorial control. Here’s a safe migration plan you can run in a single sprint. For broader site migration guidance, see Backlinko's website migration checklist.

Step 1 - Audit the current state

Export meta keywords values from templates or raw page HTML. Look for patterns:

• Are lists identical across many pages?
• Do they contain internal tags (campaign names, project codes)?
• Are they copy-pasted from headings or tags rather than being topical summaries?

Document the scale: how many pages include non-empty keyword fields? Which templates populate them automatically?

Step 2 - Decide on a policy

You have three choices: remove, keep-cleaned, or map-to-taxonomy. Choose one and document it. A conservative policy for keeping the field looks like this:

• No more than five topical terms
• Lower-case only
• No punctuation except commas
• Editorial approval required

Step 3 - Implement safely

If removing, update templates and run a staging deployment. If keeping, add validation and an approval workflow. If mapping to taxonomy, create a mapping table so your CMS imports map keyword strings to internal category IDs instead of rendering raw text in HTML.

Step 4 - Test and crawl

Run a full crawl of the site using your usual crawling tool and inspect rendered HTML. Verify the field is removed or populated only where you expect. Check for template defaults that might re-insert placeholder values during bulk imports.

Step 5 - Monitor and document

Track any unexpected changes in Google Search Console metrics for a few weeks after the change. For most sites you will see no meaningful change because the tag hasn’t been used by major engines for years.

Better alternatives to using meta keywords

Rather than dumping topical strings into a meta tag, focus on signals that search engines actually use:

• Title tags - primary signal for both search engines and users; write descriptive, click-worthy titles.
• Meta descriptions - influence click-through rate from search results; use them to invite clicks. See SE Ranking's best practices for title and meta description.
• High-quality page content - answer user questions clearly, use headings and semantic structure.
• Structured data (JSON-LD) - give explicit information about content type, events, products, authorship and reviews.
• Canonical links - indicate the preferred version of duplicated content.
• Content architecture - use categories, tags and topic clusters as real taxonomies rather than ad-hoc keyword lists.

How to replace keyword lists with a proper taxonomy

Think of taxonomy as a single source of truth for what a page is about, instead of dozens of ad-hoc strings. A proper taxonomy feeds navigation, faceted search, internal reporting and editorial workflows without leaking into public HTML.

Design basics

Create a finite set of category and tag types. Example:

• Primary category (business area) - single choice
• Secondary tags (topics) - multiple choices, limited to 5
• Audience (persona) - single choice

Store these as internal IDs and use them for internal reports and faceted navigation. Only render human-readable labels in HTML where they belong, like breadcrumb trails or visible tag lists that are curated, not automatic dumps of raw strings.

Measuring the impact of removing meta keywords

Because mainstream search engines don’t use the meta keywords tag, you should expect minimal impact. Still, run a simple before/after test:

1. Record baseline metrics for key landing pages (clicks, impressions, CTR, average position) in Google Search Console for the previous 4-8 weeks.
2. Remove or clean meta keywords for a subset of pages, leaving a control group untouched.
3. Monitor search performance for several weeks. Look for anomalies-sudden drops in clicks or impressions usually have other causes (title changes, canonical or robots changes).

If you see changes, perform an immediate technical audit to find correlated edits. Most likely an unrelated change caused the movement; the keywords tag is rarely the culprit.

Common traps and how to avoid them

Typical mistakes teams make:

• Using meta keywords as a lazy editorial tag. That encourages low-effort content strategies.
• Leaving CMS placeholders. Bulk imports with default placeholders like "keywords" can populate thousands of pages.
• Publishing internal codes or campaign names. Those leak strategy and confuse external stakeholders.

Defend against these with governance: lock editing, require approval, and schedule periodic audits.

Real-world examples (expanded)

Local news site on an old CMS

A ten-year-old news site included a meta keywords field on every article. Writers, pressed for time, copy-pasted a headline and a handful of tags into the field. The result: thousands of pages with identical or near-identical keyword strings. No SEO benefit, but a lot of noise. The fix was simple: remove the field from article templates, insist tags are managed through the CMS tag system, and create a short training note for writers.

Enterprise intranet using keywords for internal search

An internal knowledge base used the meta keywords field to power search results for staff. In that case the field had value. The team moved to a proper taxonomy inside the CMS and used internal-only metadata fields that do not appear in public HTML. This change reduced accidental public leaks and improved search relevancy.

Regional directory that still uses the tag

A small directory relied on meta keywords for a custom vertical index. The operator kept the tag but implemented a strict rule: no more than five topical terms and editorial approval required. That balance preserved the directory’s needs without encouraging broad stuffing.

How to add meta keywords safely in HTML (short code and cautions)

If you need to add the tag, keep it minimal and controlled.

Example:

Keep it to a handful of true topical terms. Don’t try to game search engines with long lists-those are ineffective and invite clutter.

Troubleshooting checklist

If after changing keyword fields you see unexpected search behaviour, check these areas first:

• Have title tags or meta descriptions been modified at the same time?
• Did canonical or URL structures change?
• Were robots.txt or noindex directives altered?
• Are there template defaults repopulating the field?
• Has the site undergone a content or CMS migration?

Governance: a short template for policy

Create a one-page policy that answers:

• Does the meta keywords field exist in production HTML?
• Who is allowed to edit it?
• How many terms are allowed?
• Where else should topical signals live (categories, tags, topic IDs)?
• Who audits the field and how often?

Apply change control: require a pull request for template edits and a content review for any mass import.

When Orvus recommends keeping or removing the tag

At Orvus Ltd., we treat the meta keywords field as legacy metadata. When clients still have it in templates, we recommend removing it unless a clear, documented internal need exists. If removal isn’t possible, we implement strict editorial constraints and map keyword inputs to internal taxonomies that do not render in public HTML. For a calm, practical consultation on rationalising metadata and rebuilding content architecture, consider our services.

Explore Orvus services for metadata and search architecture

Use this short checklist during a tidy-up sprint.

Migration checklist you can copy

Use this short checklist during a tidy-up sprint:

1. Run a full export of meta keywords values and sample the top 1,000 pages.
2. Identify templates that auto-populate the field.
3. Decide: remove, clean, or map to taxonomy.
4. Implement template edits in staging and run a full crawl.
5. Deploy to production, then re-crawl and compare rendered HTML.
6. Monitor Google Search Console for 4-8 weeks and document results.

Testing plan and KPIs

Track these metrics before and after the change:

• Clicks and impressions (Search Console)
• Average position for main queries
• Click-through rate (CTR)
• Bounce rate and engagement metrics (Analytics)

Look for correlated changes: if clicks drop, check whether title tags or canonical links changed at the same time.

Long-term editorial moves worth your time

Rather than tinkering with old tags, invest in:

• Content briefs that answer user intent
• Structured headings that map to common questions
• A clear taxonomy that supports navigation and internal reporting
• Schema markup for clear entity signalling
• A lightweight content governance process

Read more on our blog: useful knowledge and posts.

Fun fact

Meta keywords were once thought to be a powerful SEO signal-too powerful, in fact. The internet community collectively learned that easily manipulated signals quickly lose value. That lesson shaped today’s emphasis on signals that are harder to fake: quality content, user behaviour and authoritative linking.

Summary of action points

Here are the practical next steps you can take today:

• Audit: export and inspect existing meta keywords across templates.
• Decide: remove if unused, or implement strict limits if needed.
• Map: replace public keyword dumps with internal taxonomies where appropriate.
• Govern: document who edits metadata and require approvals.
• Measure: monitor search performance after any change.

Want help implementing this safely?

Final thought

Meta keywords are a historical footnote for mainstream search, but how you treat them reveals your content discipline. Cleaning up old fields is less about chasing search engines and more about running a tidy, intentional site. Small housekeeping saves time and risk later.