Expand my Community achievements bar.

Submissions are now open for the 2026 Adobe Experience Maker Awards.
SOLVED

How to prevent AEM from adding meta tag "keywords"?

Avatar

Level 1

Hi All,

 

I'm not sure what is adding a meta tag to all pages based on that page's tags some, something like this:

<meta name="keywords" content="Blogs,Workplace Security">

 

The problem is that, we are not adding this in our code, in fact we are overriding the head.html for all templates.This tag is only added on the AEMaaCS instances and not on local environments. Also, the tag is not inserted by JavaScript on the client side.

 

Does anybody have any idea where to look for this?

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Hi @ReneDa 

If you are using core components then it is added from /libs/core/wcm/components/page/v3/page/head.html 

https://github.com/adobe/aem-core-wcm-components/blob/a0866659765c7225bb3139ed180cc7e90686c203/conte...

you have to overlay the head.html in your page component in order to adjust htl.

Arun Patidar

AEM LinksLinkedIn

View solution in original post

4 Replies

Avatar

Community Advisor

Hi @ReneDa,

This meta tag comes from the page tags set in Page Properties (Basic tab).

Screenshot 2025-09-03 at 2.31.12 PM.png

When a page has cq:tags assigned, the default Page component (both foundation and Core Components) will automatically render a

<meta name="keywords" content="...">

element in the page head. The values are taken directly from the page’s tags and concatenated into a comma-separated list.


Santosh Sai

AEM BlogsLinkedIn


Avatar

Correct answer by
Community Advisor

Hi @ReneDa 

If you are using core components then it is added from /libs/core/wcm/components/page/v3/page/head.html 

https://github.com/adobe/aem-core-wcm-components/blob/a0866659765c7225bb3139ed180cc7e90686c203/conte...

you have to overlay the head.html in your page component in order to adjust htl.

Arun Patidar

AEM LinksLinkedIn

Avatar

Level 10

Please review your Sling Model implementation. If we assume you are using core components, the keyword values are generated by utilizing the "Tags" field, as mentioned by Sai - so it does not explain your situation. Is it possible that your model has implemented custom logic to inherit from the first parent page that has a non-empty "Tags" field?

Avatar

Administrator

@ReneDa Just checking in! Were you able to get this resolved? If you found your own solution, sharing the details would be a big help to others who might face the same issue later on. And if one of the replies here helped—whether it fully solved the problem or simply pointed you in the right direction—marking it as accepted makes it much easier for future readers to find. Thanks again for helping close the loop and contributing to the community!



Kautuk Sahni