documentation/locale/sources/websites.pot

# SOME DESCRIPTIVE TITLE.
# Copyright (C) Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 14.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2022-03-18 13:48+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"

#: ../../content/applications/websites.rst:5
msgid "Websites"
msgstr ""

#: ../../content/applications/websites/ecommerce.rst:8
msgid "eCommerce"
msgstr ""

#: ../../content/applications/websites/ecommerce.rst:10
msgid "Run a modern open-source online store with Odoo eCommerce. Learn how to sell online, promote products and increase your average cart sizes."
msgstr ""

#: ../../content/applications/websites/ecommerce.rst:14
#: ../../content/applications/websites/website.rst:14
msgid "Odoo offers a :ref:`free custom domain name <domain-name/odoo-register>` to all Odoo Online databases for one year. Visitors can then access your website with an address such as ``www.example.com`` rather than the default ``example.odoo.com``."
msgstr ""

#: ../../content/applications/websites/ecommerce.rst:19
#: ../../content/applications/websites/website.rst:20
msgid "`Odoo Tutorials: Website <https://www.odoo.com/slides/website-25>`_"
msgstr ""

#: ../../content/applications/websites/ecommerce.rst:20
#: ../../content/applications/websites/website.rst:21
msgid "`Odoo Tutorials: eCommerce <https://www.odoo.com/slides/ecommerce-26>`_"
msgstr ""

#: ../../content/applications/websites/ecommerce/getting_started.rst:5
msgid "Get started"
msgstr ""

#: ../../content/applications/websites/ecommerce/getting_started/catalog.rst:3
msgid "How to customize my catalog page"
msgstr ""

#: ../../content/applications/websites/ecommerce/getting_started/catalog.rst:6
msgid "Product Catalog"
msgstr ""

#: ../../content/applications/websites/ecommerce/getting_started/catalog.rst:8
msgid "All your published items show up in your catalog page (or *Shop* page)."
msgstr ""

#: ../../content/applications/websites/ecommerce/getting_started/catalog.rst:13
msgid "Most options are available in the *Customize* menu: display attributes, website categories, etc."
msgstr ""

#: ../../content/applications/websites/ecommerce/getting_started/catalog.rst:20
msgid "Highlight a product"
msgstr ""

#: ../../content/applications/websites/ecommerce/getting_started/catalog.rst:22
msgid "Boost the visibility of your star/promoted products: push them to top, make them bigger, add a ribbon that you can edit (Sale, New, etc.). Open the Shop page, switch to Edit mode and click any item to start customizing the grid."
msgstr ""

#: ../../content/applications/websites/ecommerce/getting_started/catalog.rst:26
msgid "See how to do it: https://www.odoo.com/openerp_website/static/src/video/e-commerce/editing.mp4"
msgstr ""

#: ../../content/applications/websites/ecommerce/getting_started/catalog.rst:29
msgid "Quick add to cart"
msgstr ""

#: ../../content/applications/websites/ecommerce/getting_started/catalog.rst:31
msgid "If your customers buy a lot of items at once, make their process shorter by enabling purchases from the catalog page. To do so, add product description and add to cart button. Turn on the following options in *Customize* menu:  Product Description, Add to Cart, List View (to display product description better)."
msgstr ""

#: ../../content/applications/websites/ecommerce/getting_started/product_page.rst:3
msgid "How to build a product page"
msgstr ""

#: ../../content/applications/websites/ecommerce/getting_started/product_page.rst:5
msgid "On the website click *New Page* in the top-right corner."
msgstr ""

#: ../../content/applications/websites/ecommerce/getting_started/product_page.rst:7
msgid "Then click *New Product* and follow the blinking tips."
msgstr ""

#: ../../content/applications/websites/ecommerce/getting_started/product_page.rst:12
msgid "Here are the main elements of the Product page:"
msgstr ""

#: ../../content/applications/websites/ecommerce/getting_started/product_page.rst:17
msgid "Many elements can be made visible from the *Customize* menu."
msgstr ""

#: ../../content/applications/websites/ecommerce/getting_started/product_page.rst:22
msgid "See how to configure your products from links here below."
msgstr ""

#: ../../content/applications/websites/ecommerce/getting_started/product_page.rst:26
msgid ":doc:`../managing_products/variants`"
msgstr ""

#: ../../content/applications/websites/ecommerce/getting_started/product_page.rst:27
msgid ":doc:`/applications/sales/sales/products_prices/taxes`"
msgstr ""

#: ../../content/applications/websites/ecommerce/getting_started/product_page.rst:28
msgid ":doc:`../maximizing_revenue/cross_selling`"
msgstr ""

#: ../../content/applications/websites/ecommerce/getting_started/product_page.rst:29
msgid ":doc:`../maximizing_revenue/reviews`"
msgstr ""

#: ../../content/applications/websites/ecommerce/getting_started/product_page.rst:30
msgid ":doc:`../maximizing_revenue/pricing`"
msgstr ""

#: ../../content/applications/websites/ecommerce/getting_started/product_page.rst:31
msgid ":doc:`../../website/optimize/seo`"
msgstr ""

#: ../../content/applications/websites/ecommerce/managing_products.rst:5
msgid "Manage my products"
msgstr ""

#: ../../content/applications/websites/ecommerce/managing_products/multi_images.rst:3
msgid "How to display several images per product"
msgstr ""

#: ../../content/applications/websites/ecommerce/managing_products/multi_images.rst:5
msgid "By default your product web page displays the main image of your product only. If you like to show your products under several angles, you can turn the image into a carrousel."
msgstr ""

#: ../../content/applications/websites/ecommerce/managing_products/multi_images.rst:11
msgid "Check *Several images per product* in :menuselection:`Website Admin --> Configuration --> Settings`."
msgstr ""

#: ../../content/applications/websites/ecommerce/managing_products/multi_images.rst:13
msgid "Open a product detail form and upload images from *Images* tab. Hit *Create* in Edit mode to get the upload wizard."
msgstr ""

#: ../../content/applications/websites/ecommerce/managing_products/multi_images.rst:19
msgid "Such extra image are common to all the product variants (if any)."
msgstr ""

#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:3
msgid "Manage product variants"
msgstr ""

#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:5
msgid "Product variants are used to offer variations of the same product to your customers on the product's page."
msgstr ""

#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:8
msgid "Let's say one of your customers selects a T-shirt from your product catalog."
msgstr ""

#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:10
msgid "Then, they choose the size and color they want. The various size and color combinations are known as product variants."
msgstr ""

#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:14
msgid "Create attributes & variants"
msgstr ""

#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:16
msgid "In order to create various attributes and variants for your products, you first need to turn on *Variants* in :menuselection:`Sales --> Configuration --> Settings`."
msgstr ""

#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:19
msgid "Then, select a product from the Products list (:menuselection:`Sales / Website --> Products --> Products`). When the product detail form opens, click on *Edit*, and go to the *Variants* tab."
msgstr ""

#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:22
msgid "Here, you can add as many different attributes as you'd like by clicking on *Add a line*."
msgstr ""

#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:24
msgid "These attributes appear as three different types:"
msgstr ""

#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:26
msgid "Radio buttons"
msgstr ""

#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:27
msgid "Color buttons"
msgstr ""

#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:28
msgid "Drop-down menu"
msgstr ""

#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:30
msgid "Several variants appear as soon as there are two values for one attribute."
msgstr ""

#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:32
msgid "Don't forget to hit *Save* once all variants have been entered."
msgstr ""

#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:39
msgid "Edit variants"
msgstr ""

#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:41
msgid "After you hit *Save*, you are able to see all the variants from the product template detail form via the *Variants* smart button."
msgstr ""

#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:48
msgid "Clicking the *Variants* smart button takes you to the Product Variants page, where you can edit the following data for each specific variant:"
msgstr ""

#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:51
msgid "Picture(s)"
msgstr ""

#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:52
msgid "Internal Reference (SKU #)"
msgstr ""

#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:53
msgid "Barcode"
msgstr ""

#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:54
msgid "Volume"
msgstr ""

#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:55
msgid "Weight"
msgstr ""

#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:56
msgid "Cost"
msgstr ""

#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:59
msgid "Both the Barcode and the Internal Reference are variant-specific. You need to populate them once the variants are generated."
msgstr ""

#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:63
msgid "Set specific prices per variant"
msgstr ""

#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:65
msgid "You can set a specific public price per variant by clicking on *Configure Variants* in the product detail form (top-left corner). That takes you to the *Product Variant Values* page for that product."
msgstr ""

#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:72
msgid "To set a specific public price for a particular variant, simply click on the variant you want to modify, then click on *Edit*."
msgstr ""

#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:75
msgid "The *Value Price Extra* field represents the monetary value that is added to the original product price whenever the corresponding attribute value is selected."
msgstr ""

#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:82
msgid "This is how the *Value Price Extra* looks on your website:"
msgstr ""

#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:89
msgid "Pricelist formulas let you set advanced price computation methods for product variants. See :doc:`../maximizing_revenue/pricing`."
msgstr ""

#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:93
msgid "Disable/archive variants"
msgstr ""

#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:95
msgid "You can disable/archive specific variants so they are no longer available in quotes or on your website (not existing in your stock, deprecated, etc.). Simply select *Archive* in their detail form. You can reactivate them the same way."
msgstr ""

#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:103
msgid "To retrieve such items, hit *Archived* in the *Filters* category while searching the variants list."
msgstr ""

#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:110
msgid ":doc:`../../../sales/sales/products_prices/products/variants`"
msgstr ""

#: ../../content/applications/websites/ecommerce/maximizing_revenue.rst:5
msgid "Maximize my revenue"
msgstr ""

#: ../../content/applications/websites/ecommerce/maximizing_revenue/cross_selling.rst:3
msgid "How to sell accessories and optional products (cross-selling)"
msgstr ""

#: ../../content/applications/websites/ecommerce/maximizing_revenue/cross_selling.rst:5
msgid "You sell computers. Why not stimulating your customers to buy a top-notch screen or an extra-warranty? That's the goal of cross-selling functionalities:"
msgstr ""

#: ../../content/applications/websites/ecommerce/maximizing_revenue/cross_selling.rst:8
msgid "Accessory products on checkout page,"
msgstr ""

#: ../../content/applications/websites/ecommerce/maximizing_revenue/cross_selling.rst:9
msgid "Optional products on a new *Add to Cart* screen (not installed by default)."
msgstr ""

#: ../../content/applications/websites/ecommerce/maximizing_revenue/cross_selling.rst:12
msgid "Accessory products when checking out"
msgstr ""

#: ../../content/applications/websites/ecommerce/maximizing_revenue/cross_selling.rst:14
msgid "Accessories (e.g. for computers: mouse, keyboard) show up when the customer reviews the cart before paying."
msgstr ""

