Moz Blog Scraper [💰$0.9] — SEO Articles, Authors & Categories avatar

Moz Blog Scraper [💰$0.9] — SEO Articles, Authors & Categories

Pricing

from $0.90 / 1,000 results

Go to Apify Store
Moz Blog Scraper [💰$0.9] — SEO Articles, Authors & Categories

Moz Blog Scraper [💰$0.9] — SEO Articles, Authors & Categories

Scrape the Moz blog by category or the whole blog and get one structured row per SEO article with author and dates plus the full article text and every image link. Ready for a spreadsheet, a content database or an AI pipeline.

Pricing

from $0.90 / 1,000 results

Rating

0.0

(0)

Developer

Black Falcon Data

Black Falcon Data

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

3 days ago

Last modified

Share

What does Moz Blog Scraper do?

Moz Blog Scraper extracts SEO articles from the Moz blog — one structured row per article with title, author, category, publish dates, excerpt, the full article text (plain text, Markdown and HTML) and every image link. Pick one or more blog categories, or * for the whole blog, set a result limit and run the same scrape consistently over time.

How to use this actor

  • 👉 Register for a free Apify account — no credit card required.
  • 🎉 Just click Sign up free on Apify → and complete a quick signup.
  • 💰 A free Apify account includes $5 in monthly credits — enough to test this actor.
  • ⏳ Scrape during the free trial, with no commitment or upfront payment required.

Key features

  • 🖼️ Images: imageUrl and images with every image URL, not just the thumbnail.
  • 🗂️ Category path: category and categories place each record in moz.com's own category tree.
  • 🗓️ Posting dates: publishedAt tell you how fresh each record is.
  • 🔍 Category scrape: scrape one or more Moz blog categories with the query input, or * for the whole blog.
  • 🔗 Paste-mode: paste moz.com URLs into startUrls to scrape exactly the pages you picked in the browser.
  • 📋 Detail enrichment: full article text as descriptionText, descriptionMarkdown and descriptionHtml, plus images from each post. On by default; turn includeDetails off for a faster listing-only run.
  • ♻️ Incremental mode: recurring runs emit only articles that are new or updated since the last run — keep a content database or an alert feed current without re-fetching the whole blog.
  • 🔔 Notifications: Telegram, Slack, Discord, WhatsApp Cloud API, and generic webhook out of the box. Pair with incremental for daily new-listing alerts without pipeline glue.
  • 📦 Compact mode: core fields only — title, author, category, publish date, URL and excerpt — for AI agents and MCP workflows.
  • 🔌 MCP connectors: push a run summary of new articles into Notion via Apify's MCP connectors — no export step, no glue code. Opt-in, deterministic field-mapping (no AI).
  • 📌 Change classification: each record carries a changeType of NEW / UPDATED / UNCHANGED / REAPPEARED / EXPIRED. Default emits NEW + UPDATED + REAPPEARED; opt into the others with emitUnchanged / emitExpired.

What data can you extract from moz.com?

Each result is one Moz blog article: title, url, author, authorName, authorUrl, category, categories, publishedAt, modifiedAt, excerpt, imageUrl and wordCount. With includeDetails on (the default) each article also gets its full body as description, descriptionText, descriptionMarkdown and descriptionHtml, plus images with every image URL in the post. The fields domain_authority, home_page_authority, linking_root_domains, ranking_keywords and spam_score exist for compatibility with Moz domain-metric tools; the blog does not publish these numbers, so they are always null. In standard mode all fields are always present — unavailable data points are returned as null, never omitted. In compact mode only core fields are returned.

Input

The main inputs are a search keyword and a result limit. Additional filters and options are available in the input schema.

