How I Built Stars In Hands: A Custom Next.js Personalized Gift Store

TL;DR

Stars In Hands is a custom personalized gift store I built around star maps, moon maps, city maps, combo maps, and memory posters. Instead of using a generic theme and forcing product personalization into app widgets, I built the storefront in Next.js with custom editors, CMS-driven pages, localization, PayPal, Razorpay, structured data, translated sitemaps, and SEO-ready product experiences.

The important lesson is simple: personalized commerce is not just a product page with extra fields. The product editor, preview renderer, checkout flow, translations, fulfillment data, and SEO architecture all have to work together.

What Is Stars In Hands?

Stars In Hands sells personalized printed keepsakes: custom star maps, moon phase prints, city maps, combo maps, and photo memory posters. Customers create a print around a meaningful date, place, message, photo, or life event.

That sounds simple from the outside. Technically, it is a mix of:

• Real-time product customization
• Date, time, and location inputs
• Print-ready preview generation
• Multi-currency pricing
• Multi-language content
• CMS-managed editorial pages
• Payment flows for India and international customers
• Search-friendly product and magazine pages
• Structured data for products, shipping, returns, and breadcrumbs

This is exactly the kind of project where a custom build makes sense. The brand experience depends on the editor, not just the catalog.

Why I Did Not Treat It Like a Normal Storefront

Most ecommerce stores are catalog-first. They show products, variants, reviews, price, cart, and checkout.

Stars In Hands is editor-first. The buying decision happens while the customer is building the gift. They need to believe three things before they pay:

• The map is meaningful and accurate.
• The preview represents what they will receive.
• The checkout will work in their country and currency.

That changes the architecture. The product page cannot be a thin landing page that pushes users to a separate customizer. The editor has to be part of the product experience, and the SEO page has to explain the emotional and technical value without slowing down the customization flow.

Product Pages Built for Search and Buyers

The store is structured around clear product-intent pages, not only a generic catalog. These are the pages I would keep strengthening with internal links, FAQs, comparison copy, and occasion-specific examples:

• Custom Star Map for night-sky prints tied to a date, time, and location
• Custom Moon Map for moon phase gifts around weddings, births, and first dates
• Custom City Map for where-we-met, first-home, travel, and memory-location gifts
• Combo Map for customers who want star, moon, and place context together
• Memory Poster for photo-led personalized keepsakes

Those links matter because Google and AI answer engines need a clean relationship between the case-study content, the commercial product pages, and the informational gift guides. A product page should not sit alone. It should be supported by explainers, comparison pages, occasion pages, and real implementation notes.

The Stack

The core build uses Next.js for the storefront and routing layer. The content layer is CMS-driven so pages like product descriptions, magazine posts, FAQs, materials, shipping, and policy content can evolve without turning every content update into a code deployment.

The important pieces are:

• Next.js App Router for localized storefront routes
• CMS content for product and editorial pages
• Custom product editors for star maps, moon maps, city maps, combo maps, and memory posters
• Location and date handling for personalized inputs
• PayPal for international checkout
• Razorpay for India-first payment coverage
• Localized routes for English, German, French, Spanish, Italian, Portuguese, Dutch, Japanese, and Polish
• Sitemap index with locale-specific sitemaps
• Canonical URLs and hreflang alternates
• Product, Organization, WebSite, and Breadcrumb structured data

The point was not to use a fashionable stack. The point was to make personalization, SEO, and checkout feel like one product.

The Product Editor Is the Product

For personalized gifts, the editor is where trust is created. A customer is not just picking a poster. They are recreating a memory.

The editor needs to support:

• A date that maps to the customer’s event
• A location that feels precise and recognizable
• Optional time input when accuracy matters
• Design choices without overwhelming the user
• Live preview updates
• Mobile-first usability
• Cart data that preserves every personalization choice

The hard part is keeping the flow calm. Too many controls make the gift feel technical. Too few controls make the product feel generic. I kept the product experience focused on the minimum fields needed to create a meaningful print, then moved supporting explanations into SEO sections, FAQs, and magazine content.

Localization Was Built Into the Store, Not Added Later

A personalized gift store can work across countries, but only if localization is treated as more than translation.

For Stars In Hands, localization affects:

• Route structure
• Hreflang tags
• Sitemap entries
• Currency display
• Product copy
• Trust and support pages
• Checkout expectations
• Shipping and return messaging

This matters for SEO and AEO. Search engines need clear language alternates, and AI answer engines need structured, consistent signals about what each page is for. A translated page that canonicalizes incorrectly or omits hreflang can compete with the original page instead of supporting it.

The live site exposes locale alternates for the homepage, product pages, and magazine pages. That is the right base for international organic growth.

Payments: PayPal and Razorpay Together

Payment coverage was a core requirement. PayPal helps with international buyers. Razorpay helps with Indian customers who expect local payment methods.

This creates practical engineering decisions:

• Keep the checkout flow consistent even when payment providers differ.
• Store enough order metadata to reproduce the personalized print.
• Avoid losing personalization data during redirects.
• Keep cart and checkout routes out of the index.
• Make payment availability feel native to the buyer’s region.

For personalized products, the payment is not the only thing that has to be reliable. The personalization payload must survive the entire journey from editor to cart to order.

SEO Architecture

Stars In Hands has a strong SEO foundation because the important public pages expose the right crawl signals:

• Product URLs are indexable.
• Canonical URLs are present.
• Hreflang alternates are present across supported languages.
• The sitemap index points to locale-specific sitemaps.
• Product pages expose Product schema.
• Shipping and return details are included in structured data.
• Breadcrumb schema helps clarify page hierarchy.
• Magazine pages target informational and gift-intent queries.

This matters because personalized gifts are searched in many different ways. Someone might search for "custom star map", "moon phase wedding gift", "where we met map", "newborn keepsake print", or "personalized anniversary gift for couple". Those are not the same intent, even if the same store can serve them.

Page Speed Results

Performance was part of the SEO work, not an afterthought. The public Stars In Hands pages I checked are scoring at or near the top of the range: page speed is around 95, and the key audit categories are at 100%.

That matters for two reasons:

• Buyers on personalized gift pages need a fast editor and a fast preview loop.
• Search engines have less friction crawling and rendering the page when public routes are fast, cacheable, and stable.

For a custom ecommerce build, I care less about chasing a vanity Lighthouse screenshot and more about keeping the product experience fast under real use: product page load, editor interaction, cart preservation, checkout handoff, and image delivery.

AEO: How I Would Make the Store Easier for AI Search

AEO, or answer engine optimization, is not separate from SEO. It is mostly clearer content, better structure, and stronger entity signals.

For a store like Stars In Hands, I would focus on direct-answer sections:

• What is a custom star map?
• How accurate is a star map?
• Do you need the exact birth time?
• What is a moon phase print?
• What is the best personalized anniversary gift?
• What should I write on a star map?
• What is the difference between a star map, moon map, and city map?

Each answer should be short near the top, then expanded below with examples, FAQs, and internal links to product pages.

AI systems need clean extraction. A beautiful page that never answers the question directly is weaker than a page with a clear answer, examples, and product proof. The biggest growth opportunity is not another generic blog. It is publishing pages that match buying intent.

The Best Content Strategy for Stars In Hands

The first content cluster should target people who already want a meaningful gift but are still choosing the format.

I would prioritize these pages:

1. Personalized Star Map Gift for Anniversary: What to Write, Which Date to Use, and Design Ideas
2. Custom Moon Phase Print: How to Find the Moon on Your Wedding, Birth, or First-Date Night
3. Star Map vs Moon Map vs City Map: Which Personalized Gift Should You Choose?
4. Newborn Keepsake Prints: Star Map, Moon Phase, Birth Details, and Photo Poster Ideas
5. How Accurate Are Custom Star Maps? Date, Time, Location, and Common Mistakes

These topics work because they sit between informational and commercial intent. The reader has a real occasion, a real question, and a reason to buy if the answer is useful.

What I Would Avoid

I would avoid publishing broad, generic posts like "Top 10 Gift Ideas" without a strong angle. Those queries are competitive, vague, and usually dominated by large publishers or marketplaces.

I would also avoid thin translated content. If a page is translated, it should still answer the local query naturally. The structure can stay consistent, but examples, phrasing, and gift occasions should feel native.

Finally, I would avoid hiding the customizer behind too many marketing sections. The user should quickly understand the product and start creating.

Technical Lessons from the Build

The biggest lesson is that personalized ecommerce requires a different mental model from normal ecommerce.

In a normal store, the product exists before the customer arrives. In a personalized gift store, the product is created by the customer. That means the application must protect the creative state.

The architecture has to answer:

• Can the customer preview the gift clearly?
• Can the cart preserve the full configuration?
• Can checkout complete without losing personalization?
• Can fulfillment recreate the exact print?
• Can search engines understand the public product pages?
• Can translated routes support international discovery?

When those answers are yes, the store becomes much more than a checkout wrapper. It becomes a product creation system.

Related Work

This project connects to the kind of Shopify and custom commerce work I do regularly:

• Custom storefront architecture
• Product customizers
• International ecommerce
• Payment integrations
• CMS-driven SEO pages
• Performance and structured data audits

If you are comparing custom ecommerce with a Shopify build, the decision usually comes down to control. Shopify is excellent for standard commerce. A custom Next.js build makes sense when the product experience, personalization logic, or checkout requirements are the differentiator.

Frequently Asked Questions

Is Next.js good for a personalized gift store?

Yes. Next.js is a strong fit when the store needs custom product editors, localized routes, CMS content, and SEO-controlled product pages. The tradeoff is that you own more architecture than you would in a hosted ecommerce platform.

Why use both PayPal and Razorpay?

PayPal supports international buyer trust, while Razorpay supports India-first payment behavior. Using both helps the same storefront serve global and Indian customers without forcing everyone into one payment pattern.

What matters most for personalized product SEO?

The product page must explain the gift clearly, answer common buyer questions, expose structured data, and preserve clean canonical and hreflang signals. For Stars In Hands, pages around anniversary gifts, moon phase prints, newborn keepsakes, and star map accuracy are high-value SEO targets.

Should a personalized gift store have a blog?

Yes, but the blog should not be generic. It should answer buying questions: what date to use, what message to write, which map type to choose, how accurate the design is, and what gift works for each occasion.

Is a custom build better than Shopify for this type of store?

Not always. Shopify is better when the store is mostly catalog and checkout. A custom build is better when the product editor, preview rendering, localization, and personalization payload are central to the buying experience.