SEO settings guide - Remapdb Docs

This guide explains every SEO setting in Remapdb in plain language. You will learn what each setting does, why it matters for visibility and traffic, and how to set it correctly so more people can discover your website, open your widget pages, and contact you for tuning services.

Who this guide is for

Use this guide if you manage a Remapdb widget and you want better search visibility, better shared links, and clearer page content for visitors.

Before you configure SEO

Open page Code installation.
Complete Step 1: Save website in Remapdb so your website is in Allowed websites.
Confirm your widget is already live on your real website page.

If your website is missing in Allowed websites, the widget may not load, and SEO updates cannot run on your live page.

Where to configure these settings

Click the Settings item in the Widget section of the main navigation.
Go to section SEO.

How these settings support visibility, traffic, and leads

Better titles and descriptions make your pages clearer in search results, which can improve click-through rate.
Better social previews make shared links look more trustworthy, which can increase link clicks.
Visible vehicle summary text helps visitors understand gains faster, which can increase quote or contact intent.
Cleaner shareable links make it easier for people to revisit and share the same vehicle page.

If a setting is disabled

Some SEO controls depend on your plan.

Page title mode, Page title, Page description, and Title separator need Automatic metadata access.
Summary container ID, and Summary template need Automatic vehicle summary access.

If a control is disabled in the interface, open page Feature availability by plan and confirm your current plan access.

What each SEO setting does

What users can see vs what only search engines/bots read

This is important: not all SEO settings are visible as page text. Some settings are mostly for search engines, social crawlers, and bots.
Some settings are visible to normal visitors on your website. Quick rule:

If it is meta tags or structured data, visitors usually do not see it in page text.
If it is summary content, visitors do see it on the page.
If it is URL behavior, visitors see it in the address bar and shared links.

What meta tags are and where they are:

Meta tags are small information labels in the page <head> section (the top metadata area of the HTML document).
They are not shown as normal visible text in the page body.
Search engines and social crawlers read them to understand what your page is about.
Normal users usually see their effect indirectly, for example in Google snippets or social link previews.

Simple examples in page code:

<head>
  <title>Stage 2 tuning for Audi A3 2.0 TDI 150HP</title>
  <meta name="description" content="From 150 HP to Stage 2 190 HP...">
  <meta property="og:title" content="Stage 2 tuning for Audi A3 2.0 TDI 150HP">
  <meta property="og:description" content="From 150 HP to Stage 2 190 HP...">
</head>

In this example:

Visitors see the <title> in the browser tab.
Visitors usually do not see <meta ...> lines directly on the page.
Bots use those meta lines for search and social preview understanding.

Below, each category explains exactly what is visible to visitors and what is mostly for bots.

Search visibility settings

Visibility in this category:

Automatic metadata, Page title mode, and Title separator are control settings. Users do not see them as page text.
Page title appears in the browser tab and can appear in search results.
Page description is mainly a meta tag in the page <head>, used mostly by search engines.

Simple code example from this category:

<head>
  <title>Stage 2 tuning for Audi A3 2.0 TDI 150HP | Remapdb</title>
  <meta name="description" content="From 150 HP to Stage 2 190 HP...">
</head>

Automatic metadata

Turn this on when you want Remapdb to update your page title and page description based on the selected vehicle. In simple terms, this setting makes each vehicle page feel like a specific landing page instead of a generic widget page. When a visitor switches from one vehicle to another, Remapdb updates the SEO text to match that exact selection. This helps search engines and users understand what is on the page without guessing. Why this helps:

Search engines can understand each vehicle page better.
Search result snippets become more specific.
Better snippets usually bring more relevant clicks from people already searching for tuning.

Page title mode

This setting controls how Remapdb combines SEO title text with your existing page title. Options:

Append to existing title: keeps your current page title first, then adds vehicle SEO text.
Prepend to existing title: puts vehicle SEO text first, then adds your current page title.
Replace existing title: uses only the Remapdb SEO title.

Why this helps:

You can balance brand visibility and vehicle-specific keywords.
You can decide whether brand-first or vehicle-first wording works better for your audience.

Page title

