Old website template name showing when I send a link to the website

I used a template called “Solar Tech” and this name is showing up when I attach the link to a WhatsApp message or send via Slack instead of my actual website name.

I have followed the instructions on the forum about changing the title of the page in the settings part for every page and I have done that for every page. I cannot see Solar Tech anywhere in the titles or settings but this bug is still affecting Slack and WhatsApp links - please advise.

Were you able to solve this? I’ve ran into the same issue. Did it change in time?

No, doesn’t seem like anyone checks messages :smiling_face_with_tear:

Please leave a website url, and I will check it out

you can see that Solar Tech is coming up instead of Vu Nexus

Hi Sam,
Just to clarify: You have changed the SEO information for each page? This can be done by going to the “Pages” tab, right clicking the page and click on “Settings”.

There you will find page settings to manage page SEO, meta data - used by search engines, and open graph - used by social media.

If your pages has been crawled, then the old SEO and meta data might be stuck with the old input until it is crawled again.

Also, check this thread on the subject for more details: How to remove template name from showing on open graph?

yes did all of that in Oct 24 and have updated my website multiple times and re-published so Google would have def crawled it multiple times since. Please check on your end because other people have had the same issue - there is some kind of bug on the divhunt side

Okay! thanks for the heads up, Sam. My meta data and SEO is showing up correct, but I created my websites from scratch.

Hi Stefan please can you respond? This query has been open since Oct 2024… :smiling_face_with_tear:

Hey Sam, have you tried clearing your cookies and cache?

Everything seems fine on my end, I tested it across multiple platforms.

try forwarding the website link on Slack - it still shows up as Solar Tech so the bug must be there still.

You are right, my bad. I can see it in the page source as well:

It’s probably a bug, we’ll take a look.