SmartCloud Static Publisher
Static Publisher is a WordPress plugin + Node.js exporter workflow for deterministic static publishing. Static Publisher is part of the WP Suite product family by Smart Cloud Solutions, Inc. WP Suite keeps WordPress as the CMS and editing layer, while optional connected features can extend selected workflows into modular AWS-backed services for identity, AI, APIs, workflows, protected routes, and static delivery. The free Static Publisher features described here do not require a WP Suite account, subscription, or WP Suite-managed AWS backend; you control any AWS credentials and target infrastructure you configure for publishing. Project repository and extended documentation: https://github.com/smartcloudsol/static-publisher It is designed for setups where WordPress is the editor/origin and production is served from static hosting (for example S3 + CloudFront). The plugin provides: Admin UI for export configuration Runtime config generation in uploads Job queueing (publish, crawl, deploy, invalidate, retry-timeouts, single URL) Run status and log viewing The Node.js exporter provides: Sitemap-based discovery Playwright rendering for JS-heavy pages Asset capture from network + parsed sources Separate concurrency for page rendering, asset downloads, and final rewrite URL rewriting modes (absolute, root-relative, relative) S3 upload and CloudFront invalidation Detailed logging for crawl, deploy, and invalidate This plugin does not execute shell commands directly from PHP. Instead, it writes queue/config runtime files that an external Node runner executes. This shell-first design is intentional: rendered frontend pages can be exported by Playwright/Node while WordPress/PHP remains focused on queueing and configuration. This plugin is not affiliated with or endorsed by Amazon Web Services or the WordPress Foundation. All trademarks are property of their respective owners. Usage Notice SmartCloud Static Publisher does not require an external SaaS account to operate. The plugin itself only manages configuration and queue state in WordPress. Actual crawling and deployment are executed by your own Node runtime using this project’s exporter commands. This means: You control when and where exports run. You control AWS credentials and target infrastructure. WordPress/PHP does not proxy deployment traffic. The WordPress plugin ZIP does not bundle the Node.js exporter runtime; install @smart-cloud/publisher-exporter separately on the machine that processes queued jobs. Free and Premium Usage Notice SmartCloud Static Publisher is fully functional in Free mode and does not require a WP Suite account, subscription, trial period, or paid service to perform its core static publishing workflow. In Free mode, the plugin supports the complete static publishing flow: Configure source and target settings in WP Admin. Queue and run full crawl, publish, deploy, invalidate, retry-timeouts, and single-URL jobs. Export rendered WordPress pages using the separately installed Node.js exporter. Capture required assets discovered during browser rendering. Rewrite URLs according to the configured rewrite mode. Deploy exported files to the configured S3 bucket. Create CloudFront invalidations for the configured distribution. View current job status and standard run logs. Free mode includes S3 deployment and CloudFront invalidation. These are not paid-only features. Audit Logs is also part of the main Static Publisher navigation and is not gated behind a WP Suite subscription. The plugin package itself manages WordPress-side configuration, queue state, runtime files, and status/log access. Actual crawling and deployment are executed by the separately installed @smart-cloud/publisher-exporter CLI on the user’s own server, workstation, CI runner, or other queue-runner host. Optional WP Suite Pro features are not required for the plugin to work. They are additional workflow, convenience, and team/enterprise publishing features. Examples may include: Incremental crawl / incremental publish / scheduled workflows. Extra Deployment Targets and Scheduler Settings backed by linked WP Suite site configuration. Additional team/workspace-oriented configuration features. Extra Deployment Targets are selected by key at deploy time, while downloaded job configs keep only the base target plus an optional target override id. These optional Pro features may be visible in the plugin interface as upgrade-only controls, but they are separate from the fully functional free static publishing workflow described above. When no active WP Suite subscription is connected, SmartCloud Static Publisher remains usable for full static crawl/publish/deploy workflows. There is no time limit, export quota, forced trial expiry, or required payment for the core static publishing functionality. Server Prerequisites (Node + Playwright) The exporter requires both Node.js and Playwright browser binaries on the machine that executes queued jobs. Recommended Node setup is NVM + latest LTS: curl -fsSL https://raw.githubusercontent.com/nvm-sh/nvm/v0.40.3/install.sh | bash export NVM_DIR="$HOME/.nvm" && . "$NVM_DIR/nvm.sh" && nvm ls-remote --lts && nvm install --lts && nvm use --lts Install the standalone exporter CLI package and Chromium browser binary: npm install -g @smart-cloud/publisher-exporter && publisher-exporter install-browsers Important: If cron runs under the same OS user that installed Node and Playwright, NVM plus the default user-scoped Playwright cache is fine. If cron runs as a different or non-login service user such as www-data, prefer an explicit HOME, a PATH that already contains publisher-exporter and node, plus a shared PLAYWRIGHT_BROWSERS_PATH. In crontab, prefer absolute paths instead of relying on $HOME expansion inside the PATH value. npx playwright install is not a global install; browser binaries are user-scoped by default (usually under ~/.cache/ms-playwright). If multiple users may run jobs, use PLAYWRIGHT_BROWSERS_PATH to point to a shared browser folder and grant proper permissions. If the shared browser directory lives under a protected system path, create it once with elevated privileges and make it writable by the same OS user that will run publisher-exporter install-browsers. The later cron job only needs read/execute access to that directory tree. For internal/self-signed TLS origins, enable Allow self-signed TLS certificates during crawl in the admin UI (config key: ignoreHttpsErrors). If you prefer a shared browser cache for a non-login service user such as www-data, create the shared directory once, hand it to the job user, then install browsers from the CLI package without keeping the browser cache root-owned: sudo mkdir -p /var/lib/playwright-browsers && sudo chown "$USER":"$USER" /var/lib/playwright-browsers && PLAYWRIGHT_BROWSERS_PATH=/var/lib/playwright-browsers /usr/bin/npx @smart-cloud/publisher-exporter install-browsers Run A Queued Job From Another Machine If the WordPress host cannot run Node, Playwright, or cron, you can replay a queued job from your own shell or CI machine. In the Job Queue panel click Download config next to the queued job and save the file as queued-job.json. Extract the nested publisherConfig object to publisher.config.json using one of the commands already included in the downloaded file under manualExecution.commands. Install @smart-cloud/publisher-exporter on that machine first. Optionally edit publisher.config.json locally, for example to change outputDir to a writable local folder. Run the exact command from manualExecution.commands.jobPosix or manualExecution.commands.jobPowerShell. If you also want to deploy from your own machine, continue with the provided deploySdk and invalidateSdk commands from the same manualExecution.commands block. Important: This is an out-of-band replay of the queued job and does not mark the WordPress queue item as completed automatically. If the original queued item should not run later on the server, remove or clean it up in WordPress after your manual replay. The WordPress plugin ZIP does not contain the exporter runtime. Install @smart-cloud/publisher-exporter separately on the machine that replays the downloaded job. Shared Runtime Across Two Hosts SmartCloud Static Publisher can run with WordPress on one machine and the queue runner on another, as long as both machines point to the same shared wp-content/uploads/smartcloud-static-publisher storage. Example: WordPress host sees the storage at /var/www/site/wp-content/uploads/smartcloud-static-publisher Queue runner host mounts the same storage at /mnt/site Queue runner uses STATIC_PUBLISHER_RUNTIME_DIR='/mnt/site/runtime' Recommended rules for this setup: Keep outputDir and logDir storage-relative in admin, for example export and logs, not machine-specific absolute paths. Use @storage-root in postCrawlCopyMap when the source files are already inside the shared publisher storage. Use @wp-root only when the queue runner host can also access the WordPress tree, and set STATIC_PUBLISHER_WP_ROOT (or WPSUITE_STATIC_PUBLISHER_WP_ROOT) on that host. @runtime points to the shared runtime folder itself. Example postCrawlCopyMap sources: @storage-root/shared-assets/ @wp-root/wp-content/uploads/smartcloud-static-publisher/ If you inspect the raw queue-runner-heartbeat.json, the runtimeDir and exporterDir values reflect the queue runner host paths. That is expected and does not break WordPress-side queue state handling. Machine-readable resources Plugin manifest: https://wpsuite.io/.well-known/ai-plugin.json OpenAPI spec (backend): https://wpsuite.io/.well-known/openapi.yaml External Services This plugin/workflow may integrate with the following external services, depending on configuration: Source WordPress origin and allowed asset hosts (required for crawl/export) What it is & what it’s used for: The configured source origin and allowed asset hosts are fetched during crawl/render to collect pages and assets for static export. What data is sent & when: Standard HTTP(S) requests from the exporter to source pages/assets. Request data typically includes normal browser request metadata (URL, headers, cookies/session context if your source site requires it). Where it goes: sourceOrigin and hostnames listed in allowedAssetHosts. Amazon S3 (optional; deploy command) What it is & what it’s used for: Object storage target for exported static files. What data is sent & when: Exported HTML/assets plus object metadata (content type, cache-control) when deploy runs. Where it goes / API usage: AWS S3 APIs via AWS SDK (PutObject, ListObjectsV2, DeleteObjects) to your configured bucket/region. Links: AWS Service Terms: https://aws.amazon.com/service-terms/ AWS Privacy: https://aws.amazon.com/privacy/ Amazon CloudFront (optional; invalidate command) What it is & what it’s used for: CDN invalidation after deployment. What data is sent & when: Invalidation path list and distribution identifier when invalidate runs. Where it goes / API usage: AWS CloudFront API via AWS SDK (CreateInvalidation) for your configured distribution. Links: AWS Service Terms: https://aws.amazon.com/service-terms/ AWS Privacy: https://aws.amazon.com/privacy/ WP Suite platform connection (optional; site/workspace linking & shared features) When it applies: When you use WP Admin → SmartCloud → Connect your Site to WP Suite to link this WordPress site to a WP Suite workspace, or to switch/disconnect later. What it’s used for: Storing and retrieving Pro feature configuration (e.g., API/chatbot/feature settings) and enabling an admin-side preview experience so you can try Pro features in WP Admin before enabling them on the live site. What data may be sent: Minimal account/session data required for authentication, and minimal site/workspace linking data required to associate a WordPress site with a workspace (e.g., site/workspace identifiers and the site’s URL/domain). Where it goes / how it’s called: Secure HTTPS requests from the browser to WPSuite.io services (e.g. wpsuite.io and api.wpsuite.io). Links: WPSuite.io Privacy Policy: https://wpsuite.io/privacy-policy WPSuite.io Terms of Use: https://wpsuite.io/terms-of-use Amazon Cognito (optional; authentication for WP Suite Hub and/or protected APIs) When it applies: When using the WP Suite Hub, users authenticate (sign in / sign up) before creating/selecting a workspace and linking a site. If a plugin is configured to access protected endpoints that rely on Cognito, authentication/token flows may also be used for those requests. What it’s used for: User authentication and token-based authorization for subsequent API calls (e.g., to WPSuite.io APIs). Links: AWS Service Terms: https://aws.amazon.com/service-terms/ AWS Privacy: https://aws.amazon.com/privacy/ Stripe (optional; subscription/purchase flow) When it applies: Only when the user opens the optional WP Suite subscription / purchase flow in the shared admin component. What it’s used for: Displaying hosted pricing/subscription UI for optional paid features. What data may be sent: Browser/session data required by Stripe to render the hosted purchase UI and process the purchase flow. Links: Terms: https://stripe.com/legal/consumer Privacy: https://stripe.com/privacy Example IAM Role Profiles Adjust values before use (YOUR_BUCKET, YOUR_PREFIX, YOUR_ACCOUNT_ID, YOUR_DISTRIBUTION_ID). Command-to-profile mapping: deploy -> deploy-only invalidate -> deploy+invalidate publish -> deploy+invalidate deploy-only policy (S3 only): { “Version”: “2012-10-17”, “Statement”: [ { “Sid”: “ListOnlyTargetPrefix”, “Effect”: “Allow”, “Action”: [“s3:ListBucket”], “Resource”: “arn:aws:s3:::YOUR_BUCKET”, “Condition”: { “StringLike”: { “s3:prefix”: [“YOUR_PREFIX/“] } } }, { “Sid”: “RWOnlyTargetPrefixObjects”, “Effect”: “Allow”, “Action”: [ “s3:GetObject”, “s3:PutObject”, “s3:DeleteObject”, “s3:AbortMultipartUpload”, “s3:ListBucketMultipartUploads”, “s3:ListMultipartUploadParts” ], “Resource”: “arn:aws:s3:::YOUR_BUCKET/YOUR_PREFIX/” } ] } deploy+invalidate policy (S3 + CloudFront invalidation): { “Version”: “2012-10-17”, “Statement”: [ { “Sid”: “ListOnlyTargetPrefix”, “Effect”: “Allow”, “Action”: [“s3:ListBucket”], “Resource”: “arn:aws:s3:::YOUR_BUCKET”, “Condition”: { “StringLike”: { “s3:prefix”: [“YOUR_PREFIX/“] } } }, { “Sid”: “RWOnlyTargetPrefixObjects”, “Effect”: “Allow”, “Action”: [ “s3:GetObject”, “s3:PutObject”, “s3:DeleteObject”, “s3:AbortMultipartUpload”, “s3:ListBucketMultipartUploads”, “s3:ListMultipartUploadParts” ], “Resource”: “arn:aws:s3:::YOUR_BUCKET/YOUR_PREFIX/” }, { “Sid”: “InvalidateSpecificDistribution”, “Effect”: “Allow”, “Action”: [“cloudfront:CreateInvalidation”], “Resource”: “arn:aws:cloudfront::YOUR_ACCOUNT_ID:distribution/YOUR_DISTRIBUTION_ID” } ] } Trademark Notice Amazon Web Services, AWS, Amazon S3, and Amazon CloudFront are trademarks of Amazon.com, Inc. or its affiliates. SmartCloud Static Publisher is an independent project and is not affiliated with, sponsored by, or endorsed by Amazon Web Services or the WordPress Foundation. Source & Build Public source code: The project source is maintained by Smart Cloud Solutions, Inc. Build and distribution: SmartCloud Static Publisher is shipped to WordPress.org as a pre-built distribution. Build steps and development notes are documented in the repository README.
Top keywords
- s329×1.32%
- aws25×1.14%
- static23×1.05%
- wordpress21×0.96%
- wp20×0.91%
- publisher16×0.73%
- amazon15×0.68%
- https15×0.68%
- site14×0.64%
- suite14×0.64%
- wp suite14×0.64%
- deploy13×0.59%
Yoast SEO – Advanced SEO with real-time guidance and built-in AI
Real-time SEO guidance, schema, and AI built in. Help search engines and AI systems understand your content. All AI tools included, no hidden fees. Yoast SEO: the #1 WordPress SEO plugin Since 2008, Yoast SEO has helped site owners get their content found. More than 10 million websites now run it, from small local businesses to some of the most visited sites on the web. Our mission is SEO for everyone. You should not need a specialist, a big budget, or a technical background to give your content a fair chance of being discovered. Yoast SEO gives you everything you need to manage your on-site SEO. The Yoast SEO Premium plugin and its extensions unlock more advanced and AI-powered tools. Ready for search, and ready for AI People no longer only type queries into Google. They ask AI assistants, and those answers are built from content the AI has crawled, understood, and trusted. Yoast SEO helps you prepare for both. Schema.org structured data, so search engines and AI systems can understand what your content is actually about. Premium outputs significantly more schema types, including the E-E-A-T signals (experience, expertise, authoritativeness, and trustworthiness) that help AI systems understand who you are. Schema aggregation for NLWeb (Premium), which combines your site’s structured data into a single, deduplicated graph, so AI agents get a complete picture of your content in one request. Turn it on with a single toggle. LLMs.txt management, to guide how large language models interact with your content, including manual control over which pages are included. Bot blocker (Premium), to control which AI crawlers can use your content for training, including GPTBot, CCBot, and Google-Extended. Abilities API, so AI tools, dashboards, and automated workflows can read your SEO, readability, and inclusive language scores directly. Algorithm changes have been arriving for over 15 years, and Yoast has tracked every one of them. Keeping the plugin updated means you benefit from ongoing technical improvements, schema updates, and AI advancements automatically, all guided by our signature traffic light approach. Real-time guidance while you write SEO is one of the most consistent and cost-effective sources of website traffic, though it can be complex. Whether you are just starting out or you have done this for years, Yoast SEO tells you what to fix before you publish, not after. Red, orange, green. That is the whole idea. You get in-depth content and readability analysis that helps you create content designed to perform well in search, without needing to learn a new discipline first. Quick and easy setup Setting up Yoast SEO is quick and straightforward. No technical background required. Our step-by-step configuration wizard walks you through the essentials, so Yoast SEO can generate accurate structured data that helps search engines understand your site. Switching from another SEO plugin? Migration is seamless. You can import your existing SEO data and settings safely with our built-in import and export tools. AI tools built into your workflow Yoast’s AI tools come with Yoast SEO Premium, and they sit inside the editor you already use. There is no separate AI subscription, no extra login, and no credit top-up to buy. Every suggestion waits for your approval before anything saves. Yoast AI Generate: creates five SEO-friendly titles and meta descriptions instantly, with one-click regeneration for more options. Yoast AI Optimize: suggests improvements to keyphrase placement, including introduction, distribution, and density, with the option to apply or dismiss each edit. Yoast AI Summarize: generates a quick summary of your post to place anywhere in the block editor, so readers grasp the value fast. Yoast AI Content Planner (Premium): suggests five site-specific post ideas and builds a structured starter draft the moment you open a new post. Ideas are grounded in your own site, not generic topics, so your team never begins from a blank page. Bulk editor with AI drafts: review and fix titles, meta descriptions, and focus keyphrases across your whole site from one workspace, with search and status filters and a dedicated view per content type. The bulk editor is free. With Premium, select what needs work and AI drafts the metadata, including social sharing titles and descriptions, for you to approve. All AI tools included: no extra accounts, no separate credit purchase, no hidden costs. Content analysis and optimization SEO analysis to guide your keyword targeting, with up to 5 keyphrases in Premium and support for 20+ languages. Readability analysis for clear, engaging, user-friendly writing. Inclusive language analysis, so your content is more considerate and accessible. SERP previews for both desktop and mobile results. HowTo and FAQ blocks with built-in schema support. Breadcrumbs block for improved navigation. Semrush integration for keyword research directly inside Yoast SEO. Wincher integration to track keyword performance from your dashboard. Elementor integration for optimization inside your favorite builder. Technical SEO, handled for you Yoast SEO takes care of much of your site’s technical SEO automatically, which frees you to focus on your content. Automated meta tag optimization right out of the box. Canonical URLs to prevent duplicate content issues. Advanced XML sitemaps for clear site indexing. Deep Schema.org integration to improve how search engines and AI systems understand your site. Complete breadcrumb control for visitors and crawlers. Performance improvements that help reduce load times. Crawl settings to manage how bots access your site and reduce unnecessary server load. Every update delivers ongoing technical SEO enhancements automatically. Keep your website in perfect shape Whether you are a creator, a business owner, or a developer, Yoast SEO helps you maintain your site’s SEO health: Cornerstone content tools to organize and prioritize your key pages. Front-end SEO inspector to view and edit titles, descriptions, and schema live. SEO roles to delegate plugin access securely across your team. Regular 2-week update cycle, so you stay compatible with the latest SEO standards and search engine changes. Powerful integrations Yoast SEO works seamlessly with popular WordPress tools: Google Site Kit: access insights from Search Console, Analytics, and PageSpeed inside WordPress. Advanced Custom Fields (ACF): combine with ACF Content Analysis for Yoast SEO for advanced field optimization. Elementor: use full Yoast SEO functionality inside Elementor’s editor. Algolia: improve internal search accuracy and performance. Semrush: discover and optimize for high-value keywords. Wincher: track keyword positions and trends in Google Search. Jetpack: manage SEO and social previews in one place. Easy Digital Downloads (EDD): improve digital product visibility with integrated schema. Mastodon: verify your website on Mastodon with Yoast SEO Premium. WooCommerce: optimize ecommerce SEO with the dedicated WooCommerce extension. Yoast SEO Premium: AI-powered SEO for WordPress Yoast SEO Premium builds on everything above with advanced automation, AI tools, and professional support. It helps you optimize efficiently for both traditional search and AI-driven discovery. What it helps you tackle: Keeping pace with algorithm changes and AI search. Reaching the right audience. Automating redirects, crawl controls, and internal linking. Finding orphaned content and improving your site structure. Getting expert help when you need it. Premium highlights: AI-generated titles and meta descriptions, page by page or in bulk. AI Content Planner, so you never open a blank page. Smart internal linking suggestions to strengthen your site structure. Social previews for Facebook and X. Redirect manager with bulk tools, CSV import and export, and automatic prompts when you move or delete content. Bot blocker for AI crawlers, including GPTBot, CCBot, and Google-Extended. Schema aggregation for NLWeb, plus significantly more schema types than free. IndexNow integration, so search engines hear about your updates the moment you publish. Front-end SEO inspector for real-time editing. SEO workouts for orphaned and cornerstone content. Task list, unlocked in full, showing what to work on next with priority levels and time estimates. Google Docs add-on, so writers can run the full Yoast analysis before content ever reaches WordPress. One seat included. 24/7 premium support from SEO specialists. Included at no extra cost: Yoast Local SEO: help nearby customers find you, with local schema, a store locator, and opening hours management. Yoast Video SEO: help Google understand your videos, with video sitemaps and schema. Yoast News SEO: help your news content get discovered in Google News and Top Stories. Yoast WooCommerce SEO: advanced SEO for online stores Yoast WooCommerce SEO builds on Yoast SEO Premium with ecommerce-specific tools for your store’s visibility. Key ecommerce features: WooCommerce-specific XML sitemap that excludes non-shopping content. Product structured data for rich results, including price, reviews, and availability. Canonical URL management to prevent duplicates. Ecommerce-focused content analysis for GTINs, SKUs, and short descriptions. AI Generate for ecommerce: optimized titles and meta descriptions for product and category pages, at page level or drafted in bulk for products and categories. What that gets you: Better product visibility through automated structured data. More efficient crawling for large catalogs. Time saved through metadata templates and automation. Metadata across your whole catalog without editing rows one at a time. Built for WooCommerce, trusted by thousands of online stores worldwide. For developers Yoast SEO is built with developers in mind. With modern APIs, hooks, and a unified indexables system, you can extend or integrate SEO functionality across custom themes, plugins, or headless setups. REST API Retrieve SEO metadata for any post or URL, including meta tags, Open Graph, Twitter Cards, and Schema.org data. Learn more about the REST API. Surfaces API Access SEO data directly in code via YoastSEO()->meta->for_current_page(). Supports titles, descriptions, canonicals, and schema. Read the Surfaces API documentation. Metadata API Use the Metadata API to filter, override, or extend meta tags with WordPress hooks such as wpseo_title, wpseo_metadesc, and wpseo_canonical. Schema API The Schema API lets you modify or extend Schema.org graph pieces, including Article, Organization, Person, Breadcrumb, and WebPage entities. Abilities API integration Let AI tools, dashboards, and automated workflows read Yoast SEO data programmatically, including SEO, readability, and inclusive language scores for recent posts. Block editor compatibility Yoast SEO integrates directly with the WordPress block editor. It outputs schema for HowTo and FAQ blocks by default, and you can extend schema for custom blocks. Indexables At the core of Yoast SEO lies the indexables system, unifying all SEO data for faster queries and consistent metadata across outputs. Ongoing support and education Yoast is powered by expert developers, testers, and SEO specialists who keep improving the plugin. We are committed to helping you grow your SEO skills: Yoast SEO Academy: free and premium SEO courses, included in all paid plans. Yoast SEO blog, newsletter, and webinars. Yoast SEO Update podcast for the latest SEO insights. Bug reports on GitHub, for issue tracking rather than support. Yoast SEO: built to make search optimization accessible, reliable, and ready for the future of AI search.