Resource Review10 min read

Literal Word BibleTagger

4.0Editor rating

A free, lightweight JavaScript widget and WordPress plugin that turns written Bible references into linked hover or tap previews without ads, accounts, or API keys—but remote runtime dependence, a hostname usage signal, client-side scanning limits, and a restrictive service license deserve attention before a publisher installs it sitewide.

Visit official site ↗

Starting price: Free
Free tier: Yes
Platforms: JavaScript websites · WordPress 5.2+ · modern browsers
Developer: Literal Word
Launched: 2026
Updated: Aug 16, 2026

FreePrice

One script tag or WordPress pluginSetup

Up to 5 versesPopup length

NASB 1995 · LSB · ESV · NKJV · KJVTranslations

Neither requiredAccount / API key

Under 40 KB advertisedScript size

The verdict

BibleTagger is one of the easiest ways for a sermon, article, curriculum, or church blog to make Scripture citations useful without building a Bible API integration. The free price, scoped selectors, translation choices, theme controls, no-ad presentation, and restrained popup length are strong. Use it only after testing content coverage, keyboard and screen-reader behavior, performance, content-security policy, consent requirements, and the consequence of making every tagged page depend on Literal Word’s remote script and endpoints.

Try Literal Word BibleTagger ↗

Opens literalword.com

Literal Word BibleTagger is a publisher tool from the team behind the Literal Word Bible reader. It looks through selected text on a webpage, recognizes references such as John 3:16 or Romans 8:1–4, turns them into links, and shows the cited text in a small popup when a reader hovers or taps. A popup displays up to five verses; longer passages link to the full selection on Literal Word. The page owner chooses NASB 1995, Legacy Standard Bible, ESV, NKJV, or KJV and can follow the visitor’s system theme or force light or dark presentation.

There are two installation paths. A general site can add one remotely hosted JavaScript line and configure selectors, excluded areas, translation, theme, and CSS custom properties. A WordPress owner can install the official plugin and use an administration screen instead of editing a template. The widget skips headings, existing links, and code by default, and its selector controls prevent it from rewriting navigation, comments, or other page regions that the publisher does not intend to scan.

The experience is intentionally narrow. It does not insert a full reader, search tool, concordance, commentary, study notes, original-language data, or account system. It makes citations easier to check in context. That modest scope helps performance—the vendor advertises a script under 40 KB, loaded without blocking the page, with verse text requested on demand—but it also means the host site is relying on a third party each time a reader asks to preview a verse.

This is a researched review of the official product page, current terms, WordPress listing, published privacy explanation, and visible setup model. We did not install the plugin on a production WordPress site. The wrapper is released under GPLv2 or later, while Literal Word’s hosted widget, verse endpoints, and translation content remain governed by separate service terms. That distinction matters: “open-source plugin” does not make the complete hosted service self-hostable or grant a publisher rights to cache and redistribute the Bible text.

✓ The good

No-cost installation - the widget and WordPress plugin require no subscription, account, card, or API key
Low-friction reading - readers can check a short citation without leaving the article or losing their place
Five respected translations - NASB 1995, LSB, ESV, NKJV, and KJV cover common formal-English preferences
Useful scope controls - publishers can select content containers, exclude problem areas, and avoid headings, links, and code
Customizable presentation - light, dark, and system modes plus CSS variables and exposed shadow parts support brand adaptation
No advertising in the preview - the popup stays focused on the biblical text and the full-passage link
Transparent WordPress data note - the listing explains the remote script, on-hover verse request, and one hostname usage signal

✗ Watch out

Remote dependency - the script, verse endpoint, availability, behavior, and service rules remain under Literal Word’s control
Static scan boundary - content injected after BibleTagger loads is not automatically recognized, which can miss modern app-rendered sections
Limited translation set - NIV, NLT, CSB, NRSV, Catholic editions, non-English Bibles, and publisher-owned text are not offered
Hostname signal - the WordPress documentation says one anonymous usage event containing the site hostname is sent per page
Restrictive license - hosted verse content cannot become a general API, feed, cache, bulk corpus, competing service, or modified widget
No uptime commitment - the terms permit throttling, blocking, modification, revocation, or discontinuation without notice
Small public plugin footprint - the WordPress listing had fewer than ten active installations when reviewed, so field evidence is thin

Best for

Churches publishing sermon manuscripts, devotionals, statements of faith, or study notes
Christian writers who cite many short Bible passages inside long articles
WordPress administrators who want verse previews without managing an API key
Developers comfortable testing a small third-party JavaScript dependency and content-security policy

Avoid if

You need a self-hosted, offline, guaranteed-availability, or auditable verse service
Your required translation or language is outside the five supported English editions
Your site renders most article text after page load without a compatible rescan strategy
Your privacy, security, accessibility, or procurement policy forbids an undeclared third-party runtime

What Literal Word BibleTagger is

BibleTagger is a browser-side enhancement layer. It finds recognizable Scripture references in allowed parts of an already rendered webpage, inserts links, and requests the corresponding text only when a reader interacts. It avoids running a publisher’s own Bible database or shipping every verse with the page. The host keeps writing ordinary references; the widget supplies recognition and preview behavior.

