Publish llms.txt - Wialon

Overview

Site: https://wialon.com/ (Wialon, by Gurtam)
Source: GEO technical site audit, 1 September 2026, factor 2 of 7 - scored 0/10.

Finding, verified in a live browser session against the origin server:

• https://wialon.com/llms.txt returns HTTP 404 with content-type: text/html. It resolves to Wialon's branded 404 page ("404 We can't find the page you're looking for.").
• https://wialon.com/llms-full.txt - 404, same branded error page.
• https://wialon.com/.well-known/llms.txt - 404, same branded error page.
• https://www.wialon.com/ 301-redirects to the apex, so the www host serves no separate files and needs no separate copy.

No llms.txt or equivalent exists on the domain in any location.

A second reason, specific to this site's robots configuration: robots.txt applies a blanket Disallow: *? with a single carve-out for knowledge-base pagination. Blog pagination uses the same ?page= pattern and has no carve-out, so roughly 534 of 577 English blog posts have no crawlable internal path. Until that is fixed separately, llms.txt is one of the few signals that can point a model at content the link graph currently hides.

Your setup

Every row below was verified against the live site.

Critical implication of row 3: whatever mechanism already serves /robots.txt as text/plain at the root is the mechanism that should serve /llms.txt. This is not a new capability, and it should not require a new subsystem.

The five steps

01 Create the file

Plain-text file named exactly llms.txt, all lowercase. UTF-8, no BOM, Unix (LF) line endings. The content is Markdown, but the file extension and the served content type are both plain text.

Do not create this as a CMS page, a route in the application, or anything that renders through the site template. A templated page returns HTML wrapped in the Wialon theme, which defeats the entire purpose - and on this site it is exactly the failure mode already in place, since /llms.txt currently returns the branded 404 as text/html.

02 Place it at the document root

The file must resolve at https://wialon.com/llms.txt - root, not a subdirectory, not under a language prefix. Deploy it beside robots.txt and sitemap.xml using the same mechanism that already serves those two.

Do not create /en/llms.txt, /es/llms.txt or any per-language variant. The spec expects one file at the root. English is the reference language here and the file itself points at /en/ canonicals.

.well-known/llms.txt is not required and should not be used as the primary location.

03 Serve it as text/plain

The response must carry content-type: text/plain; charset=utf-8 and return HTTP 200. Match whatever rule already produces text/plain for /robots.txt.

Two failure modes to check for explicitly on this stack, because both are live behaviours of the current configuration:

• A catch-all route intercepting unknown root paths and returning the branded 404 template. This is what happens today.
• A CDN or edge rule rewriting unknown extensions, or serving the file as application/octet-stream, which triggers a download prompt instead of an inline response.

04 Reconcile with robots.txt

Three rules, all specific to this site's configuration:

• Never list a URL containing a query string. robots.txt blocks *? for every user agent. A query-string URL in llms.txt points a model at something it has been told not to fetch, which is worse than omitting it.
• Use /en/-prefixed paths for every entry except the homepage. Bare content paths 404 on this site. The homepage is the single exception: its canonical is https://wialon.com/.
• Do not add a Disallow for /llms.txt. It needs to be fetchable. The current rules do not block it; leave it that way.

Optionally add a Sitemap:-adjacent comment line in robots.txt noting the file's existence. This is not part of any spec and no crawler requires it, but it costs nothing and helps the next person who reads the file.

05 Verify

Covered in its own section below.

The file content

Every URL below was confirmed to return HTTP 200 with no redirect on 1 September 2026. Descriptions were drawn from the live pages, not written speculatively.

# Wialon

> Wialon is a fleet management and fleet digitalization platform developed by Gurtam. It is sold primarily to telematics service providers, system integrators and IoT startups who deliver fleet services to their own clients, rather than direct to fleet owners. Founded 2002. Over 4 million connected vehicles, 2,700+ partner companies, 160+ countries, and 4,100+ compatible GPS device models from 700+ manufacturers.

The Wialon product family consists of four solutions: Wialon Hosting (cloud), Wialon Local (on-premise), Wialon Platform (white-label solution builder) and Wialon Lite (lightweight cloud). Wialon is hardware-agnostic and integrates with most GPS device models on the market.

This file lists canonical English pages. Equivalent Spanish, French, Portuguese and Russian versions exist under /es/, /fr/, /pt/ and /ru/.

## Start here

