Add it once
One line of JavaScript
Add Verbison once to your website’s global template. The embed then works across your domain. Choose which pages receive audio in Verbison, without rebuilding your CMS.
- Add it once
- CMS-independent
- For every configured page
Add it once to your template, then test a complete page
- Register your website. Copy its code from the website configuration in your account. It contains your public site ID; replace PUBLIC_SITE_ID in the example above with that value.
- Use the shared page layout. Insert the script once before the closing </body> tag, or in your CMS’s global code area. If the site uses several templates, check that each relevant template serves it. You do not then need a separate embed for every article.
- Check the published page. In your browser’s network tools, confirm that verbison.js loads. A content security policy, script blocker or incorrect site ID can prevent the connection. A script tag in the source alone does not prove that the integration works.
- Configure a specific URL. Open that page with #verbison-admin and sign in to the Studio, or select it in your account. Sitemap discovery helps you find pages; it does not generate audio.
- Publish a reviewed edition. Check the spoken text and recording, publish the chosen language and save the player placement. Then open the same URL in an ordinary visitor window.
ProWebSolutions uses this embed on its own website. The PHP article is an existing published example. This is our own integration, not an independent customer endorsement.
The script loads, but no player appears?
Check the exact URL: is audio enabled for this page, is a completed recording published in at least one language, and have the display and placement settings been saved? For an inline entry point, its selected target element must still exist in the current layout. Test the Studio preview and the public visitor view separately.
A CMS-independent starting point
The generic JavaScript approach is not tied to one CMS. It can complement sites whose templates allow external scripts and expose the content needed for player placement. That is a practical integration model, not a promise that every theme, plugin or closed platform works without checking.
Protected pages, restrictive content security policies and unusual navigation behaviour deserve a specific review. Existing website developers can assess those conditions within the normal deployment process. Verbison does not require a speculative new CMS project merely to add a listening option to a suitable page.
Find pages before configuring audio
Sitemap and URL discovery help create an inventory of website pages. Editors can search for a title or URL and choose the content they want to prepare. Discovered pages and audio-configured pages are separate concepts.
Finding a URL does not start translation or synthesis. It also does not make every website page count as a configured audio page. The workflow explains what happens after selection: prepare the text, choose languages and voices, generate, review and publish.
Player placement in the real page
Use the Studio to select a suitable content block and preview the position. An inline read-aloud button can appear near the introduction or another relevant section. A compact inline player can suit layouts with enough room for immediate audio controls.
Save the placement when it fits the page. Inspect the result against headings, images, captions and calls to action. A preview helps evaluate the choice, while the saved setting determines the visitor experience. Desktop placement should also be checked in the mobile layout.
Inline or floating
A floating player keeps playback controls available while readers move through a longer article. An inline option makes the audio entry point part of the page itself. Neither is universally better: choose according to the content and how visitors navigate it.
Check fixed headers, consent banners and other floating controls. Audio should not obstruct the website's existing tasks. For regular editorial production, the publisher overview explains how the player fits into the wider article experience.
Editing on the website
Once Verbison is embedded, there is no need to switch between your CMS and a separate audio platform. The On-Page Studio opens beside your actual website. Edit spoken text, language editions and player settings in the context of the page.
Placement selection happens against real website elements. You can assess the result where readers will use it, instead of guessing from an unrelated preview screen. Authentication and site verification remain necessary for the private workflow.
Keep the content connection intact
The public player displays the current spoken sentence and highlights its corresponding passage in the original article. For a foreign-language edition, the highlight remains tied to the source content. This makes article structure relevant to the integration: clear paragraphs give listeners useful orientation.
Review unusual layouts, hidden duplicate text and dynamically replaced content on representative pages. A reliable setup uses the actual published article, including its mobile presentation, rather than assuming that one successful homepage check covers every template.
Test a complete publishing cycle
Prepare one representative page, publish a reviewed edition and test playback, language choice and placement. Audio is generated beforehand; ordinary playback consumes no new audio characters. See plans for website and configured-page allowances before expanding the rollout.