diff --git a/.github/styles/config/vocabularies/Docs/accept.txt b/.github/styles/config/vocabularies/Docs/accept.txt index 457c4f2d68..c2af02c301 100644 --- a/.github/styles/config/vocabularies/Docs/accept.txt +++ b/.github/styles/config/vocabularies/Docs/accept.txt @@ -1,6 +1,5 @@ \bApify\b(?:-\w+)? @apify\.com -Actor(s)? SDK(s) [Ss]torages Crawlee @@ -106,5 +105,20 @@ subwoofer captcha captchas deduplicating +reindexes +READMEs +backlink +backlinks +subreddit +subreddits +upvote +walkthrough +walkthroughs +influencers +livestreams +outro +Chatbot +Tripadvisor +[Rr]epurpose jQuery diff --git a/nginx.conf b/nginx.conf index 88e4b2ce2e..0639286c83 100644 --- a/nginx.conf +++ b/nginx.conf @@ -401,6 +401,10 @@ server { rewrite ^/api/v2/users-monthly-usage$ /api/v2/users permanent; rewrite ^/api/v2/users-account-and-usage-limits$ /api/v2/users permanent; + # Actor marketing playbook addition + + rewrite ^/academy/get-most-of-actors /academy/actor-marketing-playbook + } # Temporarily used to route crawlee.dev to the Crawlee GitHub pages. diff --git a/sources/academy/platform/get_most_of_actors/actor_basics/_category_.yaml b/sources/academy/platform/get_most_of_actors/actor_basics/_category_.yaml new file mode 100644 index 0000000000..74ba842c8c --- /dev/null +++ b/sources/academy/platform/get_most_of_actors/actor_basics/_category_.yaml @@ -0,0 +1,2 @@ +label: Actor basics +position: 2 diff --git a/sources/academy/platform/get_most_of_actors/actor_basics/actor_description_seo_description.md b/sources/academy/platform/get_most_of_actors/actor_basics/actor_description_seo_description.md new file mode 100644 index 0000000000..726fb7c705 --- /dev/null +++ b/sources/academy/platform/get_most_of_actors/actor_basics/actor_description_seo_description.md @@ -0,0 +1,160 @@ +--- +title: Actor description & SEO description +description: Learn about Actor description and meta description. Where to set them and best practices for both content and length. +sidebar_position: 3 +category: apify platform +slug: /actor-marketing-playbook/actor-basics/actor-description +--- + +Learn about Actor description and meta description. Where to set them and best practices for both content and length. + +--- + +## What is an Actor description? + +First impressions are important, especially when it comes to tools. Actor descriptions are the first connection potential users have with your Actor. You can set two kinds of descriptions: _regular description_ (in Apify Store) and _SEO description_ (on Google search), along with their respective names: regular name and SEO name. + +:::tip + +You can change descriptions and names as many times as you want. + +::: + +## Regular description vs. SEO description + +| | Actor description & name | SEO description & name | +|---|---|---| +| Name length | 40-50 characters | 40-50 characters | +| Description length | 300 characters | 145-155 characters | +| Visibility | Visible on Store | Visible on Google | + +### Description & Actor name + +Actor description is what users see on the Actor's web page in Apify Store, along with the Actor's name and URL. When creating an Actor description, a “warm” visitor experience is prioritized (more on that later). + +![actor name & description](images/actor-description-name.png) + +Actor description is also present in Apify Console and across Apify Store. + +![actor description in store](images/actor-description-store.png) + +### SEO description & SEO name + +Actor SEO description is a tool description visible on Google. It is shorter and SEO-optimized (keywords matter here). When creating the SEO description, a “cold” visitor experience is prioritized. + +![seo description](images/seo_description.png) + +Usually the way the potential user interacts with both these descriptions goes like this: SEO first, regular description second. Is there any benefit in them being different? + +### Is there any benefit in the description and meta description being different? + +Different descriptions give you a chance to target different stages of user acquisition. And make sure the acquisition takes place. + +_SEO description (and SEO name)_ is targeting a “cold” potential user who knows nothing about your tool yet and just came across it on Google search. They’re searching to solve a problem or use case. The goal of the meta description is to convince that visitor to click on your tool's page among other similar search results on Google. While it's shorter, SEO description is also the space to search-engine-optimize your language to the max to attract the most matching search intent. + +_Description (and name)_ is targeting a “warm” potential user who is already curious about your tool. They have clicked on the tool's page and have a few seconds to understand how complex the tool is and what it can do for them. Here you can forget SEO optimization and speak directly to the user. The regular description also has a longer character limit, which means you can expand on your Actor’s features. + +Learn more about search intent here: [SEO](/academy/actor-marketing-playbook/promote-your-actor/seo) + +## Where can Actor descriptions be set? + +Both descriptions can be found and edited on the very right **Publication tab → Display information.** It has to be done separately for each Actor. + +:::note + +Setting the SEO description and SEO name is optional. If not set, the description will just be duplicated. + +::: + +![changing seo name](images/changing__SEO_name.png) + +![changing actor name and seo name](images/changing_Actor_name_and_SEO_name.png) + +Actor description specifically can also be quick-edited in this pop-up on the Actor's page in Apify Console. Open the **Actor's page**, then click on **…** in the top right corner, and choose ✎ **Edit name or description**. Then set the URL in the **Unique name** ✎ field and click **Save**. + +![changing actor description](images/change_Actor_description.png) + +## Tips and recommendations on how to write descriptions + +When writing a description, less is more. You only have a few seconds to capture attention and communicate what your Actor can do. To make the most of that time, follow these guidelines used by Apify (these apply to both types of descriptions): + +### Use variations and experiment 🔄 + +- _SEO name vs. regular name_: + - name: Airbnb Scraper + - SEO name: Airbnb Data Scraper +- _Keywords on the web page_:
+Include variations, e.g. Airbnb API, Airbnb data, Airbnb data scraper, Airbnb rentals, Airbnb listings + - No-code scraping tool to extract Airbnb data: host info, prices, dates, location, and reviews. + - Scrape Airbnb listings without official Airbnb API! +- _Scraping/automation process variations_:
+Use terms, e.g. crawl, crawler, scraping tool, finder, scraper, data extraction tool, extract data, get data + - Scrape XYZ data, scraped data, data scraper, data crawler. + +### Choose how to start your sentences 📝 + +- _Noun-first (descriptive)_: + - Data extraction tool to extract Airbnb data: host info, prices, dates, location, and reviews. +- _Imperative-first (motivating)_: + - Try a free web scraping tool to extract Airbnb data: host info, prices, dates, location, and reviews. + + +### Keep it short and SEO-focused ✂️ + +- _Be concise and direct_: clearly state what your Actor does. Avoid unnecessary fluff and boilerplate text. + - ✅ Scrapes job listings from Indeed and gathers... + - ❌ *This Actor scrapes job listings from Indeed in order to gather... +- _Optimize for search engines_: include popular keywords related to your Actor’s functionality that users might search for. + - ✅ This Indeed scraper helps you collect job data efficiently. Use the tool to gather... + - ❌ This tool will search through job listings on Indeed and offers you... + + +### List the data your Actor works with 📝 + +- Data extraction tool to extract Airbnb data: host info, prices, dates, location, and reviews. +- Get hashtags, usernames, mentions, URLs, comments, images, likes, locations without the official Instagram API. + +### Use keywords or the language of the target website 🗣️ + +- Extract data from hundreds of Airbnb home rentals in seconds. +- Extract data from chosen tik-toks. Just add a TikTok URL and get TikTok video and profile data: URLs, numbers of shares, followers, hashtags, hearts, video, and music metadata. +- Scrape Booking with this hotels scraper and get data about accommodation on Booking.com. + +### Highlight your strong suits 🌟 + +- Ease of use, no coding, user-friendly: + - Easy scraping tool to extract Airbnb data. +- Fast and scalable: + - Scrape whole cities or extract data from hundreds of Airbnb rentals in seconds. +- Free (only if the trial run can cover $5 free credits): + - Try a free scraping tool to extract Airbnb data: host info, prices, dates, location, and reviews. + - Extract host information, locations, availability, stars, reviews, images, and host/guest details for free. +- Available platform features (various formats, API, integrations, scheduling): + - Export scraped data in formats like HTML, JSON, and Excel. +- Additional tips: + - Avoid ending lists with etc. + - Consider adding relevant emojis for visual appeal. + +### Break it down 🔠 + +Descriptions typically fit into 2-3 sentences. Don't try to jam everything into one. + +Examples: + +1. Scrape whole cities or extract data from hundreds of Airbnb rentals in seconds. +1. Extract host information, addresses, locations, prices, availability, stars, reviews, images, and host/guest details. +1. Export scraped data, run the scraper via API, schedule and monitor runs, or integrate with other tools. + +## FAQ + +#### Can the Actor's meta description and description be the same? + +Yes, they can, as long as they have the same (shorter) length (under 150 characters). But they can also be different - there's no harm in that. + +#### How different can description and meta description be? + +They can be vastly different and target different angles of your Actor. You can experiment by setting up different SEO descriptions for a period of time and seeing if the click-through rate rises. + +#### I set a custom SEO description but Google doesn't show it + +Sometimes Google picks up a part of the README as the SEO description. It's heavily dependent on the search query. Sometimes what you see on Google might look differently compared to how you set the SEO description. It's all a part of how Google customizes search results. diff --git a/sources/academy/platform/get_most_of_actors/actor_basics/actors-and-emojis.md b/sources/academy/platform/get_most_of_actors/actor_basics/actors-and-emojis.md new file mode 100644 index 0000000000..9f1a721f06 --- /dev/null +++ b/sources/academy/platform/get_most_of_actors/actor_basics/actors-and-emojis.md @@ -0,0 +1,31 @@ +--- +title: Actors & emojis +description: Discover how emojis can boost your Actors by grabbing attention, simplifying navigation, and enhancing clarity. Improve user experience and engagement on Apify Store. +sidebar_position: 5 +category: apify platform +slug: /actor-marketing-playbook/actor-basics/actors-and-emojis +--- + +Using emojis in Actors is a science on its own. Learn how emojis enhance the user experience in Actors by grabbing attention, simplifying navigation, and making information clearer. + +## On the use of emojis in Actors + +We started using emojis in Actors for several reasons. First, tech today often uses emojis to make things look more user-friendly. Second, people don’t read as much as we’d like. You only have a few seconds to grab their attention, and text alone can feel overwhelming. Third, we don’t have many opportunities or space to explain things about Actors, and we want to avoid users needing to open extra tabs or pages. Clarity should come instantly, so we turned to emojis. + +When evaluating a new tool, those first 5 seconds are critical. That’s why we use emojis extensively with our Actors. They’re part of the Actor SEO title and description to help the tool stand out in Google search results, although Google doesn't always display them. In READMEs, they serve as shortcuts to different sections and help users quickly understand the type of data they’ll get. In complex input schemas, we rely on emojis to guide users and help them navigate the tool more efficiently. + +## Emoji science + +Believe it or not, there’s a science to emoji usage. When we use emojis in Actors and related content, we tap into the brain's iconic and working memory. Iconic memory holds information for less than a second - this is unconscious processing, where attributes like color, size, and location are instantly recognized. This part is where emojis guide the person's attention in the sea of text. They signify that something important is here. Emojis help with that immediate first impression and create a sense of clarity. + +After that, the brain shifts to working memory, where it combines information into visual chunks. Since we can only hold about 3-4 chunks at once, emojis help reinforce key points, thus reducing cognitive load. Consistent emoji use across the Actor ecosystem ensures users can quickly connect information without getting overwhelmed. + +As an example of this whole process, first, the user notices the emojis used in the field titles (pre-attentive processing). They learn to associate the emojis with those titles (attentive processing). Later, when they encounter the same emojis in a README section, they’ll make the connection, making it easier to navigate without drowning in a sea of text. + +## Caveats to emojis + +1. Don't overuse them, and don’t rely on emojis for critical information. Emojis should support the text, not replace key explanations or instructions. They're a crutch for concise copywriting, not a universal solution. +2. Use them consistently. Choose one and stick with it across all content: descriptions, parts of input schema, mentions in README, blog posts, etc. +3. Some emojis have multiple meanings, so choose the safest one. It could be general internet knowledge or cultural differences, so make sure the ones you choose won’t confuse or offend users in other markets. +4. Some emojis don’t render well on Windows or older devices. Try to choose ones that display correctly on Mac, Windows, and mobile platforms. Besides, emoji-heavy content can be harder for screen readers and accessibility tools to interpret. Make sure the information is still clear without the emojis. +5. It's okay not to use them. diff --git a/sources/academy/platform/get_most_of_actors/actor_basics/how-to-create-actor-readme.md b/sources/academy/platform/get_most_of_actors/actor_basics/how-to-create-actor-readme.md new file mode 100644 index 0000000000..503e8a18d5 --- /dev/null +++ b/sources/academy/platform/get_most_of_actors/actor_basics/how-to-create-actor-readme.md @@ -0,0 +1,268 @@ +--- +title: How to create an Actor README +description: Learn how to write a comprehensive README to help users better navigate, understand and run public Actors in Apify Store. +sidebar_position: 3 +category: apify platform +slug: /actor-marketing-playbook/actor-basics/how-to-create-an-actor-readme +--- + +**Learn how to write a comprehensive README to help users better navigate, understand and run public Actors in Apify Store.** + +--- + +## What's a README in the Apify sense? + +At Apify, when we talk about a README, we don’t mean a guide mainly aimed at developers that explains what a project is, how to set it up, or how to contribute to it. At least, not in its traditional sense. + +You could argue our notion of README is closer to this [one described on GitHub](https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes): + +README files typically include information on: + +- What the project does +- Why the project is useful +- How users can get started with the project +- Where users can get help with your project + +We mean all of this and even more. At Apify, when we talk about READMEs, we refer to the public Actor detail page on Apify Store. Specifically, its first tab. The README exists in the same form both on the web and in Console. So what is it for? + +Before we dive in, a little disclaimer: you don't need your Apify README to fulfill all its purposes. Technically, you could even publish an Actor with just a single word in the README. But you'd be missing out if you did that. + +Your Actor’s README has at least four functions: + +1. _SEO_ - If your README is well-structured and includes important keywords — both in headings and across the text — it has a high chance of being noticed and promoted by Google. Organic search brings the most motivated type of potential users. If you win this game, you've won most of the SEO game. +2. _First impression_ - Your README is one of the first points of contact with a potential user. If you come across as convincing, clear, and reassuring it could be the factor that will make a user try your Actor for their task. +3. _Extended instruction_ - The README is also the space that explains specific complex input settings. For example, special formatting of the input, any coding-related, or extended functions. Of course, you could put that all in a blog post as well, but the README should be their first point of contact. +4. _Support_ - Your users come back to the README when they face issues. So use it as a space to let them know that's where they can find links to the tutorials if they run into issues, describe common troubleshooting techniques, share tricks, or warn you about bugs. + +## README elements theory + +These are the most important elements of the README. This structure is also not to be followed to a “t”. Of course, what you want to say to your potential users and how you want to promote your Actor will differ case by case. These are just the most common practices we have for our Actor READMEs. Beware that the headings are written with SEO in mind, which is why you see certain keywords repeated over and over. + +Aim for sections 1–6 below and try to include at least 300 words. You can move the sections around to some extent if it makes sense, e.g. 3 might come after 6. Consider using emojis as bullet points or otherwise trying to break up the text. + +### Intro and features + +What is [Actor]? + +- explain in two or three sentences what the Actor does and the easiest way to try it. Mention briefly what kind of data it can extract and any other tangible goal the tool can achieve. Describe the input in one sentence. Highlight the most important words in bold. + +What can this [Actor] do? + +- list the main features of this tool. list multiple ways of input if applicable. list platform advantages. If it's a bundle, mention the steps that the Actor will do for you, mention specific obstacles this tool is able to overcome, say upfront how many results you can get for free. + +:::tip Remember the Apify platform! + +Your Actor + the Apify platform. They come as a package. Don't forget to flaunt all the advantages that the platform gives to your solution. + +::: + +Imagine if there was a solution that is identical to yours but without the platform advantages such as monitoring, access to API, scheduling, possibility of integrations, proxy rotation. Now, if that tool suddenly gained all those advantages it would surely make a selling point out of it. This is how you should be thinking about your tool — as a solution boosted by the Apify platform. Don't ever forget that advantage. + +What data can [Actor] extract? + +What data can you extract from [target website] + +- Create a table that represents the main datapoints that the Actor can extract. You don't have to list every single one, just list the most understandable and relatable ones. + +Depending on the complexity of your Actor, you might include one or all three of these sections. It will also depend on what your Actor does. If your Actor has simple input but does a lot of steps for the user under the hood (like a bundle would), you might like to include the "What can this Actor do?" section. If your Actor extracts data, it makes sense to include a section with a table. + +### Tutorial section + +This could be a simple listed step-by-step section or a paragraph with a link to a tutorial on a blog. + +A step-by-step section is reassuring for the user, and it can be a section optimized for Google. + +How do I use [Actor] to scrape website data? + +### Pricing + +How much will it cost to scrape [target site]? + +How much will scraping [target site] cost? + +Is scraping [target site] free? + +How much does it cost to extract [target site] data? + +Web scraping can be very unpredictable because there are a lot of elements involved in order for the process to be successful: the complexity of the website, proxies, cookies, etc. This is why it's important to set the pricing and scraping volume expectations for your users. + +You might think the part above the Actor detail page already indicates pricing. But this paragraph can still be useful. First of all, cost-related questions can show up in Google, if they are SEO optimized. Second, you can use this space to inform and reassure the user about the pricing, give more details about it, or entice them with the promise of very scalable scraping. + +- If it's a consumption pricing model (only consumed CUs), you can use this space to set expectations and explain what it means to pay for Compute Units. Similarly, if it's a rental Actor, you can also use this paragraph to set expectations. Talk about the average amount of data that can be scraped per given price. Make it easy for users to imagine how much they will pay for a given dataset. This will also make it easier for them to compare your solution with others on the market price-wise and value-wise. +- If it's price per result, you can extrapolate how many results a user can get on a free plan and also entice them with a larger plan and how many thousands of results they can get with that. +- If it's a bundle that consists of a couple of Actors that are priced differently, you can use this section to talk about the difference between all the Actors involved and how that will affect the final price of a run. + +In any case, on top of setting expectations and reassuring users, this paragraph can get into Google. If somebody is Googling "How much does it cost to scrape [website]", they might come across this part of your README and it will lead them from Google search directly to your Actor's detail page. So you don't want to miss that opportunity. + +![readme example](images/readme.png) + +### Input and output examples + +This is what people click on the most in the table of contents of the README. After they are done scrolling through the first part of the README, users are interested in how difficult the input it, what it looks like, and what kind of information they can expect. + +**Input**: often a screenshot of the input schema. This is also a way for people to see the platform even before they create an account. + +**Output**: can be shown as a screenshot if your output schema looks like something you would want to promote to users. You can also just include a JSON example containing a few objects. Even better if there's continuity between the input example and output example. + +If your datasets come out too complex and you want to save your users some scrolling, you can also show multiple output examples: one for reviews, one for contact details, one for ads, etc. + +### Other Actors + +Don't forget to promote your other Actors. While our system for Actor recommendation works - you can see related Actors at the bottom of the README — it only works within the same category or similar name. It won't recommend a completely different Actor from the same creator. So make sure to interconnect your work by taking the initiative yourself. You can mention your other Actors in a list or as a table. + +### FAQ, disclaimers, and support + +The FAQ is a section where you can keep all the secondary questions that might still come up. + +Here are just a few things we usually push to the FAQ section. + +- disclaimers and legality +- comparison table between your Actor and similar solutions +- information about the official API and how the scraper is a stand-in for it (SEO) +- questions brought up by the users +- tips on how best to use the Actor +- troubleshooting and mentioning known bugs +- mentioning the Issues tab and highlighting that you're open for feedback and collecting feedback +- mentioning being open to creating a custom solution based on the current one and showing a way to contact you +- interlinking +- mentioning the possibility of transferring data using an API — API tab +- possibility for integrations +- use cases for the data scraped, success stories exemplifying the use of data + +## Format of the README + +### Markdown + +The README has to be written in Markdown. The most important elements are H2 and H3 headings, links to pages, links to images, and tables. For specific formatting, you can try using basic HTML. That will also work. CSS won’t. + +### HTML use + +You can use HTML and Markdown interchangeably. For example, you can write the same table either way. + +### Tone of the README + +Apify Store has many Actors in its stock, and it's only growing. The advantage of an Actor is that an Actor can be anything, as versatile or complex as possible. From a single URL type of input to complex features that give customized control over the input parameters to the user. There are Actors that are intended for users who aren't familiar with coding and don't have any experience with it. Ideally, the README should reflect the level of skill one should need to use the Actor. + +The tone of the README should make it immediately obvious who the tool is aimed at. If your tool's input includes glob patterns or looking for selectors, it should be immediately visible from the README. Before the user even tries the tool. Trying to simplify this information using simple words with ChatGPT can be misleading to the user. You will attract the wrong audience, and they will end up churning or asking you too many questions. + +And vice versa. If your target audience is people with little to no coding skills, who just prefer point-and-click solutions, this should be visible from the README. Speak in regular terms, avoid code blocks or complex information at the beginning unless it's absolutely necessary. This means that, when people land on your Actor detail page, they will have their expectations set from the get-go. + +### Length of a README + +When working on improving a README, we regularly look at heatmaps that show us where our website visitors spend most of their time. From our experience, most first-time visitors don't scroll past the first 25% of a README. That means that the first quarter of the README is where you want to focus the most of your attention if you're trying to persuade the page visitor to try your Actor. + +From the point of view of acquisition, the first few sections should make it immediately obvious what the tool is about, how hard it is to use, and who it is created for. This is why, in Apify's READMEs, you can see our first few paragraphs are built in such a way as to explain these things and reassure the visitors that anyone can use these tools. + +From the point of view of retention, it doesn't mean you can't have long or complex READMEs or not care for the information beyond the 25% mark. Since the README is also intended to be used as a backup when something goes wrong or the user needs more guidance, your users will come back to it multiple times. + +### Images and videos + +As for using screenshots and GIFs, put them in some sort of image hosting. Your own GitHub repository would be best because you have full control over it. Name the images with SEO in mind and try to keep them compressed but good enough quality. You don't want to load an image or GIF for too long. + +One trick is not only to add images but also to make them clickable. For some reason, people like clicking on images, at least they try to when we look at the heatmaps. You can lead the screenshot clicks towards a signup page, which is possible with Markdown. + +If your screenshot seems too big or occupies too much space, smaller size images are possible by using HTML. + +To embed a YouTube video, all you have to do is include its URL. No further formatting is needed, the thumbnail will render itself on the README page. + +:::tip Try Carbon for code + +If you want to add snippets of code anywhere in your README, you can use [Carbon](https://github.com/carbon-app/carbon). + +::: + +If you need quick Markdown guidance, check out [https://www.markdownguide.org/cheat-sheet/](https://www.markdownguide.org/cheat-sheet/) + + +## README and SEO + +Your README is your landing page. + +If there were only one thing to remember about READMEs on Apify Store, it would be this. A README on Apify Store is not just dry instructions on how to use your Actor. It has much more potential than that. + +In the eyes of Google, your Actor's detail page, aka README, is a full-fledged landing page containing all the most important information to be found and understood by users. + +Of course, that all only counts if your README is both well formatted and contains keywords. We'll talk about that part later on. + +What makes a good README? + +A good README has to be a balance between what you want your page visitors to know, your users to turn to when they run into trouble, and Google to register when it's indexing pages and considering which one deserves to be put up higher. + +### Table of contents + +The H1 of your page is the Actor name, so you don't have to set that up. Don't add more H1s. README headings should be H2 or H3. H2 headings will make up the table of contents on the right. So if you don't want the table to be too crowded, keep the H2s to the basics and push all the longer phrases and questions to H3s. H3s will stay hidden in the accordion in the default state until the visitor hovers their cursor over it. H4 readings can also be included, of course, but they won't show up as a part of the table of contents. + +### Keyword opportunities + +Do SEO research for keywords and see how they can fit organically into the text. Priority for H2s and H3s, then the regular text. Add new keyword-heavy paragraphs if you see an opportunity. + +The easiest sections to include keywords in are, for example: + +- API, as in Instagram API +- data, as in extract Instagram data +- Python, as in extract data in Python +- scrape, as in how to scrape X +- scraping, as in scraping X + +Now, could every H2 just say exactly what it is about, without SEO? Of course. You don't have to optimize your H2s and H3s, and are free to call them simply Features, How it works, Pricing, Support, etc. or not even to have many H2s at all and keep it all as one page. + +However, the H2s and H3s are what sometimes get into the Google Search results. If you're familiar with the People Also Ask section, that's the best place to match your H2s. They can also get highlighted in the Sitelinks of Google Search Results. + +Any part of your README can make it onto Google pages. The intro sentence describing what your Actor is about, a video, a random question. Each one can become a good candidate for those prime Google pages. That's why it's important to structure and write your README with SEO in mind. + +### Importance of including a video + +If your page has a video, it has a better chance of ranking higher in Google. + +## README and input schema + +The README should serve as a fallback for your users if something isn't immediately obvious in the input schema. There's also only that much space in the input schema and the tooltips, so naturally, if you want to provide more details about something: input, formatting, expectations — you should put it in the README and refer to it from the relevant place in the input schema. + +Learn about [How to create a great input schema](/academy/actor-marketing-playbook/product-optimization/how-to-create-a-great-input-schema) + +## [Readme elements template](https://docs.apify.com/academy/actor-marketing-playbook/actor-readme#what-should-you-add-to-your-actor-readme) + +1. What does (Actor name) do? + - in 1–2 sentences describe what the Actor does and what it does not do + - consider adding keywords like API, e.g. Instagram API + - always have a link to the target website in this section +2. Why use (Actor name)? or Why scrape (target site)? + - How it can be beneficial for the user + - Business use cases + - Link to a success story, a business use case, or a blog post. +3. How to scrape (target site) + - Link to "How to…" blogs, if one exists (or suggest one if it doesn't) + - Add a video tutorial or GIF from an ideal Actor run. + +:::tip Embedding YouTube videos + +For better user experience, Apify Console automatically renders every YouTube URL as an embedded video player. Simply add a separate line with the URL of your YouTube video. + +::: + +- Consider adding a short numbered tutorial, as Google will sometimes pick these up as rich snippets. Remember that this might be in search results, so you can repeat the name of the Actor and give a link, e.g. + +1. Is it legal to scrape (target site)? + - This can be used as a boilerplate text for the legal section, but you should use your own judgment and also customize it with the site name. + + > Our scrapers are ethical and do not extract any private user data, such as email addresses, gender, or location. They only extract what the user has chosen to share publicly. We therefore believe that our scrapers, when used for ethical purposes by Apify users, are safe. However, you should be aware that your results could contain personal data. Personal data is protected by the GDPR in the European Union and by other regulations around the world. You should not scrape personal data unless you have a legitimate reason to do so. If you're unsure whether your reason is legitimate, consult your lawyers. You can also read our blog post on the legality of web scraping + > +2. Input + - Each Actor detail page has an input tab, so you just need to refer to that. If you like, you can add a screenshot showing the user what the input fields will look like. + - This is an example of how to refer to the input tab: + + > Twitter Scraper has the following input options. Click on the input tab for more information. + > +3. Output + - Mention "You can download the dataset extracted by (Actor name) in various formats such as JSON, HTML, CSV, or Excel.” + - Add a simplified JSON dataset example, like here https://apify.com/compass/crawler-google-places#output-example +4. Tips or Advanced options section + - Share any tips on how to best run the Actor, such as how to limit compute unit usage, get more accurate results, or improve speed. + +If you want some general tips on how to make a GitHub README that stands out, check out these guides. Not everything in there will be suitable for an Apify Actor README, so you should cherry-pick what you like and use your imagination. + +## Resources + +[Build a Stunning README For Your GitHub Profile](https://towardsdatascience.com/build-a-stunning-readme-for-your-github-profile-9b80434fe5d7) + +[How to Create a Beautiful README for Your GitHub Profile](https://yushi95.medium.com/how-to-create-a-beautiful-readme-for-your-github-profile-36957caa711c) diff --git a/sources/academy/platform/get_most_of_actors/actor_basics/images/actor-description-name.png b/sources/academy/platform/get_most_of_actors/actor_basics/images/actor-description-name.png new file mode 100755 index 0000000000..6d3431b413 Binary files /dev/null and b/sources/academy/platform/get_most_of_actors/actor_basics/images/actor-description-name.png differ diff --git a/sources/academy/platform/get_most_of_actors/actor_basics/images/actor-description-store.png b/sources/academy/platform/get_most_of_actors/actor_basics/images/actor-description-store.png new file mode 100755 index 0000000000..52d31e0d9d Binary files /dev/null and b/sources/academy/platform/get_most_of_actors/actor_basics/images/actor-description-store.png differ diff --git a/sources/academy/platform/get_most_of_actors/actor_basics/images/actor-name.png b/sources/academy/platform/get_most_of_actors/actor_basics/images/actor-name.png new file mode 100755 index 0000000000..84ce8802d6 Binary files /dev/null and b/sources/academy/platform/get_most_of_actors/actor_basics/images/actor-name.png differ diff --git a/sources/academy/platform/get_most_of_actors/actor_basics/images/actor-seo-name.png b/sources/academy/platform/get_most_of_actors/actor_basics/images/actor-seo-name.png new file mode 100755 index 0000000000..33557ca98a Binary files /dev/null and b/sources/academy/platform/get_most_of_actors/actor_basics/images/actor-seo-name.png differ diff --git a/sources/academy/platform/get_most_of_actors/actor_basics/images/change_Actor_description.png b/sources/academy/platform/get_most_of_actors/actor_basics/images/change_Actor_description.png new file mode 100755 index 0000000000..934f37192f Binary files /dev/null and b/sources/academy/platform/get_most_of_actors/actor_basics/images/change_Actor_description.png differ diff --git a/sources/academy/platform/get_most_of_actors/actor_basics/images/changing_Actor_name_and_SEO_name.png b/sources/academy/platform/get_most_of_actors/actor_basics/images/changing_Actor_name_and_SEO_name.png new file mode 100755 index 0000000000..a5f53e37d3 Binary files /dev/null and b/sources/academy/platform/get_most_of_actors/actor_basics/images/changing_Actor_name_and_SEO_name.png differ diff --git a/sources/academy/platform/get_most_of_actors/actor_basics/images/changing__SEO_name.png b/sources/academy/platform/get_most_of_actors/actor_basics/images/changing__SEO_name.png new file mode 100755 index 0000000000..f20d5f2aa9 Binary files /dev/null and b/sources/academy/platform/get_most_of_actors/actor_basics/images/changing__SEO_name.png differ diff --git a/sources/academy/platform/get_most_of_actors/actor_basics/images/how-and-where-to-set-the-actor-url-console.png b/sources/academy/platform/get_most_of_actors/actor_basics/images/how-and-where-to-set-the-actor-url-console.png new file mode 100755 index 0000000000..c1f833db41 Binary files /dev/null and b/sources/academy/platform/get_most_of_actors/actor_basics/images/how-and-where-to-set-the-actor-url-console.png differ diff --git a/sources/academy/platform/get_most_of_actors/actor_basics/images/how-and-where-to-set-the-actor-url.png b/sources/academy/platform/get_most_of_actors/actor_basics/images/how-and-where-to-set-the-actor-url.png new file mode 100755 index 0000000000..8814bb64d0 Binary files /dev/null and b/sources/academy/platform/get_most_of_actors/actor_basics/images/how-and-where-to-set-the-actor-url.png differ diff --git a/sources/academy/platform/get_most_of_actors/actor_basics/images/readme.png b/sources/academy/platform/get_most_of_actors/actor_basics/images/readme.png new file mode 100755 index 0000000000..2ac7acc79c Binary files /dev/null and b/sources/academy/platform/get_most_of_actors/actor_basics/images/readme.png differ diff --git a/sources/academy/platform/get_most_of_actors/actor_basics/images/seo_description.png b/sources/academy/platform/get_most_of_actors/actor_basics/images/seo_description.png new file mode 100755 index 0000000000..c2e6086c66 Binary files /dev/null and b/sources/academy/platform/get_most_of_actors/actor_basics/images/seo_description.png differ diff --git a/sources/academy/platform/get_most_of_actors/actor_basics/images/what-is-actor-url.png b/sources/academy/platform/get_most_of_actors/actor_basics/images/what-is-actor-url.png new file mode 100755 index 0000000000..9379fcdf34 Binary files /dev/null and b/sources/academy/platform/get_most_of_actors/actor_basics/images/what-is-actor-url.png differ diff --git a/sources/academy/platform/get_most_of_actors/actor_basics/importance-of-actor-url.md b/sources/academy/platform/get_most_of_actors/actor_basics/importance-of-actor-url.md new file mode 100644 index 0000000000..48678dc7fc --- /dev/null +++ b/sources/academy/platform/get_most_of_actors/actor_basics/importance-of-actor-url.md @@ -0,0 +1,109 @@ +--- +title: Importance of Actor URL +description: Learn how to set your Actor’s URL (technical name) and name effectively when creating it on Apify. Follow best practices to optimize your Actor’s web presence and ensure it stands out on Apify Store. +sidebar_position: 2 +category: apify platform +slug: /actor-marketing-playbook/actor-basics/importance-of-actor-url +--- + +**Actor URL (or technical name, as we call it), is the page URL of the Actor shown on the web. When you're creating an Actor, you can set the URL yourself along with the Actor name. Here are best practices on how to do it well.** + +![actor url example](images/what-is-actor-url.png) + +--- + +## Why is Actor URL so important? + +The Actor URL plays a crucial role in SEO. Google doesn't just read the Actor's name or README; it also analyzes the URL. The _URL is one of the first signals to Google about the content of your page_- whether it's a product listing, a tool, a blog post, a landing page for a specific offering, or something else entirely. Therefore, it's important to know how to use this shorthand to your advantage and clearly communicate to Google what your page offers. + +:::tip Choose the URL carefully + +This part of the manual is only applicable to new Actors. _Once set, existing Actor URLs shouldn't change_. + +::: + +## How to choose a URL + +The right naming can propel or hinder the success of the Actor on Google Search. Just as naming your Actor is important, so is choosing its URL. The only difference is, once set, the URL is intended to be permanent (more on this [later](/academy/actor-marketing-playbook/actor-basics/importance-of-actor-url)). What's the formula for the best Actor URL? + +### Brainstorming + +What does your Actor do? Does it scrape, find, extract, automate, connect? Think of these when you are looking for a name. You might already have a code name in mind, but it’s essential to ensure it stands out and is distinct from similar names—both on Google and on Apify Store. + +### Matching URL and name + +The easiest way is to make sure the Actor name and the technical name match. As in TikTok Scraper (tiktok-scraper) or Facebook Data Extractor (facebook-data-extractor). But they can also be different. + +### SEO + +The name should reflect not only what Actor does (or what website it targets), but also what words people use when they search for it. This is why it's also important to do SEO research to see which keywords work best for the topic. Ideally, the URL should include a keyword that has low complexity (low competition) but high traffic (high demand). + +Learn more about SEO research and the best tools for it here: [SEO](/academy/actor-marketing-playbook/promote-your-actor/seo) + +### Inspiration in Apify Store + +Explore Store URLs of similar Actors. But avoid naming your Actor too similarly to what already exists, because of these two reasons: + +1. There’s evidence that new URLs that are similar to existing ones can have drastically different levels of success. The first URL might thrive while a similar one published later struggles to gain traction. For example, _onedev/pentagon-scraper_ was published first and has almost 100x traction than _justanotherdev/pentagon-scraper_. It will be very hard for the latter to beat the former. The reason for this is that Google operates on a "first come, first served” basis, and once it's set, it is very hard to make Google change its ways and make it pay attention to new pages with a similar name. +2. As Apify Store is growing, it's important to differentiate yourself from the competition. A different URL is just one more way to do that. If a person is doing research on Store, they will be less likely to get confused between two tools with the same name. + +### Length of URL + +Ideally, keep it under four words. As in, _Facebook Data Extractor_ (_facebook-data-extractor_), not (_facebook-data-meta-online-extractor-light_). If the name is long and you're trying to match it with your URL, keep only the most essential words for the URL. + +### Variations + +It can be a long-tail keyword with the tool type in it: scraper, finder, extractor. But you can also consider keywords that include terms like API, data, and even variations of the website name. Check out what keywords competitors outside of Apify Store are using for similar tools. + +### Nouns and adjectives + +One last tip on this topic is to _avoid adjectives and verbs_. Your page is about a tool, so keep it to nouns. Anything regarding what the tool does (scrape, automate, import) and what it's like (fast, light, best) can be expressed in the Actor's name, not the Actor's URL. Adding an adjective or verb like that either does nothing for SEO and might even damage the SEO chances of the page. + +## Why you shouldn’t change your Actor URL + +:::tip Don't change the URL + +There's only one rule about Actor URL: don't change the URL. The Actor's name, however, can be changed without any problems. + +::: + +Once set, the page URL should not be changed. Because of those two important reasons: + +- Google dislikes changes to URLs. Once your Actor has built up keyword associations and familiarity with Google, regaining that standing after a URL change can be challenging. You will have to start from scratch. +- Current integrations will break for your Actor's users. This is essential for maintaining functionality. + +If you absolutely have to change the URL, you will have to communicate that fact to your users. + +💡 Learn more about the easiest ways to communicate with your users: [Emails to Actor users] + +## How and where to set the Actor URL + +In Console. Open the **Actor's page**, then click on **…** in the top right corner, and choose ✎ **Edit name or description**. Then set the URL in the **Unique name** ✎ field and click **Save**. + +![set actor url in console](images/how-and-where-to-set-the-actor-url-console.png) + +![set the actor url](images/how-and-where-to-set-the-actor-url.png) + + +## FAQ + +#### Can Actor URL be different from Actor name? + +Yes. While they can be the same, they don’t have to be. For the best user experience, keeping them identical is recommended, but you can experiment with the Actor's name. Just avoid changing the Actor URL. + +#### Can I change a very fresh Actor URL? + +Yes, but act quickly. It takes Google a few days to start recognizing your page. For this reason, if you really have to, _it is best to change the Actor's name in the first few days_, before you build a steady user base and rapport with Google. + +#### How long does it take Google to pick up on the new URL? + +Google reindexes Apify web pages almost every day. It might take anywhere from 3-7 days for it to pick up a new URL. Or it might happen within a day. + +#### Can I use the identical technical name as this other Actor? + +Yes, you can. But it will most likely lower your chances of being noticed by Google. + +#### Does changing my Apify account name affect the Actor URL? + +Yes. If you're changing from _justanotherdev/pentagon-scraper_ to _dev/pentagon-scraper_, it counts as a new page. Essentially, the consequences are the same as after changing the technical name of the Actor. + diff --git a/sources/academy/platform/get_most_of_actors/actor_basics/name-your-actor.md b/sources/academy/platform/get_most_of_actors/actor_basics/name-your-actor.md new file mode 100644 index 0000000000..e21ce1ccfd --- /dev/null +++ b/sources/academy/platform/get_most_of_actors/actor_basics/name-your-actor.md @@ -0,0 +1,157 @@ +--- +title: Name your Actor +description: Learn Apify’s standards for naming Actors and how to choose the right name for your scraping and automation tools and maximize visibility on Apify Store. +sidebar_position: 1 +category: apify platform +slug: /actor-marketing-playbook/actor-basics/name-your-actor +--- + +**Apify's standards for Actor naming. Learn how to choose the right name for scraping and automation Actors and how to optimize your Actor for search engines.** + +--- + +Naming your Actor can be tricky, especially after you’ve worked hard on it. To help people find your Actor and make it stand out, we’ve set some naming guidelines. These will help your Actor rank better on Google and keep things consistent on [Apify Store](https://apify.com/store). + +Ideally, you should choose a name that clearly shows what your Actor does and includes keywords people might use to search for it. + +## Parts of Actor naming + +Your Actor's name consists of four parts: actual name, SEO name, URL, and GitHub repository name. + +- Actor name (name shown in Apify Store), e.g. _Booking Scraper_. + - Actor SEO name (name shown on Google Search, optional), e.g. _Booking.com Hotel Data Scraper_. + - If the SEO name is not set, the Actor name will be the default name shown on Google. +- Actor URL (technical name), e.g. _booking-scraper_. + - More on it on [Importance of Actor URL](/academy/actor-marketing-playbook/actor-basics/importance-of-actor-url) page. +- GitHub repository name (best to keep it similar to the other ones, for convenience), e.g. _actor-booking-scraper_. + +## Actor name + +The Actor name provides a human-readable name. The name is the most important real estate from an SEO standpoint. It should exactly match the most likely search query that potential users of your Actor will use. At the same time, it should give your Actor a clear name for people who will use it every day. + +:::tip + +Your Actor's name should be _40-50 characters_ long. You can change your Actor name freely in Apify Console. + +::: + +### Actor name vs. SEO name + +There's an option to step away from your Actor's name for the sake of search engine optimization — the Actor SEO name. The Actor name and Actor SEO name serve different purposes: + +- _Actor name_: this is the name visible in Apify Store and Console. It should be easy for users to understand and quickly show what your Actor does. It’s about attracting users who browse the Store. + + ![actor name example](images/actor-name.png) + +- _Actor SEO name_: this is the name that appears in search engine results. It should include keywords people might search for to find your Actor. It’s about improving visibility on search engines and encouraging users to click on your link. + + ![actor seo name example](images/actor-seo-name.png) + +For example: + +- _Actor name_: YouTube Scraper +- _Actor SEO name_: YouTube data extraction tool for video analysis + +Here, the SEO name uses extra keywords to help people find it through search engines, while the Actor name is simpler and easier for users to understand and find on Apify Store. + +💡 When creating the SEO name, focus on using relevant keywords that potential users might search for. It should still match what your Actor does. More about SEO name and description: [Actor description and SEO description] + +### Actor name vs. technical name + +The Actor name and technical name (or URL) have different uses: + +- _Actor name_: this is the name users see on Apify Store and Console. It’s designed to be user-friendly and should make the Actor's purpose clear to anyone browsing or searching for it. +- _Technical name_: this is a simplified, URL-friendly version used in technical contexts like API calls and scripts. This name should be concise and easily readable. Once set, it should not be changed as it can affect existing integrations and cause broken links. + +For example: + +- _Actor name_: Google Search Scraper +- _Technical name_: google-search-scraper + +The Actor name is user-friendly and descriptive, while the technical name is a clean, URL-compatible version. Note that the technical name does not include spaces or special characters to ensure it functions properly in technical contexts. + +:::important + +This is important for SEO! Once set, the technical name should not be changed. Make sure you finalize this name early in development. More on why here: [Importance of Actor URL] + +::: + +## Best practices for naming + +### Brainstorming + +What does your Actor do? Does it scrape, find, extract, automate, connect, or upload? When choosing a name, ensure it stands out and is distinct from similar names both on Google and on Apify Store. + +- _Use nouns and variations_: use nouns like "scraper", "extractor", “downloader”, “checker”, or "API" to describe what your Actor does. You can also include terms like API, data, or variations of the website name. +- _Include key features_: mention unique features or benefits to highlight what sets your Actor apart. +- _Check for uniqueness_: ensure your name isn’t too similar to existing Actors to avoid confusion and help with SEO. + +### Match name and URL + +The simplest approach is to make all names match. For example, TikTok Ads Scraper (tiktok-ads-scraper) or Facebook Data Extractor (facebook-data-extractor). However, variations are acceptable. + +### Name length + +Keep the name concise, ideally less than four words. For instance, Facebook Data Extractor is preferable to Facebook Meta Data Extractor Light. + +### Check Apify Store for inspiration + +Look at the names of similar Actors on Apify Store, but avoid naming your Actor too similarly. By choosing a unique name, you can stand out from the competition. This will also reduce confusion and help users easily distinguish your Actor. + +### Keep SEO in mind + +Even though you can set a different variation for SEO name specifically, consider doing a bit of research when setting the regular name as well. The name should reflect what the Actor does and the keywords people use when searching for it. If the keywords you find sound too robotic, save them for the SEO name. But if they sound like something you'd search for, it's a good candidate for a name. + +You can also check the keywords competitors use for similar tools outside Apify Store. + +### Occasionally experiment + +You can test and refine your SEO assumptions by occasionally changing the SEO name. This allows you to track how changes to names affect search rankings and user engagement. Changing the regular name is not forbidden but still less desirable since it can confuse your existing users and also affect SEO. + +## Naming examples + +### Scraping Actors + +✅: + +- Technical name (Actor's name in the [Apify Console](https://console.apify.com/)): `${domain}-scraper`, e.g. youtube-scraper. +- Actor name: `${Domain} Scraper`, e.g. YouTube Scraper. +- Name of the GitHub repository: `actor-${domain}-scraper`, e.g. actor-youtube-scraper. + +❌: + +- Technical name: `the-scraper-of-${domain}`, e.g. the-scraper-of-youtube. +- Actor name: `The Scraper of ${Domain}`, e.g. The Scraper of YouTube. +- GitHub repository: `actor-the-scraper-of-${domain}`, e.g. actor-the-scraper-of-youtube. + +If your Actor only caters to a specific service on a domain (and you don't plan on extending it), add the service to the Actor's name. + +For example, + +- Technical name: `${domain}-${service}-scraper`, e.g. google-search-scraper. +- Actor name: `${Domain} ${Service} Scraper`, e.g. [Google Search Scraper](https://apify.com/apify/google-search-scraper). +- GitHub repository: `actor-${domain}-${service}-scraper`, e.g. actor-google-search-scraper. + +### Non-scraping Actors[](https://docs.apify.com/academy/actor-marketing-playbook/naming-your-actor#non-scraping-actors) + +Naming for non-scraping Actors is more liberal. Being creative and considering SEO and user experience are good places to start. Think about what your users will type into a search engine when looking for your Actor. What is your Actor's function? + +Below are examples for the [Google Sheets](https://apify.com/lukaskrivka/google-sheets) Actor. + +✅: + +- Technical name: google-sheets. +- Actor name: Google Sheets Import & Export. +- GitHub repository: actor-google-sheets. + +❌: + +- Technical name: import-to-and-export-from-google-sheets. +- Actor name: Actor for Importing to and Exporting from Google Sheets. +- GitHub repository: actor-for-import-and-export-google-sheets. + +:::warning Renaming your Actor + +You may rename your Actor freely, except when it comes to the Actor URL. Remember to read [Importance of Actor URL](/academy/actor-marketing-playbook/actor-basics/importance-of-actor-url) to find out why! + +::: diff --git a/sources/academy/platform/get_most_of_actors/index.md b/sources/academy/platform/get_most_of_actors/index.md index 8c4efb8395..25c7aabbd0 100644 --- a/sources/academy/platform/get_most_of_actors/index.md +++ b/sources/academy/platform/get_most_of_actors/index.md @@ -1,24 +1,184 @@ --- -title: Getting the most of Actors on Apify Store -description: Learn how to optimize your public Actors on Apify Store and monetize them by renting your Actor to other platform users. +title: Actor marketing playbook +description: Learn how to optimize and monetize your Actors on Apify Store by sharing them with other platform users. sidebar_position: 10 category: apify platform -slug: /get-most-of-actors +slug: /actor-marketing-playbook --- -**Learn how to optimize your public Actors on Apify Store and monetize them by renting your Actor to other platform users.** +**Learn how to optimize and monetize your Actors on Apify Store by sharing them with other platform users.** --- -The [Apify Store](https://apify.com/store) is a marketplace featuring thousands of ready-made automation tools called Actors. As a developer, you can publish your own Actors and generate revenue through our [monetization program](https://apify.com/partners/actor-developers). +import Card from '@site/src/components/Card'; +import CardGrid from '@site/src/components/CardGrid'; -To help you succeed, we've created a comprehensive Marketing Playbook. This resource shows you how to: +[Apify Store](https://apify.com/store) is a marketplace featuring thousands of ready-made automation tools called Actors. As a developer, you can publish your own Actors and generate revenue through our [monetization program](https://apify.com/partners/actor-developers). -- Optimize your Actor's visibility in the store +To help you succeed, we've created a comprehensive Actor marketing playbook. You'll learn how to: + +- Optimize your Actor's visibility on Apify Store - Create compelling descriptions and documentation - Build your developer brand - Promote your work to potential customers - Analyze performance metrics - Engage with the Apify community -Ready to grow your presence on the platform? Check out our [Marketing Playbook](https://apify.notion.site/3fdc9fd4c8164649a2024c9ca7a2d0da?v=6d262c0b026d49bfa45771cd71f8c9ab) and learn how to [publish your first Actor](/platform/actors/publishing). +## Apify Store basics + + + + + + + + + +## Actor basics + + + + + + + + + +## Promoting your Actor + + + + + + + + + + + +## Interacting with users + + + + + + + +## Product optimization + + + + + +
+Ready to grow your presence on the Apify platform? Check out our guide to [publishing your first Actor](/platform/actors/publishing). diff --git a/sources/academy/platform/get_most_of_actors/interact_with_users/_category_.yaml b/sources/academy/platform/get_most_of_actors/interact_with_users/_category_.yaml new file mode 100644 index 0000000000..bc25bda8d9 --- /dev/null +++ b/sources/academy/platform/get_most_of_actors/interact_with_users/_category_.yaml @@ -0,0 +1,2 @@ +label: Interact with users +position: 4 diff --git a/sources/academy/platform/get_most_of_actors/interact_with_users/emails_to_actor_users.md b/sources/academy/platform/get_most_of_actors/interact_with_users/emails_to_actor_users.md new file mode 100644 index 0000000000..7fb3b97612 --- /dev/null +++ b/sources/academy/platform/get_most_of_actors/interact_with_users/emails_to_actor_users.md @@ -0,0 +1,147 @@ +--- +title: Emails to Actor users +description: Email communication is a key tool to keep users engaged and satisfied. Learn when and how to email your users effectively to build loyalty and strengthen relationships with this practical guide. +sidebar_position: 1 +category: apify platform +slug: /actor-marketing-playbook/interact-with-users/emails-to-actor-users +--- + +**Getting users is one thing, but keeping them is another. While emailing your users might not seem like a typical marketing task, any seasoned marketer will tell you it’s essential. It’s much easier to keep your current users happy and engaged than to find new ones. This guide will help you understand when and how to email your users effectively.** + +--- + +## Whom and where to email + +You can email the audience of a specific Actor directly from Apify Console. Go to **Actors > Emails > Compose new ＋**. From there, select the Actor whose users you want to email, write a subject line, and craft your message. An automatic signature will be added to the end of your email. + +## How to write a good email + +Emails can include text, formatting, images, GIFs, and links. Here are four main rules for crafting effective emails: + +1. Don’t email users without a clear purpose. +2. Keep your message concise and friendly. +3. Make the subject line direct and to the point. Consider adding an emoji to give users a hint about the email’s content. +4. Use formatting to your advantage. Console emails support Markdown, so use bold, italics, and lists to highlight important details. + +Additional tips: + +- Show, don’t tell — use screenshots with arrows to illustrate your points. +- If you’re asking users to take action, include a direct link to what you're referring to. +- Provide alternatives if it suits the situation. +- Always send a preview to yourself before sending the email to all your users. + +## When to email users + +Our general policy is to avoid spamming users with unnecessary emails. We contact them only if there's a valid reason. Here’s the list of regular good reasons to contact users of the Actor: + +### 1. Introducing a new feature of the Actor + +New filter, faster scraping, changes in input schema, in output schema, a new Integration, etc. + +>✉️ 🏙️ Introducing Deep city search for Tripadvisor scrapers +> +>Hi, +> +>Tired of Tripadvisor's 3000 hotels-per-search limit? We've got your back. Say hello to our latest baked-in feature: Deep city search. Now, to get all results from a country-wide search you need to just set Max search results above 3000, and watch the magic happen. +> +>A bit of context: while Tripadvisor never limited the search for restaurants or attractions, hotel search was a different case; it always capped at 3000. Our smart search is designed to overcome that limit by including every city within your chosen location. We scrape hotels from each one, ensuring no hidden gems slip through the cracks. This feature is available for [Tripadvisor Scraper](https://console.apify.com/actors/dbEyMBriog95Fv8CW/console) and [Tripadvisor Hotels Scraper](https://console.apify.com/actors/qx7G70MC4WBE273SM/console). +> +>So get ready for an unbeatable hotel-hunting experience. Give it a spin, and let us know what you think! + +Introduce and explain the features, add a screenshot of a feature if it will show in the input schema, and ask for feedback. + +### 2. Actor adapting to the changes of the website it scrapes + +A common situation in web scraping that's out of your control. + +>✉️ 📣 Output changes for Facebook Ads Scraper +> +>Hi, +> +>We've got some news regarding your favorite Actor – [Facebook Ads Scraper](https://console.apify.com/actors/JJghSZmShuco4j9gJ/console). Recently, Facebook Ads have changed their data format. To keep our Actor running smoothly, we'll be adapting to these changes by slightly tweaking the Actor Output. Don't worry; it's a breeze! Some of the output data might just appear under new titles. +> +>This change will take place on October 10; please** **make sure to remap your integrations accordingly. +> +>Need a hand or have questions? Our support team is just one friendly message away. + +Inform users about the reason for changes and how the changes impact them and the Actor + give them a date when the change takes effect. + +### 3. Actor changing its payment model (from rental to pay-per-result, for example) + +Email 1 (before the change, warning about deprecation). + +>✉️ 🛎 Changes to Booking Scraper +> +>Hi, +> +>We’ve got news regarding the Booking scraper you have been using. This change will happen in two steps: +> +>1. On September 22, we will deprecate it, i.e., new users will not be able to find it in Store. You will still be able to use it though. +>2. At the end of October, we will unpublish this Actor, and from that point on, you will not be able to use it anymore. +> +>Please use this time to change your integrations to our new [Booking Scraper](https://apify.com/voyager/booking-scraper). +> +>That’s it! If you have any questions or need more information, don’t hesitate to reach out. + +Warn the users about the deprecation and future unpublishing + add extra information about related Actors if applicable + give them steps and the date when the change takes effect. + +Email 2 (after the change, warning about unpublishing) + +>✉️ **📢 Deprecated Booking Scraper will stop working as announced 📢** +> +>Hi, +> +>Just a heads-up: today, the deprecated [Booking Scraper](https://console.apify.com/actors/5T5NTHWpvetjeRo3i/console) you have been using will be completely unpublished as announced, and you will not be able to use it anymore. +> +>If you want to continue to scrape Booking.com, make sure to switch to the [latest Actor version](https://apify.com/voyager/booking-scraper). +> +>For any assistance or questions, don't hesitate to reach out to our support team. + +Remind users to switch to the Actor with a new model. + +### 4. After a major issue + +Actor downtime, performance issues, Actor directly influenced by platform hiccups. + +>✉️ **🛠️ Update on Google Maps Scraper: fixed and ready to go** +> +>Hi, +> +>We've got a quick update on the Google Maps Scraper for you. If you've been running the Actor this week, you might have noticed some hiccups — scraping was failing for certain places, causing retries and overall slowness. +> +>We apologize for any inconvenience this may have caused you. The **good news is those performance issues are now resolved**. So feel free to resurrect any affected runs using the "latest" build, should work like a charm now. +> +>Need a hand or have questions? Feel free to reply to this email. + +Apologize to users and or let them know you're working on it/everything is fixed now. This approach helps maintain trust and reassures users that you're addressing the situation. + +:::tip + +It might be an obvious tip, but If you're not great at emails, just write a short draft and ask ChatGPT to polish it. Play with the style until you find the one that suits you. You can even create templates for each situation. If ChatGPT is being too wordy, you can ask it to write at 9th or 10th-grade level, and it will use simpler words and sentences. + +::: + +## Emails vs. newsletters + +While sending an email is usually a quick way to address immediate needs or support for your users, newsletters can be a great way to keep everyone in the loop on a regular basis. Instead of reaching out every time something small happens, newsletters let you bundle updates together. + +Unless it's urgent, it’s better to wait until you have 2 or 3 pieces of news and share them all at once. Even if those updates span across different Actors, it’s perfectly fine to send one newsletter to all relevant users. + +Here are a few things you can include in your newsletter: + +- updates or new features for your Actors or Actor-to-Actor Integrations +- an invitation to a live webinar or tutorial session +- asking your users to upvote your Actor, leave a review or a star +- a quick feedback request after introducing new features +- spotlighting a helpful blog post or guide you wrote or found +- sharing success stories or use cases from other users +- announcing a promotion or a limited-time discount +- links to your latest YouTube videos or tutorials + +Newsletters are a great way to keep your users engaged without overwhelming them. Plus, it's an opportunity to build a more personal connection by showing them you’re actively working to improve the tools they rely on. + +## Emailing a separate user + +There may be times when you need to reach out to a specific user — whether it’s to address a unique situation, ask a question that doesn’t fit the public forum of the **Issue tab**, or explore a collaboration opportunity. While there isn’t a quick way to do this through Apify Console just yet, you can ensure users can contact you by **adding your email or other contact info to your Store bio**. This makes it easy for them to reach out directly. + +✍🏻 Learn best practices on how to use your Store bio to connect with your users [Your Store bio](/academy/actor-marketing-playbook/interact-with-users/your-store-bio). diff --git a/sources/academy/platform/get_most_of_actors/interact_with_users/images/issues-tab-example.png b/sources/academy/platform/get_most_of_actors/interact_with_users/images/issues-tab-example.png new file mode 100755 index 0000000000..d2c5e4b532 Binary files /dev/null and b/sources/academy/platform/get_most_of_actors/interact_with_users/images/issues-tab-example.png differ diff --git a/sources/academy/platform/get_most_of_actors/interact_with_users/issues_tab.md b/sources/academy/platform/get_most_of_actors/interact_with_users/issues_tab.md new file mode 100644 index 0000000000..d604e362f9 --- /dev/null +++ b/sources/academy/platform/get_most_of_actors/interact_with_users/issues_tab.md @@ -0,0 +1,97 @@ +--- +title: Issues tab +description: Learn how the Issues tab can help you improve your Actor, engage with users, and build a reliable, user-friendly solution. +sidebar_position: 2 +category: apify platform +slug: /actor-marketing-playbook/interact-with-users/issues-tab +--- + +**Once you publish your Actor in Apify Store, it opens the door to new users, feedback, and… issue reports. Users can create issues and add comments after trying your Actor. But why is this space so important?** + +--- + +## What is the Issues tab? + +The Issues tab is a dedicated section on your Actor’s page where signed-in users can report problems, share feedback, ask questions, and have conversations with you. You can manage each issue thread individually, and the whole thread is visible to everyone. The tab is divided into three categories: **Open**, **Closed**, and **All**, and it shows how long each response has been there. While only signed-in users can post and reply, all visitors can see the interactions, giving your page a transparent and welcoming vibe. + +:::note Keep active + +🕑 On the web, your average 🕑 **Response time** is calculated and shown in your Actor Metrics. The purpose of this metric is to make it easy for potential users to see how active you are and how well-maintained the Actor is. + +::: + +You can view all the issues related to your Actors by going to **Actors** > [**Issues**](https://console.apify.com/actors?tab=issues) in Apify Console. Users can get automatic updates on their reported issues or subscribe to issues they are interested in, so they stay informed about any responses. When users report an issue, they’re encouraged to share their run, which helps you get the full context and solve the problem more efficiently. Note that shared runs aren’t visible on the public Actor page. + +## What is the Issues tab for? + +The tab is a series of conversations between you and your users. There are existing systems like GitHub for that. So why create a separate system like an Issues tab? Since the Issues tab exists both in private space (Console) and public space (Actor's page on the web), it can fulfill two different sets of purposes. + +### Issues tab in Apify Console + +Originally, the Issues tab was only available in Apify Console, and its main goals were: + +- Convenience: a single space to hold the communication between you and your users. +- Unity and efficiency: make sure multiple users don't submit the same issue through multiple channels or multiple times. +- Transparency: make sure users have their issues addressed publicly and professionally. You can’t delete issues, you can only close them, so there's a clear record of what's been resolved and how. +- Quality of service and innovation: make sure the Actor gets fixed and continuously improved, and users get the quality scraping services they pay for. + +### Issues tab on the web + +Now that the Issues tab is public and on the web, it also serves other goals: + +- Credibility: new users can check how active and reliable you are by looking at the issues and your average 🕑 **Response time** even before trying your Actor. It also sets expectations for when to expect a response from you. +- Collaboration: developers can learn from each other’s support styles, which motivates everyone to maintain good interactions and keep up good quality work. +- SEO boost: every issue now generates its own URL, potentially driving more keyword traffic to your Actor's page + +## Example of a well-managed Issues tab + +Check out how the team behind the **Apollo.io leads scraper** manages their [Issues tab](https://apify.com/curious_coder/apollo-io-scraper/issues/open) for a great example of professional responses and quick problem-solving. + +Note that this Actor is a rental, so users expect a high-quality service. + +![issues tab example](images/issues-tab-example.png) + +:::warning + +Once your Actor is public, you’re required to have an Issues tab. + +::: + +## SEO for the Issues tab + +Yes, you read that right! The public Issues tab can boost your search engine visibility. Each issue now has its own URL, which means every report could help your Actor rank for relevant keywords. + +When we made the tab public, we took inspiration from StackOverflow’s SEO strategy. Even though StackOverflow started as a Q&A forum, its strong SEO has been key to its success. Similarly, your Actor’s Issues tab can help bring in more traffic, with each question and answer potentially generating more visibility. This makes it easier for users to find solutions quickly. + +## Tips for handling Actor issues + +1. _Don’t stay silent_ + + Respond quickly, even if it’s just a short note. If an issue takes weeks to resolve, keep the user in the loop. A quick update prevents frustration and shows the user (and others following it) that you’re actively working on solving the issue. + +2. _Encourage search to avoid duplication_ + + Save time by encouraging users to search for existing issues before submitting new ones. If a similar issue exists, they can follow that thread for updates instead of creating a new one. + +3. _Encourage reporters to be specific_ + + The more context, the better! Ask users to share details about their run, which helps you diagnose issues faster. If needed, remind them that runs are shared privately, so sensitive data won’t be exposed. + +4. _Use screenshots and links_ + + The same goes for your side. Screenshots and links to specific runs make your answers much clearer. It’s easier to walk the user through a solution if they can see what you’re referencing. + +5. _Structure issue reporting_ + + As you get more experienced, you’ll notice common types of issues: bugs, feature requests, questions, reports, misc. This way, you can prioritize and respond faster based on the category. + +6. _Have ready answers for common categories_ + + Once you recognize recurring types of issues, have pre-prepared responses. For example, if it’s a bug report, you might already have a troubleshooting guide you can link to, or if it’s a feature request, you can figure out the development timeline. + +7. _Be polite and precise_ + + Politeness goes a long way! Make sure your responses are respectful and straight to the point. It helps to keep things professional, even if the issue seems minor. + + +https://rewind.com/blog/best-practices-for-using-github-issues/ diff --git a/sources/academy/platform/get_most_of_actors/interact_with_users/your_store_bio.md b/sources/academy/platform/get_most_of_actors/interact_with_users/your_store_bio.md new file mode 100644 index 0000000000..07d5e60d35 --- /dev/null +++ b/sources/academy/platform/get_most_of_actors/interact_with_users/your_store_bio.md @@ -0,0 +1,48 @@ +--- +title: Your Store bio +description: Your Apify Store bio is all about helping you promote your tools & skills. +sidebar_position: 3 +category: apify platform +slug: /actor-marketing-playbook/interact-with-users/your-store-bio +--- + +## Your Apify Store bio and Store “README” + +To help our community showcase their talents and projects, we introduced public profile pages for developers. On a dedicated page, you can showcase contact info, a summary of important Actor metrics (like total users, response time, and success rates), and all of their public Actors. We took inspiration from freelance platforms. + +This space is all about helping you shine and promote your tools and skills. Here’s how you can use it to your advantage: + +- Share your contact email, website, GitHub, X (Twitter), LinkedIn, or Discord handles. +- Summarize what you’ve been doing in Apify Store, your main skills, big achievements, and any relevant experience. +- Offer more ways for people to connect with you, such as links for booking a meeting, discounts, a subscription option for your email newsletter, or your YouTube channel or blog. + - You can even add a Linktree to keep things neat. +- Highlight your other tools on different platforms. +- Get creative by adding banners and GIFs to give your profile some personality. + +Everything is neatly available under a single URL, making it easy to share. + +Need some inspiration? Check out examples of how others are using their Store bio and README. You can set yours up by heading to **Settings > Account > Profile.** + + + +[https://apify.com/anchor](https://apify.com/anchor) + + + +[https://apify.com/jupri](https://apify.com/jupri) + + + +[https://apify.com/apidojo](https://apify.com/apidojo) + + + +[https://apify.com/curious_coder](https://apify.com/curious_coder) + + + +[https://apify.com/epctex](https://apify.com/epctex) + + + +[https://apify.com/microworlds](https://apify.com/microworlds) diff --git a/sources/academy/platform/get_most_of_actors/monetizing_your_actor.md b/sources/academy/platform/get_most_of_actors/monetizing_your_actor.md index 37d5dbd7b3..3695616e9d 100644 --- a/sources/academy/platform/get_most_of_actors/monetizing_your_actor.md +++ b/sources/academy/platform/get_most_of_actors/monetizing_your_actor.md @@ -2,7 +2,8 @@ title: Monetizing your Actor description: Learn how you can monetize your web scraping and automation projects by publishing Actors to users in Apify Store. sidebar_position: 5 -slug: /get-most-of-actors/monetizing-your-actor +slug: /actor-marketing-playbook/monetizing-your-actor +unlisted: true --- **Learn how you can monetize your web scraping and automation projects by publishing Actors to users in Apify Store.** diff --git a/sources/academy/platform/get_most_of_actors/product_optimization/_category_.yaml b/sources/academy/platform/get_most_of_actors/product_optimization/_category_.yaml new file mode 100644 index 0000000000..7df7832630 --- /dev/null +++ b/sources/academy/platform/get_most_of_actors/product_optimization/_category_.yaml @@ -0,0 +1,2 @@ +label: Product optimization +position: 5 diff --git a/sources/academy/platform/get_most_of_actors/product_optimization/actor_bundles.md b/sources/academy/platform/get_most_of_actors/product_optimization/actor_bundles.md new file mode 100644 index 0000000000..af7e87347d --- /dev/null +++ b/sources/academy/platform/get_most_of_actors/product_optimization/actor_bundles.md @@ -0,0 +1,69 @@ +--- +title: Actor bundles +description: Learn what an Actor bundle is, explore existing examples, and discover how to promote them. +sidebar_position: 2 +category: apify platform +slug: /actor-marketing-playbook/product-optimization/actor-bundles +--- + +**Learn what an Actor bundle is, explore existing examples, and discover how to promote them.** + +--- + +## What is an Actor bundle? + +If an Actor is an example of web automation software, what is an Actor bundle? An Actor bundle is basically a chain of multiple Actors unified by a common use case. Bundles can include both scrapers and automation tools, and they are usually designed to achieve an overarching goal related to scraping or automation. + +The concept of an Actor bundle originated from frequent customer requests for comprehensive tools. For example, someone would ask for a Twitter scraper that also performs additional tasks, or for a way to find all profiles of the same public figure across multiple social media platforms without needing to use each platform separately. + +For example, consider a bundle that scrapes company reviews from multiple platforms, such as Glassdoor, LinkedIn, and Indeed. Typically, you would need to use several different scrapers and then consolidate the results. But this bundle would do it all in one run, once provided with the name of the company. Or consider a bundle that scrapes all posts and comments of a given profile, and then produces a sentiment score for each scraped comment. + +The main advantage of an Actor bundle is its ease of use. The user inputs a keyword or a URL, and the Actor triggers all the necessary Actors sequentially to achieve the desired result. The user is not expected to use each Actor separately and then process and filter the results themselves. + +### Examples of bundles + +🔍 [Social Media Finder](https://apify.com/tri_angle/social-media-finder) searches for profiles on 13 social media sites provided just the (nick)name. + +🍝 [Restaurant Review Aggregator](https://apify.com/tri_angle/restaurant-review-aggregator) gets restaurant reviews from Google Maps, DoorDash, Uber Eats, Yelp, Tripadvisor, and Facebook in one place. + +🤔 [Social Media Sentiment Analysis Tool](https://apify.com/tri_angle/social-media-sentiment-analysis-tool) not only collects comments from Facebook, Instagram, and TikTok but also performs sentiment analysis on them. It unites post scrapers, comments scrapers and a text analysis tool. + +🦾 [Website Content Crawler + Pinecone bundle](https://apify.com/tri_angle/wcc-pinecone-integration) scrapes a website and stores the data in a Pinecone database to build and improve your own AI chatbot assistant. + +🤖 [Pinecone GPT Chatbot](https://apify.com/tri_angle/pinecone-gpt-chatbot) combines OpenAI's GPT models with Pinecone's vector database, which simplifies creating a GPT Chatbot. + +As you can see, they vary in complexity and range. + +--- + +## Caveats + +### Pricing model + +Since bundles are still relatively experimental, profitability is not guaranteed and will depend heavily on the complexity of the bundle. + +However, if you have a solid idea for a bundle, don’t hesitate to reach out. Prepare your case, write to our support team, and we’ll help determine if it’s worth it. + +### Specifics of bundle promotion + +First of all, when playing with the idea of creating a bundle, always check the keyword potential. Sometimes, there are true keyword gems just waiting to be discovered, with high search volume and little competition. + +However, bundles may face the challenge of being "top-of-the-funnel" solutions. People might not search for them directly because they don't have a specific keyword in mind. For instance, someone is more likely to search for an Instagram comment scraper than imagine a bundle that scrapes comments from 10 different platforms, including Instagram. + +Additionally, Google tends to favor tools with rather focused descriptions. If your tool offers multiple functions, it can send mixed signals that may conflict with each other rather than accumulate. + +Sometimes, even though a bundle can be a very innovative tool product-wise, it can be hard to market from an SEO perspective and match the search intent. + +In such cases, you may need to try different marketing and promotion strategies. Once you’ve exhausted every angle of SEO research, be prepared to explore non-organic marketing channels like Product Hunt, email campaigns, community engagement, Reddit, other social media, your existing customer base, word-of-mouth promotion, etc. + +Remember, bundles originated as customized solutions for specific use cases - they were not primarily designed to be easily found. + +This is also an opportunity to tell a story rather than just presenting a tool. Consider writing a blog post about how you created this tool, recording a video, or hosting a live webinar. If you go this route, it’s important to emphasize how the tool was created and what a technical feat it represents. + +That said, don’t abandon SEO entirely. You can still capture some SEO value by referencing the bundle in the READMEs of the individual Actors that comprise it. For example, if a bundle collects reviews from multiple platforms, potential users are likely to search for review scrapers for each specific platform—Google Maps reviews scraper, Tripadvisor reviews scraper, Booking reviews scraper, etc. These keywords may not lead directly to your review scraping bundle, but they can guide users to the individual scrapers, where you can then present the bundle as a more comprehensive solution. + +--- + +## Resources + +Learn more about Actor Bundles: https://blog.apify.com/apify-power-actors/ diff --git a/sources/academy/platform/get_most_of_actors/product_optimization/how_to_create_a_great_input_schema.md b/sources/academy/platform/get_most_of_actors/product_optimization/how_to_create_a_great_input_schema.md new file mode 100644 index 0000000000..1c9c70f1f8 --- /dev/null +++ b/sources/academy/platform/get_most_of_actors/product_optimization/how_to_create_a_great_input_schema.md @@ -0,0 +1,164 @@ +--- +title: How to create a great input schema +description: Optimizing your input schema. Learn to design and refine your input schema with best practices for a better user experience. +sidebar_position: 1 +category: apify platform +slug: /actor-marketing-playbook/product-optimization/how-to-create-a-great-input-schema +--- + +Optimizing your input schema. Learn to design and refine your input schema with best practices for a better user experience. + +--- + +## What is an input schema? + +So you've succeeded: your user has 1. found your Actor on Google, 2. explored the Actor's landing page, 3. decided to try it, and 4. created an Apify account. Now they’re on your Actor's page in Apify Console. The SEO fight is over. What’s next? + +Your user is finally one-on-one with your Actor — specifically, its input schema. This is the moment when they try your Actor and decide whether to stick with it. The input schema is your representative here, and you want it to work in your favor. + +Technically, the input schema is a `JSON` object with various field types supported by the Apify platform, designed to simplify the use of the Actor. Based on the input schema you define, the Apify platform automatically generates a _user interface_ for your Actor. + +Of course, you can create an Actor without setting up an elaborate input schema. If your Actor is designed for users who don't need a good interface (e.g. they’ll use a JSON object and call it via API), you can skip this guide. But most users engage with Actors in Manual mode, aka the Actor interface. So, if your Actor is complex or you’re targeting regular users who need an intuitive interface, it's essential to consider their experience. + +In this article, _we’ll refer to the input schema as the user interface_ of your Actor and focus exclusively on it. + +:::tip Understand input schemas + +To fully understand the recommendations in this blog post, you’ll first need to familiarize yourself with the [technical aspects of the input schema](https://docs.apify.com/platform/actors/development/actor-definition/input-schema). This context is essential to make good use of the insights shared here. + +::: + +## The importance of a good input schema + +It can feel intimidating when facing the Apify platform for the first time. You only have a few seconds for a user to assess the ease of using your Actor. + +If something goes wrong or is unclear with the input, an ideal user will first turn to the tooltips in the input schema. Next, they might check the README or tutorials, and finally, they’ll reach out to you through the **Issues** tab. However, many users won’t go through all these steps — they may simply get overwhelmed and abandon the tool altogether. + +A well-designed input schema is all about managing user expectations, reducing cognitive load, and preventing frustration. Ideally, a good input schema, as your first line of interaction, should: + +- Make the tool as easy to use as possible +- Reduce the user’s cognitive load and make them feel confident about using and paying for it +- Give users enough information and control to figure things out on their own +- Save you time on support by providing clear guidance +- Prevent incorrect or harmful tool usage, like overcharges or scraping personal information by default + +### Reasons to rework an input schema + +- Your Actor is complex and has many input fields +- Your Actor offers multiple ways to set up input (by URL, search, profile, etc.) +- You’re adding new features to your Actor +- Certain uses of the Actor have caveats that need to be communicated immediately +- Users frequently ask questions about specific fields + +👀 Input schema can be formatted using basic HTML. + +## Most important elements of the input schema + +You can see the full list of elements and their technical characteristics in [Docs](https://docs.apify.com/academy/deploying-your-code/input-schema): titles, tooltips, toggles, prefills, etc. That's not what this guide is about. It's not enough to just create an input schema, you should ideally aim to place and word its elements to the user's advantage: to alleviate the user's cognitive load and make the acquaintance and usage of your tool as smooth as possible. + +Unfortunately, when it comes to UX, there's only so much you can achieve armed with HTML alone. So here are the best elements to focus on, along with some best practices for using them effectively: + +- **`description` at the top** + - As the first thing users see, the description needs to provide crucial information and a sense of reassurance if things go wrong. Key points to mention: the easiest way to try the Actor, links to a guide, and any disclaimers or other similar Actors to try. + + ![Input schema description example](images/description-sshot.png) + + - Descriptions can include multiple paragraphs. If you're adding a link, it’s best to use the `target_blank` property so your user doesn’t lose the original Actor page when clicking. +- **`title` of the field (regular bold text)** + - This is the default way to name a field. + - Keep it brief. The user’s flow should be 1. title → 2. tooltip → 3. link in the tooltip. Ideally, the title alone should provide enough clarity. However, avoid overloading the title with too much information. Instead, make the title as concise as possible, expand details in the tooltip, and include a link in the tooltip for full instructions. + + ![Input schema input example](images/title-sshot.png) + +- **`prefill`, the default input** + - this is your chance to show rather than tell + - Keep the **prefilled number** low. Set it to 0 if it's irrelevant for a default run. + - Make the **prefilled text** example simple and easy to remember. + - If your Actor accepts various URL formats, add a few different **prefilled URLs** to show that possibility. + - Use the **prefilled date** format that the user is expected to follow. This way, they can learn the correct format without needing to check the tooltip. + - There’s also a type of field that looks like a prefill but isn’t — usually a `default` field. It’s not counted as actual input but serves as a mock input to show users what to type or paste. It is gray and disappears after clicking on it. Use this to your advantage. +- **toggle** + - The toggle is a boolean field. A boolean field represents a yes/no choice. + - So how would you word this toggle: **Skip closed places** or **Scrape open places only**? And should the toggle be enabled or disabled by default? + + ![Input schema toggle example](images/toggle-sshot.png) + + - You have to consider this when you're choosing how to word the toggle button and which choice to set up as the default. If you're making this more complex than it's needed (e.g. by using negation as the ‘yes’ choice), you're increasing your user's cognitive load. You also might get them to receive way less, or way more, data than they need from a default run. + - In our example, we assume the default user wants to scrape all places but still have the option to filter out closed ones. However, they have to make that choice consciously, so we keep the toggle disabled by default. If the toggle were enabled by default, users might not notice it, leading them to think the tool isn't working properly when it returns fewer results than expected. +- **sections or `sectionCaption` (BIG bold text) and `sectionDescription`** + - A section looks like a wrapped toggle list. + + ![Input schema sections example](images/sections-sshot.png) + + - It is useful to section off non-default ways of input or extra features. If your tool is complex, don't leave all fields in the first section. Just group them by topic and section them off (see the screenshot above ⬆️) + - You can add a description to every section. Use `sectionDescription` only if you need to provide extra information about the section (see the screenshot below ⬇️. + - sometimes `sectionDescription` is used as a space for disclaimers so the user is informed of the risks from the outset instead of having to click on the tooltip. + + ![Input schema section description example](images/section-description-sshot.png) + +- tooltips or `description` to the title + - To see the tooltip's text, the user needs to click on the `?` icon. + - This is your space to explain the title and what's going to happen in that field: any terminology, referrals to other fields of the tool, examples that don't fit the prefill, or caveats can be detailed here. Using HTML, you can add links, line breaks, code, and other regular formatting here. Use this space to add links to relevant guides, video tutorials, screenshots, issues, or readme parts if needed. + - Wording in titles vs. tooltips. Titles are usually nouns. They have a neutral tone and simply inform on what content this field is accepting (**Usernames**). + - Tooltips to those titles are usually verbs in the imperative that tell the user what to do (_Add, enter, use_). + - This division is not set in stone, but the reason why the tooltip is an imperative verb is because, if the user is clicking on the tooltip, we assume they are looking for clarifications or instructions on what to do. + + ![Input schema tooltips example](images/tooltips-sshot.png) + +- emojis (visual component) + - Use them to attract attention or as visual shortcuts. Use emojis consistently to invoke a user's iconic memory. The visual language should match across the whole input schema (and README) so the user can understand what section or field is referred to without reading the whole title. + - Don't overload the schema with emojis. They attract attention, so you need to use them sparingly. + +:::tip + +Read more on the use of emojis: [Actors and emojis] + +::: + +## Example of an improved input schema + +1. A well-used `description` space. The description briefly introduces possible scraping options, visual language (sections represented by emojis), the easiest way to try the tool, and a link to a tutorial in case of issues. The description isn't too long, uses different formatting, and looks reassuring. +2. The main section is introduced and visually separated from the rest. This is the space for the user to try the first run before they can discover the other options. +3. The title says right away that this field refers to multiple other fields, not only the first section. +4. `prefill` is a small number (so in case users run the tool with default settings, it doesn't take too long and isn't expensive for them) and uses the language of the target website (not results or posts, _videos_). +5. The tooltip expands with more details and refers to other sections it's applicable to using matching emojis. +6. Section names are short. Sections are grouped by content type. +7. More technical parameters lack emojis. They are formatted this way to attract less attention and visually inform the user that this section is the most optional to set. +8. Visual language is unified across the whole input schema. Emojis are used as a shortcut for the user to understand what section or field is referred to without actually reading the whole title. + +![Input schema example](images/improved-input-schema-example.png) + +### Example of a worse input schema + +The version above was the improved input schema. Here's what this tool's input schema looked like before: + +1. Brief and dry description, with little value for the user, easy to miss. Most likely, the user already knows this info because what this Actor does is described in the Actor SEO description, description, and README. +2. The field title is wordy and reads a bit techie: it uses terminology that's not the most accurate for the target website (_posts_) and limiting terms (_max_). The field is applicable for scraping by hashtags (field above) and by profile (section below). Easy detail to miss. +3. The prefilled number is too high. If the user runs the Actor with default settings, they might spend a lot of money, and it will take some time. Users often just leave if an Actor takes a long time to complete on the first try. +4. The tooltip simply reiterates what is said in the title. Could've been avoided if the language of the title wasn't so complex. +5. Merging two possible input types into one (profiles and URLs) can cause confusion. Verbose, reminds the user about an unrelated field (hashtags). +6. This section refers to profiles but is separate. The user had to make extra effort to scrape profiles. They have to move across 3 sections: (use Max posts from section 1, use Profiles input from section 2, use Date sorting filters from section 3). +7. The proxy and browser section invites the users to explore it even though it's not needed for a default run. It's more technical to set up and can make an impression that you need to know how to set it so the tool works. + +![Input schema example](images/worse-input-schema.png) + +## Best practices + +1. Keep it short. Don’t rely too much on text - most users prefer to read as little as possible. +2. Use formatting to your advantage (bold, italic, underline), links, and breaks to highlight key points. +3. Use specific terminology (e.g., posts, images, tweets) from the target website instead of generic terms like "results" or "pages." +4. Group related items for clarity and ease of use. +5. Use emojis as shortcuts and visual anchors to guide attention. +6. Avoid technical jargon — keep the language simple. +7. Minimize cognitive load wherever possible. + +## Signs and tools for improving input schema + +- _User feedback_. If they're asking obvious things, complaining, or consistently making silly mistakes with input, take notes. Feedback from users can help you understand their experience and identify areas for improvement. +- _High churn rates_. If your users are trying your tool but quickly abandon it, this is a sign they are having difficulties with your schema. +- _Input Schema Viewer_. Write your base schema in any code editor, then copy the file and put it into [**Input Schema Viewer](https://console.apify.com/actors/UHTe5Bcb4OUEkeahZ/source).** This tool should help you visualize your Input Schema before you add it to your Actor and build it. Seeing how your edits look in Apify Console right away will make the process of editing the fields in code easier. + +## Resources + +- Basics of input schema: [https://docs.apify.com/academy/deploying-your-code/input-schema](https://docs.apify.com/academy/deploying-your-code/input-schema) +- Specifications of input schema: [https://docs.apify.com/platform/actors/development/actor-definition/input-schema](https://docs.apify.com/platform/actors/development/actor-definition/input-schema) diff --git a/sources/academy/platform/get_most_of_actors/product_optimization/images/description-sshot.png b/sources/academy/platform/get_most_of_actors/product_optimization/images/description-sshot.png new file mode 100755 index 0000000000..49c207f274 Binary files /dev/null and b/sources/academy/platform/get_most_of_actors/product_optimization/images/description-sshot.png differ diff --git a/sources/academy/platform/get_most_of_actors/product_optimization/images/improved-input-schema-example.png b/sources/academy/platform/get_most_of_actors/product_optimization/images/improved-input-schema-example.png new file mode 100755 index 0000000000..21b8a9d7dc Binary files /dev/null and b/sources/academy/platform/get_most_of_actors/product_optimization/images/improved-input-schema-example.png differ diff --git a/sources/academy/platform/get_most_of_actors/product_optimization/images/section-description-sshot.png b/sources/academy/platform/get_most_of_actors/product_optimization/images/section-description-sshot.png new file mode 100755 index 0000000000..5191c1c608 Binary files /dev/null and b/sources/academy/platform/get_most_of_actors/product_optimization/images/section-description-sshot.png differ diff --git a/sources/academy/platform/get_most_of_actors/product_optimization/images/sections-sshot.png b/sources/academy/platform/get_most_of_actors/product_optimization/images/sections-sshot.png new file mode 100755 index 0000000000..1521e69315 Binary files /dev/null and b/sources/academy/platform/get_most_of_actors/product_optimization/images/sections-sshot.png differ diff --git a/sources/academy/platform/get_most_of_actors/product_optimization/images/title-sshot.png b/sources/academy/platform/get_most_of_actors/product_optimization/images/title-sshot.png new file mode 100755 index 0000000000..bf6795cb7b Binary files /dev/null and b/sources/academy/platform/get_most_of_actors/product_optimization/images/title-sshot.png differ diff --git a/sources/academy/platform/get_most_of_actors/product_optimization/images/toggle-sshot.png b/sources/academy/platform/get_most_of_actors/product_optimization/images/toggle-sshot.png new file mode 100755 index 0000000000..675fcb09d2 Binary files /dev/null and b/sources/academy/platform/get_most_of_actors/product_optimization/images/toggle-sshot.png differ diff --git a/sources/academy/platform/get_most_of_actors/product_optimization/images/tooltips-sshot.png b/sources/academy/platform/get_most_of_actors/product_optimization/images/tooltips-sshot.png new file mode 100755 index 0000000000..6861f81151 Binary files /dev/null and b/sources/academy/platform/get_most_of_actors/product_optimization/images/tooltips-sshot.png differ diff --git a/sources/academy/platform/get_most_of_actors/product_optimization/images/worse-input-schema.png b/sources/academy/platform/get_most_of_actors/product_optimization/images/worse-input-schema.png new file mode 100755 index 0000000000..111077ab9f Binary files /dev/null and b/sources/academy/platform/get_most_of_actors/product_optimization/images/worse-input-schema.png differ diff --git a/sources/academy/platform/get_most_of_actors/promote_your_actor/_category_.yaml b/sources/academy/platform/get_most_of_actors/promote_your_actor/_category_.yaml new file mode 100644 index 0000000000..363e5e0947 --- /dev/null +++ b/sources/academy/platform/get_most_of_actors/promote_your_actor/_category_.yaml @@ -0,0 +1,2 @@ +label: Promote your Actor +position: 3 diff --git a/sources/academy/platform/get_most_of_actors/promote_your_actor/blogs_and_blog_resources.md b/sources/academy/platform/get_most_of_actors/promote_your_actor/blogs_and_blog_resources.md new file mode 100644 index 0000000000..4d5f34bd7b --- /dev/null +++ b/sources/academy/platform/get_most_of_actors/promote_your_actor/blogs_and_blog_resources.md @@ -0,0 +1,121 @@ +--- +title: Blogs and blog resources +description: Blogs are still a powerful way to promote your Actors and build authority. By sharing expertise, engaging users, and driving organic traffic, blogging remains a key strategy to complement social media, SEO, and other platforms in growing your audience. +sidebar_position: 5 +category: apify platform +slug: /actor-marketing-playbook/promote-your-actor/blogs-and-blog-resources +--- + +**Blogs remain a powerful tool for promoting your Actors and establishing authority in the field. With social media, SEO, and other platforms, you might wonder if blogging is still relevant. The answer is a big yes. Writing blog posts can help you engage your users, share expertise, and drive organic traffic to your Actor.** + +## Why blogs still matter + +1. SEO. Blog posts are great for boosting your Actor’s search engine ranking. Well-written content with relevant keywords can attract users searching for web scraping or automation solutions. For example, a blog about “how to scrape social media profiles” could drive people to your Actor who might not find it on Google otherwise. +2. Establishing authority. When you write thoughtful, well-researched blog posts, you position yourself as an expert in your niche. This builds trust and makes it more likely users will adopt your Actors. +3. Long-form content. Blogs give you the space to explain the value of your Actor in-depth. This is especially useful for complex tools that need more context than what can fit into a README or product description. +4. Driving traffic. Blog posts can be shared across social media, linked in webinars, and included in your Actor’s README. This creates multiple avenues for potential users to discover your Actor. + +## Good topics for blog posts + +1. Problem-solving guides. Write about the specific problems your Actor solves. For example, if you’ve created an Actor that scrapes e-commerce reviews, write a post titled "How to automate e-commerce review scraping in 5 minutes". Focus on the pain points your tool alleviates. +2. Actor use cases. Show real-world examples of how your Actor can be applied. These can be case studies or hypothetical scenarios like "Using web scraping to track competitor pricing." +3. Tutorials and step-by-step guides. Tutorials showing how to use your Actor or similar tools are always helpful. Step-by-step guides make it easier for beginners to start using your Actor with minimal hassle. +4. Trends. If you’ve noticed emerging trends in web scraping or automation, write about them. Tie your Actor into these trends to highlight its relevance. +5. Feature announcements or updates. Have you recently added new features to your Actor? Write a blog post explaining how these features work and what makes them valuable. + +🪄 These days, blog posts always need to be written with SEO in mind. Yeah, it's annoying to use keywords, but think of it this way: even if there's the most interesting customer story and amazing programming insights, but nobody can find it, it won't have the impact you want. Do try to optimize your posts with relevant keywords and phrases — across text, structure, and even images — to ensure they reach your target audience. + +--- + +## Factors to consider when writing a blog + +1. Audience. Know your target audience. Are they developers, small business owners, or data analysts? Tailor your writing to match their technical level and needs. +2. SEO. Incorporate relevant keywords naturally throughout your post. Don’t overstuff your content, but make sure it ranks for search queries like "web scraping tools", "automation solutions", or "how to scrape LinkedIn profiles". Remember to include keywords in H2 and H3 headings. +3. Clarity and simplicity. Avoid jargon, especially if your target audience includes non-technical users. Use simple language to explain how your Actor works and why it’s beneficial. +4. Visuals. Include screenshots, GIFs, or even videos to demonstrate your Actor’s functionality. Visual content makes your blog more engaging and easier to follow. +5. Call to action (CTA). Always end your blog with a clear CTA. Whether it’s "try our Actor today" or "download the demo", guide your readers to the next step. +6. Engage with comments. If readers leave comments or questions, engage with them. Answer their queries and use the feedback to improve both your blog and Actor. + +--- + +## Best places to publish blogs + +There are a variety of platforms where you can publish your blog posts to reach the right audience: + +1. [Dev.to](http://dev.to/): It's a developer-friendly platform where technical content gets a lot of visibility, and a great place to publish how-to guides, tutorials, and technical breakdowns of your Actor. +2. Medium: Allows you to reach a broader, less technical audience. It’s also good for writing about general topics like automation trends or how to improve data scraping practices. +3. ScrapeDiary: Run by Apify, [scrapediary.com](http://scrapediary.com) is a blog specifically geared toward Apify community devs and web scraping topics. Publishing here is a great way to reach users already interested in scraping and automation. Contact us if you want to publish a blog post there. +4. Personal blogs or company websites. If you have your own blog or a company site, post there. It’s the most direct way to control your content and engage your established audience. + +--- + +## Not-so-obvious SEO tips for blog posts + +Everybody knows you should include keywords wherever it looks natural. Some people know the structure of the blog post should be hierarchical and follow an H1 - H2 - H3 - H4 structure with only one possible H1. Here are some unobvious SEO tips for writing a blog post that can help boost its visibility and ranking potential: + +### 1. Keep URL length concise and strategic + +Optimal length. Keep your URL short and descriptive. URLs between 50-60 characters perform best, so aim for 3-4 words. Avoid unnecessary words like "and", "of", or long prepositions. + +Include keywords. Ensure your primary keyword is naturally integrated into the URL. This signals relevance to both users and search engines. + +Avoid dates. Don’t include dates or numbers in the URL to keep the content evergreen, as dates can make the post seem outdated over time. + +### 2. Feature a video at the top of the post + +Engagement boost. Videos significantly increase the time users spend on a page, positively influencing SEO rankings. Blog posts with videos in them generally do better SEO-wise. + +Thumbnail optimization. Use an optimized thumbnail with a clear title and engaging image to increase click-through rates. + +### 3. Alt text for images with a keyword focus + +Descriptive alt text. Include a short, descriptive alt text for every image with one or two keywords where it makes sense. This also improves accessibility. + +Optimize file names. Name your images with SEO-friendly keywords before uploading (e.g., "web-scraping-tools.png" rather than "IMG12345_screenshot1.png"). This helps search engines understand the content of your images. + +File format and size. Use web-optimized formats like WebP or compressed JPEGs/PNGs to ensure fast page loading, which is a key SEO factor. + +Lazy loading images. Use lazy loading to only load images when the user scrolls to them, reducing initial page load times, which can help your SEO ranking. + +### 4. Interlinking for better user experience and SEO + +Internal links. Use contextual links to other relevant blog posts or product pages on your site. This not only helps with SEO but also keeps users engaged longer on your site, reducing bounce rates. + +Anchor text. When linking internally, use keyword-rich anchor text that describes what users will find on the linked page. + +Content depth. By interlinking, you can show Google that your site has a strong internal structure and is a hub of related, authoritative content. + +### 5. Target the 'People Also Ask' section of Google results with an FAQ + +Answer common questions. Including an FAQ section that answers questions people search for can help you rank in the "People Also Ask" section of Google. Research questions that come up in this feature related to your topic and address them in your content. + +Provide clear, concise answers to the FAQs, typically between 40-60 words, since these match the format used in "People Also Ask". + +Don't bother using FAQ schema. Google doesn't react to those anymore unless you’re a .gov or .edu domain. + +### 6. Optimize for readability and structure + +Short paragraphs and subheadings. Make your blog post easy to scan by using short paragraphs and meaningful subheadings that contain keywords. + +Bullet points and lists. Include bullet points and numbered lists to break up content and make it more digestible. Search engines prioritize well-structured content. + +Readability tools. Use tools like Hemingway Editor or Grammarly to improve readability. Content that is easy to read tends to rank higher, as it keeps readers engaged. + +## Referring to blogs in your Actor’s ecosystem + +To drive traffic to your blog and keep users engaged, reference your blog posts across various touchpoints: + +1. README. Add links to your blog posts in your Actor’s README. If you’ve written a tutorial or feature guide, include it under a "Further reading" section. +2. Input schema. Use your input schema to link to blog posts. For instance, if a certain field in your Actor has complex configurations, add a link to a blog post that explains how to use it. +3. YouTube videos. If you’ve created tutorial videos about your Actor, link them in your blog and vice versa. Cross-promoting these assets will increase your overall engagement. +4. Webinars and live streams. Mention your blog posts during webinars, especially if you’re covering a topic that’s closely related. Include the links in follow-up emails after the event. +5. Social media. Share your blog posts on Twitter, LinkedIn, or other social platforms. Include snippets or key takeaways to entice users to click through. + +🔄 Remember, you can always turn your blog into a video and vice versa. You can also use parts of blog posts for social media promotion. + +## Additional tips for blog success + +1. Consistency. Regular posting helps build an audience and makes sure you keep at it. Try to stick to a consistent schedule, whether it’s weekly, bi-weekly, or monthly. As Woody Allen said, “80 percent of success is showing up”. +2. Guest blogging. Reach out to other blogs or platforms like [Dev.to](http://dev.to/) for guest blogging opportunities. This helps you tap into new audiences. +3. Repurpose content. Once you’ve written a blog post, repurpose it. Turn it into a YouTube video, break it down into social media posts, or use it as the base for a webinar. +4. Monitor performance. Use analytics to track how your blog is performing. Are people reading it? Is it driving traffic to your Actor? What keywords is it ranking for? Who are your competitors? Use this data to refine your content strategy. diff --git a/sources/academy/platform/get_most_of_actors/promote_your_actor/parasite_seo.md b/sources/academy/platform/get_most_of_actors/promote_your_actor/parasite_seo.md new file mode 100644 index 0000000000..df4b101b28 --- /dev/null +++ b/sources/academy/platform/get_most_of_actors/promote_your_actor/parasite_seo.md @@ -0,0 +1,63 @@ +--- +title: Parasite SEO +description: Explore parasite SEO, a unique strategy that leverages third-party sites to boost rankings and drive traffic to your tools. +sidebar_position: 3 +category: apify platform +slug: /actor-marketing-playbook/promote-your-actor/parasite-seo +--- + +**Do you want to attract more users to your Actors? Consider parasite SEO, a non-conventional method of ranking that leverages third-party sites.** + +--- + +Here’s a full definition, from Authority Hackers: + +> Parasite SEO involves publishing a quality piece of content on an established, high-authority external site to rank on search engines. This gives you the benefit of the host’s high traffic, boosting your chances for leads and successful conversions. These high DR websites have a lot of authority and trust in the eyes of Google +> + +As you can see, you’re leveraging the existing authority of a third-party site where you can publish content promoting your Actors, and the content should rank better and faster as you publish it on an established site. + +You can do parasite SEO for free, but you can also pay for guest posts on high-authority sites to post your articles promoting the Actors. + +Let’s keep things simple and practical for this guide, so you can start immediately. We will cover only the free options, which should give you enough exposure to get started. + +If you want to learn more, we recommend the following reading about parasite SEO: + +- [Authority Hackers](https://www.authorityhacker.com/parasite-seo/) +- [Ahrefs](https://ahrefs.com/blog/parasite-seo/) + +In this guide, we will cover the following sites that you can use for parasite SEO for free: + +- Medium +- LinkedIn +- Reddit +- Quora + +## Medium + +You probably know [Medium](https://medium.com/). But you might not know that Google quite likes Medium, and you have a good chance of ranking high in Google with articles you publish there. + +1. You need a Medium account. It’s free and easy to create. +2. Now, you need to do keyword research. Go to [Ahrefs Free Keyword Generator](https://ahrefs.com/keyword-generator/?country=us), enter your main keyword (e.g. Airbnb scraper), and check what keyword has the highest search volume. +3. Search for that keyword in Google. Use incognito mode and a US VPN if you can. Analyze the results and check what type of content you need to create. Is it a how-to guide on how to create an Airbnb scraper? Or is it a list of the best Airbnb scrapers? Or perhaps it’s a review or just a landing page. +4. Now, you should have a good idea of the article you have to write. Write the article and try to mimic the structure of the first results. Check the [SEO guide](https://docs.google.com/document/d/17fGGo1yGpYPvPFClShEpMuDnP0Y_ziU3EdMvaDZy0ms/edit#) for more guidance. +5. Once you’re done with the article, don’t forget to include a few calls to action linking to your Actor on Apify Store. Don’t be too pushy, but mention all the benefits of your Actor. +6. Publish the article. Make sure your title and URL have the main keyword and that the main keyword is also in the first paragraph of the article. Also, try to use relevant tags for your Actor. + +## LinkedIn Pulse + +LinkedIn Pulse is similar to Medium, so we won’t go into too much detail. The entire process is the same as with Medium; the way you publish the article differs. + +[Here is a full guide](https://www.linkedin.com/pulse/how-publish-content-linkedin-pulse-hamza-sarfraz/) for publishing your article on LinkedIn Pulse. + +## Reddit + +1. You must have a Reddit account to use to comment in relevant Subreddits. +2. Go to Google and perform this search: `site:reddit.com `, where you replace `` with the main topic of your Actor. +3. Now, list relevant Reddit threads that Google gives you. For an Airbnb scraper, this might be a good thread: [Has anybody have an latest Airbnb scraper code?](https://www.reddit.com/r/webscraping/comments/m650ol/has_anybody_have_an_latest_airbnb_scraper_code/) +4. To prioritize threads from the list, you can check the traffic they get from Google in [Ahrefs Traffic Checker](https://ahrefs.com/traffic-checker). Just paste the URL, and the tool will give you traffic estimation. You can use this number to prioritize your list. If the volume exceeds 10, it usually has some traffic potential. +5. Now, the last step is to craft a helpful comment that also promotes your Actor. Try to do that subtly. People on Reddit usually don’t like people who promote their stuff, but you should be fine if you’re being genuinely helpful. + +## Quora + +Quora is similar to Reddit, so again we won’t go into too much detail. The entire process is the same. You just have to use a different search phrase in Google, which is `site:quora.com `. diff --git a/sources/academy/platform/get_most_of_actors/promote_your_actor/product_hunt.md b/sources/academy/platform/get_most_of_actors/promote_your_actor/product_hunt.md new file mode 100644 index 0000000000..474cb80a3f --- /dev/null +++ b/sources/academy/platform/get_most_of_actors/promote_your_actor/product_hunt.md @@ -0,0 +1,76 @@ +--- +title: Product Hunt +description: Boost your Actor’s visibility by launching it on Product Hunt, a top platform for tech innovations. Attract early adopters, developers, and businesses while showcasing your tool’s value through visuals or demos. +sidebar_position: 4 +category: apify platform +slug: /actor-marketing-playbook/promote-your-actor/product-hunt +--- + +Product Hunt is one of the best platforms for introducing new tools, especially in the tech community. It attracts a crowd of early adopters, startup enthusiasts, and developers eager to discover the latest innovations. Even [Apify itself](https://www.producthunt.com/products/apify) was on PH. + +If you're looking to build awareness and generate short-term traffic, Product Hunt can be a powerful tool in your marketing strategy. It's a chance to attract a wide audience, including developers, startups, and businesses looking for automation. If your Actor solves a common problem, automates a tedious process, or enhances productivity, it's a perfect candidate for Product Hunt. + +Product Hunt is also great for tools with a strong visual component or demo potential. If you can show the value of your Actor in action, you’re more likely to grab attention and drive engagement. + +--- + +## How to promote your Actor on Product Hunt + +### Create a compelling launch + +Launching your Actor on Product Hunt requires thoughtful planning. Start by creating a product page that clearly explains what your Actor does and why it’s valuable. You’ll need: + +- _A catchy tagline_. Keep it short and to the point. Think of something that captures your Actor's essence in just a few words. +- _Eye-catching visuals_. Screenshots, GIFs, or short videos that demonstrate your Actor in action are essential. Show users what they’ll get, how it works, and why it’s awesome. +- _Concise description_. Write a brief description of what your Actor does, who it’s for, and the problem it solves. Use plain language to appeal to a wide audience, even if they aren’t developers. +- _Demo video_. A short video that shows how your Actor works in a real-life scenario will resonate with potential users. + +Once your page is set up, you’ll need to choose the right day to launch. Product Hunt is most active on weekdays, with Tuesday and Wednesday being the most popular launch days. Avoid launching on weekends or holidays when traffic is lower. + +### Build momentum before launch + +Start building awareness before your launch day. This is where your social media channels and community engagement come into play. Share teasers about your upcoming Product Hunt launch on Twitter (X), Discord, LinkedIn, and even StackOverflow, where other developers might take an interest. Highlight key features or the problems your Actor solves. + +If you have a mailing list, give your subscribers a heads-up about your launch date. Encourage them to visit Product Hunt and support your launch by upvoting and commenting. This pre-launch activity helps create early momentum on launch day. + +### Timing your launch + +The timing of your Product Hunt launch matters a lot. Since Product Hunt operates on a daily ranking system, getting in early gives your product more time to gain votes. Aim to launch between 12:01 AM and 2:00 AM PST, as this will give your product a full day to collect upvotes. + +Once you’ve launched, be ready to engage with the community throughout the day. Respond to comments, answer questions, and thank users for their support. Product Hunt users appreciate creators who are active and communicative, and this can help drive more visibility for your Actor. + +### Engage with your audience + +The first few hours after your launch are crucial for gaining traction. Engage with users who comment on your product page, answer any questions, and address any concerns they might have. The more interaction you generate, the more likely you are to climb the daily rankings. + +Be transparent and friendly in your responses. If users point out potential improvements or bugs, acknowledge them and make a commitment to improve your Actor. Product Hunt users are often open to giving feedback, and this can help you iterate on your product quickly. + +If possible, have team members or collaborators available to help respond to comments. The more responsive and helpful you are, the better the overall experience will be for users checking out your Actor. + +:::tip Leverage Apify + +You can also give a shoutout to Apify, this way your Actor will also notified to the community of Apify on Product Hunt: [https://www.producthunt.com/stories/introducing-shoutouts](https://www.producthunt.com/stories/introducing-shoutouts) + +::: + +## Expectations and results + +Launching on Product Hunt can provide a massive spike in short-term traffic and visibility. However, it’s important to manage your expectations. Not every launch will result in hundreds of upvotes or immediate sales. Here’s what you can realistically expect: + +- _Short-term traffic boost_. Your Actor might see a surge in visitors, especially on the day of the launch. If your Actor resonates with users, this traffic may extend for a few more days. +- _Potential long-term benefits_. While the short-term traffic is exciting, the long-term value lies in the relationships you build with early users. Some of them may convert into paying customers or become advocates for your Actor. +- _SEO boost_. Product Hunt is a high-authority site with a 91 [domain rating](https://help.ahrefs.com/en/articles/1409408-what-is-domain-rating-dr). Having your product listed can provide an SEO boost and help your Actor's page rank higher in search engines. +- _User feedback_. Product Hunt is a great place to gather feedback. Users may point out bugs, request features, or suggest improvements. + +## Tricks for a successful launch + +1. _Leverage your network_. Ask friends, colleagues, and early users to support your launch. Ask the Apify community. Ask your users. Encourage them to upvote, comment, and share your product on social media. +2. _Prepare for feedback_. Product Hunt users can be critical, but this is an opportunity to gather valuable insights. Be open to suggestions and use them to improve your Actor. +3. _Use a consistent brand voice_. Make sure your messaging is consistent across all platforms when you're responding to comments and promoting your launch on social media. +4. _Offer a special launch deal_. Incentivize users to try your Actor by offering a discount or exclusive access for Product Hunt users. This can drive early adoption and build momentum. + +## Caveats to Product Hunt promotion + +- _Not every Actor is a good fit_. Product Hunt is best for tools with broad appeal or innovative features. If your Actor is highly specialized or niche, it may not perform as well. +- _High competition_. Product Hunt is a popular platform, and your Actor will be competing with many other launches. A strong marketing strategy is essential to stand out. +- _Short-term focus_. While the traffic spike is great, Product Hunt tends to focus on short-term visibility. To maintain long-term growth, you’ll need to continue promoting your Actor through other channels. diff --git a/sources/academy/platform/get_most_of_actors/promote_your_actor/seo.md b/sources/academy/platform/get_most_of_actors/promote_your_actor/seo.md new file mode 100644 index 0000000000..4e474e45ba --- /dev/null +++ b/sources/academy/platform/get_most_of_actors/promote_your_actor/seo.md @@ -0,0 +1,124 @@ +--- +title: SEO +description: Learn how to optimize your content to rank higher on search engines like Google and Bing, attract more users, and drive long-term traffic - all for free. +sidebar_position: 1 +category: apify platform +slug: /actor-marketing-playbook/promote-your-actor/seo +--- + +SEO means optimizing your content to rank high for your target queries in search engines such as Google, Bing, etc. SEO is a great way to get more users for your Actors. It’s also free, and it can bring you traffic for years. This guide will give you a simple framework to rank better for your targeted queries. + +## Search intent + +Matching the search intent of potential users is super important when creating your Actor's README. The information you include should directly address the problems or needs that led users to search for a solution like yours. For example: + +- _User goals_: What are users trying to accomplish? +- _Pain points_: What challenges are they facing? +- _Specific use cases_: How might they use your Actor? + +Make sure your README demonstrates how your Actor aligns with the search intent. This alignment helps users quickly recognize your Actor's value and helps Google understand your Actor and rank you better. + +_Example:_ + +Let’s say you want to create a “YouTube Hashtag Scraper” Actor. After you search YouTube HashTag Scraper, you see that most people searching for it want to extract hashtags from YouTube videos, not download videos using a certain hashtag. + +## Keyword research + +Keyword research is a very important part of your SEO success. Without that, you won’t know which keywords you should target with your Actor, and you might be leaving traffic on the table by not targeting all the angles or targeting the wrong one. + +We will do keyword research with free tools, but if you want to take this seriously, we highly recommend [Ahrefs](https://ahrefs.com/). + +### Google autocomplete suggestions + +Start by typing your Actor's main function or purpose into Google. As you type, Google will suggest popular search terms. These suggestions are based on common user queries and can provide insight into what your potential users are searching for. + +_Example:_ + +Let's say you've created an Actor for scraping product reviews. Type "product review scraper" into Google and note the suggestions: + +- product review scraper free +- product review scraper amazon +- product review scraper python +- product review scraper api + +These suggestions reveal potential features or use cases to highlight in your README. + +### Alphabet soup method + +This technique is similar to the previous one, but it involves adding each letter of the alphabet after your main keyword to discover more specific and long-tail keywords. + +_Example_: + +Continue with "product review scraper" and add each letter of the alphabet: + +- product review scraper a (autocomplete might suggest "api") +- product review scraper b (might suggest "best") +- product review scraper c (might suggest "chrome extension") + +...and so on through the alphabet. + +### People Also Ask + +Search for your Actor's main function or purpose on Google. Scroll down to find the "People Also Ask" section, which contains related questions. + +_Example_: + +For a "product review scraper" Actor: + +- How do I scrape product reviews? +- Is it legal to scrape product reviews? +- What is the best tool for scraping reviews? +- How can I automate product review collection? + +Now, you can expand the “People Also Ask” questions. Click on each question to reveal the answer and generate more related questions you can use in your README. + +### Google Keyword Planner + +Another way to collect more keywords is to use the official Google Keyword Planner. Go to [Google Keyword Planner](https://ads.google.com/home/tools/keyword-planner/) and open the tool. You need a Google Ads account, so just create one for free if you don’t have one already. + +After you’re in the tool, click on “Discover new keywords”, make sure you’re in the “Start with keywords” tab, enter your Actor's main function or purpose, and then select the United States as the region and English as the language. Click “Get results” to see keywords related to your actor. + +Write them down. + +### Ahrefs Keyword Generator + +Go to [Ahrefs Keyword Generator](https://ahrefs.com/keyword-generator), enter your Actor's main function or purpose, and click “Find keywords.” You should see a list of keywords related to your actor. + +Write them down. + +## What to do with the keywords + +First, remove any duplicates that you might have on your list. You can use an online tool [like this one](https://dedupelist.com/) for that. + +After that, we need to get search volumes for your keywords. Put all your keywords in a spreadsheet, with one column being the keyword and the second one being the search volume. + +Go to the [Keyword Tool](https://backlinko.com/tools/keyword), enter the keyword, and write down the search volume. You will also see other related keywords, so you might as well write them down if you don’t have them on your list yet. + +At the end, you should have a list of keywords together with their search volumes that you can use to prioritize the keywords, use the keywords to name your Actor, choose the URL, etc. + +### Headings + +If it makes sense, consider using keywords with the biggest search volume and the most relevant for your Actor as H2 headings in your README. + +Put the most relevant keyword at the beginning of the heading when possible. Also, remember to use a clear hierarchy. The main features are H2, sub-features are H3, etc. + +### Content + +When putting keywords in your Actor’s README, it's important to maintain a natural, informative tone. Your primary goal should be to create valuable, easily understandable content for your users. + +Aim to use your most important keyword in the first paragraph of your README. This helps both search engines and users quickly understand what your Actor does. But avoid forcing keywords where they don't fit naturally. + +In your content, you can use the keywords you gathered before where they make sense. We want to include those keywords naturally in your README. + +If there are relevant questions in your keyword list, you can always cover them within an “FAQ” section of your Actor. + +Remember that while including keywords is important, always prioritize readability and user experience. Your content should flow naturally and provide real value to the reader. + +## Learn more about SEO + +If you want to learn more about SEO, these two free courses will get you started: + +- [SEO Course for Beginners](https://ahrefs.com/academy/seo-training-course) by Ahrefs +- [SEO Courses](https://www.semrush.com/academy/courses/seo/) by Semrush + +The [Ahrefs YouTube channel](https://www.youtube.com/@AhrefsCom/featured) is also a great resource. You can start with [this video](https://www.youtube.com/watch?v=xsVTqzratPs). diff --git a/sources/academy/platform/get_most_of_actors/promote_your_actor/social_media.md b/sources/academy/platform/get_most_of_actors/promote_your_actor/social_media.md new file mode 100644 index 0000000000..7b772c1ca8 --- /dev/null +++ b/sources/academy/platform/get_most_of_actors/promote_your_actor/social_media.md @@ -0,0 +1,95 @@ +--- +title: Social media +description: Leverage social media to connect with users and grow your Actor’s audience. Learn how to showcase features, engage with users, and avoid common pitfalls. +sidebar_position: 2 +category: apify platform +slug: /actor-marketing-playbook/promote-your-actor/social-media +--- + +**Social media is a powerful way to connect with your Actor users and potential users. Whether your tool focuses on web scraping or automation, social platforms can help you showcase its features, answer user questions, and grow your audience. This guide will show you how to use social media effectively, what to share, and how to avoid common mistakes along the way.** + +Now, before we start listing social media platforms, it might be important to acknowledge something. + +Developers are notorious for not using social media that much. Or they use social media exclusively in the context of their own interests: that won’t find them new users, but rather colleagues or collaborators. + +That's a good start, and maybe it's enough. A developer that can also “do” social media is a unicorn. These are super rare. And if you want to really promote your Actor, you'll need to become that unicorn. Before we start, you need to understand the benefits of this activity. + +--- + +## Why be active on social media + +Engaging with your users on social media offers a lot of benefits beyond just promoting your Actor. Let’s look at some of the main reasons why being active online can be a game-changer for your Actor’s success: + +1. Social platforms make it easy to gather real-time feedback and also provide support in real-time. You can quickly learn what users love, what they struggle with, and what features they’d like to see. This can guide your Actor’s future development. It also allows you to build trust and credibility with your audience. +2. Shot in the dark: social media exposes your Actor to new users who might not find you through search engines alone. A shared post or retweet can dramatically expand your reach, helping you grow your user base. +3. Consistent activity on social platforms creates more backlinks to your Actor’s page, which can improve its search engine ranking and drive organic traffic. + +## Where to engage: Choosing the right platforms + +Choosing the right platforms is key to reaching your target audience. Here's a breakdown of the best places for developers to promote their web scraping and automation tools: + +- _Discord_: We started with an easy one. Create a community around your Actor to engage with users directly. Offering quick support and discussing the features of your Actor in a real-time chat setting can lead to deeper user engagement. + + :::tip Use Apify's Discord + + You can also promote your tools through [Apify's Discord](https://discord.com/invite/crawlee-apify-801163717915574323). + + ::: + +- _Twitter (X)_: Good for short updates, feature announcements, and quick interactions with users. The tech community on Twitter is very active, which makes it a great spot for sharing tips and getting noticed. +- _Reddit_: In theory, subreddits like r/webscraping, r/automation, and r/programming allow you to share expertise, engage in discussions, and present your Actor as a solution. However, in reality, you have to be quite careful with promotion there. Be very mindful of subreddit rules to avoid spamming or over-promoting. For Reddit, personal stories on how you built the tool + a roadblock you might be facing right now are the safest formula. If a tool is already finished and perfected, it will be treated as promotional content. But if you're asking for advice - now that's a community activity. +- _TikTok_: Might not be an obvious choice, but that’s where most young people spend time. They discuss a myriad of topics, laugh at the newest memes, and create trends that take weeks to get to Reels and Shorts. If you want to create educational, fun, short video content (and be among the first to talk about web scraping), this is your place for experiments and taking algorithm guesses. +- _YouTube_: Ideal for tutorials and demos. A visual walk-through of how to use your Actor can attract users who prefer watching videos to reading tutorials or READMEs. It's also good for Shorts and short, funny content. +- _StackOverflow_: While not a traditional social media platform, StackOverflow is a great space to answer technical questions and demonstrate your expertise. Offering help related to web scraping or automation can build credibility, and you can subtly mention your Actor if it directly solves the issue (as long as it adheres to community guidelines). +- _LinkedIn_: If your Actor solves problems for professionals or automates business tasks, LinkedIn is the place to explain how your tool provides value to an industry or business. + +--- + +## Best practices for promoting your Actor on social media + +Now that you know where to engage and why it’s important, here are some best practices to help you make the most of social media: + +1. _Offer value beyond promotion_: If you look around, you'll see that the golden rule of social media these days is to educate and entertain. Focus on sharing useful information related to your Actor. Post tips on automation, web scraping techniques, or industry insights that can help your audience. When you do promote your Actor, users will see it as part of a valuable exchange, not just an ad. Besides, constantly posting promotional content turns anybody off. +2. _Post consistently_: The most important rule for social media is to show up. Whether it’s a weekly post about new features or daily tips for using your Actor more effectively, maintaining a regular posting schedule keeps your audience connected. +3. _Visuals matter_: Screenshots, GIFs, and short videos can explain more than text ever could. Show users how your Actor works, the results it scrapes, or how automation saves time. +4. _Widen your reach_: Web scraping is a niche topic. Find ways to talk about it more widely. If you stumble upon ways to relate it to wider topics: news, science, research, even politics and art, use it. Or you can go more technical and talk about various libraries and languages you can use to build it. +5. _Use relevant hashtags_: Hashtags like #webscraping, #automation, #programming, and #IT help you reach a wider audience on platforms like Twitter and TikTok. Stick to a few relevant hashtags per post to avoid clutter. +6. _Engage actively_: Social media is a two-way street. Reply to comments, thank users for sharing your content, create stitches, and answer questions. Building relationships with your users helps foster loyalty and builds a sense of community around your Actor. +7. _Use polls and Q&As_: Interactive content like polls or Q&A sessions can drive engagement. Ask users what features they’d like to see next or run a live Q&A to answer questions about using your Actor. These tools encourage participation and provide valuable insights. +8. _Collaborate with other creators_. + +## Caveats to social media engagement + +1. _Over-promotion_: Constantly pushing your Actor without offering value can turn users away. Balance your promotional content with educational posts, interesting links, or insights into the development process. Users are more likely to engage when they feel like they’re learning something, rather than just being sold to. +2. _Handling negative feedback_: Social media is a public forum, and not all feedback will be positive. Be prepared to address user concerns or criticism professionally. Responding kindly (or funnily) to criticism shows you’re committed to improving your tool and addressing users' needs. +3. _Managing multiple platforms_: Social media management can be time-consuming, especially if you’re active on multiple platforms. Focus on one or two platforms that matter most to your audience instead of spreading yourself too thin. +4. _Algorithm changes_: Social media platforms often tweak their algorithms, which can impact your content’s visibility. Stay updated on these changes, and adjust your strategy accordingly. If a post doesn’t perform well, experiment with different formats (videos, visuals, polls) to see what resonates with your audience. +5. _Privacy and compliance_: Very important here to be mindful of sharing user data or results, especially if your Actor handles sensitive information. Make sure your posts comply with privacy laws and don’t inadvertently expose any personal data. + +## For inspiration + +It's sometimes hard to think of a good reason to scream into the void that is social media. Here are 25 scenarios where you might use social media to promote your Actor or your work: + +1. _Funny interaction with a user_: Share a humorous tweet or post about a quirky question or feedback from a user that highlights your Actor’s unique features. +2. _Roadblock story_: Post about a challenging bug you encountered while developing your Actor and how you solved it, including a screenshot or snippet of code. +3. _Success story_: Share a post detailing how a user’s feedback led to a new feature in your Actor and thank them for their suggestion. +4. _Tutorial video_: Create and share a short video demonstrating how to use a specific feature of your Actor effectively. +5. _Before-and-after example_: Post a visual comparison showing the impact of your Actor’s automation on a task or process. +6. _Feature announcement_: Announce a new feature or update in your Actor with a brief description and a call-to-action for users to try it out. +7. _User testimonial_: Share a positive review or testimonial from a user who benefited from your Actor, including their quote and a link to your tool. +8. _Live Q&A_: Host a live Q&A session on a platform like Twitter or Reddit, answering questions about your Actor and its capabilities. +9. _Behind-the-scenes look_: Post a behind-the-scenes photo or video of your development process or team working on your Actor. +10. _Debugging tip_: Share a tip or trick related to debugging or troubleshooting common issues with web scraping or automation. +11. _Integration highlight_: Post about how your Actor integrates with other popular tools or platforms, showcasing its versatility. Don't forget to tag them. +12. _Case study_: Share a case study or success story showing how a business or individual used your Actor to achieve specific results. +13. _Commentary on a news piece_: Offer your perspective on a recent news story related to technology, scraping, or automation. If possible, explain how it relates to your Actor. +14. _User-generated content_: Share content created by your users, such as screenshots or examples of how they’re using your Actor. +15. _Memes_: Post a relevant meme about the challenges of web scraping or automation. +16. Milestone celebration: Announce and celebrate reaching a milestone, such as a certain number of users or downloads for your Actor. +17. _Quick tip_: Share a short, useful tip or hack related to using your Actor more efficiently. +18. _Throwback post_: Share a throwback post about the early development stages of your Actor, including any challenges or milestones you achieved. +19. _Collaboration announcement_: Announce a new collaboration with another developer or tool, explaining how it enhances your Actor’s functionality. +20. _Community shout-out_. Give a shout-out to a user or community member who has been particularly supportive or helpful. +21. _Demo invitation_: Invite your followers to a live demo or webinar where you’ll showcase your Actor and answer questions. +22. _Feedback request_: Ask your audience for feedback on a recent update or feature release, and encourage them to share their thoughts. +23. _Book or resource recommendation_: Share a recommendation for a book or resource that helped you in developing your Actor, and explain its relevance. diff --git a/sources/academy/platform/get_most_of_actors/promote_your_actor/video_tutorials.md b/sources/academy/platform/get_most_of_actors/promote_your_actor/video_tutorials.md new file mode 100644 index 0000000000..4972b05c63 --- /dev/null +++ b/sources/academy/platform/get_most_of_actors/promote_your_actor/video_tutorials.md @@ -0,0 +1,47 @@ +--- +title: Video tutorials +description: Use video tutorials to demonstrate features, offer tutorials, and connect with users in real time, building trust and driving interest in your tools. +sidebar_position: 6 +category: apify platform +slug: /actor-marketing-playbook/promote-your-actor/video-tutorials +--- + +**Videos and live streams are powerful tools for connecting with users and potential users, especially when promoting your Actors. You can use them to demonstrate functionality, provide tutorials, or engage with your audience in real time.** + +--- + +## Why videos and live streams matter + +1. _Visual engagement_. Videos allow you to show rather than just tell. Demonstrating how your Actor works or solving a problem in makes the content more engaging and easier to understand. For complex tools, visual explanations can be much more effective than text alone. +2. _Enhanced communication_. Live streams offer a unique opportunity for direct interaction. You can answer questions, address concerns, and gather immediate feedback from your audience, creating a more dynamic and personal connection. +3. _Increased reach_. Platforms like YouTube and TikTok have massive user bases, giving you access to a broad audience. Videos can also be shared across various social media channels, extending your reach even further. + +Learn more about the rules of live streams in our next section: [Webinars](/academy/actor-marketing-playbook/promote-your-actor/webinars) + +## Optimizing videos for SEO + +1. _Keywords and titles_. Use relevant keywords in your video titles and descriptions. For instance, if your Actor is a web scraping tool, include terms like “web scraping tutorial” or “how to use web scraping tools” to help users find your content. +2. _Engaging thumbnails_. Create eye-catching thumbnails that accurately represent the content of your video. Thumbnails are often the first thing users see, so make sure they are visually appealing and relevant. +3. _Transcriptions and captions_. Adding transcripts and captions to your videos improves accessibility and can enhance SEO. They allow search engines to index your content more effectively and help users who prefer reading or have hearing impairments. + +## YouTube vs. TikTok + +1. _YouTube_. YouTube is an excellent platform for longer, detailed videos. Create a channel dedicated to your Actors and regularly upload content such as tutorials, feature walkthroughs, and industry insights. Utilize YouTube’s SEO features by optimizing video descriptions, tags, and titles with relevant keywords. Engage with your audience through comments and encourage them to subscribe for updates. Collaborating with other YouTubers or influencers in the tech space can also help grow your channel. +2. _TikTok_. TikTok is ideal for short, engaging videos. Use it to share quick tips, demo snippets, or behind-the-scenes content about your Actors. The platform’s algorithm favors high engagement, so create catchy content that encourages viewers to interact. Use trending hashtags and participate in challenges relevant to your niche to increase visibility. Consistency is key, so post regularly and monitor which types of content resonate most with your audience. + +## Growing your channels + +1. _Regular content_. Consistently upload content to keep your audience engaged and attract new viewers. Create a content calendar to plan and maintain a regular posting schedule. +2. _Cross-promotion_. Share your videos across your social media channels, blogs, and newsletters. This cross-promotion helps drive traffic to your videos and increases your reach. +3. _Engage with your audience_. Respond to comments and feedback on your videos. Engaging with viewers builds a community around your content and encourages ongoing interaction. +4. _Analyze performance_. Use analytics tools provided by YouTube and TikTok to track the performance of your videos. Monitor metrics like watch time, engagement rates, and viewer demographics to refine your content strategy. + +--- + +## Where to mention videos across your Actor ecosystem + +1. _README_: include links to your videos in your Actor’s README file. For example, if you have a tutorial video, mention it in a "How to scrape X" or "Resources" section to guide users. +2. _Input schema_: if your Actor’s input schema includes complex fields, link to a video that explains how to configure these fields. This can be especially helpful for users who prefer visual guides. +3. _Social media_: share your videos on platforms like Twitter, LinkedIn, and Facebook. Use engaging snippets or highlights to attract users to watch the full video. +4. _Blog posts_: embed videos in your blog posts for a richer user experience. If you write a tutorial or feature update, include a video to provide additional context. +5. _Webinars and live streams_: mention your videos during webinars or live streams. If you’re covering a topic related to a video you’ve posted, refer to it as a supplemental resource. diff --git a/sources/academy/platform/get_most_of_actors/promote_your_actor/webinars.md b/sources/academy/platform/get_most_of_actors/promote_your_actor/webinars.md new file mode 100644 index 0000000000..d020d6d042 --- /dev/null +++ b/sources/academy/platform/get_most_of_actors/promote_your_actor/webinars.md @@ -0,0 +1,113 @@ +--- +title: Webinars +description: Webinars and live streams are powerful tools to showcase your Actor’s features. Learn how to plan, host, and maximize the impact of your webinar. +sidebar_position: 7 +category: apify platform +slug: /actor-marketing-playbook/promote-your-actor/webinars +--- + +Webinars and live streams are a fantastic way to connect with your audience, showcase your Actor's capabilities, and gather feedback from users. Though the term webinar might sound outdated these days, the concept of a live video tutorial is alive and well in the world of marketing and promotion. + +Whether you're introducing a new feature, answering questions, or walking through a common use case, a live event can create more personal engagement, boost user trust, and open the door for valuable two-way communication. + +But how do you get started? Here's a friendly guide on where to host, how to prepare, and what to do before, during, and after your webinar. + +--- + +## Why host a live stream? + +Here are a few reasons why live streams are ideal for promoting your Actor: + +- _Demo_. You can show your Actor in action and highlight its most powerful features. You can tell a story about how you built it. You can also show how your Actor interacts with other tools and platforms and what its best uses are. A live demo lets users see immediately how your tool solves their problems. +- _Building trust and rapport_. Interacting directly with your users builds trust and rapport. Even showing up and showing your face/voice, it's a chance to let your users meet you and get a feel for the team behind the Actor. +- _Live Q&A_. Users often have questions that can be hard to fully address in documentation, README, or tutorials. A live session allows for Q&A, so you can explain complex features and demonstrate how to overcome common issues. +- _Tutorial or training_. If you don't have time for complex graphics, this is an easy replacement for a video tutorial until you do. Remember that some platforms (YouTube) give the option of publishing the webinar after it's over. You can reuse it later in other content as well as a guide. Also, if you’ve noticed users struggling with particular features, a webinar is a great way to teach them directly. + +Webinars help build a community around your Actor and turn one-time users into loyal advocates. + +## Where to host your webinar or live stream + +It all goes back to where you have or would like to have your audience and whether you want to have the webinar available on the web later. + +1. Social media: + 1. _YouTube_: ideal for reaching a broad audience. It’s free and easy to set up. You can also make recordings available for future viewing. + 2. _TikTok_: same, ideal for reaching a broad audience, free and easy to set up. However, live video will disappear once the broadcast has ended. TikTok does allow you to save your livestreams. You won't be able to republish them to the platform (we assume your live stream will be longer than 10 minutes). But you can later re-upload it elsewhere. + 3. _Twitch_: Known for gaming, Twitch has become a space for tech demos, coding live streams, and webinars. If your target audience enjoys an interactive and casual format, Twitch might be a good fit. + 4. _LinkedIn_: If your audience is more professional, LinkedIn Live could be a good fit to present your Actor there. Once a stream is complete, it will remain on the feed of your LinkedIn Page or profile as a video that was ‘previously recorded live’. + 5. Facebook: Not recommended. +2. General platforms: + 1. _Zoom_ or _Google Meet_: More personal, these are great for smaller webinars where you might want closer interaction. They also give you control over who attends. + +Pick a platform where your users are most likely to hang out. If your audience is primarily tech-savvy, YouTube or Twitch could work. If your Actor serves businesses, LinkedIn might be the best spot. + +## Webinar/live stream prep + +### Promote your webinar and get your users + +Send an email blast if you have an email list of users or potential users, send a friendly invite. Include details about what you’ll cover and how they can benefit from attending. + +- Social media promotion on Twitter (X), LinkedIn, or other platforms. Highlight what people will learn and any special features you’ll be demonstrating. Do it a few times - 2 weeks before the webinar, 1 week before, a day before, and the day of. Don't forget to announce on Apify’s Discord. These are places where your potential audience is likely hanging out. Let them know you’re hosting an event and what they can expect. +- Use every piece of real estate on Apify Store and Actor pages. Add a banner or notification to your Actor’s page (top of the README): This can be a great way to notify people who are already looking at your Actor. A simple “join us for a live demo on DATE” message works well. Add something like that to your Store bio and its README. Mention it at the top description of your Actor's input schema. + +:::tip Use UTM tags + +When creating a link to share to the webinar, you can add different UTM tags for different places where you will insert the link. That way you can later learn which space brought the most webinar sign-ups. + +::: + +- Collaborate with other developers. If you can team up with someone in the Apify community, you’ll double your reach. Cross-promotion can bring in users from both sides. + +--- + +### Plan the content + +Think carefully about what you’ll cover. Focus on what’s most relevant for your audience: + +- _Decide on your content_. What will you cover? A demo? A deep dive into Actor configurations? Create a flow and timeline to keep yourself organized. +- Prepare visuals. Slides, product demos, and examples are helpful to explain complex ideas clearly. +- _Feature highlights_. Demonstrate the key features of your Actor. Walk users through common use cases and be ready to show live examples. +- _Input schema_. If your Actor has a complex input schema, spend time explaining how to use it effectively. Highlight tips that will save users time and frustration. You can incorporate your knowledge from the issues tab. +- _Q&A session_. Leave time for questions at the end. Make sure to keep this flexible, as it’s often where users will engage the most. + +Don't forget to add an intro with an agenda and an outro with your contact details. + +:::tip Consider timezones + +When thinking of when to run the webinar, focus on the timezone of the majority of your users. + +::: + +### Prepare technically + +Test your setup before going live. Here’s what to focus on: + +- _Stable internet connection_. This one’s obvious but essential. Test your stream quality ahead of time. +- _Test the Actor live_. If you're demoing your Actor, ensure it works smoothly. Avoid running scripts that take too long or have potential bugs during the live session. +- _Audio quality_. People are far more likely to tolerate a blurry video than bad audio. Use a good-quality microphone to ensure you’re heard clearly. +- Screen sharing. If you’re doing a live demo, make sure you know how to seamlessly switch between windows and share your screen effectively. +- _Backup plan_. Have a backup plan in case something goes wrong. This could be as simple as a recorded version of your presentation to share if things go south during the live session. +- _Make it interactive_. Consider using polls or a live Q&A session to keep the audience engaged. Maybe have a support person assisting with that side of things while you're speaking. + +## Best practices during the live stream + +When the time comes, here’s how to make the most of your webinar or live stream: + +- _Start with an introduction_. Begin with a brief introduction of yourself, the Actor you’re showcasing, and what attendees can expect to learn. This sets expectations and gives context. It's also best if you have a slide that shows the agenda. +- _Try to stay on time_. Stick to the agenda. Users appreciate when events run on schedule. +- _Show a live demo_. Walk through a live demo of your Actor. Show it solving a problem from start to finish. +- _Explain as you go_. Be mindful that some people might be unfamiliar with technical terms or processes. Try to explain things simply and offer helpful tips as you demonstrate but don't go off on a tangent. +- _Invite questions and engage your audience_. Encourage users to ask questions throughout the session. This creates a more conversational tone and helps you address their concerns in real time. You can also ask a simple question or poll to get the chat going. Try to direct the Q&A into one place so you don't have to switch tabs. Throughout the presentation, pause for questions and make sure you're addressing any confusion in real time. +- _Wrap up with a clear call to action_. Whether it’s to try your Actor, leave a review, or sign up for a future live, finish with a clear CTA. Let them know the next step to take. + +This works for when it's a simple tutorial walkthrough and if you have a code-along session, the practices work for it as well.s + +## After the live session + +Once your live session wraps up, there are still sides of it you can benefit from: + +- _Make it public and share the recording_. Not everyone who wanted to attend will have been able to make it. Send a recording to all attendees whose emails you have and make it publicly available on your channels (emails, README, social media, etc.). Upload the recorded session to YouTube and your Actor’s documentation. If it's on YouTube, you can also ask Apify's video team to add it to their Community playlist. Make it easy for people to revisit the content or share it with others. +- _Follow up with attendees, thank them, and ask for feedback_. Send a follow-up email thanking people for attending. Include a link to the recording, additional resources, and ways to get in touch if they have more questions. Share any special offers or discount codes if relevant. If you don’t have the attendees' emails, include a link in your newsletter and publish it on your channels. Ask for feedback on what they liked and what could be improved. This can guide your next webinar or help fine-tune your Actor. +- _Answer lingering questions_. If any questions didn’t get answered live, take the time to address them in the follow-up email. +- _Create a blog post or article_. Summarize the key points of your webinar in a written format. This can boost your SEO and help users find answers in the future. +- _Review your performance_. Analyze the data from your webinar, if available. How many people attended? Which platform brought the most sign-ups? How many questions did you receive? Were there any technical difficulties? This helps refine your approach for future events. +- _Share snippets from the webinar or interesting takeaways on social media_. Encourage people to watch the recording and let them know when you’ll be hosting another event. diff --git a/sources/academy/platform/get_most_of_actors/store_basics/_category_.yaml b/sources/academy/platform/get_most_of_actors/store_basics/_category_.yaml new file mode 100644 index 0000000000..82effc00e4 --- /dev/null +++ b/sources/academy/platform/get_most_of_actors/store_basics/_category_.yaml @@ -0,0 +1,2 @@ +label: Store basics +position: 1 diff --git a/sources/academy/platform/get_most_of_actors/store_basics/actor_success_stories.md b/sources/academy/platform/get_most_of_actors/store_basics/actor_success_stories.md new file mode 100644 index 0000000000..736d12de0a --- /dev/null +++ b/sources/academy/platform/get_most_of_actors/store_basics/actor_success_stories.md @@ -0,0 +1,22 @@ +--- +title: Actor success stories +description: Learn about developers who successfully make passive income from their Actors. +sidebar_position: 5 +category: apify platform +slug: /actor-marketing-playbook/store-basics/actor-success-stories +--- + +_Web scraping freelance financial freedom with microworlds._ + +Discover how Caleb David, founder of `microworlds`, achieved financial freedom through freelance web scraping. His journey showcases how mastering the craft with tools like Crawlee and creating a Twitter scraper transformed his career. See the full story [here](https://blog.apify.com/web-scraping-freelance-financial-freedom/) and learn from his success. + +https://apify.com/microworlds + +_Web scraping for freelance success – insights from Tugkan._ + +In this success story, our first community dev Tugkan shares how his journey into freelancing via Apify changed his life. Learn about his process, challenges, and how his paid Actors have brought him financial rewards and freedom. Check out his story [here](https://apify.com/success-stories/paid-actor-journey-apify-freelancer-tugkan) for inspiration. + +https://apify.com/epctex + + +Interested in sharing your story? Reach out to our marketing team at [marketing@apify.com](mailto:marketing@apify.com) for a case study to showcase your journey. diff --git a/sources/academy/platform/get_most_of_actors/store_basics/how_actor_monetization_works.md b/sources/academy/platform/get_most_of_actors/store_basics/how_actor_monetization_works.md new file mode 100644 index 0000000000..ed6de04e78 --- /dev/null +++ b/sources/academy/platform/get_most_of_actors/store_basics/how_actor_monetization_works.md @@ -0,0 +1,124 @@ +--- +title: How Actor monetization works +description: Discover how to share your tools and explore monetization options to earn from your automation expertise. +sidebar_position: 3 +category: apify platform +slug: /actor-marketing-playbook/store-basics/how-actor-monetization-works +--- + +**You can turn your web scrapers into a source of income by publishing them on Apify Store. Learn how it's done and what monetization options you have.** + +--- + +## Monetizing your Actor + +Monetizing your Actor on the Apify platform involves several key steps: + +1. _Development_: create and refine your Actor. +2. _Testing_: ensure your Actor works reliably. +3. _Publication & monetization_: publish your Actor and set up its monetization model. +4. _Promotion_: attract users to your Actor. + +--- + +## Monetization models + +### Rental pricing model + +![rental model example](images/rental-model.png) + +- _How it works_: you offer a free trial period and set a monthly fee. Users on Apify paid plans can continue using the Actor after the trial. You earn 80% of the monthly rental fees. +- _Example_: you set a 7-day free trial and $30/month rental. If 3 users start using your Actor: + - 1st user on a paid plan pays $30 after the trial (you earn $24). + - 2nd user starts their trial but pays next month. + - 3rd user on a free plan finishes the trial without upgrading to a paid plan and can’t use the Actor further. + +### Pay-per-result pricing model + +![pay per result model example](images/ppr-model.png) + +- _How it works_: you charge users based on the number of results your Actor generates. You earn 80% of the revenue minus platform costs. +- _Cost breakdown_: + - Compute unit: $0.4 per CU + - Residential proxies: $13 per GB + - SERPs proxy: $3 per 1,000 SERPs + - Data transfer (external): $0.20 per GB + - Dataset storage: $1 per 1,000 GB-hours +- _Example_: you set a $1 per 1,000 results price. Two users generate 50,000 and 20,000 results, paying $50 and $20, respectively. If platform costs are $5 and $2, your profit is $49. + +## Setting up monetization + +1. _Go to your Actor page_: navigate to the **Publication** tab and open the **Monetization** section. +2. _Fill in billing details_: set up your payment details for payouts. +3. _Choose your pricing model_: use the monetization wizard to select your model and set fees. + +### Changing monetization + +Adjustments to monetization settings take 14 days to take effect and can be made once per month. + +### Tracking and promotion + +- _Track profit_: review payout invoices and statistics in Apify Console (**Monitoring** tab). +- _Promote your Actor_: optimize your Actor’s description for SEO, share on social media, and consider creating tutorials or articles to attract users. + +## Marketing tips for defining the price for your Actor + +It's up to you to set the pricing, of course. It can be as high or low as you wish, you can even make your Actor free. But if you're generally aiming for a successful, popular Actor, here are a few directions: + +### Do market research outside Apify Store + +The easiest way to understand your tool's value is to look around. Are there similar tools on the market? What do they offer, and how much do they charge? What added value does your tool provide compared to theirs? What features can your tool borrow from theirs for the future? + +Try competitor tools yourself (to assess the value and the quality they provide), check their SEO (to see how much traffic they get), and note ballpark figures. Think about what your Actor can do that competitors might be missing. + +Also, remember that your Actor is a package deal with the Apify platform. So all the platform's features automatically transfer onto your Actor and its value. Scheduling, monitoring runs, ways of exporting data, proxies, and integrations can all add value to your Actor (on top of its own functionalities). Be sure to factor this into your tool's value proposition and communicate that to the potential user. + +### Do research in Apify Store + +Apify Store is like any other marketplace, so take a look at your competition there. Are you the first in your lane, or are there other similar tools? What makes yours stand out? Remember, your README is your first impression — communicate your tool's benefits clearly and offer something unique. Competing with other developers is great, but collaborations can drive even better results 😉 + +Learn more about what makes a good readme here: [How to create an Actor README](/academy/actor-marketing-playbook/actor-basics/how-to-create-an-actor-readme) + +### Rental, pay-per-result (PPR), or pay-per-event (PPE) + +Rental pricing is technically easier: you set the rental fee, and the user covers their CU usage. So all you have to define is how much you want to charge the users. With pay-per-result, you’ll need to include both CU usage and your margin. So you have to calculate how much the average run is going to cost for the user + define how much you want to charge them. + +To figure out the average cost per run for users, just run a few test runs and look at the statistics in the Actor [**Analytics**](https://console.apify.com/actors?tab=analytics) tab. + +From an average user's perspective, pay-per-result is often easier to grasp — $25 for a thousand pages, $5 for a thousand videos, $1 for a thousand images, etc. It gives users a clearer idea of what they’re paying for and allows them to estimate faster. But rental pricing has its fans, too — if your tool provides high value, users will come. + +Pay-per-event (PPE) lets you define pricing for individual events. You can charge for specific events directly from your Actor by calling our PPE charging API. The most common events will most likely be Actor start, dataset item, external API calls, etc. PPE is great for users who want to optimize their costs and value transparency. PPE is also a fairer pricing model for integration and AI-driven use cases, where dataset-based pricing doesn’t make sense. + +### Adapt when needed + +Don’t be afraid to experiment with pricing, especially at the start. You can monitor your results in the dashboard and adjust if necessary. + +Keep an eye on SEO as well. If you monitor the volume of the keywords your Actor is targeting as well as how well your Actor's page is ranking for those keywords, you can estimate the number of people who actually end up trying your tool (aka conversion rate). If your keywords are getting volume, but conversions are lower than expected, it might point to a few issues It could be due to your pricing, a verbose README, or complex input. If users are bouncing right away, it makes sense to check out your pricing and your closest competitors to see where adjustments might help. + +### Summary & a basic plan + +Pick a pricing model, run some tests, and calculate your preliminary costs (**Analytics** tab in Console). + +Then check your costs against similar solutions in the Store and the market (try Google search or other marketplaces), and set a price that gives you some margin. + +It’s also normal to adjust pricing as you get more demand. For context, most prices on Apify Store range between $1-10 per 1,000 results. + +Example of useful pricing estimates from the **Analytics** tab: + +![example of pricing estimates in analytics tab](images/analytisc-example.png) + +:::tip Use emails! + +📫 Don't forget to set an email sequence to warn and remind your users about pricing changes. Learn more about emailing your users here: [Emails to Actor users] + +::: + +## Resources + +- Learn about [incentives behind monetization](https://apify.com/partners/actor-developers) +- Detailed guide to [setting up monetization models](https://docs.apify.com/academy/actor-marketing-playbook/monetizing-your-actor) +- Guide to [publishing Actors](https://docs.apify.com/platform/actors/publishing) +- Watch our webinar on how to [build, publish and monetize Actors](https://www.youtube.com/watch?v=4nxStxC1BJM) +- Read a blog post from our CEO on the [reasoning behind monetizing Actors](https://blog.apify.com/make-regular-passive-income-developing-web-automation-actors-b0392278d085/) +- Learn about the [Creator plan](https://apify.com/pricing/creator-plan), which allows you to create and freely test your own Actors for $1 + diff --git a/sources/academy/platform/get_most_of_actors/store_basics/how_store_works.md b/sources/academy/platform/get_most_of_actors/store_basics/how_store_works.md new file mode 100644 index 0000000000..4245d01751 --- /dev/null +++ b/sources/academy/platform/get_most_of_actors/store_basics/how_store_works.md @@ -0,0 +1,115 @@ +--- +title: How Apify Store works +description: Learn how to create and publish your own Actor, and join a growing community of innovators in scraping and web automation. +sidebar_position: 1 +category: apify platform +slug: /actor-marketing-playbook/store-basics/how-store-works +--- + +**Out of the 3,000+ Actors on [Apify Store](https://apify.com/store) marketplace, hundreds of them were created by developers just like you. Let's get acquainted with the concept of Apify Store and what it takes to publish an Actor there.** + +--- + +## What are Actors (and why they're called that)? + +[Actors](https://apify.com/actors) are serverless cloud applications that run on the Apify platform, capable of performing various computing tasks on the web, such as crawling websites or sending automated emails. They are developed by independent developers all over the world, and _you can be one of them_. + +The term "Actor" is used because, like human actors, these programs follow a script. This naming convention unifies both web scraping and web automation solutions, including AI agents, under a single term. Actors can range in complexity and function, targeting different websites or performing multiple tasks, which makes the umbrella term very useful. + +## What is Apify Store? + +[Apify Store](https://apify.com/store) is a public library of Actors that is constantly growing and evolving. It's basically a publicly visible (and searchable) part of the Apify platform. With over 3,000 Actors currently available, most of them are created and maintained by the community. Actors that consistently perform well remain on Apify Store, while those reported as malfunctioning or under maintenance are eventually removed. This keeps the tools in our ecosystem reliable, effective, and competitive. + +### Types of Actors + +- _Web scraping Actors_: for instance, [Twitter (X) Scraper](https://apify.com/apidojo/twitter-user-scraper) extracts data from Twitter. +- _Automation Actors_: for example, [Content Checker](https://apify.com/jakubbalada/content-checker) monitors website content for changes and emails you once a change occurs. +- _Bundles_: chains of multiple Actors united by a common data point or target website. For example, [Restaurant Review Aggregator](https://apify.com/tri_angle/restaurant-review-aggregator) can scrape reviews from six platforms at once. + +Learn more about bundles here: [Actor bundles](/academy/actor-marketing-playbook/product-optimization/actor-bundles) + +## Public and private Actors + +Actors on Apify Store can be public or private: + +- _Private Actors_: these are only accessible to you in Apify Console. You can use them without exposing them to the web. However, you can still share the results they produce. +- _Public Actors_: these are available to everyone on Apify Store. You can choose to make them free or set a price. By publishing your web scrapers and automation solutions, you can attract users and generate income. + +## How Actor monetization works (briefly) + +You can monetize your Actors using three different pricing models: + +- Pay for usage: charge based on how much the Actor is used. +- Pay per result: the price is based on the number of results produced, with the first few free. +- Pay per event: the price is based on specific events triggered by the Actor. +- Monthly billing: set a fixed monthly rental rate for using the Actor. + +For detailed information on which pricing model might work for your Actor, refer to [How Actor monetization works](/academy/actor-marketing-playbook/store-basics/how-actor-monetization-works). + +## Actor ownership on Store + +Actors are either created and maintained by Apify or by members of the community: + +- _Maintained by Apify_: created and supported by the Apify team. +- _Maintained by Community_: created and managed by independent developers from the community. + +To see who maintains an Actor, check the upper-right corner of the Actor's page. + +When it comes to managing Actors on Apify, it’s important that every potential community developer understands the differences between Apify-maintained and Community-maintained Actors. Here’s what you need to know to navigate the platform effectively and ensure your work stands out. + +### Community-maintained Actors + +✨ _Features and functionality_: offers a broader range of use cases and features, often tailored to specific needs. Great for exploring unique or niche applications. + +🧑‍💻 _Ownership_: created and maintained by independent developers like you. + +🛠 _Maintenance_: you’re responsible for all updates, bug fixes, and ongoing maintenance. Apify hosts your Actor but does not manage its code. + +👷‍♀️ _Reliability and testing_: it’s up to you to ensure your Actor’s reliability and performance. + +☝️ _Support and Issues_: Apify does not provide direct support for Community-maintained Actors. You must manage issues through the Issues tab, where you handle user queries and problems yourself. + +✍️ _Documentation_: you’re responsible for creating and maintaining documentation for your Actor. Make sure it’s clear and helpful for users. + +:::tip Test your Actor! + +For the best results, make sure your Actor is well-documented and thoroughly tested. Engage with users through the Issues tab to address any problems promptly. By maintaining high standards and being proactive, you’ll enhance your Actor’s reputation and usability in Apify Store. + +::: + +## Importance of Actor testing and reliability + +It's essential to test your Actors and make sure they work as intended. That's why Apify does it on our side as much as you should do it on yours. + +Apify runs automated tests daily to ensure all Actors on Apify Store are functional and reliable. These tests check _if an Actor can successfully run with its default input within 5 minutes_. If an Actor fails for three consecutive days, it’s labeled under maintenance, and the developer is notified. Continuous failures for another 28 days lead to deprecation. + +To restore an Actor's health, developers should fix and rebuild it. The testing system will automatically recognize the changes within 24 hours. If your Actor requires longer run times or authentication, contact support to explain why it should be excluded from tests. For more control, you can implement your own tests using the Actor Testing tool available on Apify Store. + +### Actor metrics and reliability score + +On the right panel of each Actor on Store, you can see a list of Actor metrics. + +Actor metrics such as the number of monthly users, star ratings, success rates, response times, creation dates, and recent modifications collectively offer insights into its reliability. Basically, they serve as a _shorthand for potential users to assess your Actor's reliability_ before even trying it out. + +A high number of monthly users indicates widespread trust and effective performance, while a high star rating reflects user satisfaction. A success rate nearing 100% demonstrates consistent performance. Short response times show a commitment to addressing issues promptly, though quicker responses are ideal. A recent creation date suggests modern features and ongoing development, while recent modifications point to active maintenance and continuous improvements. Together, these metrics provide a comprehensive view of an Actor’s reliability and quality. + +### Reporting Issues in Actors + +Each Actor has an **Issues** tab in Apify Console and on the web. Here, users can open an issue (ticket) and engage in discussions with the Actor's creator, platform admins, and other users. The tab is ideal for asking questions, requesting new features, or providing feedback. + +Since the **Issues** tab is public, the level of activity — or lack thereof — can be observed by potential users and may serve as an indicator of the Actor's reliability. A well-maintained Issues tab with prompt responses suggests an active and dependable Actor. + +Learn more about how to handle the [Issues tab] + + +### Getting featured in Apify Store + +Actors that perform reliably and efficiently may be featured in the [Apify picks](https://apify.com/store/collections/apify_picks) section or the **Featured developers** section of Apify Store. The purpose of this is to highlight them for users seeking top-quality tools. + +## Resources + +- Best practices on setting up [testing for your Actor](https://docs.apify.com/platform/actors/publishing/test) +- What are Apify-maintained and [Community-maintained Actors](https://help.apify.com/en/articles/6999799-what-are-apify-maintained-and-community-maintained-actors)? On ownership, maintenance, features, and support +- Step-by-step guide on how to [publish your Actor](https://docs.apify.com/platform/actors/publishing) +- Watch our webinar on how to [build, publish and monetize Actors](https://www.youtube.com/watch?v=4nxStxC1BJM) +- Detailed [guide on pricing models](https://docs.apify.com/platform/actors/running/actors-in-store) for Actors in Store diff --git a/sources/academy/platform/get_most_of_actors/store_basics/how_to_build_actors.md b/sources/academy/platform/get_most_of_actors/store_basics/how_to_build_actors.md new file mode 100644 index 0000000000..0bc4fd333d --- /dev/null +++ b/sources/academy/platform/get_most_of_actors/store_basics/how_to_build_actors.md @@ -0,0 +1,171 @@ +--- +title: How to build Actors +description: Learn how to create web scrapers and automation tools on Apify. Use universal scrapers for quick setup, code templates for a head start, or SDKs and libraries for full control. +sidebar_position: 2 +category: apify platform +slug: /actor-marketing-playbook/store-basics/how-to-build-actors +--- + +At Apify, we try to make building web scraping and automation straightforward. You can customize our universal scrapers with JavaScript for quick tweaks, use our code templates for rapid setup in JavaScript, TypeScript, or Python, or build from scratch using our JavaScript and Python SDKs or Crawlee libraries for Node.js and Python for ultimate flexibility and control. This guide offers a quick overview of our tools to help you find the right fit for your needs. + +## Three ways to build Actors + +1. [Our universal scrapers](https://apify.com/store/scrapers/universal-web-scrapers) — customize our boilerplate tools to your needs with a bit of JavaScript and setup. +2. [Our code templates](https://apify.com/templates) for web scraping projects — for a quick project setup to save you development time (includes JavaScript, TypeScript, and Python templates). +3. Open-source libraries and SDKs + 1. [JavaScript SDK](https://docs.apify.com/sdk/js/) & [Python SDK](https://docs.apify.com/sdk/python/) — for creating your own solution from scratch on the Apify platform using our free development kits. Involves more coding but offers infinite flexibility. + 2. [Crawlee](https://crawlee.dev/) and [Crawlee for Python](https://crawlee.dev/python) — for creating your own solutions from scratch using our free web automation libraries. Involves even more coding but offers infinite flexibility. There’s also no need to host these on the platform. + +## Universal scrapers & what are they for + +[Universal scrapers](https://apify.com/scrapers/universal-web-scrapers) were built to provide an intuitive UI plus configuration that will help you start extracting data as quickly as possible. Usually, you just provide a [simple JavaScript function](https://docs.apify.com/tutorials/apify-scrapers/getting-started#the-page-function) and set up one or two parameters, and you're good to go. + +Since scraping and automation come in various forms, we decided to build not just one, but _six_ scrapers. This way, you can always pick the right tool for the job. Let's take a look at each particular tool and its advantages and disadvantages. + +| Scraper | Technology | Advantages | Disadvantages | Best for | +| --- | --- | --- | --- | --- | +| 🌐 Web Scraper | Headless Chrome Browser | Simple, fully JavaScript-rendered pages | Executes only client-side JavaScript | Websites with heavy client-side JavaScript | +| 👐 Puppeteer Scraper | Headless Chrome Browser | Powerful Puppeteer functions, executes both server-side and client-side JavaScript | More complex | Advanced scraping with client/server-side JS | +| 🎭 Playwright Scraper | Cross-browser support with Playwright library | Cross-browser support, executes both server-side and client-side JavaScript | More complex | Cross-browser scraping with advanced features | +| 🍩 Cheerio Scraper | HTTP requests + Cheerio parser (JQuery-like for servers) | Simple, fast, cost-effective | Pages may not be fully rendered (lacks JavaScript rendering), executes only server-side JavaScript | High-speed, cost-effective scraping | +| ⚠️ JSDOM Scraper | JSDOM library (Browser-like DOM API) | + Handles client-side JavaScript
+ Faster than full-browser solutions
+ Ideal for light scripting | Not for heavy dynamic JavaScript, executes server-side code only, depends on pre-installed NPM modules | Speedy scraping with light client-side JS | +| 🍲 BeautifulSoup Scraper | Python-based, HTTP requests + BeautifulSoup parser | Python-based, supports recursive crawling and URL lists | No full-featured web browser, not suitable for dynamic JavaScript-rendered pages | Python users needing simple, recursive crawling | + +### How do I choose the right universal web scraper to start with? + +🎯 Decision points: + +- Use 🌐 [Web Scraper](https://apify.com/apify/web-scraper) if you need simplicity with full browser capabilities and client-side JavaScript rendering. +- Use 🍩 [Cheerio Scraper](https://apify.com/apify/cheerio-scraper) for fast, cost-effective scraping of static pages with simple server-side JavaScript execution. +- Use 🎭 [Playwright Scraper](https://apify.com/apify/playwright-scraper) when cross-browser compatibility is crucial. +- Use 👐 [Puppeteer Scraper](https://apify.com/apify/puppeteer-scraper) for advanced, powerful scraping where you need both client-side and server-side JavaScript handling. +- Use ⚠️ [JSDOM Scraper](https://apify.com/apify/jsdom-scraper) for lightweight, speedy scraping with minimal client-side JavaScript requirements. +- Use 🍲 [BeautifulSoup Scraper](https://apify.com/apify/beautifulsoup-scraper) for Python-based scraping, especially with recursive crawling and processing URL lists. + + +To make it easier, here's a short questionnaire that guides you on selecting the best scraper based on your specific use case: + +
+ Questionnaire + 1. Is the website content rendered with a lot of client-side JavaScript? + - Yes: + - Do you need full browser capabilities? + - Yes: use Web Scraper or Playwright Scraper + - No, but I still want advanced features: use Puppeteer Scraper + - No: + - Do you prioritize speed and cost-effectiveness? + - Yes: use Cheerio Scraper + - No: use JSDOM Scraper + 2. Do you need cross-browser support for scraping? + - Yes:** use Playwright Scraper + - No:** continue to the next step. + 3. Is your preferred scripting language Python?** + - Yes:** use BeautifulSoup Scraper + - No:** continue to the next step. + 4. Are you dealing with static pages or lightweight client-side JavaScript?** + - Static pages: use Cheerio Scraper or BeautifulSoup Scraper + - Light client-side JavaScript: + - Do you want a balance between speed and client-side JavaScript handling? + - Yes: use JSDOM Scraper + - No: use Web Scraper or Puppeteer Scraper + 5. Do you need to support recursive crawling or process lists of URLs? + - Yes, and I prefer Python: use BeautifulSoup Scraper + - Yes, and I prefer JavaScript: use Web Scraper or Cheerio Scraper + - No: choose based on other criteria above. + +This should help you navigate through the options and choose the right scraper based on the website’s complexity, your scripting language preference, and your need for speed or advanced features. + +
+ + +📚 Resources: + +- How to use [Web Scraper](https://www.youtube.com/watch?v=5kcaHAuGxmY) to scrape any website +- How to use [Beautiful Soup](https://www.youtube.com/watch?v=1KqLLuIW6MA) to scrape the web +- Learn about our $1/month [Creator plan](https://apify.com/pricing/creator-plan) that encourages devs to build Actors based on universal scrapers + +## Web scraping code templates + +Similar to our universal scrapers, our [code templates](https://apify.com/templates) also provide a quick start for developing web scrapers, automation scripts, and testing tools. Built on popular libraries like BeautifulSoup for Python or Playwright for JavaScript, they save time on setup, allowing you to focus on customization. Though they require more coding than universal scrapers, they're ideal for those who want a flexible foundation while still needing room to tailor their solutions. + +| Code template | Supported libraries | Purpose | Pros | Cons | +| --- | --- | --- | --- | --- | +| 🐍 Python | Requests, BeautifulSoup, Scrapy, Selenium, Playwright | Creating scrapers Automation Testing tools | - Simplifies setup - Supports major Python libraries | - Requires more manual coding (than universal scrapers)- May be restrictive for complex tasks | +| ☕️ JavaScript | Playwright, Selenium, Cheerio, Cypress, LangChain | Creating scrapers Automation Testing tools | - Eases development with pre-set configurations - Flexibility with JavaScript and TypeScript | - Requires more manual coding (than universal scrapers)- May be restrictive for tasks needing full control | + + +📚 Resources: + +- [How to build a scraper](https://www.youtube.com/watch?v=u-i-Korzf8w) using a web scraper template. + +## Toolkits and libraries + +### Apify JavaScript and Python SDKs + +[Apify SDKs](https://docs.apify.com/sdk/js/) are designed for developers who want to interact directly with the Apify platform. It allows you to perform tasks like saving data in Apify Datasets, running Apify Actors, and accessing the key-value store. Ideal for those who are familiar with [Node.js](https://docs.apify.com/sdk/js/) and [Python](https://docs.apify.com/sdk/python/), SDKs provide the tools needed to develop software specifically on the Apify platform, offering complete freedom and flexibility within the JavaScript ecosystem. + +- _Best for_: interacting with the Apify platform (e.g., saving data, running Actors, etc) +- _Pros_: full control over platform-specific operations, integrates seamlessly with Apify services +- _Cons_: requires writing boilerplate code, higher complexity with more room for errors + +### Crawlee + +[Crawlee](https://crawlee.dev/) (for both Node.js and [Python](https://crawlee.dev/python)) is a powerful web scraping library that focuses on tasks like extracting data from web pages, automating browser interactions, and managing complex scraping workflows. Unlike the Apify SDK, Crawlee does not require the Apify platform and can be used independently for web scraping tasks. It handles complex operations like concurrency management, auto-scaling, and request queuing, allowing you to concentrate on the actual scraping tasks. + +- _Best for_: web scraping and automation (e.g., scraping paragraphs, automating clicks) +- _Pros_: full flexibility in web scraping tasks, does not require the Apify platform, leverages the JavaScript ecosystem +- _Cons_: requires more setup and coding, higher chance of mistakes with complex operations + +### Combining Apify SDK and Crawlee + +While these tools are distinct, they can be combined. For example, you can use Crawlee to scrape data from a page and then use the Apify SDK to save that data in an Apify dataset. This integration allows developers to make use of the strengths of both tools while working within the Apify ecosystem. + +📚 Resources: + +- Introduction to [Crawlee](https://www.youtube.com/watch?v=g1Ll9OlFwEQ) +- Crawlee [blog](https://crawlee.dev/blog) +- Webinar on scraping with [Crawlee 101](https://www.youtube.com/watch?v=iAk1mb3v5iI): how to create scrapers in JavaScript and TypeScript +- Step-by-step video guide: [building an Amazon Scraper](https://www.youtube.com/watch?v=yTRHomGg9uQ) in Node.js with Crawlee +- Webinar on how to use [Crawlee Python](https://www.youtube.com/watch?v=ip8Ii0eLfRY) +- Introduction to Apify's [Python SDK](https://www.youtube.com/watch?v=C8DmvJQS3jk) + + +## Code templates vs. universal scrapers vs. libraries + +Basically, the choice here depends on how much flexibility you need and how much coding you're willing to do. More flexibility → more coding. + +[Universal scrapers](https://apify.com/scrapers/universal-web-scrapers) are simple to set up but are less flexible and configurable. Our [libraries](https://crawlee.dev/), on the other hand, enable the development of a standard [Node.js](https://nodejs.org/) or Python application, so be prepared to write a little more code. The reward for that is almost infinite flexibility. + +[Code templates](https://apify.com/templates) are sort of a middle ground between scrapers and libraries. But since they are built on libraries, they are still on the rather more coding than less coding side. They will only give you a starter code to begin with. So please take this into account when choosing the way to build your scraper, and if in doubt — just ask us, and we'll help you out. + +## Switching sides: how to transfer an existing solution from another platform + +You can also take advantage of the Apify platform's features without having to modify your existing scraping or automation solutions. + +### Integrating Scrapy spiders + +The Apify platform fully supports Scrapy spiders. By [deploying your existing Scrapy code to Apify](https://apify.com/run-scrapy-in-cloud), you can take advantage of features like scheduling, monitoring, scaling, and API access, all without needing to modify your original spider. This process is made easy with the [Apify CLI](https://docs.apify.com/cli/), which allows you to convert your Scrapy spider into an Apify Actor with just a few commands. Once deployed, your spider can run in the cloud, offering a reliable and scalable solution for your web scraping needs. + +Additionally, you can monetize your spiders by [publishing them as Actors](https://apify.com/partners/actor-developers) on Apify Store, potentially earning passive income from your work while benefiting from the platform’s extensive features. + +### ScrapingBee, ScrapingAnt, ScraperAPI + +To make the transition from these platforms easier, we've also created [SuperScraper API](https://apify.com/apify/super-scraper-api). This API is an open-source REST API designed for scraping websites by simply passing a URL and receiving the rendered HTML content in return. This service functions as a cost-effective alternative to other scraping services like ScrapingBee, ScrapingAnt, and ScraperAPI. It supports dynamic content rendering with a headless browser, can use various proxies to avoid blocking, and offers features such as capturing screenshots of web pages. It is ideal for large-scale scraping tasks due to its scalable nature. + +To use SuperScraper API, you can deploy it with an Apify API token and access it via HTTP requests. The API supports multiple parameters for fine-tuning your scraping tasks, including options for rendering JavaScript, waiting for specific elements, and handling cookies and proxies. It also allows for custom data extraction rules and JavaScript execution on the scraped pages. Pricing is based on actual usage, which can be cheaper or more expensive than competitors, depending on the configuration. + +📚 Resources: + +- [How to integrate Scrapy projects](https://docs.apify.com/cli/docs/integrating-scrapy) +- Scrapy monitoring: how to [manage your Scrapy spider on Apify](https://blog.apify.com/scrapy-monitoring-spidermon/) +- Run ScrapingBee, ScraperAPI, and ScrapingAnt on Apify — [SuperScraper API Tutorial](https://www.youtube.com/watch?v=YKs-I-2K1Rg) + +## General resources + +- Creating your Actor: [Actor sources](https://docs.apify.com/academy/getting-started/creating-actors) +- Use it, build it or buy it? [Choosing the right solution on Apify](https://help.apify.com/en/articles/3024655-choosing-the-right-solution) +- How to programmatically retrieve data with the [Apify API](https://www.youtube.com/watch?v=ViYYDHSBAKM&t=0s) +- Improved way to [build your scrapers from a Git repo](https://www.youtube.com/watch?v=8QJetr-BYdQ) +- Webinar on [how to build and monetize Actors](https://www.youtube.com/watch?v=4nxStxC1BJM) on Apify Store +- 6 things you should know before buying or [building a web scraper](https://blog.apify.com/6-things-to-know-about-web-scraping/) +- For a comprehensive guide on creating your first Actor, visit the [Apify Academy](https://apify.com/academy). diff --git a/sources/academy/platform/get_most_of_actors/store_basics/ideas_page_and_its_use.md b/sources/academy/platform/get_most_of_actors/store_basics/ideas_page_and_its_use.md new file mode 100644 index 0000000000..81e5df5416 --- /dev/null +++ b/sources/academy/platform/get_most_of_actors/store_basics/ideas_page_and_its_use.md @@ -0,0 +1,63 @@ +--- +title: Ideas page and its use +description: Learn where you can draw inspiration for your Actors. +sidebar_position: 4 +category: apify platform +slug: /actor-marketing-playbook/store-basics/ideas-page +--- + +So you want to build an Actor and publish it on Apify Store. Where should you start? How can you make people want to use it? + +To generate new Actor ideas, you can draw from your experience. You can also use SEO tools to discover relevant search terms and explore sites related to web scraping, automation, or integrations. But for direct inspiration straight from Apify, check out our Actor [Ideas page](https://apify.com/ideas) to see what data extraction tools are trending in the Apify community. Let's see how you can both use and contribute to this valuable resource. + +--- + +## What's the Ideas page? + +The [Ideas page](https://apify.com/ideas) is where users can submit and explore potential projects for Actors, including scrapers, integrations, and automations. It serves as a collaborative space for proposing new tool ideas and finding inspiration for building and developing web scraping and automation solutions. + +## How you, as a developer, can use the Ideas page + +Got an innovative Actor idea or unsure what to build next? The Apify Ideas page is your go-to destination for submitting, developing, and claiming Actor concepts. If you're a developer ready to build an Actor using the Apify Ideas page, here’s how you can get involved: + +1. _Browse the Ideas page_
+ Check out the [Ideas page](https://apify.com/ideas) to find ideas that interest you. Look for ideas that align with your skills and the kind of Actor you want to build. +2. _Select an idea_
+ Once you’ve found a promising idea, review the details and requirements provided. If you see an idea you want to develop, make sure to check its current status. If it’s marked as **Open to develop**, you’re good to go. +3. _Develop your Actor_
+ Start building your Actor based on the idea. You don’t need to notify Apify about your development process. Focus on creating a functional and well-documented tool. +4. _Prepare for launch_
+ Once your Actor is ready, ensure it meets all quality standards and has a comprehensive README. This documentation should include installation instructions, usage details, and any other relevant information. +5. _Publish your Actor_
+ Deploy your Actor on Apify Store. Make sure it’s live and accessible for users. +6. _Claim your idea_
+ After your Actor is published, email [ideas@apify.com](mailto:ideas@apify.com) with the URL of your Actor and the original idea. This will allow us to tag the idea as Completed and link it to your new Actor, giving you credit and visibility. +7. _Monitor and optimize_
+ Make sure to monitor your Actor’s performance and user feedback. Use this information to make improvements and keep your Actor up to date. + +By following these steps, you’ll be able to contribute to the community while also gaining recognition for your work. + +## Criteria for claiming an idea + +To claim an idea, ensure that: + +1. Your Actor is functional. +2. Your README contains relevant information. +3. Your Actor closely aligns with the original idea. + +## Giving back to the Ideas page + +The Ideas page at Apify offers a variety of concepts for scrapers, integrations, and automations, and is a great place to find inspiration or solutions. It’s also a platform where you can contribute your own ideas to drive innovation and growth in our community. + +1. _Submit your Ideas_
+ Got a great Actor concept? Share it with us through the [Ideas form](https://apify.typeform.com/to/BNON8poB#source=ideas). Provide clear details about what your tool should do and how it should work. +2. _Engage with the community_
+ Upvote ideas you find intriguing. The more support an idea receives, the more likely it is to catch a developer’s eye and move forward. +3. _Don’t forget to claim your idea_
+ Once your Actor is up and running, claim your idea by emailing [ideas@apify.com](mailto:ideas@apify.com) with your Actor's URL and the original idea. We’ll mark your idea as **Completed** and link it to your Actor - a signal to the other developers that this tool already exists on Apify Store. + +## Multiple developers for one idea + +No problem! Apify Store can host multiple Actors with similar functions. However, we go by the “first come - first served” rule, so the first developer to claim an idea will receive the **Completed** tag and a link from the Ideas page. + +Remember that Apify Store is just like any other marketplace. We believe that competition helps developers thrive and improve upon their code, especially when there are similar scrapers on the horizon! You can still build the Actor, but try to be imaginative when it comes to its set of features. diff --git a/sources/academy/platform/get_most_of_actors/store_basics/images/analytisc-example.png b/sources/academy/platform/get_most_of_actors/store_basics/images/analytisc-example.png new file mode 100755 index 0000000000..107419fbba Binary files /dev/null and b/sources/academy/platform/get_most_of_actors/store_basics/images/analytisc-example.png differ diff --git a/sources/academy/platform/get_most_of_actors/store_basics/images/ppr-model.png b/sources/academy/platform/get_most_of_actors/store_basics/images/ppr-model.png new file mode 100755 index 0000000000..700b22e571 Binary files /dev/null and b/sources/academy/platform/get_most_of_actors/store_basics/images/ppr-model.png differ diff --git a/sources/academy/platform/get_most_of_actors/store_basics/images/rental-model.png b/sources/academy/platform/get_most_of_actors/store_basics/images/rental-model.png new file mode 100755 index 0000000000..ce9b77d9d9 Binary files /dev/null and b/sources/academy/platform/get_most_of_actors/store_basics/images/rental-model.png differ diff --git a/sources/platform/actors/running/store.md b/sources/platform/actors/running/store.md index f68304cce6..b3dbbd06fe 100644 --- a/sources/platform/actors/running/store.md +++ b/sources/platform/actors/running/store.md @@ -14,7 +14,7 @@ toc_max_heading_level: 4 :::info Publishing and monetizing Actors -Anyone is welcome to [publish Actors](/platform/actors/publishing) in the store, and you can even [monetize your Actors](/platform/actors/publishing/monetize). For more information about how to monetize your Actor, best practices, SEO, and promotion tips and tricks, head over to the [Getting the most of your public Actors in Apify Store](/academy/get-most-of-actors) section of the Apify Developers Academy. +Anyone is welcome to [publish Actors](/platform/actors/publishing) in the store, and you can even [monetize your Actors](/platform/actors/publishing/monetize). For more information about how to monetize your Actor, best practices, SEO, and promotion tips and tricks, head over to the [Getting the most of your public Actors in Apify Store](/academy/actor-marketing-playbook) section of the Apify Developers Academy. :::