“I want to display a clean LP (HTML/CSS/JS) made with AI in WordPress without it falling apart.”
But in practice, you often run into walls like:theme CSS and headers/footers get mixed in and break the layout/code gets broken in the block editor/external JS interferes…and similar problems.
So in this article, I’ll organize options with similar ideas and use cases—including Raw HTML Pages (No Theme Wrapper)which I sell—by use case, and then give you a comparison table that makes everything clear at a glance.First, the conclusion: your choice depends on what you prioritize
“I don’t want the theme to be applied at all”
- (don’t mix, don’t break, swap as quickly as possible)Direct HTML output on a dedicated URL
→ is the best fit (that’s your snippet here)“It’s okay to use the theme, but I want to remove only the header/footer” - (use it like an LP template)Blank template (no header/footer) style
→ “I want to embed HTML into part of an existing page” - Custom HTML blocks / snippet injection style
→ Comparison table (what it can and can’t do)
1) My snippet: Raw HTML Pages (No Theme Wrapper) (the star of this article)
| 方式/ツール | テーマ完全バイパス | 専用URL発行 | HTML保管のしやすさ | 下書き共有 | noindex標準 | 主な弱点 |
|---|---|---|---|---|---|---|
| 僕のスニペット:Raw HTML Pages (No Theme Wrapper) | ◎ | ◎(/raw/{slug}) | ◎(管理画面で作成/一覧) | ◎(トークン) | ◎ | “生HTML”運用前提(WPの装飾やブロック機能は使わない) |
| WP Custom HTML Page(s) | ○(HTMLを直接出す思想) | ◎(URL指定系) | ○ | △ | △ | 更新状況/対応WPバージョンは要確認(テスト対象が古い表記あり) WordPress.org |
| WIT Custom Output (WITCO) | ○(直出し思想に近い) | ○ | ○ | △ | △ | “開発/テスト段階”表記あり。配布形態や保守状況は要確認 wit.rs |
| Blank Slate(空テンプレ) | ×(テーマは動く) | △(固定ページURL) | ◎ | △ | △ | テーマCSS/プラグイン影響は残る(「完全に混ざらない」ではない) WordPress.org |
| WPCode(スニペット管理) | × | × | ◎(挿入管理が強い) | × | × | “ページを生HTMLとして直出し”用途とは別物(挿入用途) WordPress.org |
| カスタムHTMLブロック | × | × | △ | × | × | ブロックの中に別ブロックは入れられない/用途が限定されがち Stack Overflow |
My snippet has a very clear philosophy:
it completely bypasses the theme
- and outputs the saved HTML as-is at a dedicated URL (for example:
- )
/raw/{slug}It also handles the annoying operational details (noindex / sharing / nocache, etc.) all in one place - …and that “quietly helpful in real production work” all-in-one design is its strength.
This LP itself is a “working demo”
Example URL:
https://bright-ms.net/raw/raw-html-url-snippetIf you’re placing it inside the LP, to avoid breaking the design, put it either
right after “Features”or just before the “Specifications and Limitations” section(that links the “proof” and the “understanding” naturally).Here’s copy you can paste as-is:
✅
This page is displayed with this snippetThis LP
is displayed by directly outputting only the saved “raw HTML” via a dedicated URL for/raw/without passing through the WordPress theme at allThe LP code was generated by
Google Geminiand all you have to do is paste it into the snippet editor and update itIt avoids the theme CSS/header/footer effects that tend to get mixed in with normal pages or custom HTML embeds, so you can publish with the exact intended design. 。
2) WP Custom HTML Page(s): similar, but a “check before adopting” option
A plugin with a similar approach—creating HTML in the admin screen and outputting it at any URL—is
WP Custom HTML Page(s) .However, the publicly available information shows an older
supported/tested WP versionnotation, so if you’re considering it now, it’s safer to check the “last updated” date, forum activity, and whether it works on your live site. WordPress.org3) WIT Custom Output (WITCO): similar philosophy, but choose based on distribution/maintenance status
WITCO follows a direction where you can output not just HTML but also CSS/JS/JSON, making it quite close to your raw output philosophy.
On the other hand, the official page gives a
test-phasefeel, so whether you should adopt it often comes down to its current distribution format and update frequency. wit.rs4) Blank Slate: a practical LP solution, but not a complete bypass
Blank Slate provides a page template without a header/footer, which is convenient for LP operations.
However, this is **a method that keeps the theme active while making the layout “blank”**, so it is different from the
“nothing gets mixed in” guaranteethat your snippet aims for. WordPress.org5) WPCode / Custom HTML block: a different use case (for embedding)
WPCode
- is geared toward inserting snippets into a site, so it belongs to a different category from directly outputting raw HTML at a dedicated URL . WordPress.orgThe Custom HTML block
- is handy, but an HTML block is not a “container for blocks,” so its flexibility for layout integration is limited. Stack OverflowSo which should you choose?
“I absolutely don’t want it mixed with the theme” / “I want to reuse AI-made LPs as-is”
→ **My snippet (Raw HTML Pages / No Theme Wrapper)** is the most straightforward choice.
“I’m okay with theme-based operation, and I just want to remove the header/footer like an LP template”
Blank Slate
→ and other blank-template style options. WordPress.org“I want to embed HTML in the middle of an existing article”
→ Custom HTML block / snippet injection style (but mixing is part of the deal).
Stack OverflowReference links and sources
My sales page
- (feature description for Raw HTML Pages / No Theme Wrapper)WP Custom HTML Page(s) (official listing page)
- WordPress.orgWIT Custom Output (WITCO) (official page)
- wit.rsBlank Slate (WordPress.org plugin page)
- WordPress.orgWPCode (listed in the WordPress.org plugin directory)
- WordPress.orgLimitations of the HTML block (reference)
- Stack Overflow
Conversation
Be the First Voice
この場所に、最初の感想や気づきをそっと残せます。