SEO Articles with Apify, MCP, and Website Context
Tech
SEO
Apify
MCP
AI agents

SEO Articles with Apify, MCP, and Website Context

A direct breakdown of the service: SEO drafts, scoring, rewrites, images, pricing, and how customers connect Apify MCP per client.

Uygar DuzgunUUygar Duzgun
Jul 4, 2026
9 min read

SEO articles with Apify do not get better because the prompt is longer. They get better when the system understands the company website, audience, offer, publishing destination, and which pages the article should support.

That is what I am building with Apify and MCP: a practical workflow for SEO drafts, article reviews, rewriting, and images. The service is made for teams that want to move faster from brief to publish-ready material without dropping human review.

I come from practical SEO work in e-commerce, where organic traffic is one of the most invested channels. Generic AI text is not enough there. The article has to fit the page, internal links, product range, search intent, and the brand's way of selling.

Affiliate disclosure: I link to Apify with my referral link. If you create an account through https://apify.com?fpr=v5tn4v, I may receive compensation from Apify.

SEO Articles with Apify: What We Offer

The service consists of three Apify Actors and a managed setup for companies that want help with the full workflow.

ServiceWhen to use itOutputLaunch price
------------
SEO Article Generator with Website ContextWhen you want to create a new article draftMarkdown article, title, excerpt, focus keyword, meta description, FAQ, sources, internal links, and optional image$7.99 per completed article draft
Article SEO Score and Fix PlanWhen you want to review an existing draft or live articleContent readiness score, top issues, fix plan, keyword gaps, metadata check, and rewrite brief$0.99 per completed article score
SEO Article Rewrite with Before/After ScoreWhen you want to improve an existing articleRewritten markdown, before/after score, improved headings, metadata, and remaining fixes$4.99 per completed rewrite
Managed setupWhen you want the system configured per client or teamConfiguration, test runs, prompt structure, client separation, and review workflowQuote per scope

Self-Service Through Apify Store

Self-service fits customers who already know how to run Actors and want a clear input field for topic, website, destination URL, and reference pages. The prices are launch prices for Apify Store. The current price should always be checked in the Apify listing once it is live.

Managed Setup for Companies

Recommended reading

Managed setup fits teams that want a ready workflow per client. I set up accounts, MCP configuration, input templates, test runs, and the review flow. It builds on the same way I run my own AI content pipeline, packaged for client work.

How Article Creation Works

Illustration: the flow from website context to SEO draft, image, and human review
Illustration: the flow from website context to SEO draft, image, and human review

A good article starts with context. The customer does not only provide a topic. The customer sends the website, publishing destination, and relevant pages the article should understand.

text
Customer website
-> destination URL
-> 2-5 reference pages
-> audience and offer
-> search intent
-> SEO brief
-> article draft
-> featured image
-> content readiness score
-> human review
-> publishing

The important part is that the AI does not write in a vacuum. It gets to see the company, the page goal, and which internal links are reasonable. The result is not a finished truth. It is stronger editorial material.

SEO Article Generator with Website Context

The generator creates a new article draft from a topic or a YouTube URL. It can use the customer's website, destination URL, and reference pages as context before writing.

This is the right choice when you want a first draft that already has SEO structure:

clear H1/H2 structure
focus keyword and supporting keywords
meta description
FAQ suggestions
sources and references when available
internal link suggestions
optional featured image

I do not use it as an automatic publishing machine. I use it to create a better first draft faster.

Article SEO Score and Fix Plan

The score service is for articles that already exist. You send a URL or paste markdown/text. The service returns a content readiness score and a concrete fix plan.

I do not call it a Google ranking score. That would be wrong. This is an editorial SEO assessment of how ready the article is based on structure, intent, metadata, internal links, and coverage.

That makes the score service useful for two things:

lead magnet: "Check your article's SEO score"
paid audit: "Here is what we should fix before publishing or rewriting"

SEO Article Rewrite with Before/After Score

The rewrite service takes an existing draft or live article and improves it using website context. It returns rewritten markdown and shows the before/after score.

It is useful when the customer already has content but the text is weak, thin, or angled the wrong way. You do not need to start over. You need to understand what is missing and rewrite with a better direction.

This works especially well for:

old blog posts that have lost relevance
category-supporting articles in e-commerce
SaaS articles that need clearer intent
local service pages with weak structure
consultant pages where internal links and the offer need to become clearer

Images, Charts, and Visual Blocks

An article can receive a generated featured image. For articles where the process needs explanation, we can also add visual blocks: process images, pricing comparisons, architecture sketches, and simple charts.

I keep text and numbers in the article tables, not inside the AI image itself. Image models can misspell words or invent text. That is why images work best as visual support, while prices, steps, and instructions live as real HTML/markdown.

Visual blockPurposeWhere it fits
---------
Hero imageGive the article a clear visual identityAt the top of the article and in blog cards
Process illustrationShow how creation worksAfter the introduction or in a "How it works" section
Pricing chart/tableMake packages easy to compareIn the pricing section
MCP architectureShow how each client is connected separatelyIn the onboarding section

