Free Title Capitalization Fixer

WordPress with Yoast or Rank Math

1. Run all titles through the fixer before saving the post
2. Copy the corrected title into the post Title field; ensure SEO title tag inherits or matches
3. For sites with hundreds of legacy posts, use the bulk paste mode to process all titles, then update via WP-CLI or DB script
4. Verify Yoast or Rank Math SEO title preview shows the corrected version with proper character count
5. Document your chosen style guide (AP / Chicago / MLA) in your WordPress style guide page for editorial reference

Webflow CMS Collections

1. Use the fixer before adding new CMS items; corrected title goes in the Name field
2. For migrating existing content, export collection as CSV, run titles through bulk fixer, re-import via Webflow CSV import
3. Map title case style consistently across all collection types (Blog Posts, Articles, Authors)
4. Webflow Designer auto-styles H1 from CMS Name; ensure your selected style displays correctly
5. Set the SEO Title field to inherit from Name plus brand suffix per Webflow native settings

Shopify product titles and pages

1. Apply title case to product titles per your brand style; Shopify search and storefront display benefit from consistency
2. Use bulk product editor to update many titles at once after running through the fixer
3. For SEO Title and Meta Description (different from Product Title), apply your style guide separately
4. Collection (Category) titles also benefit from consistent capitalization; review and standardize quarterly
5. Verify product schema markup includes the standardized title in the name field

Notion / Roam editorial workflow

1. Add the fixer as a starred bookmark for one-click access from any page
2. In your editorial template, include a checklist item: "Title checked through capitalization fixer"
3. For team consistency, document chosen style guide in your editorial Notion page
4. Use Notion API integration to apply title case automatically on save (advanced)
5. Periodically audit titles across your knowledge base for style consistency

GitHub Markdown and documentation sites

1. Apply title case to top-level headings (#) in Markdown documentation; sentence case for sub-sections is also acceptable
2. For docs sites (Docusaurus, MkDocs, GitBook), the H1 from frontmatter should follow your chosen style
3. Use a pre-commit hook with our API to auto-fix capitalization on commit
4. For consistency across many maintainers, add a CONTRIBUTING.md note specifying the title case style
5. Periodically run a bulk audit on all repository titles via our API

Wrong style guide selected

Cause: You applied AP rules to a publication that uses Chicago, leading to inconsistent capitalization with prior content.

Fix: Switch to your publication style guide in settings; the tool re-renders all output with the new rules instantly.

Brand name lowercased incorrectly

Cause: Custom-cased brand name (eBay, iPhone, OpenAI) was treated as a regular word and got standard capitalization applied.

Fix: Add the brand to the Custom Dictionary as always-capitalized with your preferred casing; it will be preserved in all conversions.

First word of subtitle not capitalized

Cause: Title contains a colon, but the word after was treated as mid-title and lowercased per the rules.

Fix: Enable Capitalize After Colon option; or use sentence case mode for subtitle handling per Chicago Manual conventions.

All-caps input flattened to lowercase

Cause: Input was ALL CAPS and the converter normalized it to lowercase before applying title case rules.

Fix: This is intentional; if you need to preserve all-caps for an acronym embedded in the input, use the Custom Dictionary.

Hyphenated compound capitalized inconsistently

Cause: Style guide rules differ on hyphenated compounds; the wrong style was selected for your context.

Fix: Switch style guides until output matches your standard; or use the per-element override toggle for that specific title.

Output exceeds 60 characters

Cause: Title is too long for SERP display; Google will truncate with ellipsis on most devices.

Fix: Edit the title to fit within 60 characters; the pixel-width counter shows actual SERP truncation point per device.

Numbers attached to lowercase letters

Cause: A number directly followed by a lowercase word was not separated by space, and capitalization detection failed.

Fix: Add a space between the number and word; the converter handles "30 days" correctly but treats "30days" as one word.

Special characters break the parser

Cause: Title contained unusual punctuation or symbols (em-dashes, smart quotes) that the parser interpreted as word boundaries.

Fix: Use standard punctuation (regular hyphens, straight quotes); the converter normalizes most special chars but not all.