# augment require\_head method

**URL:** <https://community.hubspot.com/t/augment-require-head-method/107974>\
**Category:** CMS Development\
**Tags:** professional\
**Created:** [May 24, 2024, 8:09pm UTC](https://community.hubspot.com/t/augment-require-head-method/107974 "2024-05-24T20:09:58Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![tony5280](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/tony5280/32/202741_2.png) [@tony5280](https://community.hubspot.com/u/tony5280)\
**Post date:** [May 24, 2024, 8:09pm UTC](https://community.hubspot.com/t/augment-require-head-method/107974/1 "2024-05-24T20:09:58Z")

</div>

Would like to use (a) this method to push a canonical or a robots to the head without creating a conflict - override/clobber/supercede any previous or existing auto-generated values.  
I’m trying to think of a good reason to push duplicate or conflicting values into the head, and there may be some, but I can’t think of any at the moment.  
I can turn off auto-canonicals, and push it to the header manually, but then admin users (the seo guy) loses the ability to declare canonical overrides on individual page settings.

---

<div class="post-metadata">

**Author:** ![Jaycee\_Lewis](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/jaycee_lewis/32/61352_2.png) [@Jaycee\_Lewis](https://community.hubspot.com/u/Jaycee_Lewis)\
**Post date:** [June 4, 2024, 11:53pm UTC](https://community.hubspot.com/t/augment-require-head-method/107974/2 "2024-06-04T23:53:53Z")

</div>

Hey, @tony5280 👋 Thanks for the interesting question. Did you decide on how to proceed with your project? I don’t have the answer or a specific suggestion.

From my understanding:  
Pros

• Prevents multiple conflicting tags  
• Admins can still override canonical tags on individual pages  
• Maintains clean and accurate meta information for search engines

Things to consider:

• Ensure the script runs after everything is fully loaded  
• Managing updates to avoid performance issues  
• Timing of updates to prevent race conditions  
• Ensure cross browser compatibility  
• Setting tags to reflect your SEO strategy

Best,

Jaycee