augment require_head method

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.

Hey, @tony5280 :waving_hand: 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