Aion Peptides SEO Plan

Why: Checkout is locked until a visitor completes the AI Consultation. Recommending compounds to match someone's goals reads as personal advice, and the gate blocks buyers who already know what they want.

Scope

• Product cards (/, /shop, related products): replace "Consult to unlock" and "Complete a consultation to unlock purchasing" with price, size selector and Add to cart.
• Product page: keep "Verify Location to Purchase" as the only step before Add to cart; make the consultation a secondary text link.
• Remove any consultation-completed flag from cart and checkout logic, client and server.

Acceptance criteria

• A new visitor in a fresh session can add any in-stock product to the cart and reach checkout without the consultation
• The location check still blocks restricted locations
• The server rejects nothing because a consultation is missing (direct Store API test)
• "Consult to unlock" and "unlock purchasing" are gone from the production build output
• Product JSON-LD offers still renders price and availability

Why: Turns the feature from personalized recommendation into catalog navigation, which matches what the consultation page already says it is.

Scope

• /consultation moves to /catalog-finder with a 301. Update nav, footer, sitemap and internal links.

• Results screen keeps its reasoning and adds: "Catalog navigation only. Not a recommendation for human or animal use."

Acceptance criteria

• /consultation returns 301 to /catalog-finder; title "Catalog Finder | Aion Peptides"
• No page contains "recommend the best peptides," "matched to your study" or "AI Consultation"
• sitemap.xml lists /catalog-finder, not /consultation

