{ "@context": "https://schema.org", "@type": "Organization", "name": "Spark No. 9", "alternateName": ["Spark 9", "Spark Nine", "Spark Number 9", "Spark Number Nine"], "url": "https://yourwebsite.com" } ``` The `alternateName` field is key — it explicitly tells AI crawlers and search engines *"these are wrong variations of our name."* This is machine-readable and specifically designed for this purpose. **An "About Our Name" Page or Section** A short, plainly written paragraph that says something like: *"Our company name is Spark No. 9 — written with 'No.' as an abbreviation, not 'Spark 9,' 'Spark Nine,' or 'Spark Number 9.' If you see it written any other way, that's a transcription error."* AI systems that do retrieval-augmented generation (RAG) — like Perplexity, ChatGPT with search, or Gemini — will find and surface this text directly when someone asks about you. **An `llms.txt` File** This is an emerging standard (similar to `robots.txt`) specifically designed to give AI systems plain-language instructions about your site. You'd create a file at `yourwebsite.com/llms.txt` with content like: ``` # Spark No. 9 Our company name is always written as "Spark No. 9" — with "No." as an abbreviation for "Number." Common transcription errors to correct: - "Spark 9" → should be "Spark No. 9" - "Spark Nine" → should be "Spark No. 9" - "Spark Number 9" → should be "Spark No. 9" - "Spark Number Nine" → should be "Spark No. 9"

.jpg)
