- [Wialon homepage](https://wialon.com/): What Wialon is, the four-product suite, key functionality and the partner proposition.
- [About Wialon](https://wialon.com/en/about): Company history from 2002, scale figures, philosophy, awards and the relationship to Gurtam.
- [Wialon: the vehicle tracking and fleet digitalization system](https://wialon.com/en/vehicle-tracking-system): The flagship product page. Core capabilities, target buyer, mobile apps, integrations, and 15 answered FAQs.
- [Pricing](https://wialon.com/en/pricing): How pricing works across Wialon Hosting, Local, Lite and Platform, plus discount structures and data migration options.
- [Contact us](https://wialon.com/en/contacts): Offices in Vilnius (HQ), the USA, Dubai and Tbilisi, with sales, 24/7 support and press contacts.

## Products

- [Wialon Platform](https://wialon.com/en/platform): A solution builder that lets service providers create, brand and expand their own fleet products without an in-house development team.
- [Wialon Lite](https://wialon.com/en/lite): The lightweight cloud version covering essential fleet digitalization for lower-complexity operations.
- [Marketplace](https://wialon.com/en/marketplace): Third-party applications, customized solutions and integrations from the Wialon team and community.
- [Gurtam Maps](https://wialon.com/en/maps): The mapping layer used across Wialon products.
- [Custom Wialon integrations and solutions](https://wialon.com/en/soft-developers): Software developers building on the Wialon SDK and API, and what they deliver.

## Hardware compatibility

- [Integrated devices](https://wialon.com/en/gps-hardware): The hardware catalog hub. 4,100+ compatible GPS device models with live counts of connected and registered units.
- [Hardware manufacturers](https://wialon.com/en/hw-manufacturers): Catalog of 700+ telematics hardware manufacturers whose devices integrate with Wialon.
- [Vehicle trackers](https://wialon.com/en/gps-hardware/auto): Wialon-integrated GPS trackers for cars, trucks and commercial vehicles.
- [Asset trackers](https://wialon.com/en/gps-hardware/asset): Wialon-integrated trackers for non-powered assets and equipment.
- [Video telematics hardware](https://wialon.com/en/gps-hardware/video): Wialon-integrated dashcams and video telematics devices.
- [Personal trackers](https://wialon.com/en/gps-hardware/personal): Wialon-integrated personal and wearable GPS trackers.
- [OBD trackers](https://wialon.com/en/gps-hardware/obd): Wialon-integrated plug-in OBD-port tracking devices.

## Solutions by use case

- [Smart farming](https://wialon.com/en/agriculture-gps-tracking): Agricultural fleet operations and field-work control.
- [Delivery fleet management](https://wialon.com/en/delivery-fleet-management): Delivery operations, transportation arrangements and route planning.
- [Driver behavior monitoring](https://wialon.com/en/eco-driving): Scoring driver performance on speeding, harsh acceleration, braking and cornering to improve safety and cut costs.
- [Fleet maintenance management](https://wialon.com/en/fleet-maintenance-management): Planning, controlling and costing all maintenance activity.
- [Fuel monitoring system](https://wialon.com/en/fuel-management-system): Fuel flow visibility from filling station to vehicle tank, and misuse detection.
- [Public transportation management](https://wialon.com/en/public-transport-management): Stops, route optimization, vehicle distribution and schedule monitoring.
- [WiaTag employee GPS tracking](https://wialon.com/en/employee-gps-tracking): Turning a smartphone into a tracker for monitoring employees and assigning tasks.

## Knowledge base

- [Telematics fleet management 101](https://wialon.com/en/knowledge-base/telematics-fleet-management-101): Plain-language explanations of telematics fleet management for explaining the category to clients and staff.
- [What makes a great fleet management platform?](https://wialon.com/en/knowledge-base/choosing-fleet-management-platform): The selection criteria that matter most to fleets and to telematics service providers.
- [Top fleet management software compared](https://wialon.com/en/knowledge-base/top-fleet-management-software): Wialon compared against Geotab, Navixy, Samsara and Verizon Connect, by hardware support, market and business model.
- [Ready-made or custom fleet management software](https://wialon.com/en/knowledge-base/ready-made-or-custom-fleet-management-software): How to choose between an off-the-shelf platform and a custom build.
- [Fleet automation](https://wialon.com/en/knowledge-base/fleet-automation): How telematics providers build competitive, scalable automated fleet services.
- [Fleet risk management](https://wialon.com/en/knowledge-base/fleet-risk-management): The main fleet risks and how modern tooling prevents them, with real examples.
- [The benefits of eco-driving](https://wialon.com/en/knowledge-base/benefits-of-eco-driving): Eco-driving benefits for a fleet management business and the techniques behind them.
- [Logistics fleet management](https://wialon.com/en/knowledge-base/logistics-fleet-management): The key components of a logistics fleet management offering.
- [How APIs power integrated fleet management solutions](https://wialon.com/en/knowledge-base/how-apis-power-integrated-fleet-management-solutions): The role of APIs in connecting fleet management to ERP, BI and accounting systems.
- [Electric vehicle logistics](https://wialon.com/en/knowledge-base/electric-vehicle-logistics): EV logistics as an opportunity for telematics service providers.
- [Digitalization in agriculture](https://wialon.com/en/knowledge-base/digitalization-in-agriculture): EU progress and strategy on agricultural digitalization.
- [Knowledge base index](https://wialon.com/en/knowledge-base): All guides and analysis, organized into fleet management basics and fleet management insights.

## Proof and trust

- [Case study library](https://wialon.com/en/case-studies): Deployed Wialon projects by industry and region.
- [Security](https://wialon.com/en/security): ISO 27001:2017 certification, 99.5% SLA-guaranteed uptime and security practice.
- [Data center](https://wialon.com/en/datacenter): Tier-3 data center infrastructure across the US, Europe and beyond.
- [Technical support](https://wialon.com/en/techsupport): 24/7 support in five languages, and what is covered.
- [Technology partners](https://wialon.com/en/technology-partners): The technology partnership program and its participants.

## For partners

- [Find a Wialon partner](https://wialon.com/en/dealers): Partner map for locating a local Wialon provider.
- [Wialon community](https://wialon.com/en/community): The telematics and IoT professional community around the platform.
- [Get started with Wialon](https://wialon.com/en/request): Request form for becoming a partner or evaluating the platform.

## Optional

- [Blog](https://wialon.com/en/blog): Product updates, release notes, events and company news. Note: only the first page is reachable by internal links; the full archive is in sitemap.xml.

Verification

1. Status and content type.

curl -sI https://wialon.com/llms.txt

Expect HTTP/2 200 and content-type: text/plain. If you see text/html, the catch-all route is still intercepting.

2. Body.

curl -s https://wialon.com/llms.txt | head -20

Expect the Markdown, not an HTML document. If the first line is <!DOCTYPE html>, you are looking at the branded 404.

3. Encoding.

file llms.txt

Expect UTF-8 Unicode text, not with BOM and not with CRLF line terminators.

4. Every link resolves. Extract and test the URLs in one pass:

grep -oE 'https://wialon\.com[^)]*' llms.txt | sort -u | xargs -I{} sh -c 'printf "%s " "{}"; curl -s -o /dev/null -w "%{http_code}\n" "{}"'

Every line must end in 200. Anything returning 301 means a non-canonical form slipped in; anything returning 404 means a path changed since publication.

5. Not blocked. Confirm no Disallow rule in robots.txt matches /llms.txt, and that no entry in the file contains a ?.

6. In a browser. Load https://wialon.com/llms.txt directly. It should render as plain text in the window, not download, and not show the Wialon header and footer.

Maintenance note

llms.txt is not a set-and-forget artifact. Re-verify it whenever the site's URL structure changes, whenever a knowledge-base article is added or retired, and whenever robots.txt is edited. The two files are a pair: a change to the query-string rules or the language prefixes can silently invalidate entries here.

Review cadence: at minimum quarterly, and always as part of any release that touches routing, the language trees or the knowledge base. Re-run verification step 4 each time - it takes seconds and catches everything structural.

Checklist

• ☐ File named exactly llms.txt, lowercase, UTF-8, no BOM, LF line endings
• ☐ Deployed at the document root, beside robots.txt and sitemap.xml
• ☐ Returns HTTP 200 with content-type: text/plain; charset=utf-8
• ☐ Not rendered through the site template - no header, no footer, no branded 404
• ☐ No per-language copies created (/en/llms.txt and friends do not exist)
• ☐ Every URL uses the /en/ prefix, except the homepage, which is the bare apex
• ☐ No URL in the file contains a query string
• ☐ All URLs verified to return 200 with no redirect
• ☐ No robots.txt rule blocks /llms.txt
• ☐ Loads as readable plain text in a browser, with no download prompt
• ☐ Review date set for the next quarter