Translate WordPress with GTranslate vs Override Post Title with First Content Heading

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)

This plugin is developed at Shepherd Interactive for the benefit of the community. No support is available. Please post any questions to the support forum. On a singular post/page, normally in The Loop the_title() returns post_title; if, however, this needs to be overridden so that a custom content heading is displayed (i.e. for SEO purposes), then an h1 or h2 element may be supplied at the beginning of the post_content and the contents of this heading element will be returned by the_title() instead of post_title. From a technical perspective, the site title in the main header should be an h1 element and the page/post title should in an h2 element within an article, per HTML5: Sections may contain headings of any rank, but authors are strongly encouraged to either use only `h1` elements, or to use elements of the appropriate rank for the section’s nesting level. This is seen in the default WordPress theme and the HTML specifications. However, SEO places higher priority on the contents of an h1 element, so if every page of a site has the exact same h1 contents (the site name), then search engines may not be as likely to rank the page based on the unique contents of the h2. It has been suggested therefore that the h1 and the h2 elements be swapped, so that the site title appears in an h2 and so that the unique page title appears in the h1. While the specifications don’t prefer this arrangement, it is not incorrect, also per HTML5: Both of the documents are semantically identical and would produce the same outline in compliant user agents. So if different heading levels are semantically equivalent, and if search engines really place that much importance on h1, then SEO wins. In both cases, content section headings should be coded with h3 and below. Technical note: If the $post object is not passed into the_title filter, then the page’s the_title() must be called before every other the_title() call in_the_loop()