Draft a small sitemap from up to three supplied URLs, with XML values escaped automatically. This tool does not crawl your site or validate addresses; review the output before deployment.
The XML sitemap generator formats up to three supplied URL entries into a basic urlset document. It does not visit your website, discover links or export every route from a database. Begin with a reviewed list of the pages intended for this small draft. A site with dozens of pages needs a maintained inventory and an appropriate generation workflow rather than the assumption that entering the homepage will make this form find all the others automatically.
For each selected page, identify the actual preferred public address and verify it through your normal site workflow. The generator does not detect redirects, duplicate routes or unavailable content. Keep the inventory associated with the draft so a reviewer can see why each address is present. Correct XML structure alone is not enough to make an arbitrary collection of addresses a useful representation of the content your site intends to publish and maintain.
Each of the three rows has a URL field, date field, change-frequency control and priority field. A row is included when its URL value is non-empty; the function does not trim and validate the address first. A whitespace-only value can therefore produce an unhelpful location entry. Blank ordinary URL fields are skipped, and the function still creates the surrounding XML wrapper even if no usable page entries were supplied.
For a basic sample, enter “https://example.com/guide” in row one and leave the other URL fields empty. The output contains one url block with a loc and a priority value. Additional date or frequency values can add their corresponding elements for that included row. Check the actual result rather than assuming every visible control is mandatory or that a generated wrapper proves the document includes the pages you intended to list.
A supplied date becomes the lastmod value for its row. The tool does not inspect a page's modification history or choose a date for you. Use a date that accurately reflects the relevant content change rather than automatically setting every entry to the day you generated the file. The date field helps format your input, but the meaning and truthfulness of that value remain part of your site's content-maintenance process.
If you do not have a reliable date, review whether to omit it rather than inserting an invented one to make the sitemap look complete. The function omits lastmod for an empty date field. Keep the source of any supplied date with the inventory when dates are part of a review. Google describes lastmod as useful when it is consistently accurate, so a mechanically refreshed timestamp is not a substitute for a real record of meaningful page updates.
The first row's frequency control starts with daily, while the optional rows can start blank. The function includes changefreq only when the corresponding control has a value. Priority uses the entered string or the fallback 0.5 when the field is empty. It does not verify that a supplied priority is numeric or within the protocol's range. An out-of-range value can therefore appear in the draft without an alert.
Do not treat a high priority or a frequent update label as a command that forces better ranking or immediate crawling. Google says it ignores priority and changefreq. These controls are included because the draft format supports those elements, not because the generator can make promises about how every consumer schedules visits. Choose any supplied values deliberately, validate the resulting format and keep the page inventory and meaningful update dates as the central information you are maintaining.
The function escapes ampersands, quotation marks and angle brackets in field values before writing them into XML elements. A URL containing an ampersand between query parameters is represented with an entity reference, preserving the original address when the XML is parsed. Keep that representation in the copied file rather than changing it back to a raw ampersand. The output textarea is not an external validation service, so still parse the complete document and review its addresses before serving it to consumers.
XML escaping and URL encoding are related implementation concerns but are not interchangeable edits to apply blindly. Preserve the intended address while representing it correctly inside the XML element. Use a maintained generator or serializer when your real inventory contains complex URLs, many entries or dynamic content. This three-row form is useful for understanding a small draft, but it does not replace the validation, serialization and maintenance requirements of a production sitemap pipeline.
The output starts with an XML declaration and a urlset namespace, then joins the included url blocks. It does not generate a sitemap index, image extensions, video entries or alternate-language structures. It also does not check that a page is reachable, indexable or suitable as a preferred representative. The presence of the standard wrapper is one formatting feature, not evidence that every sitemap requirement or site-specific decision has been satisfied.
For a larger site, connect sitemap maintenance to the actual publishing inventory so additions and removals are reflected deliberately. Repeatedly copying three-row drafts can miss pages or leave stale entries if there is no source of truth. Keep the sample separate from the live automated process when using it as an explanation or test. A complete sitemap workflow needs the right set of addresses and a repeatable update path, not only a page that can display XML-looking text.
The generator does not save, upload or submit the document. After validating the draft, use your normal deployment process to serve the intended file and confirm its public response and contents. Reference or submit the actual sitemap address through the appropriate site tooling. A local output box cannot establish that a search service has fetched a file or accepted every listed entry, and a successful paste into a text editor is not deployment verification.
Use complete intended addresses for the listed locations and keep their relationship to your preferred page URLs coherent. Review any existing CMS-generated sitemap before replacing it with a manually prepared sample. A working larger inventory should not be overwritten merely because a small draft is easier to read. Preserve the previous configuration and verify the live file after an intentional change so omissions can be identified before they become a long-running maintenance problem.
Select Generate XML Sitemap again after changing any row because the separate output is generated on demand. Parse and inspect the fresh document, compare the number of url blocks with your intended entries and test representative addresses. A row with an empty URL is skipped even if its other fields contain values. A populated field is not validated merely because the corresponding element appears, so keep content review and format validation as separate checks.
After deployment, use available sitemap reporting to investigate retrieval or processing issues and keep the inventory current as pages change. Submitting a sitemap is a hint rather than a guarantee of crawling or indexing. The useful outcome is accurate, maintained information about actual pages. This tool helps draft a very small XML document, while page quality, access, URL choices and the behavior of search systems remain outside what the three-row form can certify or control.
No. It formats up to three URLs you supply and does not discover other pages.
The current interface has three rows. Use suitable inventory-based tooling for a larger site.
Ordinary empty rows are skipped, but whitespace-only values are not comprehensively rejected. Inspect the generated locations.
The function supplies 0.5. It does not validate every custom priority value.
No. Do not interpret that field as a crawling command. Google also ignores changefreq and priority values.
No. Use a meaningful, accurate modification date when available rather than the generation date by default.
Yes. XML values are escaped automatically, including query-string ampersands. Keep the entity references in the file and validate the complete sitemap before upload.
Not through the current form. It produces a basic urlset document only.
No. Saving, deployment and submission belong to your separate site workflow.
No. It supplies information for discovery and is not an indexing or ranking guarantee.