#: ../../content/applications/websites/ecommerce/maximizing_revenue/cross_selling.rst:20
msgid "Select accessories in the *Sales* tab of the product detail page."
msgstr ""

#: ../../content/applications/websites/ecommerce/maximizing_revenue/cross_selling.rst:26
msgid "There is an algorithm to figure out the best accessories to display in case several items are added to cart. If any item is the accessory of several products added to cart, it is most likely that it will be atop the list of suggested accessories."
msgstr ""

#: ../../content/applications/websites/ecommerce/maximizing_revenue/cross_selling.rst:31
msgid "Optional products when adding to cart"
msgstr ""

#: ../../content/applications/websites/ecommerce/maximizing_revenue/cross_selling.rst:33
msgid "Optional products are directly related to the item added to cart (e.g. for computers: warranty, OS software, extra components). Whenever the main product is added to cart, such a new screen pops up as an extra step."
msgstr ""

#: ../../content/applications/websites/ecommerce/maximizing_revenue/cross_selling.rst:40
msgid "To publish optional products:"
msgstr ""

#: ../../content/applications/websites/ecommerce/maximizing_revenue/cross_selling.rst:42
msgid "Install *eCommerce Optional Products* addon in *Apps* menu. Remove the default filter to search on addons as well, otherwise only main apps show up."
msgstr ""

#: ../../content/applications/websites/ecommerce/maximizing_revenue/cross_selling.rst:48
msgid "Select optional items from the *Sales* tab of the product detail form."
msgstr ""

#: ../../content/applications/websites/ecommerce/maximizing_revenue/cross_selling.rst:54
msgid "The quantity of optional items added to cart is the same than the main item."
msgstr ""

#: ../../content/applications/websites/ecommerce/maximizing_revenue/pricing.rst:3
msgid "Adapt prices to website visitors"
msgstr ""

#: ../../content/applications/websites/ecommerce/maximizing_revenue/pricing.rst:5
msgid "This section sheds light on pricing features found in the eCommerce app:"
msgstr ""

#: ../../content/applications/websites/ecommerce/maximizing_revenue/pricing.rst:7
msgid "force a price by geo-localization,"
msgstr ""

#: ../../content/applications/websites/ecommerce/maximizing_revenue/pricing.rst:9
msgid "let the customer choose the currency."
msgstr ""

#: ../../content/applications/websites/ecommerce/maximizing_revenue/pricing.rst:11
msgid "As a pre-requisite, check out how to managing product pricing: :doc:`/applications/sales/sales/products_prices/prices/pricing`)."
msgstr ""

#: ../../content/applications/websites/ecommerce/maximizing_revenue/pricing.rst:15
msgid "Geo-IP automatically applies the right price"
msgstr ""

#: ../../content/applications/websites/ecommerce/maximizing_revenue/pricing.rst:17
msgid "Assign country groups to your pricelists. That way, visitors who aren't logged in yet will get their own currency when landing on your website."
msgstr ""

#: ../../content/applications/websites/ecommerce/maximizing_revenue/pricing.rst:20
msgid "Once logged in, they get the pricelist matching their country."
msgstr ""

#: ../../content/applications/websites/ecommerce/maximizing_revenue/pricing.rst:23
msgid "Currency selector"
msgstr ""

#: ../../content/applications/websites/ecommerce/maximizing_revenue/pricing.rst:25
msgid "In the case that you sell in several currencies, you can let your customers choose their own. Check the *Selectable* box to add the pricelist to the website drop-down menu, which can be found in *Pricelists* under the *Products* menu, located in the Website application."
msgstr ""

#: ../../content/applications/websites/ecommerce/maximizing_revenue/pricing.rst:35
msgid ":doc:`/applications/sales/sales/products_prices/prices/pricing`"
msgstr ""

#: ../../content/applications/websites/ecommerce/maximizing_revenue/pricing.rst:36
msgid ":doc:`/applications/sales/sales/products_prices/prices/currencies`"
msgstr ""

#: ../../content/applications/websites/ecommerce/maximizing_revenue/pricing.rst:37
msgid ":doc:`promo_code`"
msgstr ""

#: ../../content/applications/websites/ecommerce/maximizing_revenue/promo_code.rst:3
msgid "How to create & share promotional codes"
msgstr ""

#: ../../content/applications/websites/ecommerce/maximizing_revenue/promo_code.rst:5
msgid "Want to boost your sales for Xmas? Share promocodes through your marketing campaigns and apply any kind of discounts."
msgstr ""

#: ../../content/applications/websites/ecommerce/maximizing_revenue/promo_code.rst:9
#: ../../content/applications/websites/ecommerce/maximizing_revenue/reviews.rst:13
#: ../../content/applications/websites/website/publish/multi_website.rst:18
msgid "Setup"
msgstr ""

#: ../../content/applications/websites/ecommerce/maximizing_revenue/promo_code.rst:11
msgid "Go to :menuselection:`Sales --> Settings` and choose *Advanced pricing based on formula* for *Sale Price*."
msgstr ""

#: ../../content/applications/websites/ecommerce/maximizing_revenue/promo_code.rst:14
msgid "Go to :menuselection:`Website Admin --> Catalog --> Pricelists` and create a new pricelist with the discount rule (see :doc:`pricing`). Then enter a code."
msgstr ""

#: ../../content/applications/websites/ecommerce/maximizing_revenue/promo_code.rst:21
msgid "Make the promocode field available on your *Shopping Cart* page (option in *Customize* menu). Add a product to cart to reach it."
msgstr ""

#: ../../content/applications/websites/ecommerce/maximizing_revenue/promo_code.rst:27
msgid "Once turned on you see a new section on the right side. On clicking *Apply* prices get automatically updated in the cart."
msgstr ""

#: ../../content/applications/websites/ecommerce/maximizing_revenue/promo_code.rst:33
msgid "The promocode used by the customer is stored in the system so you can analyze the performance of your marketing campaigns."
msgstr ""

#: ../../content/applications/websites/ecommerce/maximizing_revenue/promo_code.rst:39
msgid "Show sales per pricelists..."
msgstr ""

#: ../../content/applications/websites/ecommerce/maximizing_revenue/promo_code.rst:43
msgid ":doc:`pricing`"
msgstr ""

#: ../../content/applications/websites/ecommerce/maximizing_revenue/reviews.rst:3
msgid "How to enable comments & rating"
msgstr ""

#: ../../content/applications/websites/ecommerce/maximizing_revenue/reviews.rst:5
msgid "Publishing and monitoring customer experience will help you gain the trust of new customers and better engage with your community. In 2 clicks, allow your customer to share their feedback!"
msgstr ""

#: ../../content/applications/websites/ecommerce/maximizing_revenue/reviews.rst:15
msgid "Activate comments & rating from the *Customize* menu of the product web page."
msgstr ""

#: ../../content/applications/websites/ecommerce/maximizing_revenue/reviews.rst:21
msgid "Visitors must log in to share their comments. Make sure they are able to do so (see Portal documentation)."
msgstr ""

#: ../../content/applications/websites/ecommerce/maximizing_revenue/reviews.rst:25
msgid "Review the posts in real time"
msgstr ""

#: ../../content/applications/websites/ecommerce/maximizing_revenue/reviews.rst:27
msgid "Whenever a post is published, the product manager and all the product followers get notified in their Inbox (*Discuss* menu)."
msgstr ""

#: ../../content/applications/websites/ecommerce/maximizing_revenue/reviews.rst:34
msgid "By default the user who created the product is automatically set as follower."
msgstr ""

#: ../../content/applications/websites/ecommerce/maximizing_revenue/reviews.rst:36
msgid "Click the product name to open the detail form and review the comment (in the product discussion thread)."
msgstr ""

#: ../../content/applications/websites/ecommerce/maximizing_revenue/reviews.rst:43
msgid "Moderate & unpublish"
msgstr ""

#: ../../content/applications/websites/ecommerce/maximizing_revenue/reviews.rst:45
msgid "You can easily moderate by using the chatter, either in the product detail form or on the web page."
msgstr ""

#: ../../content/applications/websites/ecommerce/maximizing_revenue/reviews.rst:48
msgid "To unpublish the post, open the product web page and click the *Published* button to turn it red (*Unpublished*)."
msgstr ""

#: ../../content/applications/websites/ecommerce/maximizing_revenue/reviews.rst:56
msgid "..tip::"
msgstr ""

#: ../../content/applications/websites/ecommerce/maximizing_revenue/reviews.rst:55
msgid "You can access the web page from the detail form by clicking the *Published* smart button (and vice versa)."
msgstr ""

#: ../../content/applications/websites/ecommerce/maximizing_revenue/upselling.rst:3
msgid "How to sell pricier alternative products (upselling)"
msgstr ""

#: ../../content/applications/websites/ecommerce/maximizing_revenue/upselling.rst:5
msgid "In order to maximize your revenue, suggesting pricier alternative products is strongly advised for basic items. That way, your customer will spend more time browsing your catalog."
msgstr ""

#: ../../content/applications/websites/ecommerce/maximizing_revenue/upselling.rst:12
msgid "To do so:"
msgstr ""

#: ../../content/applications/websites/ecommerce/maximizing_revenue/upselling.rst:14
msgid "Select such *Alternative Products* in the *Sales* tab of the product detail form. 3 alternatives are fine! Don't publish too many otherwise your customers will be confused."
msgstr ""

#: ../../content/applications/websites/ecommerce/maximizing_revenue/upselling.rst:20
msgid "Turn on *Alternative Products* from the *Customize* menu of the product web page."
msgstr ""

#: ../../content/applications/websites/ecommerce/publish.rst:5
msgid "Launch my website"
msgstr ""

#: ../../content/applications/websites/ecommerce/shopper_experience.rst:5
msgid "Get paid"
msgstr ""

#: ../../content/applications/websites/ecommerce/shopper_experience/payment_acquirer.rst:3
msgid "Manage orders paid with Payment Acquirers"
msgstr ""

#: ../../content/applications/websites/ecommerce/shopper_experience/payment_acquirer.rst:5
msgid "The moment a payment is officially authorized by a Payment Acquirer, Odoo *automatically* confirms the order, which triggers the delivery. And, if you invoice based on ordered quantities, you are requested to invoice the order, as well."
msgstr ""

#: ../../content/applications/websites/ecommerce/shopper_experience/payment_acquirer.rst:9
msgid "Let’s take a closer look at how to manage orders paid with Payment Acquirers."
msgstr ""

#: ../../content/applications/websites/ecommerce/shopper_experience/payment_acquirer.rst:12
msgid "Checking the status of a payment"
msgstr ""

#: ../../content/applications/websites/ecommerce/shopper_experience/payment_acquirer.rst:14
msgid "To check the status of a payment, go to :menuselection:`Website --> Orders --> Orders`. Then, simply click on the order you wish to check on."
msgstr ""

