Can SEO tricks for SPAs be applied to compose/WASM apps?

# compose-web

[Mario Andhika]

Can SEO tricks for SPAs be applied to compose/WASM apps?

[Hristijan]

There's no HTML in Compose WASM

[Mario Andhika]

Shouldn’t there be one that contains the canvas?

[David Herman]

https://bitspittle.dev/blog/2024/c4w#seo-indexing (short answer: no)

[Daniel Weidensdörfer]

There is an html with canvas inside. I would put your text content into the body of the html for some SEO with wasm canvas on top. So still the html content is not visible, but you provide something for Googles crawler to look at.

[Skaldebane]

There's HTML that houses the canvas, but currently that's all it does.
I'm sure JetBrains will surely add a lot more "ghost" HTML nodes matching the actual Compose semantics modifiers for accessibility (Flutter does this), which could then be read by web crawlers etc (though this requires the JS/Wasm code to run, which many crawlers may not do at all).

[Skaldebane]

Currently, try to separate your landing page from the actual app.
Make a nice static landing page that is easily crawled even without running JS, to promote the app. That's great for accessibility, SEO, loading times, and everything else.

The rest of the actual app can then live in a separate page (e.g. <http://mysite.com/app|mysite.com/app> or <http://app.mysite.com|app.mysite.com> ), and that should be excluded from crawling (even apps built with HTML/CSS/JS don't try to optimize the actual dashboards and back-offices that are behind a login for SEO).

[Mario Andhika]

Thanks! I'll try that