Kadence Reading Time - WordPress Plugin

Guide to Setting Up Kadence Reading Time for WordPress Posts

Kadence Reading Time is not just a decorative blog extra. It gives readers a clear signal up front: how long the article is likely to take, so they can decide whether to read it now, save it, or come back later. This guide focuses on the practical setup, not the sales pitch: where the output is enabled, how to choose a reading speed, what to do with post meta, how to use the shortcode, and how to verify the result on a real page.

The plugin is especially useful on sites with lots of long-form content: tutorials, reviews, recipes, news posts, training articles, documentation, case studies, and expert columns. At the same time, it is easy to configure it too mechanically: leave the default English label on a localized site, place the time in the wrong spot, forget about archives, or assume automatic output will work for every custom post type. Below is a practical setup sequence with no invented features and no edits to the plugin files.

We will start with preparation and installation, then move through the global settings, break down the [kt_reading_time] shortcode, build a setup pattern for a content-driven site, verify the result, and look at why reading time may fail to appear. At the end, you will find an FAQ, similar tools, and a clean download link for anyone who has already decided whether this plugin fits their site.

What problem reading-time display actually solves

A reading-time estimate works like a small promise before the reader commits to the article. Instead of seeing a vague wall of text, the visitor gets a simple cue: this is a short read, a medium read, or something that needs dedicated time. On a blog, knowledge base, or guide section, that reduces uncertainty. Readers can choose faster, and editors can set expectations more honestly.

Kadence Reading Time calculates an estimated duration based on the post content and a global words-per-minute value. The official documentation points to the settings path under Appearance -> Kadence -> Reading Time, and it describes several display options: before single-post content, inside archive excerpts, in post meta, and via shortcode. That makes the plugin a focused readability tool for content pages, not a full analytics builder.

It is important to understand the boundary here: reading time does not measure actual visitor behavior, show scroll depth, or replace engagement analytics. It is an estimated cue based on text volume and the reading speed you choose. If your site needs a progress bar, image-aware timing, advanced analytics, or read-completion tracking, you will need a different tool or an additional integration.

Where this kind of block makes the most sense

The plugin works best on pages where readers are actively judging the effort before they start. For example, on an agency blog you might show Reading Time: 7 Minutes next to the author and date, while in a knowledge base you could place the estimate before a tutorial so users know whether they can finish it right now. In media projects, the label also helps distinguish a quick note from a long deep dive.

• Tutorials and how-to articles. Readers can see how long the material will take and are less likely to abandon it because the length caught them off guard.
• Company or expert blogs. Reading time makes it easier to compare several posts in an archive and pick the right one.
• Documentation and knowledge bases. A small cue next to the headline or in the meta block makes long instructions feel less intimidating.
• Long-form analysis and feature stories. A label before the text gives an honest heads-up that the piece requires attention.

When the plugin may be unnecessary

If the site mostly consists of short news items, product cards, landing pages, or service pages, a separate reading-time indicator can add visual noise. It also does not solve much on sites where the key content lives in videos, galleries, interactive blocks, or card-based layouts that do not map cleanly to ordinary post text. In those cases, check first whether visitors are really making decisions based on text length.

Practical check: pick the 5 most important pieces of content on the site and ask whether knowing "3 minutes" or "12 minutes" would actually help the reader decide. If yes, the plugin makes sense. If not, it is better not to add another element to the post meta block.

What to check before installing it on a live site

You do not need a full audit before installation, but you should understand exactly where the reading time is supposed to appear. Kadence Reading Time is tied to post display, archives, post meta, and shortcodes, so issues usually come from expectations rather than calculation: a user enables the plugin and expects it to appear on pages, in builder cards, in a custom post type, and in every theme template at once.

Start with a test post. It should not be an empty publication or a one-line teaser, but a normal piece with several paragraphs, subheadings, and images. That makes it easier to see how the output looks before the content, whether it gets in the way of the first paragraph, and whether it sits correctly next to the author, date, or category.

Quick pre-launch checklist

• Make sure the plugin is available in your Kadence plan. The official pages indicate that Reading Time belongs to selected Kadence plans, so the site should have a legitimate ZIP source.
• Check the theme and the post-meta area. If your theme hides the post meta block or replaces the standard template with a builder layout, automatic meta output may not appear where you expect it.
• Prepare localized labels. The documented defaults are Reading Time, Minutes, and Minute. On a non-English site, it is better to replace them right away.
• Define your content types. For standard posts, use automatic output. For custom post types, plan on using the shortcode in advance.
• Clear cache after testing. If the site uses page cache, minification, or server-side cache, you may see an older version of the page after saving settings.

