Missing search visibility is a symptom, not proof that your app is broken. First isolate fixable public manifest, association, asset, and WAF failures. Then treat registration, genuine usage, and client indexing as separate signals.
It checks the public manifest, page embed, response headers, and referenced assets. It cannot prove search eligibility, engagement thresholds, ranking, or future visibility.
Work from public bytes outward. Stop when a layer fails, fix that layer, and re-fetch the deployed result before drawing conclusions about search or ranking.
Open the exact production launch URL directly, then fetch its manifest fromhttps://your-domain/.well-known/farcaster.json without a browser session. A working direct link proves only that the page is reachable. It does not prove that a client indexed the app, accepted the manifest, or can fetch the same bytes server-side.
Use Farcaster's manifest tool for the production domain. Check that the manifest is complete, that noindex is not set to true, and that required discovery fields such as name, homeUrl, iconUrl, and description are present. Development tunnels are not production discovery domains.
The signed accountAssociation.payload.domain must match the manifest FQDN exactly, including the subdomain. Verify the signature rather than merely decoding the payload. Fetch the icon and every discovery image at their final URLs, then check status, MIME type, bytes, dimensions, aspect ratio, and transparency. A URL-shaped string is not evidence that an image is usable.
Bot protection can let your own browser through while challenging Farcaster's server-side manifest or image fetch. Treat this as a hypothesis only when an unauthenticated request returns HTML, a challenge, or an unexpected status. On Vercel, use the documented narrowly scoped WAF bypass for the required public paths. Do not disable protection site-wide or invent an IP allowlist.
Keep a clean unauthenticated re-fetch after the narrow rule change, including its final response hash.Farcaster's discovery documentation says search depends on recent opens, additions, and other engagement signals as well as valid metadata. The public docs do not provide a numeric threshold that an external audit can prove you have met. Do not buy fake opens, automate additions, or call a technically clean manifest a guarantee of visibility.
Record genuine usage evidence separately from transport, schema, and asset checks.After changing a public blocker, deploy, fetch the exact production bytes again, and refresh the official manifest tool. Indexing can lag, but delay is not a diagnosis. If the public evidence is clean and the app still does not appear, report the timestamp, domain, manifest-tool result, and sanitized evidence to the relevant client or platform. Do not repeatedly submit unchanged data.
Keep before-and-after hashes and the final tool result; never publish private keys or auth tokens.TLMNT can capture public transport, JSON, association, embed, and asset evidence. It cannot observe a client's private indexing queue or guarantee that engagement-based search criteria are met.
A technically valid app may remain absent from search. A visible app may still contain broken public evidence. Keep those claims separate.
Product criteria change. Official Farcaster documentation is the source of truth. The community link documents the symptom only; it is not evidence of a universal root cause.
TLMNT accepts a repair only when one technical failure can be reproduced and scoped. You grant only the access needed for that fix. Payment is requested only after before-and-after evidence is delivered and you verify the result. We do not sell fake engagement or promise search placement. Submitting the form authorizes neither access nor payment.