RFC 4180 is the technical document that provides a formal definition for the Comma-Separated Values (CSV) file format. It established the standard rules for how data should be structured in a CSV to ensure it transfers correctly between different software applications. This standard [formally registered the "text/csv" MIME type in October 2005] (RFC Editor) to help computers identify and handle these files consistently.
Entity Tracking
- RFC 4180: An informational document released in 2005 that codifies the structure of CSV files and registers their official media type.
- CSV (Comma-Separated Values): A plain text data format used for storing tabular information where fields are separated by commas and records by newlines.
- text/csv: The official MIME subtype registered with IANA for identifying CSV files on the internet.
- CRLF: A specific line-ending sequence consisting of a Carriage Return (CR) and a Line Feed (LF) used to separate records in a standard CSV.
- MIME Type: A standard identifier used to label the format of a file so that software knows how to process it.
- RFC 7111: A later standard that [describes the use of URI fragments to select specific rows or columns] (Wikipedia) within a CSV document.
- W3C (World Wide Web Consortium): An international standards organization that released [recommendations for CSV metadata and semantics in December 2015] (Wikipedia).
What is RFC 4180?
Before this document, there was no master specification for CSV files. Different programs used various methods to escape characters or handle line breaks, which caused errors when moving data between tools. RFC 4180 gathered the most common practices into a single informational guide to improve interoperability.
The specification defines CSV as a format for "passive text data." While it provides a clear set of rules, it is categorized as "Informational," meaning it documents a common practice rather than a mandatory internet protocol. It remains the primary reference used by developers when building the export and import functions for SEO platforms and spreadsheet software.
Why RFC 4180 matters
- Data Interchange: It allows you to move keyword lists, crawl results, and backlink data between incompatible systems without losing structure.
- Human Readability: Because the format is plain text, you can open and fix data files using simple text editors if a spreadsheet program fails to load them.
- Universal Support: Almost all database management systems and ecommerce platforms support CSV as a primary export format.
- Compression Efficiency: CSV files are highly compressible, which reduces the storage space and bandwidth needed for large SEO data exports.
- Tool Stability: Following the standard prevents "broken" files where columns shift or data disappears during an import.
How RFC 4180 works
The standard relies on a specific set of formatting rules to keep data organized in rows and columns.
- Line Breaks: Each record must stay on its own line, separated by a CRLF (Carriage Return and Line Feed). The very last record in a file does not strictly require a line break.
- Header Row: The first line can optionally contain column names. This row must follow the same format and have the same number of fields as the data rows.
- Comma Separation: Fields are separated by commas. You must not include a comma after the final field in a record.
- Field Consistency: Every row in the file must contain the same number of fields.
- Space Handling: Spaces are treated as part of the data and are not ignored by the parser.
- Double Quotes: You may wrap fields in double quotes. This is mandatory if the field contains a comma, a line break, or a double quote character.
- Escaping Quotes: If a field is wrapped in double quotes and contains an internal double quote, you must "escape" it by preceding it with another double quote (e.g., "Company ""Name""").
Best practices
- Include a header row: Always provide names for your columns to ensure different SEO tools map the data to the correct fields.
- Use double quotes for text: Wrap any fields containing SEO descriptions or titles in double quotes. This prevents a comma inside a description from being mistaken for a column break.
- Verify your line endings: Ensure your software uses CRLF for line breaks. Using different line-ending characters can cause some import tools to treat the entire file as a single long row.
- Check character encoding: While RFC 4180 does not mandate a specific encoding, it notes that US-ASCII is common. For SEO data containing international characters, verify the encoding (like UTF-8) separately.
- Mind the row limits: Be aware that spreadsheet programs have limits, such as [Microsoft Excel which supports a maximum of 1,048,576 rows] (Wikipedia).
Common mistakes
Mistake: Including a trailing comma at the end of a line. Fix: Ensure the last field of every row is followed immediately by the line break.
Mistake: Using a single double-quote inside a quoted field.
Fix: Use Two double-quotes (e.g., "") to represent one quote mark within the data.
Mistake: Assuming the first line is always a header. Fix: Explicitly define the "header" parameter in your MIME type as "present" or "absent" when possible, as there is no way for a computer to test this automatically.
Mistake: Neglecting spaces. Fix: Do not add spaces after commas unless you want those spaces to appear as part of the data in your SEO tool.
Examples
Standard record format:
Keyword,Volume,Difficulty
"seo tools",1500,Easy
"backlink audit",800,Medium
Escaping a internal quote:
ID,Description
1,"This is a ""top"" priority keyword"
Handling a field with a comma:
Name,Location
"Agency, Inc.","New York, NY"
FAQ
Does RFC 4180 require a specific character encoding? No. While it mentions US-ASCII as a common usage, it allows for other character sets. The standard acknowledges that CSV data typically survives translation between character sets, but the encoding must often be communicated separately to the receiving program.
What happens if my data contains a line break? According to RFC 4180, fields containing line breaks must be enclosed in double quotes. However, you should be careful, as some older programs may still fail to parse these correctly even when quoted.
How do I know if a file is a formal CSV?
A formal CSV will use the MIME type text/csv. Software can use this label to distinguish CSV files from other delimited files, such as those using tabs (TSV).
Can I use a semicolon instead of a comma? Technically, RFC 4180 only defines the comma as the delimiter. Using semicolons or other characters creates a "dialect" of CSV. While many tools (including LibreOffice Calc) support multiple separators, they do not strictly follow the RFC 4180 format.
Is there a limit to how many rows I can have? The RFC 4180 specification does not set a limit on row counts. However, the software you use to open the file will have limits. For instance, [Google Sheets is limited to 10,000,000 cells] (Wikipedia).
