How is FAQ schema auto-detected?

The plugin scans your post for any of: Yoast FAQ blocks, Rank Math FAQ blocks, SEOPress FAQ blocks, OR native HTML5 QuestionAnswer markup. If found, a FAQPage schema with Question / Answer items is emitted.

by Gunjan Jaswal 5 (1 reviews)

StaticForge for Cloudflare Pages

Name: StaticForge for Cloudflare Pages
Rating: 5.0 (1 reviews)
Author: Gunjan Jaswal

Auto-export WordPress as static HTML to Cloudflare Pages on publish — with SEO meta, JSON-LD schemas, sitemaps, and robots.txt.

StaticForge for Cloudflare Pages ranks #31,665 among WordPress.org plugins with 10+ active installations, is #1,301 of 3,802 in the SEO & Marketing category, a 5/5 rating from 1 reviews, and was last updated Sep 22, 2026. Data from WordPress.org, refreshed twice daily — see methodology.

Compatible with WP 7.1.1

v1.8.5 Current Version v1.8.5

Updated 10 hours ago Last Update on 22 Sep, 2026

Refreshed 7 hours ago Last Refreshed on

#1,301 of 3,802 in SEO & Marketing Top 50% by installs Actively maintained

View on WordPress.org

Rank

#31,665

— No change

Active Installs

10+

-37.5%

KW Avg Position

164

— No change

Downloads

952

+48 today

Support Resolved

— No change

Rating

100%

Review 5 out of 5

5 (1 reviews)

Next Milestone 20

Total Progress 40%

10+ 20+

18,403

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 6 more installs to reach 20+

Rank Changes

Current #31,665

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

5.0

1 reviews

Overall 100%

1 (100%)

0 (0%)

Track This Plugin

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

Start Tracking Free

Plugin Details

Version: 1.8.5
Last Updated: Sep 22, 2026
Requires WP: 5.8+
Tested Up To: 7.1.1
PHP Version: 7.4 or higher
Author: Gunjan Jaswal

Support & Rating

Rating: ★ ★ ★ ★ ★ 5
Reviews: 1
Support Threads: 0
Resolved: 0%

Keywords

cloudflare deploy seo sitemap 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,758

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

30K+ installs

#1,008

Yoast SEO - Advanced SEO with real-time guidance and built-in AI

10M+ installs

$Rank Math SEO – AI SEO Tools to Dominate SEO Rankings$

Rank Math SEO – AI SEO Tools to Dominate SEO Rankings

4M+ installs

#13

All in One SEO – AI SEO Plugin to Boost SEO Rankings & Traffic (Schema, Local SEO, Sitemap & SEO Insights)

MC4WP: Mailchimp for WordPress

1M+ installs

#34

Hostinger Reach – AI-Powered Email Marketing for WordPress

1M+ installs

#44

XML Sitemap Generator for Google

View all Seo-and-marketing plugins

Frequently Asked Questions

Common questions about StaticForge for Cloudflare Pages

Yes. Direct Upload deployments don't consume build minutes. There's a soft cap of about 100 deployments per day per project — the plugin's debounce setting (default 120 seconds) keeps you well under that for normal editorial workflows.

No — two-tier dedup is built in. General SEO plugins (handle everything: meta + og + schema) — when any of these is detected, ALL our injection is skipped: Yoast SEO (free or Premium), Rank Math, All in One SEO Pack (v4+ and legacy), SEOPress, The SEO Framework, Slim SEO, Squirrly, SmartCrawl, WP Meta SEO. Schema-only plugins (handle only JSON-LD) — when any of these is detected, ONLY our JSON-LD is skipped, but our meta description, robots, canonical, Open Graph, and Twitter Card tags still emit so you don't lose social previews: Schema & Structured Data for WP & AMP (saswp by Magazine3), Schema Pro, WPSSO Core, Schema (by Hesham), Schema App, Magazine3 Schema variants. Niche plugin not in either list? Extend detection via the sforge_seo_competing_plugin filter (general) or sforge_schema_competing_plugin filter (schema-only), or simply untick the "Inject SEO meta" setting.

If the plugin can reach sitemap.xml, sitemap_index.xml, or wp-sitemap.xml on your origin, it mirrors that as-is (including all child sitemaps for sitemap-index files). If none are reachable, the plugin generates sitemap.xml itself from the Sitemap Generator settings (StaticForge for Cloudflare Pages → Settings → Sitemap Generator): Post Types — multi-checkbox of public post types. Default: post + page. Include Homepage — adds the front page and posts page (if separate). Include Taxonomy archives — all public taxonomy term archives. Include Author archives — authors with at least one published post. Split into multiple files — off (single sitemap.xml) or on (a <sitemapindex> referencing per-type sub-sitemaps such as sitemap-post.xml, sitemap-page.xml, sitemap-authors.xml, sitemap-taxonomy-category.xml). Sitemap inclusion is independent of Export Scope, so you can export a CPT without listing it in the sitemap and vice versa. Filter sforge_sitemap_groups exposes the grouped URL list for custom modification. The activity log shows which path was taken: Sitemap mirrored from origin: ... vs Sitemap generated locally (single mode|split mode): N URLs ....

