Tuesday, March 3, 2020
Well after trying it for a couple of projects, here's everything that is wrong right now.
Google doesn't index Blazor sites. It doesn't load the webassembly. It only parses what's on the page before the webassembly loads.
The suggested solution to this is to also generate the page serverside as a placeholder. If you're doing that you might as well make the whole site serverside imo.
I'm sure if enough sites go webassembly that Google will have to eventually start loading them up and indexing them properly - but it ain't happening yet.
3. Source Code
You'd think since you're compiling to webassembly your code would all be jumbled up assembly that no-one can download and understand? Right?
Nope. It's legit c# dlls. You can download them and decompile to view the contents like any other .net dll.
4. Download Size
Maybe since they're all common Dlls they're versioned and downloaded and cached from a microsoft cdn, so once you've visited a blazor site you already have 90% of the content cached?
Nope. Hope you like downloading 5mb to view a single page with the words "Hello World"
This is all new, so I'm sure all this stuff will get better over time, but for me right now it isn't ready to replace anything that needs indexing that gets casual viewers.