> ## Documentation Index > Fetch the complete documentation index at: https://docs.zenrows.com/llms.txt > Use this file to discover all available pages before exploring further. # Content guidelines for Zenrows affiliates > A step-by-step guide for Zenrows affiliates: how to prepare, which topics to cover, how to shape a piece, where to publish it, and how to get it amplified. This is the working guide for the Zenrows Affiliates program. Follow it in order for each piece you produce. For which topics to cover, see [Topics that convert](/partners/affiliates/content-topics). This page covers everything else. New to the program? Do [Step 0](#step-0-prepare-once) once, then repeat Steps 1 to 5 for every piece. ## Step 0: Prepare once Spending a little time with Zenrows before your first piece makes everything after it easier to write, and it is the difference between content that reads like a press release and content that reads like experience. The Free plan gives you 5,000 credits per month, enough to explore every product. See [Pricing](/first-steps/pricing) for what a credit buys. Send [your first request](/fetch/first-request), or connect the [Zenrows MCP server](/mcp/overview) to your AI assistant, or run a command with the [CLI](/cli/introduction). Whichever surface your audience uses. Whatever made you think "oh, that's neat" will do the same for your audience. Those moments are your content, not the feature list. Keep [the docs](/first-steps/welcome), [the topic list](/partners/affiliates/content-topics), and the [Zenrows media kit](https://www.zenrows.com/media) open while you work. ## Step 1: Pick your topics and intent Match each piece to a real search intent and stay with it. A reader searching "how to give Claude web access" wants a setup walkthrough, not a product overview. * **Choose topics** from [Topics that convert](/partners/affiliates/content-topics). Every cluster there is backed by real search demand. * **Choose the funnel stage** and shape the piece around it. Awareness pieces teach, evaluation pieces solve a specific problem, decision pieces help someone choose. * **Play to your own audience.** A Python-heavy audience wants code. A founder or ops audience wants the outcome and the setup steps. The same topic works for both if you change the framing. **AI and integrations convert best right now.** Pieces about connecting Zenrows to the tools people already use, especially through the [Zenrows MCP server](/mcp/overview) and the [CLI](/cli/introduction), reach an audience actively looking for a solution and facing very little competing content. "How to give Claude web data access at scale with Zenrows MCP" is the shape to aim for. ## What to emphasize about Zenrows Whatever the topic, these are the things worth showing. They are where Zenrows is strongest, and they are what readers are actually evaluating. * **Fetch and Batch on protected sites, at scale.** [Fetch](/fetch/api-reference) handles the pages that block ordinary tools, and [Batch](/batch/introduction) runs the same job across large lists of URLs without you building the orchestration. The pairing is the real story: one request shape that works on a hard page, and a managed way to run it a hundred thousand times. * **High-volume recurring extraction.** Most readers do not need one page once, they need the same pages every day. Show a job that submits a URL list, retries transient failures on its own, and returns results you can collect on a schedule. * **Reliability where ordinary tools give up.** This is the clearest differentiator you can demonstrate. Show a request that fails without Zenrows and succeeds with it, and point to the public track record: 100% Fetch uptime over the last 90 days, across more than 10 billion requests a month. * **The CLI and MCP server as an agent toolkit.** The [CLI](/cli/introduction) and the [MCP server](/mcp/overview) turn Zenrows into something an AI agent installs and uses directly rather than something a developer wires up by hand. The [Agent Toolkit](/cli/agent-toolkit-overview) is the part built specifically for that. This is the most under-covered angle available to you right now. * **Security and compliance, for business readers.** Enterprise plans include SOC 2 and ISO 27001 compliance, an SLA on uptime and success rate, and SSO/SAML. Worth a line in any piece aimed at teams who need procurement approval. Link to [Pricing](/first-steps/pricing) rather than restating the terms. ## Step 2: Show Zenrows in action You do not need to build anything elaborate. A clear demonstration, even a short one, does more work than paragraphs of description. Pick whichever of these fits your format: | What to show | Why it lands | | ------------------------------------------------ | --------------------------------------------------------------------------------------- | | **A page that would not load, now loading** | The most immediate before and after you can show, in any format | | **An AI assistant answering from live web data** | Connect Zenrows MCP to Claude, Cursor, or another client and let it pull real pages | | **One call replacing a lot of setup** | Everything a developer would otherwise assemble themselves, handled in a single request | | **Structured data instead of raw HTML** | A clean, ready-to-use response | | **The same job running across many pages** | Shows the production use case rather than the toy example | If you are writing for a non-developer audience, the MCP and integration angles need no code at all. A short screen recording of an assistant fetching live data is often the strongest demonstration you can make. ## Step 3: Shape the piece These are examples of shapes that hold attention, not rules. Adapt or ignore them to suit your audience and your format. Around 1,800 to 3,000 words works well. 1. **Hook.** The problem and why it matters. 2. **What you will build.** Describe the result and show it. 3. **Prerequisites.** Tools, accounts, and a Zenrows API key. 4. **The basic setup.** The simplest thing that works. 5. **Handling the harder part.** Add capability step by step. 6. **Using the output.** Parsing, storing, or feeding it to an assistant. 7. **Conclusion.** Recap, link to the docs, link to your other pieces. Often shorter than a tutorial, and frequently higher converting. 1. **The outcome.** What the reader's tool can do once this is set up. 2. **Prerequisites.** The tool, a Zenrows account, an API key. 3. **Connect it.** The configuration, exactly as it should be pasted. 4. **Prove it works.** One real prompt, command, or run with its output. 5. **Where to take it next.** Two or three things the reader can now do. Around 7 to 12 minutes for a tutorial. 1. **Introduction** (30 to 45 sec). State the problem. 2. **Outcome preview** (30 to 45 sec). Show the finished result. Viewers who see the result first drop off far less. 3. **Setup** (1 to 2 min). Install, connect, get the API key. 4. **Build it on screen** (5 to 8 min). 5. **Pro tips** (30 to 60 sec). What you learned using it for real. 6. **Wrap-up** (30 to 45 sec). Recap and one clear next step. 15 to 60 seconds, shot in portrait. 1. **Hook in the first two seconds.** Lead with the result, not with your face. 2. **One idea only.** 3. **Captions always.** Most viewers watch on mute. 4. **One next step.** Point to the full piece, not to a signup page. The same cut works on YouTube Shorts, TikTok, and Instagram Reels. Post it to all three. 400 to 900 words. Newsletter audiences in this niche are small, technical, and unusually high intent. * A short case study. * A recurring "tool of the week" or "target of the week" breakdown. * A walkthrough of a setup you actually use. One tracked link per issue, clearly placed. ## Step 4: Publish it where it will be found Publish to your own site first so you own the traffic, then syndicate. | Channel | What works there | Notes | | ----------------------- | ------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Your own blog** | Any format | Your canonical home. Everything else should point back here. | | **dev.to** | Tutorials and integration guides, 1,500 to 2,000 words | Write like you are helping a colleague. Up to 4 tags. Set a canonical URL when cross-posting. | | **Hashnode** | Long technical guides | Enable the table of contents and use the TL;DR field. | | **Medium** | Pieces already published elsewhere | Strong distribution through publications like Better Programming and Towards Data Science. Member-only stories get lift inside Medium but are gated for Google, so set a canonical tag back to your original. | | **LinkedIn Articles** | Use-case and integration pieces | Lead with the business outcome. Publish as an Article for indexing, then share a teaser post that links to it. | | **X Articles** | Long-form posts for an audience you already have on X | Keeps readers on-platform, which X rewards in reach. Pair with a short thread pointing to it. | | **Substack or beehiiv** | Newsletter issues and essays | Both index in Google and build a list you own. | | **GitHub** | The demo repo or config behind your piece | A README with working code or an MCP config, and a link back. Frequently outranks the article itself. | | **YouTube** | Tutorials and short-form | Put the full written version in the description. | | **Product Hunt** | A tool or template you built on Zenrows | Launch Tuesday to Thursday morning with a demo video. | ## Step 5: Promote it | Surface | What works there | | --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **X (Twitter)** | Short technical tips, code snippets, before and after demos. Screen recordings outperform text. Tag [@ZenRowsHQ](https://x.com/ZenRowsHQ). | | **LinkedIn** | Frame web data as a business capability. Native video outperforms links. Best shape is a 3 to 5 paragraph narrative plus the link. Post Tuesday to Thursday, 8 to 10 AM. | | **Reddit** | r/webscraping, r/learnpython, r/webdev, r/datascience, r/ClaudeAI, r/mcp. "I built X to solve Y" posts with real detail. Read each subreddit's rules on self-promotion first. | | **Hacker News** | Original benchmarks, teardowns, and research. Submit weekday mornings, US Eastern. | | **Discord and Slack** | Contribute for a few days before you share anything. Answer the question fully, then offer your piece as a resource. | | **Stack Overflow** | Answer completely and technically under `[web-scraping]`, `[python-requests]`, `[beautifulsoup]`, `[selenium]`. Mention Zenrows where it genuinely solves the asker's problem. | | **Quora** | 100 to 300 word answers that address the question directly, linking to your piece rather than a product page. | Answer platforms and forums rank well in Google and are quoted heavily by AI assistants. A good Stack Overflow or Reddit answer keeps sending readers to your content years after you write it. ## Accuracy rules These apply to every piece, in every format. * **Describe capabilities as they are documented.** "Handles common anti-bot systems" is accurate and is what the docs support. * **Use the real names.** Parameters like `js_render`, `premium_proxy`, and `extract=auto` are exact strings. Products are Fetch (formerly, Universal Scraper API), Extract, Batch, and Browser Sessions (formerly, Scraping Browser). * **Check prices against the live page.** Plans and credit costs change. Link to [Pricing](/first-steps/pricing) rather than restating numbers that will go stale. * **Target public data.** Publicly accessible pages such as product listings, search results, and public profiles make the strongest pieces. * **Avoid personal data at scale.** Pieces that harvest names, emails, or phone numbers create GDPR and CCPA problems for your readers. * **Do not target the forbidden list.** See [Forbidden sites](/forbidden-sites) for sites Zenrows does not serve. ## Brand assets Download logos, symbols, app icons, screenshots, and approved descriptions from the [Zenrows media kit](https://www.zenrows.com/media). It is the single source of truth for Zenrows brand assets. The rules that matter most: * **The name is always "Zenrows"**, capital Z and the rest lowercase. Not a capital R mid-word, not all lowercase. * **Keep clear space** around the wordmark, at least the height of the "o". * **Pick the variant with the most contrast** against your background. The wordmark ships in white, dark, teal, and purple. * **Use the symbol** where the full wordmark will not fit. The glow variant needs a dark background. * **Do not** add effects, rotate, stretch, recolor, rebuild the wordmark in another typeface, or place it on a busy background. Brand colors: purple `#7C4FE8`, teal `#7ADAE6`, warm dark `#1D1612`, white `#FFFFFF`. ## Get your content amplified Zenrows regularly reshares affiliate content from its own channels. To be considered: 1. Tag [@ZenRowsHQ](https://x.com/ZenRowsHQ) on X or mention Zenrows on LinkedIn when you publish. 2. Send the link to [marketing@zenrows.com](mailto:marketing@zenrows.com). What gets reshared has a clear angle, working examples, and describes Zenrows accurately. ## Pre-publish checklist Run through this before anything goes live. * [ ] The topic comes from [Topics that convert](/partners/affiliates/content-topics) or matches a real search query you verified * [ ] The piece serves a clear funnel stage * [ ] The framing fits the audience you are publishing to * [ ] Any code or configuration in the piece works as written * [ ] Parameter and product names are spelled exactly as documented * [ ] Pricing links to the live page rather than restating figures * [ ] The piece demonstrates Zenrows rather than only describing it * [ ] Screenshots have descriptive alt text * [ ] The primary keyword appears in the title, the first H2, and the first 100 words * [ ] The target is public data * [ ] The target is not on the [forbidden sites](/forbidden-sites) list * [ ] No personal data collected at scale * [ ] "Zenrows" is spelled correctly everywhere * [ ] Logo assets came from the [media kit](https://www.zenrows.com/media) and are unmodified * [ ] Canonical URL is set if you are cross-posting * [ ] Internal links point to your other Zenrows pieces * [ ] The link is sent to [marketing@zenrows.com](mailto:marketing@zenrows.com)