很多人找 kadence 教學,blocksy pro,blocksy child,woodmart theme,woodmart tutorial,blocksy content blocks,其实不是想看一堆参数介绍,而是想解决一个很具体的问题:主题装好了,下一步到底该配置什么?哪些内容放主题后台,哪些内容用内容块,哪些修改必须进子主题,商城站又该不该直接用 WoodMart?
这篇教程按“新站上线前”的真实顺序来写。你可以把它当作一份检查清单:先选对主题使用方式,再配置全局样式、页眉页脚、内容块、子主题代码和 WooCommerce 商店页。它不追求把每个按钮都讲一遍,而是帮你少走返工路。

第一步:先判断你的网站属于哪一类,不要只看演示站
主题选择最容易被演示站带偏。演示站首页漂亮,不代表你的内容页、商品页、移动端菜单和结账流程就一定好维护。Kadence、Blocksy Pro、WoodMart 都是成熟主题,但它们的重点不同。
- Kadence:适合内容站、企业站、服务落地页。它的优势是轻量、上手快、全局样式清楚。
- Blocksy Pro:适合需要条件显示和复用模块的网站,尤其是经常要在不同分类、文章类型、用户状态下显示不同内容。
- WoodMart:更偏 WooCommerce 商城,重点是商品归档、筛选器、促销、购物车抽屉、商品页转化。
如果你是教程站,先把文章模板、目录、内链、相关文章和移动端阅读体验做好;如果你是商城,先把商品页、分类页、筛选器、结账流程做好。首页装修可以后置,因为用户从 Google 进入网站时,很多时候看到的并不是首页。
第二步:Kadence 教学的核心,是先搭全局骨架
Kadence 的正确打开方式不是不停导入模板,而是先建立统一骨架。进入后台后,建议先完成颜色、字体、按钮、容器宽度、页眉、页脚、文章页布局这几项。这样后面新增页面时,不需要每页都单独修样式。
- 在自定义器里设置品牌色和基础字体,不要每个区块手动换颜色。
- 确定内容容器宽度,内容站通常不要做得太宽,否则中文阅读会累。
- 页眉先做简单:Logo、主菜单、搜索或按钮,不要堆太多图标。
- 文章页检查标题、特色图、目录、正文间距和相关文章。
- 移动端单独看一遍菜单、按钮大小和首屏高度。
很多“看起来不高级”的网站,反而 SEO 表现稳定,因为它们的阅读路径清楚、速度快、内容页一致。Kadence 新手先把这些基础做稳,比花一天调动画更有价值。
第三步:Blocksy Pro 最值得用的是 Content Blocks
Blocksy Content Blocks 可以理解成“可复用的条件内容模块”。你可以把一段提示、一个按钮、一组链接、一个活动横幅,插入到文章底部、页眉下方、商品页说明区或指定分类页面。它的价值不在于炫,而在于集中管理。

适合用 Content Blocks 的场景
- 主题教程分类文章底部,统一放“继续阅读”或“建站检查清单”。
- WooCommerce 商品页统一显示发货、售后、授权说明。
- 只在某个分类显示活动横幅,而不是全站打扰用户。
- 未登录用户显示注册提示,登录用户显示会员入口。
- 节日活动结束后,一次关闭所有相关横幅。
实操步骤:创建一个文章底部引导块
- 进入 WordPress 后台,确认 Blocksy Companion 和 Pro 授权已启用。
- 打开 Content Blocks,新建一个模块,后台标题建议写清楚,例如“主题教程文章底部引导”。
- 类型选择 Hook,位置先选文章内容之后,不要一开始就插入复杂区域。
- 用 Gutenberg 写内容:一段说明、两三个相关链接、一个按钮即可。
- 设置 Display Conditions:只显示在文章页,或只显示在 WordPress 主题、WP主题装修等相关分类。
- 保存后打开无痕窗口检查,确认未登录访客也能正常看到。
注意,Content Blocks 不是关键词堆放工具。它应该服务用户下一步操作。例如用户读完 WoodMart 教程后,继续看筛选器、性能优化或结账流程文章,这就是自然内链;如果每篇文章底部都塞十几个无关链接,体验和 SEO 都会变差。
如果你想看更细的 Content Blocks 思路,可以延伸阅读站内这篇:Blocksy Pro Content Blocks 使用教程The
第四步:blocksy child 什么时候才需要?
很多新手一安装 Blocksy 就急着建 blocksy child,但子主题不是万能保险箱。主题后台能完成的内容,优先放后台;Content Blocks 能解决的复用内容,优先用内容块;只有代码级、长期维护的修改,才适合放进子主题。
判断标准很简单:如果是文字、按钮、图片、短代码,用后台或 Content Blocks;如果是 PHP 函数、模板覆盖、项目级 CSS/JS,再考虑 child theme。
适合放进子主题的内容包括:functions.php 自定义函数、WooCommerce Hook 调整、模板覆盖、项目专用 JS/CSS、需要 Git 管理的代码。不要把临时测试代码、复制来的未知片段长期堆在子主题里,否则后期排错会很痛苦。
第五步:WoodMart 主题要围绕成交路径配置
If you use the woodmart theme,思路要从“页面好不好看”切到“用户能不能顺利买”。WoodMart 的强项是 WooCommerce 场景,不要只盯着首页 Slider,而忽略商品归档、筛选、商品详情和结账。

