something wrong with meta

Hi @wayneg03
While you still can edit your post (within 60 minutes), I’d suggest that you enter the address (URL) of your site in the special URL field, which is only visible to logged-in users and thus won’t be seen by search engines.
It will just be so much easier for someone to help you if they can have a look at your site themselves.

Disclosing my URL publicly is not what i need right now.
If support want to actually help then i might give it to them personally, not that taking a browse is going to reveal what code is not functioning, that would require admin permissions.
This is a serious issue, enough to break the whole plugin, yet they ignore me.

Hello!

I feel obligated to jump in on this matter with my perspective. Please excuse me, for although I do not intend to, I might come off peevish.

If support want to actually help […]

We’re always here to help!

Please note that these forums are powered by volunteers, like Tor-Bjorn and me. We bring support on these forums because we feel it’s the right thing to do; at the same time, you can’t expect anyone to reply and move everything aside–things they have to deal with in their (personal/business) offline-life.

There are real humans on the other side, with real lives and real families. Please do understand that these odd times of crisis affect us both physically as mentally. With that, you can’t expect everyone to be as responsive or in high spirits as they usually are. Circumstantially as an example, my neighbor’s dog could really do with a more responsible owner.

Nevertheless, I always try to help our users as quickly as I can, both in goodwill and–let’s be transparent–from a business perspective.

[…] not that taking a browse is going to reveal what code is not functioning […]

Browsing your site will help us spot or deduct any possible (known) issues; in this case, we’re dealing with four possible scenarios.

We (well, I) live and dream TSF’s code and its output–even a single space-character too many could tell us the problem, and it could allow us to replicate the issue. Moreover, we no longer have to assume that what you try to convey is fallacious or fact. Lastly, we can quickly assert which plugins and themes are active, possibly affecting the plugin’s behavior.

For over 3200 replies I made for this plugin, I have never had to ask for admin permissions. For good reasons, it’s also not allowed.

Now, I have to look at your activity on the forums to guess where things might’ve gone wrong ?? This takes tremendous effort and will always result in wasted time for both you and me. Not to mention, there are inaccuracies involved.

Courteous proactivity will help us help you.

[…] yet they ignore me

I’m sure we’ve never ignored you. I take you’re referring to another plugin’s support topic?

With that out of the way…
Here are the four known issues that might explain the issue you’re encountering:

1. Google hasn’t yet processed your changes. After you update your website, Google must first go to your website, fetch the page, process its contents, and only then they may index it. Here Google explains how crawling and indexing works.
2. Google ignored your changes. Sometimes, Google recognizes that your input isn’t well-suited for certain (or all) search queries, and they can replace it with content taken from your page, or even from their caches obtained elsewhere. From Google’s documentation: “Google will sometimes use the <meta> description tag from a page to generate a search results snippet, if we think it gives users a more accurate description than would be possible purely from the on-page content.”–You can experiment with this via a site:-query.
3. WCFM Marketplace builds on top of WordPress. And, it’s therefore not a part of the WordPress API we should communicate with. Here’s some background information. I had to assume you use this plugin from your forum activity.
4. The term might have assigned an ID that’s similar to a post/page/product. And that causes TSF to assert your term to be both a page as a term, causing a fail-safe to engage. The fail-safe prevents TSF from outputting any SEO-metadata, so that saved us a major headache. This issue is most prominently present when using WooCommerce, and it already has already been addressed. A patch is underway. Again, I had to assume you use this plugin based on your forum activity.

I hope this abundant information helps! If you wish for me to take a closer look, then a URL to the affected webpage would be most helpful. Cheers!

*update:
I have resubmitted a more extensive sitemap and created new meta title/description for every page, now things are looking much better.

thank you for your time.

I’m glad everything worked out ??

If you require further assistance with anything else, feel free to open a new topic. Cheers!