It is distinct from Literal Word itself. Literal Word is a full Bible-reading and study website with search and language tools. BibleTagger is infrastructure for other publishers. The products share a developer and destination, but they answer different search intent, involve different setup and privacy questions, and warrant separate reviews rather than one duplicate page.

Why small publishers use BibleTagger instead of building verse previews

A reliable reference parser has more edge cases than it appears: abbreviations, numbered books, ranges, multiple citations, punctuation, mobile taps, dark mode, overlapping links, and invalid references. BibleTagger packages that work into one line and places a short passage beside the sentence that cited it. Compared with linking every reference manually, it reduces editing labor and preserves the reader’s context.

The absence of accounts and API keys is unusually friendly, but convenience shifts operational control to Literal Word. A publisher cannot promise that a free endpoint will always respond, that a translation will remain available, or that a future script update will behave identically. Pinning a reviewed version is not presented as an option. Treat the widget as an enhancement: the underlying citation and article should remain understandable when JavaScript, the network, or the service fails.

Reference recognition and five-verse previews: useful without overwhelming the article

BibleTagger recognizes conventional Bible references in the containers a publisher selects. Hovering with a pointer or tapping on mobile opens the verse text; up to five verses stay in the popup, while longer passages lead to Literal Word. Existing links, code, and headings are skipped by default, limiting accidental changes to navigation and technical examples.

The five-verse ceiling is a sensible editorial boundary. It supports fact-checking a quotation or reading its immediate context without turning every citation into a giant modal. It also drives traffic to an external reader and means visitors who need a full chapter leave the host site. Publishers should write descriptive link context and preserve the original reference so the page remains usable when the preview is unavailable.

Themes, selectors, and CSS hooks: enough control for most church sites

A site can choose light, dark, or system-following appearance, change documented CSS variables, and target exposed shadow parts for deeper styling. Inclusion and exclusion selectors keep scanning inside an article body and away from forms, menus, footnotes, comments, or interactive components. WordPress administrators can configure the behavior without creating their own plugin.

Customization still needs quality assurance. Test narrow phones, zoom, high contrast, reduced motion, keyboard-only use, screen readers, right-to-left layouts, nested citations, footnotes, print styles, and touch dismissal. Shadow-DOM styling and inserted links may interact with existing CSS or analytics. The vendor page does not substitute for the host’s own accessibility conformance and browser matrix.

On-demand remote delivery: small initial weight with a continuing trust cost

The advertised script is under 40 KB, loads without blocking the page, and fetches verse text only on interaction. The WordPress plugin says it loads the remote script on every page and sends a single anonymous per-page usage signal containing the site hostname; an interaction sends the reference and chosen translation, not the surrounding article text.

Those requests still expose ordinary connection metadata to the service and hosting chain, and a hostname can identify a church or publisher even when it does not identify an individual visitor. Administrators should document the dependency in their privacy and cookie assessment, restrict it through content-security policy, measure layout and interaction latency, and decide what happens if regional blocking or an outage prevents the request.

Pricing

Best value

JavaScript widget

Free

Add the published script to a website and configure its HTML attributes or JavaScript options. No account, API key, payment card, usage tier, or advertised view cap is required. The license is for the unmodified widget and hosted service, not a general Bible-content API.

WordPress plugin

Free

The official plugin supplies an administration interface and loads the hosted BibleTagger script on pages. The WordPress wrapper is GPLv2 or later; its readme says WordPress 5.2+, PHP 7+, and a tested version through WordPress 7.0.2.

Full Literal Word reader

Free external service

When a citation is longer than five verses, the preview links readers to Literal Word for the whole passage. That outbound reader is a separate product experience, not an embedded paid tier or a copy of the text hosted by the publisher.

The published price is genuinely simple: zero dollars for both the script and WordPress wrapper, without an account, API key, card, metered plan, or advertising inside the popup.

Free does not mean without cost. A publisher assumes performance testing, privacy disclosure, accessibility verification, content-security configuration, update monitoring, translation-rights compliance, and incident response if the third-party script changes or fails.

The terms grant a revocable, non-exclusive, non-transferable right to use the unmodified widget. They prohibit scraping, bulk extraction, caching or storing verse content, republishing it as a feed or API, reverse engineering, derivative or competing services, and removal of attribution.

Literal Word may throttle, block, alter, or discontinue the service without notice and disclaims uptime and performance. The liability cap is the greater of one dollar or the amount paid in the prior month—which is effectively one dollar for a free user. Organizations needing guaranteed service should use a licensed Bible API or self-host text they are legally permitted to distribute.

Where Literal Word BibleTagger falls behind

Publish a versioned change policy. A hosted script installed across many sites should expose stable version URLs, release notes, deprecation windows, integrity hashes, rollback instructions, and an incident-status channel.

Expand privacy documentation beyond the plugin readme. Name hosting and analytics processors, connection fields, lawful basis, regional routing, retention, deletion handling, security, and whether usage data trains or prioritizes product changes.

