postgresql.org

scanned 7/25/2026, 8:40:32 PM · cached · refresh in 20h · rubric 2026.07.4

Needs work

This is how AI agents (not browsers) experience postgresql.org. The score weights five categories of machine-readability; the ticks on the arc are the 30 individual checks behind it.

Discoverability

✉ Email me this report + alert me when it changes ↓

Top fixes

Checks tagged “emerging” are 2026 agent-protocol standards most of the web hasn’t adopted yet — adopting early is an edge, not a defect.

failCanonical URLDiscoverability

No <link rel="canonical"> tag in <head>. Agents use canonical URLs to dedupe and cite.

Fix: Add <link rel="canonical" href="…"> pointing at the primary URL of each page.

failJSON-LD presentStructured data

No JSON-LD blocks found. Add a <script type="application/ld+json"> with a schema.org type for this page.

Fix: Add a <script type="application/ld+json"> describing the page (Organization, Article, Product, FAQPage).

warnllms.txt presentDiscoverability

Found /llms.txt but missing H1 header and markdown links.

Fix: Publish /llms.txt at your domain root. Build a spec-compliant one at /tools/llms-txt-generator.

failLink response headersDiscoverability

No HTTP Link: response headers. Emit canonical/alternate/describedby relations so HEAD-only or stream-rendering agents get them without parsing HTML.

Fix: Emit `Link:` headers for canonical, alternate-language, and describedby relations. Agents that fetch HEAD-only or stream-render rely on these.

warnTime to first bytePerformance

TTFB 1432ms. Slow. Agents time out aggressively.

Fix: Agents time out aggressively. Use edge caching for anonymous requests to cut TTFB below 800ms.

failContent-Signal directivesemergingDiscoverability

No Content-Signal directives. Add e.g. `Content-Signal: ai-train=no, ai-summarize=yes` to declare granular AI usage policy beyond binary allow/disallow.

Fix: Add `Content-Signal:` directives to your robots.txt. This is the emerging standard (Cloudflare-driven) for declaring fine-grained AI usage policy beyond a binary allow/disallow.

Don’t lose this report

Get it in your inbox now — and a heads-up whenever postgresql.org’s agent-readiness score changes. Free, unsubscribe anytime.

Fix it

Generated, ready-to-ship files for the gaps above — copy them or download and drop them into your repo.

Add an llms.txt

Publish this at https://postgresql.org/llms.txt

# PostgreSQL: The world's most advanced open source database

> The official site for PostgreSQL, the world

