Filenames and file formatting
Stay organized with collections
Save and categorize content based on your preferences.
This document provides guidance on how feed files should be named, encoded and
formatted.
Filenames
Feed filenames should remain static once a feed has been delivered.
Changing the filename after this point can result in feeds being misplaced by
Google's pipelines.
Some file names reference data points that change over time, for example, the
date of an election in a pre-election feed filename. Even if such a data point
changes in the feed itself, the feed's filename shouldn't be updated to match
it.
Encode all XML files with UTF-8. Enter line breaks as LF (\n) as opposed to CR
LF (\r\n).
For consistency across files and to aid human readability, use two spaces for
all indentation of elements. Don't use tabs to indent. Be sure to indent each
child node of an element an additional two spaces.
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2024-11-11 UTC.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2024-11-11 UTC."],[[["\u003cp\u003eFeed filenames should remain static to avoid misplacement by Google's systems, even if data points within the feed change.\u003c/p\u003e\n"],["\u003cp\u003eAll XML files must use UTF-8 encoding, LF line breaks, and consistent two-space indentation for readability and processing.\u003c/p\u003e\n"]]],[],null,["# Filenames and file formatting\n\nThis document provides guidance on how feed files should be named, encoded and\nformatted.\n\nFilenames\n---------\n\nFeed filenames should remain static once a feed has been delivered.\n\nChanging the filename after this point can result in feeds being misplaced by\nGoogle's pipelines.\n\nSome file names reference data points that change over time, for example, the\ndate of an election in a pre-election feed filename. Even if such a data point\nchanges in the feed itself, the feed's filename shouldn't be updated to match\nit.\n\nFile formatting\n---------------\n\nEncode all XML files with UTF-8. Enter line breaks as LF (`\\n`) as opposed to CR\nLF (`\\r\\n`).\n\nFor consistency across files and to aid human readability, use two spaces for\nall indentation of elements. Don't use tabs to indent. Be sure to indent each\nchild node of an element an additional two spaces."]]