How Polestar Protects Customer Trust With US Sales Banned

Polestar's announcement that it cannot sell new cars in the United States but will continue honoring warranties and parts orders underscores a shift in how the brand will interact with U.S. customers online. For website owners, this means a sudden surge in service‑related traffic—customers will be searching for warranty claims, parts availability, and support rather than new‑vehicle inventory. The change also raises the likelihood of automated bots probing Polestar’s support pages for scraped warranty information or to generate fraudulent service requests. Because Polestar’s U.S. sales are halted, any AI‑driven recommendation engines or chatbots that previously promoted new models must be re‑configured to focus solely on post‑sale assistance, or they risk violating Polestar’s updated compliance stance. **Actionable tips:** 1. **Update your llms.txt** to explicitly list Polestar’s support URLs (e.g., `/support/*`, `/warranty/*`) as allowed endpoints for trusted AI bots, while blocking crawling of any discontinued sales pages. 2. Deploy a bot‑detection layer that flags high‑frequency requests to parts‑lookup APIs; route suspicious traffic to a CAPTCHA or rate‑limit it to protect warranty data. 3. Use llms.txt “User‑Agent” directives to whitelist only your own customer‑service LLMs, preventing third‑party scrapers from harvesting warranty terms that could be misused.