agentleFS
oegeyilmaz9oegeyilmaz9/seo-aeo-geo-ultimate/llms.txt

seo-aeo-geo-ultimate

llms.txt6 starsChanged 3 months agoApache-2.0View on GitHub

A complete, evidence-first SEO, AEO, GEO and AI-search suite for Codex and Claude Code. Version 3.3.1. Source documents and native artifacts are maintained together. Python 3.11+ is required for the formal tools. If you are an LLM looking for information, use the content map to select the relevant topic and open its direct Markdown document. Use that document's cited evidence; if the requested information is absent, report that gap. Example fixtures are not observed engine facts.

The file

We split this llms.txt into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If you are an LLM looking for information, use the content map to select the relevant topic and open its direct Markdown document.

    line 6
  2. Distinctive:

    Use that document's cited evidence.

    line 7

≈ “Common” is an estimate: at least 1 in 5 of the 3,727 llms.txt files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
llms.txt
# SEO-AEO-GEO Ultimate

> A complete, evidence-first SEO, AEO, GEO and AI-search suite for Codex and Claude Code.

Version 3.3.1. Source documents and native artifacts are maintained together. Python 3.11+ is required for the formal tools.
If you are an LLM looking for information, use the content map to select the relevant topic and open its direct Markdown document.
Use that document's cited evidence; if the requested information is absent, report that gap. Example fixtures are not observed engine facts.

## Start here

- [Complete content map](https://raw.githubusercontent.com/oegeyilmaz9/seo-aeo-geo-ultimate/main/sitemap.md): Every declared public source resource, grouped by topic.
- [Turkish guide](https://raw.githubusercontent.com/oegeyilmaz9/seo-aeo-geo-ultimate/main/docs/REHBER-TR.md): Plain-language explanation and direct workflow destinations.
- [Executable Markdown quickstart](https://raw.githubusercontent.com/oegeyilmaz9/seo-aeo-geo-ultimate/main/docs/MARKDOWN-QUICKSTART.md): Local work index, public maps, native hints and keyword ownership.
- [SEO router](https://raw.githubusercontent.com/oegeyilmaz9/seo-aeo-geo-ultimate/main/skills/seo/SKILL.md): One front door and all 27 lane decisions.
- [Project README](https://raw.githubusercontent.com/oegeyilmaz9/seo-aeo-geo-ultimate/main/README.md): Installation, capability coverage and validation.

## Workflow contracts

- [Markdown delivery](https://raw.githubusercontent.com/oegeyilmaz9/seo-aeo-geo-ultimate/main/docs/MARKDOWN-DISCOVERY.md): Conventional SEO plus public Markdown parity, complete maps and private work notes.
- [Keyword protocol](https://raw.githubusercontent.com/oegeyilmaz9/seo-aeo-geo-ultimate/main/skills/seo-research/references/keyword-research-protocol.md): Query evidence, intent, decisions and exact answer ownership.
- [Provider boundaries](https://raw.githubusercontent.com/oegeyilmaz9/seo-aeo-geo-ultimate/main/docs/PROVIDER-OPERATIONS.md): Actual permissions, submissions and separate outcome evidence.

## Optional

- [License](https://raw.githubusercontent.com/oegeyilmaz9/seo-aeo-geo-ultimate/main/LICENSE): Apache-2.0 terms.
- [Security](https://raw.githubusercontent.com/oegeyilmaz9/seo-aeo-geo-ultimate/main/SECURITY.md): Vulnerability reporting.
- [Contributing](https://raw.githubusercontent.com/oegeyilmaz9/seo-aeo-geo-ultimate/main/CONTRIBUTING.md): Contribution and maintenance guidance.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.