Public audit / not a customer
Discover What the Audit Engine Found on postdew.com
Nebula ran its evidence-backed audit on postdew.com on August 3, 2026. PostDew is not a Nebula customer. This page shows the raw output of the same engine every free scan uses - 5 findings, evidence included.
Score
4.8/10
Grade
D
Findings
5
Audited
August 3, 2026
Same engine, public URL
Page snapshot · August 3, 2026
Five 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
No Static H1 Detected
No <h1> tag was found in the fetched document. If the primary promise is rendered only through client-side code, non-JavaScript readers and some extraction systems receive no primary heading.
Evidence
Fetched source: h1 count = 0. Page title: "PostDew - Protect your LinkedIn credibility". Snapshot timestamp: 2026-08-03T07:38:26Z.
Recommended Fix
Render one descriptive H1 in the initial HTML and align it with the credibility promise already present in the title.
Finding 2
No Source-Level CTA Candidate
No button or link text was found in fetched source HTML. Client-rendered controls may still exist, so browser validation is required before calling this a visible CTA failure.
Evidence
Fetched source: no button or link text candidate. Rendered primary journey remains unverified. Snapshot timestamp: 2026-08-03T07:38:26Z.
Recommended Fix
Inspect the rendered mobile and desktop hero. Make the first action explicit and tie it to the buyer outcome without inventing a performance promise.
Finding 3
No Static Trust Markers
No testimonials, reviews, named proof, or other recognized trust markers were found in the fetched source. An early product may not have customer proof yet; the absence should be treated as a constraint, not a reason to fabricate proof.
Evidence
Fetched source trust terms: none; recognized proof markers: none. Snapshot timestamp: 2026-08-03T07:38:26Z.
Recommended Fix
Use honest process proof first: a sample transformation, transparent product demo, or clearly labeled beta feedback. Add customer proof only when it exists.
Finding 4
Ad Tracking Not Observed in Static Source
No recognized ad-tracking artifact was observed in fetched source HTML. Runtime or server-side tracking remains unknown.
Evidence
Not observed: Facebook Pixel initializer, GA4 measurement ID, UTM-bearing link, or explicit conversion call. Snapshot timestamp: 2026-08-03T07:38:26Z.
Recommended Fix
Validate the actual event path in a consent-aware browser before deciding whether tracking is missing or simply implemented outside the static document.
Finding 5
No JSON-LD or Canonical Detected
The static page has Open Graph tags but no valid JSON-LD block and no canonical URL was detected. This is a machine-readable structure gap, not proof of absent search visibility.
Evidence
Valid JSON-LD blocks: 0/0; Open Graph tags: 5/5 non-empty; canonical: absent. Snapshot timestamp: 2026-08-03T07:38:26Z.
Recommended Fix
Add only accurate Organization/WebSite schema and a self-referencing canonical URL. Validate the JSON-LD after deployment.
What This Demonstrates
PostDew founder Manish Bhusal described the product and launch results in an IndieHackers post: 0 paying customers, approximately 10 cold DMs, 2 replies, 0 signups from those replies, and 0 signups from a Show HN post. Source: https://www.indiehackers.com/post/i-built-a-saas-in-10-days-3-weeks-live-0-paying-customers-heres-the-data-7cb6b6accf. This teardown does not attribute those outcomes to any single page defect. It identifies what the current public source makes difficult to verify or understand.
Work at PostDew? 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.