| 开发者 | nokazehayato |
|---|---|
| 更新时间 | 2026年7月13日 09:11 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
functions.php snippet to make the setting permanent. Deactivate or remove the plugin without losing your configuration.
Test Posts
Generate flagged test posts in one click. Each post is marked internally, so you can delete all test content before launch with zero risk of touching real posts.
WordPress Pre-Launch Checklist
A checklist that actually does the work. Before handing off the site, the Pre-Launch tab handles everything in one screen:
functions.php snippet to keep your Hide Blocks settings after deactivating or removing the plugin/wp-content/plugins/noshi-kanamerHead to Tools > Noshi-Kanamer in your WordPress admin. If you're starting a new build, head to Pre-Launch when you're ready to run through the handoff checklist. If you're taking over an existing site, start with Site Check to see which installed plugins need attention. If you want to hide blocks from your client's editor, go to the Hide Blocks tab.
No. Noshi-Kanamer marks each test post with a hidden flag. Only flagged posts are deleted — your real content is never touched.
It applies globally to all users on the site, using the allowed_block_types_all filter.
Use the Pre-Launch tab to generate a functions.php snippet beforehand. Paste it into your theme and your block visibility settings remain permanent — even without the plugin active.
The Pre-Launch tab displays a live progress card (X of Y complete) and a sticky Next Action card that always surfaces the single most important unresolved item — with a direct link to the fix for settings-based checks, and clear next-step guidance for the rest. You're never left guessing what's still outstanding.
Beyond the standard WordPress Reading Settings check, Noshi-Kanamer also inspects the wp_robots filter output and — on hosts that support server-to-server loopback requests — the actual rendered HTML <meta name="robots"> tag. This catches noindex directives injected by your theme or an SEO plugin that a Reading Settings check alone would miss.
Blocks exclusive to Full Site Editing (FSE) — such as core/template-part and query pagination blocks — cannot be rendered on standard pages or posts. All blocks usable in the standard block editor are included.
Block Showcase requires the Gutenberg block editor and is not compatible with Elementor. When Elementor is active, pages are managed through the Elementor editor, which does not support Gutenberg blocks. Other features (Hide Blocks, Test Posts, Pre-Launch Cleanup) work normally alongside Elementor.
It's purely a developer tool — designed for WordPress freelancers and agencies during the build phase. It is not intended for clients. We recommend deactivating or removing it before handing off the site.
For most WordPress setups, yes. Pre-Launch Cleanup, Hide Blocks, and Test Posts work across standard and FSE themes. Note that Block Showcase requires the Gutenberg block editor and is not compatible with Elementor-powered pages — other features work normally alongside Elementor.
Noshi-Kanamer covers the full checklist across two tabs for a clean client handoff. The Pre-Launch tab handles test content, rewrite rules, search engine indexing (noindex), WP_DEBUG, the admin email address, and four security loose ends (file editor, XML-RPC, debug.log, the default admin username) — all in one screen. The Media Manager tab finds and removes unused images before client delivery. When the "All pre-launch checks are complete!" banner appears, your site is clean and ready to hand off.
Most engineers deactivate or remove it just before handing off the site — keeping the client's dashboard clean and focused. That said, you can always reactivate it later for maintenance, post-launch adjustments, or follow-up work.
N/10 complete and a sticky Next Action card (bottom-right) so you can see exactly what's left and how to do it — no more guessing why "All checks complete" isn't appearing.wp_robots filter output and inspects the rendered HTML for <meta name="robots" content="noindex">, so theme/SEO-plugin-driven noindex directives are no longer silently missed even when the Reading setting says "indexed".