- 先配置 WooCommerce 基础:币种、配送、税费、支付、邮件通知。
- 再配置 WoodMart 分类页:每行商品数、侧边栏、移动端筛选入口、排序方式。
- 检查商品卡片:价格、评分、促销标签、变体色块是否清楚。
- 检查商品页:主图比例、加入购物车按钮、库存提示、配送售后说明。
- 购物车和结账页保持克制,尽量不要放弹窗、大横幅和无关动画。
WoodMart 分类页筛选器可以继续参考:WoodMart 分类页产品筛选器教程。如果商品多,筛选器和移动端体验往往比首页更影响转化。
第六步:上线前做一次主题巡检
主题配置完成后,不要马上开始投放或大量发文章。先做一次上线巡检,尤其是使用 Content Blocks、子主题代码和 WooCommerce 模块的网站。很多问题不是编辑后台能看到的,而是在未登录访客、移动端、缓存环境下才暴露。
- 前台是否只有一个 H1,正文标题是否从 H2 开始。
- 特色图和正文图片是否有贴题 alt,至少两张图能帮助用户理解配置流程。
- Content Blocks 是否只出现在需要的位置,购物车、结账页是否已排除无关横幅。
- 子主题代码是否有注释,是否能在关闭缓存后正常工作。
- 移动端菜单、筛选器、按钮、通知条是否遮挡正文或购买按钮。
- 清理缓存后用无痕窗口检查一次,再用手机网络打开一次。
内链也要在这个阶段顺手补好。主题类文章可以自然链接到 WordPress Themes,WP Theme Decoration 这类分类页,也可以链接到真正相关的 WoodMart、Blocksy、性能优化文章。内链的目的不是堆数量,而是让用户继续解决问题。
common problems
Kadence 和 Blocksy Pro 哪个更适合新手?
如果你主要做内容站和企业展示,Kadence 更容易快速搭好骨架;如果你经常要按分类、页面类型、用户状态显示不同模块,Blocksy Pro 更灵活。新手不要只看演示站,要看后期维护是否轻松。
Blocksy Content Blocks 会影响速度吗?
简单文本、按钮和少量图片影响很小。真正容易拖慢速度的是大图、视频、第三方脚本、表单、轮播和过多字体。如果内容块里嵌入外部脚本,要单独测试。
WoodMart 用户能用 blocksy child 吗?
不能混用。WoodMart 有自己的子主题体系,使用 WoodMart 就创建 WoodMart child theme;Blocksy child 只服务 Blocksy。不同主题的模板结构和 Hook 不一样,混用只会增加风险。
总结:主题教程的重点不是功能多,而是可维护
Kadence 适合先搭轻量骨架,Blocksy Pro 适合用 Content Blocks 管理条件内容,blocksy child 适合保存长期代码修改,WoodMart 则要围绕 WooCommerce 成交路径配置。把这四件事分清楚,主题使用就会稳定很多。
如果你正在搭新站,建议按本文 6 步走一遍:判断站点类型、配置全局骨架、设置内容块、决定是否需要子主题、优化商城路径、上线前巡检。先把维护逻辑做清楚,再追求视觉细节,后面发内容、做 SEO、改活动页都会轻松得多。
Link to this article:https://www.361sale.com/en/88133/The article is copyrighted and must be reproduced with attribution.




















