Sitedex

@Orangek21865157 llms.txt is protocol theater. context needs to be relevant.

Hot take: Most "AI SEO" advice is backwards. People ship llms.txt first. Meanwhile robots.txt, Cloudflare, or host-level rules are quietly blocking the bots. No crawl = no citation. The real order: access -> discovery -> context Almost everyone starts with the last step.

@launchwitharyan @framer Why not generate your own for free, based on your site content? sitedex.dev/llms-txt

@framer can you add native support for /llms.txt? Right now it's locked behind the Pro plan via redirects, which means Basic plan users can't do proper AEO optimization. A lot of simple sites run on Basic. This shouldn't be a paid feature.

@anitakirkovska @nextjs @sanity_io You can automate agentic discovery quite a bit, too. For example, you can autogenerate your llms.txt and semantic search through Sitedex. app.sitedex.dev/sites/vellum.ai

We officially churned off of Webflow and saved $30k/year Now, our whole website runs on @Nextjs + @sanity_io Our marketing team ships updates in minutes It wasn't an easy journey, here's what we did & the path ahead 👇🏻

@TTrimoreau GitHub right?

Name a tech company that literally nobody hates

@asaio87 Not really. Local models get handily beaten in my testing for complex stuff. For simple things, they are more than enough.

Local AI models are starting to get a lot of traction I have read somewhere local models are at least 97% the same as the mainstream cloud models

@sandislonjsak @levelsio @marclou @theo @jackfriks @ChShersh @robj3d3 @icanvardar @bruvimtired @yacineMTB @Ahmekal @forgebitz @JanuBuilds @dhh @FrancescoCiull4 @enjojoyy @SoraiaDev @maks6361 Strong list!

20 must follow accounts if you build software: - @levelsio - @marclou - @theo - @jackfriks - @ChShersh - @robj3d3 - @icanvardar - @bruvimtired - @yacineMTB - @Ahmekal - @forgebitz - @JanuBuilds - @dhh - @FrancescoCiull4 - @enjojoyy - @SoraiaDev - @maks6361 - @eliana_jordan - @razvanmuntian - @itsolelehmann

@KaiCromwell Plus it increases the likelihood of AI getting a real answer from your site. Too many people have junk that offers no new insights.

Deleted all the one-shot prompt AI blogs and published 10 AI + human written blogs. Humanization is worth the time investment.

@MerlinEgalite Here are some suggestions: app.sitedex.dev/sites/morpho.o…

A lot of small teams are reaching out to get advice on how to build on Morpho. Most of the Morpho team is currently under water but i'd still like to support them in a way that is scalable. Wdyt is missing in Morpho's doc so they have all the necessary tools to keep building?

@mattyp @NousResearch @Teknium Honestly, I refuse to use tools that are not agent friendly. If my agent can't Q/A your product, I dont want to use it.

. @NousResearch & @Teknium a very simple way to get more people using Hermes is to spend some time on your docs: - Agent unfriendly (No llms.txt / llms-full.txt) - Unclear product story - No deployment path - Overwhelming navigation structure Could be 1000x easier to get started

@esimitkarlgusta Wow, amazing job. Collab Tower is very agent friendly. app.sitedex.dev/sites/collabto…

Added llms.txt on Collab Tower. There has been a lot of hype as to it being the future for LLMs to use to understand your site. I saw Product Hunt have it too on their site.

@ajaydsouza @vapvarun @SybreWaaijer llms.txt is generally a fallback. Most LLMs fetch the main site, and in case they can not get answers, fallback on llms.txt That's why we focus on AI-friendly content rather than protocol tooling.

@vapvarun Are you seeing calls to llms.txt ? I recall a post by @SybreWaaijer on some tests he ran where llms.txt was never called.

