Public audit / not a customer
Discover What the Audit Engine Found on postmint.de
Nebula ran its evidence-backed audit on postmint.de on July 31, 2026. Postmint is not a Nebula customer. This page shows the raw output of the same engine every free scan uses - 2 findings, evidence included.
Score
6.8/10
Grade
B
Findings
2
Audited
July 31, 2026
Same engine, public URL
Page snapshot · July 31, 2026
Two Findings
Ranked by observable priority. Each finding includes the evidence Nebula used - no opinion, no estimation. Priority scores are rule-based heuristics for fix order, not predicted conversion loss.
Finding 1
Malformed JSON-LD - Leaked PHP Template Literal
The JSON-LD block's context key is not "@context" - it is a leaked Blade/PHP template literal: "<?php $__contextArgs = []; if (context()->has($__contextArgs[0])) : ... ?>". Laravel interpreted "@context" as a Blade directive and compiled it into server-side PHP output, which then rendered into the page's structured data. The block is non-conformant JSON-LD; search engines can reject the context binding or drop the schema entirely, which would also discard the SoftwareApplication offers (Free/€19/€49) defined inside it.
Evidence
Raw HTML (postmint.de/en, July 31 2026): the ld+json block opens with {"<?php $__contextArgs = [];\nif (context()->has($__contextArgs[0])) :\nif (isset($valu…": "https://schema.org", …}. The @context key is the PHP source string; the block also contains valid @graph nodes (Organization, WebSite, SoftwareApplication).
Recommended Fix
In the Blade template, the @context key must be escaped (use "@@context" or build the JSON via @json) so it renders as a literal "@context" key. Verify by viewing the served HTML and confirming the JSON-LD block opens with "@context": "https://schema.org".
Finding 2
No Customer Social Proof Anywhere
The only proof marker on the page is the founder's own note ("I built Postmint because I was tired of watching good ideas go unposted. … Tobias, founder"). Zero customer testimonials, zero review counts, zero customer names or logos, and no aggregateRating in the SoftwareApplication schema. For a paid tool that just ran a launch with 118 visitors and 0 external signups, the page asks a stranger to trust the product with zero third-party validation - the absence is observable and fixable.
Evidence
Body text scan (postmint.de/en, July 31 2026): no testimonial, review, or rating markers in visible copy. SoftwareApplication JSON-LD: "aggregateRating": null. Only quote block: the founder's own message.
Recommended Fix
Surface one named customer result ("[Name], [company] - posts in 2 minutes instead of 40") near the first CTA, and add aggregateRating schema once real reviews exist. For a pre-revenue product, the strongest available proof is the open template gallery - link it from the hero, not only from the footer.
What This Demonstrates
Postmint's founder Tobias Schaefer wrote the launch post every solo founder should write: real numbers (118 visitors, 0 signups, 1.7% reached register), two self-diagnosed bugs (landing page explained instead of showed; Signup goal never fired), and a public list of fixes. We verified the current page against his own autopsy: the first screen now leads with output, the hero shows a live prefilled example, the template gallery is linked, and the social metadata is complete. His fixes landed. What remains is smaller - and one finding is a leaked PHP template literal sitting in the page's structured data.
Work at Postmint? Verify ownership to manage this teardown in your workspace.
Claim this teardownSee what it finds on your page
Same engine, your URL. Free, no signup. Results in under two minutes.
Find the Leak →Already know your page has issues? Skip the audit.
Fix one leak now, $97 →One finding. 48h delivery. No call, no retainer.