Every page on the site, in one place.

Generally, an HTML sitemap exists for three audiences. Specifically, screen reader users rely on sitemaps to navigate complex editorial sites efficiently. Notably, search engine crawlers use HTML sitemaps as a secondary discovery signal beyond the XML sitemap. And regular readers use them as a fast alternative to navigating through main menus and submenus.

Generally, this page lists every published and planned page on Essential Oils Index. Specifically, the directory below organizes more than two hundred pages into nine sections by topic and function. Notably, status indicators distinguish published pages from pages the team is currently drafting. Live pages link directly. Coming-soon pages show the planned URL with an indicator that the editorial team is preparing the content on a defined schedule.

Generally, the editorial position behind this page fits the broader site approach. Specifically, the site is independent and Utah-based. Notably, the sitemap follows the same direct-naming convention used elsewhere. Brand names, hub topic areas, and sub-page titles appear exactly as they do in the live navigation. Readers familiar with one navigation pattern will find the sitemap easy to scan.

Generally, this page serves multiple reader patterns. Specifically, first-time visitors looking for an overview can scan the section headings. Notably, regular visitors looking for a specific page can use the search-style Top 10 table or the user-intent matrix. Power users tracking editorial progress can review the coming-soon entries across hubs. The structure below supports each pattern explicitly.

Generally, the editorial team revises the sitemap structure whenever the site introduces a new content type. Specifically, the nine-section grouping reflects how the team thinks about the site internally — foundation pages handle credibility, hubs anchor topic areas, sub-pages flesh out each hub, and reference plus legal documents round out the remaining content. Notably, this matches how regular readers think about the site as well, so the internal mental model and the external navigation align.

Generally, the sitemap also doubles as accessibility documentation. Specifically, the page follows WCAG 2.1 AA standards including proper heading hierarchy, descriptive link text, visible focus indicators, and semantic list elements. Notably, the Accessibility Statement page documents the full accessibility commitment and known issues. The sitemap itself is one of the pages that benefits most from accessibility-aware construction.

Generally, the editorial team treats this page as a living document rather than a one-time deliverable. Specifically, the team reviews every link weekly and updates the section structure whenever the site adds a new topic area. Notably, this distinguishes the sitemap from typical pages that publish once and rarely change. The sitemap evolves alongside the site itself.

Generally, reader feedback shapes the sitemap as much as internal planning. Specifically, readers who notice broken links or missing pages send emails that feed directly into the next weekly review. Notably, the editorial team prioritizes fixing reader-reported issues ahead of internal restructuring work. A broken link affects a real reader trying to find something. An internal reorganization affects nobody until it ships.

Generally, the editorial team views this sitemap as a public commitment to coverage and transparency. Specifically, listing coming-soon pages openly creates accountability that less-transparent sites avoid. Notably, readers can compare what the editorial team promised three months ago against what actually published since then. The team accepts this scrutiny willingly because the alternative — hiding the editorial roadmap — produces a worse site over time.

Generally, the directory below is the main attraction of this sitemap. Specifically, the nine sections correspond to the natural structure of the site. Notably, foundation pages handle administrative and editorial credibility. The seven category hubs cover the main editorial topics. Reference pages and legal documents round out the remaining content.

Generally, each entry shows the page title and a status indicator. Specifically, “Live page” means the page exists and the link works. Notably, “Coming soon” means the page sits on the editorial schedule and will publish in the coming weeks or months. Coming-soon entries appear unlinked because the URL does not yet point anywhere. The status updates weekly as new content publishes.

Generally, the sitemap follows a defined maintenance process designed to keep entries current. Specifically, the team checks every link on this page weekly against the live site. Notably, the check produces a delta report that flags new pages awaiting addition to the sitemap, broken links awaiting repair, and entries whose status has changed from coming-soon to live. The team works through the delta before the weekly publish cycle.

Generally, the accessibility standards behind this page draw on multiple authoritative sources. Specifically, the WCAG 2.1 AA guidelines define the technical accessibility requirements. Notably, the W3C Web Accessibility Initiative provides ongoing guidance on how those guidelines apply to specific page types like sitemaps. The Accessibility Statement page documents the full accessibility commitment for the site.

1. Weekly link check — The team verifies every link weekly against the live site URL set. Broken links go on the repair queue before the next publish cycle.
2. Editorial schedule synchronization — The team pulls coming-soon entries directly from the editorial production schedule. When a page moves from drafting to published, its sitemap status updates within the same week.
3. WCAG 2.1 AA accessibility audit — The team reviews the page structure against W3C accessibility guidelines. The audit covers heading hierarchy, link text descriptiveness, and focus indicators on each significant restructure.
4. Screen reader testing — The team tests the sitemap with VoiceOver and NVDA periodically to confirm navigation works as expected for users who rely on assistive technology.
5. XML sitemap reconciliation — The team cross-checks the HTML sitemap against the machine-readable XML sitemap at /sitemap.xml to ensure no published page goes missing from either format.
6. Reader-reported issues — Broken links, missing pages, and structural feedback from readers feed into the weekly delta. Reports go to editorial@essentialoilsindex.com.
7. Search Console integration — Google Search Console reports on which pages search engines have indexed. The team investigates any discrepancies between Search Console and the sitemap.
8. Categorization standards — The nine-section structure follows information-architecture conventions for editorial sites. Foundation, hubs, sub-pages, reference, and legal form the natural top-level groupings.
9. URL stability commitment — Published page URLs do not change without redirects. Readers who bookmark this page can rely on the link structure remaining stable over time.
10. Status indicator consistency — The sitemap uses only two status states: “Live page” and “Coming soon.” The team does not introduce intermediate states like “in review” or “scheduled” to avoid reader confusion.
11. Section header descriptions — Each of the nine sections carries a meta line explaining what the section covers. Screen readers announce these for assistive navigation.
12. Editorial review — The editorial team reviews the sitemap monthly for structural improvements alongside the weekly link check.

The sitemap exists to serve readers, screen-reader users, and search engines. Verified readers who notice missing pages, broken links, or accessibility issues should contact the editorial team at editorial@essentialoilsindex.com. The XML version of the sitemap lives at /sitemap.xml for machine consumption. Published: May 2026. Last updated: May 2026. Next scheduled review: June 2026.