Directory submission register

Was the product eligible, which category or audience fit, and what supported that decision?

Which plan was selected, what did it cost, and which material terms or restrictions applied?

Was a reciprocal badge or link required, and how was or will it be implemented?

No reciprocal-link requirement is recorded in the submitted plan or founder report.

What exact submission URL or workflow was available and used?

What did the directory promise about timing, permanence, promotion, analytics, leads, or link treatment?

No host promise about timing, permanence, promotion, analytics, leads, or link treatment is recorded.

Was the attempt accepted, rejected, withdrawn, or still pending, and why?

What response or launch timing was stated or observed, and when is follow-up due?

No platform review timing or follow-up date was returned in recorded evidence.

Was the listing indexable, detected, and still accurate and accessible at scheduled persistence checks?

403 from this host is bot-block, not absence. Rendered Official Website still nofollow noopener.

Did the live listing match the submitted identity, copy, pricing, categories, and assets?

Rendered via third-party fetch after controlled HTTP 403. Name, icon, official website, and description present.

What destination, anchor, rel attributes, redirects, and canonical behavior did the live outbound link use?

Which promised queue timing, permanence, promotion, analytics, leads, or link features were actually delivered?

No host promise was recorded, so delivery cannot be scored. Observed: listing still public at D+30.

What canonical public URL, first-live time, and accessibility state were observed?

Should this channel be continued, upgraded, maintained, removed, or avoided, and why?

Was the product eligible, which category or audience fit, and what supported that decision?

Prepared record exists, but no form action, receipt, outcome, or confirmed terms evidence was recorded. Dropped from the wave at D+7 by default.

Which plan was selected, what did it cost, and which material terms or restrictions applied?

Free listing is conditional on a permanent reciprocal badge. No submission was made.

Was a reciprocal badge or link required, and how was or will it be implemented?

A permanent footer badge was approved for implementation, but the site change has not shipped and is required before submission.

What exact submission URL or workflow was available and used?

Prepared record exists, but no form action, receipt, outcome, or confirmed terms evidence was recorded. Dropped from the wave at D+7 by default.

What did the directory promise about timing, permanence, promotion, analytics, leads, or link treatment?

Prepared record exists, but no form action, receipt, outcome, or confirmed terms evidence was recorded. Dropped from the wave at D+7 by default.

Should this channel be continued, upgraded, maintained, removed, or avoided, and why?

Was the product eligible, which category or audience fit, and what supported that decision?

Which plan was selected, what did it cost, and which material terms or restrictions applied?

Was a reciprocal badge or link required, and how was or will it be implemented?

No reciprocal badge, backlink, or link-to-PeerPush requirement visible on rendered pre-launch listing 2026-08-24.

What exact submission URL or workflow was available and used?

What did the directory promise about timing, permanence, promotion, analytics, leads, or link treatment?

Was the attempt accepted, rejected, withdrawn, or still pending, and why?

Was the listing indexable, detected, and still accurate and accessible at scheduled persistence checks?

Listing live and accurate at the canonical URL 14 days after launch. Published on Aug 25, 2026 still shown. Primary CTA still the tracked profile URL.

Did the live listing match the submitted identity, copy, pricing, categories, and assets?

Compared submitted tagline to live og:description/visible tagline; exact match. Identity TrustGrowth exact. Socials LinkedIn company + X @trustgrowth_ai render.

What destination, anchor, rel attributes, redirects, and canonical behavior did the live outbound link use?

Visit-site CTA carries the full campaign tracking parameters (rel=noopener). Secondary trustgrowth.ai link carries source and ref parameters with rel=sponsored nofollow noopener. Query strings are omitted from this public row.

Which promised queue timing, permanence, promotion, analytics, leads, or link features were actually delivered?

Paid Standard Launch delivered permanent public URL and published on scheduled launch day 2026-08-25. Boosted=false as purchased. Free-queue wait not applicable.

What canonical public URL, first-live time, and accessibility state were observed?

Launch-day render: HTTP 200; UI shows Published on Aug 25, 2026; scheduled phrase absent; Trending Now badge present.

Should this channel be continued, upgraded, maintained, removed, or avoided, and why?

Was the product eligible, which category or audience fit, and what supported that decision?

Which plan was selected, what did it cost, and which material terms or restrictions applied?

Was a reciprocal badge or link required, and how was or will it be implemented?

No recorded SaaSHub badge or reciprocal-link requirement in the reviewed submission or live-placement evidence.

What exact submission URL or workflow was available and used?

What did the directory promise about timing, permanence, promotion, analytics, leads, or link treatment?

No vendor promise about timing, permanence, promotion, analytics, or leads was recorded; acceptance and live status are observed separately.

Was the attempt accepted, rejected, withdrawn, or still pending, and why?

What response or launch timing was stated or observed, and when is follow-up due?

Was the listing indexable, detected, and still accurate and accessible at scheduled persistence checks?

Primary Visit website still empty rel (followed). Unchanged from D+14.

Did the live listing match the submitted identity, copy, pricing, categories, and assets?

What destination, anchor, rel attributes, redirects, and canonical behavior did the live outbound link use?

Which promised queue timing, permanence, promotion, analytics, leads, or link features were actually delivered?

No directory promises were recorded, so delivery cannot be assessed; observed acceptance and live placement are recorded independently.

What canonical public URL, first-live time, and accessibility state were observed?

