tridim.sk

robots.txt is a small text file at yoursite.com/robots.txt where you tell visiting robots what they may read. Many sites carry an old rule that blocks ALL robots, which now also blocks the AI assistants your customers ask for recommendations.

ChatGPT, Claude, and Perplexity each send a named crawler (GPTBot, ClaudeBot, PerplexityBot). If your robots.txt turns them away, they cannot read your pages. So when a customer asks an assistant about your product, the assistant answers from what everyone ELSE says about you, or recommends a competitor it could read.

1. Open yoursite.com/robots.txt in a browser to see what you have today.
2. Look for "User-agent: *" followed by "Disallow: /". That single pair blocks everything, AI agents included.
3. Add an explicit allow block for each AI agent you want (GPTBot, ClaudeBot, PerplexityBot, OAI-SearchBot), placed after the wildcard rule so it wins.
4. The generated robots.txt in the Fix it section below has the exact lines for this site. Copy it, or merge the blocks into your existing file.

• After deploying, open yoursite.com/robots.txt and confirm the new blocks are live, not cached.
• Hit Re-scan above: "robots.txt allows AI agents" should flip to PASS.
• The free robots.txt checker at /tools/robots-txt-checker shows per-agent allow/block for your live file.

• Don’t delete rules you added deliberately. If you block a specific scraper for a reason, keep that block; just don’t let a blanket rule catch the assistants too.
• Allowing crawlers you actually want blocked just to raise a score is backwards. The score measures readiness for agents you WANT; decide the policy first, then express it precisely.
• Don’t serve a different robots.txt to different visitors. Inconsistent answers get you treated as unreliable by every crawler.

A sitemap is a machine-readable list (sitemap.xml) of every page on your site. It is how crawlers find pages that aren’t linked from your homepage.

Agents discovering your site crawl outward from the pages they know. Without a sitemap, anything not linked from a top-level page (docs, older articles, product variants) may simply never be read, so it can’t be quoted or recommended.

1. Most platforms generate one automatically: Next.js (app/sitemap.ts), WordPress (Yoast/Rank Math), Shopify and Wix (built in). Turn it on rather than hand-writing.
2. Add a "Sitemap: https://yoursite.com/sitemap.xml" line to robots.txt so crawlers find it.
3. Submit it once in Google Search Console and Bing Webmaster Tools for the search side.

• Open yoursite.com/sitemap.xml. It should list real page URLs, not error.
• Re-scan: "Sitemap present" flips to PASS.

• Don’t list URLs that redirect or 404. A sitemap full of dead links teaches crawlers to distrust it.
• Don’t include private or staging URLs; a sitemap is a public document.

HTTP responses can carry a Link header: the same canonical and alternate-language information your HTML declares, but delivered in the response envelope itself. Agents that only send a HEAD request, or that decide what to do while the page is still streaming, read the header without parsing any HTML. Yours is missing (or carries none of the relations agents use: canonical, alternate, describedby).

An agent triaging fifty URLs doesn’t want to download and parse fifty pages to learn which are duplicates of which. The Link header answers at the cheapest possible layer. Sites that provide it get correctly de-duplicated and correctly language-routed even by the most minimal fetchers.

1. Emit a Link header alongside each page, mirroring what your HTML head already declares. Example: Link: <https://yoursite.com/page>; rel="canonical".
2. Most stacks set this in one place: Next.js headers() config, an nginx add_header line, or a CDN response-header rule.
3. If you serve translations, add rel="alternate" entries with hreflang, matching your HTML.

• Run: curl -sI https://yoursite.com | grep -i "^link:" and confirm the relations appear.
• Hit Re-scan above: "Link response headers" flips to PASS.

• The header must AGREE with the HTML. A Link header pointing one place while the in-page canonical points another gives machines two contradictory answers, which is worse than one missing answer.
• Don’t inject the same site-wide canonical on every page via a blanket CDN rule; each page names its own clean URL, exactly as in the HTML tag.

Of everything your server sends for this page, very little is actual readable text. The rest is code, styling, and markup wrapper. Agents fetched a lot of bytes and found few words.

Agents work with retrieval budgets. A page that is 2% text either gets skimmed (and mis-summarised) or skipped. More signal per byte means more of your actual message survives into the agent’s summary.

1. Confirm your real copy is server-rendered. See the JavaScript check; these two usually fail together.
2. Cut boilerplate wrappers: deeply nested divs, inline SVG logos repeated per section, base64 images inlined into HTML.
3. Move large inline styles and scripts into external files.
4. Check how much of the document is inline script: your report now says. If most of it is, that is your framework serializing state for hydration, often a second copy of text already in the HTML. Send only the props a component cannot recompute, and render statically where a page does not need to hydrate.

• Re-scan: "Text-to-markup ratio" improves, and "Page weight" often improves alongside.

• Don’t pad the page with keyword text to inflate the ratio. The ratio is a proxy for substance, and stuffing is the opposite of substance.

Your page’s actual content (headlines, product info, pricing) only appears after JavaScript runs in a browser. Most AI agents read the raw HTML that arrives FIRST, and for your site, that first delivery is nearly empty.

An agent fetching your page gets the skeleton: navigation links, a footer, loading placeholders. It then summarises your business from a skeleton. Sites in this state get described as "this page contains little information" while the full pitch renders only for humans.

1. Server-render the content that matters: hero copy, value proposition, pricing, product details.
2. Next.js: use Server Components or static generation for marketing pages. Don’t fetch above-the-fold content in a client useEffect.
3. Quick self-test: view the page source (Ctrl+U shows the raw HTML, not the inspector) and search for your headline. If it isn’t there, agents don’t see it.

• Your headline and pricing appear in the raw page source.
• Re-scan: "Content without JavaScript" flips, and "Text-to-markup ratio" usually improves with it.
• The "What the agent receives" section below shows exactly what a no-JS agent gets from your page.

• Don’t serve a special pre-rendered version only to detected bots (cloaking). Agents compare notes with real user agents, and a divergence gets you classified as deceptive.
• Don’t paste an HTML copy of the content into a hidden div as a workaround. Duplicated content that drifts from the rendered version fails coherence in the ugliest way.