Skip to main content

​
Release 22 — 27 August 2026

This release is corrections. Nothing here is a new capability, and nothing you have configured needs to change.

​
Microsite — delivery and publishing

  • The Cloudflare route that binds the proxy Worker is now generated for you, wildcard included. A route pattern without a trailing * matches one exact URL, so every page beneath the mount — and the mount itself once a visitor arrives with a tracking parameter — was served by your own origin instead. Nothing logged an error, because an unmatched route is not a fault. Copy the pattern from the portal’s Integration tab. See Reverse proxy.
  • Four fixes to the Worker template on that page: the mount path is now stripped by position rather than by first match, each srcset candidate is moved on its own rather than the attribute being prefixed whole, the request body is forwarded so a non-GET is no longer emptied, and the origin’s cache and trace headers are removed from every response rather than only from non-HTML ones. If you copied an earlier version, take the current one.
  • Publishing a page to one channel no longer misreports the other. Publishing to Preview could flip Production to “Serving” while production carried on serving the snapshot it already had, and removed the control that would have corrected it. Freshness is now resolved per channel.
  • Publish controls only appear where publishing changes anything. On prerendered delivery the deploy is the publish, so the Publish button, the Preview and Production columns and the publish menu items are no longer shown there — none of them could change what a visitor receives. See Deployment modes.
  • There is one place to set where your pages are served. Two editors wrote the same value under two names, and one of them disappeared when the delivery route changed. A single Served at readout in Site Settings now shows the domain and path, and states what depends on them: the reverse-proxy rule, the sitemap root, and which pages are measured.
  • The page editor preview shows a listing’s current content immediately. An edited listing could keep rendering its previous copy in the preview for up to five minutes.
  • Accented characters survive sitemap slug generation. Any character outside a-z0-9 became a hyphen, so Santarém lost its accented letter as punctuation instead of folding to santarem.

​
Translations

  • Listing translations are being scheduled again. From 18 to 25 August no listing translation was created for any organisation: one large account consumed each run’s entire time allowance and every account behind it was never reached. Jobs now resume from where the previous run stopped, so no account can hold up another’s translations.
  • No credit warnings for a re-scan you did not ask for, and a run that fails part way is retried rather than recording itself as complete. Credits are still charged per translation, exactly as before.
  • On-demand localisation audits complete again. Audits for organisations with no translation scope set could not finish, so requests sat unserviced.

​
Embeddable widget

  • preferredTravelMode values are uppercase — DRIVING, WALKING, BICYCLING, TRANSIT. The configuration reference previously showed them in lower case, and listed cycling, which is not a value. Any other value fails validation and the setting is ignored. See the Configuration reference.

​
Documentation

  • The NGINX, Apache, IIS and Caddy reverse-proxy examples now name sites.obvlo.com and mount at a path. They still named the prerendered origin and mounted at your domain root, which would route your home page and every existing route to Obvlo. Only the Cloudflare example had been corrected. If you copied one of the four, take the current version.
  • Five pages were unreachable for nine days after a mistaken revert on 18 August — deployment modes, the WordPress plugin, dynamic serving, the Embed API, and translations. All are restored.

​
Release 21 — 18 August 2026

This release adds three new ways to put Obvlo content on your own domain, and changes which one we recommend.

