Embedding a hub on a site

Gallery, then Embed. With several sites, pick the site first.

The code

One snippet. Paste it into the page at the site's path (for example /news/). The gallery sizes itself to its content. Copy copies it; Open test page and Open live are beside it.

Article addresses

The one choice that changes the code:

• Clean: yoursite.com/news/article-name/. Best for search, and a link shared in WhatsApp, LinkedIn or Slack previews as the article. Needs one rewrite rule on your web server, which sends every address under /news/ to the gallery page, or the proxy line further down.
• Hash: yoursite.com/news/#/article-name/. Works on any site with no server changes. A shared link previews as the gallery, not the article, because nothing after # reaches a server.

Clean is the default. If the site cannot serve clean addresses yet, the gallery notices on the first visit and uses Hash addresses on its own, so nothing breaks; add the rule and it switches back by itself. An old Hash link opened on a site that serves clean addresses moves to the clean address.

The setting also decides how links in that site's widgets are built.

The site check

mxAURA looks at your page and tells you what is true, instead of giving generic instructions:

• whether the embed code is on the page yet,
• whether the code on the page uses the same address style as this setting (the page's own code wins if it sets data-mode),
• for Clean addresses, whether the server already sends article addresses to the gallery page. If it does not, the rewrite rule for your host appears; pick the host from the list.

Links

The gallery page on your site, the JSON feed and the sitemap, each with Copy.

What the gallery does on your page

• Links to your own site leave the gallery. A link in an article or an author card that points at your site opens in the page itself, not inside the gallery. A link written as a path (/services/) goes to that path on your site. Links to other sites open in a new tab. A link whose target was set in the editor keeps it.
• The tab title follows the reader. Opening an article puts its title on the browser tab; going back to the gallery puts your page's own title back. Analytics that read the page title get the article's.
• A hidden title leaves no gap. With the hub title turned off (Gallery > Design), the header column it sat in closes up, and a header with nothing else in it is not drawn.

Getting the article text onto your page

Search engines and AI answer engines read what your server sends at an article's address. The gallery is drawn inside a frame, so on its own that page carries the title, description and schema but not the article's words. Each article also has a plain version at …/e/KEY/slug/content.json: the title, byline, lead answer, body and approved FAQs as HTML, with the schema to match. Your site's developer puts that HTML into the page (inside the gallery's mount element). The gallery keeps it on screen until it has loaded and then takes over; if the gallery never loads, the article is still readable. An address that is not a live article answers 404, so your site can too. The developer guide has the details and an example.

There is a simpler way on hosts that can pass an address through to another server (Netlify, Vercel, nginx). Gallery > Embed shows a line under Article pages search engines can read. Use it in place of the rewrite rule and mxAURA returns your own page with the article already in it. Nothing else to build.

Iframe

For a page that cannot run scripts. Fixed height, and article addresses do not change as readers click through.

All topics