Guides: getting seen by AI

• Connect Claude to your Hilyt profile and let it keep your page current — Hilyt has a remote MCP server, so Claude can read your profile, propose updates from what it already knows about you, and publish only what you confirm. Setup takes one URL. (2026-08-04)
• How to add llms.txt to a Next.js site — Put llms.txt in the public directory and Next.js serves it at your site root in both routers. When content changes often, a route handler generates it instead. (2026-08-03)
• How to add llms.txt to a Squarespace site — Squarespace 7.1 publishes llms.txt natively — SEO Settings, LLMS.txt tab, paste and save. On 7.0 you need a URL-mapping redirect. Both routes, with checks. (2026-08-03)
• How to add llms.txt to a Webflow site — Webflow serves llms.txt natively — upload the file in your site's SEO settings and it appears at your domain root. Fallbacks: a 301 redirect or a Worker. (2026-08-03)
• How to add llms.txt to a WordPress site — Put a file named llms.txt in your WordPress root folder — the one with wp-config.php — via SFTP or your host's file manager. No plugin needed. Starter inside. (2026-08-03)
• AI crawler user agents: the full list (GPTBot, ClaudeBot, PerplexityBot and more) — The current AI crawler user agents — GPTBot, ClaudeBot, PerplexityBot, Google-Extended, Applebot and more — what each does and whether it obeys robots.txt. (2026-08-03)
• AI keeps confusing you with someone else — how to disambiguate — AI mixes people up when nothing machine-readable separates them. A canonical URL, Person JSON-LD with sameAs links and consistent bios fix retrieval confusion. (2026-08-03)
• An AI-readable profile for consultants — When a buyer asks an AI assistant who can help in your niche, it shortlists from pages it can read. How a consultant becomes findable and verifiable then. (2026-08-03)
• An AI-readable profile for freelance developers — GitHub proves you can code, not that you are for hire. What a developer's AI-readable profile adds: plain-text stack, availability, rates posture and contact. (2026-08-03)
• AI visibility for job seekers: how recruiters' AI tools see you — Two machines read job seekers: ATS parsers scanning the CV you submit, and AI assistants searching your name. How to be readable by both and not misread. (2026-08-03)
• How to become an entity AI models recognise — An entity is a thing machines can identify consistently across sources. Build one with a canonical URL, one bio everywhere, Person JSON-LD and sameAs links. (2026-08-03)
• Can AI read your Notion page, Substack, Medium — or your PDF CV? — GitHub, Substack and Framer serve HTML that AI can read. Public Notion pages are JavaScript shells, Medium blocks AI crawlers, and a PDF CV needs a web page. (2026-08-03)
• Can ChatGPT read your LinkedIn profile? — No, not reliably. LinkedIn requires login for most profile views and blocks crawlers, so assistants see at best fragments cached by search engines. (2026-08-03)
• ChatGPT says something wrong about you — how to fix it — Wrong ChatGPT answers come from stale training data or bad sources it reads live. You cannot edit model weights, but you can fix the sources today. (2026-08-03)
• Cloudflare is blocking AI crawlers on your site — how to check and fix it — Cloudflare defaults many zones to blocking AI crawlers two ways — a managed robots.txt override and edge-level UA blocking. Check both under Security and Bots. (2026-08-03)
• Do you need a Wikipedia page for AI to know who you are? — No — Wikipedia helps when you qualify, but almost nobody does. AI builds its picture of you from the open web: your site, consistent bios, structured sources. (2026-08-03)
• Generative engine optimisation (GEO), explained — GEO is optimising to be cited in AI-generated answers. The foundations are still SEO; what changes is extraction, entity identity and zero-click wins. (2026-08-03)
• How to get your business cited by AI assistants — When ChatGPT or Claude recommends companies, it quotes pages it can read and verify. Most small-business sites fail that test on defaults alone. Here is the fix, layer by layer. (2026-08-03)
• How AI assistants decide which sources to cite — AI assistants cite sources found through live retrieval — search, fetch, extract, synthesise. What each stage rewards, and what disqualifies a page. (2026-08-03)
• How to add yourself to Wikidata (and whether you should) — Wikidata's bar is lower than Wikipedia's but not zero. Items need serious public references or a structural need; self-created items that lack them get deleted. (2026-08-03)
• How to check what AI says about your brand (free, in ten minutes) — Ask each assistant the questions your customers ask, with browsing on and off, and record the citations. A free checker automates the technical half. (2026-08-03)
• How to create an AI-readable profile of yourself — Publish one open, server-rendered page at a stable URL: your name, what you do, dated facts, Person JSON-LD and sameAs links. Here's the full build. (2026-08-03)
• How to get cited by Perplexity — Perplexity builds every answer from live search results and cites by design. Be crawlable by PerplexityBot, get indexed, and answer questions directly. (2026-08-03)
• How to get seen in ChatGPT — the mechanics, not the myths — When someone asks ChatGPT about you, it searches the web and reads what it can. Here is what it can actually read, what it ignores, and the shortest path to being in the answer. (2026-08-03)
• Indexed by Google but invisible to AI? Here is why — Googlebot renders JavaScript and most AI crawlers do not, so Google indexing proves little about AI readability. Three checks reveal which problem you have. (2026-08-03)
• LLM SEO for your personal brand — what works and what is snake oil — A working list of what actually influences how AI systems describe you, and the growing pile of tactics that do nothing. Written from building an AI-visibility checker and watching real results. (2026-08-03)
• How to make your startup findable by AI assistants — AI models have never heard of a new startup, so live retrieval is the only path: buyer-language copy, Organization JSON-LD with a founder, and corroboration. (2026-08-03)
• Person schema markup: a copy-paste JSON-LD example — A complete ProfilePage and Person JSON-LD example you can copy, where the script tag goes, Person vs ProfilePage, and what AI systems do with it. (2026-08-03)
• How to add Person schema to WordPress without a plugin — Hook wp_head from a child theme or snippets tool and print Person JSON-LD on your front and about pages only. Complete PHP included — no SEO plugin needed. (2026-08-03)
• Preparing your site for AI agents — AI agents fetch, parse and compare — no persuasion, only extraction. Server-rendered HTML, JSON-LD, llms.txt and stable URLs are what readiness means today. (2026-08-03)
• robots.txt rules for AI crawlers, explained — robots.txt controls AI crawlers per user-agent. How to allow GPTBot, why training and answer-time agents need separate rules, and what blocking does. (2026-08-03)
• Semantic HTML for AI readability: the markup that makes you legible — Most AI crawlers read raw HTML and never run JavaScript. Semantic HTML — real headings, paragraphs and lists in the source — makes a page legible. (2026-08-03)
• What does ChatGPT actually see when it looks you up? — Two paths: what's baked into the model's training, and what live search retrieves right now. Only open, server-rendered pages make it into the second. (2026-08-03)
• What is llms.txt — and how to write one (with a full example) — llms.txt is a proposed plain-markdown index at your site root that tells AI systems what your site contains. How to write one, with a full example. (2026-08-03)
• Why doesn't ChatGPT recommend your business? — ChatGPT recommends businesses it can read and corroborate. If it cannot fetch your site or find third-party evidence, it recommends a competitor it can. (2026-08-03)
• How to check whether AI can actually read your website — Six checks that decide whether ChatGPT and Claude can see your site at all — each one testable by hand in a minute, or all at once with our free checker. (2026-08-01)
• JS shells and soft 404s: how your site lies to crawlers — Our own site scored 41/100 on its own AI-readability test. A first-hand tour of the two failure modes that make modern sites invisible — and how we fixed ours at the edge. (2026-08-01)
• llms.txt for people: what it is, and an honest take on whether it matters — A plain-text index that tells AI systems what's on your site. Adoption is early and unproven — here's why we ship it anyway, and what an llm.txt card for a person looks like. (2026-08-01)
• Person and Organization schema that AI actually uses — The JSON-LD identity mistakes that make models misdescribe you — including the url-versus-sameAs error we shipped ourselves before catching it. (2026-08-01)
• Why LinkedIn can't get you cited by AI — The most complete professional profile you own sits behind a login wall — which means the AI tools people now ask about you have never read it. (2026-08-01)
• How does Claude know who a person is? — Written with Claude, about Claude: what actually makes a person legible to an AI model, why LinkedIn is invisible to it, and what to do about it. (2026-07-22)

hilyt.it · Directory