## Key pages
- [Home](https://postgresql.org/)
- [PostgreSQL: The World's Most Advanced Open Source Relational Database](https://postgresql.org/)
- [New to PostgreSQL?](https://postgresql.org/)
- [Latest Releases](https://postgresql.org/)
- [Upcoming Events](https://postgresql.org/)
- [Mailing Lists](https://postgresql.org/)
- [Learning Opportunities Ahead](https://postgresql.org/)

## About
Describe what postgresql.org does, who it's for, and the primary action you want an
agent to be able to complete. Keep it factual and current.

What the agent receives

The agent’s-eye view

PostgreSQL: The world's most advanced open source database Home About Download Documentation Community Developers Support Donate Your account July 16, 2026: PostgreSQL 19 Beta 2 Released! PostgreSQL: The World's Most Advanced Open Source Relational Database Download New to PostgreSQL? New to PostgreSQL? PostgreSQL is a powerful, open source object-relational database system with over 35 years of active development that has earned it a strong reputation for reliability, feature robustness, and performance. There is a wealth of information to be found describing how to install and use PostgreSQL through the official documentation . The open source community provides many helpful places to become familiar with PostgreSQL, discover how it works, and find career opportunities. Learn more on how to engage with the community . Learn More Feature Matrix Governance Latest Releases 2026-07-16 - PostgreSQL 19 Beta 2 Released! The PostgreSQL Global Development Group announces that the 2nd beta release of PostgreSQL 19 is now available for download . This release contains PostgreSQL 19 feature previews ahead of general availability, though some details of the release can change during the testing period. You can find information about all of the PostgreSQL 19 features and changes in the release notes . In the spirit of the open source PostgreSQL community, we strongly encourage you to test the new features of PostgreSQL 19 on your systems to help us eliminate bugs and other issues. While we do not advise you to run beta versions in production environments, we encourage you to find ways to run your typical application workloads against this beta release. Your testing and feedback help the community ensure that PostgreSQL 19 upholds our standards of delivering a stable, reliable release of the world's most advanced open source relational database. Please read more about our testing process and how you can contribute. PostgreSQL 14 will stop receiving fixes on November 12, 2026. If you are running PostgreSQL 14 in a production environment, we suggest that you make plans to upgrade to a newer, supported version of PostgreSQL. Please see our versioning policy for more information. 18.4 &middot; 2026-05-14 &middot; Notes 17.10 &middot; 2026-05-14 &middot; Notes 16.14 &middot; 2026-05-14 &middot; Notes 15.18 &middot; 2026-05-14 &middot; Notes 14.23 &middot; 2026-05-14 &middot; Notes Download Why Upgrade? Security Upcoming Events 2026-08-20 &ndash; 2026-08-21 &middot; Hyderabad Postgres Days 2026 2026-09-08 &middot; PGDay UK 2026 2026-10-20 &ndash; 2026-10-23 &middot; PGConf.EU 2026 2026-10-25 &middot; PGDay Israel 2026 2026-10-30 &middot; PG Down Under 2026 2026-11-17 &ndash; 2026-11-18 &middot; PGCONF.ASIA 2026 2026-11-18 &ndash; 2026-11-21 &middot; PgConf.Nepal 2026 indicates that an event is recognised under the community event guidelines and is directly helping the PostgreSQL community. Check Schedule Add Your Event Mailing Lists The PostgreSQL mailing lists enable you to interact with active community participants on subjects related to the development of PostgreSQL, discovering how to use PostgreSQL, or learning about upcoming events and product releases. In order to manage your mailing list subscription, you need a PostgreSQL community account . Signing up is easy and gives you direct access to the global PostgreSQL community . Subscribe View Archives Learning Opportunities Ahead Want to learn more about PostgreSQL and help build the community? Come to one of the many events, local user groups, &amp; training sessions where you can meet experienced PostgreSQL users and enhance your database skills. Browse Events Browse User Groups Latest News PostgreSQL 19 Beta 2 Released! &nbsp;2026-07-16 The PostgreSQL Global Development Group announces that the 2nd beta release of PostgreSQL 19 is now available for download . This release contains PostgreSQL 19 feature previews ahead of general availability, though some details of the release can change during the testing period. You can find information about all of the PostgreSQL 19 features and changes in the release notes . In the spirit of the open source PostgreSQL community, we strongly encourage you to test the new features of PostgreSQL 19 on your systems to help us eliminate bugs and other issues. While we do not advise you to run beta versions in production environments, we encourage you to find ways to run your typical application workloads against this beta release. Your testing and feedback help the community ensure that PostgreSQL 19 upholds our standards of delivering a stable, reliable release of the world's most advanced open source relational database. Please read more about our testing process and how you can contribute. PostgreSQL 14 will stop receiving fixes on November 12, 2026. If you are running PostgreSQL 14 in a production environment, we suggest that you make plans to upgrade to a newer, supported version of PostgreSQL. Please see our versioning policy for more information. Release Announcement Release Notes PostgreSQL 19 Open Items Versioning Policy Download Browse Archives Submit News PostgreSQL 19 Beta 2 Released! &nbsp;2026-07-16 by PostgreSQL Global Development Group Odyssey 1.5.1 released &nbsp;2026-07-14 by Yandex powa-archivist 5.2.0 is out! &nbsp;2026-07-12 by PoWA PostgreSQL ODBC Version REL-18_00_0002 Released &nbsp;2026-07-08 by Postgresql ODBC Autobase 2.9.0 released &nbsp;2026-07-08 by vitabaks PLANET POSTGRESQL All Your GUCs in a Row: full_page_writes &nbsp;Christophe Pettus &nbsp;2026-07-25 Looking Forward to Postgres 19: Autovacuum Tweaks &nbsp;Shaun Thomas &nbsp;2026-07-24 All Your GUCs in a Row: fsync &nbsp;Christophe Pettus &nbsp;2026-07-24 The Right Way to Give a Third-Party DBA Access to Your PostgreSQL Database &nbsp;SHRIDHAR KHANAL &nbsp;2026-07-23 All Your GUCs in a Row: from_collapse_limit &nbsp;Christophe Pettus &nbsp;2026-07-23 Hybrid Search in PostgreSQL: BM25, Sparse Vectors, and Reciprocal Rank Fusion &nbsp;Ahsan Hadi &nbsp;2026-07-22 All Your GUCs in a Row: file_extend_method &nbsp;Christophe Pettus &nbsp;2026-07-22 Building The OAPE PostgreSQL Certification &nbsp;Cornelia Biacsics &nbsp;2026-07-21 Big Apple, Big PostgreSQL: EDB at Postgres Summit US 2026 &nbsp;Floor Drees &nbsp;2026-07-21 Browse Archives Seeing unexpected behavior? The PostgreSQL community takes pride in releasing software that reliably stores your data. If you believe you've discovered a bug, please click the button below and follow the instructions on how to submit a bug. Submit a Bug Policies | Code of Conduct | About PostgreSQL | Contact Copyright &copy; 1996-2026 The PostgreSQL Global Development Group

Show your score

Embed this badge on your site. It links back to this live scan and updates on every rescan.

<a href="https://agentspeed.com/scan/postgresql.org"><img src="https://agentspeed.com/badge/postgresql.org" alt="AgentSpeed agent-readiness score" height="56"></a>

Track this score

Get this report by email, then a heads-up when postgresql.org’s agent-readiness actually changes — a check regressing, or the composite dropping.

Two things never trigger an email: a score change caused by us publishing a new rubric, because that is a different instrument rather than a change to your site, and movement explained only by timing-derived checks, which shift run to run on a site nobody touched.

Want it on your own schedule, with Slack or a webhook instead of email? Score-drift monitoring is on every paid plan.

Full breakdown

13 pass2 warn12 fail3 skip

Show only failures

Discoverability

pass

robots.txt present

A robots.txt is reachable at the site root.

100/100

pass

robots.txt allows AI agents

All 8 answer-time access agents allowed.

100/100

fail

Content-Signal directivesemerging

No Content-Signal directives. Add e.g. `Content-Signal: ai-train=no, ai-summarize=yes` to declare granular AI usage policy beyond binary allow/disallow.

0/100

warn

llms.txt present

Found /llms.txt but missing H1 header and markdown links.

60/100

pass

Sitemap present

sitemap.xml reachable and referenced from robots.txt.

100/100

fail

Link response headers

No HTTP Link: response headers. Emit canonical/alternate/describedby relations so HEAD-only or stream-rendering agents get them without parsing HTML.

0/100

fail

Canonical URL

No <link rel="canonical"> tag in <head>. Agents use canonical URLs to dedupe and cite.

0/100

fail

MCP server cardemerging

No valid MCP Server Card at /.well-known/mcp/server-card.json. Publish one so agents can discover your tools without HTML scraping.

0/100

fail

OAuth authorization metadataemerging

No RFC 8414 metadata at /.well-known/oauth-authorization-server. Agents that act on behalf of users need this to discover your authorization endpoints.

0/100

fail

OAuth resource metadataemerging

No RFC 9728 metadata at /.well-known/oauth-protected-resource. Publish it so agents can discover required scopes without hand-coded credentials.

0/100

fail

API catalog / OpenAPIemerging

No /.well-known/api-catalog (RFC 9727) and no /openapi.json|yaml. Publish one so agents that integrate with APIs can discover your endpoints.

0/100

fail

Web Bot Authemerging

No Web Bot Auth JWKS at /.well-known/http-message-signatures-directory.json. Publish one to allow trusted agents while keeping a default-deny posture for the rest.

0/100

Readability

fail

Markdown negotiationemerging

Accept: text/markdown returns HTML, not markdown. Serve a markdown variant of primary content when requested; agents summarize and cite it more reliably.

0/100

pass

Text-to-markup ratio

Visible text is 26.8% of HTML weight (6683/24892 bytes). Healthy.

100/100

skip

Content without JavaScript

Browser pass unavailable; cannot measure JS dependency.

—

pass

Heading hierarchy

Hierarchy is well-formed (1 H1, no skipped levels, 24 headings total).

100/100

pass

Cookie wall blocks content

No common consent-modal markers detected.

100/100

pass

Page title

A concise <title> is present (58 chars).

100/100

pass

Meta description

A well-sized meta description is present (80 chars).

100/100

Structured data

fail

JSON-LD present

No JSON-LD blocks found. Add a <script type="application/ld+json"> with a schema.org type for this page.

0/100

skip

Structured data validates

No JSON-LD blocks present; nothing to validate (covered by structured_data.jsonld_present).

—

pass

Schema type coverage

Page intent unclear; no specific schema.org type expected.

100/100

Actionability

pass

Paywall / login wall

No paywall or login-wall detected on the landing URL.

100/100

fail

Agent Skills manifestemerging

No Agent Skills manifest at /.well-known/agent-skills.json. Enumerate the tasks agents can perform (search, add-to-cart, contact-support) so they pick the right one without scraping.

0/100

fail

WebMCP actionsemerging

No WebMCP detected. On pages with first-class actions (cart, support, account), embed a WebMCP server so on-page agents invoke tools directly.

0/100

pass

Primary action reachable

Primary offering identified ("open source relational database system") with price/CTA ("Download").

100/100

pass

Reachability

HTTP 200 after 1 redirect.

100/100

Performance

warn

Time to first byte

TTFB 1432ms. Slow. Agents time out aggressively.

40/100

skip

Full render time

Full-render time unavailable (browser pass skipped or failed).

—

pass

Page weight

Initial document is a lean 24 KB.

100/100

Beyond the scan

Running AI agents of your own? AgentSpeed also monitors them in production — every run, its latency, cost, and failures, with alerts when something breaks. Free for 10,000 events a month, no credit card.

Start watching free →See plans