This is the title template Remapdb uses for search engines and browser tabs. What is a page title: it is the main headline search engines usually show for your page, and it is also the text people see in their browser tab. This is often the first text a potential customer sees before they click your page. Example page title template: Stage ${best_stage} tuning for ${vehicleName} Example output for one vehicle: Stage 2 tuning for Audi A3 2.0 TDI 150HP Why this helps:

A clear vehicle title can improve click-through rate from search results.
Better click-through means more qualified visitors landing on your pages.

Page description

This is the description template shown under the title in many search results. What is a page description: it is the short summary under your page title in search results. It gives visitors context before they click, so they can quickly decide if your service is relevant for their vehicle. Example page description template:

Best available result for ${vehicleName}: Stage ${best_stage} with ${hp_best} HP and ${nm_best} Nm (OEM ${hp_oem} HP / ${nm_oem} Nm).

Example output for one vehicle: Best available result for Audi A3 2.0 TDI 150HP: Stage 2 with 190 HP and 410 Nm (OEM 150 HP / 320 Nm). Important clarification: ${best_stage}, ${hp_best}, and ${nm_best} always represent one single stage only, the highest available stage for that vehicle. They do not list all stages. Why this helps:

A clear description can attract people who are ready to compare tuning options.
Better description quality can increase visits from relevant users.

Title separator

This is the short separator text between your existing title and generated SEO title. This is mostly a readability setting. It does not add content value by itself, but it keeps your title clean when your base website title and dynamic Remapdb title are combined. Example separators: | or -. Why this helps:

Keeps page titles readable.
Makes brand and vehicle text easy to scan.

Visibility in this category:

Social sharing metadata is not visible as body text. It is mostly for social crawlers and bots.
Structured data is not visible as body text. It is a hidden JSON-LD script for bots.
Visitors mostly see the result indirectly when links render richer previews.

Simple code examples from this category:

<head>
  <meta property="og:title" content="Stage 2 tuning for Audi A3 2.0 TDI 150HP">
  <meta property="og:description" content="From 150 HP to Stage 2 190 HP...">
  <meta property="og:image" content="https://.../audi-a3.jpg">
  <script type="application/ld+json">{ ... }</script>
</head>

Turn this on to improve how links look when shared in places like Facebook, LinkedIn, and messaging apps. When this is on, Remapdb sends structured share-preview data for your current vehicle page, such as:

a social title (og:title)
a social description (og:description)
a preview image (og:image)
the page link (og:url)

This is why shared links can show a proper preview card instead of a plain URL. Better preview cards are easier to trust and usually attract more clicks from people who are already interested in tuning. Why this helps:

Shared links look more complete and professional.
Better previews usually get more clicks when your pages are shared.

Structured data

Turn this on to add hidden machine-readable vehicle data for search engines. What structured data is: a hidden block of information in a standard format that search engines read to understand page meaning. Visitors do not see it in the page body, but search engines use it as extra context. Remapdb outputs this in JSON-LD format. Simple example:

{
  "@context": "https://schema.org",
  "@type": "Thing",
  "name": "Audi A3 2.0 TDI 150HP",
  "description": "OEM 150 HP / 320 Nm to Stage 2 190 HP / 410 Nm"
}

This helps search engines understand that your page is about a specific vehicle and a specific tuning result, not only generic content. Why this helps:

Search engines understand your page context more clearly.
Clearer understanding can improve how your content is categorized and surfaced over time.

Structured data improves understanding, not instant rankings. It is a long-term quality signal.

Visibility in this category:

Automatic vehicle summary creates visible text in the page body.
Summary container ID is a technical placement setting (users do not see the ID itself).
Summary template is visible output text and can be read by both users and search engines.

Simple page-body example from this category:

<div id="rdb-ss">
  Audi A3 2.0 TDI 150HP: OEM 150 HP / 320 Nm to Stage 2 190 HP / 410 Nm.
</div>

Automatic vehicle summary

Turn this on to show visible, readable vehicle summary text on your page. This summary appears in your page content (outside the widget) in the location you control with Summary container ID. It updates when the selected vehicle changes, so visitors and search engines can both read vehicle-specific text directly on your page. Why this helps:

Search engines rely on visible page text, not only hidden tags.
Visitors immediately see useful tuning details without extra clicks.