Document accessibility evidence. Publish keyboard behavior, focus management, screen-reader output, zoom and reflow testing, contrast, touch target size, reduced-motion behavior, and a supported assistive-technology matrix.

Handle dynamic applications explicitly. Offer a documented rescan API, mutation observer option, framework examples, performance guardrails, and guidance for content rendered after the initial script pass.

Clarify availability and support. A public status page, response channel, abuse process, rate limits, fair-use boundaries, and advance notice before translation or endpoint removal would make the free dependency easier to govern.

Broaden legitimate choices. More languages, deuterocanonical editions, current mainstream translations, custom licensed text, localization, and a paid service-level tier would serve churches outside the current English-Protestant translation set.

BibleTagger vs. Bible Gateway vs. API.Bible vs. manual links

Bible Gateway supplies a familiar external passage destination and a much wider translation library, but a plain link takes the reader away and does not automatically recognize every reference. API.Bible gives developers explicit programmatic access to many licensed Bibles and more architectural control, while requiring an API key, implementation, rights compliance, quotas, caching rules, and ongoing code. BibleTagger is faster for a small publisher that accepts its five translations and remote widget.

Manual links have no injected script, usage signal, parsing surprise, or popup accessibility layer. They also consume editorial time and are often omitted. Blue Letter Bible, Logos, and Literal Word itself are complete study destinations rather than embeddable tagging layers. Choose BibleTagger for convenient in-context reading; choose a licensed API or controlled text corpus when stability, language range, offline behavior, custom presentation, or service guarantees matter more than one-line setup.

The bottom line

Literal Word BibleTagger does its small job well on paper: one free integration recognizes citations, previews up to five verses, respects selected page regions, offers five respected English translations, supports dark mode and styling, and avoids advertisements, accounts, and API-key administration. That is a meaningful reader improvement for sermon archives and Christian articles. Its strongest benefit is also its dependency: Literal Word hosts the mutable code and verse response, receives the site hostname signal described by the WordPress plugin, limits reuse through a revocable license, promises no uptime, and can change or discontinue access. Install it as a progressive enhancement, not as the only place the passage exists. Test it on a staging copy, preserve visible references, document the third party, verify accessibility and performance, and keep a removal plan. Publishers requiring a contractual SLA, broad translations, self-hosting, caching, or full data control should build on an appropriately licensed API instead.

Alternatives to Literal Word BibleTagger

Literal Word 4.9The developer’s full Bible reader and study site. It is the destination behind long BibleTagger passages, but it does not replace the tagging integration on another publisher’s pages.

Bible Gateway 3.7A familiar passage destination with a much broader translation catalog. Manual outbound links are simpler operationally, but they lack an automatic in-page preview.

API.Bible 4.0A developer API for integrating licensed Bible content with more control and translation choice. It requires authentication, engineering, and compliance work.

Blue Letter Bible 4.7A deeper free study destination with lexicons and commentaries. Better after the click; not a drop-in tagging widget for a publisher’s own article.

Logos Bible Software 4.9A professional research environment with rich linking and original-language tools. Far more capable and expensive, and aimed at study rather than public-site enhancement.

Frequently asked questions

Is Literal Word BibleTagger free?

Yes. The JavaScript widget and official WordPress plugin are offered without a subscription, account, API key, credit card, or advertised traffic tier. The hosted service remains subject to Literal Word’s revocable terms and comes without an uptime guarantee.

Which Bible translations does BibleTagger support?

The published choices are NASB 1995, Legacy Standard Bible, ESV, NKJV, and KJV. The tool does not currently advertise NIV, NLT, CSB, NRSV, Catholic editions, non-English translations, or publisher-supplied licensed text.

Does BibleTagger collect visitor data?

The WordPress listing says a single anonymous usage signal containing the website hostname is sent once per page, and a verse request sends the reference and selected translation when a visitor hovers or taps. Ordinary network metadata may also reach the service chain. Evaluate and disclose the dependency under your own privacy requirements.

Does BibleTagger slow down a website?

Literal Word advertises a script under 40 KB that loads without blocking and fetches verse text on demand. Actual cost depends on page length, number of references, devices, network, other scripts, and remote response time. Measure real pages with and without it before sitewide deployment.

Will BibleTagger recognize content added after page load?

The published WordPress documentation says content added dynamically after the initial page load is not scanned. Sites built around client-side navigation, infinite loading, expandable notes, or late hydration should test carefully and ask the developer for a supported rescan method.

Can I cache BibleTagger verses or use it as a free Bible API?

No. The terms prohibit scraping, mass extraction, caching or storing verse content, republishing it as a feed or API, creating a derivative or competing service, and reverse engineering. Use an appropriately licensed API or text corpus for those purposes.

Is the complete BibleTagger system open source?

The WordPress wrapper is distributed under GPLv2 or later. The remotely hosted widget, service endpoints, and licensed Bible content are governed separately and are not presented as a self-hostable open-source stack. Review both layers before making an open-source claim.