Using a ready-made tool to create a sitemap does not necessarily require coding, but it is not always a ten-minute task. A small site can use a tool to generate a sitemap, while a large site may take hours just to crawl. Adding automatic updates to a custom-built site also involves configuring code and working with the build process. Before estimating the time required, distinguish between an XML list of URLs and an HTML navigation page for visitors, and consider initial creation separately from ongoing updates.
Ten minutes is an estimate for using a tool, not a timeline for every site
Neil Patel’s 2021 article estimates that creating a sitemap with Screaming Frog or Yoast can take less than ten minutes, with a first run through the full process taking up to about twenty minutes. However, the same article also notes that crawling a site can take anywhere from minutes to hours. The author describes working on an e-commerce site with millions of URLs that took hours just to crawl.
These estimates therefore cannot apply to sites of every size. When planning the work, consider at least these tasks separately:
- Tool installation and configuration: if the tool is not installed yet, allow time to set it up.
- Site crawling: the number of pages affects the waiting time.
- Content selection: before generating the XML, you still need to decide which pages to include.
Static sites can use tools; choose the format before compiling a sitemap manually
An answer on Webmasters Stack Exchange describes one approach for static sites: enter the site’s URL and let a tool generate a downloadable XML sitemap. This avoids having to write your own code to generate the sitemap. However, Neil Patel’s example also shows that choosing which pages to include may involve concepts such as noindex and canonical, so “no coding required” does not mean no judgment is needed.
If you want an HTML sitemap for visitors, Semrush’s 2020 article suggests that small sites with no more than one hundred pages can also compile one manually: first list all the pages, then have a developer create an HTML page containing the links. This is a suggested approach for HTML sitemaps, not a page limit for XML sitemaps. Compiling the sitemap manually gives you control over its structure and design, but you must also update it manually when pages change.
Automatic updates can reduce repeated work but still require technical setup
If a site frequently adds content, you need to consider how to update the sitemap as well as how to create the initial file. The forum answer mentioned above notes that dynamic sites can regenerate a sitemap when content changes or generate it on demand when a request arrives. A content management system (CMS) can also handle this through modules or plugins.
A custom-built site may require changes to its build process. An iThome example uses next-sitemap to generate sitemap.xml and robots.txt during the build. The setup includes specifying the site URL, modifying the build command in package.json, and adding the generated files to an ignore list. This approach requires knowing how to modify project settings and run builds, so the ten-minute estimate for using a plugin cannot simply be applied to it. The example provides no estimate of development time, so it cannot support a promise about how quickly a sitemap can be implemented on a custom-built site.
Creating a sitemap: perspectives from across the web
Do you have to have a Google Search Console account to create a sitemap?
Not necessarily. One forum contributor says that creating a sitemap requires a Google Search Console account. However, another example of a tool for static sites describes only entering the site’s URL, generating an XML sitemap, and downloading it, without listing an account as a prerequisite. Creating a sitemap and submitting it to a search engine should be considered separately; the requirements of a particular workflow should not be treated as prerequisites for every site.
Does a sitemap generated by a plugin still need adjustments?
Start by checking the sitemap generated with the default settings, then adjust it to suit the site’s needs. Neil Patel’s 2021 article describes Yoast’s default sitemaps as generally quite comprehensive and uses the exclusion of non-public pages to illustrate how they can be customized. However, this advice concerned a particular plugin at that time. It does not mean that every tool’s defaults suit every site, and it should not be treated as up-to-date instructions.
References
- SEO Tips When Creating a Site Map?www.warriorforum.com — Discusses: Do you have to have a Google Search Console account to create a sitemap?
- Sitemaps HTML and otherswebmasters.stackexchange.com — Discusses: Do you have to have a Google Search Console account to create a sitemap?
- How to Create an SEO-Boosting XML Sitemap in 20 Minutes (or Less)neilpatel.com · 2021-09-30T22:00:00+00:00 — Discusses: Does a sitemap generated by a plugin still need adjustments?
- 使用 next-sitemap 生成 Sitemap - Modern Next.js Blog 系列 #18ithelp.ithome.com.tw — Source used in the article above.
- HTML Sitemap: The Benefits for SEO and Userswww.semrush.com · 2020-12-17T14:29:00Z — Source used in the article above.
