Notes · 7 November 2026

What a website builder's sitemap tells you: 8 platforms checked, 4 of them behind an index file

When a builder won't export your blog, the sitemap is the inventory: one file that lists every page the site wants Google to know. On 7 November 2026 we requested /robots.txt and /sitemap.xml on the main domain of eight platforms (curl, following redirects) and counted what came back. These are the builders' own marketing sites, not customer sites: an illustration of how the files are built, not a survey.

What we found

PlatformTypeURLsNotes
WixFlat list10,828Every URL has a lastmod date
SquarespaceFlat list6,3636,276 of them have a lastmod date
JimdoFlat list384No lastmod at all; robots.txt points to /sitemap-index.xml, not /sitemap.xml
GhostIndex20 child sitemapsEach child carries a date
WebflowIndex6 child sitemapsNo dates in the index
WordPress.comIndex1 child sitemaprobots.txt lists 3 sitemaps (main, news, /go/)
FramerIndex2 child sitemapsrobots.txt lists the main one and the marketplace one
GoDaddyUnknownn/a403 for robots.txt and sitemap.xml (bot block)

Three things to take from it

Limits

One request per file, from one machine, on one day. A 403 means a bot filter answered, not that the file is missing. Sizes change daily. We counted child sitemaps for index files but did not open them.

Related

For the posts themselves, see which builders publish a blog feed. And scan your own site for free: Decamp reads the sitemap (including index files), counts your posts and pages, and tells you what it can and can't take before you pay.