March 11, 13:490
Now definitely still do SEO, just play changed. Previously rely on heaps of content, heaps of keywords can have traffic, and now pay more attention to the quality of content + brand trust + user experience. In addition to relying solely on SEO is actually more and more difficult, a lot of good basically SEO + social media + content marketing + private domain conversion to do together. SEO is still a long-term customer acquisition channel, but can no longer be taken as the only channel.Hehe is working.
March 11, 10:540
Normal, included only on behalf of Google to see the page, does not mean that the ranking immediately, "has been included but not ranked" usually because: Keyword competition, page weight is low, the content is not strong enough, the page is relatively new. Continue to optimize the long-tail keywords, content quality and internal chain, usually takes a little time, the ranking will slowly come out!Amelia Foster March 6, 16:200
Do you have a screenshot?lit. even a son who is not a fish knows the joy of fish March 6, 09:230
Don't pile on the optimization plugins first, locate the bottlenecks first: Use Query Monitor to see slow SQL, slow hooks. Pause all plugins for comparison, then turn them on one by one. Check autoload is too big (options table). Check database indexes with large table queries. Tackle host/database performance first if server TTFB is high.Hehe is working.
March 3, 16:470
Hi Windjammer, there's really no need to mess with complicated local environments, regular people follow these steps and the update basically won't crash the site 👇 First, backup the whole site, files + database are prepared, this is the bottom line, out of the problem can be a key to go back. Don't change the whole thing in one click, change it in batches, change the unimportant plug-ins first, and then change the core ones. Immediately after the update, clear the cache, go to the foreground to check the home page, article page, buttons, forms, these key positions. It is best to install a plug-in that supports version rollback, in case of a crash, cut back to the old version in a second. To summarize: backup first, change in batches, check after changing, leave a way back, stable ✅😎 Hope this helps!bugbang March 2, 09:550
Usually it's not that the payment didn't work, but that the callback (webhook) didn't write back the order status. Troubleshooting steps: WooCommerce → Status → Logs: see if the payment gateway has webhook error / signature error / timeout Check if the site is blocked by WAF (Cloudflare, Pagoda Firewall, security plugins) Check if "Cache checkout pages/interface paths" is enabled (checkout pages and callback interfaces should not be cached) Look at the server error logs for 500/fatal errors that interrupt the callback execution. Solution: Release wp-json, wc-api, payment gateway callback URLs (configure as per gateway documentation) Disable cache and JS merge compression test on checkout page once If using Cloudflare: set no-challenge, no-block rules for callback URLsUlla Nala Zhenhuan (18嬛嬛嬛) January 31st, 09:360
1) Determine whether it is "Normal Waiting" or "Abnormally Stuck". You can first look at 3 signals: whether the page release time is within 7-14 days, whether there are only a small number of pages with this status, and whether the page has appeared in the XML Sitemap. If all three are satisfied, most likely belong to the normal crawling and evaluation stage, do not need to do it immediately. 2) Under what circumstances is it useless to "wait"? The following cases will not be solved automatically by time: the page has almost no internal links (isolated page), the content is highly similar to the existing pages on the site, canonical points to other URLs, and too many similar articles are published on the same topic for a short period of time. In this case, Google has been crawled, but judged that "it is not worth entering the index". 3) The most effective way of manual intervention (no tossing) Prioritize these 3 things: add internal links, link to the page from related old articles or columns, and enhance the density of information on the first screen. The first 2-3 paragraphs directly answer the user's question, avoid too much padding, confirm canonical as self-referential, avoid being judged as a duplicate page, and then go to GSC to request reindexing after doing so. 4) What "intervention actions" are counterproductive? It is not recommended: frequent deletion and re-posting, clicking "request to index" several times in a row, forcing keywords to be stacked for the sake of indexing, changing URLs or titles arbitrarily. These operations will allow Google to reassess the stability of the page, but slow down the inclusion. 5) a practical judgment standard If an article: has been crawled, there is no noindex / robots problem, there are at least 1-2 related internal links, the content obviously solves an independent problem, then it is included, just a matter of time, not a plug-in problem.Post Porter January 30th 10:000
The new station does not do external links can be completely, the first content and station structure to do a good job more stable. Only rely on the content can generally get included and part of the long-tail word rankings, but the amount of high competition will be slow. It is recommended to wait for the site stable inclusion, 30-50 quality content, keywords began to enter the top 20/30, and then a small amount of external links, priority brand words/naked chain/citation type, do not come up to chase the number. 👍