Key parameters:

  • query — Blog category slug to scrape, e.g. link-building, local-seo, keyword-research, whiteboard-friday. Use * for the whole blog. Use a JSON array for several categories, e.g. ["link-building","local-seo"]. Required if no startUrls provided.
  • maxResults — Maximum total results (0 = unlimited). (default: 100)
  • startUrls — Paste raw moz.com blog listing URLs (e.g. https://moz.com/blog/category/link-building). Each URL becomes its own search task; results are merged and deduped by listing ID across all URLs. When provided, startUrls REPLACE the query/location fields (each supported URL becomes one task; unsupported URLs are skipped, and if none is supported the run stops with an input error). (default: [])
  • includeDetails — Fetch full listing details. (default: true)
  • descriptionMaxLength — Truncate description to N chars. 0 = no truncation. (default: 0)
  • compact — Core fields only (for AI-agent/MCP workflows). (default: false)
  • descriptionFormat — Pick a single description representation. all keeps every variant; text / html / markdown drop the others. (default: "all")
  • excludeEmptyFields — Drop null, empty-string, and empty-array fields from each record before push. Smaller payloads for AI agents and dashboards. (default: false)
  • incrementalMode — Compare against previous run state. stateKey is optional — defaults to a value derived from search inputs (categories, startUrls) so different filter sets never share state. (default: false)
  • stateKey — Optional. Stable identifier for the tracked search universe. Leave empty to auto-generate from search inputs.
  • emitUnchanged — When incremental, also emit records that haven't changed. (default: false)
  • emitExpired — When incremental, also scan the full category so records no longer listed are detected. (default: false)
  • ...and 14 more parameters

Input examples

One category — Articles from one Moz blog category with a result cap.

→ Full payload per article — body text, Markdown, HTML and image links included.

{
"query": "link-building",
"maxResults": 50
}

Whole blog, new articles only — Scan the whole blog and only emit articles that are new or changed since the previous run with this stateKey.

→ First run builds the baseline state; later runs emit only new or updated articles.

{
"query": "*",
"maxResults": 0,
"incrementalMode": true,
"stateKey": "moz-blog-tracker"
}

Compact output for AI agents — Core fields only for one category.

→ Small payload with title, author, category, date, URL and excerpt — ideal for piping into LLMs.

{
"query": "local-seo",
"maxResults": 50,
"compact": true
}

Output

Each run produces a dataset of structured article records. Results can be downloaded as JSON, CSV, or Excel from the Dataset tab in Apify Console.

Example article record

{
"input": "link-building",
"domain": "moz.com",
"link": "https://moz.com/blog/two-truths-and-lie-about-digital-pr",
"report_link": "https://moz.com/blog/two-truths-and-lie-about-digital-pr",
"listingKey": "two-truths-and-lie-about-digital-pr",
"title": "Two Truths and a Lie About Digital PR",
"url": "https://moz.com/blog/two-truths-and-lie-about-digital-pr",
"portalUrl": "https://moz.com/blog/two-truths-and-lie-about-digital-pr",
"author": "Debbie Chew",
"authorName": "Debbie Chew",
"authorUrl": "https://moz.com/community/users/18690613",
"authorImageUrl": "https://moz.com/images/user/photo/360360-profileavatar-1646242600050.jpg?w=160&h=160&auto=compress%2Cformat&fit=crop&dm=1646712894&s=1c35e54dfd794ced1dfc36ba20019033",
"publishedAt": "2026-09-09T00:00:00-07:00",
"createdAt": "2026-08-28T12:27:44-07:00",
"modifiedAt": "2026-09-08T12:07:10-07:00",
"category": "Digital PR",
"categories": [
"Digital PR",
"Keyword Research",
"Link Building"
],
"excerpt": "You don't need an agency for digital PR. Debbie Chew shares her CIDER framework, a real $1M campaign recovery, and how to get your brand cited by AI.",
"imageUrl": "https://moz.com/images/blog/insets/MozCon-2026-Inset-Images/Debbie-Chew-MozCon-2026-NYC-Inset-Image-Speaker-Only.png?w=1300&h=900&auto=compress%2Cformat&fit=crop&dm=1784737156&s=45d7ecba510a5340b71f11...",
"ogImageUrl": "https://moz.com/images/blog/Blog-OG-images/Two-Truths-and-a-Lie-About-Digital-PR-Debbie-Chew-OG-Image.png?w=1200&h=630&q=82&auto=format&fit=crop&dm=1788883444&s=12114aa2422815a57d37fc55cb01eea0",
"seoTitle": "Two Truths and a Lie About Digital PR",
"language": "en-us",
"wordCount": 1584,
"readingTimeMinutes": 7,
"bodyText": "Digital PR is more than just a link from Forbes. Campaigns can fail. And you need an agency to do it. That last one's the lie. Most teams believe it, so they default to on-site tactics while third-par...",
"description": "You don't need an agency for digital PR. Debbie Chew shares her CIDER framework, a real $1M campaign recovery, and how to get your brand cited by AI.",
"descriptionText": "Digital PR is more than just a link from Forbes. Campaigns can fail. And you need an agency to do it. That last one's the lie. Most teams believe it, so they default to on-site tactics while third-par...",
"descriptionMarkdown": "Digital PR is more than just a link from Forbes. Campaigns can fail. And you need an agency to do it. That last one's the lie. Most teams believe it, so they default to on-site tactics while third-par...",
"listingId": "08590c09c5d39bac9fa704655e1602fffc3b856c7645cd53cb6182430eaa1790",
"searchQuery": "link-building",
"contentQuality": "full",
"detailFetched": true,
"scrapedAt": "2026-10-20T01:47:50.231Z",
"source": "moz.com"
}

Incremental fields

When incremental mode is on, each record also carries:

  • changeType — one of NEW, UPDATED, UNCHANGED, REAPPEARED, EXPIRED. Default output covers NEW / UPDATED / REAPPEARED; set emitUnchanged: true or emitExpired: true to opt into the others.
  • isRepost, repostOfId, repostDetectedAt — populated when a new listing matches the tracked content of a previously expired one. Set skipReposts: true to drop detected reposts from the output.

How to scrape moz.com

  1. Go to Moz Blog Scraper in Apify Console.
  2. Enter one or more blog category slugs in query (e.g. link-building, local-seo), * for the whole blog, or paste moz.com blog URLs into startUrls.
  3. Set maxResults to control how many articles you need (0 = all).
  4. Keep includeDetails on for the full article text and every image link.
  5. Click Start and wait for the run to finish.
  6. Export the dataset as JSON, CSV, or Excel.

Use cases

  • Extract article data from moz.com for market research and competitive analysis.
  • Monitor new and changed articles on scheduled runs without processing the full dataset every time.
  • Feed structured data into AI agents, MCP tools, and automated pipelines using compact mode.
  • Export clean, structured data to dashboards, spreadsheets, or data warehouses.

How much does it cost to scrape moz.com?

Moz Blog Scraper uses pay-per-event pricing. You pay a small fee when the run starts and then for each result that is actually produced.

  • Run start: $0.00005 per run
  • Per result: $0.0009 per article record

Example costs:

  • 10 results: $0.00904
  • 25 results: $0.023
  • 100 results: $0.09
  • 200 results: $0.18
  • 500 results: $0.45

Example: recurring monitoring savings

These examples compare full re-scrapes with incremental runs at different churn rates. Churn is the share of articles that are new or whose tracked content changed since the previous run. Actual churn depends on your query breadth, source activity, and polling frequency — the scenarios below are examples, not predictions.

Example setup: 250 articles per run, daily polling (30 runs/month). Costs scale linearly with the number of articles.

Churn rateFull re-scrape run costIncremental run costSavings vs full re-scrapeMonthly cost after baseline
5% — stable niche query$0.23$0.01$0.21 (95%)$0.34
15% — moderate broad query$0.23$0.03$0.19 (85%)$1.01
30% — high-volume aggregator$0.23$0.07$0.16 (70%)$2.03

Full re-scrape monthly cost at the same cadence: $6.75. First month with incremental costs $0.55 / $1.21 / $2.18 for the 5% / 15% / 30% scenarios because the first run builds baseline state at full cost before incremental savings apply.

Platform usage is included in the per-result fee shown above.

FAQ

How many results can I get from moz.com?

The number of results depends on the search query and available articles on moz.com. Use the maxResults parameter to control how many results are returned per run.

Does Moz Blog Scraper support recurring monitoring?

Yes. Enable incremental mode to only receive new or changed articles on subsequent runs. This is ideal for scheduled monitoring where you want to track changes over time without re-processing the full dataset.

Can I integrate Moz Blog Scraper with other apps?

Yes. Moz Blog Scraper works with Apify's integrations to connect with tools like Zapier, Make, Google Sheets, Slack, and more. You can also use webhooks to trigger actions when a run completes.

Can I use Moz Blog Scraper with the Apify API?

Yes. You can start runs, manage inputs, and retrieve results programmatically through the Apify API. Client libraries are available for JavaScript, Python, and other languages.

Can I use Moz Blog Scraper through an MCP Server?

Yes. Apify provides an MCP Server that lets AI assistants and agents call this actor directly. Use compact mode, descriptionMaxLength, a single descriptionFormat, and excludeEmptyFields to keep payloads manageable for LLM context windows.

This actor extracts publicly available data from moz.com. Web scraping of public information is generally considered legal, but you should always review the target site's terms of service and ensure your use case complies with applicable laws and regulations, including GDPR where relevant.

Your feedback

If you have questions, need a feature, or found a bug, please open an issue on the actor's page in Apify Console. Your feedback helps us improve.

You might also like

Getting started with Apify

New to Apify? Create a free account with $5 credit — no credit card required.

  1. Sign up — $5 platform credit included
  2. Open this actor and configure your input
  3. Click Start — export results as JSON, CSV, or Excel

Need more later? See Apify pricing.

Disclaimer

This actor accesses only publicly available data on moz.com. You are responsible for how you use the extracted data — in particular any personal information such as names, phone numbers, or email addresses — and for complying with Moz Blog's terms of use, applicable data-protection law (including the GDPR where it applies), and the anti-spam rules of your jurisdiction.

This actor is an independent tool and is not affiliated with, endorsed by, or sponsored by Moz Blog or any of its subsidiaries. All trademarks mentioned are the property of their respective owners.

Search keywords

moz scraper, moz api, apify moz, moz data extraction, moz blog scraper, moz blog api, apify moz blog, moz blog data extraction, moz.com scraper, moz.com data, moz.com api.