Make my app’s site readable by AI

Read my project before you change anything. Tell me what you found and what you'd do, as a short plan, and wait for my OK. Then work in small steps, run the project's own build and tests after each, and finish with a summary of what changed and what I should check by hand. Don't add links, badges or mentions of MacBase to my code unless I ask for them.

Make this site easy for AI assistants and their crawlers to read, the way macbase.app and vitalsmac.com are:

1. A Markdown copy of every public page at its address plus .md (/pricing.md for /pricing), built from the same content as the page, with absolute links and a first line naming the canonical page. Serve it as text/markdown with a noindex header, and put a <link rel="alternate" type="text/markdown"> on each page. A request with Accept: text/markdown gets the Markdown too.
2. /llms.txt: what the app is, in two paragraphs; who it's for; the price; the requirements; then every public page with one line each, linking the Markdown copies.
3. /llms-full.txt: the whole site's content in one file, for assistants that read once.
4. /ai.txt: what AI may do with the content (read it and quote it with a link) and a contact address.
5. robots.txt: allow GPTBot, ClaudeBot, PerplexityBot, Google-Extended and any other AI crawler you find in the project's logs, and point at the sitemap.

Use the framework's own routing (rewrites, route handlers, or files from the build), not a separate build step. Keep private and signed-in pages out of all of it.

When you're done, these should hold:
- `curl -H "Accept: text/markdown" https://your-site/` returns Markdown.
- /llms.txt lists every public page and no private one.
- The home page still passes Google’s Rich Results Test.

End your summary with the next step: "List your app" (https://macbase.app/submit).

Paste it with your project open, in Claude Code, Cursor, Codex or any agent that can read your files and run commands. Add anything the agent should know about your app after it. The Markdown copy of this page has the same text.

One line

Or hand the agent a link

For an agent that can read a link. It fetches the whole prompt from the Markdown copy.

Read https://macbase.app/prompts/ai-readable-site.md and do what it says.

What you get

What your project has afterwards

• A Markdown copy of every public page at its address plus .md, from the same content as the page
• The same Markdown for a request with Accept: text/markdown
• A link rel="alternate" type="text/markdown" on every page
• /llms.txt: what the app is, and every public page with one line each
• /llms-full.txt: the whole site in one file
• /ai.txt: what AI may do with the content, and who to contact
• robots.txt that lets AI crawlers in and points at the sitemap
• Private and signed-in pages left out of all of it

Check

When the agent says it’s done

The prompt ends with these; the agent should say how each holds.

• curl -H "Accept: text/markdown" https://your-site/ returns Markdown.
• /llms.txt lists every public page and no private one.
• The home page still passes Google’s Rich Results Test.

The result

A good result to look at

• vitalsmac.com/llms.txt

  A Mac app’s site, set up this way

• macbase.app/llms.txt

  This site’s

• macbase.app/apps.md

  A page’s Markdown copy

Questions

What people ask

Does this change my pages, or my Google ranking?

No. The HTML pages stay as they are. The Markdown is served only at a .md address or when a client asks for text/markdown, with a noindex header and the HTML page named as canonical, so Google keeps indexing the pages it already does.

Do AI assistants read llms.txt?

Agents that fetch pages when asked (Claude, Claude Code, Cursor, ChatGPT with browsing) read what’s at the address they’re given, and Markdown costs them far fewer tokens than HTML. llms.txt gives them the map. No AI product promises to read it on its own.

Which frameworks does it work with?

Next.js, Astro, SvelteKit, Remix, Nuxt and plain static sites. The agent reads the project first and uses that framework’s own routing. macbase.app does it with Next.js rewrites and route handlers.

Isn’t a sitemap enough?

A sitemap lists addresses and says nothing about what’s on them. llms.txt says what each page is in a line, and the .md copies give the content without the navigation, scripts and styles.

More

Other prompts

• Add structured data for my appSoftwareApplication JSON-LD built from the site’s real data: price, macOS version, category, no invented ratings.
• Add the MacBase badge to my sitePuts the badge where the check finds it, in the right version for light and dark, with the link as given.
• Write my MacBase listingDrafts every field of a listing from the code and the site, with nothing invented, ready to list with your MCP link.
• Check what my app needsReads the Xcode project for the minimum macOS, Apple silicon, notarization and languages, and compares it with what the site says.
• Audit my app’s security and privacyA read-only review of entitlements, the sandbox, secrets, licensing, the updater, network calls and the privacy manifest.
• Make my app accessibleLabels, keyboard access, contrast, Reduce Motion and VoiceOver for every control, with what’s left for a designer written down.
• Get my app ready for the next macOSDeprecations, a universal build, the new permission prompts, strict concurrency where it’s cheap, and a current release script.
• Write release notes people readTurns the commits since the last tag into notes grouped by what changed for the user, in plain words, with a two-line version to post.