RTEO Connect pulls live, never-stale schema.org Course structured data from your RTEO workspace and injects it server-side into your course page . It also provides the [rteo_connect embed=table object=…] shortcode to drop the live course instance table (dates, locations, prices, availability, enrol buttons) anywhere on your site. It never authors or stores content in WordPress — it only renders content served by RTEO.
Embed a course page’s live instance table by pasting the shortcode from your RTEO course page editor, e.g. [rteo_connect embed=table object=sch_xxxxx]. Optional attributes: display (tabs|combined), rows (3|6|10|all), sort (date|spots|cost|location), dir (asc|desc), theme (auto|light|dark). The table renders in an isolated Shadow DOM in your site’s brand colours and stays in sync with your live schedule.
The Course JSON-LD is injected server-side (in wp_head), not via client-side JavaScript, so search engines and AI consumers index it reliably. The plugin transient-caches the fetched JSON-LD so it adds no per-render network cost, and it fetches from RTEO’s public, anonymous schema endpoint, storing no secrets.
External services
This plugin relies on the RTEO application — a third-party SaaS platform operated by RTEO — to generate and serve the schema.org Course structured data and the live course instance table for your courses. The plugin only reads and renders content that RTEO produces; it never authors or stores content in WordPress.
By default it connects to the live RTEO service at https://staging.rteo.com.au. This is configurable via the rteo_endpoint_base option, which RTEO sets for you during a remote install (for example, to point at a self-hosted RTEO instance).
What data is sent, and when:
-
Schema fetch (server-side, on page render). When a page has an RTEO schema token configured, the plugin makes a server-to-server request to the RTEO schema endpoint (https://staging.rteo.com.au/api/schema/) to fetch that page’s Course JSON-LD. The only data sent is the page’s opaque schema token (e.g.
sch_xxxx) — no personal data, post content, or site credentials. Responses are cached locally so the request is not repeated on every render. -
Embed widget (in the visitor’s browser, only when used). When you add the [rteo_connect embed=table] shortcode to a page, the visitor’s browser loads the RTEO embed widget script from https://staging.rteo.com.au/dist/rteo-instances.js, which then requests the public, anonymous instance-table data for the page’s token from https://staging.rteo.com.au/api/embed/page/. As with any externally hosted script, the visitor’s browser contacts staging.rteo.com.au (sending its IP address and standard request headers) when the table is displayed.
This service is provided by RTEO. Its terms and privacy policy:
- Terms & Conditions: https://rteo.com.au/terms-conditions
- Privacy Policy: https://rteo.com.au/privacy-policy