Support » Plugin: Yoast SEO » YOAST warning is not true!

  • Resolved Demir

    (@sdarthenos)


    Hello,

    When editing an article with Gutenberg, a warning like this appears on the screen. However, there are both internal and external links in the article. WordPress, Gutenberg and YOAST plugins are up to date.

    Why does this warning appear, is there a solution?
    Thanks in advance for your attention and help!
    Regards.

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

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support devnihil

    (@devnihil)

    There are a few cases where a link might not be recognized:

      Only links from inside the WordPress post editor are recognized. This means that links from navigational bars, menus, sidebars or footers are not recognized.
      ​Links need to be in absolute form. This means that links need to include the full domain. For example, http://www.example.com/page-a is an absolute link, while /page-a/ is a relative link.

    ​The internal linking tool will only recognize links on the page that are input in the standard fashion of including a text based link from within the WordPress editor, and not from links that were created using modules of other plugins in WordPress, such as many page builders for examples.

    Plugin Support amboutwe

    (@amboutwe)

    This thread has been marked as resolved due to a lack of activity.

    You’re always welcome to re-open this topic. Please read this post before opening a new request.

    Thanks for understanding!

    Demir

    (@sdarthenos)

    Hello again,

    I think I couldn’t explain the problem clearly. We use the standard paragraph block of the Gutenberg editor. When we first viewed the article, there was no problem as seen here. However, we receive such a warning when any minor changes to the document (even if a null character is added).

    Although all web addresses on the page are correctly defined, the warning continues, unless we save the article and refresh the page.

    Something is wrong, this is certain. I think this is a bug. And that’s why I opened this support issue. If I am wrong, I would like you to tell me where I made a mistake or what to do.

    Thanks in advance for your attention and help.
    Regards.

Viewing 3 replies - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.