#: ../../content/applications/websites/ecommerce/shopper_experience/payment_acquirer.rst:17
msgid "Once you are on the Sales Order page, you will find the payment is confirmed with an automatic note in the *Chatter*."
msgstr ""

#: ../../content/applications/websites/ecommerce/shopper_experience/payment_acquirer.rst:24
msgid "If the user decides to create an invoice, the payment is directly reconciled. This note in the *Chatter* includes a link to the Payment entry, which contains various details about the transaction, along with a link to the related Journal Entry."
msgstr ""

#: ../../content/applications/websites/ecommerce/shopper_experience/payment_acquirer.rst:32
msgid "Specific messages are provided to your customers for every payment status whenever they are redirected to Odoo after the transaction. To edit these messages, go to the *Messages* tab of the payment method."
msgstr ""

#: ../../content/applications/websites/ecommerce/shopper_experience/payment_acquirer.rst:38
msgid "Automatically generate invoices at order"
msgstr ""

#: ../../content/applications/websites/ecommerce/shopper_experience/payment_acquirer.rst:40
msgid "When the order is confirmed, you can also choose to have an invoice automatically issued and paid. This fully-automated feature is designed for businesses that invoice orders right away."
msgstr ""

#: ../../content/applications/websites/ecommerce/shopper_experience/payment_acquirer.rst:47
msgid "To do automatically generate invoices at order:"
msgstr ""

#: ../../content/applications/websites/ecommerce/shopper_experience/payment_acquirer.rst:45
msgid "Go to :menuselection:`Website --> Configuration --> Settings --> Invoicing`."
msgstr ""

#: ../../content/applications/websites/ecommerce/shopper_experience/payment_acquirer.rst:46
msgid "Then, under the **Invoicing Policy** option, select *Invoice what is ordered*."
msgstr ""

#: ../../content/applications/websites/ecommerce/shopper_experience/payment_acquirer.rst:47
msgid "Then activate *Automatic Invoices* and *Save*."
msgstr ""

#: ../../content/applications/websites/ecommerce/shopper_experience/payment_acquirer.rst:54
msgid "Capture payment after the delivery"
msgstr ""

#: ../../content/applications/websites/ecommerce/shopper_experience/payment_acquirer.rst:56
msgid "If the acquirer handling the payment is configured to capture amounts manually, the order is confirmed, but the amount is kept on hold. Once the delivery is processed, you can capture the payment from the related Sales Order."
msgstr ""

#: ../../content/applications/websites/ecommerce/shopper_experience/payment_acquirer.rst:61
msgid ":doc:`../../../finance/payment_acquirers`"
msgstr ""

#: ../../content/applications/websites/ecommerce/shopper_experience/payment_acquirer.rst:62
msgid ":ref:`Payment Acquirers: Place a hold on a card <payment_acquirers/capture_amount>`"
msgstr ""

#: ../../content/applications/websites/ecommerce/shopper_experience/portal.rst:3
msgid "How customers can access their customer account"
msgstr ""

#: ../../content/applications/websites/ecommerce/shopper_experience/portal.rst:5
msgid "It has never been so easy for your customers to access their customer account. Forget endless signup forms, Odoo makes it as easy as ABC. They are suggested to sign up (name, email, password) when the order is placed, and not before. Indeed, nothing is more annoying than going through a signup process before buying something."
msgstr ""

#: ../../content/applications/websites/ecommerce/shopper_experience/portal.rst:14
msgid "Sign up"
msgstr ""

#: ../../content/applications/websites/ecommerce/shopper_experience/portal.rst:16
msgid "The invitation to sign up shows up when the customer wants to visualize the order from order confirmation email."
msgstr ""

#: ../../content/applications/websites/ecommerce/shopper_experience/portal.rst:23
msgid "Customer account"
msgstr ""

#: ../../content/applications/websites/ecommerce/shopper_experience/portal.rst:25
msgid "Once logged in the customer will access the account by clicking *My Account* in the login dropdown menu."
msgstr ""

#: ../../content/applications/websites/ecommerce/shopper_experience/portal.rst:31
msgid "THere they find all their history. The main address (billing) can also be modified."
msgstr ""

#: ../../content/applications/websites/ecommerce/shopper_experience/portal.rst:37
msgid "If the customer is set as a contact of a company in your address book, they will see all the documents whose the customer belongs to this company."
msgstr ""

#: ../../content/applications/websites/ecommerce/taxes.rst:5
msgid "Collect taxes"
msgstr ""

#: ../../content/applications/websites/livechat.rst:8
msgid "Live Chat"
msgstr ""

#: ../../content/applications/websites/livechat.rst:11
msgid "`Live Chat: product page <https://www.odoo.com/app/live-chat>`_"
msgstr ""

#: ../../content/applications/websites/livechat/overview.rst:5
#: ../../content/applications/websites/website/publish/translate.rst:6
msgid "Overview"
msgstr ""

#: ../../content/applications/websites/livechat/overview/get_started.rst:3
msgid "Get Started with Live Chat"
msgstr ""

#: ../../content/applications/websites/livechat/overview/get_started.rst:5
msgid "Live Chat has the highest satisfaction rating of any communication tool. It allows fast responses and it is accessible and convenient, as your customers can keep doing what they are doing while interacting with you. Remember: your customers want to talk to you, so let's make it easy."
msgstr ""

#: ../../content/applications/websites/livechat/overview/get_started.rst:10
msgid "Set up"
msgstr ""

#: ../../content/applications/websites/livechat/overview/get_started.rst:12
msgid "Once *Live Chat* is installed on your database, if your website was created with Odoo, the application is automatically added to it. All that is left to do is to go to :menuselection:`Website --> Configuration --> Settings --> Live Chat`."
msgstr ""

#: ../../content/applications/websites/livechat/overview/get_started.rst:21
msgid "Select the channel to be linked to your website or create one on the fly."
msgstr ""

#: ../../content/applications/websites/livechat/overview/get_started.rst:27
msgid "For both scenarios, under:"
msgstr ""

#: ../../content/applications/websites/livechat/overview/get_started.rst:30
msgid "- **Operators**: add agents to respond to the chat requests. Add as many as you like, and keep in mind that operators that do not show any activity in Odoo for more than 30min are considered disconnected."
msgstr ""

#: ../../content/applications/websites/livechat/overview/get_started.rst:33
msgid "- **Options**: set the default text to be shown on the live chat button; an automated welcome message to be seen by visitors when a conversation is initiated, and the text that prompts the user to initiate a chat."
msgstr ""

#: ../../content/applications/websites/livechat/overview/get_started.rst:36
msgid "- **Channel Rules**: choose an action for a given URL, and/or per country. In the example below, the chat window automatically pops-up 3 seconds after users (from any country) land on the contact us page."
msgstr ""

#: ../../content/applications/websites/livechat/overview/get_started.rst:43
msgid "GeoIP, which refers to the process of finding a computer terminal’s geographical location by its IP address, must be installed on your server. Otherwise, under *Channel Rules*, countries are not taken into account."
msgstr ""

#: ../../content/applications/websites/livechat/overview/get_started.rst:48
msgid "External options"
msgstr ""

#: ../../content/applications/websites/livechat/overview/get_started.rst:51
msgid "If your website was not created with Odoo, you can find the code to be added to your own, under the *Widget* tab."
msgstr ""

#: ../../content/applications/websites/livechat/overview/get_started.rst:52
msgid "Odoo also offers an URL you can send to users so they can have access to a single live chat page."
msgstr ""

#: ../../content/applications/websites/livechat/overview/get_started.rst:59
msgid "Managing chat requests"
msgstr ""

#: ../../content/applications/websites/livechat/overview/get_started.rst:61
msgid "Conversations initiated by visitors pop up as a direct message, and are shown in *Discuss*. Therefore, inquiries can be answered wherever you are in Odoo."
msgstr ""

#: ../../content/applications/websites/livechat/overview/get_started.rst:69
msgid "Conversations are dispatched based on the current workload of the online operators."
msgstr ""

#: ../../content/applications/websites/livechat/overview/get_started.rst:72
msgid "Leave or join a channel"
msgstr ""

#: ../../content/applications/websites/livechat/overview/get_started.rst:74
msgid "Go to :menuselection:`Website --> Configuration --> Settings`, access your channel under *Live Chat*, and *Join Channel* or *Leave Channel*."
msgstr ""

#: ../../content/applications/websites/livechat/overview/get_started.rst:82
#: ../../content/applications/websites/livechat/overview/responses.rst:48
msgid ":doc:`ratings`"
msgstr ""

#: ../../content/applications/websites/livechat/overview/get_started.rst:83
#: ../../content/applications/websites/livechat/overview/ratings.rst:45
msgid ":doc:`responses`"
msgstr ""

#: ../../content/applications/websites/livechat/overview/ratings.rst:3
msgid "Ratings"
msgstr ""

#: ../../content/applications/websites/livechat/overview/ratings.rst:5
msgid "Giving users the opportunity to rate their interactions can help you improving the experience you offer. That means staying on top of your customers' needs, besides keeping track of your operators’ performances."
msgstr ""

#: ../../content/applications/websites/livechat/overview/ratings.rst:10
msgid "Customer Rating"
msgstr ""

#: ../../content/applications/websites/livechat/overview/ratings.rst:12
msgid "Once the user chooses to close the chat window, he can rate his interaction."
msgstr ""

#: ../../content/applications/websites/livechat/overview/ratings.rst:14
msgid "If the user is *Not satisfied* or *Highly dissatisfied*, a field allowing for an explanation is shown."
msgstr ""

#: ../../content/applications/websites/livechat/overview/ratings.rst:15
msgid "A copy of the conversation can also be sent by email."
msgstr ""

#: ../../content/applications/websites/livechat/overview/ratings.rst:22
msgid "The rating is shown on the chat window itself for the operator."
msgstr ""

#: ../../content/applications/websites/livechat/overview/ratings.rst:28
msgid "And under :menuselection:`Report --> Customer Ratings`."
msgstr ""

#: ../../content/applications/websites/livechat/overview/ratings.rst:35
msgid "Make the rating public"
msgstr ""

#: ../../content/applications/websites/livechat/overview/ratings.rst:37
msgid "Go to :menuselection:`Website --> Configuration --> Settings`, access your channel form, click on *Go to Website* and on *Unpublished*, to publish the rating of that channel on your website."
msgstr ""

#: ../../content/applications/websites/livechat/overview/responses.rst:3
msgid "Commands and Canned Responses"
msgstr ""

#: ../../content/applications/websites/livechat/overview/responses.rst:5
msgid "Using canned responses can help you save time and have a previous, well-thought response, to some of your most common questions and comments."
msgstr ""

