HTML Page Publisher

Yes. Zip the exported folder — index.html at the top level (or inside a single folder), assets in subfolders — and upload the .zip instead of an .html file. Files keep their relative paths, so css/site.css and img/hero.png references work unchanged. Executable files (.php etc.), anything outside the allowed types, and any file containing PHP code are skipped and reported. ZIP import needs PHP's ZipArchive extension, which nearly every host provides; if yours does not, upload the HTML and its files separately.

Tick Save as draft when uploading a new page, or switch a page to Draft in its Page Settings. Drafts return a 404 to visitors and search engines; administrators can view them, and the Preview button gives you a link with a secret token you can share with anyone (use Reset preview link to revoke it). Publish from Page Settings when you are happy.

Yes. In a page's settings, set Custom path to promo to serve it at https://example.com/promo/, or to / to make it the front page. If you later change the path, the old one redirects to the page. Paths that belong to existing WordPress pages or posts, core routes, category/tag/author bases and post-type archives are refused; other rewrite rules (e.g. from other plugins) are not checked, so choose a path you know is free. The front page keeps working for WordPress's own query-string routes (search, previews, REST, feeds).

HTML Pages → Settings → Global snippets. Paste the tags into the head or footer snippet; they are inserted into every published page when it is served (so re-uploading a page never loses them). Pages can opt out individually.

Published pages that are not marked noindex are listed at /wp-sitemap-htmlpp-1.xml, which is linked from WordPress's built-in sitemap index. SEO plugins such as Yoast or Rank Math replace the core sitemap with their own; in that case use the htmlpp_sitemap_entries filter (or HTMLPP_Sitemap::entries()) to feed their sitemap.

Yes. The plugin exposes a REST API at /wp-json/htmlpp/v1 (list, create/replace from an HTML file or ZIP, update HTML or settings, rename, duplicate, files, versions, preview links). Authenticate with an application password (Users → Profile → Application Passwords) for an administrator: curl -u "admin:xxxx xxxx xxxx xxxx" -F slug=spring-promo -F file=@index.html https://example.com/wp-json/htmlpp/v1/pages With shell access, wp htmlpp publish spring-promo ./site.zip --overwrite does the same. The GitHub repository ships a Claude Code skill (skills/publish-to-wordpress) so Claude can publish a page it just generated.

Any tool that gives you a single, self-contained HTML file. Claude Design's "Export as standalone HTML" is supported directly, including automatic removal of the runtime wrappers it injects. Pages from ChatGPT, Gemini, or written by hand work as-is. Tools such as v0 and Bolt export React/Vite projects rather than static HTML, so you need to build or export those to plain HTML first.

In wp-content/uploads/html-page-publisher/<slug>/. Each page has its own directory containing an index.html and an assets/ folder for images. Version-history snapshots are kept separately in wp-content/uploads/html-page-publisher-backups/<slug>/. Both folders contain an .htaccess that denies direct access, so pages are only reachable at their public URL.

nginx ignores .htaccess. Pages still work at their public URL, but the raw files could also be fetched from the uploads folder. HTML Pages → Settings shows whether direct access is blocked and gives you a ready-made location block to add to your nginx server configuration. The same applies to Apache or LiteSpeed configured with AllowOverride None.

Open HTML Pages, click Edit on a page. You get the native WordPress code editor for the HTML, a Version History panel to restore earlier saves, and a Files & Assets panel to add, replace, or delete the page's images, CSS, JS, fonts and other files without re-uploading the HTML. Use Replace (rather than uploading a new file) to swap a file while keeping the same name, so existing references in your HTML keep working.

The upload is refused with a message explaining why, unless you tick Replace the existing page. With the box ticked the new HTML replaces the live page and the previous version is saved to the page's version history. Automated workflows can allow overwrites with the htmlpp_allow_overwrite filter.

Yes. The standard DISALLOW_FILE_EDIT (or DISALLOW_FILE_MODS) constant in wp-config.php disables in-dashboard HTML editing, file changes, renaming and replacing existing pages, the same way it disables WordPress's core file editor. Uploading new pages, duplicating and deleting remain available.

Two steps:

1. DNS: Add an A or CNAME record pointing your subdomain (e.g. sales.yourdomain.com) at the same server as your WordPress site.
2. Web server: Configure your hosting to serve that subdomain from the same WordPress install. On shared hosting with cPanel this is typically an "addon domain" or "subdomain" option. On managed hosts, you may need to request it from support.

Only users with the manage_options capability (administrators by default) can upload pages. Uploaded HTML is served as-is, including any <script> tags it contains, so only upload HTML you trust.

No. Uninstalling removes the plugin's settings but leaves the uploaded pages in wp-content/uploads/html-page-publisher/ (and their version-history snapshots in wp-content/uploads/html-page-publisher-backups/) intact, together with their metadata (draft status, custom paths, redirects) so a reinstall does not publish former drafts. Delete those folders and the htmlpp_pages, htmlpp_redirects and htmlpp_path_redirects options manually if you want everything gone.

Yes. Pages are served before WordPress's main query runs, with ETag and Last-Modified headers; conditional requests get a 304 Not Modified and HEAD requests are supported. The page HTML is sent with max-age=0, must-revalidate so edits show immediately; assets get one hour. To let a CDN cache the HTML itself, use the htmlpp_cache_max_age filter: add_filter( 'htmlpp_cache_max_age', function ( $seconds, $file, $ext, $is_page ) { return $is_page ? 600 : $seconds; }, 10, 4 );

Yes. Rules are a named array of PCRE pattern/replacement pairs: add_filter( 'htmlpp_sanitizer_rules', function ( $rules, $slug, $context ) { $rules['my-tool-banner'] = array( 'pattern' => '/<div class="made-with">.*?<\/div>/is', 'replacement' => '' ); return $rules; }, 10, 3 ); You can also unset() a built-in rule by its key (for example claude-design-cfasync-script) if it interferes with your markup.