Also consider the site language. The plugin calculates based on words per minute, which works fine for Russian and English texts. But for languages where character count matters more than word count, the official Kadence request page includes a user request for character-based calculation. That does not mean the feature exists in the current interface. If the site is multilingual and some content is in Chinese, Japanese, Korean, or another language with a different reading model, check the result manually and do not promise mathematical precision.

Installation and first launch without unnecessary risk

The official documentation describes installation through a ZIP file: the downloaded archive should not be unpacked, and it is uploaded to WordPress from the Add Plugins screen. This guide does not cover purchasing, account access, or licensing steps, because that is about product access rather than feature setup. If you already have the file, the process is standard for WordPress.

Basic ZIP installation

1. Open the WordPress admin panel.
2. Go to Plugins -> Add New Plugin.
3. Click Upload Plugin and select the Kadence Reading Time ZIP archive.
4. Start the installation with Install Now.
5. After it finishes, click Activate Plugin.

After activation, do not jump straight to the front end. Open the plugin settings first at Appearance -> Kadence -> Reading Time. This matters because many users look under Settings, but the official documentation points specifically to the Kadence section inside Appearance.

First check after activation

Open any published post in a new tab and compare what you see with the settings. If you have not yet enabled output before content or in post meta, the plugin may be active but invisible on the public-facing site. That is normal. On first launch, the goal is not perfect placement right away. It is simply to confirm that the settings screen is available, the plugin is active, WordPress is not showing errors, and the test post opens without breaking the template.

Quick takeaway: after installation, you should be able to access the Reading Time screen under the Kadence section. If the settings do not open, first check your administrator permissions, the plugin status on the Plugins screen, and any admin-side caching issues before blaming the site template.

Core settings: reading speed, labels, and display locations

Kadence Reading Time settings are simple, but they determine whether the indicator feels natural or awkward. One field set incorrectly can create a strange result, such as Reading Time: 1 Minutes on a localized site or a "1 minute" estimate for content that obviously takes longer. The best approach is not to move through the options mechanically from top to bottom, but to follow a sequence: where it appears, how it is calculated, how it is labeled, and how it is verified.

Display before single-post content

The option to insert reading time before the content works well on sites where the theme's meta block is overloaded or hidden altogether. It is highly visible, but it can also clash with the lead paragraph, an ad block, a table of contents, or a custom builder element. Enable this if readers should see the estimate before they start reading and the first screen of the post can comfortably handle an extra line.

After saving, open the post like a normal visitor would. Check whether the block appears twice: once before the content and again in post meta. If it does, keep only one primary output method. For a clean layout, it is usually better to choose either the meta block next to the date or the line before the content, not both at the same time.

Display in archive excerpts

The documentation also describes an option to insert reading time into archive excerpts. This is useful when users are choosing between multiple articles: a blog archive, category page, author page, or content feed. If the post card already shows the date, author, category, and comments, add reading time carefully. The goal is to support decision-making, not turn the card into a crowded strip of meta data.

Check more than just the main blog page. Some themes use different templates for the primary archive, categories, and search results. If reading time appears in one place but not another, the reason may be the theme template rather than the plugin itself.

Reading speed in words per minute

The official documentation lists 250 words per minute as the default value. That is not universal truth, just a starting point. For dense technical guides, legal texts, medical content, or articles with a lot of code, you may want to lower the speed so the estimate stays conservative. For light news posts and short updates, a value close to the default is usually fine.

The principle is simple: the more demanding the material, the fewer words per minute you should assume. But do not try to force mathematical precision down to the second. The indicator should be an honest estimate, not a measuring instrument. Check 3 or 4 pieces of content with different lengths and make sure the numbers feel believable: a short note should not become "0 minutes," and a long tutorial should not look like "2 minutes."

Label, Postfix, and Postfix for singular

The label and suffix fields matter most on localized sites. The documentation shows the default values Reading Time, Minutes, and Minute. On a Russian-language site, for example, it is often better to use a short, calm phrasing such as a localized equivalent of "Reading Time" plus a neutral abbreviation for minutes. If the design allows a more conversational tone, a localized equivalent of "Read in" can work well too.

Russian introduces a practical complication here: the interface gives you a separate singular value, but not a full declension system for forms like 2, 3, 4, and 5 minutes. That is why a neutral abbreviation for minutes is often the most practical choice. It avoids awkward grammar and keeps you out of the code for a purely linguistic issue.

Insert into post meta

The Insert the Reading Time in the Post Meta option is convenient for sites using Kadence Theme and similar layouts where post meta is already presented cleanly. In that case, reading time becomes part of the familiar line next to the date, author, or category. This usually feels more natural than a separate block before the first paragraph.

