How I Built a Research-First Lavender Oil Guide with Static HTML and Cloudflare

I wanted to take one niche keyword through the entire site-building pipeline: research, information architecture, development, deployment, and Google indexing.

The subject I chose was lavender essential oil. Search results were full of broad health articles and product pages, but the evidence, practical instructions, and safety limits were scattered across many sources. That led me to build Lavender Essential Oil Benefits as a free educational site.

The stack

• Semantic static HTML
• Custom CSS and vanilla JavaScript
• Cloudflare Workers Static Assets
• Responsive English and Simplified Chinese pages
• XML sitemap, canonical URLs, hreflang, Open Graph, and article structured data
• Research manually reviewed against PubMed and other primary or authoritative sources

I deliberately avoided a framework. The site is small, most pages are editorial, and static HTML keeps the deployment simple and the rendered content immediately available to crawlers.

The page strategy: one page, one clear question

Instead of trying to make every page rank for the broad phrase "lavender essential oil benefits," I created focused pages around specific search intent.

One example is this guide:

👉 Lavender Oil for Hair: Human Studies, Uses, and Safety

When I researched the topic, my keyword tool estimated difficulty in the low 20s and roughly 500 searches per month. Those numbers are only estimates, but the search intent was much clearer than the broad head term.

The page answers a single question thoroughly:

• What human studies have actually tested
• Why results from a multi-oil formula do not prove that lavender alone grows hair
• A conservative dilution table
• Patch-testing and stop signs
• A comparison with rosemary oil
• Situations that need professional diagnosis instead of stronger DIY oil

That evidence boundary became one of the most important parts of the project.

Technical SEO lessons from a static site

A small static site can still create indexing problems if URL signals are inconsistent. I ended up checking all of the following:

1. The preferred URL returns 200.
2. HTTP and www variants redirect to the HTTPS apex domain.
3. Each language version has its own self-referencing canonical.
4. English and Chinese pages reference one another with hreflang.
5. The target page appears in sitemap.xml.
6. The homepage and related guides link to the target page.
7. Informational pages use BlogPosting, BreadcrumbList, and relevant FAQ markup—not Product or Offer markup.

That last point mattered. An earlier version of the site had product-like structured data even though the current site does not sell anything. Removing irrelevant commerce markup was better than inventing prices, reviews, shipping policies, or GTIN values just to satisfy a report.

After submitting the sitemap directly in Google Search Console, Google detected all 11 submitted URLs, and the hair guide moved from "crawled, currently not indexed" to indexed.

Content quality was harder than the code

Essential-oil content touches health, so confident wording can become misleading very quickly. I used a simple editorial rule:

• If a claim has human evidence, describe the exact formula and population tested.
• If the study used several oils, do not credit the result to lavender alone.
• If evidence is limited, say so plainly.
• Separate cosmetic or sensory use from treatment claims.
• Put dilution and safety guidance close to the instructions, not in a distant disclaimer.

The result is less dramatic than many wellness pages, but it is more useful and easier to maintain.

What I would do differently

• Choose a shorter domain if the project were not primarily a learning exercise.
• Submit the sitemap in Search Console immediately.
• Build author, editorial-policy, and citation pages before publishing the first guide.
• Design internal links while outlining the content cluster, not afterward.
• Start earning relevant links gradually instead of treating backlinks as a launch-day task.

The biggest lesson was that niche SEO is not only about finding a low-difficulty keyword. The page still needs a clear purpose, technically consistent URL signals, honest evidence boundaries, and a reason for a reader to trust it.

If you are building a small content site with a static stack, what has been the hardest part for you: publishing, indexing, or earning the first relevant links?webdevseocloudflarebeginners