OmniCon 2.0.210 — Sign in with Google or Microsoft, magic-link sign-ups, a fresh-channel welcome, real per-article rank, and more

June 19, 2026

Twelve versions on from 2.0.198. The headline is a much shorter path from "I want to try OmniCon" to "I'm editing a real article" — sign in with Google or Microsoft, or skip passwords entirely with an email magic link, and either way you land directly in a freshly-provisioned channel with a "What are you building?" welcome card that seeds sample articles in your shape. On the SEO side, the rank numbers next to each keyword are now actually per article rather than channel-wide aggregates, and a long-running canonical-URL story is finally honoured end-to-end for customers who consume OmniCon via API and render on their own domain.

2.0.210 is twelve versions on from 2.0.198. Five things stand out: social sign-in for Google and Microsoft, magic-link sign-up as a password-free alternative, auto-provisioned starter channels with a one-click welcome & sample seed, a per-article SEO rank story end to end for API consumers, and a long list of smaller polish.

Sign in with Google or Microsoft

The Register and Login pages now show Continue with Google and Continue with Microsoft buttons above the email form. One click, provider consent, you're in — no email confirmation step because the provider already verified you.

• Frictionless first-time signup. When the provider returns an email claim (almost always — Google and most Microsoft tenants), the legacy "Associate your account" form is skipped entirely. You go from consent screen to a usable channel in one redirect.
• Display name & profile photo pre-populated. Pulled from the provider's claims so your profile isn't blank on day one.
• Connect or disconnect later. Sign in with email and password first? You can connect Google or Microsoft to your existing OmniCon account from Profile → Connected accounts, and disconnect a provider at any time (with a guard so you can't accidentally lock yourself out of your only sign-in method).
• X (Twitter) is wired up in code — we're holding off the rollout until the developer-portal setup is less painful.

Magic-link sign-in — no password

If you'd rather not pick yet another password, there's now a passwordless path: enter your email, click the link in your inbox, and you're signed in.

• One form for sign-up and sign-in. If the email already has an account we send a sign-in link. If it doesn't, we send the same shape of link and your account is created when you click it — no separate flow to remember.
• 15-minute single-use links. Long enough to survive slow email delivery and tab switching; short enough that a stolen inbox doesn't become a long-tail attack surface.
• Per-IP rate limit. Stops anyone using OmniCon as a spam relay; generous enough that a user who lost the first email can request again.
• Surfaced as "Sign in with an email link instead" on the Login page and "Sign up with an email link instead" on Register.

Land on a usable channel, not the org picker

Whichever sign-in path you take, brand-new users now arrive directly inside a freshly-provisioned starter channel.

• Personal workspace + first channel created automatically. Named after you ("{nickname}'s Workspace", "{nickname}'s Contents") and pre-populated with the default author. Private by default so a brand-new channel isn't accidentally indexable on day one.
• Idempotent. Users who arrive via an invitation magic-link still land in the inviting organisation — no redundant personal workspace gets spun up on top.
• Same provisioning across every signup path. Email + password, Google, Microsoft, and magic-link sign-up all run the same code.

"What are you building?" welcome card

The first time you load a brand-new channel's dashboard, a welcome card asks one question with five answers. Click and we seed real sample articles in the right voice for that shape:

• Help center — "Welcome to your help center" + "Writing help articles people actually read"
• Blog — "Hello world — your first blog post"
• News / release notes — a release-note skeleton you can copy
• Developer docs — "Getting started" + "How these docs are organised"
• Empty channel — just dismiss; start from scratch

The seeded articles read like real prose you could honestly start from — not lorem ipsum. Edit, rewrite, delete — they're regular articles. The card stays gone after you've picked something, and never appears on channels older than 24 hours or that already have any article.

SEO for API consumers

If you pull OmniCon content over the API and render it on your own domain (customer.com/help/…), the SEO suite finally treats that as the canonical source.

• External Base URL on each channel. Set it under channel settings or via the MCP update_channel tool. The SEO suite reports article URLs under {ExternalBaseUrl}/{permaName} for that channel.
• Canonical link tag on the OmniCon-served page. When an article's canonical points elsewhere, the OmniCon page emits a <link rel="canonical"> pointing at your real page — Google indexes the customer's site, not the OmniCon duplicate.
• Per-article rank rows from Google Search Console. The nightly pull now adds the page dimension and stores rank data per (article, keyword, day) instead of channel-wide aggregates. "This specific article ranks 8.3 for that specific keyword" instead of "your channel averages 8.3."
• "Top ranking articles" card on the SEO Health overview — top 10 by impressions, joined to article title + keyword phrase. Real numbers, sorted to where your attention should go.
• SEO Health URL hint. A small line at the top of the page shows the URL pattern your articles will report under (omnicon.cloud, your custom domain, or your ExternalBaseUrl), so you can validate the config at a glance.

Pick the right Google Search Console property

The 2.0.198 GSC connector silently auto-bound the first matching property after OAuth — which sometimes meant a portal-level sc-domain:omnicon.cloud winning over the customer's actual content site, and rank tracking pulling the wrong numbers. Fixed.

• Picker page after OAuth. Lists every Search Console property the connected Google account can read, grouped into URL-prefix properties and Domain properties so the difference is obvious.
• No silent auto-bind. Single-property accounts still bind directly with the URL shown in the success toast; multi-property accounts always see the picker. The pre-selection only fires on a confident exact-host match against the channel's custom domain.
• Change site link on the Integrations index so re-binding doesn't need disconnecting + re-OAuthing.

Also in this release

• URL-based file ingest. New MCP upload_from_url tool and POST /api/storage/ingest-url REST endpoint. Pass a public URL, OmniCon fetches and stores it — one round-trip instead of "give me a token, now I PUT the bytes myself." Includes a strict SSRF guard that re-checks every redirect hop, blocks loopback / RFC1918 / cloud-metadata addresses, and caps the response at 50 MB. The existing pre-signed flow stays for browser uploads and large videos.
• Connected accounts on your profile. Profile page now shows linked external logins with one-click Disconnect, plus Connect buttons for providers you haven't linked yet. Disconnect is disabled if it would leave you with no way back in.
• Custom domains support both apex and www. Verify a custom domain and the www. subdomain is automatically registered in Front Door and 301-redirects to the bare domain, so links work either way without two separate setups.
• Public article-search JSON endpoint. A paginated listing API for channel-search results — suitable for headless front-ends that want to render their own results page.
• Page-scoped channel assets in custom layouts. Custom-layout CSS/JS can now be scoped per page so a sales-page asset doesn't bleed into the blog — less collision, smaller payloads.
• Editor polish. TinyMCE no longer shows the visible focus-ring pseudo-element when you click into an editable region; the "browse files" button in the page editor now includes the media picker so you actually have something to browse; the media picker no longer opens behind the TinyMCE image dialog.

If you'd like a hand wiring up social sign-in for your team, setting a channel's External Base URL, or connecting Google Search Console so the new per-article rank picks you up overnight, drop us a note.