Shalom Shawn
Fragments to Light artwork
Post-upload launch order

Indexing Checklist

This page gives the cleanest post-upload order for crawling and indexing the official Shalom Shawn site. It is designed to help search engines, AI systems, and humans discover the main identity pages first, then the catalog pages, then the deeper song-level reference layer.

Core identity pages first5 pages
Core catalog pages next8 pages
Verified release pages4 pages
Verified song pages57 pages
Open indexing JSON Open Reference Center Open Official Links
Step 1

Verify the public crawl files before you request indexing.

These pages and files should open on the live domain first. If they do not load publicly, the deeper release and song layers are harder for search engines and AI systems to discover consistently.

Crawl map

sitemap.xml

Primary list of public pages, release pages, song pages, and machine-readable files published on the site.

Crawl rules

robots.txt

Confirms the site is crawlable and points crawlers to the sitemap.

AI routing

llms.txt

Fast plain-text route for AI systems that prefer a short summary and canonical page map.

Master map

reference-index.json

Machine-readable top-level map of the official identity, catalog, song, and semantic reference stack.

Step 2

Request indexing in this order.

The goal is to teach crawlers the entity layer first, then the catalog layer, then the deep track-level layer. That reduces ambiguity and gives the strongest pages the best chance to become the primary references.

Priority group 1

Core identity and summary pages

Priority group 2

Core catalog and hub pages

Priority group 3

Deep song-level pages

Step 3

Expand carefully into the full song layer.

  • Submit the strongest current song pages first after the core pages are live and stable.
  • Move through the remaining song pages in manageable batches instead of all at once.
  • Keep songs.html, song-pages.json, and the four release pages in the crawl path so the song detail pages stay well connected.
  • If a song page changes materially, update the sitemap date on the next pass so the refresh signal stays clear.
The site already has strong internal links from the songs hub and the release pages. This step is mostly about sequencing discovery, not rebuilding the page layer.
Machine-readable checks

Validate the files that support the deep catalog.

Step 4

Recheck the public signals after submission.

  • Confirm the main pages load with the correct canonical domain.
  • Confirm the reference and JSON files still open publicly after deployment.
  • Recheck the homepage, press kit, official links, reference center, sound themes, music, discography, and songs pages first.
  • Then spot-check the highest-priority release and song pages.
If a page lags

Check the obvious blockers before changing the page.

  • Is the page linked from the site navigation, hubs, or reference pages?
  • Is the page listed in sitemap.xml?
  • Is the page using the canonical `shalomshawn.com` URL?
  • Is the page meant to be indexed, or is it intentionally legacy content like `webapp.html`?
Fast launch route

Open robots and sitemap, request indexing for the identity layer first, then the catalog hubs, then the release pages, then the song pages in batches.

That order gives the site the best chance to be understood correctly before crawlers and AI systems expand into the deeper track-level pages.

Open sitemapOpen Reference CenterOpen Official LinksOpen Songs