By default the plugin keeps /wp-content/* URLs (theme CSS/JS, plugin assets, uploads) pointing at the WordPress origin so those assets keep working without bundling multi-gigabyte folders in every deploy. Structured data (og:image, JSON-LD image/logo/thumbnailUrl) and <img src> will therefore reference your dashboard host on the deployed site. To make every URL on the deployed site reference the live host, you need a proxy on the live host that forwards /wp-content/* requests back to the WordPress dashboard, and then tick Export Scope → Rewrite /wp-content/ URLs in the plugin settings. Cloudflare Worker (recommended). Create a Worker (Workers & Pages → Create application → Workers → Hello World) with this code: export default { async fetch(request) { const url = new URL(request.url); if (url.pathname.startsWith('/wp-content/')) { url.hostname = 'dashboard.example.com'; return fetch(url, request); } return fetch(request); } }; Replace dashboard.example.com with your actual dashboard host. Deploy, then add routes example.com/wp-content/* and www.example.com/wp-content/* under the Worker's Triggers tab. Nginx / Apache reverse proxy. On the live host: Nginx location /wp-content/ { proxy_pass https://dashboard.example.com; proxy_set_header Host dashboard.example.com; proxy_ssl_server_name on; } Verify with curl -I https://example.com/wp-content/uploads/some-file.jpg — it should return HTTP 200 with the image content-type. Only then tick the Rewrite /wp-content/ URLs setting and Rebuild + Deploy Now. If the toggle is on but no proxy is set up, every image, theme stylesheet, and plugin script on the deployed site will return 404. The full step-by-step is also available inside the plugin: StaticForge for Cloudflare Pages → Setup Guide → Clean /wp-content/ URLs (advanced).

Shared-hosting servers (HostArmada, SiteGround, GoDaddy, etc.) often block traffic from Cloudflare Workers / proxy IPs. Symptoms: the proxy approach above returns 522 or 520 for /wp-content/uploads/*, while a direct browser request to dashboard.example.com works fine. You usually cannot whitelist Cloudflare's edge IPs on shared hosting. Solution: tick Export Scope → Bundle /wp-content/uploads/ into deploy (leave Rewrite /wp-content/ URLs off). The plugin then: Scans every rendered page for /wp-content/uploads/... references (<img src>, srcset, og:image, JSON-LD image/logo/thumbnailUrl, inline CSS url(), oEmbed thumbnails). Fetches each unique file from your origin during rebuild. Uploads them into the Cloudflare Pages deploy at their original /wp-content/uploads/... paths. Rewrites image URLs in HTML/JSON-LD to the live host so the static site is fully self-contained. Theme CSS/JS and plugin assets still load from the origin (those rarely cause shared-hosting firewall issues). Cost scales with what's actually referenced — only files used by exported pages get bundled, not the entire media library. Cloudflare's check-missing API deduplicates unchanged files between deploys so subsequent rebuilds only upload new images. Verify after deploy: curl -I https://example.com/wp-content/uploads/<any-image>.jpg should return HTTP 200 with Server: cloudflare (served by CF Pages, not your origin).

The plugin scans your post for any of: Yoast FAQ blocks, Rank Math FAQ blocks, SEOPress FAQ blocks, OR native HTML5 <details><summary>Question</summary>Answer</details> markup. If found, a FAQPage schema with Question / Answer items is emitted.

The plugin scans your post for: Yoast HowTo blocks, Rank Math HowTo blocks. As a fallback, posts whose title starts with "How to" / "How To" and that contain an ordered list (<ol>) with 3 or more items are also recognised — each list item becomes a HowToStep.

Yes — the schemas follow schema.org spec with proper @id linking between Article ↔ Author ↔ Organization, mainEntity linking on ProfilePage, BreadcrumbList with position indexing, and EntryPoint for the homepage SearchAction. Validate with Google's Rich Results Test or schema.org Validator.

A Person node (display name, URL, bio from user description, avatar 256×256 ImageObject, sameAs array of social URLs from user_url + Twitter/Facebook/LinkedIn/Instagram/YouTube/GitHub user meta) plus a ProfilePage node that links to the Person via mainEntity. Both inside a single @graph so search engines see them as a unit.

No. The plugin keeps URLs under /wp-content/* pointing at your WordPress origin host. This avoids re-uploading gigabytes of media on every deploy. Make sure your origin is reachable over HTTPS.