​
Microsite — how content reaches your domain

  • The reverse proxy to sites.obvlo.com is now the recommended way to run a microsite. Pages render on request, so publishing a change makes it live within seconds and new pages appear without a rebuild. The Reverse proxy examples now point at this origin.
  • Dynamic serving. The origin behind that recommendation. Your reverse proxy configuration keeps the same shape — only the origin it fetches from changes, so switching is two lines and reverses the same way. See Dynamic serving.
  • WordPress plugin. The same reverse proxy, packaged and pre-configured for your site. Upload it, activate it, and there is no web server configuration at all. It serves a cached copy if Obvlo is ever unreachable, and gives the path back to WordPress when you deactivate it. See WordPress plugin.
  • Embed API. Place a single guide inside a page you already render, as an HTML fragment. There is a client-side script for supplementary content and a server-side include that puts the guide in the HTML a crawler receives — use the second one if the guide is the reason the page should rank. See Embed API.
  • Prerendered serving is unchanged and still fully supported. Nothing you have configured needs to change, and there is no deadline to move. It is no longer the default recommendation for a new site, because a published change there is not visible until the next rebuild.
  • A microsite can now be mounted on a whole subdomain, such as guides.yourdomain.com, instead of on a path of your main domain. Nothing on the main domain is touched and no existing route moves, which makes it the quickest way to put a pilot in front of real traffic. The trade-off is real: SEO authority accrues to the subdomain rather than to your primary domain, so a path mount remains the recommendation for production. See Mounting on a subdomain.
  • A comparison of all four, with the trade-offs of each and how to switch between them, at Deployment modes.

​
Microsite — performance

  • Pages load faster on the dynamic path — responses are compressed and cached at the edge, and page CSS is inlined rather than fetched as a separate render-blocking file.
  • Hero images appear immediately. The image at the top of a page previously waited for you to move the mouse, press a key or scroll — otherwise eight seconds — before it was requested at all.

​
Documentation

  • The NGINX and Apache reverse-proxy examples now mount at a path, matching the Cloudflare example. The previous examples mounted at your domain root, which would route your home page and every existing route to Obvlo. If you copied one of those, see Reverse proxy for the corrected version.
  • Every reverse-proxy example now names sites.obvlo.com. If your domain is still on prerendered delivery, substitute content.obvlo.com in the two places each example names the origin — the URL it fetches and the Host header it sends. Everything else, including the path after the host, is identical.
  • A new WordPress plugin page covers install, the permalink requirement, what visitors get during an outage, and how updates work.

​
Release 20 — 27 July 2026

This release makes AI Visibility measurement more accurate and adds a significant Portal platform update.

​
AI Visibility — Measurement and attribution

  • Connect Google Analytics and Search Console once per website. A connection is now shared across everything on the same website, so there’s nothing to connect twice and no duplicate data pull. A specific set of pages can still use its own tag or property where it needs one. See Connecting your data sources.
  • Analytics and search data land on the right pages. Every row is attributed to the set of pages that owns it, matched on the longest matching URL path, with anything else rolled into a rest of the site bucket.
  • One definition of “which pages belong to a microsite”. Monitoring, effectiveness, and Measure now agree, so your own existing pages are no longer counted as Obvlo-generated ones.
  • Fixed: Measure could read a stale Search Console connection after connecting; it now reads the current shared connection.

​
Portal

  • Clearer strategy model — content strategy is now presented in three columns (pillars, clusters, and targets), making it easier to see how topics ladder up.
  • New destination wizard — a guided setup flow with AI Visibility onboarding built in.
  • Per-breakpoint theming — the theme editor can now override component styles per screen size.
  • Self-registration and invitation management — pending invitations are now listed alongside active users, and can be resent, copied as a link, or revoked. See Adding team members.
  • Angular 22 upgrade for performance and long-term maintainability.

​
Microsite

  • Component-level theming — page sections now consume theme variables through a faster styling pipeline, so your site’s look is applied more consistently.
  • Theme-accurate previews in the page editor.
  • New building blocks — a blog card and a Markdown block section.
  • Fixed: tel: links now render correctly.

​
Platform reliability

  • Domains interrupted mid-scan now recover instead of getting stuck.
  • Support for compressed (gzip) sitemaps, detection of JavaScript-only pages, and a guard against URLs that don’t really exist.
  • Fixed: scanning a specific path is no longer overridden by the site’s root, so discovery stays where you pointed it.
The API reference is unchanged in this release. See the API changelog for API-specific history.