starwinelist.com

Can AI crawlers find and read your site at all? These signals tell language models where your content lives and that they are welcome to read it.

• ✗ llms.txt present
  ?

  What: a /llms.txt that describes your service for AI crawlers. Why: it helps language models understand what you do and cite you correctly (like robots.txt, but for AI).
  
  Add an llms.txt that describes your service for AI crawlers.
  llms.txt (place at {base_url}/llms.txt) Copy

  # Starwinelist
  > One-line summary of what Starwinelist does and who it is for.
  
  https://starwinelist.com
  
  ## Key pages
  - [Home](https://starwinelist.com/): what Starwinelist offers, in brief
  - [About](https://starwinelist.com/about): who Starwinelist is
  - [Contact](https://starwinelist.com/contact): how to get in touch
  
  ## Notes
  Written for AI assistants: plain facts about Starwinelist, kept current.

• ✓ robots.txt present
  ?

  What: a /robots.txt that controls what crawlers may read. Why: without it, important pages can be missed or the wrong pages indexed.
• ✗ sitemap.xml present
  ?

  What: a /sitemap.xml listing your pages. Why: crawlers and AI find your whole structure so nothing important is missed.
  
  Publish a sitemap.xml so your content is found.

Machine-readable facts about who you are and what you offer. The clearer your structured data, the more accurately AI can understand and describe you instead of guessing.

• ✗ Structured data (JSON-LD)
  ?

  What: JSON-LD describing your company and products in a machine-readable way. Why: AI uses it to understand what you are and describe you correctly.
  
  Add schema.org JSON-LD (Organization/Product/FAQ).
  Organization schema (JSON-LD) Copy

  <script type="application/ld+json">
  {
    "@context": "https://schema.org",
    "@type": "Organization",
    "name": "Starwinelist",
    "url": "https://starwinelist.com",
    "logo": "https://starwinelist.com/logo.png",
    "description": "One or two plain sentences describing what Starwinelist does and who it is for.",
    "sameAs": [
      "https://www.linkedin.com/company/your-company"
    ]
  }
  </script>

• ✗ FAQ / questions and answers
  ?

  What: an FAQ with clear questions and answers. Why: it matches how people ask AI - models often lift answers straight from well-structured FAQs.
  
  Add an FAQ that answers buyer questions (ideally with FAQPage schema).
  FAQ schema (FAQPage JSON-LD) Copy

  <script type="application/ld+json">
  {
    "@context": "https://schema.org",
    "@type": "FAQPage",
    "mainEntity": [
      {
        "@type": "Question",
        "name": "What does Starwinelist do?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Answer in one or two plain sentences a model can quote directly."
        }
      },
      {
        "@type": "Question",
        "name": "Who is Starwinelist for?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Describe your ideal customer in plain language."
        }
      }
    ]
  }
  </script>

The plain, static content AI actually reads. Clear titles, headings and descriptions in the page source mean models read what you do instead of an empty shell.

• ✗ Canonical URL
  ?

  What: a canonical URL points to the 'real' address when the same content lives on several URLs. Why: it stops your visibility being split across duplicates.
  
  Set a canonical URL on each page.
• ✗ Open Graph tags
  ?

  What: Open Graph tags (title/image/description) control how the page looks when shared. Why: they give AI and social media a clear, correct summary.
  
  Add OG tags for sharing and previews.
• ✓ Meta description
  ?

  What: the page's short summary. Why: search engines and AI use it to describe you - a good description means you are described the way you want.
• ✓ Page title
  ?

  What: the page title. Why: it is the first thing AI and search engines read - a clear title with what you do helps you get named in the right context.