Most AI SEO advice is unproven. We tested what ChatGPT, Claude, and Perplexity actually read on our own site. Six LLM visibility techniques that worked, eight that didn't, and the metrics to tell the difference.

The RubyLA blog offers insights, tutorials, and community updates for Ruby developers in Los Angeles and beyond. Developers can explore Ruby language features, web development frameworks, and best practices for building Ruby applications. Additionally, the blog covers Ruby meetups, events, and job opportunities in the Los Angeles area, fostering collaboration and networking within the local Ruby community.

RUBYLAND

A practical guide to making websites readable by LLMs and AI agents, based on real-world testing on evilmartians.com. Six techniques are ranked by impact vs. effort: creating an llms.txt file, serving .md routes for every page, adding <link rel="alternate"> tags and HTTP Link headers, using a visually hidden div hint for conversational AI, publishing llms-full.txt, and implementing Accept: text/markdown content negotiation. The post also debunks eight popular but ineffective AI SEO techniques (including meta tags with no spec, HTML comments, User-Agent sniffing, and JSON-LD for LLM visibility), citing a Princeton/IIT Delhi GEO study showing only enriched visible text improves AI visibility. Honest caveats are included: major LLM crawlers don't yet fetch llms.txt or .md files unprompted, so the primary value is in human-initiated AI interactions. Measurement via server-side analytics tracking User-Agent and referrer is recommended.

Making your site visible to LLMs: 6 techniques that work, 8 that don't—Martian Chronicles, Evil Martians’ team blog

1. What is llms.txt and why does every site need one?

2. Why are .md routes the thing that actually matters?

3. How do LLMs discover your Markdown version? <link> tags and HTTP Link headers

4. What about when someone just pastes your URL into ChatGPT?

OK, how do you know any of this is working?