by Smart Cloud Solutions Inc. 0 (0 reviews)

SmartCloud Static Publisher

Name: SmartCloud Static Publisher
Author: Smart Cloud Solutions Inc.

Reliable static export for WordPress with sitemap-based crawl, browser rendering, asset capture, and S3 + CloudFront deployment.

SmartCloud Static Publisher ranks #33,305 among WordPress.org plugins with 10+ active installations, is #2,295 of 5,310 in the Utilities & Tools category, and was last updated Oct 30, 2026. Data from WordPress.org, refreshed twice daily — see methodology.

Compatible with WP 7.1.4

v1.2.2 Current Version v1.2.2

Updated 1 week ago Last Update on 30 Oct, 2026

Refreshed 1 week ago Last Refreshed on

#2,295 of 5,310 in Utilities & Tools Top 50% by installs Actively maintained

View on WordPress.org

Rank

#33,305

— No change

Active Installs

10+

-41.2%

KW Avg Position

62.3

1 worse

Downloads

1.7K

+9 today

Support Resolved

— No change

Rating

Review 0 out of 5

0 (0 reviews)

Next Milestone 20

Total Progress 70%

10+ 20+

10,132

Ranks to Climb

Growth Needed

8,000,000

Active Installs

Pro

Unlock Exact Install Count

See the precise estimated active installs for this plugin, calculated from real-time ranking data.

Exact install estimates within tiers
Track install growth over time
Milestone progress predictions

Upgrade to Pro

Need 3 more installs to reach 20+

Rank Changes

Current #33,305

Change

Best #

Upgrade to Pro

Unlock 30-day and 90-day rank history charts with a Pro subscription.

Upgrade Now

Active Installs Growth

Upgrade to Pro

Active Installs 0,000,000+

Growth +0.0%

Peak 0,000,000

Downloads Growth

Downloads

Growth

Peak

Upgrade to Pro

Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.

Upgrade Now

Reviews & Ratings

0.0

0 reviews

Overall 0%

0 (0%)

Track This Plugin

Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.

Start Tracking Free

Plugin Details

Version: 1.2.2
Last Updated: Oct 30, 2026
Requires WP: 6.9+
Tested Up To: 7.1.4
PHP Version: 8.1 or higher
Author: Smart Cloud Solutions Inc.

Support & Rating

Rating: ☆ ☆ ☆ ☆ ☆ 0
Reviews: 0
Support Threads: 0
Resolved: 0%

Keywords

cloudfront export playwright s3 static site

Upgrade to Pro

Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.

Upgrade Now

Similar Plugins

Adminify – White Label, Admin Menu Editor, Login Customizer

6K+ installs

#2,757

Master Addons for Elementor – Elementor Addons, Widgets, Mega Menu Builder, Popup Builder, Widget Builder & Template Kits

30K+ installs

#1,015

Elementor Website Builder – more than just a page builder

10M+ installs

Contact Form 7

10M+ installs

All-in-One WP Migration and Backup

5M+ installs

#10

UpdraftPlus: WP Backup & Migration Plugin

4M+ installs

#14

WPCode – Insert Headers and Footers + Custom Code Snippets – WordPress Code Manager

View all Utilities-and-tools plugins

Frequently Asked Questions

Common questions about SmartCloud Static Publisher

No. For safety and reliability, PHP only stores config and queue instructions. The actual crawl/deploy is performed by the Node exporter.

Not by default. This plugin does not spawn Node.js from PHP. Recommended production setup is system cron (or systemd timer) that runs publisher-exporter queue-runner.

No. Scheduler rules are evaluated only when the external publisher-exporter queue-runner process starts from cron, systemd timer, or Windows Task Scheduler. Important details: * Scheduler only adds matching jobs to runtime/queue.json; the same runner tick or a later tick then processes them through the normal queue. * Recommended cadence is every 1 minute. * Supported scheduled commands are publish, crawl, deploy, invalidate, retry-timeouts, url, and Professional/Agency-only content-sync. * Content sync requires a successful normal publish baseline and processes only the configured post types, multisite scope, listings, archives, and sitemap surfaces. * The scheduler timezone field is currently informational for operations context; interval matching is based on elapsed minute buckets checked at each runner start. * If an equivalent queued or running job already exists for the same command, crawl mode, deployment profile, and URL, the rule is skipped for that interval bucket.

Yes. Start publisher-exporter queue-runner or npx @smart-cloud/publisher-exporter queue-runner manually from PowerShell for one-off processing, or use Windows Task Scheduler with a repeating 1-minute trigger plus a small PowerShell wrapper. Linux production should use system cron.

Yes. Use Download config next to the queued job, extract publisherConfig into publisher.config.json, then run the exact manualExecution.commands.jobPosix or manualExecution.commands.jobPowerShell command from the downloaded JSON. This replays the job outside WordPress and does not update queue state automatically.

Yes. Exporter config supports two SDK modes: * sdk-upload-delete * sdk-upload-only

Yes. Deploy and invalidate now write detailed progress logs in addition to crawl logs. Use logLevel (error, warn, info, debug) to control verbosity.

No. SDK deploy now skips unchanged files using S3 ETag + size fast checks, with checksum metadata fallback (x-amz-meta-wpsuite-sha256) when ETag is not decisive.

Processing concurrency sets the local page-render, asset-download, and final rewrite worker counts together. When Delegate processing to Lambda is enabled, the same value is also the coordinator's requested fan-out for each delegated page-render, asset-fetch, rewrite, or deploy phase. With full delegation, rendered HTML and downloaded assets remain in the worker S3 workspace for Lambda rewrite and direct S3-to-S3 deployment; the coordinator does not download them for a second HTML scan or restage the completed export. It still owns the dynamic URL queues, safety and incremental decisions, compact manifests, retries, logs, invalidation, and terminal job state. The setting is not an account-wide Lambda concurrency limit: function reserved concurrency, regional quotas, other sites, available batches, and downstream capacity can reduce effective parallelism. Existing installations that saved different legacy settings for individual phases keep those values until an administrator changes the corresponding common control. The Configuration screen shows a warning for that mixed legacy state. Render, rewrite, and deploy batch sizes are configurable independently. A render batch reuses one Chromium process for up to 20 sequential pages; rewrite and deploy support larger bounded batches because they do not load WordPress. Runtime progress advances after each completed batch. Asset downloads use protocol-bounded batches of 20 URLs. Retry counts remain internal compatibility settings.

Use blockedSearchFragments for preview or editor query patterns that must never enter the crawl queue. The setting is empty by default. If your WordPress setup exposes plugin-specific preview URLs, add those fragments explicitly to your config. Typical examples include page-builder previews, WordPress Customizer preview parameters, multilingual editor preview flags, and similar per-plugin markers. This matters because exported page output paths ignore query strings, so a preview URL can overwrite the canonical output for the same page path.