Languages, SEO, and publishing

Translate page text, review locale layouts, configure search and social metadata, run final checks, and publish safely.

PageDesigner stores one shared layout and separate translated values for bound text. SEO and social metadata are configured on the page record. Publication remains a separate final action.

How translations workCopy Anchor Link

Each translatable canvas text node can be bound to a stable key. The page stores values by locale:

{
  "hero.title": {
    "en": "Fast hosting for growing teams",
    "fr": "Un hébergement rapide pour les équipes en croissance"
  }
}

The component carries a data-pd-i18n key. At render time, PageDesigner resolves the visitor's locale and falls back according to the Paymenter locale configuration when a value is unavailable.

Normal editors do not need to edit keys manually.

Enable translations in the Text modalCopy Anchor Link

1. Select the section.
2. Open Text.
3. Select Enable translations.
4. Choose a locale.
5. Enter each translated value.
6. Switch locales and complete the same fields.
7. Close the modal and save.

Review a locale on the canvasCopy Anchor Link

Use the globe control in the top toolbar.

This is an editor-only review:

• it applies stored values to the canvas;
• it helps reveal wrapping and overflow;
• it does not change the Paymenter site's active locale;
• it does not publish or select a locale for visitors.

Check every supported language on mobile. A concise English CTA can become much wider in another language.

Translation quality checklistCopy Anchor Link

• Every meaningful text node is translated or intentionally falls back.
• Headings, paragraphs, CTA labels, captions, plan labels, and FAQ text agree.
• Prices, dates, numbers, currencies, units, and legal wording are correct for the audience.
• CTA text still describes the linked destination.
• Translated text fits each device width.
• A fluent reviewer checked important sales, support, billing, and policy text.
• No translation key was casually deleted or rebound.

SEO tabCopy Anchor Link

Open the page record and select SEO.

Meta DescriptionCopy Anchor Link

Write a concise, natural summary for a person deciding whether to open the page. The field allows up to 500 characters, but search interfaces often show a shorter excerpt.

Example:

Compare managed hosting plans, understand what each tier includes, and choose the right starting point for your team.

Do not repeat the title mechanically or fill the field with keyword variations.

Meta KeywordsCopy Anchor Link

This optional comma-separated field is not a replacement for useful visible content. Keep it short and honest if your organization uses it.

OG Image URLCopy Anchor Link

Enter a public HTTPS image URL for link previews.

Recommended practice:

• use a relevant landscape image;
• test the URL in a signed-out browser;
• use an image that can be redistributed on social platforms;
• check how it looks when cropped;
• avoid text-heavy artwork.

Canonical URLCopy Anchor Link

Use this only when your SEO owner has identified another URL as the preferred version of this content. Leave it blank for normal PageDesigner pages.

An incorrect canonical URL can tell crawlers to prefer a different page.

What PageDesigner outputsCopy Anchor Link

PageDesigner can render the configured description, keywords, Open Graph image, canonical link, and related title/URL metadata into the page head. Custom head HTML is separate and should not duplicate or contradict these fields.

Full pre-publish checklistCopy Anchor Link

Page recordCopy Anchor Link

• Title is clear and unique.
• Slug is short, stable, and conflict-free.
• Published is still off during review.
• Navigation visibility and order are intentional.
• SEO fields are complete.
• Custom Code has been reviewed.

ContentCopy Anchor Link

• No filler text, sample names, example prices, draft dates, or placeholder images.
• The main value and action appear early.
• Claims and prices match the current source of truth.
• Headings form a logical outline.
• Buttons use descriptive action labels.

Accessibility and responsive reviewCopy Anchor Link

• Desktop, tablet, and mobile are readable.
• Light and dark modes have sufficient contrast.
• Important images have meaningful alt text.
• Controls are easy to tap and operate.
• Interactive components work with keyboard and touch.
• No content overflows horizontally.

FunctionalityCopy Anchor Link

• Save reports Saved.
• Full Preview loads.
• Every link, button, linked image, and checkout CTA goes to the correct target.
• Video and interactive components work.
• External URLs work for a signed-out visitor.
• Optional theme integration is active where a component needs it.

LanguagesCopy Anchor Link

• Every supported locale was reviewed.
• Translation fallback is acceptable.
• Long translations fit mobile.
• Links still match the translated action.

Publish and verifyCopy Anchor Link

1. Save in the editor.
2. Open full Preview.
3. Complete the checklist.
4. Return to the page record.
5. Turn on Published.
6. Configure Show in Navigation and Navigation Order if needed.
7. Save the record.
8. Open View Page.
9. Verify the public page in a signed-out window and on a real mobile device when possible.

After publicationCopy Anchor Link

Schedule review for pages with:

• prices or product availability;
• seasonal offers and dates;
• policy or legal statements;
• staff and contact details;
• time-sensitive links;
• third-party embeds.

PageDesigner makes editing easier, but it does not know when business information becomes outdated.