#: ../../content/applications/websites/livechat/overview/responses.rst:9
msgid "Use commands"
msgstr ""

#: ../../content/applications/websites/livechat/overview/responses.rst:11
msgid "Commands are shortcuts that do specific actions within the chat window:"
msgstr ""

#: ../../content/applications/websites/livechat/overview/responses.rst:13
msgid "**/help**: shows a help message."
msgstr ""

#: ../../content/applications/websites/livechat/overview/responses.rst:14
msgid "**/helpdesk**: creates a helpdesk ticket."
msgstr ""

#: ../../content/applications/websites/livechat/overview/responses.rst:15
msgid "**/helpdesk_search**: searches for a helpdesk ticket."
msgstr ""

#: ../../content/applications/websites/livechat/overview/responses.rst:16
msgid "**/history**: shows the last 15 visited pages."
msgstr ""

#: ../../content/applications/websites/livechat/overview/responses.rst:17
msgid "**/lead**: creates a new lead."
msgstr ""

#: ../../content/applications/websites/livechat/overview/responses.rst:18
msgid "**/leave**: leaves the channel."
msgstr ""

#: ../../content/applications/websites/livechat/overview/responses.rst:0
msgid "- For *helpdesk tickets*: make sure the application is installed on your database and the option *Live Chat* under :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams` is enabled."
msgstr ""

#: ../../content/applications/websites/livechat/overview/responses.rst:0
msgid "- For *leads*: the *CRM* application must be installed on your database."
msgstr ""

#: ../../content/applications/websites/livechat/overview/responses.rst:26
msgid "To access the ticket or lead created from the chat, click on the shortcut link."
msgstr ""

#: ../../content/applications/websites/livechat/overview/responses.rst:33
msgid "Helpdesk tickets created from the chat automatically add the conversation as a description of the ticket. The same goes for the creation of a lead."
msgstr ""

#: ../../content/applications/websites/livechat/overview/responses.rst:37
msgid "Send canned responses"
msgstr ""

#: ../../content/applications/websites/livechat/overview/responses.rst:40
msgid "Canned responses allow you to have a full piece of text being placed when you type a shortcut word. To create them, go to :menuselection:`Live Chat --> Configuration --> Canned Responses`."
msgstr ""

#: ../../content/applications/websites/livechat/overview/responses.rst:41
msgid "To use them during a conversation, simply type **:** followed by the shortcut word you created."
msgstr ""

#: ../../content/applications/websites/website.rst:8
msgid "Website"
msgstr ""

#: ../../content/applications/websites/website.rst:10
msgid "Discover the best **Open-Source Website Builder** and learn how to build beautiful websites that convert visitors into leads or revenues."
msgstr ""

#: ../../content/applications/websites/website/optimize.rst:5
msgid "Optimize"
msgstr ""

#: ../../content/applications/websites/website/optimize/google_analytics.rst:3
msgid "How to track your website's traffic in Google Analytics"
msgstr ""

#: ../../content/applications/websites/website/optimize/google_analytics.rst:5
msgid "To follow your website's traffic with Google Analytics:"
msgstr ""

#: ../../content/applications/websites/website/optimize/google_analytics.rst:7
msgid "`Create a Google Analytics account <https://www.google.com/analytics/>`__ if you don't have any."
msgstr ""

#: ../../content/applications/websites/website/optimize/google_analytics.rst:10
msgid "Go through the creation form and accept the conditions to get the tracking ID."
msgstr ""

#: ../../content/applications/websites/website/optimize/google_analytics.rst:15
msgid "Copy the tracking ID to insert it in Odoo."
msgstr ""

#: ../../content/applications/websites/website/optimize/google_analytics.rst:20
msgid "Go to the *Configuration* menu of your Odoo's Website app. In the settings, turn on Google Analytics and paste the tracking ID. Then save the page."
msgstr ""

#: ../../content/applications/websites/website/optimize/google_analytics.rst:27
msgid "To make your first steps in Google Analytics, refer to `Google Documentation <https://support.google.com/analytics/answer/1008015?hl=en/>`_."
msgstr ""

#: ../../content/applications/websites/website/optimize/google_analytics.rst:32
msgid ":doc:`google_analytics_dashboard`"
msgstr ""

#: ../../content/applications/websites/website/optimize/google_analytics_dashboard.rst:3
msgid "How to track your website traffic from your Odoo Dashboard"
msgstr ""

#: ../../content/applications/websites/website/optimize/google_analytics_dashboard.rst:5
msgid "You can follow your traffic statistics straight from your Odoo Website Dashboard thanks to Google Analytics."
msgstr ""

#: ../../content/applications/websites/website/optimize/google_analytics_dashboard.rst:8
msgid "A preliminary step is creating a Google Analytics account and entering the tracking ID in your Website's settings (see :doc:`google_analytics`)."
msgstr ""

#: ../../content/applications/websites/website/optimize/google_analytics_dashboard.rst:11
msgid "Go to `Google APIs platform <https://console.developers.google.com>`__ to generate Analytics API credentials. Log in with your Google account."
msgstr ""

#: ../../content/applications/websites/website/optimize/google_analytics_dashboard.rst:14
msgid "Select Analytics API."
msgstr ""

#: ../../content/applications/websites/website/optimize/google_analytics_dashboard.rst:19
msgid "Create a new project and give it a name (e.g. Odoo). This project is needed to store your API credentials."
msgstr ""

#: ../../content/applications/websites/website/optimize/google_analytics_dashboard.rst:25
msgid "Enable the API."
msgstr ""

#: ../../content/applications/websites/website/optimize/google_analytics_dashboard.rst:30
msgid "Create credentials to use in Odoo."
msgstr ""

#: ../../content/applications/websites/website/optimize/google_analytics_dashboard.rst:35
msgid "Select *Web browser (Javascript)* as calling source and *User data* as kind of data."
msgstr ""

#: ../../content/applications/websites/website/optimize/google_analytics_dashboard.rst:41
msgid "Then you can create a Client ID. Enter the name of the application (e.g. Odoo) and the allowed pages on which you will be redirected. The *Authorized JavaScript origin* is your Odoo's instance URL. The *Authorized redirect URI* is your Odoo's instance URL followed by '/google_account/authentication'."
msgstr ""

#: ../../content/applications/websites/website/optimize/google_analytics_dashboard.rst:51
msgid "Go through the Consent Screen step by entering a product name (e.g. Google Analytics in Odoo). Feel free to check the customizations options but this is not mandatory. The Consent Screen will only show up when you enter the Client ID in Odoo for the first time."
msgstr ""

#: ../../content/applications/websites/website/optimize/google_analytics_dashboard.rst:56
msgid "Finally you are provided with your Client ID. Copy and paste it in Odoo."
msgstr ""

#: ../../content/applications/websites/website/optimize/google_analytics_dashboard.rst:61
msgid "Open your Website Dashboard in Odoo and link your Analytics account to past your Client ID."
msgstr ""

#: ../../content/applications/websites/website/optimize/google_analytics_dashboard.rst:67
msgid "As a last step, authorize Odoo to access Google API."
msgstr ""

#: ../../content/applications/websites/website/optimize/link_tracker.rst:3
msgid "Track clicks and visitors using Link Trackers"
msgstr ""

#: ../../content/applications/websites/website/optimize/link_tracker.rst:5
msgid "Link Trackers allow you to track your marketing campaigns (emails, banner ads, blog posts, social media posts, affiliate links, etc.). This way, you are able to identify your best traffic sources and make informed decisions about the distribution of your marketing budget."
msgstr ""

#: ../../content/applications/websites/website/optimize/link_tracker.rst:10
msgid "Configuration"
msgstr ""

#: ../../content/applications/websites/website/optimize/link_tracker.rst:12
msgid "Go to :menuselection:`Website --> Configuration --> Settings` and activate *Link Trackers*."
msgstr ""

#: ../../content/applications/websites/website/optimize/link_tracker.rst:19
msgid "Set up traceable URLs"
msgstr ""

#: ../../content/applications/websites/website/optimize/link_tracker.rst:21
msgid "Go to :menuselection:`Website --> Go to website --> Promote --> Track this page`. Here, you are able to get a specific tracked URL based on the campaign, medium, and source being used."
msgstr ""

#: ../../content/applications/websites/website/optimize/link_tracker.rst:28
msgid "**URL**: url of the page you want to track (e.g. the home page or a product's page)."
msgstr ""

#: ../../content/applications/websites/website/optimize/link_tracker.rst:29
msgid "**Campaign**: context of your link (e.g. a special promotion)."
msgstr ""

#: ../../content/applications/websites/website/optimize/link_tracker.rst:30
msgid "**Medium**: channel used to share (deliver) your link (e.g. an email or a Facebook ad)."
msgstr ""

#: ../../content/applications/websites/website/optimize/link_tracker.rst:31
msgid "**Source**: platform where the traffic originates (e.g. Google or Twitter)."
msgstr ""

#: ../../content/applications/websites/website/optimize/link_tracker.rst:33
msgid "Now, click on *Get tracked link* to generate a URL that you can post or send by the source you have decided on."
msgstr ""

#: ../../content/applications/websites/website/optimize/link_tracker.rst:37
msgid "Follow-up on tracked links"
msgstr ""

#: ../../content/applications/websites/website/optimize/link_tracker.rst:39
msgid "To look at statistics of your links, go to :menuselection:`Website --> Go to website --> Promote --> Track this page`. Besides being able to see the *Most Clicked* and *Recently Used* links, you can also see complete statistics by clicking on *Stats*, including the number of clicks, and the country of origin for those clicks."
msgstr ""

#: ../../content/applications/websites/website/optimize/link_tracker.rst:50
msgid "You can also access the link tracker on *odoo.com/r* via your browser."
msgstr ""

#: ../../content/applications/websites/website/optimize/link_tracker.rst:51
msgid "Activate the developer mode (:menuselection:`Settings --> Activate the developer mode`) and get access to the *Link Tracker* module and its back-end functionalities."
msgstr ""

#: ../../content/applications/websites/website/optimize/link_tracker.rst:53
msgid "Integrated with :doc:`Google Analytics <google_analytics>`, those trackers allow you to see the number of clicks and visitors to keep you on top of your marketing campaigns."
msgstr ""