Why: Proves each buyer certified research use at the time of purchase (BenchGrade's model). Protects the business with processors and regulators.

Scope

• Required checkbox above the pay button, unchecked by default; pay button disabled until checked. Draft text, pending legal sign-off: "I confirm I am 21 or older, that these products are for laboratory research use only, and that I will not administer them to humans or animals."
• Text kept in one constant or WP option with a version id (attest-2026-10-v1).
• WooCommerce Store API: accept the field via ExtendSchema (namespace aion); validate in woocommerce_store_api_checkout_update_order_from_request; 400 if missing. Save _aion_attest_version, _aion_attest_text_sha256, _aion_attest_at, _aion_attest_ip, _aion_attest_user_agent.
• Read-only meta box on the wp-admin order screen; privacy policy updated for IP and user agent storage.

Acceptance criteria

• Checkout can't be submitted unchecked, in the UI or by direct Store API request
• Every new order has all five meta fields
• Changing the text and version applies to new orders only
• Legal has approved the final wording

Why: Performance, Anti Aging, Sleep, Recovery and Wellness describe outcomes for people, on every card and in the Product schema.

• Product owner confirms the category for each of the 21 products.
• Badges, product eyebrow, /shop filters and JSON-LD category read the new names; 301 any live category URL.
• Remove the outcome tags under the COA panel ("recovery," "wellness," "joint-tissue," "inflammation") or replace them with the research-area name.

Acceptance criteria

• No page or JSON-LD uses the old labels as categories
• /shop filters work
• Rich Results Test passes for one product per category
• No product page shows outcome tags such as recovery, wellness, joint-tissue or inflammation

Why: The three testimonials can't be verified (FTC endorsement risk) and mention "anti-aging studies" and "personalized recommendations."

Scope

• Delete the "What researchers say" section and its component.
• No Review or AggregateRating schema until a real review system exists.

Acceptance criteria

• "What researchers say," "Verified Researcher" and "Lab Director" are gone from the build output
• No empty gap in the layout at desktop and mobile widths

Blocked until counsel decides whether RTT-3 stays in the catalog.

Why: The RTT-3 20mg image is served as …/2026/08/secret_peptide_20mg.png, visible in page source and JSON-LD, and reads as concealment.

Scope

• If RTT-3 stays: re-upload as rtt-3-20mg-vial.png, check the 10mg image, alt text "RTT-3 20mg lyophilized research peptide vial," regenerate thumbnails, delete the old media item.
• If RTT-3 is pulled: unpublish both products, return 410 for both URLs, remove from the sitemap.

Acceptance criteria

• "secret_peptide" appears nowhere in source, JSON-LD or the media library
• Either the new image shows, or the URLs return 410 and are out of the sitemap

Why: Every KPI depends on Search Console data, and the baseline has to be captured before changes ship.

Scope

• Search Console Domain property for aion-peptides.com via DNS TXT (covers commerce. and www).
• Submit https://aion-peptides.com/sitemap.xml; import into Bing Webmaster Tools.
• Give the marketing lead Full access; link Search Console to GA4 after AION-109.

Acceptance criteria

• Both verified; TXT record documented
• Sitemap "Success" with 32 URLs in both tools
• URL Inspection result for /products/bpc-157-10mg logged for the baseline

Why: Bing, Yandex and the AI answer engines that rely on Bing's index pick up changes in minutes.

Scope

• Serve the key at https://aion-peptides.com/<key>.txt from Next.js public/.
• On save_post_product, stock and price changes: map commerce.../product/<slug>/ to aion-peptides.com/products/<slug>, queue, and POST batches to https://api.indexnow.org/indexnow.
• Debounce to one submission per URL per 10 minutes; log responses. Later pages use the Next.js revalidation webhook.

Acceptance criteria

• A product update sends one request with the storefront URL and gets 200 or 202
• Bing shows the URL under IndexNow submissions
• Failures are logged, retried once, and never block saving

Why: Organic orders and revenue are the main success metric, and the site loads no analytics tag today.

Scope

• GA4 via @next/third-parties/google or GTM, on every route including client-side navigations.
• Events with items[] (SKU, name, size variant, research-area category, price, quantity): view_item_list, view_item, add_to_cart, begin_checkout, add_payment_info, purchase (order number, value, shipping, USD).
• Dedupe purchase on transaction_id; send no personal data; mark purchase as a key event.

Acceptance criteria

• Full event sequence in DebugView for a test order
• Reloading the confirmation page doesn't double-count
• Test order in Monetization reports within 48 hours with source attributed
• No personal data in any event parameter

Why: Sizes are baked into URLs (/products/bpc-157-10mg). RTT-3 already has two pages competing for one search, and every new size adds another. With 21 product URLs, now is the cheapest time to fix it.

Scope

• WooCommerce: one variable product per compound with a Size attribute. Only RTT-3 has two sizes today; for the rest this is a slug change that leaves room for future sizes.
• Next.js: /products/[slug] on the compound slug; the size selector updates price, stock and COA without changing the URL.
• redirects() in next.config.js with permanent: true, one per old URL (table below).
• Product JSON-LD: url is the compound URL, one Offer per size with its own sku, price and availability.
• Update internal links, the sitemap and canonicals. No links through a redirect.

Acceptance criteria

• Every old URL returns a single-hop 308 or 301 to its new URL
• New pages self-canonicalize; the sitemap lists only new URLs
• Choosing a size updates price, stock and COA; the URL stays the same
• One Offer per size in JSON-LD; Rich Results Test passes
• Request indexing of all new product URLs in Search Console after launch

Why: On mobile, the BPC-157 page takes 10.1 s to show its main content. The LCP element is the product image, an <img> loading a full-size PNG directly from commerce.aion-peptides.com/wp-content/uploads/…. Lighthouse estimates 1.4 MB of savings from modern formats and 0.9 MB from correct sizing. Homepage cards already use /_next/image; the product page doesn't.

Scope

• next/image for the main product image with priority, explicit dimensions (or fill in a sized box) and sizes="(max-width: 768px) 100vw, 50vw".
• next.config.js: allow commerce.aion-peptides.com in images.remotePatterns; images.formats: ['image/avif', 'image/webp'].
• Re-export source PNGs in WordPress at 1200 px on the long side, at most.
• Related-product cards below the fold: lazy-load with a small sizes value.

Acceptance criteria

• Lighthouse mobile LCP 2.5 s or less on BPC-157, GHK-Cu and Glow Blend
• Main image transfers as AVIF or WebP under 150 KB at 412 px width
• CLS stays at 0
• No product page requests an image from commerce.aion-peptides.com/wp-content directly

Why: Home is at 2.8 s and shop at 3.2 s. The LCP element is text, so the delay comes from font loading or an entrance animation, not images.

Scope

• If the hero heading or shop intro starts at opacity: 0 and fades in, render it visible from the first paint.
• Load fonts with next/font (self-hosted, display: 'swap', preloaded); remove render-blocking font links or imports.
• Remove or defer the roughly 27 KiB of unused JavaScript Lighthouse flags.

Acceptance criteria

• Lighthouse mobile LCP 2.5 s or less on / and /shop
• Hero heading visible in the first rendered frame (filmstrip)
• Performance score stays at 90 or higher

Why: The WordPress backend is mostly well-behaved: shop, cart and category URLs redirect to the storefront and send X-Robots-Tag: noindex. A few loose ends remain.

Scope

• Turn off core sitemaps: add_filter( 'wp_sitemaps_enabled', '__return_false' );
• Delete the default "Hello World" post (?p=1) and any sample page.
• Send X-Robots-Tag: noindex, nofollow on wp-login.php.
• Storefront /cart, /checkout and /account are noindex but declare the homepage as canonical. Remove the canonical tag on these pages.

Acceptance criteria

• commerce.aion-peptides.com/wp-sitemap.xml returns 404
• ?p=1 returns 404 or redirects to the storefront homepage
• wp-login.php sends X-Robots-Tag: noindex
• Cart, checkout and account have noindex and no canonical

Why: Every URL in today's sitemap shows the build time as lastmod (2026-10-04T01:36:55Z), so search engines learn to ignore it. One flat file won't scale to 150 pages, and robots.txt has no Sitemap: line.

Scope

• /sitemap.xml becomes an index pointing to /sitemaps/pages.xml and /sitemaps/products.xml; add learn.xml and coa.xml when those sections launch.
• Product lastmod from WooCommerce date_modified_gmt; static pages use their last content change, never the build time.
• Add Sitemap: https://aion-peptides.com/sitemap.xml to robots.txt; keep the AI-crawler rules as they are.
• Use the new product URLs from AION-110.

Acceptance criteria

• Search Console accepts the index; each child sitemap shows "Success"
• Editing one product changes only that product's lastmod
• robots.txt has the Sitemap: line
• No redirected or noindexed URL appears in any sitemap

Why: Google and AI answer engines weigh whether a store is a real, identifiable business. The Organization schema has a name, legal name ("Aion Research"), logo and email, but no address, founding date or profiles. Competitors publish addresses.

Needs from the business: a publishable address (a registered office or registered-agent address is fine), the founding date, official profiles, and optionally a support phone number.

Scope

• Contact and About show the address and support hours (Mon–Fri 9am–6pm PT, Sat–Sun 10am–2pm PT).
• Organization JSON-LD: address, foundingDate, sameAs[], contactPoint.hoursAvailable; telephone only if monitored.
• One business config object feeds JSON-LD, Contact, About, footer and llms.txt.

Acceptance criteria

• The address on Contact and About matches the JSON-LD exactly
• Schema Markup Validator shows the new fields with no errors
• One config change updates every page and llms.txt

Why: The current title carries no trust terms, and the meta description makes two claims the site can't back up: "assayed to 99%+ purity" (IGF-1 LR3 is 98.00%) and "a Certificate of Analysis on every batch" (14 of 21 compounds have one).

Scope

• Title: Research Peptides with Published, Lab-Named COAs | Aion Peptides
• Description: Research peptides assayed by independent third-party labs, with each certificate published and the lab named. Ships to all 50 states, free over $150.
• Matching og:title, og:description and a 1200×630 og:image.
• Keep "99%+ peak purity" only if labeled as a peak figure; replace any blanket "99%+" claim with "purity published per lot."

Acceptance criteria

• Title and description render server-side exactly as above
• No page claims 99%+ for the whole catalog, or a COA for every batch, until both are true
• Link previews show the new title and card

Why: NextGenPeps and BenchGrade both publish what they are and aren't. It's the first page a processor, regulator or careful buyer looks for. Aion's boundary language is spread across About, FAQ and the footer.

Content outline (marketing drafts, legal approves)

• What Aion is: Aion Research, a US supplier of research chemicals to researchers.
• What it is not: not a pharmacy, compounding pharmacy or outsourcing facility (503A, 503B), not a supplement seller, not medical advice.
• Who may buy: 21+, laboratory research only, with the exact checkout attestation text and version from AION-103.
• What support answers: orders, shipping and COAs; never use in people or animals.
• Labeling and US-only shipping; a compliance contact email.

Acceptance criteria

• Live at /compliance, linked from the footer and About
• Attestation text pulled from the same constant as checkout
• Legal sign-off recorded

Why: Testing is Aion's strongest differentiator but exists only in fragments. One page can rank for "third-party tested peptides" and "how to read a peptide COA."

Content outline

• How testing works: independent labs, varying by batch because compounds are sourced domestically and internationally, named on each certificate.
• Methods: HPLC for purity, mass spec for identity, endotoxin where tested; which tests each COA includes.
• Lot numbers: how to read them (for example ABL-BPC-2602) and match a vial to its certificate.
• How to read a COA: an annotated example using the BPC-157 certificate (Freedom Diagnostics, 99.59%).
• What "COA in progress" means: 7 of 20 compounds have no certificate yet, and their pages don't claim one.

Acceptance criteria

• Live at /testing, linked from every COA panel and the footer
• The annotated example is a real Aion COA with lab and lot named
• Counts come from the COA data, not typed copy

Why: NextGenPeps, BenchGrade and PX1 all put a COA library in their main navigation. Aion already publishes PDFs (/coa/bpc-157-10mg.pdf) but has no page listing them.

Scope

• /coa: one row per compound with latest lot, purity, lab, analysis date and PDF, or "In progress." Sortable, filterable by research area.
• /coa/[compound]: lot history, newest first, linking to the product.
• Data from the WooCommerce fields behind today's COA panel; add analysis_date if missing.
• Existing PDF URLs keep resolving alongside the dynamic route; redirect if AION-110 renames them.
• ItemList JSON-LD on /coa; "COA library" in the main navigation.

Acceptance criteria

• /coa lists all 20 compounds (13 published, 7 in progress today), generated from data
• Every old PDF URL still returns the PDF
• A new lot in WooCommerce appears without a code change
• Reachable from the main navigation and every product page

Blocked until the business approves terms and legal reviews them.

Why: BenchGrade's guarantee turns testing into a promise. Aion's refund policy covers only damaged, defective or incorrect items reported within 48 hours.

Terms to decide (proposal)

• Trigger: an ISO/IEC 17025-accredited US lab reports purity more than 2 points below the published COA, or an identity mismatch, for the same lot.
• Remedy: refund of the order total and lab fee, up to a cap the business sets.
• Window: within 60 days of delivery, with the lab's report and lot number.

Scope (once approved)

• /guarantee with plain-language terms and how to claim.
• "Covered by the Aion Lab-Test Guarantee" beside Add to cart.
• /refund-policy references the guarantee.

Acceptance criteria

• Terms approved and recorded
• Linked from product pages, footer and /testing
• Refund policy and guarantee don't contradict each other

Why: Aion's llms.txt is already better than any competitor's. It needs the week 1–3 changes and should be generated from data so it never goes stale.

Scope

• Serve /llms.txt from a route handler using the product data and business config.
• New compound URLs from AION-110, with prices by size.
• A "Trust and testing" section linking /compliance, /testing, /coa and /guarantee, with the current COA count.
• Keep the "Important product boundary" section word for word, and the note about the former Las Vegas and Henderson courier service.

Acceptance criteria

• Returns text/plain, no links to redirected URLs, every published product listed
• A price change in WooCommerce updates it on the next revalidation
• The product boundary section is unchanged

Why: The nine-part template needs structured fields. Today a product has a description, price, stock and a COA record; everything else is free text or missing.

Acceptance criteria

• All fields editable in wp-admin, returned through the API, typed in Next.js
• Handling fields containing dose terms are blocked with a clear message
• Products with only today's data still render
• A one-page editor guide covers each field and the Ground rules

Why: Only the Description tab is in the server HTML, which caps the value of every other Phase 2 ticket.

Scope

• All panels in the initial HTML (hidden panels use CSS or hidden, not client fetches).
• Move any client-side tab fetch into the server component.
• Prefer the long-form layout from AION-124 over tabs.

Acceptance criteria

• curl of a product page contains the overview, COA lot and lab, and storage text
• URL Inspection "View crawled page" shows the same content
• CLS stays 0 when switching tabs

Why: Product pages are the purchase-intent pages that matter most, and today they're thin.

Scope, in page order

• Title [Compound] Research Peptide [sizes] | [lot purity]% HPLC, Lot COA | Aion, for example BPC-157 Research Peptide 10mg | 99.59% HPLC, Lot COA | Aion; meta from the overview's first sentence plus "Lot COA from [lab]."
• Above the fold: H1, size selector, price, stock, ship-by, purity with date and lab, COA link, attestation note, Add to cart.
• Identity block, research overview with model-labeled citations, handling in mg/mL, COA panel (AION-127), server-rendered FAQ, reviewer line (AION-130), related links (AION-128).
• Keep the research-use-only banner and 21+ notice; no outcome tags.

Acceptance criteria

• BPC-157, GHK-Cu and Glow Blend render every section server-side
• Title uses the live lot's purity and updates with the lot
• Mobile LCP stays at 2.5 s or less
• No doses, outcomes or brand-drug names anywhere

Why: Hubs give the site a followable structure and rank for broader searches like "tissue repair research peptides." Aion's /shop is one flat list.

Scope

• /peptides/ overview of the five areas.
• /peptides/[area]/ for tissue-repair, endocrine-gh-axis, cellular-mitochondrial, neuropeptide and metabolic: H1, 150–300 word intro, product cards, "Top guides" (Phase 3), COA link.
• Breadcrumbs Home › Peptides › [Area] › [Product]; /shop filters link to hubs.
• Sitemap plus CollectionPage and BreadcrumbList JSON-LD.

Acceptance criteria

• Five hubs with unique titles and intros
• Every product links to its hub through the breadcrumb
• Hubs in the sitemap; breadcrumbs pass the Rich Results Test

Scope

• Product with additionalProperty for CAS, formula and molecular weight; category = research area.
• One Offer per size with availability from stockBySku and shippingDetails (free over $150, $10 otherwise, US only).
• FAQPage (the gain is AI answers; Google shows FAQ rich results mainly for government and health sites).
• BreadcrumbList through the hub; no Review or AggregateRating yet.

Acceptance criteria

• Rich Results Test passes on three products
• Offer availability matches live stock
• JSON-LD matches visible content exactly

Scope

• Purity, lot, lab, analysis date, test types, and a chromatogram image exported from the PDF.
• The panel follows the size selector.
• "COA in progress" state for the 7 compounds without one, with no purity figure.
• Links to the PDF, /coa/[compound] and /testing.

Acceptance criteria

• Switching size updates the lot without a reload
• No purity claim on the 7 in-progress compounds
• Chromatogram via next/image; no LCP regression

Scope

• RelatedLinks: two comparisons, one guide and the hub, chosen by editors, falling back to the newest page in the same area.
• Related-product cards limited to the same area (four maximum), without outcome tags.
• [[product:bpc-157]] link helper so links survive renames.
• Build-time orphan report.

Acceptance criteria

• Every product shows its hub link plus comparison and guide links where they exist
• A slug rename updates every helper link on the next build
• Orphan report in CI lists zero product or hub pages

Scope

• Content edited in WordPress (recommended) so non-developers can publish.
• Guide, comparison and supplier templates: H1, 40–60 word answer box, body, model-labeled citations, reviewer line, related links, last-updated date.
• Comparison pages get a side-by-side identity table from both products' data.
• Hubs stay noindex until they have three pages; new pages join the sitemap and trigger IndexNow.
• Editor checklist: compliance check, reviewer sign-off, two internal links.

Acceptance criteria

• An editor can publish a guide and a comparison without a developer
• New pages appear in the right sitemap and trigger IndexNow
• Hubs under three pages are noindex

Blocked until a named reviewer is recruited.

Scope

• Profile at /about/reviewers/[slug]: name, credentials, affiliation if agreed, bio, reviewed pages.
• "Reviewed by [name, credentials] on [date]" on product, learn and compare pages, only after CMS sign-off.
• Person JSON-LD on the profile; reviewedBy on reviewed pages.

Acceptance criteria

• Profile live with the reviewer's written consent on file
• Bylines only on signed-off pages, with the date
• Schema validates

Type: content (writer plus reviewer), not pointed. Starts in Sprint C once AION-122 ships.

Per compound

• Identity fields checked against PubChem and the COA.
• 300–600 word overview built on the existing description, 3–6 model-labeled citations.
• Storage, solubility and one mg/mL example; 4–5 FAQs; reviewer sign-off.

Order: the 13 compounds with COAs first, starting with the five best sellers (confirm from sales data; likely BPC-157, TB-500, GHK-Cu, the Glow Blend and Tesamorelin), then the 7 without. RTT-3 waits on the legal decision.

Acceptance criteria

• 20 compounds complete (19 if RTT-3 is pulled), each signed off
• Every citation has a working PMID or DOI and a model label
• A spot-check of 5 pages finds no doses, outcome claims or brand-drug names

Checklist

• Full crawl: no 4xx, no redirect chains, no orphans, one canonical per page, unique titles and descriptions.
• Lighthouse mobile on 5 products, 2 hubs and /coa: LCP 2.5 s or less, CLS under 0.1.
• Rich Results Test on 5 products and 2 hubs; curl checks on all 20 products.
• Compliance review signed by the marketing lead; updated sitemaps submitted and key pages requested for indexing.

Acceptance criteria (the Phase 2 gate)

• All 20 compounds on the new template with server-rendered content
• Five hubs and the COA library live and in navigation
• Zero crawl errors and zero orphan pages
• Results attached and signed off by the marketing lead

Why: At 6–8 pages a week, a manual check alone will miss things. PX1's legal page says dosing charts are prohibited while its blog publishes them; this is the safeguard against that.

Scope

• Pre-publish check on title, body, FAQ, meta and alt text.
• Block: dose and administration terms ("dose," "dosage," "mcg per," "IU," syringe "units," "inject," "protocol" for people, "cycle"), brand-drug names (Ozempic, Wegovy, Mounjaro, Zepbound, Rybelsus), human-outcome phrases ("lose weight," "fat loss," "anti-aging," "heal your").
• Warn: "benefits," "results," "side effects," "near me," any GLP-class name. Reviewer must acknowledge.
• Required: 40–60 word answer box, at least one citation with a model label, two internal links, reviewer sign-off.
• Term lists in one editable config; every block and warning logged.

Acceptance criteria

• A page containing "recommended dose" can't be published, and the editor sees what to fix
• Missing answer box, citation or sign-off blocks publishing
• Warnings require a logged reviewer acknowledgment
• Live by Nov 13

Scope

• Looker Studio on Search Console and GA4, segmented by /products, /peptides, /learn, /compare, /suppliers, /coa and trust pages.
• Weekly clicks and impressions by section, top queries, high-impression low-CTR pages, organic orders by landing page, and the KPI table with week-13 and week-26 targets.
• Monday email to the marketing lead.

Acceptance criteria

• All seven segments with data from launch
• KPI table matches the plan
• Monday email arrives automatically

Scope

• /learn/glossary/[term]: one-sentence definition, 100–300 word explanation, related terms and products.
• DefinedTerm and DefinedTermSet JSON-LD.
• Auto-link the first mention of each term on learn and compare pages, never in headings.

Acceptance criteria

• Schema validates
• At most one glossary link per term per page
• Hub noindex until three terms

Scope

• /price-index: cost per mg for about 20 compounds by vendor, monthly median, 6-month trend.
• Entered monthly by hand from public product pages, each price linked and dated; no scraping that breaks a site's terms.
• Methodology section that names Aion as one of the vendors; Dataset JSON-LD and a CSV for journalists.
• Legal review before first publish.

Acceptance criteria

• Monthly update takes under an hour, no developer
• Every price links to its source with the date
• Legal sign-off recorded

Scope

• Monthly list of pages with clicks down 20% or more over 28 days, pages not updated in 90 days, and pages ranking 8–20 for their main query.
• "Last updated" comes from real content edits, not template deploys; refreshed pages show a changelog line.

Acceptance criteria

• All three lists, ranked by clicks lost
• A template-only deploy changes no page's date

Why: Where buyers decide, and where the Peptide Sciences closure left open searches. Page 1 is time-sensitive.

Page 1 uses only verified facts (closure on March 6, 2026, and the company's own notice); circulating reasons and revenue figures are unverified and labeled so. No page names a competitor negatively.

Acceptance criteria

• Page 1 live and requested for indexing by Nov 13
• All 6 pass the linter and reviewer sign-off
• Each links to /coa, /testing and a hub

Acceptance criteria

• Pages 1–3 annotate real Aion COAs with lab and lot named
• Page 6 states Aion's own range honestly (98.00% to 99.98% across published lots as of Oct 3)
• All 12 link to /testing and /coa

Boundary: mg/mL for preparing solutions; storage, stability, solubility. Never doses, syringe units or administration. The linter enforces this.

Acceptance criteria

• All 15 pass the linter
• Page 12 links to the Phase 4 concentration calculator once it exists
• Each links to at least two product pages

Framing: structure, mechanism and literature, never which works better in people. No AOD-9604, RTT-3 or GLP-class pairs.

Acceptance criteria

• Identity table built from data on every page
• Links to both products and one guide
• Pairs 15–20 chosen from data

Each guide targets "[compound] mechanism"; the product page keeps the compound-name and purchase searches.

Acceptance criteria

• Every claim carries its model label; "what the research doesn't show" closes each guide
• Links to its product page and hub
• No guide competes with its product page for the compound name (checked after 4 weeks)

Blends (4): what's in the Glow Blend and how to verify a blend COA; why CJC-1295 and Ipamorelin are studied together; blends vs single compounds in study design; reading a multi-component COA.

Glossary (15): research use only, lyophilization, HPLC, mass spectrometry, net peptide content, TFA salt, endotoxin, CAS number, PubChem CID, retro-inverso peptide, pentadecapeptide, amidation and acetylation, bacteriostatic water, certificate of analysis, ISO/IEC 17025.

Acceptance criteria

• Blend pages use the Glow Blend's real COA
• Each term auto-links from at least three pages

First edition January 18, 2027, then the third Monday of each month: Aion plus five or more US vendors with public pricing, each price linked and dated, with a short "what changed" note pitched to newsletters in Phase 4.

Acceptance criteria

• Published on schedule, every price sourced and dated
• Legal sign-off on the first edition

Using the AION-134 dashboard, compare clusters against the week-13 targets (80 indexed pages, 5 of 21 products in the top 10).

• Shift effort to the clusters gaining impressions fastest
• Choose comparison pairs 15–20 from real queries
• Set the pace for weeks 14–20 (four or eight pages a week)
• Retire planned pages with no search demand

Acceptance criteria

• A one-page review in the doc with the reordered backlog
• Week-26 targets confirmed or reset with evidence

Why: No competitor publishes aggregate test results, failures included. It is the asset most likely to earn links, and it turns Aion's "14 of 21" candor into a strength.

Scope

• Store every lot tested, including rejected lots: status, reject_reason, tests_run, lab, analysis_date.
• /reports/coa-transparency/[year]-q[n]: lots tested, published and rejected by compound; purity histogram; labs used; endotoxin results; identity confirmation rate; methodology and plain-language summary.
• Server-rendered charts; Dataset JSON-LD; CSV of lot-level data.
• First edition covers lots through Dec 31, 2026 and publishes Jan 25.

Acceptance criteria

• Every number generated from COA data
• Rejected lots included in the counts
• CSV matches page totals
• Marketing lead and reviewer sign off each edition

Why: Free tools earn links from lab guides and educators for years, and the lab handling pages need them.

Scope

• /tools/peptide-molecular-weight-calculator: sequence plus modifications to average and monoisotopic mass, formula and residue count; one-click load of Aion sequences.
• /tools/solution-concentration-calculator: mg and mL to mg/mL, µM and mM; reverse mode; dilution (C1V1 = C2V2).
• Guardrails: no syringe units, no dose fields or labels, no per-day or per-kg outputs.
• Client-side math with a server-rendered explanation and worked example; WebApplication JSON-LD; optional embed with attribution link.

Acceptance criteria

• Molecular weight within 0.1 Da of PubChem for five Aion compounds
• Concentration math unit-tested
• No syringe units or dose language anywhere
• Live by Dec 18 and linked from lab handling pages

Why: Every live competitor runs one, and it is NextGenPeps' main traffic source. Terms follow BenchGrade (20% on first orders and reorders, 60-day cookie), without PX1's 30% volume tier.

Scope

• Platform: AffiliateWP on the WooCommerce backend (recommended); GoAffPro is the hosted alternative.
• Headless tracking: ?ref=<code> stored in a 60-day first-party cookie and passed to the order through the Store API extension. Canonicals already handle ?ref= URLs.
• 20% of product subtotal after discounts (no shipping or tax) on first orders and every reorder; reversed on refund or chargeback; 30-day hold.
• A 10% first-order code per affiliate that also attributes the order; monthly payouts, $50 minimum, W-9 first; no self-referrals.

Acceptance criteria

• Link and code test orders both credit the right affiliate
• A reorder 90 days later still credits them
• Refunds reverse commission automatically
• Shipping, tax and lab-water lines excluded

Why: Affiliates are where human-use messaging leaks into the category. The program makes the rules clear, every promotion visible, and breaking the rules costly.

Scope

• /affiliates with plain-language terms and an application form; every application reviewed by hand.
• Terms (legal approves): research-use-only messaging only, in every channel including private groups; FTC disclosure and rel="sponsored"; no coupon sites, brand bidding or paid ads in Aion's name; termination and forfeit on violation.
• Partner kit behind login: logos, the transparency report, COA guides, approved descriptions, no outcome copy.
• Monthly referrer and coupon-source report; top 20 referrers reviewed by hand; violations logged.

Acceptance criteria

• Terms approved and accepted before activation
• No auto-approval
• Monthly report runs automatically
• Program opens Jan 11

Scope

• /press: fact sheet from the business config, reviewer bio, latest report and price index, logo downloads, press email as text.
• "Aion in the news" list added by hand.

Acceptance criteria

• Facts come from the same config as the schema and llms.txt
• Linked from footer and About

Why: The KPI is Aion mentioned in 6 of 20 fixed prompts by week 26, which needs repeatable measurement.

Scope

• 20 fixed, versioned prompts ("best US research peptide supplier," "where can I find a peptide certificate of analysis").
• Monthly script through the OpenAI, Anthropic and Perplexity APIs logging mentions, Aion citations, competitors named and full answers.
• Google AI Overviews checked by hand for the same prompts; results feed the AION-134 dashboard.

Acceptance criteria

• December baseline logged before outreach
• Monthly run is automatic apart from AI Overviews
• Dashboard shows mentions and citations per engine

API answers can differ from consumer apps; the trend matters more than any single result.

Why: Aion's own pages disagree today: the homepage claims a COA "on every batch," the About page says 14 of 21.

Scope

• CI check comparing name, legal name, address, founding year, shipping terms, refund window and COA count across config, schema, llms.txt, /press, About, FAQ and policies.
• Quarterly manual check of off-site listings.

Acceptance criteria

• A fact changed outside the config fails CI
• First-run mismatches fixed or ticketed

Scope

• 100+ targets: science newsletters, lab-technique educators, testing communities, podcasts, journalists covering peptide regulation or the Peptide Sciences closure.
• Pitch the calculators (Dec 18), the transparency report (Jan 25), the price index (monthly) and testing guides. Data or tools only, never products or discounts.
• CRM sheet: contact, asset, date, reply, link earned.

Acceptance criteria

• 10 pitches a week from week 10
• 15 referring domains by week 13 and 40 by week 26, or a written explanation

Scope

• One clearly labeled official account per community that allows vendors, run by a named staff member.
• Answers only testing, COA, shipping and order questions; declines questions about use and links to /compliance.
• Legal-reviewed guidelines before the first post.
• Never: undisclosed accounts, undisclosed paid posts, review stuffing, or private groups where dosing talk happens.

Acceptance criteria

• Guidelines approved; every account labeled as Aion
• Monthly log of answers posted and questions declined

Scope

• Register the named reviewer on Qwoted and Featured for comment on testing, COAs and lab quality, never on use in people.
• List Aion in lab-supply and research-chemical directories that check listings, with facts matching the config.

Acceptance criteria

• Profiles on two services with two or more responses a month
• Five or more verified listings, all facts matching

Score every KPI against its target (150 indexed pages, 12 of 21 products in the top 10, 10× baseline non-brand clicks, 25% of orders organic, 40 referring domains, 6 of 20 AI mentions, zero compliance failures), then plan the next two quarters.

Acceptance criteria

• Review page with actual vs target for each KPI
• Next-quarter plan approved by the marketing lead