HTML Sitemaps: When a Page List Still Helps Your SEO

HTML sitemaps are ordinary web pages that list links to the important pages on your site, and on some sites they still help Google and visitors reach pages the menu doesn't show. I'm Marven Salgado, founder of Social Influence in Mascouche, and I build websites for small businesses around Mascouche, Terrebonne and Repentigny. Owners often assume a page list is outdated once the site has a decent menu, and sometimes they're right. On a site with older pages, or with location pages buried a few clicks deep, a simple list can still give Google a way in to what the menu skips.

HTML sitemaps vs XML sitemaps: what each one does for a small business site

HTML sitemaps are pages written for people, and XML sitemaps are files written for search engines; a small business site can use both, because each one does a different job.

An XML sitemap is a plain file built for crawlers like Google's. It lists the URLs you want indexed, often with the date each page last changed, and you submit it in Google Search Console. Visitors never see it.

An HTML sitemap is a regular page on your site, with links grouped by category. Someone who gets lost, or who wants an overview of everything you offer, can open it and click straight through to the page they need. Google crawls it like any other page, so each link on it is also a path for the crawler to follow.

The two work side by side. The XML file tells Google which URLs exist. The HTML page puts those same pages within reach of real visitors and gives the crawler internal links to follow.

Google crawling and internal links: where a page list still adds value

Google finds most pages by following links from pages it already knows, so a page list adds value wherever important pages sit outside the menu and nothing else on the site links to them.

Plenty of small business sites have a main menu with five or six entries and a lot more pages sitting underneath it: location pages for Mascouche, Terrebonne and Repentigny, older blog posts, service pages added after the site launched. If a page isn't in the menu and no other page points to it, Google may only know about it through the XML sitemap, and a page nothing links to gives Google little reason to treat it as important. An HTML sitemap gives that page a direct link from a page Google already visits. A page list won't improve rankings by itself; it makes the pages you already have easier for Google and your visitors to reach.

Deep, orphaned and location pages that the menu does not reach

Orphan pages are pages with no internal links pointing to them, and they pile up because a menu can only hold so many links before it turns into a mess.

Location pages and old blog posts are the usual cases, along with seasonal landing pages built for an ad campaign that has since ended. The content on them can be perfectly good. Without a link leading to them, Google has a much harder time finding them.

An HTML sitemap gives each of those pages at least one internal link. I treat it as a safety net and don't worry much about how it looks. If you run a separate page for each city or neighbourhood you cover, the sitemap is often the only thing connecting those pages to the rest of the site. Finding the orphans in the first place is part of an SEO audit, where a crawl of the site shows which published pages nothing links to.

When an HTML sitemap adds little to a well-linked small site

An HTML sitemap adds little when your site is small and the menu already links to every page, because Google can reach everything through the menu, the footer and the ordinary links between pages.

Picture a renovation contractor in Terrebonne with fifteen pages, every one of them in the main menu. A sitemap page would only add more links to pages that are already one click away. It won't hurt, but I wouldn't spend much time on it until the site grows past what one menu can handle cleanly. Until then, that time is better spent on clearer page titles, better service descriptions and a few solid links from other sites.

The quality of your internal linking matters more than any list. A service page that links to the cities where you offer that service, or a blog post that links to the service it talks about, tells Google how those pages relate. A list of links on a single page says much less. An HTML sitemap also won't fix thin or duplicate pages, since listing a weak page only gives Google another route to it. If you want a quick read on where your site stands before you decide, run it through the website grader.

WordPress page list structure for bilingual French and English sites

WordPress page lists on a bilingual site work best as two separate blocks, with French pages under one heading and English pages under another, each block organized by service and location.

If every page goes into one long mixed list, visitors have to hunt for their language, and the plan de site HTML stops reading as a clear outline of the site. Inside each block, I group the links the same way in both languages:

French section	English section
Accueil, À propos, Contact	Home, About, Contact
Services (one link per service)	Services (one link per service)
Secteurs desservis (one link per city)	Service areas (one link per city)
Blogue	Blog

Each French entry sits in the same row as its English twin, which makes gaps easy to spot when one language has a page the other doesn't. Give the French list the same care as the English one; with Loi 96 in force, Québec customers should find the French side complete.

You don't need to list every URL. Include your services, your location pages, the main sections and the articles people look for. Leave out thin pages, duplicates and anything low priority, because a list stuffed with every page is harder to use. On a phone, a long list means a lot of scrolling, so keep clear section headings, consider collapsible sections, and split the list into more than one page if it grows very long.

Then link the page from your footer so it's one click away from anywhere on the site, labelled Plan du site on the French pages and Sitemap on the English ones.

Google Search Console checks after you publish the page list

Google Search Console tells you whether Google has found and indexed the new sitemap page, and whether the pages it lists are being crawled.

Start with the URL Inspection tool. Paste in the address of the sitemap page to see whether it's indexed or whether something is blocking it, then click Request Indexing. That asks Google to crawl the page, but it doesn't guarantee when the page gets indexed, or whether it will be.

The pages on the list matter more than the list itself, so inspect a few of the deep ones as well, such as location pages that used to be orphaned, and see whether Google has crawled them since the sitemap went live.

Over the following weeks, open the Pages report under Indexing. If the sitemap page or the pages it lists still show as not indexed, look for a noindex tag, a page blocked by robots.txt, or content Google may see as too thin to index. A link from a sitemap won't get a weak page indexed, so in that case the fix is the page itself.

Maintenance checklist for keeping an HTML sitemap accurate

An HTML sitemap stays accurate when you update it every time you add, remove or merge a page, and run a full check every month or two.

This is the routine I follow:

1. Click every link on the page and fix any broken URL before Google finds it.
2. Compare the list with the pages you have published, since new service pages and blog posts need to appear on it.
3. Remove or update links to pages you've deleted or merged, so visitors and the crawler don't land on a dead end.
4. Check the Pages report in Search Console for listed URLs flagged as not found or redirected.
5. Ask whether the sections still make sense as the business grows, and whether the French and English lists still match.

If keeping the list current is one more job that never gets done, it can be folded into regular WordPress maintenance so someone checks it on a schedule.