Integration

Static Shield + WordPress Default Themes

Coded compatibility profile Covers six built-in themes at once: Twenty Twenty-One, Twenty Twenty-Two, Twenty Twenty-Three, Twenty Twenty-Four, Twenty Twenty-Five, and Twenty Twenty-Six

WordPress's own bundled default themes get one shared compatibility profile rather than six near-identical ones, since they behave the same way: WordPress-core-team maintained, template-only, with no theme-specific AJAX, REST route, or form of their own. Twenty Twenty-One is a hybrid classic/block theme; Twenty Twenty-Two onward are pure block themes (theme.json plus block templates) — both shapes render fully server-side with no client-side hydration.

Recommended mode

Fully Static

Static behavior

Template parts and block templates render fully server-side HTML. Page content comes entirely from whatever blocks or plugins are actually placed in it — this profile covers the theme shell itself, not the content placed inside it.

Dynamic behavior

Nothing — every feature covered here is static or admin-only.

Bridges & routes

None needed — none of these six themes declares any public routes, AJAX actions, or cookies of their own.

Setup

No special setup — detected automatically whenever any of the six covered default themes is active.

Limitations

This is not yet verified against a live install. It covers the theme shell only — a site using blocks or plugins with their own dynamic behavior (a contact form block, a WooCommerce block, etc.) gets that block or plugin's own compatibility profile layered on top independently. Extending this same adapter to older defaults (Twenty Twenty, Twenty Nineteen, ...) would be a one-line change if ever needed, but isn't included here since Twenty Twenty-One is the oldest one currently covered.

Want to see this against your own site?

Static Shield Lite is free to install and inspects your actual plugins, not just what's publicly visible.

Get Static Shield