1.4.0 doesn't introduce breaking changes to your theme code or content — it's a SEO- and content-tooling release. Here's the practical checklist for confirming everything it added is actually working on your site after you update.
Unlike some jekcms releases, 1.4.0 doesn't touch your theme's function signatures, your database schema in a way that requires manual intervention, or your existing content. It's additive: SEO/schema standardization, automatic breadcrumbs, an automatic table of contents, a rebuilt Content Optimizer, and a Turkish slug fix. The update itself is a one-click pull from Version Manager. This post is the practical checklist for confirming everything landed correctly on your specific site.
Verify Breadcrumbs Are Rendering
Open a category or tag archive page and a single post, and confirm the breadcrumb trail appears where your theme expects it. Then check the page's structured data with Google's Rich Results Test to confirm the BreadcrumbList schema validates — a custom or heavily modified theme is the most likely place for this to need a manual template adjustment if your theme doesn't call the standard breadcrumb output function.
Confirm the Table of Contents Appears on Long Posts
The TOC only generates when a post has enough <h2>/<h3> headings to be worth one. Open a few of your longer posts and confirm it's rendering where your theme places it — sidebar or inline, depending on the theme. If a post uses <h4> or deeper for its structure instead of <h2>/<h3>, it won't be picked up; that's a content-authoring detail worth knowing rather than a bug.
Check the Content Optimizer's Language Setting
The Content Optimizer now uses your site's ai_content_language setting to pick between the Turkish and English synonym dictionaries automatically. If your site publishes in a language other than what that setting currently reflects, correct it in Settings › General before relying on the optimizer — otherwise it'll be checking suggestions against the wrong dictionary.
Run fix-slugs.php If You Publish in Turkish
This is the one step we'd actually call mandatory rather than optional. If your site has ever generated slugs from Turkish titles before this release, some of them may contain stray hyphens or dropped characters from the transliteration bug this version fixes. Run the fix-slugs.php utility once after upgrading — it repairs affected slugs in place without touching post content, and it's safe to run even if nothing needs fixing.
Re-check Your Site Name in Search Results
If your site's name has ever shown up blank or as your domain instead of your configured site name in Google search results or in shared-link previews, that was likely the og:site_name/WebSite schema bug this release fixes. Give Google a few days to recrawl after upgrading, then check how your site name appears in a fresh search.
What You Don't Need to Do
You don't need to update theme code, run a database migration script, or remap any custom fields — none of 1.4.0's changes require it. If you're on a heavily customized theme that overrides the default header/footer templates, it's worth a quick visual check that breadcrumbs and the TOC integrate cleanly, but that's a review, not a required code change.
Sources and verification
Verify release and technical details with these primary sources.