Should this channel be continued, upgraded, maintained, removed, or avoided, and why?

Was the product eligible, which category or audience fit, and what supported that decision?

Which plan was selected, what did it cost, and which material terms or restrictions applied?

Was a reciprocal badge or link required, and how was or will it be implemented?

No reciprocal-link condition was recorded in the submission evidence.

What exact submission URL or workflow was available and used?

What did the directory promise about timing, permanence, promotion, analytics, leads, or link treatment?

No vendor promise was recorded; current in-review state is observed separately.

Was the attempt accepted, rejected, withdrawn, or still pending, and why?

What response or launch timing was stated or observed, and when is follow-up due?

No platform response-time or follow-up date is recorded; attempt remains in_review.

Was the listing indexable, detected, and still accurate and accessible at scheduled persistence checks?

Post-launch read 2026-09-19: HTTP 200, no redirect. Page shows Launched yesterday. Same canonical URL as the pre-launch page.

Did the live listing match the submitted identity, copy, pricing, categories, and assets?

Post-launch read 2026-09-19: HTTP 200, no redirect. Page shows Launched yesterday. Same canonical URL as the pre-launch page.

What destination, anchor, rel attributes, redirects, and canonical behavior did the live outbound link use?

The directory replaced our tracking parameters with its own ref parameter. Prior reads on 2026-08-23 and 2026-09-08 had no HTML outbound.

Which promised queue timing, permanence, promotion, analytics, leads, or link features were actually delivered?

No vendor promise was recorded, so delivery cannot be scored. Observed: the listing launched on the founder-reported date 2026-09-18.

What canonical public URL, first-live time, and accessibility state were observed?

Post-launch read 2026-09-19: HTTP 200, no redirect. Page shows Launched yesterday. Same canonical URL as the pre-launch page.

Should this channel be continued, upgraded, maintained, removed, or avoided, and why?

Was the product eligible, which category or audience fit, and what supported that decision?

Breadcrumb on the edit surface reads Seo analysis > TrustGrowth, confirming category placement matches our positioning.

Which plan was selected, what did it cost, and which material terms or restrictions applied?

Supersedes the 2026-08-18 answer that recorded receipt not_yet_provided and tax unknown.

Was a reciprocal badge or link required, and how was or will it be implemented?

No reciprocal backlink is demanded. The listing does enable a vendor discount-code commitment, which is a pricing obligation. Whether that code is redeemable in billing is not verified and is open.

What exact submission URL or workflow was available and used?

The route is the authenticated vendor dashboard, not a public form. The earlier paid-path exclusion for this wave was superseded by an approved paid path.

What did the directory promise about timing, permanence, promotion, analytics, leads, or link treatment?

Vendor states no ranking or traffic promise anywhere on the edit surface. An analytics surface exists and is the D+7/D+30 outcome source.

Was the attempt accepted, rejected, withdrawn, or still pending, and why?

Ledger selection moved hold -> selected on 2026-08-19 after primary-source verification. No live-listing claim is made until the public page is verified.

What response or launch timing was stated or observed, and when is follow-up due?

Controlled HTTP to the public listing returns 403 to us, so placement verification is an operator browser check, not an automated probe.

Was the listing indexable, detected, and still accurate and accessible at scheduled persistence checks?

Founder attested live on 2026-08-20 with a screenshot. D+30 third-party fetch still renders the listing. Rank 2277 (was 2309). Views 205 (was 134).

Did the live listing match the submitted identity, copy, pricing, categories, and assets?

Deltas are vendor taxonomy normalisation, not copy we supplied; no correction requested.

What destination, anchor, rel attributes, redirects, and canonical behavior did the live outbound link use?

Tracked query string withheld from the public value; the full tracked href is held in the private ledger

Which promised queue timing, permanence, promotion, analytics, leads, or link features were actually delivered?

The public discount claim was the only claim-risk item in this listing; it is now backed by a real, checked discount rather than an intention.

What canonical public URL, first-live time, and accessibility state were observed?

Rendered capture of the live profile; plain HTTP clients receive a 403 bot challenge, so a rendered capture is the only usable observation method for this channel.

Should this channel be continued, upgraded, maintained, removed, or avoided, and why?

Was the product eligible, which category or audience fit, and what supported that decision?

Which plan was selected, what did it cost, and which material terms or restrictions applied?

Vendor list price is the directory's published price. What we paid, the invoice reference and the issuing entity are withheld from the public projection.

Was a reciprocal badge or link required, and how was or will it be implemented?

No reciprocal-link requirement is recorded.

What exact submission URL or workflow was available and used?

What did the directory promise about timing, permanence, promotion, analytics, leads, or link treatment?

Was the attempt accepted, rejected, withdrawn, or still pending, and why?

What response or launch timing was stated or observed, and when is follow-up due?

Was the listing indexable, detected, and still accurate and accessible at scheduled persistence checks?

D+30 placement check 25 by Distribution: rendered, HTTP 200, listing identity present, tracked outbound present.

Did the live listing match the submitted identity, copy, pricing, categories, and assets?

What destination, anchor, rel attributes, redirects, and canonical behavior did the live outbound link use?

Which promised queue timing, permanence, promotion, analytics, leads, or link features were actually delivered?

What canonical public URL, first-live time, and accessibility state were observed?

Should this channel be continued, upgraded, maintained, removed, or avoided, and why?