TL;DR

Four new content pieces are live covering PDF tool reviews and practical PDF guides, all available in 19 languages from day one. Automated Node.js scripts now handle translation and JSON-LD schema validation so new content stays globally consistent without manual editing.

What's New

• New blog posts: Smallpdf review, Sejda review, PDF redaction guide, and PDF merging guide published to the blog
• 19-language translations: All new blog content automatically translated using a Node.js script backed by the Anthropic API
• JSON-LD SEO validation script: New Node.js script validates structured data schema across blog posts to keep SEO markup clean as content scales
• Internal cross-linking: Translation script automatically appends localized internal links across all language variants
• Bug fix: JPG to PDF tool: Resolved a user-facing conversion bug affecting JPG to PDF output
• Blog layout fixes: Resolved a duplicated header issue and corrected typography rendering in the blog layout
• Next.js updates: page.tsx blog rendering logic and global CSS updated to support improved layout and formatting

How to Use

All new blog posts are available at https://www.gethonestpdf.com/blog. Language variants are served automatically based on locale. No action needed from users.

For contributors, the two new scripts are:

1. Run the translation script after adding new markdown content to generate all 19 locale files
2. Run the JSON-LD validation script before publishing to verify structured data is well-formed

FAQ

Which languages are the new blog posts available in?

All four new posts are translated into 19 languages including French, German, Japanese, Portuguese, Spanish, and others. Translations are generated automatically via the Anthropic API and applied to every locale file in a single script run.

What was the JPG to PDF bug and who did it affect?

The bug caused incorrect output during JPG to PDF conversion for affected users. It has been fully resolved in this update and the tool is working correctly.

How does the automated translation pipeline work?

A Node.js script reads new markdown blog content, calls the Anthropic API to produce localized versions, and writes the results to each of the 19 language files. It also injects locale-appropriate internal links automatically.

What does the JSON-LD validation script check?

The script parses structured data blocks in blog markdown files and validates them against expected JSON-LD schema shapes, catching malformed or missing fields before they affect search engine indexing.

TL;DR

Four new content pieces are live covering PDF tool reviews and practical PDF guides, all translated into 20+ languages via the existing Anthropic API pipeline. A duplicated header bug and typography issues on blog pages have also been resolved.

What's New

• Smallpdf review: In-depth breakdown of Smallpdf's features, pricing, and limitations
• Sejda review: Detailed review of Sejda as a PDF editing and management tool
• PDF redaction guide: Step-by-step walkthrough on redacting sensitive content from PDF files
• PDF merging guide: Practical guide covering how to merge PDF files and when to use different approaches
• Multilingual translations: All four new posts translated into 20+ supported languages using the AI-assisted translation script
• SEO utility scripts: Added scripts for validating JSON-LD structured data and managing internal link appending across localized content
• Duplicated header bug fix: Blog layout pages were rendering a duplicate header element, now resolved
• Typography fixes: Corrected typographic inconsistencies across blog post templates

How to Use

All new content is accessible directly from the HonestPDF blog at https://www.gethonestpdf.com/. Localized versions are served automatically based on user locale settings. No configuration needed.

For contributors using the internal scripts:

1. Run the SEO validation script to check JSON-LD schema integrity before publishing
2. Use the link-appending script to automatically add internal links across all locale markdown files after a new post is published

FAQ

Are the new blog posts available in all supported languages?

Yes. All four posts were translated into 20+ languages using the Anthropic API translation pipeline, so every locale is complete from day one.

What was the duplicated header bug?

Blog layout pages were rendering the header component twice due to a structural issue in the layout template. This affected the visual appearance of blog posts and has been corrected.

Do the new SEO scripts run automatically?

No. The SEO validation and link-appending scripts are utility scripts intended to be run manually as part of the content publishing workflow, not as automated CI steps at this time.

Will future blog posts also be translated automatically?

Yes. The translation pipeline is already in place. New posts go through the same script-based process, so global availability from day one is the default for all future content.

TL;DR

Four new long-form posts are live covering Smallpdf, Sejda, PDF redaction, and PDF merging. Internal Node.js scripts now handle AI-assisted translation via the Anthropic API and JSON-LD schema validation, making future content updates faster and more consistent across all 20+ supported locales.

What's New

• New blog posts added:
  • Smallpdf review
  • Sejda review
  • PDF redaction guide
  • PDF merging guide
• append_links.js: Node.js script that uses the Anthropic API to auto-translate new posts and append internal cross-links across all localized markdown files
• check_page.js: Script that validates JSON-LD structured data schema for blog pages, keeping SEO metadata accurate as content grows
• Existing blog content updated: Metadata, expanded body text, and cross-links refreshed across 20+ localized markdown files
• Bug fixes in page.tsx and globals.css: Resolved duplicated header rendering and corrected typography spacing issues in the blog layout

How to Use

To translate and cross-link a new post across all locales, run:

node scripts/append_links.js

To validate JSON-LD schema for blog pages:

node scripts/check_page.js

Both scripts require a valid ANTHROPIC_API_KEY in your environment.

FAQ

What does the append_links.js script actually do?

It reads new or updated markdown blog posts, uses the Anthropic API to generate localized translations, and appends consistent internal cross-links to all 20+ language variants automatically.

