# AGENTS.md: make the Apify actor eliai/snoffle-report easy for buyers and AI agents to find and choose

This task file came from a Snoffle report (2026-10-31: the listing reads 84/100, store search finds it 0/100). Work through it in order, run each Verify line, then re-check.

You are improving the Apify Store listing of eliai/snoffle-report (https://apify.com/eliai/snoffle-report) so buyers and AI agents searching the Apify Store find it and choose it.
Snoffle checked it on 2026-10-31: the listing reads 84/100; store search finds it 0/100. Apply the 6 changes below, in order. Change only what each step says; keep the actor's code and behaviour as they are.

The listing lives in two places: Apify Console (your actor → Publication: title, description, icon, categories, SEO, monetization) and the actor's files (`.actor/actor.json`, `.actor/input_schema.json`, the README). Files only reach the store after a rebuild. Never put an API token in any file.

## 1. Make the store title the task, in the words buyers search
Snoffle saw: Title: "Snoffle: AI Search & Agent-Readiness Report for Any Product URL" (63 characters; Snoffle's range is 10 to 60). Task word: "Search".
In Apify Console → your actor → Publication, set the title to the job it does in buyer words, 60 characters or fewer, task words first (for example "AI Search & Agent-Readiness Report for Any Product URL", 54 characters, the current title without its brand prefix). Snoffle searched the store for: "ai search agent-readiness report", "seo report". Put the same title in `.actor/actor.json` ("title") so a later build does not change it back.
Verify: curl -s https://api.apify.com/v2/acts/eliai~snoffle-report | grep -o '"title": *"[^"]*"' | head -1  → the new title, 60 characters or fewer

## 2. Make the store description say what, from what, into what, for whom
Snoffle saw: The description names what it does ("searches"), the input ("URL"), the output ("returns"); it never says who it is for (plain-rules check: present, clarity not judged).
In Apify Console → Publication, rewrite the description as one or two plain sentences, 80 to 300 characters: what it does, the input it takes, what you get back, and who it is for. It is missing who it is for. Shape: "[what it does] from [input]. Returns [output]. For [fill in: who it is for, e.g. "SEO agencies"]." Keep `.actor/actor.json` ("description") the same.
Verify: curl -s https://api.apify.com/v2/acts/eliai~snoffle-report | grep -o '"description": *"[^"]*"' | head -1  → names the input, the output and who it is for

## 3. Use the words buyers search in the title, description and README
Snoffle saw: Apify Store search: not in the 83 results it returned (top: white-lion-studio/white-label-seo-audit, eliai/seo-audit-report, taroyamada/csv-local-business-list-scoring-report).
Apify Store search did not rank this actor near the top for: "seo report" (not in the 83 results it returned). Put those exact words where store search reads them: the title (if it still reads naturally), the first sentence of the description, and the README's first heading and first paragraph. Open the actors that rank instead (https://apify.com/white-lion-studio/white-label-seo-audit, https://apify.com/eliai/seo-audit-report, https://apify.com/taroyamada/csv-local-business-list-scoring-report) and note the words their titles and descriptions use for the same job. Then rebuild (`apify push`, or Build in Apify Console) so the store shows the new build.
Verify: curl -s "https://api.apify.com/v2/store?search=seo%20report&limit=25" | grep -c '"name": *"snoffle-report"'  → 1 once it is in the first 25 (re-check on Snoffle in a few days; ranking takes time)

## 4. Prefill the input with a real example so the first run succeeds
Snoffle saw: Input schema: 1 field, 1 prefilled (url = https://example.com); placeholder value in url, so the first run shows a sample, not a real result.
In `.actor/input_schema.json`, give "url" a "prefill" with a real example a buyer would use, not a placeholder:
```json
"url": {
  "title": "[keep]",
  "type": "[keep]",
  "prefill": "[fill in: a real example input that returns real output]"
}
```
If a real run costs money, keep the run for that exact example free or cheap. Then rebuild (`apify push`, or Build in Apify Console) so the store shows the new build.
Verify: curl -s https://api.apify.com/v2/acts/eliai~snoffle-report/builds/default | grep -o '\\"prefill\\": *[^,]*'  → the real example; then press Start on https://apify.com/eliai/snoffle-report with no edits: the run ends green with real results

## 5. Set the SEO title and SEO description Google shows
Snoffle saw: SEO title: not set; SEO description: not set.
In Apify Console → your actor → Publication, set the SEO title (60 characters or fewer) and the SEO description (155 characters or fewer) using the words buyers type into Google, such as "ai search agent-readiness report", "seo report", plus what it returns.
Verify: curl -s https://api.apify.com/v2/acts/eliai~snoffle-report | grep -o '"seo\(Title\|Description\)": *"[^"]*"'  → both lines

## 6. Upload an icon for the store card
Snoffle saw: No icon is set (the listing has no picture URL).
In Apify Console → your actor → Publication, upload a square icon (PNG, at least 256×256) that shows the site or data it works on, so the store card is not blank.
Verify: curl -s https://api.apify.com/v2/acts/eliai~snoffle-report | grep -c '"pictureUrl"'  → 1

When all steps are live, re-check, but only if your Snoffle key has reports left (`access.reportsLeft` > 0 on its last report): GET https://snoffle.broke2builtai.com/api/check?fresh=1&url=https%3A%2F%2Fapify.com%2Feliai%2Fsnoffle-report with the key in the x-snoffle-key header (fresh=1 runs a new check and uses one report), then read `delta`. If there is no key or no report left, do not pay for one: tell your human the re-check costs a new report and let them decide.
Report back the new score and any step you could not apply, with the reason.
