For creators
Tenant SEO + meta tags
Browser tab titles, share previews, and structured data all read from your portal config — not 'The Big Class'.
Every /p/<tenant>/* page mounts a DynamicMeta client component that patches <head> with your tenant brand. Tab titles read '<page> · <your brand>'; Open Graph + Twitter share previews use your logo + brand name.
Per-page overrides
- Blog posts: post.seo.title / .description / .ogImage take precedence over auto-fields.
- Course pages: include a Course JSON-LD payload (Schema.org) with provider, author, image.
- Store pages, library, blog list — all picked up automatically.
Why this matters
When a student shares your course link in a WhatsApp group or on LinkedIn, the preview that unfurls is your brand — your logo, your title, your description — not a generic platform card. And because course pages ship Schema.org structured data (provider, author, image), Google and AI answer engines can understand and surface your content as yours. It's SEO and social proof working for your brand instead of the platform's.
Common questions
- Do I have to configure meta per page? No — titles and previews are generated from your brand automatically; you only override when you want something specific (e.g. a blog post's custom image).
- Can I set a custom title/description on a blog post? Yes — post-level SEO fields take precedence over the auto values.
- Does my course show up in Google with rich data? Course pages include Course JSON-LD, which is what enables rich, machine-readable results.
Related