#: ../../content/applications/websites/website/optimize/link_tracker.rst:55
msgid "The integration with the :doc:`CRM </applications/sales/crm/track_leads/prospect_visits>` application allows you to understand where your leads and opportunities are coming from."
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:3
msgid "How to do Search Engine Optimisation (SEO) in Odoo"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:5
msgid "Search Engine Optimization (SEO) is a set of good practices to optimize your website so that you get a better ranking in search engines like Google. In short, a good SEO allows you to get more visitors."
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:9
msgid "Some examples of SEO rules: your web pages should load fast, your page should have one and only one title ``<h1>``, meta tags (alt-tag, title-tag) should be consistent with the content, your website should have a ``/sitemap.xml`` file, etc."
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:15
msgid "To guarantee Odoo Website and Odoo eCommerce users have a great SEO, Odoo abstracts all the technical complexities of SEO and handles everything for you, in the best possible way. This will be explained here below."
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:20
msgid "But first, let see how you can easily boost your ranking by finetuning the content and the meta tags of your website."
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:24
msgid "Meta Tags"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:27
msgid "Title, Description"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:29
msgid "Every web page should define the ``<title>`` and ``<description>`` meta data. These information elements are used by search engines to promote your website. They are automatically generated based on page title & content, but you can finetune them. Make sure they fit the content of the page, otherwise you will be downgraded by search engines."
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:39
msgid "Keywords"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:40
msgid "In order to write quality content and boost your traffic, Odoo provides a ``<keyword>`` finder. Those keywords are the searches you want to head towards your website. For each keyword, you see how it is used in the content (H1, H2, page title, page description, page content) and what are the related searches in Google. The more keywords are used the better."
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:50
msgid "If your website is in multiple languages, you can use the Promote tool for every language of a single page and set specific title, description and search tags."
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:55
msgid "Content is King"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:57
msgid "When it comes to SEO, content is usually king. Odoo provides several modules to help you build your website content:"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:60
msgid "**Odoo Blogs**: write great contents."
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:62
msgid "**Odoo Slides**: publish all your Powerpoint or PDF presentations. Their content is automatically indexed on the web page. Example: `odoo.com/slides/public-channel-1 <https://www.odoo.com/slides/public-channel-1>`_"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:66
msgid "**Odoo Forum**: let your community create contents for you. Example: `odoo.com/forum/1 <https://odoo.com/forum/1>`_ (accounts for 30% of Odoo.com landing pages)"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:70
msgid "**Odoo Mailing List Archive**: publish mailing list archives on your website. Example: `odoo.com/groups/community-59 <https://www.odoo.com/groups/community-59>`_ (1000 pages created per month)"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:76
msgid "The 404 page is a regular page, that you can edit like any other page in Odoo. That way, you can build a great 404 page to redirect to the top content of your website when visitors get lost in invalid URLs."
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:81
msgid "Use Social Networks"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:83
msgid "Social media is built for mass sharing. If lots of people share your content on social media, then it's likely more people will link to it, and links are a huge factor for SEO ranking."
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:87
msgid "Odoo embeds several tools to share content through social media:"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:90
msgid "Social Network"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:92
msgid "Odoo allows to link all your social network accounts in your website footer. All you have to do is to refer all your accounts in your company settings."
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:99
msgid "Social Share"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:101
msgid "Drop the building block *Share* on any page you want your visitors to share. By clicking the icon, they are prompted to share the page in their social media wall."
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:108
msgid "Most social media use a picture of the picture to decorate the share post. Odoo uses the website logo by default but you can choose any other image of your page in the Promote tool."
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:116
msgid "Facebook Page"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:118
msgid "Drop the building block *Facebook Page* to display a widget of your Facebook business page and encourage visitors to follow it. You can display the timeline, the next events and the messages."
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:123
msgid "Twitter Scroller"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:125
msgid "Display the Twitter feeds with customer satifaction on your website. This will increase the number of tweets and shares."
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:129
msgid "Test Your Website"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:131
msgid "You can compare how your website rank, in terms of SEO, against Odoo using WooRank free services: `woorank.com <https://www.woorank.com>`_"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:136
msgid "URLs Handling"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:138
msgid "This section sheds some light on how Odoo makes URLs SEO-friendly."
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:141
msgid "URLs Structure"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:143
msgid "A typical Odoo URL will look like this:"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:145
msgid "https://www.mysite.com/fr\\_FR/shop/product/my-great-product-31"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:147
msgid "With the following components:"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:149
msgid "**https://** = Protocol"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:151
msgid "**www.mysite.com** = your domain name"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:153
msgid "**/fr\\_FR** = page language. This part of the URL is removed if the visitor browses the main language of the website Thus, the main version of this page is: https://www.mysite.com/shop/product/my-great-product-31"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:158
msgid "**/shop/product** = every module defines its own namespace (/shop is for the catalog of the eCommerce module, /shop/product is for a product page)."
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:162
msgid "**my-great-product** = by default, this is the slugified title of the product this page refers to. But you can customize it for SEO purposes. A product named \"Pain carré\" will be slugified to \"pain-carre\". Depending on the namespace, this could be different objects (blog post, page title, forum post, forum comment, product category, etc.)."
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:169
msgid "**-31** = the unique ID of the product"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:171
msgid "Note that any dynamic component of an URL can be reduced to its ID. As an example, the following URLs all do a 301 redirect to the above URL:"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:174
msgid "https://www.mysite.com/fr\\_FR/shop/product/31 (short version)"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:176
msgid "http://mysite.com/fr\\_FR/shop/product/31 (even shorter version)"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:178
msgid "http://mysite.com/fr\\_FR/shop/product/other-product-name-31 (old product name)"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:181
msgid "Some URLs have several dynamic parts, like this one (a blog category and a post):"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:184
msgid "https://www.odoo.com/blog/company-news-5/post/the-odoo-story-56"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:186
msgid "In the above example:"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:188
msgid "*Company News* is the title of the blog"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:190
msgid "*The Odoo Story* is the title of a specific blog post"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:192
msgid "When an Odoo page has a pager, the page number is set directly in the URL (does not have a GET argument). This allows every page to be indexed by search engines. Example:"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:196
msgid "https://www.odoo.com/blog/page/3"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:199
msgid "Changes in URLs & Titles"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:201
msgid "When the URL of a page changes (e.g. a more SEO friendly version of your product name), you don't have to worry about updating all links:"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:204
msgid "Odoo will automatically update all its links to the new URL."
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:206
msgid "If external websites still points to the old URL, a 301 redirect will be done to route visitors to the new address of the page."
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:209
msgid "As an example, this URL:"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:211
msgid "http://mysite.com/shop/product/old-product-name-31"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:213
msgid "Will automatically redirect to:"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:215
msgid "http://mysite.com/shop/product/new-and-better-product-name-31"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:217
msgid "In short, just change the title of a blog post or the name of a product, and the changes will apply automatically everywhere in your website. The old link still functions when used by external websites, via a 301 redirect, maintaining the SEO link juice."
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:223
msgid "HTTPS"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:225
msgid "Search engines boost ranking of secure HTTPS/SSL websites. So, by default all Odoo Online instances are fully based on HTTPS. If the visitor accesses your website through a non HTTPS url, it gets a 301 redirect to its HTTPS equivalent."
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:231
msgid "Links: Nofollow Strategy"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:233
msgid "The more a page is linked from external and quality websites, the better it is for your SEO."
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:236
msgid "Here are Odoo strategies to manage links:"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:238
msgid "Every link you add to your website is \"dofollow\", which means that this link will contribute to the SEO Juice for the linked page."
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:242
msgid "Every link posted by a contributor (forum post, blog comment, etc.) that links to your own website is \"dofollow\" too."
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:245
msgid "But every link posted by a contributor that links to an external website is \"nofollow\". In that way, you do not run the risk of people posting links on your website to third-party websites which have a bad reputation."
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:250
msgid "Note that, when using the forum, contributors having a lot of Karma can be trusted. In such case, their links will not have any ``rel=\"nofollow\"`` attribute."
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:255
msgid "Multi-Language Support"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:258
msgid "Multi-Language URLs"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:260
msgid "If you run a website in multiple languages, the same content will be available in different URLs, depending on the language used:"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:263
msgid "https://www.mywebsite.com/shop/product/my-product-1 (main language, English here)"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:265
msgid "https://www.mywebsite.com\\/fr\\_FR/shop/product/mon-produit-1 (French version)"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:267
msgid "In this example, fr\\_FR is the language of the page. You can even have several variations of the same language: pt\\_BR (Portuguese from Brazil) , pt\\_PT (Portuguese from Portugal)."
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:272
msgid "Language Annotation"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:274
msgid "To let search engines know that the second URL is the French translation of the first URL, Odoo will add an HTML link element in the header. In the HTML <head> section of the main version, Odoo automatically adds a link element pointing to the translated versions of that webpage;"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:279
msgid "<link rel=\"alternate\" hreflang=\"fr\" href=\"https://www.mywebsite.com\\/fr\\_FR/shop/product/mon-produit-1\"/>"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:282
msgid "With this approach:"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:284
msgid "Search engines will redirect to the right language according to the visitor language."
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:287
msgid "You do not get penalized by search engines if your page is not translated yet. Indeed, it's not a duplicated content, but a different version of the same content."
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:292
msgid "Language Detection"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:294
msgid "When a visitor lands for the first time on your website (e.g. yourwebsite.com/shop), they may automatically be redirected to a translated version according to their browser language preference (e.g. yourwebsite.com/fr\\_FR/shop)."
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:299
msgid "Next time, it keeps a cookie of the current language to avoid any redirection."
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:302
msgid "To force a visitor to stick to the default language, you can use the code of the default language in your link, example: yourwebsite.com/en\\_US/shop. This will always land visitors to the English version of the page, without using the browser language preferences."
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:309
msgid "Page Speed"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:312
msgid "Introduction"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:314
msgid "The time to load a page is an important criteria for search engines. A faster website not only improves your visitor's experience, but gives you a better page ranking. Some studies have shown that, if you divide the time to load your pages by two (e.g. 2 seconds instead of 4 seconds), the visitor abandonment rate is also divided by two. (25% to 12.5%). One extra second to load a page could `cost $1.6b to Amazon in sales <http://www.fastcompany.com/1825005/how-one-second-could-cost-amazon-16-billion-sales>`__."
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:325
msgid "Fortunately, Odoo does all the magic for you. Below, you will find the tricks Odoo uses to speed up your page loading time. You can compare how your website ranks using these two tools:"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:329
msgid "`Google Page Speed <https://developers.google.com/speed/pagespeed/insights/>`__"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:331
msgid "`Pingdom Website Speed Test <http://tools.pingdom.com/fpt/>`__"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:334
msgid "Images"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:336
msgid "When you upload new images, Odoo automatically compresses them to reduce their sizes (lossless compression for .PNG and .GIF and lossy compression for .JPG)."
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:340
msgid "From the upload button, you have the option to keep the original image unmodified if you prefer to optimize the quality of the image rather than performance."
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:348
msgid "Odoo compresses images when they are uploaded to your website, not when requested by the visitor. Thus, it's possible that, if you use a third-party theme, it will provide images that are not compressed efficiently. But all images used in Odoo official themes have been compressed by default."
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:354
msgid "When you click on an image, Odoo shows you the Alt and title attributes of the ``<img>`` tag. You can click on it to set your own title and Alt attributes for the image."
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:361
msgid "When you click on this link, the following window will appear:"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:366
msgid "Odoo's pictograms are implemented using a font (`Font Awesome <https://fortawesome.github.io/Font-Awesome/icons/>`__ in most Odoo themes). Thus, you can use as many pictograms as you want in your page, they will not result in extra requests to load the page."
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:375
msgid "Static Resources: CSS"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:377
msgid "All CSS files are pre-processed, concatenated, minified, compressed and cached (server-side and browser-side). The result:"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:380
msgid "only one CSS file request is needed to load a page"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:382
msgid "this CSS file is shared and cached amongst pages, so that when the visitor clicks on another page, the browser doesn't have to even load a single CSS resource."
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:386
msgid "this CSS file is optimized to be small"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:388
msgid "**Pre-processed:** The CSS framework used by Odoo is Bootstrap. Although a theme might use another framework, most of `Odoo themes <https://www.odoo.com/apps/themes>`__ extend and customize Bootstrap directly. Since Odoo supports Less and Sass, you can modify CSS rules instead of overwriting them through extra CSS lines, resulting in a smaller file."
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:395
msgid "**Concatenated:** every module or library you might use in Odoo has its own set of CSS, Less or Sass files (eCommerce, blogs, themes, etc.). Having several CSS files is great for the modularity, but not good for the performance because most browsers can only perform 6 requests in parallel resulting in lots of files loaded in series. The latency time to transfer a file is usually much longer than the actual data transfer time, for small files like .JS and .CSS. Thus, the time to load CSS resources depends more on the number of requests to be done than the actual file size."
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:405
msgid "To address this issue, all CSS / Less / Sass files are concatenated into a single .CSS file to send to the browser. So a visitor has **only one .CSS file to load** per page, which is particularly efficient. As the CSS is shared amongst all pages, when the visitor clicks on another page, the browser does not even have to load a new CSS file!"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:412
msgid "**Both files in the <head>**"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:412
msgid "**What the visitor gets (only one file)**"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:414
msgid "/\\* From bootstrap.css \\*/"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:414
#: ../../content/applications/websites/website/optimize/seo.rst:415
#: ../../content/applications/websites/website/optimize/seo.rst:421
#: ../../content/applications/websites/website/optimize/seo.rst:447
msgid ".text-muted {"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:415
#: ../../content/applications/websites/website/optimize/seo.rst:422
#: ../../content/applications/websites/website/optimize/seo.rst:448
msgid "color: #666;"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:416
msgid "color: #777;"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:416
msgid "background: yellow"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:417
msgid "background: yellow;"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:417
#: ../../content/applications/websites/website/optimize/seo.rst:418
#: ../../content/applications/websites/website/optimize/seo.rst:423
#: ../../content/applications/websites/website/optimize/seo.rst:449
msgid "}"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:420
msgid "/\\* From my-theme.css \\*/"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:426
msgid "The CSS sent by Odoo includes all CSS / Less / Sass of all pages / modules. By doing this, additional page views from the same visitor will not have to load CSS files at all. But some modules might include huge CSS/Javascript resources that you do not want to prefetch at the first page because they are too big. In this case, Odoo splits this resource into a second bundle that is loaded only when the page using it is requested. An example of this is the backend that is only loaded when the visitor logs in and accesses the backend (/web)."
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:436
msgid "If the CSS file is very big, Odoo will split it into two smaller files to avoid the 4095 selectors limit per sheet of Internet Explorer. But most themes fit below this limit."
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:440
msgid "**Minified:** After being pre-processed and concatenated, the resulting CSS is minified to reduce its size."
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:444
msgid "**Before minification**"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:444
msgid "**After minification**"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:446
msgid "/\\* some comments \\*/"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:446
msgid ".text-muted {color: #666}"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:452
msgid "The final result is then compressed, before being delivered to the browser."
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:455
msgid "Then, a cached version is stored server-side (so we do not have to pre-process, concatenate, minify at every request) and browser-side (so the same visitor will load the CSS only once for all pages they visit)."
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:461
msgid "Static Resources: Javascript"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:463
msgid "As with CSS resources, Javascript resources are also concatenated, minified, compressed and cached (server-side and browser-side)."
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:466
msgid "Odoo creates three Javascript bundles:"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:468
msgid "One for all pages of the website (including code for parallax effects, form validation, etc.)"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:471
msgid "One for common Javascript code shared among frontend and backend (Bootstrap)"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:474
msgid "One for backend specific Javascript code (Odoo Web Client interface for your employees using Odoo)"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:477
msgid "Most visitors of your website will only need the first two bundles, resulting in a maximum of two Javascript files to load to render one page. As these files are shared across all pages, further clicks by the same visitor will not load any other Javascript resource."
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:483
msgid "If you work on :ref:`developer mode <developer-mode>`, the CSS and Javascript are neither concatenated, nor minified. Thus, it's much slower. But it allows you to easily debug with the Chrome debugger as CSS and Javascript resources are not transformed from their original versions."
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:488
msgid "CDN"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:490
msgid "If you activate the CDN feature in Odoo, static resources (Javascript, CSS, images) are loaded from a Content Delivery Network. Using a Content Delivery Network has three advantages:"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:494
msgid "Load resources from a nearby server (most CDN have servers in main countries around the globe)"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:497
msgid "Cache resources efficiently (no computation resources usage on your own server)"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:500
msgid "Split the resource loading on different services allowing to load more resources in parallel (since the Chrome limit of 6 parallel requests is by domain)"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:504
msgid "You can configure your CDN options from the **Website Admin** app, using the Configuration menu. Here is an example of configuration you can use:"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:511
msgid "HTML Pages"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:513
msgid "The HTML pages can be compressed, but this is usually handled by your web server (NGINX or Apache)."
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:516
msgid "The Odoo Website builder has been optimized to guarantee clean and short HTML code. Building blocks have been developed to produce clean HTML code, usually using Bootstrap and the HTML editor."
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:520
msgid "As an example, if you use the color picker to change the color of a paragraph to the primary color of your website, Odoo will produce the following code:"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:524
msgid "``<p class=\"text-primary\">My Text</p>``"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:526
msgid "Whereas most HTML editors (such as CKEditor) will produce the following code:"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:529
msgid "``<p style=\"color: #AB0201\">My Text</p>``"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:532
msgid "Responsive Design"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:534
msgid "Websites that are not mobile-friendly are negatively impacted in search engine rankings. All Odoo themes rely on Bootstrap to render efficiently according to the device: desktop, tablet or mobile."
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:541
msgid "As all Odoo modules share the same technology, absolutely all pages in your website are mobile friendly."
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:545
msgid "Browser Caching"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:547
msgid "Javascript, images and CSS resources have an URL that changes dynamically when their content change. As an example, all CSS files are loaded through this URL: `localhost:8069/web/content/457-0da1d9d/web.assets\\_common.0.css <http://localhost:8069/web/content/457-0da1d9d/web.assets_common.0.css>`__. The ``457-0da1d9d`` part of this URL will change if you modify the CSS of your website."
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:554
msgid "This allows Odoo to set a very long cache delay (XXX) on these resources: XXX secs, while being updated instantly if you update the resource."
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:559
msgid "Scalability"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:561
msgid "In addition to being fast, Odoo is also more scalable than traditional CMS and eCommerce (Drupal, Wordpress, Magento, Prestashop). The following link provides an analysis of the major open source CMS and eCommerce compared to Odoo when it comes to high query volumes: `https://www.odoo.com/slides/slide/197 <https://www.odoo.com/slides/slide/odoo-cms-performance-comparison-and-optimisation-197>`_"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:568
msgid "Todo"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:568
msgid "fix above link"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:570
msgid "Here is the slide that summarizes the scalability of Odoo Website & eCommerce."
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:576
msgid "Search Engines Files"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:579
msgid "Sitemap"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:581
msgid "The sitemap points out pages to index to search engine robots. Odoo generates a ``/sitemap.xml`` file automatically for you. For performance reasons, this file is cached and updated every 12 hours."
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:585
msgid "By default, all URLs will be in a single ``/sitemap.xml`` file, but if you have a lot of pages, Odoo will automatically create a Sitemap Index file, respecting the `sitemaps.org protocol <http://www.sitemaps.org/protocol.html>`__ grouping sitemap URL's in 45000 chunks per file."
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:591
msgid "Every sitemap entry has 4 attributes that are computed automatically:"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:593
msgid "``<loc>`` : the URL of a page"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:595
msgid "``<lastmod>`` : last modification date of the resource, computed automatically based on related object. For a page related to a product, this could be the last modification date of the product or the page."
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:600
msgid "``<priority>`` : modules may implement their own priority algorithm based on their content (example: a forum might assign a priority based on the number of votes on a specific post). The priority of a static page is defined by it's priority field, which is normalized (16 is the default)."
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:607
msgid "Structured Data Markup"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:609
msgid "Structured Data Markup is used to generate Rich Snippets in search engine results. It is a way for website owners to send structured data to search engine robots; helping them understand your content and create well-presented search results."
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:614
msgid "Google supports a number of rich snippets for content types, including: Reviews, People, Products, Businesses, Events and Organizations."
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:617
msgid "Odoo implements micro data as defined in the `schema.org <http://schema.org>`__ specification for events, eCommerce products, forum posts and contact addresses. This allows your product pages to be displayed in Google using extra information like the price and rating of a product:"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:627
msgid "robots.txt"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:629
msgid "When indexing your website, search engines take a first look at the general indexing rules of the a``/robots.txt`` file (allowed robots, sitemap path, etc.). Odoo automatically creates it. Its content is:"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:633
msgid "User-agent: \\* Sitemap: https://www.odoo.com/sitemap.xml"
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:636
msgid "It means that all robots are allowed to index your website and there is no other indexing rule than specified in the sitemap to be found at following address."
msgstr ""

