csanchez.work
posted this
01 September 2021
Hello. I have the same issue. I have been reading all similar post here in the 'previous posted questions'. I ask too if you (nicepage team) could implement the possibility of dissable the automatic generation of the schema. Doing this, you have not to implement edit screens or anything complicated like that, because we (users) can add the script code in header html.
As a second workaround for you (nicepage team) for this issue of the schema ld-json and the problem with the logo url and the SEO, Could you please force that the 'url' generated be a complete "https://yoursite.com/path-to-image-logo" (instead of relative url starting in "image/rest-of-the-path" ? I have notice that this solves the problem that Google warning about SEO.
For the user who read this. For now, we have to, manually, after export, change in the zone of ld-json schema, "logo": "images/logo.png" to logo url: https://yoursite.com/images/logo.png and Google smiles happy. and you too.
Hello. I have the same issue. I have been reading all similar post here in the 'previous posted questions'. I ask too if you (nicepage team) could implement the possibility of dissable the automatic generation of the schema. Doing this, you have not to implement edit screens or anything complicated like that, because we (users) can add the script code in header html.
As a second workaround for you (nicepage team) for this issue of the schema ld-json and the problem with the logo url and the SEO, Could you please force that the 'url' generated be a complete "https://yoursite.com/path-to-image-logo" (instead of relative url starting in "image/rest-of-the-path" ? I have notice that this solves the problem that Google warning about SEO.
For the user who read this. For now, we have to, manually, after export, change in the zone of ld-json schema, "logo": "images/logo.png" to logo url: https://yoursite.com/images/logo.png and Google smiles happy. and you too.
