Remote Content asset and Nesting

#1

Hi Guys,

 

Just seeking advice for remote content assets. We have a remote content asset that we wish to nest into a standard page asset for a staff profile.

 

Just generally  for nest assets is it better to create a folder asset with no urls applied to place all these assets. I am just worried about google indexing the remote content asset on the server.

 

I would have gernally thought content that is nest content shouldn't need a preview url applied.

 

I am also worried that assets that don't have a url applied may not appear in the asset finder for the EES.

 

with thanks

(Joel Porgand) #2

Hi Guys,

 

Just seeking advice for remote content assets. We have a remote content asset that we wish to nest into a standard page asset for a staff profile.

 

Just generally  for nest assets is it better to create a folder asset with no urls applied to place all these assets. I am just worried about google indexing the remote content asset on the server.

 

I would have gernally thought content that is nest content shouldn't need a preview url applied.

 

I am also worried that assets that don't have a url applied may not appear in the asset finder for the EES.

 

with thanks

If nothing links to it, google won't index it. So long as it's not going to show up linked anywhere like menus or your sitemap it shouldn't be an issue.

 

That said, for content you really don't want indexed, having a folder with no urls is probably a good idea as it'll prevent accidents from happening.

 

Assets without a url applied will still appear in the EES asset finder so long as they're under the site asset node.

(Nic Hubbard) #3

You could also just use a paint layout on the Remote Content asset and then print the contents and whatever markup you want. Might be cleaner than nesting it in a Standard Page.

#4

Thanks JP and Thanks Nic - You guys always get back to me and it's very much appreciated. I think the no urls option is the safest for nest content JP so i'll go with that. 

 

 I agree Nic nesting in a standard page is a bit messier, however for our EES users they may understand nest content better - plus you cannot apply a new paint layout in the EES without having to go into admin so i'm thinking of quick wins.

 

Apologies I should have mentioned it was for our EES users.

(Nic Hubbard) #5

Thanks JP and Thanks Nic - You guys always get back to me and it's very much appreciated. I think the no urls option is the safest for nest content JP so i'll go with that. 

 

 I agree Nic nesting in a standard page is a bit messier, however for our EES users they may understand nest content better - plus you cannot apply a new paint layout in the EES without having to go into admin so i'm thinking of quick wins.

 

Apologies I should have mentioned it was for our EES users.

 

Ah, got it. No worries.