From fe5e8b6cf4e1997b98961f09a824a31da2e8224e Mon Sep 17 00:00:00 2001 From: Justin Gagne Date: Wed, 5 Aug 2026 19:12:04 +0200 Subject: [PATCH 1/7] docs: update publish task naming and add unpublish section - Fixes the SEO title field label mismatch with its own required-field error. - Renames the Publication tab to Publishing. - Renames the Display information section to Page details. - Renames SERP preview to Google preview. - Fixes Page preview and Google preview from Title Case to sentence case. - Renames the Examples tab to Example tasks. - Removes redundant phrasing across the page. - Adds a section on unpublishing a task. - Placeholder: unpublish screenshot pending capture. - Placeholder: Publish status filter pending shipping. --- .../actors/publishing/publish-task.mdx | 66 ++++++++++--------- 1 file changed, 34 insertions(+), 32 deletions(-) diff --git a/sources/platform/actors/publishing/publish-task.mdx b/sources/platform/actors/publishing/publish-task.mdx index ca7ca87c9e..c6dddc5347 100644 --- a/sources/platform/actors/publishing/publish-task.mdx +++ b/sources/platform/actors/publishing/publish-task.mdx @@ -5,7 +5,7 @@ slug: /actors/publishing/publish-task sidebar_position: 2 --- -[Actor tasks](/actors/running/tasks) are shareable, pre-configured inputs for your Actors. [Publishing a task](#publish-your-tasks) creates a public landing page that shows what the Actor does, what inputs it uses, and what output to expect. Public tasks also appear in your Actor's **Examples** tab, which helps users discover your Actor through search engines and AI agents. For monetized Actors, this can lead to more page views, more runs, and more revenue. +[Actor tasks](/actors/running/tasks) are shareable, pre-configured inputs for your Actors. [Publishing a task](#publish-your-tasks) creates a public landing page that shows what the Actor does, what inputs it uses, and what output to expect. Public tasks also appear in your Actor's **Example tasks** tab, which helps users discover your Actor through search engines and AI agents. You can create up to 50 tasks per Actor. @@ -27,7 +27,7 @@ The best tasks aim to solve a problem a user actually has. Instead of publishing For example, if you maintain Google Maps, Amazon, and Yahoo scraper Actors: -| ❌ Weak task | ✅ Strong task | +| Generic task | Specific task | | --- | --- | | Google Maps - default config | Find dentists in San Francisco with reviews | | Test run 2 | Extract restaurant emails for local marketing | @@ -35,11 +35,11 @@ For example, if you maintain Google Maps, Amazon, and Yahoo scraper Actors: | Amazon default | Monitor Amazon product prices and reviews for market research | | Yahoo Finance test | Track stock prices and news on Yahoo Finance | -Each strong task focuses on a specific industry, location, or workflow. A user searching for "dentist data San Francisco" is far more likely to land on a page with that exact framing. +Each strong task focuses on a specific industry, location, or workflow. A user searching for "dentist data San Francisco" is more likely to land on a page with that exact framing. ### Target search traffic and AI discovery -Each landing page is indexed by search engines and includes a markdown (`.md`) version that AI agents can access directly, making your task discoverable through AI-powered search and AI assistants. +Each landing page is indexed by search engines and includes a markdown (`.md`) version that AI agents can access directly, making your task discoverable through AI search and AI assistants. Think of each task as a keyword-targeted landing page: @@ -59,28 +59,26 @@ If your Actor supports multiple use cases, publish a task for each one. A web sc Once your task runs reliably and produces the output you want users to see, publish it from Apify Console. -1. From your task's page in Apify Console, open the **Publication** tab. -1. Complete the three sections: [Display information](#display-information), [Input](#input), and [Dataset schema](#dataset-schema). -1. Click **Publish task**. +1. From your task's page in Apify Console, open the **Publishing** tab. +1. Complete the three sections: [Page details](#page-details), [Input](#input), and [Dataset schema](#dataset-schema). +1. Select **Publish task**. -![Publication tab on a task page.](./images/public-tasks/task-publication-tab.webp) +![Publishing tab on a task page.](./images/public-tasks/task-publication-tab.webp) -### Display information +### Page details -This section controls how your task appears on the public task landing page and in search results. - -There are three fields in this section: +This section controls how your task appears on the landing page and in search results. - **Slug:** the URL-friendly name used in the task's landing page URL. -- **SEO task title:** shown as the heading on the landing page and as the page title in search results. +- **SEO title:** appears as the heading on the landing page and as the page title in search results. - **SEO description:** appears under the title on the landing page and as the meta description in search results. -You can live preview how the fields propagate on the right (they update as you type): +You can live preview how the fields propagate on the right: -- **Page Preview:** how the landing page will look to visitors. -- **SERP Preview:** how the page will appear in search engine results pages (SERPs). +- **Page preview:** how the landing page will look to users. +- **Google preview:** how the page will appear in search results. -![Display information section with page and SERP previews.](./images/public-tasks/task-display-information.webp) +![Page details section with page and Google previews.](./images/public-tasks/task-display-information.webp) :::tip Title format @@ -98,17 +96,12 @@ Avoid titles like "Google Maps scraper - task 3" or "Test task" that describe th ### Input -The Input section controls which fields from your task's input configuration appear on the public landing page. By default, every field defined in your task input is selected. Deselect any field that is not relevant to the task's use case. +The Input section controls which fields from your task's input configuration appear on the landing page. Every input field is selected by default. Deselect any field that isn't relevant to this task's use case. This control affects display only. The task itself always runs with the full input configuration, regardless of which fields are selected here. ![Input section with field selection.](./images/public-tasks/task-input-section.webp) -Use this section to: - -- Show only the fields that demonstrate how the task is configured for its specific use case. -- Hide configuration fields that are not relevant to the task and would confuse first-time users. - :::info Secret fields are protected automatically All input fields with `"isSecret": true` in the Actor's [input schema](/actors/development/actor-definition/input-schema) are automatically masked and never shown on the landing page. Before publishing, confirm sensitive fields are marked as secret. @@ -123,11 +116,21 @@ The Dataset schema section selects which view of the Actor's dataset is rendered For more on configuring views, see [Dataset schema](/storage/dataset-schema). +## Unpublish a task + +To remove a task's public landing page, open the task's **Publishing** tab and select **Unpublish task**. Confirm to remove the landing page. + +Unpublishing removes the public landing page, but your task and its configuration stay saved. Republish anytime. + +![Unpublish task dialog on the Publishing tab.](./images/public-tasks/task-unpublish-dialog.webp) + +To see which tasks are published, filter by **Publish status** in the Tasks list in the sidebar. + ## Task landing page -Each published task gets its own standalone landing page on the [Apify website](https://apify.com). This page is publicly accessible, indexed by search engines, and readable by AI agents. Published tasks also appear in the **Examples** tab of the Actor's detail page, linking visitors directly to the landing page. +Each published task gets its own standalone landing page on the [Apify website](https://apify.com). Published tasks also appear in the **Example tasks** tab of the Actor's detail page, linking users directly to the landing page. -![Examples tab on the Actor detail page showing published tasks.](./images/public-tasks/actor-examples-tab.webp) +![Example tasks tab on the Actor detail page showing published tasks.](./images/public-tasks/actor-examples-tab.webp) ### URL structure @@ -143,17 +146,16 @@ Keep the task name short, descriptive, and focused on the use case keyword. ![Task landing page with title, input fields, and output preview.](./images/public-tasks/task-landing-page.webp) -The landing page displays the information you configured in the [Display information](#display-information), [Input](#input), and [Dataset schema](#dataset-schema) sections: +The landing page displays the information you configured in the [Page details](#page-details), [Input](#input), and [Dataset schema](#dataset-schema) sections: -- The **SEO task title** and **SEO description** at the top of the page. -- The selected **input fields** with their configured values, so visitors can see exactly how the task is set up. +- The **SEO title** and **SEO description** at the top of the page. +- The selected **input fields** with their configured values, so users can see exactly how the task is set up. - A preview of the **Dataset schema fields** based on the dataset view you selected. -- A call-to-action button that lets visitors try the task immediately. -- Generic sections explaining how Apify works and how to integrate it. +- A call-to-action button that lets users try the task right away. -### What happens when a visitor tries the task +### What happens when a user tries the task -When a visitor clicks the call-to-action button, Apify creates a new task under their account with the same input configuration. The visitor gets their own independent copy. They can modify, run, and manage it without affecting your original task. You don't need to worry about other users consuming your resources or altering your configuration. +When a user clicks the call-to-action button, Apify creates a new task under their account with the same input configuration. The user can change, run, and manage it without affecting your original task. Your resources and configuration stay untouched. ## Next steps From 8a6e25f9de63202b0f94994d48ca9851f643f43c Mon Sep 17 00:00:00 2001 From: jgagne Date: Wed, 5 Aug 2026 22:46:05 +0200 Subject: [PATCH 2/7] docs: copy lint pass and document missing features Copy fixes: - "what it does, what inputs to provide, and what output to expect" (parallel and user-centered, replaces "it produces") - "more discoverability means more paid runs" (docs voice, not marketing) - Slug: spell out constraints (lowercase, hyphens, no spaces) - "preview updates as you type" (replaces "live preview how fields propagate") - "your original task" (consistent possessive) - Remove "automatically" from AI generation line (redundant with AI icon) - Unpublish: state outcome of confirm action New feature documentation: - Use case field (required, for Store categorization) - AI icon for generating SEO title and description - Publishing tab progress guide - Publish confirmation (privacy reassurance) - After publishing: share dialog and View landing page button - Privacy note in "After a user tries your task" - Prerequisites: blocking state when schemas are missing --- .../actors/publishing/publish-task.mdx | 31 +++++++++++++------ 1 file changed, 21 insertions(+), 10 deletions(-) diff --git a/sources/platform/actors/publishing/publish-task.mdx b/sources/platform/actors/publishing/publish-task.mdx index c6dddc5347..e94a580719 100644 --- a/sources/platform/actors/publishing/publish-task.mdx +++ b/sources/platform/actors/publishing/publish-task.mdx @@ -1,11 +1,11 @@ --- title: Publish your Actor task -description: Publish a saved Actor task as a public use-case landing page on Apify Store by completing the display information, input, and dataset schema sections. +description: Publish a saved Actor task as a public use-case landing page on Apify Store by completing the page details, input, and dataset schema sections. slug: /actors/publishing/publish-task sidebar_position: 2 --- -[Actor tasks](/actors/running/tasks) are shareable, pre-configured inputs for your Actors. [Publishing a task](#publish-your-tasks) creates a public landing page that shows what the Actor does, what inputs it uses, and what output to expect. Public tasks also appear in your Actor's **Example tasks** tab, which helps users discover your Actor through search engines and AI agents. +[Actor tasks](/actors/running/tasks) are shareable, pre-configured inputs for your Actors. [Publishing a task](#publish-your-tasks) creates a public landing page that shows what it does, what inputs to provide, and what output to expect. Public tasks also appear in your Actor's **Example tasks** tab, which helps users discover your Actor through search engines and AI agents. For monetized Actors, more discoverability means more paid runs. You can create up to 50 tasks per Actor. @@ -17,6 +17,8 @@ Before you publish a task, make sure you have: - A [saved task](/actors/running/tasks) with a complete input configuration. - An [input schema](/actors/development/actor-definition/input-schema) and at least one [dataset schema view](/storage/dataset-schema) defined on the Actor. +If your Actor is missing an input schema or dataset schema, the Publishing tab shows what needs to be set up before you can publish. + ## What tasks to publish Focus on tasks that represent a real use case someone would search for and that show your Actor solving a specific problem. Not every saved task needs a public landing page. @@ -57,7 +59,7 @@ If your Actor supports multiple use cases, publish a task for each one. A web sc ## Publish your tasks -Once your task runs reliably and produces the output you want users to see, publish it from Apify Console. +Once your task runs reliably and produces the output you want users to see, publish it from Apify Console. The Publishing tab guides you through each requirement. 1. From your task's page in Apify Console, open the **Publishing** tab. 1. Complete the three sections: [Page details](#page-details), [Input](#input), and [Dataset schema](#dataset-schema). @@ -69,11 +71,14 @@ Once your task runs reliably and produces the output you want users to see, publ This section controls how your task appears on the landing page and in search results. -- **Slug:** the URL-friendly name used in the task's landing page URL. +- **Slug:** the URL path for your task's landing page (lowercase, hyphens, no spaces). - **SEO title:** appears as the heading on the landing page and as the page title in search results. - **SEO description:** appears under the title on the landing page and as the meta description in search results. +- **Use case:** categorizes your task for Store browsing and search filtering. Required. + +Use the AI icon to generate the SEO title and description from your task configuration. -You can live preview how the fields propagate on the right: +The preview on the right updates as you type: - **Page preview:** how the landing page will look to users. - **Google preview:** how the page will appear in search results. @@ -116,11 +121,17 @@ The Dataset schema section selects which view of the Actor's dataset is rendered For more on configuring views, see [Dataset schema](/storage/dataset-schema). +### After publishing + +A confirmation dialog reminds you that your runs and data stay private. Once published, anyone on Apify can duplicate and run your task with their own input. + +A success dialog lets you share your task on social media. Use the **View landing page** button in the Publishing tab to preview it. + ## Unpublish a task -To remove a task's public landing page, open the task's **Publishing** tab and select **Unpublish task**. Confirm to remove the landing page. +To remove a task's landing page, open the task's **Publishing** tab and select **Unpublish task**. Confirm to remove it. -Unpublishing removes the public landing page, but your task and its configuration stay saved. Republish anytime. +Unpublishing removes the landing page, but your task and its configuration stay saved. Republish anytime. ![Unpublish task dialog on the Publishing tab.](./images/public-tasks/task-unpublish-dialog.webp) @@ -149,13 +160,13 @@ Keep the task name short, descriptive, and focused on the use case keyword. The landing page displays the information you configured in the [Page details](#page-details), [Input](#input), and [Dataset schema](#dataset-schema) sections: - The **SEO title** and **SEO description** at the top of the page. -- The selected **input fields** with their configured values, so users can see exactly how the task is set up. +- The selected **input fields** with their exact configured values. - A preview of the **Dataset schema fields** based on the dataset view you selected. - A call-to-action button that lets users try the task right away. -### What happens when a user tries the task +### After a user tries your task -When a user clicks the call-to-action button, Apify creates a new task under their account with the same input configuration. The user can change, run, and manage it without affecting your original task. Your resources and configuration stay untouched. +When a user clicks the call-to-action button, Apify creates a new task under their account with the same input configuration. The user can change, run, and manage it without affecting your original task. Your runs, data, and configuration stay private. ## Next steps From 2f0165c1edce258cf237f831865f57c198c3babb Mon Sep 17 00:00:00 2001 From: jgagne Date: Wed, 5 Aug 2026 22:57:45 +0200 Subject: [PATCH 3/7] docs: improve meta description for SEO - Remove "public use-case" (redundant, not a search term) - Remove implementation detail ("by completing the... sections") - Add benefit: discoverable on Google and by AI agents - Plain language pass on AI discovery section --- sources/platform/actors/publishing/publish-task.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/sources/platform/actors/publishing/publish-task.mdx b/sources/platform/actors/publishing/publish-task.mdx index e94a580719..6e708c72e0 100644 --- a/sources/platform/actors/publishing/publish-task.mdx +++ b/sources/platform/actors/publishing/publish-task.mdx @@ -1,6 +1,6 @@ --- title: Publish your Actor task -description: Publish a saved Actor task as a public use-case landing page on Apify Store by completing the page details, input, and dataset schema sections. +description: Publish a saved Actor task as a landing page on Apify Store. Each published task can be found on Google and by AI agents. slug: /actors/publishing/publish-task sidebar_position: 2 --- @@ -41,7 +41,7 @@ Each strong task focuses on a specific industry, location, or workflow. A user s ### Target search traffic and AI discovery -Each landing page is indexed by search engines and includes a markdown (`.md`) version that AI agents can access directly, making your task discoverable through AI search and AI assistants. +Each landing page shows up in Google results. It also has a markdown (`.md`) version that AI agents can read directly. Think of each task as a keyword-targeted landing page: From bf5e6d3cd1f198ceba1dc434c2a79fd64470a255 Mon Sep 17 00:00:00 2001 From: jgagne Date: Wed, 5 Aug 2026 23:12:39 +0200 Subject: [PATCH 4/7] docs: bold Publishing tab references for consistency --- sources/platform/actors/publishing/publish-task.mdx | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/sources/platform/actors/publishing/publish-task.mdx b/sources/platform/actors/publishing/publish-task.mdx index 6e708c72e0..391ed18146 100644 --- a/sources/platform/actors/publishing/publish-task.mdx +++ b/sources/platform/actors/publishing/publish-task.mdx @@ -17,7 +17,7 @@ Before you publish a task, make sure you have: - A [saved task](/actors/running/tasks) with a complete input configuration. - An [input schema](/actors/development/actor-definition/input-schema) and at least one [dataset schema view](/storage/dataset-schema) defined on the Actor. -If your Actor is missing an input schema or dataset schema, the Publishing tab shows what needs to be set up before you can publish. +If your Actor is missing an input schema or dataset schema, the **Publishing** tab shows what needs to be set up before you can publish. ## What tasks to publish @@ -59,7 +59,7 @@ If your Actor supports multiple use cases, publish a task for each one. A web sc ## Publish your tasks -Once your task runs reliably and produces the output you want users to see, publish it from Apify Console. The Publishing tab guides you through each requirement. +Once your task runs reliably and produces the output you want users to see, publish it from Apify Console. The **Publishing** tab guides you through each requirement. 1. From your task's page in Apify Console, open the **Publishing** tab. 1. Complete the three sections: [Page details](#page-details), [Input](#input), and [Dataset schema](#dataset-schema). @@ -101,7 +101,7 @@ Avoid titles like "Google Maps scraper - task 3" or "Test task" that describe th ### Input -The Input section controls which fields from your task's input configuration appear on the landing page. Every input field is selected by default. Deselect any field that isn't relevant to this task's use case. +The **Input** section controls which fields from your task's input configuration appear on the landing page. Every input field is selected by default. Deselect any field that isn't relevant to this task's use case. This control affects display only. The task itself always runs with the full input configuration, regardless of which fields are selected here. @@ -115,7 +115,7 @@ All input fields with `"isSecret": true` in the Actor's [input schema](/actors/d ### Dataset schema -The Dataset schema section selects which view of the Actor's dataset is rendered on the landing page. Each view organizes the output fields differently. Pick the one that best matches the task's use case. +The **Dataset schema** section selects which view of the Actor's dataset is rendered on the landing page. Each view organizes the output fields differently. Pick the one that best matches the task's use case. ![Dataset schema view selection.](./images/public-tasks/task-dataset-schema.webp) @@ -125,7 +125,7 @@ For more on configuring views, see [Dataset schema](/storage/dataset-schema). A confirmation dialog reminds you that your runs and data stay private. Once published, anyone on Apify can duplicate and run your task with their own input. -A success dialog lets you share your task on social media. Use the **View landing page** button in the Publishing tab to preview it. +A success dialog lets you share your task on social media. Use the **View landing page** button in the **Publishing** tab to preview it. ## Unpublish a task From 540e821d074514f3ed572b229d2143beb7c644f7 Mon Sep 17 00:00:00 2001 From: jgagne Date: Wed, 5 Aug 2026 23:21:28 +0200 Subject: [PATCH 5/7] docs: rename screenshot files and improve alt text - "task-publication-tab" to "task-publishing-tab" (matches renamed UI) - "task-display-information" to "task-page-details" (matches renamed section) - Alt text now describes what the screenshot shows, not just labels it --- ...ay-information.webp => task-page-details.webp} | Bin ...lication-tab.webp => task-publishing-tab.webp} | Bin .../platform/actors/publishing/publish-task.mdx | 14 +++++++------- 3 files changed, 7 insertions(+), 7 deletions(-) rename sources/platform/actors/publishing/images/public-tasks/{task-display-information.webp => task-page-details.webp} (100%) rename sources/platform/actors/publishing/images/public-tasks/{task-publication-tab.webp => task-publishing-tab.webp} (100%) diff --git a/sources/platform/actors/publishing/images/public-tasks/task-display-information.webp b/sources/platform/actors/publishing/images/public-tasks/task-page-details.webp similarity index 100% rename from sources/platform/actors/publishing/images/public-tasks/task-display-information.webp rename to sources/platform/actors/publishing/images/public-tasks/task-page-details.webp diff --git a/sources/platform/actors/publishing/images/public-tasks/task-publication-tab.webp b/sources/platform/actors/publishing/images/public-tasks/task-publishing-tab.webp similarity index 100% rename from sources/platform/actors/publishing/images/public-tasks/task-publication-tab.webp rename to sources/platform/actors/publishing/images/public-tasks/task-publishing-tab.webp diff --git a/sources/platform/actors/publishing/publish-task.mdx b/sources/platform/actors/publishing/publish-task.mdx index 391ed18146..2cb520ae4a 100644 --- a/sources/platform/actors/publishing/publish-task.mdx +++ b/sources/platform/actors/publishing/publish-task.mdx @@ -65,7 +65,7 @@ Once your task runs reliably and produces the output you want users to see, publ 1. Complete the three sections: [Page details](#page-details), [Input](#input), and [Dataset schema](#dataset-schema). 1. Select **Publish task**. -![Publishing tab on a task page.](./images/public-tasks/task-publication-tab.webp) +![The Publishing tab showing the Publish task button and three sections to complete.](./images/public-tasks/task-publishing-tab.webp) ### Page details @@ -83,7 +83,7 @@ The preview on the right updates as you type: - **Page preview:** how the landing page will look to users. - **Google preview:** how the page will appear in search results. -![Page details section with page and Google previews.](./images/public-tasks/task-display-information.webp) +![Page details fields (slug, SEO title, SEO description) with live page and Google previews on the right.](./images/public-tasks/task-page-details.webp) :::tip Title format @@ -105,7 +105,7 @@ The **Input** section controls which fields from your task's input configuration This control affects display only. The task itself always runs with the full input configuration, regardless of which fields are selected here. -![Input section with field selection.](./images/public-tasks/task-input-section.webp) +![Input section showing checkboxes to select which fields appear on the landing page.](./images/public-tasks/task-input-section.webp) :::info Secret fields are protected automatically @@ -117,7 +117,7 @@ All input fields with `"isSecret": true` in the Actor's [input schema](/actors/d The **Dataset schema** section selects which view of the Actor's dataset is rendered on the landing page. Each view organizes the output fields differently. Pick the one that best matches the task's use case. -![Dataset schema view selection.](./images/public-tasks/task-dataset-schema.webp) +![Dataset schema section with a dropdown to select which output view to display.](./images/public-tasks/task-dataset-schema.webp) For more on configuring views, see [Dataset schema](/storage/dataset-schema). @@ -133,7 +133,7 @@ To remove a task's landing page, open the task's **Publishing** tab and select * Unpublishing removes the landing page, but your task and its configuration stay saved. Republish anytime. -![Unpublish task dialog on the Publishing tab.](./images/public-tasks/task-unpublish-dialog.webp) +![Unpublish confirmation dialog with a Confirm button.](./images/public-tasks/task-unpublish-dialog.webp) To see which tasks are published, filter by **Publish status** in the Tasks list in the sidebar. @@ -141,7 +141,7 @@ To see which tasks are published, filter by **Publish status** in the Tasks list Each published task gets its own standalone landing page on the [Apify website](https://apify.com). Published tasks also appear in the **Example tasks** tab of the Actor's detail page, linking users directly to the landing page. -![Example tasks tab on the Actor detail page showing published tasks.](./images/public-tasks/actor-examples-tab.webp) +![Example tasks tab on an Actor page listing published tasks with their titles.](./images/public-tasks/actor-examples-tab.webp) ### URL structure @@ -155,7 +155,7 @@ Keep the task name short, descriptive, and focused on the use case keyword. ### Landing page content -![Task landing page with title, input fields, and output preview.](./images/public-tasks/task-landing-page.webp) +![A published task landing page showing the SEO title, input configuration, and dataset preview.](./images/public-tasks/task-landing-page.webp) The landing page displays the information you configured in the [Page details](#page-details), [Input](#input), and [Dataset schema](#dataset-schema) sections: From 37eb5a1e4f25f10f366df26cddb2d3a9f9fecb9d Mon Sep 17 00:00:00 2001 From: Justin Gagne Date: Thu, 6 Aug 2026 16:16:14 +0200 Subject: [PATCH 6/7] docs: ground the weak/strong task table in real examples - Replaces two rows with real example task titles currently live on Google Maps Scraper, verified on apify.com. - Keeps the "Generic task/Specific task" table headers as-is. - Tightens the Amazon and Yahoo Finance strong titles to a single focus each, matching the section's own stated principle. - Fixes the intro line to name all three Actors shown in the table. - Updates a leftover "dentist" reference and the URL structure example to match the new table. --- .../platform/actors/publishing/publish-task.mdx | 14 ++++++-------- 1 file changed, 6 insertions(+), 8 deletions(-) diff --git a/sources/platform/actors/publishing/publish-task.mdx b/sources/platform/actors/publishing/publish-task.mdx index 2cb520ae4a..546d84896f 100644 --- a/sources/platform/actors/publishing/publish-task.mdx +++ b/sources/platform/actors/publishing/publish-task.mdx @@ -27,17 +27,15 @@ Focus on tasks that represent a real use case someone would search for and that The best tasks aim to solve a problem a user actually has. Instead of publishing a generic "default configuration" task, publish one that answers a question someone might type into a search engine or AI agent. -For example, if you maintain Google Maps, Amazon, and Yahoo scraper Actors: +For example, if you maintain Google Maps, Amazon, and Yahoo Finance scraper Actors: | Generic task | Specific task | | --- | --- | -| Google Maps - default config | Find dentists in San Francisco with reviews | -| Test run 2 | Extract restaurant emails for local marketing | -| All fields enabled | Compare gym ratings across New York boroughs | -| Amazon default | Monitor Amazon product prices and reviews for market research | -| Yahoo Finance test | Track stock prices and news on Yahoo Finance | +| Google Maps business task | Analyze local business competitors with AI | +| Yahoo Finance test | Monitor stock prices on Yahoo Finance | +| Amazon scraper | Track Amazon product prices for market research | -Each strong task focuses on a specific industry, location, or workflow. A user searching for "dentist data San Francisco" is more likely to land on a page with that exact framing. +Each strong task focuses on a specific industry, location, or workflow. A user searching for "local business competitors" is more likely to land on a page with that exact framing. ### Target search traffic and AI discovery @@ -148,7 +146,7 @@ Each published task gets its own standalone landing page on the [Apify website]( The landing page URL is built from your username, Actor name, and task name. For example: ```text -https://apify.com/john/google-maps-scraper/examples/find-dentists-san-francisco +https://apify.com/john/google-maps-scraper/examples/analyze-local-business-competitors ``` Keep the task name short, descriptive, and focused on the use case keyword. From 888589748fd479d73999428a2b7d0b5352b1d753 Mon Sep 17 00:00:00 2001 From: Justin Gagne Date: Thu, 6 Aug 2026 16:17:48 +0200 Subject: [PATCH 7/7] docs: refine the example task table - Changes "Analyze local business competitors with AI" to "Analyze San Francisco business competitors with AI", naming an actual location instead of the placeholder word "local". - Updates the matching sentence below the table to reference the new phrase. - Simplifies the sentence after the table to "Each task focuses on a specific industry, location, or workflow", removing a redundant modifier on "task". - Note: the San Francisco example is no longer verbatim from the live Google Maps Scraper Examples tab, it's a modified version. The other two rows in this table remain our own examples, not live ones. --- sources/platform/actors/publishing/publish-task.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/sources/platform/actors/publishing/publish-task.mdx b/sources/platform/actors/publishing/publish-task.mdx index 546d84896f..2ab3c52bd3 100644 --- a/sources/platform/actors/publishing/publish-task.mdx +++ b/sources/platform/actors/publishing/publish-task.mdx @@ -31,11 +31,11 @@ For example, if you maintain Google Maps, Amazon, and Yahoo Finance scraper Acto | Generic task | Specific task | | --- | --- | -| Google Maps business task | Analyze local business competitors with AI | +| Google Maps business task | Analyze San Francisco business competitors with AI | | Yahoo Finance test | Monitor stock prices on Yahoo Finance | | Amazon scraper | Track Amazon product prices for market research | -Each strong task focuses on a specific industry, location, or workflow. A user searching for "local business competitors" is more likely to land on a page with that exact framing. +Each task focuses on a specific industry, location, or workflow. A user searching for "San Francisco business competitors" is more likely to land on a page with that exact framing. ### Target search traffic and AI discovery