Bitron Right of Withdrawal vs VidSEO – Video transcript embedding for WordPress & LLM

From 19 June 2026, EU member states require every consumer-facing online shop to provide an online withdrawal function — not just static information, but a continuously available electronic interface where the consumer can declare intent to withdraw, and from which the shop sends an automatic confirmation on a durable medium. In Hungary the same rule applies through the amendment of Government Decree 45/2014. Bitron Right of Withdrawal delivers exactly that, accessibly. What the plugin does A continuously available, accessible withdrawal form — embeddable via the [bitrow_form] shortcode or the Withdrawal Form Gutenberg block, so it drops into any classic-editor page, a block-built layout, or a page builder that handles either. Tight WooCommerce integration: the form is surfaced to logged-in customers as a Withdrawal item in their My Account menu, but only while they have at least one order still inside the window — so a customer with nothing eligible doesn’t see a dead link. A withdrawal link is automatically attached to WooCommerce’s customer order emails (processing, completed, invoice) while the window is open — a discreet text link (not a prominent button) to avoid accidental clicks. Its position in the email (top, after the order details, or bottom — bottom by default) and both the surrounding message text and the link label are configurable under Settings → Email. HTML and plain-text variants, with a filter to extend the list of carrier emails. Guest and logged-in customer paths. A logged-in customer sees a select of their own in-window orders. For guests, optional email verification: with the free OneCode Login plugin active, the guest proves they own their email with a one-time code, and the form then loads that email’s orders just like for a logged-in customer — closing the gap where anyone who knew an order number and the billing email could file on someone else’s behalf. When email verification is not in force, an unverified guest is never shown any order data: instead of looking up an order, they file a free-text withdrawal declaration (no order is matched server-side, no line items or totals are disclosed), which is recorded flagged as unverified for the shop to match by hand. Order data is therefore only ever shown to logged-in or email-verified customers. Item-level partial withdrawal. After the customer picks an order, they tick exactly which line items (and quantities) they want to withdraw from — the form is not all-or-nothing. Bank-account capture for non-card payments. When the original gateway can’t refund automatically (e.g. cash on delivery, bank transfer), the customer enters a Hungarian IBAN or domestic GIRO account number — validated client- and server-side with MOD-97 / CDV checks — so the shop has everything to wire the refund manually. Customizable form copy and brand colors. An optional intro paragraph above the form and the submit-button colors (background + text) are configurable from Settings → Form, with a live WCAG contrast meter that announces the ratio as you type so a custom brand color cannot quietly drop below AA. An “advanced” panel additionally exposes the form body text, wrapper background, and input/fieldset border colors for themes that need the form to blend in — these three are not contrast-checked and carry an explicit “you own the contrast” warning. The same values can be overridden per-instance through [bitrow_form] shortcode attributes or the block’s Inspector panel. Automatic confirmation email to the customer (durable medium) and notification to the shop admin, with editable subject and body templates for both — empty fields fall back to safe i18n defaults so the plugin is functional out of the box. The admin notification recipient is a configurable email address (defaults to the site administration email); leave it empty to switch admin notifications off. Optional business-customer exclusion: because the right of withdrawal is a consumer right, shops that also sell to VAT-registered businesses can switch the online form off for orders carrying a business marker (e.g. a VAT-number checkout field). Business buyers are shown a contact pointer instead; consumer orders are unaffected. It’s a technical filter, not legal advice. Per-product and per-category withdrawal exemptions for the CRD §16 / 45-2014 §29 carve-outs (perishables, custom-made, sealed digital downloads, etc.). The withdrawal form still shows exempted items inside an eligible order so the customer sees what they bought, but the quantity input is locked at zero with a visible “Not eligible for withdrawal” badge; orders that consist entirely of exempt items are blocked at step 1 with a contact pointer. A separate Settings → Exclusions tab manages the lists with searchable autocompletes. Exclusion type split — excluded by law vs waivable. The exclusion settings separate two legally distinct cases: “excluded by law” items (perishables, custom-made, opened sealed goods) where the right never applies and no customer action is involved, and “waivable” items where the right exists but the customer can expressly give it up. Each case has its own product and category pickers; existing exclusions keep behaving as “by law”. Checkout withdrawal waiver. For waivable goods (typically digital content), the shop can show a consent checkbox at checkout through which the customer expressly waives the right of withdrawal for the affected items. It appears only when the cart actually contains a waivable item, works on both the classic shortcode checkout and the block-based (Store API) checkout, can be optional or mandatory, and records the consent on the order as evidence (timestamp, IP, a fingerprint of the statement text, the covered products and the mode). Off by default; enable and word it under Settings → Exclusions. “Withdrawals” hub in the customer’s My Account area — a single durable, log-in-gated landing page for everything withdrawal-related: a one-click button to start a new declaration (when the form page is configured), plus the full list of past declarations submitted from the account (reference number, date, order link, items, refund preference, status). The menu item appears only when the customer has at least one past record OR an order still inside the withdrawal window; the list itself is privacy-scoped to the customer’s own account email and never reveals records filed under a different email. Minimal record-keeping with unique BITROW-XXXXXX references for evidentiary value, plus a per-record detail page in the admin. Admin can mark a record as closed (and reopen it) once the case is resolved, with timestamp and the closing user recorded — keeps the working list focused on what’s still pending. Withdrawal status on the order screen. When an order has an associated withdrawal, the WooCommerce order-edit screen shows a “Right of withdrawal” panel with the withdrawal’s status and a direct link to its record. Optional withdrawal column on the orders list. A Settings → General switch (off by default) adds a column to the WooCommerce orders list flagging which orders have a withdrawal and its status (a dash when none). HPOS- and legacy-orders compatible. WCAG 2.1 AA accessibility throughout — programmatic labels, focus management, live regions, sufficient contrast. GDPR integration with WordPress’ personal data export and erase tools, plus a suggested paragraph for the Privacy Policy Guide. Compatibility The plugin integrates with WooCommerce orders. It declares HPOS (High-Performance Order Storage) compatibility and uses the WooCommerce CRUD API throughout. WooCommerce is referenced for compatibility only — the trademark is not used in the plugin name or slug. Important — what this plugin does NOT do This is a technical tool, not legal advice, and does not by itself guarantee legal compliance. The plugin does not generate Terms of Service text, privacy-policy text, or other legal content — those must be prepared by your own lawyer. The confirmation email contains only a factual acknowledgement (received, when, with which ID, what content); any “what happens next” wording is the shop operator’s own policy and must come from you. The plugin records each withdrawal and notifies you, but it does not issue refunds automatically. Refunds remain a deliberate admin action through WooCommerce’s standard refund interface. Privacy The plugin stores only what is necessary to acknowledge and document the withdrawal: name, email, order reference, optional note, timestamps and a unique identifier. No IP address is stored in plain text. On plugin removal the stored records are kept by default (so an accidental deactivation cannot destroy evidence); a setting lets you opt in to deletion at uninstall. Pro version The free plugin covers the full legal compliance core on its own. Bitron Right of Withdrawal Pro adds a convenience and automation layer on top, for shops that process withdrawals regularly: One-click WooCommerce refund — issue the refund straight from the withdrawal record, instead of re-entering it by hand in WooCommerce. Status management and history — a richer status workflow (received, in progress, goods returned, refunded, rejected) with a full audit trail of who changed what and when. Automation rules — define rules that act on incoming withdrawals automatically (status transitions, notifications), so routine cases handle themselves. Custom form fields — add your own fields to the withdrawal form and store them on the record. Searchable admin + CSV export — find any declaration fast and export the list for accounting or reporting. Webhooks — push withdrawal events to your CRM, ERP or any external system in real time. REST API — read and manage withdrawal records programmatically from your own integrations. The Pro plugin is standalone: it contains the full compliance core plus the convenience layer, so you install it instead of the free plugin, not alongside it. Pro adds convenience, not extra compliance — the free plugin already makes you compliant. Learn more and see pricing

