Translate WordPress with GTranslate
Translate WordPress with GTranslate plugin uses Google Translate AI translation service to translate wordpress site with Google power and make it multilingual. With 103 available languages your site will be available to more than 99% of internet users. Our paid versions are fully SEO compatible which will increase your international traffic and sales. This translate plugin is a budget multilingual WordPress solution which combines automatic and human translations to save money and is easy to implement. GTranslate is a leading website translation services provider since 2008, it moves away the language barriers. Compared to other translation plugins for WordPress, we use cloud based approach which does not slow down your website. In addition to that, we can offer complete SEO features based on sub-domains with our paid options, which can make your website appear in search engines in different languages which will increase your international traffic and sales. In our paid versions we DO NOT limit the number of words or the number of translated pageviews. You DO NOT pay additionally for automatic translations. Please use GTranslate Support for your questions and support requests! We are multilingual! Please check our FAQ to get quick answers. Features Free Google automatic machine translation Hides Google top frame after translation Translate website on the fly Translate posts and pages Translate categories and tags Menus and widgets translation Themes and plugins translation Right to left language support Google language translator widget Auto-switch language based on browser defined language Available styles Float, Dropdown, Flags, Flags with dropdown, Nice dropdown with flags, Flags with language names, Flags with language codes, Language names, Language codes, Globe, Popup Floating language selector WooCommerce shop translation Multilingual language names in native alphabet Alternative flags for Quebec, Canada, USA, Brazil, Mexico, Argentina, Colombia Lazy loading for language flags and js libraries to boost performance Lightweight vanilla javascript without dependencies Forum Support Paid Features Multilingual SEO – Enable search engine indexing Neural machine translations with human level translation quality Increase traffic and AdSense revenue Search engine friendly (SEF) URLs Yoast SEO compatible – translate meta keywords, meta description, schema.org data structures, translate sitemaps WooCommerce compatible – translate products, schema.org data structures You can have sub-directory (example.com/es/) or sub-domain (es.example.com) URL structure URL Translation aka slug translation is possible (example.com/about-us → example.es/sobre-nosotros) Add hreflang tags for translated alternatives You can manually correct translations In context translation interface (make corrections without losing the context) Meta data translation (meta keywords, meta description) Translating schema.org microdata for better search engine appearance Seamless updates (cloud service updated on our side – SaaS, you do not need to worry about backups on your side) JSON format translation Translate WooCommerce emails AMP translation (Accelerated Mobile Pages translation) Image localization – Media translation Translation Proxy (aka Translation Delivery Network) Centralized Translation Cache – We revise and improve translations over time Language Hosting (example.fr) User Dashboard with Analytics Live Chat Support See also If you are looking for unlimited, high-quality automatic translations, check out TranslateX – an automatic translation API offering unlimited translation for your website or application. We also offer integration plugins: TranslateX for Loco Translate – integrate TranslateX API directly into Loco Translate for seamless, unlimited automatic translations. TranslateX for TranslatePress – bring unlimited automatic translation to TranslatePress using TranslateX API. These solutions make it easy to supercharge your WordPress multilingual setup with TranslateX’s secure and affordable API. GTranslate WordPress Demo Watch GTranslate Tour Edit Translations Demo (paid)
Top keywords
- translation23×4.01%
- language13×2.27%
- translate13×2.27%
- translations8×1.40%
- automatic7×1.22%
- flags7×1.22%
- multilingual6×1.05%
- translatex6×1.05%
- wordpress6×1.05%
- example5×0.87%
- google5×0.87%
- gtranslate5×0.87%
Robina
Robina is a free, open-source booking and appointment plugin for WordPress, built for service businesses that want a capable booking system without subscription fees. It is service- and resource-centric: the bookable unit is a service with its own availability, while staff, locations and resources are optional layers you add only if you need them. Highlights Front-end booking widget (Vue 3). A clean multi-step wizard — Service, Date & time, Details, Confirm — added to any page with the [robina_booking_form] shortcode, or as a popup button with [robina_booking_button]. Capacity-aware availability. Slots are computed from your business hours, slot step and buffers. Assign staff to a service and each one adds a parallel slot; a staff member booked anywhere counts as busy. With no staff, a service has a single capacity per location. Group classes. Give a service a capacity above 1 (say 20 or 40 — there is no upper limit) and several customers can book the same session until it fills up — ideal for classes, workshops and large group sessions. Front-end class schedule. Show a public timetable of upcoming classes with the [robina_schedule] shortcode — visitors switch between an Agenda list and a Month calendar grid, each session lists the seats left and links straight into booking. Give a service a weekly schedule (e.g. Monday 18:00) in its editor to put it on the timetable. Staff (optional). Tag the people who provide a service, pin them to one or more locations, and give them their own weekly hours. When a customer picks a location, only the staff who work there are offered. Locations (optional). Offices or branches with their own optional weekly hours; each service declares where it is available. Native WordPress admin. A branded Catalog (services, categories, resources), a Month/Week/Day Calendar with in-place booking creation, plus Bookings, Customers, Staff and Locations screens — all in plain WordPress UI. Email notifications to the owner and the customer on every new booking, plus optional reminders a set number of hours before the appointment. Customer self-cancellation. The confirmation email carries a personal cancel link, so a customer can free their seat themselves — instantly bookable again by someone else. Set a cancellation window (e.g. up to 12 hours before) or switch it off. Days off and booking notice. Mark single dates a service does not run (holidays, a break) and close booking a set number of minutes before the start time. Optional online payments — Pay on site, WooCommerce, Stripe or PayPal (see “External services” below). Leave them all off for free bookings. Self-contained and private. No external CDNs and no trackers; the phone-input flags and every front-end asset ship inside the plugin. Uninstalling removes Robina’s tables and options. Service-centric by design Robina deliberately keeps availability on the service, not on a mandatory “employee”. Staff, locations and resources are optional capacity and scope layers, so Robina also suits non-staff models such as equipment rental or table booking. External services By default Robina works entirely on your own site and contacts no third party. It only talks to an external service when you, the admin, enable and configure a payment gateway, and only when a customer actually chooses to pay with it. No data is sent anywhere otherwise — Robina has no “home” server and sends no telemetry or analytics. Stripe — used only when you enable “Stripe” and enter your API keys. When a customer pays by card, Robina creates a Stripe Checkout Session and redirects the customer to Stripe’s hosted payment page, and it receives Stripe webhooks to confirm payment. Data sent to Stripe: the booking amount, currency, a short description and the customer’s email. Card details are entered on Stripe’s site, never on yours. Terms: https://stripe.com/legal — Privacy: https://stripe.com/privacy PayPal — used only when you enable “PayPal” and enter your client ID and secret. When a customer pays with PayPal, Robina creates a PayPal order, redirects the customer to PayPal to approve it, then captures it on return. Data sent to PayPal: the booking amount, currency and a reference id. Terms: https://www.paypal.com/legalhub/home — Privacy: https://www.paypal.com/legalhub/privacy-full WooCommerce (optional, local) — if you enable WooCommerce checkout and WooCommerce is installed, Robina creates a pending WooCommerce order and hands payment off to WooCommerce. Robina makes no external call itself; any outbound requests are made by WooCommerce and its own gateways under their policies. Map link — a location’s address is turned into a plain “view on map” link to Google Maps (https://www.google.com/maps/search/…). It is only a link: nothing is transmitted and no map is loaded unless a visitor clicks it. Source code Robina is fully open source (GPLv2+). The front-end widget is compiled with Vite from the Vue source that ships inside the plugin under /resources. The build files (package.json, package-lock.json, vite.config.js) are bundled too, so the compiled assets in /assets/dist can be regenerated from source with: npm install && npm run build Bundled third-party libraries (installed via npm, both MIT-licensed): Vue 3 (^3.4) — https://github.com/vuejs/core intl-tel-input (^29.0) — https://github.com/jackocnr/intl-tel-input