A buyer's AI would skip Snoffle and name white-lion-studio/white-label-seo-audit instead.
Snoffle score
The listing reads about 100 with the fixes on your listing.
About 37 once the fixes on your listing are done.
This is a real saved report on Snoffle, our own Apify actor, checked October 31, 2026 from the Apify Store's public data. It is the plain-rules check; a paid report adds the buyer's-agent run. Yours will look like this.
Check my site freeAt $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.
How this score works
readable 35% · found 40% · mentioned 25%, capped at 40 while found and mentioned are both under 20.
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.
Who's fixing this?
Pick who. That person gets the whole job, written for them.


You don't need to learn any of this.
One thing at a time. Tick it, and the next one opens.
There are 5 changes on it. You never need to read them. Use a button under this list, whether or not you have a web person.
Say what it does, and post it where your buyers already look. Then ask your first users to say in public that it worked. See what to post.
When the changes are live, run the check again and see what moved. Run a free check.
That's the whole list. Nice work.
Send the listing list to my web person
Paste it once. Your agent does the rest.
For Cursor, Claude Code, Lovable, Bolt or Replit. 6 steps, each with a way to check it. It stops and asks you before a price or a name.
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.
AGENTS.md goes in your project folder; Claude Code, Cursor and Codex read it. Or download the prompt as .md. Your listing kit, ready to paste: the title, description and README sections written for your actor.
Please make these 6 changes to Snoffle's listing.
Snoffle checked it on October 31, 2026. Each ticket says what, why, where and how you know it's done.
Email these tickets
Make the store title the task, in the words buyers search
- Why
- 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
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.Make the store description say what, from what, into what, for whom
- Why
- 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
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.Use the words buyers search in the title, description and README
- Why
- 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
- The page at https://apify.com/eliai/snoffle-report
- 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)
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.
Prefill the input with a real example so the first run succeeds
- Why
- 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
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.Set the SEO title and SEO description Google shows
- Why
- SEO title: not set; SEO description: not set.
- Where
- The page at https://apify.com/eliai/snoffle-report
- Done when
- curl -s https://api.apify.com/v2/acts/eliai~snoffle-report | grep -o '"seo\(Title\|Description\)": *"[^"]*"' → both lines
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.
Upload an icon for the store card
- Why
- No icon is set (the listing has no picture URL).
- Where
- The page at https://apify.com/eliai/snoffle-report
- Done when
- curl -s https://api.apify.com/v2/acts/eliai~snoffle-report | grep -c '"pictureUrl"' → 1
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.
# 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.
I need a decision: a yes to start.
Here's why. AI tools aren't sending buyers to Snoffle. Snoffle checked on October 31, 2026.
Who gets named instead
When buyers search, they find white-lion-studio/white-label-seo-audit and taroyamada/csv-local-business-list-scoring-report instead of Snoffle.
AI tools read taroyamada/csv-local-business-list-scoring-report at 92 out of 100 and eliai/seo-audit-report at 87 out of 100 and white-lion-studio/white-label-seo-audit at 78 out of 100. They read Snoffle at 84.
What it takes
- 5 listing changes. Our web person or an AI agent can do them.
- 3 listings and mentions. For marketing.
- 0 decisions. These need you.
Snoffle measures what AI tools and Google show on the day it checks. It can't promise rankings or sales.
Email this page
Please do these 3 things so buyers can find Snoffle.
No coding agent can do this part.
Email this list
# Snoffle: what to post, from a Snoffle report (2026-10-31) ## 1. Google doesn't show it for a buyer's second question Buyer's question: "seo report" - What to do: Rank for "seo report" in Apify Store search: put those words in the store title, the first sentence of the description and the README's first heading - What 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). ## 2. Almost nobody uses it yet - What to do: Get the first users from where your buyers already are: a post in their community, a link from your site and docs to the store page - What Snoffle saw: 2 total users, 1 in the last 30 days; 13 runs in all. ## 3. It has no good reviews yet - What to do: Ask your first users who got a good result to leave an Apify Store review - What Snoffle saw: No reviews yet; 0 bookmarks.
Google doesn't show it for a buyer's second question
“seo report”
- What to do
- Rank for "seo report" in Apify Store search: put those words in the store title, the first sentence of the description and the README's first heading
What 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).
Almost nobody uses it yet
- What to do
- Get the first users from where your buyers already are: a post in their community, a link from your site and docs to the store page
What Snoffle saw
2 total users, 1 in the last 30 days; 13 runs in all.
It has no good reviews yet
- What to do
- Ask your first users who got a good result to leave an Apify Store review
What Snoffle saw
No reviews yet; 0 bookmarks.
Prepared for Snoffle by
Your agency's name
AI tools aren't sending buyers to you yet.
A buyer's AI picked white-lion-studio/white-label-seo-audit. We found 8 things to fix. Our team handles the 5 listing changes. We need 0 decisions from you, and then we re-check together.
Run it for every client.
Run it on a prospect before the call, or on every client. Reports under your own name are coming with Agency.
Agency will be $399 a month. It isn't open yet: tell us and we'll let you know.
See agency pricingSee all the detailAll the fixes Snoffle finds, who wins instead, and every check with its evidence
All 8 fixes
Most valuable first. Each one is in the prompt for your coding agent, with how to check it worked.
Google doesn't show it for a buyer's second questionMarketing
- The fix
- Rank for "seo report" in Apify Store search: put those words in the store title, the first sentence of the description and the README's first heading
- What 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).
- Worth
- +100 · found
- Effort
- minutes
Your store title does not say the job in buyer wordsWeb person or agent
- The fix
- Rewrite the Apify Store title as the task in buyer words, 60 characters or fewer
- What 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".
- Worth
- +17 · name
- Effort
- minutes
Almost nobody uses it yetMarketing
- The fix
- Get the first users from where your buyers already are: a post in their community, a link from your site and docs to the store page
- What Snoffle saw
- 2 total users, 1 in the last 30 days; 13 runs in all.
- Worth
- +42 · mentions
- Effort
- days
Your description does not say what it does, from what, for whomWeb person or agent
- The fix
- Make the Apify Store description say who it is for in one or two plain sentences
- What 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).
- Worth
- +13 · readable
- Effort
- minutes
It has no good reviews yetMarketing
- The fix
- Ask your first users who got a good result to leave an Apify Store review
- What Snoffle saw
- No reviews yet; 0 bookmarks.
- Worth
- +50 · mentions
- Effort
- days
Your store card has no iconWeb person or agent
- The fix
- Upload an Apify Store icon that shows the job at a glance (the site or data it works on)
- What Snoffle saw
- No icon is set (the listing has no picture URL).
- Worth
- +14 · readable
- Effort
- minutes
Google gets no summary written for your listingWeb person or agent
- The fix
- Set the SEO title and SEO description on the Apify listing with the words buyers type into Google
- What Snoffle saw
- SEO title: not set; SEO description: not set.
- Worth
- +14 · readable
- Effort
- minutes
A first run with no edits does not show real resultsWeb person or agent
- The fix
- Replace the placeholder prefill in .actor/input_schema.json with a real example input that shows real output
- What 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.
- Worth
- +7 · readable
- Effort
- minutes
The listing reads 84 now, about 88 with the top three, about 100 with all the fixes. Ranking in store search takes the right words, users, reviews and time.
When people ask, do they find you?
| What they ask | Apify Store | |
|---|---|---|
| ai search agent-readiness report | #1 of 2 | n/a |
| seo report | Not in the 83 returned | n/a |
Found instead of you
- white-lion-studio/white-label-seo-audit
- eliai/seo-audit-report
- taroyamada/csv-local-business-list-scoring-report
- enezli/ai-competitor-intelligence
- wrenfield-data/seo-agency-report
You can beat them
Your own actor eliai/seo-audit-report outranks this one: make each answer a different search, or point one at the other. white-lion-studio/white-label-seo-audit ranks above you once (best #1) with 3 users; you have 2. After your fixes your listing reads 100/100 to Snoffle against their best 92/100: the gap is store rank and reviews, not the listing.
Products shown instead of you
- white-lion-studio/white-label-seo-audit · reads 78/100 to AIHas: 3 users, no reviews, $0.015 per "Page analysed" event, a prefilled input that runs first time, a task-word title, an icon
- eliai/seo-audit-report · reads 87/100 to AIHas: your own actor, 2 users, no reviews, $0.04 per "Generated SEO reports" event (price on the free Apify plan), a prefilled input that runs first time, a task-word title, an icon
- taroyamada/csv-local-business-list-scoring-report · reads 92/100 to AIHas: 2 users, no reviews, $3 per "Lead scoring report" event, a prefilled input that runs first time, a task-word title, a clear price, an icon
What it would sell for
Appraisal, 2026-10-31, from the prices and public signals Snoffle read.
- Your price
- $29 per event ("Snoffle reports") (Apify Store pricing, read 2026-10-31)
Not enough comparable prices to appraise. Snoffle read 2 comparable prices from the products shown for your buyers' questions; a price band needs 3. No guess is made in its place.
- White Label SEO Audit Report: $0.015 per event (Apify Store pricing, read 2026-10-31)
- SEO Audit Report - White-Label HTML Site Audit, Up to 300 Pages: $0.04 per event (your own; Apify Store pricing, read 2026-10-31)
- CSV Local Business List Scoring & SEO Gap Report: $3 per event (Apify Store pricing, read 2026-10-31)
Snoffle could not place your price: it needs your price and a band of comparable prices on the same basis.
Traffic, from public signals
1 user and 1 successful run in the last 30 days (Apify's public Store stats (the same public API the listing check reads), read 2026-10-31)
- You: 1 user and 1 successful run in the last 30 days
- White Label SEO Audit Report: 2 users and 28 successful runs in the last 30 days
- SEO Audit Report - White-Label HTML Site Audit, Up to 300 Pages: 1 user and 29 successful runs in the last 30 days
- CSV Local Business List Scoring & SEO Gap Report: 0 users and 28 successful runs in the last 30 days
What it earns a year, estimated from public signals
- At your price today ($29)
- $348 a year (gross: what Apify users pay, before Apify's 20% and any platform costs; 1 successful run in 30 days; assumes one charged event per run)
How this was worked out
Successful runs in the last 30 days (Apify's public stats) × the per-event price × 12, assuming one charged event per run. Gross: what Apify users pay, before Apify's 20% and any platform costs.
- At your price today: 1 successful run in 30 days (measured: Apify's public Store stats (the same public API the listing check reads)) × $29 per event (measured: your Store price), assumes one charged event per run (assumed: Apify publishes runs, not events) = $29 a month; × 12 = $348 a year, gross: what Apify users pay, before Apify's 20% and any platform costs.
Your fixes target the buyer questions where you are not named; we can't measure how many visits each question brings, so we don't put a dollar figure on them.
Why this verdict
- 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).
- Title: "Snoffle: AI Search & Agent-Readiness Report for Any Product URL" (63 characters; Snoffle's range is 10 to 60). Task word: "Search".
- 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).
- 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.
Checked as an Apify actor: its store listing, README and input schema read from the public Apify API, and its rank in live Apify Store search.
“Just snoffle it”
83/100. For an Apify actor the name buyers see is its store title; the title check scores it.
Scores by area, and all 16 checks
| Status | Check | Points |
|---|---|---|
| fail | Found for "seo report" 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). | 0/100 |
| partial | Store title names the task in buyer words Title: "Snoffle: AI Search & Agent-Readiness Report for Any Product URL" (63 characters; Snoffle's range is 10 to 60). Task word: "Search". | 25/30 |
| pass | Store description is a usable length Description (260 characters): "Give a product URL. Snoffle searches Google and AI assistants with the questions buyers ask, asks a buyer's agent whether it would buy, and returns the score, …" | 15/15 |
| pass | README has Input, Output, Example, Pricing and Limits README (6,744 characters) has Input ("Input"), Output ("What one report contains"), Example ("A real example (our own product, checke…"), Pricing ("Pricing"), Limits ("Speed and limits"). | 25/25 |
| fail | Listing has an icon No icon is set (the listing has no picture URL). | 0/10 |
| pass | Store categories are set Categories: seo tools, ai. | 10/10 |
| fail | SEO title and description for Google SEO title: not set; SEO description: not set. | 0/10 |
| partial | Description says what, from what input, what output, for whom 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). | 30/40 |
| pass | Price is clear $29 per "Snoffle reports" event, described as "One complete Snoffle report for one URL: scores, buyer's-agent verdict, top fixes and the coding-ag…". The README states $29. | 30/30 |
| pass | No hidden instructions aimed at agents No prompt-injection text found in the description or README. | 10/10 |
| partial | Input is prefilled so the first run succeeds 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. | 25/30 |
| pass | Shows recent activity Last build today; last run started today. | 20/20 |
| pass | Runs succeed Public runs in the last 30 days: 1 of 1 succeeded (100%). | 20/20 |
| partial | People use it 2 total users, 1 in the last 30 days; 13 runs in all. | 8/50 |
| fail | Reviews and rating No reviews yet; 0 bookmarks. | 0/50 |
| pass | Searching its own words finds it ("ai search agent-readiness report") Apify Store search: #1 of the 2 results it returned. Every word of this search is in the title, so it shows the title finds itself, not that buyers find it. | 10/10 |
Read as an Apify actor: the store listing, README and input schema from the public Apify API, and its rank from Apify Store search. Google rank for "apify <task>" not measured (no search key configured); Found is Apify Store search only. The AI-assistant reading and the name search were not run on this report.
Checked 2026-10-31T22:15:48.502Z in 58 ms. JSON: /example/apify.json (the saved copy; opening it uses nothing)
What do these words mean?
- input schema
- The form Apify shows before a run; its prefilled values decide whether a first run just works.
- SEO title
- The title and summary Google shows for your listing, set apart from the Store card.
- README
- The long description on your actor page; buyers read it before they run anything.

