“SEO on only these post types” lists Posts multiple times

If I had to guess, I’d say another plugin or theme is causing this… possibly by creating additional post types called posts.

You can narrow this down with these steps: https://semperplugins.com/documentation/how-to-troubleshoot-issues-with-all-in-one-seo-pack/

You are right ??

For future reference for anyone else that may have this issue:

Issue is being caused by WPForms Lite plugin.

Thanks for your help.

Hey Michael,

It seems AIOSEO is displaying ALL post types, even the ones that have public disabled.

The function to return a sites post types normally excludes these post types (https://codex.www.ads-software.com/Function_Reference/get_post_types).

We don’t provide our custom post types any labels because public is disabled and they are not exposed to the UI at all. They are for internal use and we reference them using the slugs.

So in this use case, AIOSEO is pulling our private post types, then simply displaying ‘Posts’ since they do not have a label defined.

Maybe this is the intended, but just wanted to let you know (and anyone else who stumbles upon this via search)!

• This reply was modified 7 years, 4 months ago by Jared Atchison.

Hi Jared,

Thanks for explaining, both here and at the issue that I posted with your plugin at https://www.ads-software.com/support/topic/issue-being-caused-by-wpforms-plugin/#post-9703200.

Presuming Michael would agree that this is the cause, could I ask you to consider the following:

Jared – If possible, give your private posts types a suitable descriptive name, so that they do not show up as “Posts”.

Michael – If possible/suitable, show only public post types in your list of CPTs to apply SEO to.

In any case thank you both very much for your help.

@jaredatch Thanks, I’ve opened an issue here: https://github.com/semperfiwebdesign/all-in-one-seo-pack/issues/1373

@ironfish2 You can just ignore the extra ones from WPForms.

Hi Michael,

Thanks for creating a ticket about this issue.

As for ignoring the extra ones, since they are all 3 called Posts, I can’t do that ??

One could guess that the first one in the list is the correct “Posts” but there is no distinction that sets them apart.

I have up until now checked all three to have SEO applied to which I am sure adds processing overhead.

I will try it with just the first Posts checked.

• This reply was modified 7 years, 4 months ago by ironfish2.

I’m not sure what the problem is, other than an aesthetic one.

a) It’s most likely the first one, next to pages.
b) You can figure it out by trial and error (max three tries).
c) Checking the rest will do no harm, including no extra resource usage.

We’ll be providing a label to our private post types in the next update, so this should resolve the conflict with our internal post types in the future ??

@jaredatch

Awesome, looks like it will be taken care of from both sites soon.

Hi Michael:

I’m not sure what the problem is, other than an aesthetic one.

Ok, well here are the problems as I see it:

1) Your plugin is listing private CPTs to users when it should not

2) Your plugin lists Posts three times, and it there is no definite way to know which one is which CPT

2a) If a user selected the wrong Posts, then your plugin would not add SEO to the right Post type. Things would not be working properly. That is technical issue and definitely NOT an aesthetic problem.

3) Suggesting a trial and error solution to a problem that should not be there in the first place.

4) If you dont see the problem, why have you created a github ticket for it?

As for suggesting:

a) It’s most likely the first one, next to pages.

Yep, that is what I just said, prior to your last post.

b) You can figure it out by trial and error (max three tries).

Yes, that is why I said I will try the first one, prior to your last post.

PS you are welcome for me taking the time to identify by plugin the cause of this issue and working with both plugins to identify things further and suggesting resolutions. Sorry I bothered you with this non-existing problem.

• This reply was modified 7 years, 4 months ago by ironfish2.
• This reply was modified 7 years, 4 months ago by ironfish2.

I was referring to this: “As for ignoring the extra ones, since they are all 3 called Posts, I can’t do that ”

As in, I’m not sure what the problem is with you, ironfish2, ignoring the extra CPTs for now… not that there isn’t a problem at all. Obviously there is, hence the github issue.
a, b, and c were for you specifically to deal with this in the meantime, since you said you couldn’t ignore it, not as permanent solutions or for anyone else.

I’m unfollowing this thread as it’s unproductive.

• This reply was modified 7 years, 4 months ago by Michael Torbert.
• This reply was modified 7 years, 4 months ago by Michael Torbert.