Hello!
Those pages are generated by “tagDiv Opt-In Builder” during the installation. They are registered among your other pages, and I recommend applying “noindex” to the pages “Checkout,” “My account,” and “Login/Register.”
TSF might’ve highlighted these pages to search engines via its sitemap, but the affected sites you listed use all sorts of SEO plugins and face the same issue.
Please note that the “tagDiv Opt-In Builder” plugin also generates a few public post types that ought to be private. Among these are tds_email
and tds_locker
. tdb_templates
, tdc-review
, and tdc-review-email
are referred to in their code as well, and from a few sites I found them on, those appear to be incorrectly registered as “public” too.
So, I recommend applying ‘noindex’ to all those post types via “SEO Settings > Robots Meta Settings > Indexing > Post Type Settings.” If a post type isn’t listed there, it either isn’t registered or public.
Without a URL to your site, I cannot dig further into potential issues caused by these plugins. Still, I hope the above instructions already help 🙂 Cheers!
Very insightful … thank you!
At “SEO Settings > Robots Meta Settings > Indexing > Post Type Settings.”
Apply noindex
to Posts? – post
Apply noindex
to Pages? – page
Apply noindex
to Media? – attachment
Apply noindex
to Reviews? – tdc-review
[?]
Apply noindex
to Cloud Templates? – tdb_templates
[?]
I have the following setting set
General > Exclusions > Post Type Exclusions set for
(checked) Reviews – tdc-review
(checked) Cloud Templates – tdb_templates
So there isn’t an option to disable indexing tds_* entries
Perhaps this is something that needs to be added to the SEO Framework
Thank you for your very thorough explanation – very much appreciated !!!
My pleasure 🙂
I recommend disabling the exclusions because those don’t block search engines. In TSF v5.0.5, I tried to improve the explanation of these settings by adding the following in bold red:
Exclusions don’t block search engines. When a post type is publicly queryable and shouldn’t be indexed, consider applying noindex via Robots Meta Settings to purge it from search engines.
After you disable the post type exclusions, you can check the “noindex” option again for the post types. Do not reactivate the exclusions, as they disable the “noindex” option for the post type.
TSF automatically supports all custom post types registered with WordPress; I didn’t know about the tagDiv plugin before you mentioned the issue. It is up to the post type developer to register them correctly. Otherwise, I’d be maintaining thousands of post types. When a post type isn’t publicly viewable, TSF won’t acknowledge it.
But, the developers of “tagDiv Opt-In Builder” did register the post types correctly (I didn’t look closely enough before): they did set 'publicly_queryable' => false
for the tds_*
post types, so TSF doesn’t acknowledge them, and neither visitors nor search engines can view any of its posts. So, this is all good 🙂
The tdc-review
and tdb_templates
post types still require some tweaking, however. I don’t know the plugin that registers these.
-
This reply was modified 6 days, 4 hours ago by
Sybre Waaijer. Reason: More info