Does the auto-translation overwrite existing localized content?

No. The script is additive. It targets missing translations and appends new link entries without overwriting manually edited content already in place.

What was the duplicated header bug?

A rendering issue in page.tsx caused the blog post header to appear twice on certain routes. The fix corrects the component structure so the header renders once as expected.

Are the new blog posts indexed for SEO?

Yes. JSON-LD structured data is included and validated via the check_page.js script, and all posts are available in 20+ language versions for international search indexing.

TL;DR

Em dashes were inconsistently present across the codebase, spanning 20+ i18n language files, localized MDX blog content, SEO meta descriptions, and hardcoded UI components. This update replaces all of them with colons, commas, or periods depending on context, making copy consistent and clean across every locale.

What's New

• Removed em dashes from i18n JSON translation files across 20+ supported languages
• Replaced em dashes with colons or commas in localized MDX blog posts
• Cleaned em dashes from SEO meta tags (titles, descriptions, og:description fields)
• Removed em dashes from hardcoded UI component strings
• Each replacement reviewed individually for grammatical correctness in context

How to Use

No action needed. All changes are in static content and translation files. Any UI strings or blog content that previously contained em dashes now render with their replacement characters automatically.

FAQ

Why remove em dashes specifically?

Em dashes are a well-known signal of AI-generated or unreviewed text. Removing them makes the copy feel more intentional and human-edited, which matters for both user trust and content quality.

Were all 20+ language files updated?

Yes. Every locale file was checked and any em dash occurrences were replaced. No language was left with inconsistent formatting.

Does this affect any functionality or translations?

No functionality changes. Only cosmetic string content was modified. Meaning and translation accuracy are preserved.

Were replacements automated or manual?

The changes were reviewed in context rather than blindly find-and-replaced. Each em dash was substituted with the most appropriate punctuation for that specific sentence structure.

TL;DR

The Privacy Scanner Tool was missing its i18n translation keys in every language JSON file. This caused broken or empty UI strings for all non-English users. A restore script was updated to detect and reinsert the missing keys across all 20 locales at once.

What's New

• Added PrivacyScannerTool translation keys to all 20 language JSON files (fr, de, ja, pt, es, and 15 more)
• Updated restore_missing_tools.js to handle missing tool-level translation blocks and reinsert them automatically
• All locale files are now back in sync with the expected translation schema

How to Use

No action needed for end users — translations are restored automatically. If you're maintaining locale files locally, pull the latest changes and re-run the restore script if you have any custom forks:

node scripts/restore_missing_tools.js

FAQ

What languages were affected?

All 20 supported locales were missing the PrivacyScannerTool keys, including French, German, Spanish, Japanese, Portuguese, and 15 others. English was the only unaffected language.

Why did the translation keys go missing?

The PrivacyScannerTool entries were not included when the tool was originally added to the locale files, leaving a gap across all non-English JSON translation files.

Was any user data affected?

No. This was purely a UI string issue — no data processing or file handling logic was changed.

How was this fixed at scale without editing 20 files manually?

The restore_missing_tools.js script was updated to detect missing tool translation blocks and reinsert the correct keys programmatically, keeping all locale files consistent.

TL;DR

This release is the largest design and UX update to HonestPDF to date. Dark and light mode are now fully supported app-wide, the mobile experience has been rebuilt to feel native and clutter-free, and every tool now includes a visual 3-step guide to walk users through the upload-process — available in 20 languages.

What's New

• Dark/Light Mode: Full theme support added across the entire application. System preference is respected by default.
• Mobile UI Overhaul: Headers are cleaner, SEO/hero text sections are hidden on mobile viewports, and scrolling is fixed using 100svh to prevent layout overflow issues on mobile browsers.
• 3-Step Visual Upload Guide: Every tool upload zone now includes a standardized 3-step guide (drop file → configure → download) to reduce user confusion and drop-off.
• i18n for Upload Guides: The 3-step guide copy is fully translated into 20 languages, consistent with the rest of the app's localization.
• Standardized Upload Zones & Trust Badges: All 20+ tool routes now use a consistent upload zone component and trust badge layout.
• New Logo & Favicons: The HonestPDF logo and all favicons have been updated to the new brand variant.
• Automated Component Migration Scripts: Structural React component changes were applied across 20+ routes using automated scripts for consistency and accuracy.

How to Use

Dark/light mode toggles automatically based on system preference. No user action required. To manually switch themes, use the theme toggle in the navigation bar.

The 3-step upload guide appears automatically in all tool upload zones — no configuration needed.

Breaking Changes

None. All changes are additive or visual. Existing tool functionality and API behavior are unchanged.

FAQ

Does dark mode persist across sessions?

Yes, the selected theme preference is saved locally and restored on the next visit.

Which languages are supported for the new 3-step upload guide?

The guide is translated into 20 languages, matching the full i18n coverage already present throughout the app.

Were any tool features changed in this update?

No tool functionality was changed. This update focuses entirely on UI, theming, layout consistency, and UX improvements.

Why was the mobile UI rebuilt instead of patched?

The previous mobile layout inherited desktop structure that caused scrolling bugs and cluttered screens. A rebuild using 100svh and component-level visibility rules was the cleanest long-term fix.