[email protected] — 7322c30c5870bf7209e4e49a9af08325
Same account as bestcryptolawfirms and shelfregistry, i.e. the index-class sites that
deliberately sit off the main agency account (chizhseo, 63245ea296a7dff0afc83bec342dc597).
Note the difference from bestcryptolawfirms: that site is footprint-isolated from
chyzh.agency on purpose. This one is not — it names chyzh.agency as publisher in the footer
and on /methodology/. The account choice here is operational, not an anti-footprint measure.
wrangler caches an account id in node_modules/.cache/wrangler/wrangler-account.json and
ignores CLOUDFLARE_ACCOUNT_ID when that cache is present. In this repo the cache pointed
at chizhseo while the OAuth token belonged to echizhcom, producing a bare
Authentication error [code: 10000] that looks like a token problem and is not.
If a deploy fails with 10000:
rm -rf node_modules/.cache/wrangler
Then re-run with the account id set explicitly.
npm run build
CLOUDFLARE_ACCOUNT_ID=7322c30c5870bf7209e4e49a9af08325 npx wrangler pages deploy dist --project-name=rwalegalindex
First deploy creates the project. Preview lands on rwalegalindex.pages.dev.
Attach apex + www once the domain is registered and its zone is on the same account:
npx wrangler pages project list # confirm the project exists first
Then bind rwalegalindex.com and www.rwalegalindex.com in the dashboard, and add the
www → apex 301 per network convention. Apex is canonical everywhere in this network.
Domain will be under 90 days old. 1–3 deploys per week, batched by wave — see
docs/SITE-OPS-RULES.md. Three sites in this network lost rankings to deploy-spam on young
domains. Run the cross-page conflict scan before every deploy; on this site the highest-risk
conflicts are cost ranges and jurisdiction claims contradicting each other between pages.
No panic deploys. Drops and dips get 14 days of observation before anyone reacts.