But post meta depends on the theme. If the theme or a custom template hides the meta block, changes its structure, or builds the card through a page builder, the output may not appear. In that case, use the shortcode where you need it or reconsider the post template.

The [kt_reading_time] shortcode and non-standard display locations

The shortcode is the main way to show reading time where the automatic options are not a fit. The official documentation explicitly points to [kt_reading_time] for custom post types or locations not covered by the standard settings. In the block editor, you can insert it with the Shortcode block. In some builders, you can use any element that supports WordPress shortcodes.

Use the shortcode as a targeted tool, not as a universal replacement for every setting. For example, if reading time appears in post meta for standard posts, but your "Case Studies" section needs it beneath the title inside a custom template, the shortcode gives you control over that exact location without editing theme files.

Where the shortcode is especially useful

• Custom post types. If automatic output is designed around standard posts, you can add the shortcode to a template for "Case Studies," "Lessons," "Documentation," or "Reviews."
• Block templates and Kadence elements. When the layout is assembled with blocks, the shortcode is easy to place next to the title, author, or summary.
• Standalone landing pages with long-form text. If a page functions like an article but does not use the default post template, the shortcode lets you add reading time manually.
• Placement testing. You can temporarily place the shortcode in different locations and keep the version that interferes least with the design.

How to insert the shortcode in the block editor

1. Open the post or template where you want to display reading time.
2. Add a Shortcode block.
3. Insert [kt_reading_time].
4. Save or update the content.
5. Open the public page and confirm that the shortcode text has been replaced by the actual reading-time output.

If visitors see the literal text [kt_reading_time], the shortcode is not being processed. The usual reason is that it was placed in an area where WordPress does not execute shortcodes, or the block or builder is rendering it as plain text. Move it into a standard Shortcode block or check the settings of the builder element.

Light, safe styling without editing the plugin

If you are using the shortcode inside a separate block, you can style it through a wrapper class without touching Kadence Reading Time files. Create a Group block around the shortcode, assign it the additional CSS class reading-time-inline, and add CSS in your child theme or another safe location for custom theme CSS.

.reading-time-inline {
  display: inline-flex;
  align-items: center;
  gap: 0.35rem;
  padding: 0.35rem 0.65rem;
  border-radius: 6px;
  background: rgba(45, 85, 255, 0.08);
  color: inherit;
  font-size: 0.95rem;
  line-height: 1.4;
}

This change styles only your wrapper, so it is easy to roll back: remove the class from the block or delete the CSS. After adding it, open the post on both mobile and desktop. If the block breaks the meta line or wraps awkwardly, it is better to keep the theme's default output without the extra background.

Per-post adjustments for individual entries

The Kadence product page states that for a specific post, you can hide Reading Time in the meta settings or assign a custom reading time. This matters for content where the automatic calculation does not reflect the real experience. For example, a post may have a short amount of text but a long embedded video, an interactive diagram, a gallery, or a step list the user follows while reading.

Individual settings should not become your default workflow. If you find yourself changing the reading time manually on every post, the global words-per-minute value or the output location was probably chosen poorly. Manual adjustment is best reserved for exceptions: a special format, a code-heavy article, a post with an unusual structure, or content where the indicator is better hidden.

When to hide the indicator

Hiding makes sense when the reading-time value is misleading. For instance, on a page with a short introduction and a large embedded tool, a word-based calculation will show a number that is too low. Another common case is utility posts, announcements, promotions, form pages, or content where readers do not actually move through the text in a linear way.

When to assign your own value

A custom reading time is useful for complex guides where reading is tied to action. If the text itself takes 6 minutes, but real users will also be opening WordPress settings, saving changes, and checking the page as they go, a longer estimate is more honest. The key is not to turn this into a marketing trick. The value should help readers plan their time, not artificially make the article seem more substantial.

Editorial rule: change the reading time manually only when you can explain the reason in one sentence. If you cannot, keep the automatic calculation.

Practical scenario: show reading time in the blog and archive

Let us walk through a typical setup for a blog-based site: you want reading time to appear on single posts and in the category feed, without overloading the first screen. This works well for content sites, agency blogs, media projects, and knowledge bases where posts vary in length.

Goal

Display a clean reading-time label next to the main content and inside archive cards so readers can understand the scope of the material before clicking through or right at the start of reading. For a localized audience, the label should feel natural - not a mismatched default string, but wording that fits the language of the site.

Preparation

• The site has at least 3 published posts with different lengths.
• The theme displays single posts and the category archive correctly.
• Kadence Reading Time is installed and active.
• You have administrator permissions to save settings.