Most WordPress sites still return: 404 → /llms.txt That’s becoming the AI-era equivalent of missing sitemap.xml. We’ve now shipped llms.txt patterns across ~30 WordPress and static sites: • Blogs • WooCommerce stores • EDD plugin catalogs • Astro static builds The interesting part: AI assistants don’t want all your URLs. They want a curated, machine-readable index of the pages worth citing. This article covers: → Rank Math + Yoast setups → Cloudflare Worker overlays → AI bot access pitfalls → Cache/WAF problems → Verification scripts New write-up: vapvarun.com/llms-txt-wordp… #AISEO #WordPress #ChatGPT #ClaudeAI #Perplexity #TechnicalSEO

Automate your llms.txt generation!

@Basit_Miyanji @kalashvasaniya Yup, how many times has Claude/GPT actually used llms.txt? We still keep in the score, but most of the weight goes to your actual content, not protocol theater.

@kalashvasaniya An seo guy was saying llms files are myth, they don't play any role in ranking

most crazy thing on scrolllaunch.com in one click, you can generate an 8-10 min detailed blog its rank on llms, using (llms.txt, llms-full.txt, ai.txt, rss.xml, atom.xml, seoitis.com, robots.txt) + dr 41 👀 what are you waiting for?

@denohawari Seriously, we have indexed so many sites, and this is a common theme. The top brands literally write pages to answer AI.

your blog posts are too vague to get cited in ChatGPT this is one of the BIGGEST reasons brands aren't showing up in AI answers LLMs are trained to pull specific causal claims and skip over soft marketing language most copy on the internet says "this tool is effective" when it should say "this tool cut our CAC by 40%" rewrite yours like this: - "this tool is effective" → "this tool cut customer acquisition cost by 40%" - "users love this feature" → "this feature took retention from 23% to 61%" - "we help SaaS grow" → "we helped a SaaS generate $400K in 90 days from organic" - "great for small teams" → "built for teams of 5-20 with at least 3 client accounts" - "fast results" → "ranked our last client in ChatGPT in 3 days" LLMs see specific numbers as proof and cite the page vague claims get skipped over and you stay invisible write like you're trying to win a court case

@pbteja1998 Pretty cool! Execution and Agency beat almost everything else.

So many things I wanted to do... but kept postponing... I got them all done in 1 day... Hacker Residency is truly magical... once you get into the zone.

@webjuice_ie Great work. A lot of the time, those plugins break when LLMs ask questions from your site. app.sitedex.dev/sites/webjuice…

After 15 years working with WordPress, I have changed how I think about client websites The problem is rarely "WordPress is bad" The problem is usually that a simple marketing site slowly turns into an operating liability ⬇️⬇️⬇️ A theme here A page builder there A few SEO plugins A cache plugin A forms plugin A security plugin Then updates, conflicts, speed issues, broken layouts, and small fixes that should not need a developer. For content-heavy or app-like websites, WordPress can still make sense But for many service business websites, the better question is: Does this site need a database and 15 plugins to show five service pages, a blog, and a contact form? For our own agency site, we moved to Astro, Tailwind, and a cleaner static architecture The benefit was not just speed It was less maintenance, cleaner SEO, fewer moving parts, and a site that feels easier to trust That is the real migration win: not "new tech," but fewer things that can quietly break

@marclou @DataFast_ app.sitedex.dev/sites/datafa.st We are free to use, to identify content and protocol gaps. AI native is the way to go.

2026 goal: make all my startups AI-first. I'm starting with @DataFast_: ✅ Open all API endpoints ✅ llms.txt & markdown docs ⬜️ CLI (in progress) ⬜️ MCP ⬜️ Generative UI ⬜️ Onboarding w/ paywall At the speed AI is going, I think a lot of front-end will disapear and SaaS will be mostly backend. AI assistants will do the UI.

Every single Sitedex action can now be done via an API or CLI. And we use Sitedex to build Sitedex :-)

Verified data, verified facts.

@thekitze Then we move to Kimi 3 honeymoon…

yo, i'm actually worried. codex limits are genuinely insane so it's sus af .. i feel this is an intentional move for a honeymoon period until we get over the claude → codex migration and then we get rugpulled hard