Technical SEO and AI search, one problem at a time
Each post takes one question people ask about their site, and answers it from the documentation of the people who decide it, Google, Cloudflare, the AI companies, and from audits we can show.
Which technical SEO issues are most important?
An audit lists hundreds of issues. How to sort them: what Google requires, templates instead of pages, then reach, effort and traffic, with a real report as the example.
Cloudflare’s AI bot settings, and five things to check
What the Search, Agent and Training settings block, the September defaults, the robots.txt Cloudflare writes, and a five-minute check.
How we write them
A post starts from a question we were asked or saw asked, and from what the people who decide the answer say about it themselves: Google’s documentation for search, Cloudflare’s for its settings, each AI company’s for its crawlers. Where they are silent, the post says so instead of guessing. Examples come from sites we can show, trakis.io itself or our demo shop, whose full audit is on the example page; a site we cannot name is left anonymous, and the post says so. Each post is dated and lists its sources.
More to read on Trakis
- Search Console statuses, explained: every status in the Page indexing report, with a guide for the ones people ask about most.
- The technical SEO checklist: the 66 checks behind an audit, each with why it matters and how to fix it.
- AI crawlers: which bot is which, what blocking each one costs, and a checker for your robots.txt.
- A free SEO audit report template, in Word and Excel, built like the reports Trakis sends.
Last changed 15 October 2026.