Setup steps

1. Go to Appearance -> Kadence -> Reading Time.
2. Enable either display before single-post content or display in post meta. Do not enable both at once unless the design has been checked.
3. Enable display for archive excerpts if post cards should show the time before the reader clicks through.
4. Leave Words Per Minute at the starting value of 250 or lower it for more demanding tutorial content.
5. Replace Label with a localized equivalent of "Reading Time" or "Read in."
6. For Postfix, use a grammatically stable localized form for "minutes" if your language needs it.
7. Save the changes with Save Changes.

Verifying the result

Open a single post as a visitor. Check four things: the block is visible, the label matches the site language, the indicator is not duplicated, and the spacing looks normal next to nearby elements. Then open the category archive and make sure the cards have not become too noisy. If the time appears only on the single post and not in the archive, verify that the excerpt setting is enabled and that the theme uses the standard archive output.

After that, check one short post and one long one. On the short post, the number should feel like a quick cue. On the long post, it should feel like an honest warning. If nearly all articles show the same reading time, either the content lengths are very similar or the speed setting is too coarse for your content mix.

The detail people often miss

If the site uses page caching, the result may not appear immediately after you save the settings. Clear the optimization plugin cache, the server cache, or the CDN cache if those layers are in place. Do not keep changing settings in circles until you are sure you are looking at a fresh version of the page.

How to verify accuracy and appearance on the site

Do not limit verification to a single post. Reading time sits at the intersection of content, theme, archive templates, and caching, so you need to review several states. A good check takes 10 to 15 minutes, but it saves you from discovering later that the indicator breaks in a category archive or looks far too optimistic on a long article.

Calculation check

Pick one short post, one medium-length piece, and one long-form article. Compare the output. If the number feels too low for a dense article, reduce Words Per Minute. If everything looks overly long, move closer to the starting value again. Do not tune the setting around one extreme case, or the rest of the posts will become less accurate.

Design check

Open the page on both desktop and mobile. See whether the block disrupts the spacing between the title, author, date, category, and first paragraph. If output in post meta feels cramped, try the version before content. If the line before content distracts from the introduction, move the indicator back into the meta block or place it with the shortcode in a cleaner template position.

Archive check

Archives are especially sensitive to extra meta elements. A post card may not have much room, and a long localized label can wrap awkwardly. In that case, use a shorter wording or a more compact time suffix. The main thing is to keep the cards easy to scan.

SEO and accessibility check

Reading time by itself does not guarantee better rankings. But a clear estimate can improve how the page feels and reduce frustration when an article is much longer than expected. Make sure the block does not replace the headline, does not become the only text before the article, and is not hidden behind a decorative icon with no meaning. If you add CSS, keep the contrast strong and the font size readable.

Post-setup check: the reader should understand the label without extra explanation. If you have to tell people what the number next to the title means, the label is too short or the placement is not working.

Practical use ideas for different content types

Kadence Reading Time does not create complex workflows by itself, but it can be integrated thoughtfully into a site's editorial system. The useful question is not "Where else can I insert the indicator?" but "What decision is the reader making before they start?" Once you frame it that way, the label becomes part of content navigation rather than a decorative line.

Knowledge base and documentation

In a knowledge base, reading time helps separate quick answers from long instructions. For short articles, keep the indicator in the archive so users can find fast answers more easily. For longer guides, you can show the time before the content and add a short introduction explaining that part of the time will go into following steps in the admin panel.

Editorial blog

On a blog, post-meta output is often the cleanest choice. Readers already expect to see the date, author, and category there, so reading time does not feel out of place. In collections and archives, the indicator helps users pick content based on the time they have available: a quick comment, a mid-length explainer, or a full long read.

Case studies and portfolio content

If case studies are built as a custom post type, automatic output may not cover them the same way it covers standard posts. In that case, use [kt_reading_time] in the case-study template or in a block next to the summary highlights. But do not put reading time on portfolio cards if people are choosing work by image, industry, or outcome rather than by text length.

Tutorial content with code

Articles with code are usually read more slowly than ordinary news posts. If you publish a lot of that material, lower the global reading speed or adjust individual posts manually. Also check whether the reading-time block sits too tightly next to code blocks - technical content needs breathing room and calm typography.

Why reading time does not appear or looks wrong

Most Kadence Reading Time issues are tied not to the calculation itself, but to the output location. The plugin may be active, the settings may be saved, yet the theme does not show the relevant meta block, the archive uses a different template, the shortcode was inserted as plain text, or the cache is serving an old page. That is why diagnosis should move from the visible symptom to the underlying cause.

The indicator does not appear on the post

