Collection Architecture Optimization

Your product pages are optimized. But can AI actually find them?

Most jewelry sites organize collections using filtered pages. They look great to visitors. But when an AI crawler or search engine bot visits your site, it sees nothing — because the filters run on JavaScript, and crawlers don't run JavaScript.

Beautiful Rooms, No Hallways

Think of it this way: you've built beautiful rooms (your product pages), but there are no hallways connecting them. AI systems land on your site and can't navigate from one collection to the next.

When ChatGPT, Google's AI Overview, or Perplexity tries to browse your jewelry store, it doesn't see your carefully curated collections. It doesn't see your "New Arrivals" or "Gemstone Rings" or "Under $200" filters. All it sees is a flat list of navigation labels with no way to click into anything.

That's because filtered collection pages — the ones that look perfect to you when you click "Earrings" or "Sapphire" in your navigation — don't actually exist as real pages with their own web address. They're generated on the fly by JavaScript. No real page means no content for crawlers to read, no links for them to follow, and no way for AI to understand what you sell or recommend it to anyone.

"New research shows 91% of AI citations only appear in one AI engine. Educational and collection-level content has twice the cross-engine visibility of product pages alone. Your collection pages are what travel across AI systems — ChatGPT, Perplexity, Google AI Overviews. Without them, you're invisible in most places AI recommends jewelry."

— Growth Memo research, 2026

How I Know If AI Can Navigate Your Site

I run a test on every client's site using a tool called lynx. It shows me exactly what a crawler sees when it visits your store — with all the design stripped away. Just the text and links. No images, no colors, no layout. Just what AI can actually read.

Before: What AI sees now

A flat list of navigation labels. "Home." "Shop." "About." "Contact." No collection descriptions. No product links. No way to browse deeper.

The crawler lands on your site and hits a dead end. It knows your store exists, but it can't explore it.

After: What AI sees with pillar pages

A structured site with real content. "Sapphire Jewelry Collection — 14 pieces." Descriptions of each collection. Links to every product. FAQ content answering buyer questions.

The crawler can browse your entire store, understand what you sell, and recommend specific pieces.

For most jewelry sites I audit, the before screenshot is almost empty. After we build your collection pages, the same test shows a site that AI can actually navigate, understand, and recommend.

Why Me

I have been designing and selling handcrafted gemstone jewelry for 18 years. Every strategy I offer you, I tested on my own store first.

I built this entire system on my own store, andreali.com, before offering it to anyone else: 11 gemstone guides, nested navigation organized by type, gemstone, and style, and collection-level content pages that give AI a complete map of my inventory.

When I run the lynx test on my own site, it shows deep nested navigation with topical guides, collection descriptions, and links to every product. When I run it on most client sites, it shows a flat list of labels. That gap is what we fix.

The Crawlability Diagnostic

I'll show you exactly what AI sees

Every engagement starts with a crawlability audit. I run the lynx test on your site and send you a screenshot of what AI actually sees when it visits your store. No jargon — just a visual before-and-after that makes the problem (and the fix) immediately obvious.

Two Ways to Work Together

Start with one collection to see the difference. Scale to your full site when you're ready.

Start Here

Single Collection Page

One fully built collection pillar page with real content, internal links, FAQ section, and validated invisible code that tells AI what you sell.

$175

Per collection

Crawlability audit with before screenshot
Collection pillar page with its own web address
200-400 words of collection content in your brand voice
Product grid with real links that AI and search engines can follow
Internal links to product pages, care guide, shipping policy, and related collections
FAQ section (2-3 questions specific to the collection)
Structured data (the invisible code that tells AI what you sell) validated with zero errors
After screenshot showing crawlability improvement
Navigation updated to point to new page

Start with One Collection

Full Collection Architecture

Every collection on your site rebuilt as a real pillar page, plus full navigation restructuring and cross-linking between collections.

$697

All collections (typically 4-6)

Everything in the single collection tier — for every collection
Full navigation restructuring
Cross-linking between collection pages
Site-level crawlability report (before and after)

Get Full Architecture

Best Value

Product Pages + Collection Architecture

Combine Product Page Optimization ($997) with Full Collection Architecture ($697) and save $297.

$1,397

Instead of $1,694 purchased separately

Save $297

