Launch an AI Tool Directory with Cloudflare Pages, Name.com, and Search Console

1. Start with a small but crawlable site

The site should exist before the domain work starts. In this deployment, the static build already had a homepage, tool profile pages, comparison pages, guides, a robots.txt file, and a sitemap.xml file.

Only source-checked tool pages were allowed into the sitemap. Thin discovery pages remained noindex until they had official sources, update dates, screenshots, and practical notes. This keeps the first version smaller, but safer.

• Use a build command that can run in Cloudflare Pages, such as npm run build.
• Keep the output directory predictable, such as dist.
• Make sure canonical URLs use the final production domain before submitting to Google.

2. Buy the domain without add-ons

Name.com was selected because the checkout supported payment options that were easier to use from China than Cloudflare Registrar in this case. The domain selected was solobuilderstack.com.

The important part of the checkout was removing upsells. Domain Safe Pro, website builders, hosting, email, and extra SSL services were not needed because Cloudflare Pages already provides HTTPS for the deployed site.

3. Move DNS control to Cloudflare

After the domain purchase, the domain was added to Cloudflare as a connected domain. Cloudflare supplied two nameservers, and those replaced the default Name.com nameservers.

Cloudflare may briefly show a waiting state while nameserver propagation finishes. The practical check is to confirm that public NS records return the Cloudflare nameservers before continuing with the Pages custom domain setup.

• Do not keep registrar parking A records after Cloudflare imports them.
• Let Cloudflare Pages create the final CNAME records during custom-domain activation.
• Keep DNSSEC off until the basic setup is stable unless you already know the registrar and Cloudflare DNSSEC flow.

4. Attach the apex and www domains to Cloudflare Pages

Inside the Cloudflare Pages project, both solobuilderstack.com and www.solobuilderstack.com were added under Custom domains. Cloudflare created the required DNS records and enabled SSL.

The custom-domain screen should show Active for both hostnames before the site is treated as production-ready.

5. Redirect duplicate hosts to the canonical domain

The site should have one preferred host. In this setup, https://solobuilderstack.com is the canonical domain. The www host and the temporary pages.dev host were redirected to that domain with 301 redirects.

Cloudflare Pages _redirects is useful for path-level redirects inside a project, but host-level redirects for www and pages.dev are better handled with Cloudflare Bulk Redirects.

• Redirect https://www.solobuilderstack.com to https://solobuilderstack.com.
• Redirect https://solo-builder-ai-stack.pages.dev to https://solobuilderstack.com.
• Enable preserve query string, subpath matching, and preserve path suffix.

6. Verify Search Console and submit the sitemap

Google Search Console domain verification succeeded through Cloudflare DNS authorization. After verification, the sitemap URL was submitted as https://solobuilderstack.com/sitemap.xml.

The first sitemap result briefly showed a fetch issue, then changed to Success and discovered 14 pages. That delay is normal enough that it should not trigger a rebuild unless the sitemap URL itself fails in a browser or command-line HTTP check.

7. What to do before monetization

A domain, deployment, and sitemap do not create traffic by themselves. They only make the site eligible to be crawled and measured. The next work is editorial: add original tool testing, screenshots, update dates, and comparison logic that helps a reader make a decision.

AdSense and affiliate links should wait until the site has original content, clear navigation, and enough Search Console data to identify pages with impressions or clicks. Applying too early adds compliance work before there is meaningful revenue potential.