Auditizer – AI Website Audit & Optimization vs Bitron Right of Withdrawal

Auditizer gives you professional-grade SEO and accessibility auditing powered by artificial intelligence. Scan your entire WordPress site, identify critical issues, and apply AI-generated fixes automatically — all with full backup and one-click rollback protection. Perfect for content creators, agencies, and businesses that want to improve search rankings and web accessibility without hiring expensive consultants. 🚀 Core Features AI-Powered Fixes – Generate intelligent fix suggestions using OpenAI GPT-4 or Anthropic Claude Bulk Site Scanning – Scan all posts and pages at once with live progress tracking Automatic Backups – Every fix creates a full backup with one-click rollback Advanced Filtering – Filter by status, severity, category, and auto-fixable issues Training Mode – Teach the AI your brand voice and writing style Cost Tracking – Monitor AI usage and costs over the last 30 days Export Reports – Download issues as CSV for client reporting 📊 What Gets Scanned SEO Issues: * Missing or duplicate meta titles and descriptions * H1 tag problems (missing, duplicate, or mismatched) * Thin content detection * Image alt text optimization * Broken internal links * Keyword density and placement * Open Graph and Twitter Card tags * Canonical URL issues * Schema markup detection SGE (AI Search Optimization): * Content structure for AI search engines * Direct answer formatting * Topic authority signals * FAQ and Q&A detection * Entity coverage and relevance * Content freshness indicators Accessibility (WCAG 2.1): * Missing or empty alt attributes * Color contrast compliance (AA standard) * Form label associations * ARIA landmarks and roles * Keyboard navigation support * Heading hierarchy validation * Document language attributes 🎯 How It Works Run a Scan – Use bulk scan from the dashboard or scan individual posts Review Issues – See all detected problems with severity ratings and descriptions Get AI Fixes – Click “Get AI Fix” to generate intelligent solutions Apply Automatically – One-click to apply fixes with automatic backup Rollback if Needed – Restore original content instantly from any backup 🔒 Privacy & Security Only post content is sent to AI providers for fix generation No personal data, usernames, or emails are transmitted API keys stored securely in WordPress database All database operations use prepared statements Nonce verification on all actions Capability checks enforce proper permissions 🔧 Page Builder Compatibility Works seamlessly with: * Gutenberg (Block Editor) * Classic Editor * Elementor * Divi Builder * Beaver Builder * Bricks Builder * WPBakery * Any builder using standard post content storage 💡 Use Cases Bloggers – Improve SEO scores and reader accessibility Agencies – Audit client sites and generate fix reports E-commerce – Optimize product pages for better rankings Publishers – Maintain content quality across large sites Developers – Add professional auditing to client deliverables External Services This plugin connects to third-party AI services to generate content improvements. Connections only occur when you configure an API key and explicitly trigger a scan or fix. OpenAI API Purpose: Generate SEO and accessibility fix suggestions Data Sent: Post content, meta fields, issue context Service: https://platform.openai.com/ Terms: https://openai.com/policies/terms-of-use Privacy: https://openai.com/policies/privacy-policy Anthropic Claude API Purpose: Generate SEO and accessibility fix suggestions Data Sent: Post content, meta fields, issue context Service: https://www.anthropic.com/ Terms: https://www.anthropic.com/legal/consumer-terms Privacy: https://www.anthropic.com/legal/privacy No personal user data (usernames, emails, passwords) is ever transmitted to these services. Support For support, feature requests, or bug reports: WordPress.org Forum: https://wordpress.org/support/plugin/auditizer/ Documentation: https://teamjuh.com/auditizer-docs/ Website: https://teamjuh.com Credits Developed by TeamJUH – WordPress development and AI integration specialists.

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