How to Generate an XML Sitemap from a List of URLs

Understand the input and output

An XML sitemap presents site locations in a structured XML format. This tool is useful when you have a list of destinations and want to turn that text into sitemap content instead of writing the XML structure manually.

You can provide full web addresses, relative paths, or a mixture of both. A configurable base address, change-frequency value, and priority value control how entries made from supplied lines are represented. The tool formats the text you provide; it does not fetch destinations or confirm that they work.

Build the sitemap from a list

1. Prepare the source list with one web address or path on each line. Surrounding whitespace is removed from a line, and blank lines are omitted before entries are created.

2. Paste the list into the URL input. If the field contains only whitespace, leave it that way only when you intend to use the separate fallback behavior described below.

3. Set the base address when the list includes relative paths. For a nonblank line that does not begin with the supported web prefix, the tool removes a trailing slash from the base and a leading slash from the line before joining them. A full address beginning with that prefix is not given the base address.

4. Choose the change-frequency and priority text for entries created from supplied lines. When you keep the defaults, those values are monthly and 0.8. The configured text is inserted as provided, with no indicated validation or normalization step.

5. Generate the sitemap text, then inspect the XML declaration, the sitemap URL-set container, locations, and metadata. Compare the result with the source list so copied or misplaced content is easier to spot.

6. Copy or save the generated text through your usual workflow. Keep the source list available separately if you expect to revise the entries later.

Interpret the generated XML

A result made from supplied nonblank lines contains XML text with a declaration, a sitemap URL-set container, and an entry for each retained line. Relative paths should show the selected base address joined to the path, while full addresses beginning with the supported prefix remain unprefixed.

Location text from supplied lines is escaped when placed in location elements. Empty or whitespace-only input follows another path: the result has one entry at the base address followed by a slash, uses the configured change-frequency, and assigns priority 1.0.

Read metadata as inserted content rather than as a destination assessment. The generated text does not show that a supplied address is reachable, valid, complete, or standards-compliant, so review unusual characters, accidental content, and chosen values before using it.

Worked example

A site owner has an About-page path and a full Contact-page address and wants both locations formatted in one XML sitemap.

Select a base address, enter one relative path and one full address on separate lines, retain or change the metadata, and generate the sitemap text. Inspect the locations and metadata in the XML.

The result has an XML declaration, a sitemap URL-set container, and entries for the two nonblank lines. The relative path is joined to the selected base address, the full address is not prefixed, and supplied entries contain the configured metadata.

Limitations

• The tool formats supplied text without fetching, testing, or verifying the destinations, so the input is not assessed for reachability, validity, completeness, or standards compliance.
• Metadata text for supplied lines is inserted as entered without an indicated validation or normalization step.

Common errors

• An unintended base address changes a relative location. Select the intended base before generating, then inspect the joined location.
• Multiple destinations on one line prevent the intended line-based input. Put one address or path on each line and remove stray text.

FAQ

Can I generate a sitemap from relative paths?

Yes, when you set the intended base address. Each nonblank line that does not begin with the supported web prefix is joined to that base after slash trimming.

What happens if I leave the URL field blank?

When the input is empty or contains only whitespace, the tool creates one entry at the base address followed by a slash. That fallback uses the configured change-frequency and priority 1.0.

Does the tool check whether my URLs work?

No destination check is indicated. The tool formats supplied text into sitemap entries, so you need to review whether the locations are suitable.

How are locations placed in the XML?

Supplied nonblank lines receive XML escaping in their location elements, whereas the empty-input fallback uses a separate unescaped insertion path.