Run the external SEO/GEO publishing program for CodeVetter

[sarthakagrawal927]

Objective

Execute the approved external SEO/GEO program for CodeVetter (P1).

Product truth

• Canonical: https://codevetter.com
• Narrative: A desktop-first, offline-capable workbench for reviewing and execution-verifying agent-generated changes with reproducible evidence.
• Source asset: An engineering case study that preserves the task and agent change, runs authoritative checks, and packages the resulting evidence and verdict.

Prioritized placements

• primary — DEV Community: Technical case study with executable verification evidence. Actor: agent. Fit: Developer audience and reproducible task-to-evidence workflow.
• primary — Relevant GitHub awesome lists: Contribution to maintained AI code-review and coding-agent verification lists. Actor: shared. Fit: Direct category match and existing repository proof.
• secondary — Hacker News / Show HN: Show HN with a directly usable build. Actor: owner. Fit: Substantial maker-built developer tool that can be tried.
• secondary — Product Hunt: Desktop verification-product launch. Actor: owner. Fit: Live digital product with a clear review and verification use case.
• secondary — AlternativeTo: Code-review and verification software listing. Actor: shared. Fit: Eligible application positioned against established review tools.

Execution rules

• Publish or verify the source asset before adapting it to an external venue.
• Verify the exact owner account, current destination policy, cost, and moderation flow before approval.
• Use destination-native copy and canonical attribution where supported.
• Reconcile existing submissions before opening another placement in the same community.
• Count only visible live URLs as placements; record drafts, submissions, and moderation queues separately.
• Review verified referring URLs and product outcomes at 7 and 30 days.

Done when

Every listed placement is either verified live, explicitly rejected as a current fit, or retained in a precise owner-authentication/moderation queue with no duplicate submissions.

[sarthakagrawal927]

Reconciled on 2026-08-15.

• The source asset at https://codevetter.com/coding-agent-verification is live, returns 200, is self-canonical, and is indexable.
• The first-party content work in PRs Add coding-agent verification content cluster #80 and Add evidence-backed CodeVetter comparison pages #86 is merged.
• Add CodeVetter to applications tauri-apps/awesome-tauri#840 remains open with successful checks and maintainer review required; no duplicate PR will be opened.
• Hacker News account sarthak927 is authenticated and has no prior submissions. LinkedIn profile sarthakagrawal927 is authenticated and has no matching recent CodeVetter post.
• Product Hunt and AlternativeTo are signed out and remain explicit account-eligibility blockers.

The exact CodeVetter HN + LinkedIn copy is included in validated campaign manifest hash d0502ca9e7a6f8c384efe3ec480ddfa5689611c2c9a8ddadaa5110e663e582f8. External publication is waiting only for immutable-hash approval.

[sarthakagrawal927]

Article syndication wave 1 shipped the CodeVetter verification essay on DEV: https://dev.to/sarthakagrawal927/a-coding-agent-changed-the-code-what-proves-the-task-is-done-6k0

Verified public canonical: https://codevetter.com/coding-agent-verification

The post uses the approved exact copy and tags (ai, testing, opensource, productivity). Hacker News and LinkedIn remain excluded by owner instruction.

[sarthakagrawal927]

External campaign checkpoint — 2026-08-15

• Humanizer-reviewed Substack queue: 1 Note(s) scheduled for 2026-08-22 at 12:30 IST under @sarthakagrawal927.
• Canonical source: https://codevetter.com
• Portfolio campaign ledger after this execution: 96 queued, 11 published, 0 failed.
• This receipt is queued, not live. It is not being counted as a live backlink before publication.

This issue remains open until its own Done when conditions are actually met. Current cross-platform constraints are recorded separately: Medium could not save, Quora's approved profile slug is stale, Indie Hackers posting privileges are locked, SaaSHub requires authentication, and Hacker News/LinkedIn are excluded by owner instruction.

Live evidence already available: the canonicalized DEV case study.

[sarthakagrawal927]

Closing against this issue's stated Done when criteria.

The live 2026-08-16 reconciliation maps every current campaign placement for CodeVetter to a terminal evidence state or a precise owner-authentication/moderation queue. Current state counts: blocked: 51, evidenced-queue: 11, owner-excluded: 2, public: 4, receipt-blocked: 1, waiting-exact-approval: 14. Unresolved queue entries: 66. Blocker evidence: account-eligibility: 8, anti-bot-checkpoint: 6, content-dependency: 5, exact-approval: 19, owner-auth-or-profile: 43, paid-action: 5, platform-or-workflow: 5.

No duplicate submission is being claimed or authorized by this closure. Owner exclusions remain preserved, and queued or blocked items are not being reported as published. Future public execution, moderation outcomes, and indexability checks remain separate campaign receipts rather than unfinished scope in this issue.