Symptom: the plugin is activated, but no reading time appears on the published post. Possible reasons: output before content or in post meta is not enabled, the post is opening from cache, the theme hides the meta block, or you are checking a different page type instead of a single post.

What to check

• Open Appearance -> Kadence -> Reading Time and confirm which output locations are enabled.
• Open the actual public single post, not an archive, a page, or a draft preview.
• Clear page cache and CDN cache if they are in use.
• Temporarily enable display before content to separate a meta-block problem from a calculation problem.

If display before content works but post-meta output does not, the issue is most likely in the theme template or disabled meta elements. In that case, use the shortcode or adjust the theme's meta block.

The time appears on the post but not in the archive

Symptom: the indicator is visible on the post page, but not in the category archive or blog feed. Possible reasons: excerpt output is not enabled, the theme uses custom cards, the archive is builder-driven, or the excerpt is not rendered through the standard method.

Check the excerpt setting and several archive views: the main feed, a category page, an author page, and search results. If the time appears only in some archives, the templates are different. Do not try to fix that by changing WPM - the calculation is not the problem.

The shortcode shows up as text

Symptom: the visitor sees [kt_reading_time] instead of a calculated reading-time value. That usually means the shortcode was inserted in a place where WordPress does not execute shortcodes. Move it into a Shortcode block or a builder element that explicitly supports shortcodes.

If you need the shortcode in a template, test it in a normal post first. That tells you whether the shortcode itself works. If it works in a post but not in the template, the problem is in how the template renders content.

The indicator is duplicated

Symptom: reading time appears twice - for example, in the meta line and again before the first paragraph. The usual reason is that two output methods are enabled or the shortcode has been added manually on top of the automatic block. Pick one primary method. For a blog, post meta is often enough. For documentation, a line before the content is usually more effective.

The time estimate feels wrong

Symptom: a long article shows too little time, or a short post looks too long. Start with Words Per Minute. For technical material, the default may be too fast; for simple news content, it may be fine. If the problem affects only one post, use the per-post override if it is available in your interface.

Localized grammar looks awkward

Symptom: the number is followed by an awkward singular or plural form, or part of the label remains in English. On Russian-language sites, a neutral abbreviated Postfix for minutes plus a separate clear label is usually the most stable option. That is simpler and more reliable than trying to force every grammatical form manually.

Problems after caching or optimization

Symptom: the settings are saved in the admin panel, but visitors still see the old version. Clear the optimization plugin cache, server cache, and CDN cache. If aggressive HTML optimization is enabled, disable it temporarily and check the page again. A small output block like this usually does not need exclusions, but caching can delay the visual update.

Limitations and cases where you need a different tool

Kadence Reading Time is best viewed as a lightweight reading-time estimate, not a full engagement system. That makes it convenient for sites in the Kadence ecosystem, but it also creates clear boundaries. The more precisely you understand those boundaries, the less likely you are to expect things the plugin never promised.

First, the plugin is not a progress bar. It can show an estimated duration, but it does not show where the reader is within the article. Second, the setup is based on words per minute. For languages and formats where a word is not the most useful unit of measurement, the estimate may need manual review. Third, automatic output depends on the template and the locations described in the documentation. For custom post types, builder elements, and non-standard templates, you will need the shortcode or a separate layout adjustment.

Do not add the plugin just because "that is what media sites do." If your posts are short or users choose content based on a different logic, the indicator may add no value. It is far more effective when it supports a real decision: opening a long tutorial, choosing a shorter item in an archive, or judging the effort required for a guide.

When Kadence Reading Time is the right choice

Kadence Reading Time is the best fit for sites that already use the Kadence ecosystem and want a clear, lightweight reading-time estimate without heavy analytics. Its strength is the straightforward logic: choose the output location, set the reading speed, adjust the labels, and use the shortcode when needed. That is enough for most blogs, knowledge bases, and editorial sections.

If you need a progress bar, detailed image-aware timing, separate rules for many post types, or deeper read-completion analytics, look at alternatives or more specialized tools. If the goal is simpler - give readers an honest cue before the article and in the archive - this plugin is a practical option.

Before you download Kadence Reading Time, check three things: whether the site has enough long-form content for this kind of cue to matter; whether output through posts, archives, post meta, and shortcode fits your setup; and whether you are ready to tune the labels carefully and verify the result after caching. If the answer is yes across the board, you can move on to installation on a staging copy or directly on the live site with a backup in place.

After setup, do not leave the plugin without an editorial check. Open several posts, review the wording, spacing, archives, and short pieces. Well-configured reading time barely draws attention to itself, but it helps readers enter the content with less friction. That is exactly where Kadence Reading Time does its job best.