Developer forum

Hi Michael

Yes, that would make sense.

So clicking "unpublish" button would trigger a choice of 2 options

1. Only Unpublish this page and leave subpages published (default and like now)
2. Unpublish page and all subpages (new option)

BR Nicolai

Hi Nicolai,

Yes :)

Though would it mark them as only inherited, or are you suggestion that the subpages will be directly marked as unpublished?

It would be nice if you were to Publish/Unpublish the parent page, all the subpages that are published/unpublished/hidden stay unaffected.

I would push it down. Otherwise you cannot make exceptions etc.

Hmm - we are not to keen on the "Pushed" down method.

The main issue we see the most is when an Editor unpublish a page with subpages, google will still manage to find them via sitemap, since a normal Editor would not think to change the subpages page settings to hide from sitemap and what not.

Maybe all that is required is really just to give make a inherit "noindex,nofollow" function, like the exact way we can inherit page "Layout" templates to subpages, and make this option clear to a user, or maybe prompt it to the user when unpublishing a page withsubpages, instead of the whole Publish/Unpublish marking shibang on subpages?

If a page is unpublished, it will not be indexed by anything. It will return a 404.

if you are logged into the backend, you can view the pages though. If you are not, no one can see them.

By pushing the setting down every page would disappear from sitemaps etc.

So you prefer:

2. Unpublish page and all subpages (new option)

That is fine as well - better than no option ;) 

Yes, and ultimately it is the same thing. This approach is just explicit and you can opt out of it for specific pages.