Start with crawlable pages
Public pages should render a clear title, meta description, H1, canonical URL, and useful introductory content before any interactive work starts. Search engines and link previews need stable page signals, not only client-side state.
What to check
- Important routes return 200 or a clean redirect.
- The first HTML response does not include reconnect, debug, or sample-result noise.
- Tool pages show the workspace first and explanatory content below it.
- Sitemap URLs match canonical URLs.
Common mistakes
Do not rely on one generic app title for every page. Also avoid rendering hidden blocks that contain stale labels, internal status text, or disconnected UI messages.
FAQ
Can a Blazor app rank in search?
Yes, when public pages expose clear server-rendered content and metadata.
Should every interactive state be indexable?
No. Index the stable canonical page and keep filters or temporary states noindex when needed.