• Resolved maryb1

    (@maryb1)


    Hi,

    I’m noticing that when I create a new post or page, it always says Default (noindex) in the SEO setting in the post or page. This is the case even if I didn’t set noindex to pages and post in my SEO settings.

    See: https://imgur.com/a/YIQDO1n

    When I look at the source code of the posts and pages, it doesn’t say noindex (unless I select the “noindex” option instead of “Default (noindex)”, so the posts and pages are being indexed.

    But this is a bit confusing. Shouldn’t instead say Default (index)? Is there a way to fix this so that it reflects the fact that the page is being indexed?

    Thanks!

    • This topic was modified 3 weeks, 5 days ago by maryb1.
Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Sybre Waaijer

    (@cybr)

    Hello!

    When those options are unchecked, it should say “Default (index)” for new, unedited posts.

    There may still be other parameters influencing this.

    Before the page is loaded, this is assessed for a new post for the default indexing state:

    1. TSF’s robots meta is filtered via the_seo_framework_robots_meta_array. Since this requires a developer’s intent, I assume this is unlikely.

    While a page is edited, this may influence the default indexing state:

    1. When the post has a password, it’ll be set to “noindex.”
    2. When the post is marked private, it’ll be set to “noindex.”

    If you’re using TSF v5.0.2 or earlier (we’re now at v5.0.6), it had an odd bug with WordPress v6.2 and later where a non-existing page could be interpreted as the homepage when the homepage is not assigned correctly via WordPress’s Reading Settings. If the homepage has set “noindex” via TSF’s settings, then I suspect that would reflect in a new post’s SEO settings.

    • This reply was modified 3 weeks, 5 days ago by Sybre Waaijer. Reason: clarity
    Thread Starter maryb1

    (@maryb1)

    This happens on pages that don’t have a password and aren’t marked as private. I’m using the latest version 5.0.6 and WP  6.5.4.

    Are there any other situations that could cause this?

    Thread Starter maryb1

    (@maryb1)

    I know what causes it, it’s a plugin called LH Archived Post Status that sets the default visibility status to private (even if the posts aren’t really private). I’ve contacted them to see what can be done at their end. Thanks!

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