meta name=”twitter:creator” is wrong

  • Resolved Sturminator10

    (@sturminator10)


    6 months ago

    this is the code on my page

    <meta name="twitter:creator" content="@https://twitter.com/showprogress" class="yoast-seo-meta-tag" />

    @https is incorrect

    in the yoast settings there is no where for me to change this

    i already tried setting X under Other Profiles within Site Representation to just "showprogress" - that didn't change this code. So I don't know how to fix it.

    The page I need help with: [log in to see the link]

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support Mushrit Shabnam

    (@611shabnam)

    Hi @sturminator10

    While checking from my local site, I was unable to replicate the same error. Please check the screenshot.

    Can you kindly deactivate, delete Yoast SEO and then reinstall and activate Yoast SEO? Can you check if the issue exists?

    We recommend creating regular backups of your site and database for your site’s health and safety. A backup is crucial before making important changes on your website and provides you with a safety net if something were to go wrong. Learn more about the benefits of regular backups.

    Thread Starter Sturminator10

    (@sturminator10)

    Hello @611shabnam,

    I just tried that, but unfortunately it did not work.

    My guess is this code is coming from the previous interface of Yoast – of which I entered my information. The previous interface had slightly different fields, if I remember correctly.

    You can still see this in the code for any of my articles: https://edwardsturm.com/articles/

    And it says its generated by Yoast: https://snipboard.io/wdWSBL.jpg

    Plugin Support Mushrit Shabnam

    (@611shabnam)

    Hi @sturminator10

    Can you kindly head to WordPress dashboard > Users > profile > Contact Info > X username (without @)and check what you have added there? Do you have the full profile URL added there?

    Thread Starter Sturminator10

    (@sturminator10)

    @611shabnam Yes! This is what was causing the error. Thank you so much, this fixed it.

    Marking this as resolved now.

    Thank you, again.

    • This reply was modified 5 months, 4 weeks ago by Sturminator10.
Viewing 4 replies - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.