Summary container ID

This is the target page element ID where summary text is injected. Example page element:

<div id="rdb-ss"></div>

Why this helps:

It lets you choose exactly where summary text appears in your page layout.

How to control this:

Use Automatic vehicle summary to turn summary text on or off.
Use Summary container ID to define where the text appears.
Use Summary template to control the wording users see.

Summary template

This controls the actual sentence shown in the summary container. This template uses dynamic values, so one template can work for many vehicles. As visitors switch vehicles, Remapdb replaces the variable placeholders with real values and updates the sentence automatically. Why this helps:

You can keep wording aligned with your service style.
You can highlight OEM vs tuned results in a simple, trustworthy sentence.

Link structure settings

Visibility in this category:

Clean vehicle URLs and Query parameter are visible in the browser address bar.
They are visible to users, and also parsed by bots and analytics systems.
These settings control how shared links look and how vehicle state is restored when someone opens the link.

Simple URL examples from this category:

Query style: https://yourwebsite.com/?catalog=cars/audi/a3/...
Clean style: https://yourwebsite.com/catalog/cars/audi/a3/...

Clean vehicle URLs

This chooses URL style for selected vehicles.

Off: URL uses query style (example ?catalog=...).
On: URL uses path style (example /catalog/...).

Why this helps:

Path-style links are often easier to read and share.
Clear links improve trust when users copy and send them.

Better example comparison:

Query style: https://yourwebsite.com/?catalog=cars/audi/a3/8p/20-tdi-150hp-320nm
Clean style: https://yourwebsite.com/catalog/cars/audi/a3/8p/20-tdi-150hp-320nm

The second version is easier for people to read, easier to share in messages, and easier to understand at a glance.

If you turn on Clean vehicle URLs, your website must route those path URLs to the page that contains your Remapdb widget. If routing is missing, users can get a 404 page.

Simple server examples (replace /tuning with the page URL where your widget is embedded): If your Query parameter is the default catalog, clean URLs like: /catalog/cars/audi/a3/... should be routed to: /tuning?catalog=cars/audi/a3/... Apache (.htaccess)

RewriteEngine On

# Keep existing files/folders working normally
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d

# /catalog/... -> /tuning?catalog=...
RewriteRule ^catalog/(.*)$ /tuning?catalog=$1 [L,QSA]

Nginx

# /catalog/... -> /tuning?catalog=...
location ~ ^/catalog/(.+)$ {
    rewrite ^/catalog/(.+)$ /tuning?catalog=$1&$args last;
}

Notes:

Keep your normal website URLs unchanged.
Replace catalog in the rules if you changed the Query parameter (for example vehicle or rdb).
Keep /catalog/ (or your custom key) as the path prefix when Clean vehicle URLs is enabled.
After adding rules, open one clean URL and confirm it loads the page with your Remapdb widget (not a 404 page).

Query parameter

This is the key used in your vehicle URL. Default example key: catalog. Why this helps:

You can keep URL structure clean and consistent with your website.
You can avoid conflicts with existing website parameters.

What a query parameter is: in a URL, it is the key name before =.
Example URL: https://yourwebsite.com/?catalog=cars/audi/a3/...
In this example, catalog is the query parameter key. How it works in Remapdb:

Remapdb writes the selected vehicle path into this key.
Remapdb reads this key when someone opens the link, so the same vehicle can be preselected.

Why changing it can be important:

Some websites already use specific URL keys for other features.
If your site or server already uses catalog for another purpose, you can change it to avoid collisions.
This helps prevent front-end and server-side conflicts, including broken routing, unexpected behavior, or URL parsing errors.

Practical examples:

Default: https://yourwebsite.com/?catalog=cars/audi/a3/...
Custom key: https://yourwebsite.com/?vehicle=cars/audi/a3/...
Another custom key: https://yourwebsite.com/?rdb=cars/audi/a3/...

Template values you can use

You can use these values in Page title, Page description, and Summary template. What these values do: they act as placeholders in your text templates. Remapdb replaces each placeholder with real vehicle data. This is what makes one template work dynamically for many vehicle pages. Why this helps dynamic content:

You write template text once.
Remapdb automatically updates it per selected vehicle.
Your page stays specific and relevant without manual rewriting.

Value	Meaning
`${vehicleName}`	Full vehicle name
`${hp_oem}`	Original horsepower
`${nm_oem}`	Original torque
`${best_stage}`	Single highest available tuning stage number
`${hp_best}`	Horsepower from that single best stage
`${nm_best}`	Torque from that single best stage

Example template:

Remap for ${vehicleName}: best result is Stage ${best_stage} (${hp_best} HP / ${nm_best} Nm), compared with OEM ${hp_oem} HP / ${nm_oem} Nm.

Example output for one vehicle: Remap for Audi A3 2.0 TDI 150HP: best result is Stage 2 (190 HP / 410 Nm), compared with OEM 150 HP / 320 Nm.

Field limits and save rules

Setting	Rule
Page title	Required, up to 70 characters
Page description	Required, up to 160 characters
Title separator	Required, up to 5 characters
Summary container ID	Required, up to 20 characters
Summary template	Required, up to 300 characters
Query parameter	Letters only, up to 30 characters

Save behavior in this section:

Toggles and dropdowns save right after you change them.
Text fields save when you click the Save button in that field block.

Recommended setup order

Turn on Automatic metadata.
Set Page title mode.
Write Page title, Page description, and Title separator.
Turn on Social sharing metadata.
Turn on Structured data.
Turn on Automatic vehicle summary.
Set Summary container ID and Summary template.
Decide if you want Clean vehicle URLs on or off.
Set Query parameter.

How to verify everything on your live website

Open your real widget page on your website.
Select a vehicle in the widget.
Check browser tab title and page description.
Check that summary text appears in your target summary container.
Copy the page link and open it in a new tab.
Confirm the same vehicle state is loaded.
Share the link in your preferred social channel and check preview quality.

Common issues and quick fixes

Page title or description did not change

Confirm Automatic metadata is turned on.
Confirm you clicked the Save button for title and description fields.
Refresh the page and test again on the live website.

Summary text is not visible

Confirm Automatic vehicle summary is turned on.
Confirm your page contains an element with the exact Summary container ID.
Confirm you clicked the Save button after editing the summary fields.

Shared link preview still shows old data

Re-share the link after selecting a vehicle again.
Some platforms cache previews for a while, so changes can appear with delay.

URL style does not work when clean URLs are on

Confirm your website routes that path to the page where widget code is installed.
If not, turn off Clean vehicle URLs until routing is ready.

Query parameter does not save

Use letters only.
Keep it short and do not use spaces, numbers, or symbols.

​Who this guide is for

​Before you configure SEO

​Where to configure these settings

​How these settings support visibility, traffic, and leads

​If a setting is disabled

​What each SEO setting does

​What users can see vs what only search engines/bots read

​Search visibility settings

​Automatic metadata

​Page title mode

​Page title

​Page description

​Title separator

​Social sharing and search understanding

​Social sharing metadata

​Structured data

​On-page SEO content

​Automatic vehicle summary

​Summary container ID

​Summary template

​Link structure settings

​Clean vehicle URLs

​Query parameter

​Template values you can use

​Field limits and save rules

​Recommended setup order

​How to verify everything on your live website

​Common issues and quick fixes

​Page title or description did not change

​Summary text is not visible

​Shared link preview still shows old data

​URL style does not work when clean URLs are on

​Query parameter does not save

​Related actions

Who this guide is for

Before you configure SEO

Where to configure these settings

How these settings support visibility, traffic, and leads

If a setting is disabled

What each SEO setting does

What users can see vs what only search engines/bots read

Search visibility settings

Automatic metadata

Page title mode

Page title

Page description

Title separator

Social sharing and search understanding

Social sharing metadata

Structured data

On-page SEO content

Automatic vehicle summary

Summary container ID

Summary template

Link structure settings

Clean vehicle URLs

Query parameter

Template values you can use

Field limits and save rules

Recommended setup order

How to verify everything on your live website

Common issues and quick fixes

Page title or description did not change

Summary text is not visible

Shared link preview still shows old data

URL style does not work when clean URLs are on

Query parameter does not save

Related actions