This is the full foundation: every product page optimized for AI, every collection page built as a real crawlable page, your entire site cross-linked and structured so AI can navigate, understand, and recommend your jewelry.

Get the Bundle

Not sure where to start? See the FAQ below, or ask me directly.

What a Collection Pillar Page Actually Is

Right now, when someone clicks "Earrings" in your navigation, they land on a filtered view of your products. It looks like a page, but it isn't one. It has no unique web address, no content for search engines or AI to read, and no links that crawlers can follow to your individual products.

A collection pillar page replaces that filtered view with a real page that has:

Every Collection Pillar Page Includes

A real web address — a permanent URL that search engines and AI can index, bookmark, and link to
Collection content in your brand voice — 200-400 words that describe the collection, the materials, the craftsmanship, and who it's for
A product grid with real links — not a JavaScript filter, but real links to every product in the collection that search engines and AI can follow
Internal links — connections to your product pages, care guide, shipping policy, and related collections that help AI navigate your full site
An FAQ section — 2-3 questions specific to the collection (e.g., "What sapphire cuts do you offer?" or "How do I choose between stud and drop earrings?")
Structured data — the invisible code behind your page that tells AI exactly what this collection contains, validated with zero errors

To your visitors, the page looks identical to what they see now — a beautiful collection of your jewelry. The difference is entirely behind the scenes: AI and search engines can finally read it.

Why Collection Pages Matter More Than Ever

The way people find jewelry is shifting. AI tools like ChatGPT, Perplexity, and Google's AI Overviews don't just list links — they recommend specific stores and products by name. When someone asks "Where can I buy handcrafted sapphire earrings?" the AI browses the web, reads your pages, and decides whether to recommend you.

If your collection pages are invisible to crawlers, AI cannot recommend your collections. It might find one product page if you're lucky, but it can't understand your range, your specialties, or your inventory. You become one product mention instead of a store recommendation.

Collection pillar pages fix this. They give AI a structured overview of what you sell, organized by collection, with links to every product. Instead of stumbling onto a single earring, AI can see "this designer offers 14 pairs of sapphire earrings in stud, drop, and hoop styles, handcrafted with recycled gold." That's the difference between being mentioned and being recommended.

Sources: Growth Memo 2026 AI citation research; Menlo Ventures 2025 AI adoption data.

Common Questions

What is a pillar page and why does my jewelry site need one?

A pillar page is a real, permanent page on your website dedicated to a specific collection — like "Sapphire Jewelry" or "Gold Earrings." Unlike filtered collection views that are generated on the fly when visitors click navigation filters, a pillar page has its own web address, its own content, and real links to every product in the collection. Search engines and AI tools can read it, index it, and use it to understand what you sell. Without pillar pages, most of your collections are invisible to AI because the filtered views they replace don't exist as real pages.

Will my website look different to visitors?

No. Your visitors will see the same beautiful collection layout they see now — a grid of your products with collection imagery and descriptions. The change is entirely behind the scenes. The pillar page replaces the JavaScript-filtered view with a real HTML page, but the visual experience stays the same. Your customers won't notice a difference. AI crawlers and search engines will notice a massive one.

How do you know if AI can navigate my site?

I use a tool called lynx that shows exactly what a crawler sees when it visits your site — all the design stripped away, just the text and links. For most jewelry sites, the result is a flat list of navigation labels ("Home," "Shop," "About") with no way to click into any collection. After we build your pillar pages, the same test shows a structured site with real content, real product links, and clear context that tells AI what you sell. Every engagement starts with this diagnostic so you can see the gap for yourself.

How long does this take?

A single collection pillar page is typically delivered within one week. Full collection architecture (all collections plus navigation restructuring) usually takes two to three weeks depending on how many collections your site has. Most jewelry sites have four to six collections, which is a manageable scope. You'll have a crawlability before-and-after report at the start and end of the project so you can see exactly what changed.

Do I need product page optimization first, or can I start here?

You can start here. Collection architecture and product page optimization solve different problems. Product page optimization makes individual product pages more visible and more likely to be cited by AI. Collection architecture makes your site navigable so AI can discover all your products in the first place. Both matter, and they work best together — which is why there's a bundle option — but you don't need one before the other. If your product pages are already well-written and you know your main issue is that AI can't browse your collections, this is the right starting point.