#: ../../content/applications/websites/website/optimize/seo.rst:640
msgid "You can customize the file *robots* in :ref:`developer mode <developer-mode>` from *Settings --> Technical --> User Interface --> Views* (exclude robots, exclude some pages, redirect to a custom Sitemap). Make the Model Data of the view *Non Updatable* to not reset the file after system upgrades."
msgstr ""

#: ../../content/applications/websites/website/optimize/unsplash.rst:3
msgid "Unsplash (free images)"
msgstr ""

#: ../../content/applications/websites/website/optimize/unsplash.rst:6
msgid "Generate an Unsplash access key"
msgstr ""

#: ../../content/applications/websites/website/optimize/unsplash.rst:9
msgid "**As a SaaS user**, you are ready to use Unsplash. You won't need to follow this guide to set up Unsplash information since you will use our own Odoo Unsplash key in a transparent way."
msgstr ""

#: ../../content/applications/websites/website/optimize/unsplash.rst:13
msgid "Generate an Unsplash access key for non-Saas users"
msgstr ""

#: ../../content/applications/websites/website/optimize/unsplash.rst:15
msgid "Create an account on `Unsplash.com <https://unsplash.com/join>`_."
msgstr ""

#: ../../content/applications/websites/website/optimize/unsplash.rst:17
msgid "Go to your `applications dashboard <https://unsplash.com/oauth/applications>`_ and click on **New Application**."
msgstr ""

