Disable the generator, not one rendered page

Remove meta keywords at template source

First locate where the tag enters HTML: an SEO-plugin setting, CMS field, theme or hook. Save a backup, disable keywords only and verify other metadata across several templates.

Meta keywords removal process: locate source, back up, disable output and verify metadata
Source → backup → disable → verify templates.

Message for a developer or support team

“Locate the <meta name="keywords"> generator in the SEO plugin, theme, hook or template. Save the existing setting and disable keywords output only across public templates. Do not remove title, meta description, robots, canonical, viewport or Open Graph. Clear caches and provide source HTML from representative pages before and after.”

What to prepare

  • a backup of the theme, settings and related database fields;
  • home and one page from every public template;
  • a required-metadata checklist for comparison;
  • staging or a quick way to restore the setting.

Step-by-step removal

  1. Open page source and confirm the exact meta name="keywords" tag exists.
  2. Inspect SEO-plugin and CMS settings, then search templates and hooks for keywords.
  3. Record current output and create a backup.
  4. Disable the field through configuration; when unavailable, remove only its template call.
  5. Retain stored fields used by internal search or another process; stop public output only.
  6. Clear page, template and CDN caches that may retain old HTML.
  7. Inspect source and rendered HTML on every representative template and compare adjacent metadata.

Technical reference

rg -ni 'meta[^>]+name=["'"']keywords["'"']|name=["'"']keywords["'"']' \
  resources/ app/ public/

curl -sS https://example.com/ \
  | rg -ni 'name=["'"']keywords["'"']'

A repository search may find documentation, comments or an admin field. Change only the public tag source.

Risks, rollback and separate work

An overly broad change to <head> can remove important metadata. On failure, restore the template or setting, clear caches and compare the checklist. If theme updates restore keywords, move the change into a supported override or child theme.

Use the verification guide afterwards. Keyword research, title, description and content optimisation are separate. For a complex CMS, order the removal.