Content guidelines for Zenrows affiliates

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. This page covers everything else.

​

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.

​

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. 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.

​

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 handles the pages that block ordinary tools, and Batch 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 and the MCP server turn Zenrows into something an AI agent installs and uses directly rather than something a developer wires up by hand. The Agent Toolkit 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 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:

​

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.

​

Step 4: Publish it where it will be found

Publish to your own site first so you own the traffic, then syndicate.

​

Step 5: Promote 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 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 for sites Zenrows does not serve.

​

Brand assets

Download logos, symbols, app icons, screenshots, and approved descriptions from the Zenrows media kit. 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 on X or mention Zenrows on LinkedIn when you publish.
2. Send the link to 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.