How the Customer Connects Through Apify

Apify is the platform where Actors run, get logged, and get billed. Apify describes its platform as a marketplace for AI tools and web data, with Actors that can run through Console, API, and integrations.

Customers can start here:

Create an Apify account through my referral link

Once the account is ready, the customer can connect the MCP server:

https://mcp.apify.com/?tools=actors,docs,uduzgun/seo-article-draft-generator

Recommended reading

That link exposes Actors and Apify documentation, plus my SEO Article Generator Actor when it is available to the customer. More on why MCP is a control layer for agent work is in my article on MCP developer workflows.

MCP Per Client

Illustration: multiple clients connect separate Apify accounts or tokens to the same SEO Actor through MCP
Illustration: multiple clients connect separate Apify accounts or tokens to the same SEO Actor through MCP

For client work, I do not want to mix accounts, tokens, and runs. Each customer should have their own Apify environment or at least a separate API token.

That gives three advantages:

clearer cost tracking
better data separation
easier debugging per customer

A simple OAuth setup in an MCP client can look like this:

json
{
  "mcpServers": {
    "apify-client-acme": {
      "url": "https://mcp.apify.com/?tools=actors,docs,uduzgun/seo-article-draft-generator"
    }
  }
}

If the customer uses a Bearer token, the token should live in the customer's secure client or server configuration:

json
{
  "mcpServers": {
    "apify-client-acme": {
      "url": "https://mcp.apify.com/?tools=actors,docs,uduzgun/seo-article-draft-generator",
      "headers": {
        "Authorization": "Bearer <APIFY_TOKEN_FOR_CLIENT_ACME>"
      }
    }
  }
}

Do not use the same token for every customer. Do not write tokens in prompts, screenshots, issues, or shared documents.

What the Customer Needs to Send Us

For the best result, we do not need secret system details. We need the right public context.

Preferably send:

the customer's website
the URL where the article will be published
2-5 existing pages or articles the article should understand
audience and offer
main keyword or search intent
desired tone
pages that should receive internal links
anything we should not claim

We can read the customer's public pages to understand the company before writing. That does not mean we copy their old text. We use the pages as context for tone, offer, audience, and internal links.

Managed Setup for Companies

Managed setup is for teams that want the workflow ready per client, not just a link to an Actor.

Then we set up:

Apify account or client token per customer
MCP configuration per workspace
input templates for website, destination URL, and reference pages
scoring and rewrite workflow
image generation when needed
a simple review process before publishing
Recommended reading

This fits agencies, e-commerce companies, SaaS teams, and consultants who want to sell better SEO content without building everything from scratch. If you want to see how I already run publishing and SEO workflows in my own infrastructure, read about my custom CRM CMS.

Important Limitations

I do not promise rankings. No serious SEO service should.

What we can deliver is a better process, better research, clearer structure, and a faster path to an editorial draft. Publishing still requires human review of facts, brand voice, and business claims.

Legal, medical, financial, and other sensitive areas need extra review. The service should not replace a responsible expert.

Next Steps

If you want to test the workflow, send three things:

The website.
The URL or section where the article will be published.
A few reference pages that show the offer, tone, and internal links.

Then we can create a first SEO draft, score it, and show what needs to change before publishing.

You can create an Apify account here: https://apify.com?fpr=v5tn4v.

The MCP server for the workflow is here: https://mcp.apify.com/?tools=actors,docs,uduzgun/seo-article-draft-generator.

FAQ

Can the customer use MCP without sharing their Apify token with us?+
Yes. The customer can use the OAuth flow in their MCP client when the client supports it. If a Bearer token is used, it should live in the customer's own secure client or server configuration, not in a shared prompt or article.
Does each customer need their own Apify account?+
For clear cost control and data separation, it is best for each customer to use their own Apify account or at least a separate API token per customer environment.
Can the service write based on the customer's website?+
Yes. The customer can provide their website, destination URL, and reference pages. The workflow uses that public context as input for tone, offer, internal links, and structure.
Are images included?+
Yes, the service can generate a featured image for the article when image generation is enabled. For managed setups, we can also create simple process illustrations and charts that fit the article.
Are the prices fixed?+
The prices in the article are launch prices for Apify Store. The current price should always be checked in the Apify listing once the Actor is live.

Recommended for you

How I Built an AI Content Pipeline That Writes Like Me

How I Built an AI Content Pipeline That Writes Like Me

I built an AI content pipeline that writes like me using author context, Search Console data, and real internal links.

9 min read
MCP Developer Workflows: The Real Control Layer

MCP Developer Workflows: The Real Control Layer

MCP developer workflows are the control layer for production agents: scoped tools, approval gates, source-backed context, and replayable actions.

8 min read
Custom CRM CMS with Next.js and AI Agents in 2026

Custom CRM CMS with Next.js and AI Agents in 2026

How I built a custom CRM CMS with Next.js, Supabase, and AI agents to run 500+ posts, SEO workflows, and multilingual publishing.

18 min read