Product Title displaying GID and want to get rid of it

Topic summary

• Main issue: After work to add product variants by linking other products via meta fields, a specific product’s title began showing a “GID” string in the Impulse theme. The poster asks how to hide the GID on the linked product page.

• Suggested cause: A respondent says a custom code snippet was added that injects the GID into the title, and reverting those changes should fix it. They note the Impulse demo does not exhibit this behavior.

• Follow-up: The original poster did not implement the change and lacks access to the developer, asking how to locate the offending code. No concrete method for finding the code was provided in the thread.

• Current status and action: The poster created a new product to avoid the issue and archived the affected one since only that product was impacted. The root cause remains unidentified; they welcome further insight.

• Notes: A screenshot was attached illustrating the GID appearing in the title. The discussion has no definitive resolution and appears open.

Summarized with AI on January 2. AI used: gpt-5.

I was working with a developer who was showing me how we could add product variants by linking to other products in meta fields. He decided to not continue the work for his own reasons, but he did something on the page/product linked below that causes the “GID” for the product to be displayed in the product title.

Does anyone know how to hide the GID in the product title on the linked page?

Theme is Impulse

https://imperialcashmere.com/collections/cashmere-gloves/products/absinthe-green-cashmere-gloves

Somewhere in the code you added a piece of a code which adds this GID revert the changes and it will be fixed.

You can see in demo of the Impulse there is no such issue

I get that in a way this is the answer… but it’s not helpful. I did not personally make the change and don’t have access to the developer that did. is there a way to find that piece of code?

I ended up just making a new product since it was only affecting this one, and just archived the old product with the issue, but if anyone comes across this and knows why it appears i would appreciate any insight.