VidSEO is a WordPress plugin designed to solve a common and often overlooked problem: valuable information explained in videos is largely invisible to machines. Videos are excellent for human visitors, but search engines, screen readers, and modern answer engines still rely primarily on text to understand what a page contains. When important explanations live only in audio or video form, machines are forced to approximate or ignore that content. VidSEO addresses this limitation by exposing video transcripts as native HTML text directly embedded in the page, alongside the video itself. This allows machines to read what is said in the video without guessing. VidSEO does not generate content. VidSEO does not summarize or rewrite transcripts. VidSEO does not infer missing information. Its role is exposure, not interpretation. A precise, machine-first definition of VidSEO and its scope is available here: https://vidseo.dev Why transcripts still matter Despite major advances in search and AI systems, video content remains fundamentally opaque without an explicit text surface. Search engines may detect that a video exists, but they rely on surrounding text to understand its meaning. Language models face the same constraint: without readable text, they must infer what a video contains. By rendering transcripts as clean HTML, VidSEO ensures that: – the meaning expressed in the video is explicitly available, – long explanations delivered in video form are preserved as text, – machines do not need to extrapolate or hallucinate. Industry context This limitation is now widely acknowledged across the industry. In its January 2026 guide on AEO and GEO, Microsoft highlights the importance of exposing readable text surfaces alongside video content so answer engines and AI systems can reliably extract meaning. From Discovery to Influence: A Guide to AEO and GEO VidSEO provides a concrete WordPress implementation aligned with this principle. What VidSEO allows you to do With VidSEO, you can: Embed YouTube or Vimeo videos using a simple shortcode Retrieve existing YouTube subtitles automatically (when available) Associate each video with a full text transcript Display the transcript as clean HTML inside the page Structure transcripts with headings, paragraphs and links (PRO) Hide the transcript visually while keeping it readable in the source code Keep full editorial control over the transcript content Common situations where VidSEO is useful VidSEO is often used when: Important information is explained mainly in video form Videos contain long explanations, tutorials, interviews or talks You want search engines to understand what is said in your videos Accessibility requires a text alternative to audiovisual content You want to reuse existing video subtitles as readable page content Example A tutorial video explains a complex process in several minutes. With VidSEO, the full explanation becomes readable text on the same page. Search engines and answer engines can now understand what is explained, even if the visitor never plays the video. How it works VidSEO adds a dedicated content type to WordPress. For each video, you: – choose the video platform (YouTube or Vimeo), – paste the video URL, – retrieve existing YouTube subtitles automatically (when available) or add a transcript manually, – optionally format the transcript using standard HTML, – insert the generated shortcode anywhere on your site. The transcript is rendered as standard HTML directly in the page, without external files, iframes, or API dependencies. About the publisher VidSEO is developed by Pagup, a digital readability firm based in Quebec, Canada. Video content is increasingly consumed and summarized by AI systems. Without structured video metadata (VideoObject schema, proper titles, descriptions, and thumbnail references), your videos are invisible to the machine reading layer. VidSEO ensures that your video content is described in a structured format that search engines and AI systems can parse, index, and cite. Part of the Pagup ecosystem pagup.com — Digital readability firm. Diagnostic, semantic architecture, AI governance. gautierdorval.com — Doctrine, canonical definitions, interpretive governance research. interpretive-governance.org — Formal versioned standard for interpretive governance. vidseo.dev — Documentation and resources for VidSEO. Technical references VidSEO outputs transcripts as native HTML within the page DOM. No external files. No API dependencies. No inference layer. Canonical definition and scope: https://vidseo.dev Interpretability reference: https://github.com/GautierDorval/vidseo-video-llm-interpretability Who develops VidSEO? VidSEO is developed by Pagup, a digital readability firm based in Quebec, Canada. Pagup specializes in semantic architecture, interpretive SEO, and AI governance. Why does video structured data matter for AI systems? AI systems rely on structured data to understand what a video contains, who produced it, and how it relates to the page it appears on. Without VideoObject schema markup, your video is just an embedded iframe — the system cannot extract its title, description, duration, or thumbnail. This means your video content does not contribute to your site’s overall digital readability and cannot be cited in AI-generated answers. What is digital readability? Digital readability is the capacity of a website to be correctly understood by all four reading layers: humans, search engines, generative AI systems, and autonomous agents. Learn more at pagup.com.