Proxylang website translation

Reviewed 1d ago.

• tools: 6 tools scanned
• metadata: scanned

No findings.

Tools (6)

• proxylang_start

  Set up Proxylang on a website with no signup: returns the script tag, install steps for the site's platform, an agent_token for the other tools, and claim_url (sent once; save it). If the user named a language, use it; otherwise pick the one their customers most likely speak and say why. The free trial shows the first language; list other recommended languages after it.

• proxylang_check

  Is the Proxylang tag on the live site, and have words been translated? If words_translated is 0, a real browser visit to preview_url is needed first.

• proxylang_next

  Returns message_for_user: the message to end setup with (the site works, the link to keep it, and only the Proxylang features that fit this site). Show it as it is, in the user's language, with <claim_url> replaced by the saved claim_url.

• proxylang_status

  Free words left, trial expiry, and whether the user claimed or paid.

• proxylang_change_site

  Use when the trial was started for the wrong website (action "move": the old site stops), or the tag must also work on a test or staging site (action "add": both work). Same agent_token, script tag, claim_url and free words; all sites share one limit. Not needed for localhost: use localhost_script_tag.

• proxylang_style

  Restyle the language menu so it looks like part of the site. Read the site's brand color, background, text color, button roundness and dark mode first, then send only the fields to change in `style`. Colors: #hex, rgb(), hsl() or a CSS color name; each has a Light and a Dark version. Full field list: https://proxylang.dev/agents.md step 7.