SEO
Search Engine Optimization
How wissenflow.com is built for traditional search, canonical URLs, sitemaps, metadata, and structured data.
Direct answer
Wissenflow uses subdirectory first canonical URLs, automated sitemaps, Open Graph metadata, and JSON-LD schemas so Google and Bing can index product and educational content reliably.
Canonical URL architecture
Every page declares a single canonical URL via alternates.canonical. The @wissenflow/seo package centralizes URL building so staging and production never drift. Vertical pages resolve to /{slug} paths on the hub origin.
Crawlability
robots.txt allows indexing of public marketing routes and points crawlers to sitemap.xml. Noindex is reserved for drafts or internal-only routes via buildMetadata({ noIndex: true }).
Metadata & social cards
buildMetadata() sets title templates, meta descriptions, Open Graph tags, and Twitter cards consistently. Product and content pages inherit the same pattern for predictable SERP snippets.
Content hubs for long tail search
The glossary (/glossary/{term}) and blog (/blog/{slug}) create indexable long tail entry points. Each glossary term is a standalone page with DefinedTerm schema and a direct definition in the first paragraph.
Frequently asked questions
- What SEO strategy does Wissenflow use?
- Wissenflow consolidates marketing SEO on wissenflow.com using subdirectory routes (/finai, /finbild), canonical tags on every page, a generated sitemap.xml, robots.txt, and JSON-LD structured data for organizations, software products, articles, and glossary terms.
- Does Wissenflow use separate domains for SEO?
- No. The hub uses a subdirectory first strategy: all indexable marketing pages live under wissenflow.com. Product apps run on subdomains (finai.wissenflow.com, finbild.wissenflow.com) with separate authentication and are not duplicated as canonical marketing URLs.
- What structured data does wissenflow.com publish?
- Organization schema site wide, SoftwareApplication on product pages, Article on blog posts, DefinedTerm on glossary entries, FAQPage where applicable, BreadcrumbList on nested pages, and WebPage on discoverability documentation.
- How does the sitemap work?
- sitemap.xml is generated at build time from static hub paths, vertical marketing routes, and dynamic blog and glossary slugs. Each URL includes lastModified, changeFrequency, and priority hints for crawlers.