Frequently asked questions

Trilar is a website crawler that runs in the cloud. It checks a site the way Google does (technical SEO) and the way AI answer engines such as ChatGPT, Perplexity and Google AI Overviews read it (GEO and AEO), connects the results with Search Console, Analytics and server logs, and turns them into a prioritised action plan.

SEO makes sure search engines can crawl, understand and rank a site. GEO (Generative Engine Optimization) is about being cited as a source in AI-generated answers. AEO (Answer Engine Optimization) shapes content so that single sections answer a question directly and on their own, which is what answer engines quote. Trilar checks all three in the same crawl.

SEO agencies, in-house SEO and content teams, and developers who run websites with a few hundred to hundreds of thousands of pages and want to know what to fix first, for Google and for AI search.

Desktop crawlers are thorough tools that run on your own computer. Trilar runs on servers: crawls keep going when you close your laptop, large crawls do not depend on your RAM, schedules run without a machine left on, and results are shared by link. It also brings data sources (Search Console, GA4, CrUX, logs) and AI search checks together in one place. See our comparison pages for a fair side-by-side view.

No. Trilar runs in the browser. Crawls, rendering and analyses run on our servers.

Yes. Trilar renders pages in headless Chromium and compares the rendered result with the HTML the server delivers, so you see which content, links and tags only exist after JavaScript runs.

Yes. Trilar can log in through a login form, use cookies you provide or send custom headers, for example a service token for a protected staging environment. Logout links are skipped automatically. Use a test account for this.

Plans cover crawls of up to one million URLs. Crawl speed is set per site and adapts to the server: Trilar slows down on errors or slow responses so your website is never put under strain.

Yes, by default Trilar follows robots.txt for the user agent you choose. You can test robots.txt rules against any URL and user agent, and allow specific paths for an audit of your own site.

Trilar identifies itself as Trilarbot; you can also crawl as Googlebot smartphone or desktop, or with a custom user agent. If your firewall or bot protection blocks crawlers, see the Trilarbot page for how to allow it.

Yes. Besides crawling from a start URL or a sitemap, Trilar crawls URL lists. For migrations it checks a redirect mapping (old URL, expected target): target reached, redirect chain, error or wrong target.

Yes. A crawl can fetch every page with a mobile and a desktop user agent, and Trilar shows where the two versions differ.

Google Search Console (clicks, impressions, positions and queries per URL, compared with the previous period), Google Analytics 4, Core Web Vitals from the Chrome UX Report and PageSpeed Insights. Search Console can also be connected through a service account, without sharing your Google login.

Yes. Through a log integration we set up with you, Trilar imports verified bot requests per URL from your server logs, so you see which pages Googlebot and AI crawlers actually fetch, and which important pages they never visit.

Trilar compares Search Console data with the previous period and assigns lost clicks to a cause: lost rankings, a redirect, a page that disappeared or no longer indexable. It also flags redirects that point to a target that does not match the old page.

Every view exports to CSV and Google Sheets. Reports are shared with a link that works without a login, sent as PDF by e-mail after scheduled crawls, and tasks export as Markdown or CSV for your ticket system. There is also an API with keys for automation.

Yes, daily, weekly or monthly. Each run is compared with the previous one; you get an e-mail with the report and a webhook to Slack, Teams or tools like Make and Zapier, optionally only when something got worse.

Trilar asks an AI model with live web search your important search queries, the way AI search engines answer them, and records whether your site is cited, at which position, and which domains are cited instead. Results are stored, so you can follow the trend over time.

For every query where your site was not cited, Trilar names the page that should have been cited, its best matching section, the words of the query that section lacks, and a verdict: page missing, section missing, section too weak, or section good (then authority and competition decide).

Answer engines quote sections, not whole pages. Trilar splits every page at its headings and scores each section: length, whether the first sentence names the topic and stands on its own, concrete facts and numbers, and direct answers to question headings.

Trilar finds the organisations, brands and shops in your structured data and matches them with Wikidata. Where a match exists but your sameAs links do not point to it, you get the Wikidata and Wikipedia links to add, so search engines and AI tie your pages to the right entity.

Without AI, Trilar checks the trust signals of the whole site: imprint, contact, about and privacy pages, the organisation in your schema, and per page author, date, author profiles and editorial review. On request, an AI model rates single pages for experience, expertise, authoritativeness and trust, with evidence from the text and concrete fixes.

Trilar uses Claude by Anthropic through its commercial API. AI features only run when you start them, and results are stored with the crawl so you do not pay twice. Anthropic does not use API inputs to train its models by default. Everything else, from the crawl to the action plan, runs without AI.

Trilar is in early access. Plans are based on the number of crawled URLs per month plus credits for AI features. Write to us and we will set up access and discuss the right plan.

Crawl data and account data are stored in Europe. Each crawl lives in its own database, separate from other customers.

Crawls are kept according to your plan; for scheduled crawls you choose how many runs to keep. Deleted crawls are removed completely.

Yes. Crawls, saved views, segments and shared reports are available to your team; reports can be shared with clients by link without an account.

By e-mail at support@trilar.io or by phone at +41 76 77 99 820. We answer in English, German and Spanish.

Yes. In early access we set up your account and go through the first crawl and the action plan with you.

Trilar detects challenge pages and bot protection and tells you so. Allow the Trilarbot user agent (or crawl with a custom header your firewall accepts); the Trilarbot page explains how.