Thread Starter
dav74
(@dav74)
Ahh ok my mistake again I guess. If the HTML block is set to “index” then it will apepar in the sitemap which of course we do not want as it is not a page.
So it is best they are all kept as they are on “default (no index)”. And I presume all these html blocks can be read by search engines in any case, no matter what their visability options are set to (provided they appear front end on the site).
I’m not sure if those “HTML blocks” are publicly accessible, but they’re probably registered incorrectly with 'public' => true, (or otherwise 'publicly_queryable' == true) by its plugin author.
From what I understand, the “HTML block” acts as a separated page — you insert the content of that page into another page via a shortcode. While you do so, you do not transfer any SEO information because each page is evaluated as an isolated instance by TSF. The page which you request directly determines what TSF outputs; the page that holds the shortcode manages SEO, the shortcode itself is ignored.
If you wish to affirm your pages are indexed, you can do so via Google Search Console. Please see this page (and video) for more details: https://support.google.com/webmasters/answer/9012289?hl=en.
I recommend keeping the HTML Blocks deindexed until the plugin author rectifies their post-type-visibility status.
Thread Starter
dav74
(@dav74)
Thanks @cybr for your detailed reply. Well I am presuming that the HTML blocks just add to teh page content and are not hidden (I can see them in page source). I will keep the HTML Blocks deindexed as you suggest.
