What a Structural CSV Check Can and Cannot Prove
CSV stands for comma-separated values. Each record contains fields separated by commas, and a typical first record names the columns. RFC 4180 describes common CSV conventions, including quoted fields and consistent record width, although real-world exporters also use different dialects. A structural checker focuses on whether the records can be interpreted as a rectangular table without unexpected extra or missing fields.
That is not the same as confirming that an email address is deliverable, a date matches an importer’s required format, a price is numeric, or a stock keeping unit exists in a database. These are schema or business-rule checks, which require explicit expectations beyond the CSV text.
Header warnings and business checks can be useful, but their availability must be confirmed in the actual tool. A general structural pass should never be described as approval for every importer.
Read a Clean CSV Example Before Looking for Faults
Consider a product export with the columns sku, title, and price. Each record below has exactly three fields. A comma within a product title is enclosed in double quotes, while two quotation marks represent a literal quote inside a field.
sku,title,price
A101,"Notebook, blue",7.50
A102,"Set of ""three"" pencils",4.25
A103,Plain folder,2.00
The second record does not contain four columns: Notebook, blue is one quoted field. Likewise, the doubled quotes in the next row represent the value Set of "three" pencils. Counting commas without parsing quotes produces the wrong result. A reliable diagnosis follows field boundaries, not simple string splitting.
Find Rows That Have Too Many or Too Few Fields
An extra delimiter outside quotation marks adds a field, changing the shape of a row. Compare the valid example above with this malformed export:
sku,title,price
A101,Notebook, blue,7.50
A102,Pencil pack,4.25
The header has three fields, but record A101 has four. The repair is to quote the title as "Notebook, blue", provided that is what the source data actually intended. If you instead remove the comma, you silently change the product name.
A row with fewer fields needs similar attention. A104,Desk lamp has only two fields against a three-column header. If the price is intentionally blank, use A104,Desk lamp,. A trailing comma indicates an empty third field; it is not an additional fourth field in this example. An empty value and an absent column are different structural situations.
Handle Embedded Line Breaks and Quotation Marks
A quoted CSV value may contain a line break, so a logical record can occupy more than one physical line in a text editor. For example, the following CSV contains one header record and one data record even though the note appears across two source lines:
ticket,note,status
T-7,"Customer called Monday
Requested a return",open
Do not count physical lines as records until the quotation rules are interpreted. An error reported as record 12 may occur on physical line 13 or later when earlier fields span several lines. Confirm whether a diagnostic position means a record number, source line, or character offset.
An unmatched opening quote, such as T-8,"Missing closing quote,open, can cause the parser to consume following lines as part of the same field or report an end-of-file quoting error. Fix the source quotation rather than replacing every line break. Inside a quoted value, escape a literal double quote by writing it twice, not with the backslash convention used in some programming languages.
Inspect Headers Before Importing Into WordPress
A file may parse correctly and still fail because its headings do not match what the destination expects. Import systems often map fields by exact names such as post_title, sku, or regular_price. Leading spaces, capitalization differences, duplicate labels, and invisible characters can affect that mapping. Header rows are common but not mandatory in every CSV dialect; the importer determines whether one is required.
For an illustrative WordPress import, post_title,post_status and post_title,post_status, are structurally different: the latter contains an additional empty header cell. Confirm required names and column order in the importer’s actual template. The WordPress CSV Import Validator is a more targeted option in the same tool inventory, while the WordPress Redirect CSV Validator covers redirect-import workflows.
Check Delimiters, Character Encoding, and Line Endings
Not every delimited text export uses a comma. Semicolons and tabs are common alternatives, often chosen because of regional spreadsheet settings. A file separated by semicolons may appear to have only one field per record when a comma-based parser reads it. Verify which delimiter the source uses and whether the target importer supports it. Do not rename a semicolon-delimited file to .csv and assume that resolves parsing.
UTF-8 is a practical default for modern text exchange, but some exports use other encodings or include a UTF-8 byte order mark (BOM). A BOM can be mistaken for part of the first header when software does not handle it. Garbled characters can also result from opening UTF-8 bytes with a different character encoding. Mixed CRLF and LF line endings may be accepted by one parser and rejected by another, so preserve the source and test against your destination’s requirements.
If a heading looks correct but will not match, inspect invisible or nonstandard Unicode characters with the Unicode and Invisible Character Inspector, then re-export using an appropriate encoding.
Do Not Confuse Empty Values With Missing Records
Empty values are often legitimate. In A105,Stapler,, the final field exists but contains no text. In A105,Stapler, the third field is absent. A completely blank physical line may be ignored, treated as an empty record, or reported, depending on the selected CSV dialect and parser. A lone trailing newline after the final record is a normal file ending and should not automatically be treated as a defective row.
Whitespace inside fields can be meaningful. The values ABC and ABC are not necessarily equivalent identifiers. Trimming every field to make a validator happy may change account codes, names, or other data. Apply any normalization only when the destination’s data rules call for it.
Protect IDs, Dates, and Numbers During Spreadsheet Repairs
Opening and saving CSV in spreadsheet software can change values even when the exported table remains structurally valid. A product code such as 00127 may become 127, and long numeric identifiers can lose precision when interpreted as numbers. Dates may be rewritten according to locale settings. These problems are not caused by incorrect CSV quoting, so a structural validator alone will not identify every altered value.
Import sensitive columns as text when needed. Compare a repaired file against the original, paying particular attention to identifiers, postal codes, dates, prices, and fields that must remain unchanged. After passing structural checks, a CSV and JSON Converter can help inspect how a correctly parsed table maps into objects, but conversion does not guarantee that data types are appropriate.
Review CSV Formula-Injection Risks Separately
CSV is text, but spreadsheet programs may interpret some cell contents as formulas when opened. Values beginning with characters such as =, +, -, or @ may deserve special handling when they originate from untrusted users. This is called CSV or formula injection. It is a security issue separate from whether the number of columns is correct.
There is no single escaping method that is safe for every spreadsheet application and every downstream importer. Choose a mitigation that fits the consumer, and do not rewrite legitimate negative numbers or formulas indiscriminately. A structural checker should not be assumed to sanitize malicious content unless that behavior has been explicitly tested.
Use This Troubleshooting Sequence for Failed Imports
Start with the earliest confirmed parsing problem and work forward. After each repair, rerun the check and compare the record counts and key values with the original. If the structure passes but an import still fails, move to the application-specific requirements instead of repeatedly changing separators.
CSV Structure Validation Questions
Can a CSV file be valid without a header row?
Yes. CSV can represent headerless records. However, many tools and importers require column names, so follow the destination’s documented template.
Are commas allowed inside CSV fields?
Yes, when the entire field is enclosed in double quotes. A plain, unquoted comma is interpreted as a field separator in comma-delimited CSV.
Does a blank cell make a CSV invalid?
No. An empty field may be structurally valid, even if a separate business rule requires a value. A missing field that changes the record width is a different issue.
Will a structure validator automatically repair my file?
Do not assume so. A validator may only report errors. A safe repair depends on what the original data was meant to contain.
Does passing a CSV check mean WordPress will import it?
No. WordPress import plugins can require specific headers, datatypes, image fields, relationships, and configuration. Structural success is only the first checkpoint.
