Why isn't this SEO feature enabled for new sites by default?
There's a change we made that affects SEO but is only enabled if the CSM does it.
Have we considered simply making it enabled by default if it's supposedly best practice for SEO per the doc. I know it says that it could maybe break other sites but we should be thinking about the new sites for this change specifically then.
Also, maybe CSMs should be mentioning this change to their customers if it is in fact better and we do in fact say that we are optimized for SEO.
Comments
-
Seem to me the Release notes fail to mention why Vanilla blocks a page from rendering until most of its javascript is loaded, in the first place. I assume there was a reason for the original decision. Not saying this info should be in the Release notes, but it is needed for a complete explanation before deciding if it should be the default.
0 -
I THINK this is because of pockets. Current javascript pockets may rely on a particular script to be already loaded when it's rendered.
0 -
In that case, I'd say they're correct to not enable it by default. Adding a UI option to turn it on, instead of contacting the CSM, might be nice though.
0 -
What could be done is to set that feature to false for all current site where it's not explicitly enabled and turn that feature ON by default going forward.
The result would be that new customer would benefit from that from the get go without breaking stuff for old ones.
0 -
What's the process to get that implemented? Is Ops in charge of default site settings?
0 -
You'd have to talk with R&D. No it's a feature flag so it's in Vanilla.
This is all assuming that I'm right about the reason.
0 -
Part of this is a process problem. Feature flags (these
Feature.X.Enabledconfigs) shouldn't be for long-term use. They're mainly used for controlled testing of new features. After that testing period, they're usually either upgraded to an official product feature or canned. It looks like this was introduced back in March. We probably tested it on some sites and never followed up on making an official decision. That decision would probably need to be made before we can start automatically enabling it for all new customers.1 -
We actually did plan it out (before this thread was created) and it's just been completed.
The toggle and and new default behaviour will be going out in the first release next year
2020.001.We have knowledge base article ready with information about the feature and how to enable on existing sites as well.
1