↑↓ selectEnter openEsc close

    1. Elbuz

    How to put a landing page on your site and your own domain

    3 min readUpdated

    Elbuz shows a ready landing page in your site's product description and, if needed, on your domain, credited to you by search engines.

    When you need this:

    • Page ready, not on your site — a line of code in the product card or an export template variable.
    • Pages in every product — the export template inserts code only where a page is ready.
    • Pages should help your SEO — your domain in settings plus a /landing/ proxy give a canonical to it.
    • How many people saw it — your site counter goes into every page.

    Where to start: “Open page” in the list → copy the embed code.

    What you can do with a ready page

    How to embed a page in the product description on your site

    A ready page is stored as a separate file in the cloud.

    There are two ways to show it to shoppers:

    • Embed code — a line with an iframe that you copy with a button and paste into the product card on your site.
    • Export template — a construction with landing_embed in the template's “Description generator” inserts the page into the description of every product that has one.

    The product description in the database stays unchanged. By design: the page is inserted into the export dynamically via the landing_embed variable in the export template's “Description generator”. Your description stays intact; remove the embed anytime, nothing to restore. But until the variable is in the export template, no page appears on your site, however many you generate.

    How to open pages on your site's domain

    By default, a page opens at the cloud storage address, not your site's, and search engines don't credit it to your domain. To open landing pages on your domain, like https://shop.example.com/landing/…, you need two things:

    1. A reverse proxy for the /landing/ path on your site. Your server administrator sets this up: on NGINX, one location ^~ /landing/ block with proxy_pass to the platform storage; if the site is behind Cloudflare, a Workers Routes rule for shop.example.com/landing/*.
      The storage address is visible in the “Open page” link of any ready page while the “Pages domain” field is still empty: everything before /landing/ is the address the proxy points to. Once the domain is filled in, the link shows your domain. All links inside the page are relative, so it works fully through the proxy.
    2. The domain in the generator settings. In the launch window, open “Generator settings — shared by all pages”, the “Pages domain” block, and enter your site's domain in the “Site domain (e.g. shop.example.com)” field. From then on, the “Open page” link and the embed code in the generator window and the product card show your domain, and newly generated pages get a canonical tag pointing to your domain, so search engines credit them to your site. An empty field means direct storage addresses.

    Pages that are already ready. The canonical is written into a page only during generation (and when a language version is created). “Rebuild all ready” and “Rebuild HTML” don't add or update it, so pages generated before the domain was filled in get a canonical pointing to your domain only after a new generation, which is paid.

    Export to your site. The landing_embed and landing_url variables in export templates use the page's storage address, not your domain: a block embedded through the export still loads from storage. Your domain is used only in the generator window and the product card, so if you need the address on your domain, paste the code from there.

    How to give search engines a sitemap of landing pages

    In the same place is the “Sitemap (sitemap.xml)” field: the “Create automatically” value enables the /landing/sitemap.xml file on your domain. It is rebuilt after every page generation and deletion. Add the line Sitemap: https://your-domain/landing/sitemap.xml to your site's robots.txt or submit this address in Google Search Console. Without a domain filled in, no sitemap is created.

    How to count landing page visitors

    The generator has no analytics for landing page visits, sales or conversion: the “Landing generator” window shows only “Total pages”, “Ready”, “Generating”, “Errors” and “Spent, $”.

    • Page views are counted by your site's counter (Google Analytics or another). Its code goes into “Generator settings” → “Custom code on pages” → “Custom JavaScript”, and it is added to every page on generation and rebuild.
    • Orders for a product are visible in the “Sales analytics” window, but Elbuz doesn't link them to visits to a specific landing page.

    Scenarios

    Show a page in a single product card

    What to do. Copy the embed code of the ready page and paste it into this product's description in your site's admin panel.

    What you get. Shoppers see the page in the product card. The description in the Elbuz database doesn't change.

    Pages in every product through the export

    What to do. In the export template, enable “Description generator” and add a construction with landing_embed to its template — the “Copy construction” button is in the same window (description generator).

    What you get. The code is inserted only for products with a ready page in the matching language; the rest get the regular description. You can remove the embed at any time without restoring any text.

    Pages on your own domain with a sitemap

    What to do. Ask your server administrator to set up a proxy for the /landing/ path, enter the domain in “Pages domain” and choose “Create automatically” for the sitemap. Add the sitemap address to robots.txt.

    What you get. New pages get a canonical pointing to your domain, and the sitemap updates after every generation. What you won't get: pages generated earlier won't get a canonical without a new paid generation.

    What to do when the page isn't on your site

    What you seeWhyWhat to do
    The page exists, but it isn't on the sitethe embed code or the variable in the export template hasn't been addedpaste the code or add landing_embed to the template's “Description generator”
    I deleted a page, and now there's an empty space on the sitethe page files in storage are deleted together with the record, so the embedded code no longer shows anythingremove the embed code from the site or generate the page again

    FAQ

    Will the generator overwrite my product description?

    No. The description in the database doesn't change: the page is inserted into the export dynamically. You can remove the embed at any time without restoring anything.

    Where can I see how many people visited a landing page and how many of them bought?

    Not in the generator. Page views are shown by your site's counter, whose code is added in “Custom JavaScript”, and purchases by “Sales analytics” for the product, without a link to views (how to count).

    Will the export use the address on my domain?

    No. The landing_embed and landing_url variables in export templates give the storage address. Take the code with your domain from the generator window or the product card.

    If I delete a page in the generator, what happens on my site?

    The page files are deleted together with the record, and the embedded code stops showing it. Remove the code from your site or generate the page again.

    I filled in the domain — why do old pages still have a canonical pointing to storage?

    The canonical is written only during generation. A rebuild doesn't add it, so pages generated earlier need a new paid generation.

    Where it is and who has access

    Embed code
    the “Landing generator” window or the product card → ready page
    Domain and sitemap
    launch window → “Generator settings — shared by all pages” → “Pages domain”
    Prepare
    a generated page; for the domain — access to your site's server settings

    Related topics

    Was this article helpful?

    Missing a feature? Tell us.

    We will add it for free if other users need it too.

    If only you need it, we will agree on it separately.

    Article contents

    Suggest an improvement

    Try Elbuz free