URL analysée
https://www.jeronimo.dev/
Score AI-Ready
Bon
sur 100
Économie de tokens
Détail du score
Votre site n’a pas de fichier llms.txt. C’est le standard émergent pour aider les AI agents à comprendre la structure de votre site.
Comment implémenter
Créez un fichier /llms.txt en suivant la spécification de llmstxt.org. Incluez une description du site et des liens vers vos pages principales.
Votre site ne supporte pas Markdown for Agents. Ce standard Cloudflare permet aux agents IA de demander du contenu en format markdown, réduisant l'utilisation de tokens de ~80%.
Comment implémenter
Implémentez un ou plusieurs : (1) Répondre à Accept: text/markdown avec du contenu markdown. (2) Servir des URLs .md (ex : /page.md). (3) Ajouter des balises <link rel="alternate" type="text/markdown">. (4) Ajouter des en-têtes HTTP Link pour la découverte markdown.
Aucune directive Content-Signal trouvée. Celles-ci indiquent aux agents IA comment ils peuvent utiliser votre contenu (indexation, entrée IA, données d'entraînement). L'emplacement recommandé est robots.txt.
Comment implémenter
Ajoutez Content-Signal à votre robots.txt : User-agent: *\nContent-Signal: search=yes, ai-input=yes, ai-train=no. Vous pouvez aussi l'ajouter comme en-tête HTTP sur les réponses markdown.
La structure de vos titres présente des problèmes (niveaux sautés ou plusieurs balises h1). Une hiérarchie propre aide les AI agents à comprendre l’organisation du contenu.
Comment implémenter
Assurez-vous d’avoir exactement un <h1> par page et que les titres suivent un ordre séquentiel : h1 > h2 > h3. Ne sautez pas de niveaux (par ex. de h1 directement à h3).
Balises Open Graph manquantes ou incomplètes. Les balises OG aident les AI agents (et les plateformes sociales) à comprendre le titre, la description et l’image de votre page.
Comment implémenter
Ajoutez les balises meta og:title, og:description et og:image dans le <head> de votre page.
Spring Batch is one of the few existing tools in the Java Enterprise ecosystem for building batch processes or data pipelines. However, its components (ItemReader/ItemWriter) are primarily oriented toward relational databases, CSV, XML, or JSON. In a world where Data Lakes and columnar formats are increasingly important, integrating Parquet with Spring Batch opens new possibilities for building data pipelines from the Java world, without depending on complex solutions or different technology stacks that often cause friction in the Enterprise world. This week I released a new version of [Carpet](https://github.com/jerolba/parquet-carpet), the Java library for working with Parquet files. In this version, I’ve added a feature that I believe nobody will ever use: **the ability to read and write BSON-type columns**. A few days ago, the creators of DuckDB wrote the article: [Query Engines: Gatekeepers of the Parquet File Format](https://duckdb.org/2025/01/22/parquet-encodings.html), which explained how the engines that process Parquet files as SQL tables are blocking the evolution of the format. This is because those engines are not fully supporting the latest specification, and without this support, the rest of the ecosystem has no incentive to adopt it. Apache Parquet is a columnar storage format optimized for analytical workloads, though it can also be used to store any type of structured data solving multiple use cases. One of its most notable features is the ability to efficiently compress data using different compression techniques at two stages of its process. This reduces storage costs and improves reading performance. This article explains file compression in Parquet for Java, provides usage examples, and analyzes its performance. After some time working with Parquet files in Java using the Parquet Avro library, and studying how it worked, I concluded that despite **being very useful** in multiple use cases and having great potential, **the documentation and ecosystem needed for adoption in the Java world was very poor**. Many people are using suboptimal solutions (CSV or JSON files), applying more complex solutions (Spark), or using languages they are not familiar with (Python) because they don’t know how to work with Parquet files easily. That’s why I decided to **write this [series of articles](https://www.jeronimo.dev/working-with-parquet-files-in-java/)**. Once you understand it and have the examples, everything is easier. But, **can it be even easier?** Can we avoid the hassle of using *strange* libraries that serialize other formats? **Yes, it should be even easier.** That’s why I decided to **implement an Open Source library** that makes working with Parquet from Java extremely simple, something that covers it: **Carpet**. This post continues the series of articles about working with Parquet files in Java. This time, I’ll explain how to do it using the Protocol Buffers (PB) library. Finding examples and documentation on how to use Parquet with Avro is challenging, but with **Protocol Buffers, it’s even more complicated**. In the previous article, I wrote an introduction to using Parquet files in Java, but I did not include any examples. In this article, I will explain how to do this using the Avro library. Parquet with Avro **is one of the most popular ways to work with Parquet files in Java** due to its simplicity, flexibility, and because it is the library with the most examples. Parquet is a widely used format in the Data Engineering realm and holds significant potential for traditional Backend applications. This article serves as an **introduction to the format**, including some of the unique challenges I’ve faced while using it, to spare you from similar experiences. In previous posts I’ve analyzed [Protocol Buffers](https://www.jeronimo.dev/java-serialization-with-protocol-buffers/) and [FlatBuffers](https://www.jeronimo.dev/java-serialization-with-flatbuffers/), using JSON as the baseline. In this post, I will analyze Apache Avro and compare it with the previously studied formats. In the [previous post](https://www.jeronimo.dev/java-serialization-with-protocol-buffers/) I analyzed Protocol Buffers format, using JSON as baseline. In this post I’m going to analyze FlatBuffers and compare it with previously studied formats.
Spartan Blog - Jerónimo | Jerolba’s blog. Tech, JVM and random stuff. [](https://www.jeronimo.dev/ "Spartan Blog - Jerónimo")# [Spartan Blog - Jerónimo](https://www.jeronimo.dev/) Jerolba's blog. Tech, JVM and random stuff. ### [Integrating Spring Batch with Parquet](https://www.jeronimo.dev/integrating-spring-batch-with-parquet/) Spring Batch is one of the few existing tools in the Java Enterprise ecosystem for building batch processes or data pipelines. However, its components (ItemReader/ItemWriter) are primarily oriented toward relational databases, CSV, XML, or JSON. In a world where Data Lakes and columnar formats are increasingly important, integrating Parquet with Spring Batch opens new possibilities for building data pipelines from the Java world, without depending on complex solutions or different technology stacks that often cause friction in the Enterprise world. ### [The Carpet feature that nobody will use](https://www.jeronimo.dev/the-carpet-feature-that-nobody-will-use/) This week I released a new version of [Carpet](https://github.com/jerolba/parquet-carpet), the Java library for working with Parquet files. In this version, I’ve added a feature that I believe nobody will ever use: **the ability to read and write BSON-type columns**. ### [The two versions of Parquet](https://www.jeronimo.dev/the-two-versions-of-parquet/) A few days ago, the creators of DuckDB wrote the article: [Query Engines: Gatekeepers of the Parquet File Format](https://duckdb.org/2025/01/22/parquet-encodings.html), which explained how the engines that process Parquet files as SQL tables are blocking the evolution of the format. This is because those engines are not fully supporting the latest specification, and without this support, the rest of the ecosystem has no incentive to adopt it. ### [Compression algorithms in Parquet](https://www.jeronimo.dev/compression-algorithms-parquet/) Apache Parquet is a columnar storage format optimized for analytical workloads, though it can also be used to store any type of structured data solving multiple use cases. One of its most notable features is the ability to efficiently compress data using different compression techniques at two stages of its process. This reduces storage costs and improves reading performance. This article explains file compression in Parquet for Java, provides usage examples, and analyzes its performance. ### [Working with Parquet files in Java using Parquet Carpet](https://www.jeronimo.dev/working-with-parquet-files-in-java-using-carpet/) After some time working with Parquet files in Java using the Parquet Avro library, and studying how it worked, I concluded that despite **being very useful** in multiple use cases and having great potential, **the documentation and ecosystem needed for adoption in the Java world was very poor**. Many people are using suboptimal solutions (CSV or JSON files), applying more complex solutions (Spark), or using languages they are not familiar with (Python) because they don’t know how to work with Parquet files easily. That’s why I decided to **write this [series of articles](https://www.jeronimo.dev/working-with-parquet-files-in-java/)**. Once you understand it and have the examples, everything is easier. But, **can it be even easier?** Can we avoid the hassle of using *strange* libraries that serialize other formats? **Yes, it should be even easier.** That’s why I decided to **implement an Open Source library** that makes working with Parquet from Java extremely simple, something that covers it: **Carpet**. ### [Working with Parquet files in Java using Protocol Buffers](https://www.jeronimo.dev/working-with-parquet-files-in-java-using-protocol-buffers/) This post continues the series of articles about working with Parquet files in Java. This time, I’ll explain how to do it using the Protocol Buffers (PB) library. Finding examples and documentation on how to use Parquet with Avro is challenging, but with **Protocol Buffers, it’s even more complicated**. ### [Working with Parquet files in Java using Avro](https://www.jeronimo.dev/working-with-parquet-files-in-java-using-avro/) In the previous article, I wrote an introduction to using Parquet files in Java, but I did not include any examples. In this article, I will explain how to do this using the Avro library. Parquet with Avro **is one of the most popular ways to work with Parquet files in Java** due to its simplicity, flexibility, and because it is the library with the most examples. ### [Working with Parquet files in Java](https://www.jeronimo.dev/working-with-parquet-files-in-java/) Parquet is a widely used format in the Data Engineering realm and holds significant potential for traditional Backend applications. This article serves as an **introduction to the format**, including some of the unique challenges I’ve faced while using it, to spare you from similar experiences. ### [Java Serialization with Apache Avro](https://www.jeronimo.dev/java-serialization-with-avro/) In previous posts I’ve analyzed [Protocol Buffers](https://www.jeronimo.dev/java-serialization-with-protocol-buffers/) and [FlatBuffers](https://www.jeronimo.dev/java-serialization-with-flatbuffers/), using JSON as the baseline. In this post, I will analyze Apache Avro and compare it with the previously studied formats. ### [Java Serialization with Flatbuffers](https://www.jeronimo.dev/java-serialization-with-flatbuffers/) In the [previous post](https://www.jeronimo.dev/java-serialization-with-protocol-buffers/) I analyzed Protocol Buffers format, using JSON as baseline. In this post I’m going to analyze FlatBuffers and compare it with previously studied formats.
Téléversez ce fichier sous /index.md sur votre serveur pour que les AI agents puissent accéder à une version propre de votre page. Vous pouvez également configurer la négociation de contenu Accept: text/markdown pour le servir automatiquement.
llms.txt généré pour cette page individuelle
# Spartan Blog - Jerónimo > Jerolba’s blog. Tech, JVM and random stuff. ## Main - [Spartan Blog - Jerónimo](https://www.jeronimo.dev/): Jerolba’s blog. Tech, JVM and random stuff. - [Integrating Spring Batch with Parquet](https://www.jeronimo.dev/integrating-spring-batch-with-parquet/) - [The Carpet feature that nobody will use](https://www.jeronimo.dev/the-carpet-feature-that-nobody-will-use/) - [The two versions of Parquet](https://www.jeronimo.dev/the-two-versions-of-parquet/) - [Compression algorithms in Parquet](https://www.jeronimo.dev/compression-algorithms-parquet/) - [Working with Parquet files in Java using Parquet Carpet](https://www.jeronimo.dev/working-with-parquet-files-in-java-using-carpet/) - [Working with Parquet files in Java using Protocol Buffers](https://www.jeronimo.dev/working-with-parquet-files-in-java-using-protocol-buffers/) - [Working with Parquet files in Java using Avro](https://www.jeronimo.dev/working-with-parquet-files-in-java-using-avro/) - [Working with Parquet files in Java](https://www.jeronimo.dev/working-with-parquet-files-in-java/)
Le llms.txt complet nécessite une analyse de tout le domaine (bientôt disponible)
Téléversez ce fichier vers https://www.jeronimo.dev/llms.txt à la racine de votre domaine. Les AI agents comme ChatGPT, Claude et Perplexity consultent ce fichier pour comprendre la structure de votre site.
HTML sémantique
Has both <article> and <main>
2 <h1> elements (should be 1), 1 heading level skip(s)
46 semantic elements, 15 divs (ratio: 75%)
1/1 images with meaningful alt text
Avg div depth: 2.2, max: 3
Efficacité du contenu
77% token reduction (HTML→Markdown)
Content ratio: 29.2% (4359 content chars / 14947 HTML bytes)
0/175 elements with inline styles (0.0%)
HTML size: 15KB
Visibilité IA
No llms.txt found
robots.txt exists
All major AI bots allowed
Sitemap found
No markdown content negotiation
No Content-Signal header
Données structurées
JSON-LD found but basic types: WebSite
2/3 OG tags present
Meta description too short: 43 chars
Canonical URL present
lang="en-US"
Accessibilité
Content available without JavaScript
Page size: 15KB
Main content starts at 22% of HTML
{
"url": "https://www.jeronimo.dev/",
"timestamp": 1771156368416,
"fetch": {
"mode": "simple",
"timeMs": 136,
"htmlSizeBytes": 14947,
"supportsMarkdown": false,
"statusCode": 200
},
"extraction": {
"title": "Spartan Blog - Jerónimo",
"excerpt": "Jerolba’s blog. Tech, JVM and random stuff.",
"byline": "Jerónimo López",
"siteName": "Spartan Blog - Jerónimo",
"lang": "en-US",
"contentLength": 4359,
"metadata": {
"description": "Jerolba’s blog. Tech, JVM and random stuff.",
"ogTitle": "Spartan Blog - Jerónimo",
"ogDescription": "Jerolba’s blog. Tech, JVM and random stuff.",
"ogImage": null,
"ogType": "website",
"canonical": "https://www.jeronimo.dev/",
"lang": "en-US",
"schemas": [
{
"@context": "https://schema.org",
"@type": "WebSite",
"author": {
"@type": "Person",
"name": "Jerónimo López"
},
"description": "Jerolba’s blog. Tech, JVM and random stuff.",
"headline": "Spartan Blog - Jerónimo",
"name": "Spartan Blog - Jerónimo",
"publisher": {
"@type": "Organization",
"logo": {
"@type": "ImageObject",
"url": "https://www.jeronimo.dev/images/spartan-helmet.png"
},
"name": "Jerónimo López"
},
"url": "https://www.jeronimo.dev/"
}
],
"robotsMeta": null,
"author": "Jerónimo López",
"generator": "Jekyll v3.8.7"
}
},
"markdown": "Spring Batch is one of the few existing tools in the Java Enterprise ecosystem for building batch processes or data pipelines. However, its components (ItemReader/ItemWriter) are primarily oriented toward relational databases, CSV, XML, or JSON.\n\nIn a world where Data Lakes and columnar formats are increasingly important, integrating Parquet with Spring Batch opens new possibilities for building data pipelines from the Java world, without depending on complex solutions or different technology stacks that often cause friction in the Enterprise world.\n\nThis week I released a new version of [Carpet](https://github.com/jerolba/parquet-carpet), the Java library for working with Parquet files. In this version, I’ve added a feature that I believe nobody will ever use: **the ability to read and write BSON-type columns**.\n\nA few days ago, the creators of DuckDB wrote the article: [Query Engines: Gatekeepers of the Parquet File Format](https://duckdb.org/2025/01/22/parquet-encodings.html), which explained how the engines that process Parquet files as SQL tables are blocking the evolution of the format. This is because those engines are not fully supporting the latest specification, and without this support, the rest of the ecosystem has no incentive to adopt it.\n\nApache Parquet is a columnar storage format optimized for analytical workloads, though it can also be used to store any type of structured data solving multiple use cases.\n\nOne of its most notable features is the ability to efficiently compress data using different compression techniques at two stages of its process. This reduces storage costs and improves reading performance.\n\nThis article explains file compression in Parquet for Java, provides usage examples, and analyzes its performance.\n\nAfter some time working with Parquet files in Java using the Parquet Avro library, and studying how it worked, I concluded that despite **being very useful** in multiple use cases and having great potential, **the documentation and ecosystem needed for adoption in the Java world was very poor**.\n\nMany people are using suboptimal solutions (CSV or JSON files), applying more complex solutions (Spark), or using languages they are not familiar with (Python) because they don’t know how to work with Parquet files easily. That’s why I decided to **write this [series of articles](https://www.jeronimo.dev/working-with-parquet-files-in-java/)**.\n\nOnce you understand it and have the examples, everything is easier. But, **can it be even easier?** Can we avoid the hassle of using *strange* libraries that serialize other formats? **Yes, it should be even easier.**\n\nThat’s why I decided to **implement an Open Source library** that makes working with Parquet from Java extremely simple, something that covers it: **Carpet**.\n\nThis post continues the series of articles about working with Parquet files in Java. This time, I’ll explain how to do it using the Protocol Buffers (PB) library.\n\nFinding examples and documentation on how to use Parquet with Avro is challenging, but with **Protocol Buffers, it’s even more complicated**.\n\nIn the previous article, I wrote an introduction to using Parquet files in Java, but I did not include any examples. In this article, I will explain how to do this using the Avro library.\n\nParquet with Avro **is one of the most popular ways to work with Parquet files in Java** due to its simplicity, flexibility, and because it is the library with the most examples.\n\nParquet is a widely used format in the Data Engineering realm and holds significant potential for traditional Backend applications. This article serves as an **introduction to the format**, including some of the unique challenges I’ve faced while using it, to spare you from similar experiences.\n\nIn previous posts I’ve analyzed [Protocol Buffers](https://www.jeronimo.dev/java-serialization-with-protocol-buffers/) and [FlatBuffers](https://www.jeronimo.dev/java-serialization-with-flatbuffers/), using JSON as the baseline. In this post, I will analyze Apache Avro and compare it with the previously studied formats.\n\nIn the [previous post](https://www.jeronimo.dev/java-serialization-with-protocol-buffers/) I analyzed Protocol Buffers format, using JSON as baseline. In this post I’m going to analyze FlatBuffers and compare it with previously studied formats.\n",
"fullPageMarkdown": "Spartan Blog - Jerónimo | Jerolba’s blog. Tech, JVM and random stuff.\n\n[](https://www.jeronimo.dev/ \"Spartan Blog - Jerónimo\")# [Spartan Blog - Jerónimo](https://www.jeronimo.dev/)\n\nJerolba's blog. Tech, JVM and random stuff.\n\n### [Integrating Spring Batch with Parquet](https://www.jeronimo.dev/integrating-spring-batch-with-parquet/)\n\nSpring Batch is one of the few existing tools in the Java Enterprise ecosystem for building batch processes or data pipelines. However, its components (ItemReader/ItemWriter) are primarily oriented toward relational databases, CSV, XML, or JSON.\n\nIn a world where Data Lakes and columnar formats are increasingly important, integrating Parquet with Spring Batch opens new possibilities for building data pipelines from the Java world, without depending on complex solutions or different technology stacks that often cause friction in the Enterprise world.\n\n### [The Carpet feature that nobody will use](https://www.jeronimo.dev/the-carpet-feature-that-nobody-will-use/)\n\nThis week I released a new version of [Carpet](https://github.com/jerolba/parquet-carpet), the Java library for working with Parquet files. In this version, I’ve added a feature that I believe nobody will ever use: **the ability to read and write BSON-type columns**.\n\n### [The two versions of Parquet](https://www.jeronimo.dev/the-two-versions-of-parquet/)\n\nA few days ago, the creators of DuckDB wrote the article: [Query Engines: Gatekeepers of the Parquet File Format](https://duckdb.org/2025/01/22/parquet-encodings.html), which explained how the engines that process Parquet files as SQL tables are blocking the evolution of the format. This is because those engines are not fully supporting the latest specification, and without this support, the rest of the ecosystem has no incentive to adopt it.\n\n### [Compression algorithms in Parquet](https://www.jeronimo.dev/compression-algorithms-parquet/)\n\nApache Parquet is a columnar storage format optimized for analytical workloads, though it can also be used to store any type of structured data solving multiple use cases.\n\nOne of its most notable features is the ability to efficiently compress data using different compression techniques at two stages of its process. This reduces storage costs and improves reading performance.\n\nThis article explains file compression in Parquet for Java, provides usage examples, and analyzes its performance.\n\n### [Working with Parquet files in Java using Parquet Carpet](https://www.jeronimo.dev/working-with-parquet-files-in-java-using-carpet/)\n\nAfter some time working with Parquet files in Java using the Parquet Avro library, and studying how it worked, I concluded that despite **being very useful** in multiple use cases and having great potential, **the documentation and ecosystem needed for adoption in the Java world was very poor**.\n\nMany people are using suboptimal solutions (CSV or JSON files), applying more complex solutions (Spark), or using languages they are not familiar with (Python) because they don’t know how to work with Parquet files easily. That’s why I decided to **write this [series of articles](https://www.jeronimo.dev/working-with-parquet-files-in-java/)**.\n\nOnce you understand it and have the examples, everything is easier. But, **can it be even easier?** Can we avoid the hassle of using *strange* libraries that serialize other formats? **Yes, it should be even easier.**\n\nThat’s why I decided to **implement an Open Source library** that makes working with Parquet from Java extremely simple, something that covers it: **Carpet**.\n\n### [Working with Parquet files in Java using Protocol Buffers](https://www.jeronimo.dev/working-with-parquet-files-in-java-using-protocol-buffers/)\n\nThis post continues the series of articles about working with Parquet files in Java. This time, I’ll explain how to do it using the Protocol Buffers (PB) library.\n\nFinding examples and documentation on how to use Parquet with Avro is challenging, but with **Protocol Buffers, it’s even more complicated**.\n\n### [Working with Parquet files in Java using Avro](https://www.jeronimo.dev/working-with-parquet-files-in-java-using-avro/)\n\nIn the previous article, I wrote an introduction to using Parquet files in Java, but I did not include any examples. In this article, I will explain how to do this using the Avro library.\n\nParquet with Avro **is one of the most popular ways to work with Parquet files in Java** due to its simplicity, flexibility, and because it is the library with the most examples.\n\n### [Working with Parquet files in Java](https://www.jeronimo.dev/working-with-parquet-files-in-java/)\n\nParquet is a widely used format in the Data Engineering realm and holds significant potential for traditional Backend applications. This article serves as an **introduction to the format**, including some of the unique challenges I’ve faced while using it, to spare you from similar experiences.\n\n### [Java Serialization with Apache Avro](https://www.jeronimo.dev/java-serialization-with-avro/)\n\nIn previous posts I’ve analyzed [Protocol Buffers](https://www.jeronimo.dev/java-serialization-with-protocol-buffers/) and [FlatBuffers](https://www.jeronimo.dev/java-serialization-with-flatbuffers/), using JSON as the baseline. In this post, I will analyze Apache Avro and compare it with the previously studied formats.\n\n### [Java Serialization with Flatbuffers](https://www.jeronimo.dev/java-serialization-with-flatbuffers/)\n\nIn the [previous post](https://www.jeronimo.dev/java-serialization-with-protocol-buffers/) I analyzed Protocol Buffers format, using JSON as baseline. In this post I’m going to analyze FlatBuffers and compare it with previously studied formats.\n",
"markdownStats": {
"images": 0,
"links": 6,
"tables": 0,
"codeBlocks": 0,
"headings": 0
},
"tokens": {
"htmlTokens": 3880,
"markdownTokens": 892,
"reduction": 2988,
"reductionPercent": 77
},
"score": {
"score": 76,
"grade": "B",
"dimensions": {
"semanticHtml": {
"score": 91,
"weight": 20,
"grade": "A",
"checks": {
"uses_article_or_main": {
"score": 100,
"weight": 20,
"details": "Has both <article> and <main>"
},
"proper_heading_hierarchy": {
"score": 65,
"weight": 25,
"details": "2 <h1> elements (should be 1), 1 heading level skip(s)"
},
"semantic_elements": {
"score": 100,
"weight": 20,
"details": "46 semantic elements, 15 divs (ratio: 75%)"
},
"meaningful_alt_texts": {
"score": 100,
"weight": 15,
"details": "1/1 images with meaningful alt text"
},
"low_div_nesting": {
"score": 100,
"weight": 20,
"details": "Avg div depth: 2.2, max: 3"
}
}
},
"contentEfficiency": {
"score": 86,
"weight": 25,
"grade": "B",
"checks": {
"token_reduction_ratio": {
"score": 80,
"weight": 40,
"details": "77% token reduction (HTML→Markdown)"
},
"content_to_noise_ratio": {
"score": 80,
"weight": 30,
"details": "Content ratio: 29.2% (4359 content chars / 14947 HTML bytes)"
},
"minimal_inline_styles": {
"score": 100,
"weight": 15,
"details": "0/175 elements with inline styles (0.0%)"
},
"reasonable_page_weight": {
"score": 100,
"weight": 15,
"details": "HTML size: 15KB"
}
}
},
"aiDiscoverability": {
"score": 50,
"weight": 25,
"grade": "D",
"checks": {
"has_llms_txt": {
"score": 0,
"weight": 25,
"details": "No llms.txt found"
},
"has_robots_txt": {
"score": 100,
"weight": 15,
"details": "robots.txt exists"
},
"robots_allows_ai_bots": {
"score": 100,
"weight": 20,
"details": "All major AI bots allowed"
},
"has_sitemap": {
"score": 100,
"weight": 15,
"details": "Sitemap found"
},
"supports_markdown_negotiation": {
"score": 0,
"weight": 15,
"details": "No markdown content negotiation"
},
"has_content_signals": {
"score": 0,
"weight": 10,
"details": "No Content-Signal header"
}
}
},
"structuredData": {
"score": 67,
"weight": 15,
"grade": "C",
"checks": {
"has_schema_org": {
"score": 50,
"weight": 30,
"details": "JSON-LD found but basic types: WebSite"
},
"has_open_graph": {
"score": 67,
"weight": 25,
"details": "2/3 OG tags present"
},
"has_meta_description": {
"score": 50,
"weight": 20,
"details": "Meta description too short: 43 chars"
},
"has_canonical_url": {
"score": 100,
"weight": 15,
"details": "Canonical URL present"
},
"has_lang_attribute": {
"score": 100,
"weight": 10,
"details": "lang=\"en-US\""
}
}
},
"accessibility": {
"score": 93,
"weight": 15,
"grade": "A",
"checks": {
"content_without_js": {
"score": 100,
"weight": 40,
"details": "Content available without JavaScript"
},
"reasonable_page_size": {
"score": 100,
"weight": 30,
"details": "Page size: 15KB"
},
"fast_content_position": {
"score": 75,
"weight": 30,
"details": "Main content starts at 22% of HTML"
}
}
}
}
},
"recommendations": [
{
"id": "add_llms_txt",
"priority": "critical",
"category": "aiDiscoverability",
"titleKey": "rec.add_llms_txt.title",
"descriptionKey": "rec.add_llms_txt.description",
"howToKey": "rec.add_llms_txt.howto",
"effort": "quick-win",
"estimatedImpact": 10,
"checkScore": 0,
"checkDetails": "No llms.txt found"
},
{
"id": "add_markdown_negotiation",
"priority": "critical",
"category": "aiDiscoverability",
"titleKey": "rec.add_markdown_negotiation.title",
"descriptionKey": "rec.add_markdown_negotiation.description",
"howToKey": "rec.add_markdown_negotiation.howto",
"effort": "significant",
"estimatedImpact": 4,
"checkScore": 0,
"checkDetails": "No markdown content negotiation"
},
{
"id": "add_content_signals",
"priority": "critical",
"category": "aiDiscoverability",
"titleKey": "rec.add_content_signals.title",
"descriptionKey": "rec.add_content_signals.description",
"howToKey": "rec.add_content_signals.howto",
"effort": "moderate",
"estimatedImpact": 3,
"checkScore": 0,
"checkDetails": "No Content-Signal header"
},
{
"id": "fix_heading_hierarchy",
"priority": "medium",
"category": "semanticHtml",
"titleKey": "rec.fix_heading_hierarchy.title",
"descriptionKey": "rec.fix_heading_hierarchy.description",
"howToKey": "rec.fix_heading_hierarchy.howto",
"effort": "quick-win",
"estimatedImpact": 6,
"checkScore": 65,
"checkDetails": "2 <h1> elements (should be 1), 1 heading level skip(s)"
},
{
"id": "add_open_graph",
"priority": "medium",
"category": "structuredData",
"titleKey": "rec.add_open_graph.title",
"descriptionKey": "rec.add_open_graph.description",
"howToKey": "rec.add_open_graph.howto",
"effort": "quick-win",
"estimatedImpact": 4,
"checkScore": 67,
"checkDetails": "2/3 OG tags present"
}
],
"llmsTxtPreview": "# Spartan Blog - Jerónimo\n\n> Jerolba’s blog. Tech, JVM and random stuff.\n\n## Main\n- [Spartan Blog - Jerónimo](https://www.jeronimo.dev/): Jerolba’s blog. Tech, JVM and random stuff.\n- [Integrating Spring Batch with Parquet](https://www.jeronimo.dev/integrating-spring-batch-with-parquet/)\n- [The Carpet feature that nobody will use](https://www.jeronimo.dev/the-carpet-feature-that-nobody-will-use/)\n- [The two versions of Parquet](https://www.jeronimo.dev/the-two-versions-of-parquet/)\n- [Compression algorithms in Parquet](https://www.jeronimo.dev/compression-algorithms-parquet/)\n- [Working with Parquet files in Java using Parquet Carpet](https://www.jeronimo.dev/working-with-parquet-files-in-java-using-carpet/)\n- [Working with Parquet files in Java using Protocol Buffers](https://www.jeronimo.dev/working-with-parquet-files-in-java-using-protocol-buffers/)\n- [Working with Parquet files in Java using Avro](https://www.jeronimo.dev/working-with-parquet-files-in-java-using-avro/)\n- [Working with Parquet files in Java](https://www.jeronimo.dev/working-with-parquet-files-in-java/)\n\n",
"llmsTxtExisting": null,
"snippets": [
{
"id": "add_llms_txt",
"title": "Create /llms.txt",
"description": "Upload this file to your web root. It tells AI agents what your site is about and which pages matter.",
"language": "markdown",
"code": "# Spartan Blog - Jerónimo\n\n> Jerolba’s blog. Tech, JVM and random stuff.\n\n## Main\n- [Spartan Blog - Jerónimo](https://www.jeronimo.dev/): Jerolba’s blog. Tech, JVM and random stuff.\n- [Integrating Spring Batch with Parquet](https://www.jeronimo.dev/integrating-spring-batch-with-parquet/)\n- [The Carpet feature that nobody will use](https://www.jeronimo.dev/the-carpet-feature-that-nobody-will-use/)\n- [The two versions of Parquet](https://www.jeronimo.dev/the-two-versions-of-parquet/)\n- [Compression algorithms in Parquet](https://www.jeronimo.dev/compression-algorithms-parquet/)\n- [Working with Parquet files in Java using Parquet Carpet](https://www.jeronimo.dev/working-with-parquet-files-in-java-using-carpet/)\n- [Working with Parquet files in Java using Protocol Buffers](https://www.jeronimo.dev/working-with-parquet-files-in-java-using-protocol-buffers/)\n- [Working with Parquet files in Java using Avro](https://www.jeronimo.dev/working-with-parquet-files-in-java-using-avro/)\n- [Working with Parquet files in Java](https://www.jeronimo.dev/working-with-parquet-files-in-java/)\n\n",
"filename": "/llms.txt"
},
{
"id": "fix_heading_hierarchy",
"title": "Fix heading hierarchy",
"description": "Your page has 2 <h1> elements. Keep only one. Demote the rest to <h2>.",
"language": "html",
"code": "<!-- Keep only one <h1> per page -->\n<h1>Spartan Blog - Jerónimo</h1>",
"filename": "<main> or <article>"
},
{
"id": "add_open_graph",
"title": "Add missing Open Graph tags",
"description": "These tags control how your page looks when shared on social media and some AI platforms.",
"language": "html",
"code": "<meta property=\"og:image\" content=\"https://yoursite.com/og-image.jpg\">\n<meta property=\"og:url\" content=\"https://www.jeronimo.dev/\">\n<meta property=\"og:type\" content=\"website\">",
"filename": "<head>"
},
{
"id": "add_content_signals",
"title": "Add Content-Signal HTTP header",
"description": "The Content-Signal header tells AI agents about the nature of your content. Add it via your web server or CDN.",
"language": "nginx",
"code": "# Nginx — add to your server block:\nadd_header Content-Signal \"type=website; lang=en-US\" always;\n\n# Apache — add to .htaccess:\n# Header set Content-Signal \"type=website; lang=en-US\"",
"filename": "nginx.conf or .htaccess"
},
{
"id": "add_markdown_negotiation",
"title": "Support Accept: text/markdown",
"description": "When a client sends Accept: text/markdown, respond with a Markdown version of the page. This is the gold standard for AI-readiness.",
"language": "nginx",
"code": "# Nginx — serve .md files when client requests Markdown:\n# Option 1: Serve pre-generated .md files\nmap $http_accept $markdown_suffix {\n default \"\";\n \"~text/markdown\" \".md\";\n}\n\n# Then in your location block:\ntry_files $uri$markdown_suffix $uri =404;\n\n# Option 2: Use your app framework to check the Accept header\n# and return Markdown content with Content-Type: text/markdown",
"filename": "nginx.conf or application code"
}
]
}
Utilisez notre API pour obtenir ceci de manière programmatique (bientôt disponible)
Ce JSON est à usage interne — contrairement au Markdown et au llms.txt, il n’est pas destiné à être téléversé sur votre site. Conservez-le comme référence pour suivre l’évolution de votre score, partagez-le avec votre équipe de développement ou intégrez-le dans votre pipeline CI/CD.
Intégrez votre badge
Ajoutez ce badge à votre site. Il se met à jour automatiquement lorsque votre score de préparation à l’IA change.
<script src="https://agentready.md/badge.js" data-id="e2a5c805-749c-45e5-953d-a16464f3ebcc" data-domain="www.jeronimo.dev"></script>
[](https://agentready.md/fr/r/e2a5c805-749c-45e5-953d-a16464f3ebcc)
Bientôt : Analyse de domaine complet
Explorez l’ensemble de votre domaine, générez un llms.txt et surveillez votre score de préparation IA dans le temps. Rejoignez la liste d’attente pour être informé.