| 开发者 | nokazehayato |
|---|---|
| 更新时间 | 2026年8月3日 17:49 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
functions.php snippet during your handoff checklist and add it to your theme to keep the block visibility settings after Noshi-Kanamer is removed.
Test Posts
Generate flagged test posts in one click to fill carousels or list blocks without creating sample content by hand. Each test post is marked internally, so you can delete all generated test posts before launch without touching unflagged posts.
WordPress Pre-Launch Checklist
A checklist that actually does the work. Run a consistent pre-launch routine across your client sites from one screen:
functions.php snippet/wp-content/plugins/noshi-kanamerLook for Noshi-Kanamer in your WordPress admin sidebar. It opens with a quick welcome guide pointing you to the right tab to start with.
Yes. AI site builders and vibe-coding sessions are great at generating pages, but they do not automatically know which technical loose ends must be cleared before launch. Noshi-Kanamer runs the launch checks that are easy to omit from an AI-assisted build brief, including WP_DEBUG, noindex, debug.log, and test content, then generates a shareable report summarizing your pre-launch checks.
No. Noshi-Kanamer marks each test post with a hidden flag. Only posts carrying that flag are selected for deletion; unflagged posts are excluded.
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 surfaces the next unresolved item, with a direct link to the fix for settings-based checks and clear next-step guidance for the rest.
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 can catch noindex directives injected by your theme or an SEO plugin that a Reading Settings check alone may 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. Blocks you've hidden with Hide Blocks, or that require a specific parent block, are also excluded. Other supported blocks 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. The other tools remain available alongside Elementor, though Hide Blocks applies to Gutenberg blocks rather than Elementor widgets.
It is a developer tool for freelancers and agencies working on client WordPress sites, from project setup through handoff. 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. The other tools remain available, though Hide Blocks applies to Gutenberg blocks rather than Elementor widgets.
Noshi-Kanamer brings key WordPress handoff checks and cleanup tasks together across the Pre-Launch and Media Manager tabs. 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 images with no detected references before client delivery. When the "All pre-launch checks are complete!" banner appears, every item in the Pre-Launch tab has been cleared. You can then include the report in your handoff documentation.
We recommend deactivating or removing it just before handoff to keep the client's dashboard clean. That said, you can always reactivate it later for maintenance, post-launch adjustments, or follow-up work.
Yes. The Pre-Launch tab automatically detects whether WP_DEBUG is still enabled and provides a copy-paste fix for wp-config.php, alongside a check for a leftover debug.log file (with one-click deletion).
The Media Manager tab scans your media library and flags images with no detected references in post content, featured images, or supported ACF image and gallery fields, then lets you bulk-delete them in one pass.
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".