Machine-readable by design
The most machine-readable agency site in its industry.
We sell AI visibility. Our own site is the proof: every fact about WikiBusines — services, prices, policies, people — is published in formats a machine can read in one request, under terms it can verify.
The inventory
What machines get here
Fourteen surfaces, each one live. Every link below resolves to a real file or a real page on this domain — click any of them and read what the crawlers read.
/robots.txtAn open door for crawlers
Explicit welcome for 20+ AI and search crawlers — GPTBot, ClaudeBot, PerplexityBot, Google-Extended, Baiduspider, YandexBot and the rest — allow-listed by name, not buried under a wildcard.
Open the live file →/llms.txtThe short profile
Who we are, what we sell, canonical service URLs and pricing anchors in one small file — the first thing an LLM should read about us.
Read llms.txt →/llms-full.txtThe full profile, one request
Roughly 48 KB covering every service, every price, the FAQ and the complete blog index. A model gets the whole company without crawling a single HTML page.
Read llms-full.txt →/entities.jsonA public entity graph
A schema.org graph of the organization, its services and its people — our own Wikidata-style public record, served from our own domain.
Open the entity graph →/pricing.jsonThe price list, normalized
Every public price as structured data — EUR amounts, floors versus fixed prices, one entry per service — generated from the same data files that render the pricing pages.
Open the price list →/services.jsonThe service catalog
The full service registry — names, descriptions, canonical URLs and pricing anchors — exported as one JSON file from the same registry the site renders from.
Open the catalog →/offers.jsonOffers, schema.org-shaped
A schema.org OfferCatalog of every public offer — services with public floors and fixed-price products — ready for any parser that already speaks schema.org.
Open the OfferCatalog →/datasets/index.jsonA dataset registry
An index of the open datasets we publish — what each file contains, where it lives and under what license — so the data is discoverable, not buried in blog posts.
Browse the registry →/.well-known/tdmrep.jsonTDM policy, machine-checkable
A TDM Reservation Protocol file stating that text-and-data-mining of this site is explicitly permitted. Crawlers do not have to guess our stance; they can check it.
Check the TDM file →/rss.xmlThe blog, syndicated
An RSS 2.0 feed of all 80 blog essays with full excerpts, newest first — regenerated on every deploy, also served at /blog/rss.xml.
Subscribe to the feed →/sitemap.xmlEvery URL, both languages
153+ URLs with hreflang pairs linking the English pages and their Ukrainian mirrors, so nothing on this site has to be discovered by accident.
Open the sitemap →/content-licenseAn open content license
Our guides and marketing copy are free to read, index, quote and train on — with attribution to WikiBusines. The terms are written down, not implied.
Read the license →JSON-LD, per pageStructured data everywhere
Service, FAQPage, BreadcrumbList and Article markup embedded on the pages where it applies — machines parse facts from the page itself, no scraping heuristics required.
See it live on the FAQ →/downloads/*.pdfWorking documents as files
The checklists behind our guides — the notability checklist, the first-90-days plan, the vendor scorecard — as plain, linkable PDFs.
Download the notability checklist →The reasoning
Why we open our data
AI assistants answer questions about a company with whatever record exists. We would rather the record be ours.
When someone asks ChatGPT, Gemini or Perplexity about WikiBusines, the answer is assembled from whatever the model trained on or retrieved. A company can leave that record to chance — fragments, third-party summaries, stale caches — or it can publish the canonical version itself. We keep ours accurate, complete and free to read.
Training and retrieval are welcome here, with attribution. The exact terms are public in our content license. If a model quotes our prices, we want them to be our actual prices; if it describes our guarantees, we want it describing the real ones.
$ curl -s https://www.wikibusines.net/llms.txt
# WikiBusines — LLM-readable summary WikiBusines is a trust-infrastructure and AI-visibility company. We help companies, founders, agencies, and public figures build reliable presence across Wikipedia, Wikidata, Reddit, Quora and other high-authority knowledge platforms. Full machine-readable profile (all services, prices, FAQ, blog index): https://www.wikibusines.net/llms-full.txt
Excerpt from the live file, reflowed for display — fetch it yourself.
Audited June 2026
We checked the rest of the industry
The claim in the headline is specific, so we tested it before making it.
In our June 2026 audit of 10 leading Wikipedia and online-reputation agency sites, none shipped an llms-full profile, a TDM policy file, or a public entity graph — most do not even ship llms.txt.
Small print: machine-readable signals are not rankings, and none of these files makes an AI system cite us. What they do is make reading this site cheap and unambiguous — the same discipline we apply to client entities through Wikipedia AEO and Wikidata & Knowledge Graph work.
Honest framing
What this layer does — and does not do
Machine-readability is plumbing, not magic. Here is the sober version of what these fourteen surfaces buy us.
- Gives crawlers, agents and retrieval systems a canonical, always-current briefing — generated from the same data files that render this site.
- Declares licensing and TDM permissions unambiguously, so a machine checks our terms instead of guessing them.
- Makes our offers machine-comparable — normalized prices and a schema.org OfferCatalog instead of scraped marketing copy.
- Speeds discovery: new and changed URLs are pushed to search engines via IndexNow rather than waiting to be crawled.
- Act as a ranking hack — Google's own guidance says llms.txt-style files are not needed for AI Overviews or AI Mode, and visibility still rides ordinary Search ranking and content quality.
- Guarantee citations — no file makes an AI system quote us; answer engines decide for themselves what to retrieve and cite.
- Change Google Search treatment via Google-Extended — allowing it affects Gemini training and grounding, not Search inclusion or ranking.
Permissions at a glance
What machines may do with this site
The one-screen summary of our content terms. The formal, binding version is the content license.
For the formal terms — attribution requirements, scope and exclusions — read the content license.
Want your record this readable?
We apply the same discipline to client entities — canonical facts, structured data, and the sources machines actually trust. Start with an assessment of what AI currently says about you.