# Snoffle: tickets from a Snoffle report (2026-10-31)

For a dev team. Each ticket says what to change, why, where, and how you know it is done. Do them in order; the first ones move the score most.

## Why this matters

At $29 per "Snoffle reports" event, every 10 of them is about $232 to you after Apify's 20% cut (before platform usage). What is in the way: people searching the Apify Store for this job do not see you yet, so few get the chance to run it.

Your score stays at 40 or below while Store search does not show it and nobody uses it yet, however good the listing is. It lifts when Store search shows the actor for the words buyers type, and when people run it and leave a rating. The listing fixes still count: they are what turns the first visitors into users.

Score today: 31/100 (listing reads 84, found 0, used and rated 8).

## Tickets

### T1. Make the store title the task, in the words buyers search
- Why: 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".
- Where: `.actor/actor.json`
- Done when: curl -s https://api.apify.com/v2/acts/eliai~snoffle-report | grep -o '"title": *"[^"]*"' | head -1  → the new title, 60 characters or fewer

<details><summary>The exact change</summary>

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.

</details>

### T2. Make the store description say what, from what, into what, for whom
- Why: 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).
- Where: `.actor/actor.json`
- Done when: 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

<details><summary>The exact change</summary>

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.

</details>

### T3. Use the words buyers search in the title, description and README
- Why: 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).
- Where: Apify Console, the actor's Publication tab (or the actor files named in the change)
- Done when: 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)

<details><summary>The exact change</summary>

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.

</details>

### T4. Prefill the input with a real example so the first run succeeds
- Why: 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.
- Where: `.actor/input_schema.json`
- Done when: 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

<details><summary>The exact change</summary>

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.

</details>

### T5. Set the SEO title and SEO description Google shows
- Why: Snoffle saw SEO title: not set; SEO description: not set.
- Where: Apify Console, the actor's Publication tab (or the actor files named in the change)
- Done when: curl -s https://api.apify.com/v2/acts/eliai~snoffle-report | grep -o '"seo\(Title\|Description\)": *"[^"]*"'  → both lines

<details><summary>The exact change</summary>

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.

</details>

### T6. Upload an icon for the store card
- Why: Snoffle saw No icon is set (the listing has no picture URL).
- Where: Apify Console, the actor's Publication tab (or the actor files named in the change)
- Done when: curl -s https://api.apify.com/v2/acts/eliai~snoffle-report | grep -c '"pictureUrl"'  → 1

<details><summary>The exact change</summary>

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.

</details>

## Not code: what lifts the rest of the score

- Buyers searching the Apify Store do not find you
- Almost nobody uses it yet
- It has no good reviews yet

## Rules while you work

- Make only the change each task describes; keep the look, copy and behaviour otherwise.
- Never put an API key, token or password in any file.
- A run with {} as input must still succeed: Apify runs every public actor that way and quietly delists it when it fails.
- No link to a site outside apify.com in README.md, .actor/actor.json or the input schema text (Apify Store terms 2.2.4.2). Sample input URLs inside code blocks are fine.
- Do not change the price, the charge events or the visibility.
- Files reach the Store only after a build; open a pull request and let a person approve the build.

When it is deployed, re-check the same URL with Snoffle and compare the numbers.