#: ../../content/applications/websites/website/optimize/unsplash.rst:23
msgid "Accept the conditions and click on **Accept terms**."
msgstr ""

#: ../../content/applications/websites/website/optimize/unsplash.rst:28
msgid "You will be prompted to insert an **Application name** and a **Description**. Please prefix your application name by \"**Odoo:** \" so that Unsplash can recognize it as an Odoo instance. Once done, click on **Create application**."
msgstr ""

#: ../../content/applications/websites/website/optimize/unsplash.rst:35
msgid "You should be redirected to your application details page. Scroll down a bit to find your **access key**."
msgstr ""

#: ../../content/applications/websites/website/optimize/unsplash.rst:42
msgid "**As a non-SaaS user**, you won't be able to register for a production Unsplash key and will be limited to your test key that has a restriction of 50 Unsplash requests per hour."
msgstr ""

#: ../../content/applications/websites/website/optimize/unsplash.rst:46
msgid "Generate an Unsplash application ID"
msgstr ""

#: ../../content/applications/websites/website/optimize/unsplash.rst:49
msgid "You should first create and set up your Unsplash application."
msgstr ""

#: ../../content/applications/websites/website/optimize/unsplash.rst:51
msgid "Go to your `applications dashboard <https://unsplash.com/oauth/applications>`_ and click on your newly created Unsplash application under **Your applications**."
msgstr ""

#: ../../content/applications/websites/website/optimize/unsplash.rst:57
msgid "You will be redirected to your application details page. The **application ID** will be visible in your browser's URL. The URL should be something like ``https://unsplash.com/oauth/applications/<application_id>``"
msgstr ""

#: ../../content/applications/websites/website/optimize/unsplash.rst:65
msgid "**As a non-SaaS user**, you won't be able to register for a production Unsplash key and will be limited to your test key that has a 50 Unsplash requests per hour restriction."
msgstr ""

#: ../../content/applications/websites/website/publish.rst:5
msgid "Publish"
msgstr ""

#: ../../content/applications/websites/website/publish/multi_website.rst:3
msgid "Manage Multi Websites"
msgstr ""

#: ../../content/applications/websites/website/publish/multi_website.rst:8
msgid "Odoo’s Multi-Websites opens up broad possibilities of diversification and customer segmentation for your business. A multiplied audience and boosted revenue are now just a few clicks away!"
msgstr ""

#: ../../content/applications/websites/website/publish/multi_website.rst:12
msgid "Each website can work in a fully independent way, with its theme, branding, domain name, header & footer, pages, languages, products, blog posts, forum, slides, events, live chat channels, etc. Let’s go for a tour!"
msgstr ""

#: ../../content/applications/websites/website/publish/multi_website.rst:20
msgid "To create a new website, go to :menuselection:`Website --> Configuration --> Settings`. The button, *Create a new website*, lays in the first section."
msgstr ""

#: ../../content/applications/websites/website/publish/multi_website.rst:28
msgid "In the upcoming prompt, set a name for your new website and a specific domain name. Leave empty to publish the new website under the default domain of your Odoo database. You can later set some country groups to redirect visitors to it using Geo IP."
msgstr ""

#: ../../content/applications/websites/website/publish/multi_website.rst:36
msgid "Then, select a theme. This new website might have an entirely different purpose or audience than the first one. So feel free to go for a different theme!"
msgstr ""

#: ../../content/applications/websites/website/publish/multi_website.rst:40
msgid "Once the theme is selected, you can start to build the homepage of your website. Follow the purple drops; they will help you in the first steps."
msgstr ""

#: ../../content/applications/websites/website/publish/multi_website.rst:48
msgid "If you run Odoo Online, don’t forget to redirect any new domain name to your Odoo database (``CNAME``) and to authorize it Odoo-side. See :ref:`domain-name/existing`."
msgstr ""

#: ../../content/applications/websites/website/publish/multi_website.rst:52
msgid "Create the menu"
msgstr ""

#: ../../content/applications/websites/website/publish/multi_website.rst:54
msgid "The new website has a default menu with all the installed applications. To edit it, click :menuselection:`Pages --> Edit Menu`. Moving forward you only edit the menu of the current website."
msgstr ""

#: ../../content/applications/websites/website/publish/multi_website.rst:59
msgid "Switch from one website to another"
msgstr ""

#: ../../content/applications/websites/website/publish/multi_website.rst:62
msgid "As easy as ABC! There is a website switcher in the right corner of the edit bar. Switching to another website will connect to the domain of this website. If you use another domain for the website, the user is requested to sign in."
msgstr ""

#: ../../content/applications/websites/website/publish/multi_website.rst:71
msgid "When switching, you are redirected to the same domain path on the other website (e.g., ``/shop/myproduct``). If this URL is not used, you will be redirected to a 404 page but prompted to create a new page from there."
msgstr ""

#: ../../content/applications/websites/website/publish/multi_website.rst:76
msgid "Add features"
msgstr ""

#: ../../content/applications/websites/website/publish/multi_website.rst:78
msgid "The website apps you install (e.g., Slides, Blogs) are made available on all your websites. You can, of course, keep them hidden in one website by removing the menu item."
msgstr ""

#: ../../content/applications/websites/website/publish/multi_website.rst:82
msgid "Each website comes with a high range of specific options in the settings. First, select the website to configure."
msgstr ""

#: ../../content/applications/websites/website/publish/multi_website.rst:88
msgid "Then, take a look at the options flagged with the earth icon. It means they only impact the very website you are working on."
msgstr ""

#: ../../content/applications/websites/website/publish/multi_website.rst:94
msgid "You can, for instance, set specific :"
msgstr ""

#: ../../content/applications/websites/website/publish/multi_website.rst:96
msgid "languages,"
msgstr ""

#: ../../content/applications/websites/website/publish/multi_website.rst:98
msgid "domain names,"
msgstr ""

#: ../../content/applications/websites/website/publish/multi_website.rst:100
msgid "social media links,"
msgstr ""

#: ../../content/applications/websites/website/publish/multi_website.rst:102
msgid "customer portal mode (B2C vs. B2B),"
msgstr ""

#: ../../content/applications/websites/website/publish/multi_website.rst:104
msgid "dedicated live chat channels,"
msgstr ""

#: ../../content/applications/websites/website/publish/multi_website.rst:106
msgid "etc."
msgstr ""

#: ../../content/applications/websites/website/publish/multi_website.rst:108
msgid "The other options are global and apply to all your websites."
msgstr ""

#: ../../content/applications/websites/website/publish/multi_website.rst:111
msgid "Manage domain names"
msgstr ""

#: ../../content/applications/websites/website/publish/multi_website.rst:113
msgid "As said earlier, your websites can either share the same domain name or use a specific one. If you share it and want to adapt the content per region, set country groups in the setting of each website. Visitors will be redirected to the right website using GeoIP."
msgstr ""

#: ../../content/applications/websites/website/publish/multi_website.rst:122
msgid "Geo IP is installed by default in Odoo Online. If you run Odoo on-premise, don’t forget to install *GeoIP* library. See :doc:`on-premise_geo-ip-installation`"
msgstr ""

#: ../../content/applications/websites/website/publish/multi_website.rst:127
msgid ":doc:`/administration/maintain/domain_names`"
msgstr ""

#: ../../content/applications/websites/website/publish/multi_website.rst:130
msgid "Customize the visitor experience"
msgstr ""

#: ../../content/applications/websites/website/publish/multi_website.rst:133
msgid "The customer experience can be customized very profoundly thanks to the menu \\*Customize\\*. All the visual options available there are specific to each website. Go through the different pages to adapt them to this new audience. Focus on workflows, and automatic pages (eCommerce checkout, blogs, events, etc.) as the number of available options is higher there."
msgstr ""

#: ../../content/applications/websites/website/publish/multi_website.rst:143
msgid "Publish specific content per website"
msgstr ""

#: ../../content/applications/websites/website/publish/multi_website.rst:146
msgid "Like static pages, any content created from the front-end (product, blog post, etc.) is always only published in the current website. You can change that from the edit form view in the backend and leave the *Website* field blank. This will publish it in all the websites."
msgstr ""

#: ../../content/applications/websites/website/publish/multi_website.rst:154
msgid "Here are all the objects that you can link to *either one or all the websites*:"
msgstr ""

#: ../../content/applications/websites/website/publish/multi_website.rst:157
msgid "Products"
msgstr ""

#: ../../content/applications/websites/website/publish/multi_website.rst:159
msgid "Product Categories for eCommerce"
msgstr ""

#: ../../content/applications/websites/website/publish/multi_website.rst:161
msgid "Blogs"
msgstr ""

#: ../../content/applications/websites/website/publish/multi_website.rst:163
msgid "Slide Channels"
msgstr ""

#: ../../content/applications/websites/website/publish/multi_website.rst:165
msgid "Forums"
msgstr ""

#: ../../content/applications/websites/website/publish/multi_website.rst:167
msgid "Events"
msgstr ""

#: ../../content/applications/websites/website/publish/multi_website.rst:169
msgid "Job Positions"
msgstr ""

#: ../../content/applications/websites/website/publish/multi_website.rst:172
msgid "When you create the record from the backend and publish it, typically a product or an event, it is made available in all websites."
msgstr ""

#: ../../content/applications/websites/website/publish/multi_website.rst:176
msgid "Publish a page in all websites"
msgstr ""

#: ../../content/applications/websites/website/publish/multi_website.rst:178
msgid "A new static page is created and only made available in the current website. You can duplicate it to other websites from :menuselection:`Website --> Configuration --> Pages`. To do so, leave the *Website* field empty."
msgstr ""

#: ../../content/applications/websites/website/publish/multi_website.rst:182
msgid "If you want to duplicate it in just one other website, duplicate the page and set the new website."
msgstr ""

#: ../../content/applications/websites/website/publish/multi_website.rst:188
msgid "When you edit the page again, the change only affects the current website. A new page is duplicated and tied up to the website. The original page still being linked to all websites."
msgstr ""

#: ../../content/applications/websites/website/publish/multi_website.rst:193
msgid "By grouping pages by URL in the page manager, you quickly find the original page behind each edited page."
msgstr ""

