One Title Per Line: Plain Text Format and Import Checks

By huanggs

The Output Contract: Titles Only, One Per Line

A titles-only file is useful when another editor, script, CMS import, or spreadsheet expects a simple list rather than a full article. The format should be defined as a data contract: each non-empty line contains exactly one title, and nothing else appears before, after, or between the titles.

That means no introduction, no numbering, no bullets, no category labels, no markdown table, no notes such as “Here are the titles,” and no hidden metadata. If the required output is three titles, the plain text should look exactly like this:

Title Audit
Duplicate Cleanup Plan
CMS Import Checklist

Rules That Make the File Reliable

  • One title per non-empty line: a line break separates records. Do not wrap a single long title onto a second line.
  • No numbering or bullets: “1. Title,” “- Title,” and “Title — approved” are not pure title lines unless that punctuation is truly part of the title.
  • Trim accidental spaces: leading and trailing spaces create noisy comparisons and can break exact-match validation.
  • Use a consistent encoding: UTF-8 is the safest default for mixed punctuation, accents, and non-English titles.
  • Keep the count explicit: if the request says 50 titles, validation should find 50 non-empty lines.

A Simple Validation Checklist

  1. Count non-empty lines and compare the result with the expected total.
  2. Reject blank lines inside the list unless the importer explicitly allows them.
  3. Scan for leading numbering patterns such as “1.”, “01)”, bullets, or checkbox characters.
  4. Normalize titles for duplicate checks by lowercasing, trimming spaces, and collapsing repeated whitespace.
  5. Review near-duplicates manually. “Product Title Audit Checklist” and “Checklist for Auditing Product Titles” may be the same deliverable even if the strings differ.
  6. Save the accepted file with a clear name and, if needed, a separate manifest that records source prompt, editor, date, and count. Keep that manifest outside the pure title file.

Importing Into Spreadsheets or a CMS

Many tools can paste a line-separated text list directly into a single column. If a tool requires CSV instead, treat each title as one record with one field. Titles containing commas, double quotes, or embedded line breaks require proper CSV quoting; RFC 4180 CSV format documents common record-per-line and quoting rules. Do not call a plain text list “CSV” unless it is actually formatted as CSV.

A one-column CSV sample with a header and titles containing commas or quotation marks can be copied like this:

title
"SEO, Content"
"Write ""Titles Only"""
"CMS Import"

Before importing, run a small test with two or three rows. Confirm that a title with a comma stays in one cell, a title with quotation marks is escaped correctly, and the CMS does not convert smart punctuation or strip characters from the beginning of a line.

Import Checks After Saving

After saving the file, reopen it in the target tool rather than only in your text editor. Check the row count, the first and last title, any title with punctuation, and whether blank lines were added at the end. If the CMS creates draft pages, preview several drafts before bulk publishing so you can catch accidental numbering, truncated titles, or merged rows.

Clear, descriptive titles still matter after import. Google’s title link guidance recommends title text that describes the page and avoids repeated boilerplate. The one-title-per-line format helps keep the data clean; the title itself still has to match the page it will represent.