PostGIS
(https://postgis.net) 📸 Data Snapshot: May 24, 2026Count trust words (review, testimonial, rating, verified) against real outbound proof links (Google, Trustpilot, Clutch, G2, Yelp). Lots of trust language with zero verification links is trust theatre. Unlinked logo galleries count against it.
The site avoids all common trust theatre patterns; it contains a review_count of 0 and does not attempt to use unverified testimonials or generic ‘trusted by’ logos. Instead, it provides md5 hashes and links to official OSGeo and GitHub repositories for every release. This represents a move from ‘theatre’ to functional proof for its developer audience.
The ratio of verifiable evidence to claims is near 1:1. Every version mentioned in the news feed is backed by a direct download link, an md5 checksum, and specific release notes. Documentation is provided for every supported version (3.2 through 3.6), demonstrating a deep commitment to verifiable substance over vague assertions.
Trust & Proof is read by weighing trust language against real verification. Below is the page-by-page tally of review mentions and external proof links, then the schema markup that may (or may not) declare verifiable ratings and identity proof.
🛡️ Trust Signals — reviews, proof links, trust-theatre check
| Page | Reviews | Proof links |
|---|---|---|
| / (home) | 0 | 0 |
| /development/source_code/ | 0 | 0 |
| /2026/04/PostGIS-Patch-Releases/ | 0 | 0 |
| /news/ | 0 | 0 |
🔗 Identity & Technical Layer — schema JSON-LD: declared ratings, reviews & identity proof
Homepage schema
{
"@context": "http://schema.org",
"@type": "WebSite",
"name": "PostGIS",
"url": "https://postgis.net/",
"license": "CC BY-SA 4.0",
"inLanguage": "en"
}
/development/source_code/
{
"@context": "http://schema.org",
"@type": "TechArticle",
"articleSection": "Development",
"name": "Source Code",
"url": "https://postgis.net/development/source_code/",
"headline": "Source Code",
"description": "Where to find the source repository and released source code",
"wordCount": "144",
"license": "CC BY-SA 4.0",
"inLanguage": "en",
"isFamilyFriendly": "true",
"mainEntityOfPage": {
"@type": "WebPage",
"@id": "https://postgis.net/development/source_code/"
},
"copyrightHolder": "PostGIS",
"copyrightYear": "2022",
"dateCreated": "2022-02-01T00:00:00.00Z",
"datePublished": "2022-02-01T00:00:00.00Z",
"dateModified": "2022-02-01T00:00:00.00Z",
"publisher": {
"@type": "Organization",
"name": "PostGIS",
"url": "https://postgis.net/",
"logo": {
"@type": "ImageObject",
"url": "https://postgis.net/brand.svg",
"width": "32",
"height": "32"
}
}
}
/2026/04/PostGIS-Patch-Releases/
{
"@context": "http://schema.org",
"@type": "TechArticle",
"articleSection": "News",
"name": "PostGIS Patch Releases",
"url": "https://postgis.net/2026/04/PostGIS-Patch-Releases/",
"headline": "PostGIS Patch Releases",
"description": "The PostGIS development team is pleased to provide bug fix and security releases for PostGIS 3.2 - 3.6.",
"wordCount": "64",
"license": "CC BY-SA 4.0",
"inLanguage": "en",
"isFamilyFriendly": "true",
"mainEntityOfPage": {
"@type": "WebPage",
"@id": "https://postgis.net/2026/04/PostGIS-Patch-Releases/"
},
"keywords": [
"release",
"3.6",
"3.5",
"3.4",
"3.3",
"3.2"
],
"copyrightHolder": "PostGIS",
"copyrightYear": "2026",
"dateCreated": "2026-04-14T00:00:00.00Z",
"datePublished": "2026-04-14T00:00:00.00Z",
"dateModified": "2026-04-14T00:00:00.00Z",
"publisher": {
"@type": "Organization",
"name": "PostGIS",
"url": "https://postgis.net/",
"logo": {
"@type": "ImageObject",
"url": "https://postgis.net/brand.svg",
"width": "32",
"height": "32"
}
}
}
/news/
{
"@context": "http://schema.org",
"@type": "TechArticle",
"articleSection": "News",
"name": "News",
"url": "https://postgis.net/news/",
"headline": "News",
"wordCount": "0",
"license": "CC BY-SA 4.0",
"inLanguage": "en",
"isFamilyFriendly": "true",
"mainEntityOfPage": {
"@type": "WebPage",
"@id": "https://postgis.net/news/"
},
"copyrightHolder": "PostGIS",
"copyrightYear": "2026",
"dateCreated": "2026-04-14T00:00:00.00Z",
"datePublished": "0001-01-01T00:00:00.00Z",
"dateModified": "2026-04-14T00:00:00.00Z",
"publisher": {
"@type": "Organization",
"name": "PostGIS",
"url": "https://postgis.net/",
"logo": {
"@type": "ImageObject",
"url": "https://postgis.net/brand.svg",
"width": "32",
"height": "32"
}
}
}
This page presents a snapshot of public data from PostGIS, captured on May 24, 2026, to show how machine logic reads Trust & Proof signals into an AI reputation evaluation.
Purpose: This data is presented under “Fair Use” for the purpose of independent signal analysis, allowing readers to see the raw signals behind the reputation score.
Notice to PostGIS: This analysis is part of a non-adversarial audit conducted by 1 Euro SEO. The results are intended as professional feedback to help improve any website’s machine-readability and authority signals. The evaluation is free, and any company can request a fresh audit at any time.
Any company can use the insights for free and improve its voice. When a company has updated its content, it can always submit a new audit request, which will be reflected in a new current score.
To all users: You are encouraged to visit the live site at https://postgis.net to view the most current version of its content and see directly what this company is about and what it offers.