1import{M as l,N as g,O as c,p as u}from"./2fLglP_K.js";const d=async e=>{const n=e?.robots;let r="";e?.robots==="INDEX,FOLLOW"&&(r=", max-snippet:-1, max-image-preview:large, max-video-preview:-1"),l({title:e?.title,description:e?.description,robots:n+r,ogSiteName:"Weleda",ogTitle:e?.title,ogType:"website",ogUrl:e?.canonical,ogDescription:e?.description,ogImage:e?.image.image.mediumUrl,twitterDescription:e?.description,twitterCard:"summary",twitterTitle:e?.title,twitterImage:e?.image.image.mediumUrl});const s=u(()=>e?Object.keys(e?.alternateLanguageLinks).map(i=>({hreflang:i,rel:"alternate",href:e?.alternateLanguageLinks[i],key:i})):[]),{localeProperties:o}=g(),t=o.value?.language||o.value?.code;c({link:[{rel:"canonical",href:e?.canonical},...s.value],htmlAttrs:{lang:t}})};export{d as u};
Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.