Systems

Machine-readable files that govern how search engines, AI systems, and crawlers interact with the Visualist site. Not visitor-facing. Maintained by the product team and updated whenever site structure or positioning changes.

H2 · Systems

H2

Systems files

Off-nav AEO

Three files live at the root of visualistapp.com and are never linked in the main navigation. They are maintained by the product team and updated whenever the site structure, positioning, or page inventory changes significantly.

sitemap.xml

An XML file listing every indexable URL on visualistapp.com with its last modification date. Search engines use it to discover and prioritize pages for crawling. It is the definitive record of what pages exist and when they were last updated.

Located at: visualistapp.com/sitemap.xml

Updated on every publish. When a page is added, retired, or significantly updated, the sitemap is regenerated. Stale sitemaps actively harm crawl efficiency.

Only indexable pages. noindex pages, confirmation pages, and /offers/ and /partners/ campaign pages are excluded.

Submitted to Google Search Console and Bing Webmaster Tools on initial launch and resubmitted whenever the sitemap changes significantly.

robots.txt

A plain text file that tells web crawlers which parts of the site they are allowed to crawl. It is not a security mechanism: it is a directive that well-behaved crawlers follow. Malicious crawlers ignore it.

Located at: visualistapp.com/robots.txt

Allow all by default. The default directive is Allow: /. Only specific paths are disallowed where there is a clear reason.

Disallow paths with no public value. Admin paths, internal tooling, staging environments, and confirmation pages are disallowed. Campaign pages that should be noindex are handled at the page level, not via robots.txt.

Sitemap reference included. The robots.txt file includes a direct reference to the sitemap URL so crawlers can find it without needing to know the location.

llms.txt

A plain language file that tells AI systems what Visualist is, who it is for, and which pages are most authoritative. AI systems that consult llms.txt before crawling receive structured guidance on how to represent Visualist in answers. It is Visualist's direct communication channel with AI-powered search.

Located at: visualistapp.com/llms.txt

What it must contain. A plain language description of Visualist (two to three sentences using the approved positioning language). Who Visualist is for (the three verticals, named). The primary claim. A list of the most authoritative pages for product truth, ordered by importance: Changelog, Product pages, Solutions pages, Homepage.

Updated when positioning or structure changes. If the primary claim changes, if new verticals launch, or if major new product areas go live, llms.txt is updated the same day. It must always reflect the current Visualist positioning, not the version from six months ago.

Written in plain language, not JSON or XML. llms.txt is read by AI language models, not by parsers. Write it as you would write a briefing document: clear sentences, no markup.

Founder-reviewed before every update. The llms.txt file contains Visualist's positioning claims in their most distilled form. No agent updates it without Founder sign-off. It is the most consequential 200-word document on the site.

llms.txt is to AI search what robots.txt was to Google in 2003: an early-stage convention that the most sophisticated actors already follow and that will become standard practice. Visualist maintains it from day one.