#: ../../content/applications/websites/website/publish/multi_website.rst:200
msgid "Multi-companies"
msgstr ""

#: ../../content/applications/websites/website/publish/multi_website.rst:202
msgid "Each website can be linked to a specific company of your system, in a multi-companies environment."
msgstr ""

#: ../../content/applications/websites/website/publish/multi_website.rst:208
msgid "With such a configuration, only company-related data appear on the website (products, jobs, events, etc.)."
msgstr ""

#: ../../content/applications/websites/website/publish/multi_website.rst:211
msgid "Website editors can only view and edit the pages of the records they have access to, typically the ones belonging to their current company (and to their subsidiaries, or child companies in Odoo language). And so is it for visitors."
msgstr ""

#: ../../content/applications/websites/website/publish/multi_website.rst:217
msgid "If websites are multi-companies, you don’t change company when switching websites. To change the company and see the related content, use the company selector in the menu."
msgstr ""

#: ../../content/applications/websites/website/publish/multi_website.rst:223
msgid "Configure your eCommerce website"
msgstr ""

#: ../../content/applications/websites/website/publish/multi_website.rst:225
msgid "eCommerce is a crucial feature in the multi-websites environment. We made it so that the entire flow can be customized to fit the very audience of each website."
msgstr ""

#: ../../content/applications/websites/website/publish/multi_website.rst:230
msgid "Products only available on one website"
msgstr ""

#: ../../content/applications/websites/website/publish/multi_website.rst:232
msgid "We already saw earlier how to publish a specific record in only one website. You will find the \\*Website\\* field in the eCommerce tab of the product edit form. Empty means available in all websites."
msgstr ""

#: ../../content/applications/websites/website/publish/multi_website.rst:240
msgid "Products available on *some* websites"
msgstr ""

#: ../../content/applications/websites/website/publish/multi_website.rst:242
msgid "To make a product available on some websites, but not all of them, you should duplicate the product for each website."
msgstr ""

#: ../../content/applications/websites/website/publish/multi_website.rst:245
msgid "If you need a unique reference to manage in your inventory, you should install *Manufacturing\\ and create *Kits* BoMs (bills of materials). Each kit will link each published “virtual” product to the main reference managed in your inventory. That way, any item sold from your website will be converted into the storable item in the delivery order."
msgstr ""

#: ../../content/applications/websites/website/publish/multi_website.rst:252
msgid "Pricelists"
msgstr ""

#: ../../content/applications/websites/website/publish/multi_website.rst:254
msgid "To manage specific prices by websites, you can activate *Multiple Sales Prices per Product* in Website settings."
msgstr ""

#: ../../content/applications/websites/website/publish/multi_website.rst:257
msgid "Then, go to :menuselection:`Website --> Products --> Pricelists` to create additional pricelists. See :doc:`../../ecommerce/maximizing_revenue/pricing`."
msgstr ""

#: ../../content/applications/websites/website/publish/multi_website.rst:260
msgid "If you need help. Select a website to make a pricelist only available on this website."
msgstr ""

#: ../../content/applications/websites/website/publish/multi_website.rst:266
msgid "Leaving the field empty means that you make it work in all websites if *Selectable* is selected. Otherwise, it makes it only available for backend operations of Sales and Point of Sale applications."
msgstr ""

#: ../../content/applications/websites/website/publish/multi_website.rst:271
msgid "Payment Acquirers and Delivery Methods"
msgstr ""

#: ../../content/applications/websites/website/publish/multi_website.rst:273
msgid "By default, published payment acquirers and delivery methods are deployed in all websites. You could already use specific payment acquirers per country using Geo IP by defining countries in their configuration. Now you can also do it per website by filling in the *Website* field."
msgstr ""

#: ../../content/applications/websites/website/publish/multi_website.rst:279
msgid "Customer accounts"
msgstr ""

#: ../../content/applications/websites/website/publish/multi_website.rst:281
msgid "There is a setting to choose how to manage customer accounts in Website settings. You can either allow customers to use one account through all the websites or compel them to create one account for each website. This last option is convenient if your websites shouldn’t be related to each other in the visitor mind."
msgstr ""

#: ../../content/applications/websites/website/publish/multi_website.rst:291
msgid "Technical hints for customization"
msgstr ""

#: ../../content/applications/websites/website/publish/multi_website.rst:293
msgid "If you want to publish custom objects on the website, here are a few tips to make it work with multi websites:"
msgstr ""

#: ../../content/applications/websites/website/publish/multi_website.rst:297
msgid "Sitemap: don’t forget the domain in the route to only publish"
msgstr ""

#: ../../content/applications/websites/website/publish/multi_website.rst:297
msgid "available records in each website’s sitemap."
msgstr ""

#: ../../content/applications/websites/website/publish/multi_website.rst:301
msgid "Access: you should call the method"
msgstr ""

#: ../../content/applications/websites/website/publish/multi_website.rst:300
msgid "*can_access_from_current_website* in the controller to make sure the visitor can see a record in the current website."
msgstr ""

#: ../../content/applications/websites/website/publish/multi_website.rst:305
msgid "Search: when a list of records is displayed, don’t forget to specify"
msgstr ""

#: ../../content/applications/websites/website/publish/multi_website.rst:304
msgid "the domain to only display records available for the current website."
msgstr ""

#: ../../content/applications/websites/website/publish/on-premise_geo-ip-installation.rst:3
msgid "Geo IP Installation (On-Premises Database)"
msgstr ""

#: ../../content/applications/websites/website/publish/on-premise_geo-ip-installation.rst:6
msgid "Installation"
msgstr ""

#: ../../content/applications/websites/website/publish/on-premise_geo-ip-installation.rst:9
msgid "Please note that the installation depends on your computer's operating system and distribution. We will assume that a Linux operating system is being used."
msgstr ""

#: ../../content/applications/websites/website/publish/on-premise_geo-ip-installation.rst:15
msgid "Install `geoip2 <https://pypi.org/project/geoip2/>`__ Python library"
msgstr ""

#: ../../content/applications/websites/website/publish/on-premise_geo-ip-installation.rst:17
msgid "Download the `GeoLite2 City database <https://dev.maxmind.com/geoip/geoip2/geolite2/>`_. You should end up with a file called ``GeoLite2-City.mmdb``"
msgstr ""

#: ../../content/applications/websites/website/publish/on-premise_geo-ip-installation.rst:22
msgid "Move the file to the folder ``/usr/share/GeoIP/``"
msgstr ""

#: ../../content/applications/websites/website/publish/on-premise_geo-ip-installation.rst:24
msgid "Restart the server"
msgstr ""

#: ../../content/applications/websites/website/publish/on-premise_geo-ip-installation.rst:27
msgid "If you can't/don't want to locate the geoip database in ``/usr/share/GeoIP/``, you can use the ``--geoip-db`` option of the Odoo command line interface. This option takes the absolute path to the GeoIP database file and uses it as the GeoIP database. For example:"
msgstr ""

#: ../../content/applications/websites/website/publish/on-premise_geo-ip-installation.rst:36
msgid ":doc:`CLI documentation </developer/misc/other/cmdline>`."
msgstr ""

#: ../../content/applications/websites/website/publish/on-premise_geo-ip-installation.rst:39
msgid "``GeoIP`` Python library can also be used. However this version is discontinued since January 1.    See `GeoLite Legacy databases are now discontinued <https://support.maxmind.com/geolite-legacy-discontinuation-notice/>`_"
msgstr ""

#: ../../content/applications/websites/website/publish/on-premise_geo-ip-installation.rst:44
msgid "How To Test GeoIP Geolocation In Your Odoo Website"
msgstr ""

#: ../../content/applications/websites/website/publish/on-premise_geo-ip-installation.rst:45
msgid "Go to your website. Open the web page that you want to test ``GeoIP``."
msgstr ""

#: ../../content/applications/websites/website/publish/on-premise_geo-ip-installation.rst:46
msgid "Choose :menuselection:`Customize --> HTML/CSS/JS Editor`."
msgstr ""

#: ../../content/applications/websites/website/publish/on-premise_geo-ip-installation.rst:47
msgid "Add the following piece of XML in the page :"
msgstr ""

#: ../../content/applications/websites/website/publish/on-premise_geo-ip-installation.rst:53
msgid "You should end up with a dictionary indicating the location of the IP address."
msgstr ""

#: ../../content/applications/websites/website/publish/on-premise_geo-ip-installation.rst:59
msgid "If the curly braces are empty ``{}``, it can be for any of the following reasons :"
msgstr ""

#: ../../content/applications/websites/website/publish/on-premise_geo-ip-installation.rst:61
msgid "The browsing IP address is the localhost (``127.0.0.1``) or a local area network one (``192.168.*.*``)"
msgstr ""

#: ../../content/applications/websites/website/publish/on-premise_geo-ip-installation.rst:62
msgid "If a reversed proxy is used, make sure to configure it correctly. See :option:`proxy mode <odoo-bin --proxy-mode>`"
msgstr ""

#: ../../content/applications/websites/website/publish/on-premise_geo-ip-installation.rst:63
msgid "``geoip2`` is not installed or the GeoIP database file wasn't found"
msgstr ""

#: ../../content/applications/websites/website/publish/on-premise_geo-ip-installation.rst:64
msgid "The GeoIP database was unable to resolve the given IP address"
msgstr ""

#: ../../content/applications/websites/website/publish/translate.rst:3
msgid "How to translate my website"
msgstr ""

#: ../../content/applications/websites/website/publish/translate.rst:8
msgid "In addition to creating great modern websites, Odoo gives you the possibility to translate it in different languages."
msgstr ""

#: ../../content/applications/websites/website/publish/translate.rst:12
msgid "Process"
msgstr ""

#: ../../content/applications/websites/website/publish/translate.rst:14
msgid "Once your website is created, you have the opportunity to translate it in as many different languages as you want."
msgstr ""

#: ../../content/applications/websites/website/publish/translate.rst:17
msgid "You can only translate your website manually, follow the next step."
msgstr ""

#: ../../content/applications/websites/website/publish/translate.rst:19
msgid "Now go to your website. On the bottom right corner of the page, click on **Add a language**."
msgstr ""

#: ../../content/applications/websites/website/publish/translate.rst:25
msgid "Choose the language in which you want to translate your website and then click on **Load.**"
msgstr ""

#: ../../content/applications/websites/website/publish/translate.rst:31
msgid "You will see that Now, next to English there is also French, which means that the page for the translation has been created. You can also see that some of the text has been translated automatically."
msgstr ""

#: ../../content/applications/websites/website/publish/translate.rst:38
msgid "To translate the content of the website, click on **Translate** (here **Traduire** since we want to translate the website in French)."
msgstr ""