SiteDefaults are not localizable

[svdigital-development]

SiteDefault ("/seo-pro/site-defaults/edit") are NOT localizable.

Blueprint sets some of them (ie. Meta Title, Meta Description, Site Name) as such, but actually it's impossible to translate them.

Furthermore, the yaml file where this data is saved (at least according to the default of the seo-pro config) is located in /content/seo-pro.yaml. This effectively prevents the possibility of locating its content.

The file should be saved in a dedicated folder within /content, e.g. /content/seo-pro/, in which the file is saved in the different sites, e.g. /content/seo-pro/default/seo-pro.yaml, /content/seo-pro/french/seo-pro.yaml, /content/seo-pro/german/seo-pro.yaml...

The SiteDefaults class should therefore handle the "cascade" of the values starting from the "default" locale and adding/overwriting the values of the selected locale.

Finally, the form to use I think should be the one used eg. in Globals, where the field to select the Site is next to the "Save" button above the form, on the right.

[mattmultiplied]

We're having the same issue, all the fields say localisable but they're not. This is also the case for the section defaults too.

[Swennet]

Same here! +1

[rubzie]

This can actually be quite important, we're now content editing a dozen (sub)sites next to an already live main site. Al the sub sites are indexed by Google already, which is causing big problems for SEO of course... We wanted to set them to noindex but that caused all sites to be noindex, panic ensued... 🫨

[johannitsa]

+1 Same here

[jesseleite]

Some site default values can be localized using the From Field option, and referencing another localizable field. But admittedly this isn't an option for things like 'Site Name'.

I realize this is a long-standing issue, but just wanted to say that we definitely have plans to improve multisite support in SEO Pro 👍