Ecommerce SEO + rebuild / Client identity withheld
A store rebuilt.
From about $20k to over $200k a month.
MooseRank reports this growth in monthly store revenue, in USD, over nine months for an anonymous peptide ecommerce client.
The engagement combined SEO with a move from WordPress and WooCommerce to a custom Next.js site backed by MedusaJS. The new setup allowed agents to deploy site updates.
The reported change
Nine months.
Two revenue endpoints.
A separate search signal.
The reported monthly store-revenue level grew from around $20,000 to more than $200,000 USD during the engagement. The starting figure is approximate and the ending figure is a lower bound.
The figures describe reported endpoints. No intermediate monthly results or cumulative nine-month revenue are reconstructed.
Confirmed delivery / The platform change
WordPress + WooCommerce
to Next.js + MedusaJS.
MooseRank rebuilt the client's store as a custom Next.js website and added MedusaJS as the commerce backend. This is the architecture supplied by the owner, shown without identifying the client.
WordPress
WooCommerce store
Next.js
Custom website / storefront
MedusaJS
Commerce backend
Agent-driven deployments
Agents could deploy updates to the site.
Architecture illustration based on the reported implementation. It is not a client screenshot or a complete infrastructure diagram.
What changed operationally
A site agents
could update and deploy.
The owner identifies agent-driven deployment as a capability enabled by this rebuild. Site updates could be delivered through agents, connecting the custom website to the way MooseRank implements ongoing work.
That makes implementation part of the campaign story: the website was rebuilt to support the delivery model, alongside the SEO engagement.
For a new store, we assess the platform, access, deployment process and implementation responsibilities before recommending a change. A rebuild needs a business case; this example does not mean every WooCommerce store should migrate.
Source and measurement
Keep the growth
beside its context.
MooseRank's owner supplied the revenue endpoints and nine-month timeframe on November 3, 2026, then confirmed USD, the original WordPress/WooCommerce platform, the Next.js/MedusaJS rebuild and agent-driven site deployment capability. The client is unnamed at the owner's request.
- Business context
- Anonymous peptide ecommerce client
- Revenue measure / currency
- Monthly total store revenue / USD
- Reported change / duration
- Approximately $20,000 → over $200,000 per month / Nine months
- Original platform
- WordPress and WooCommerce
- Confirmed rebuild
- Custom Next.js site with MedusaJS as the commerce backend
- Confirmed deployment capability
- Agents could deploy site updates.
Revenue, search data and attribution details
The revenue figures are supplied by MooseRank's owner. A store export, audited statement, gross-versus-net definition, refunds/tax treatment and organic channel breakdown are not published. Revenue is not profit or return on the campaign fee.
The approximately 100-to-3,000 monthly Google Search clicks are a previously supplied account based on Search Console. Its underlying chart/export and exact reporting windows are not published here. Clicks, sessions, orders and revenue are different measures.
Exact campaign kickoff, rebuild launch and endpoint dates are not supplied. November 3, 2026 is the confirmation and publication date. The nine-month duration is not a forecast or guarantee for another store.
Custom ecommerce website design & development
Explore the service behind the store rebuild.
Our ecommerce website service connects Next.js, MedusaJS and agent-driven site updates. Scope the product and category experience, checkout, integrations, migration and ongoing development around your store.
Ecommerce builds receive a custom quote based on the catalog, integrations and implementation requirements.
Explore ecommerce web design & development ↗Website redesign & SEO migration
Explore website redesign and SEO migration.
This case records a confirmed platform rebuild during the engagement. Our service page explains how a new project is scoped: assess the existing site, plan the replacement, review URL decisions and check the live transition.
Connect the implementation to the planning
Explore the work
behind an ecommerce decision.
These guides explain MooseRank's planning approach. Their examples and competitor studies are separate from this client's implementation record.
Catalog architecture
Categories, filters and preferred page owners.
Read the catalog guide ↗Product-page evidence
Product facts, documentation and useful purchase paths.
Read the product guide ↗Commercial search intent
Separate product, category and informational decisions.
Read the keyword guide ↗Migration planning
Review the search paths a rebuild needs to preserve.
Read the migration guide ↗Questions about this account
The practical details.
What growth does MooseRank report?
MooseRank reports that monthly store revenue grew from approximately $20,000 USD to over $200,000 USD within nine months. These are reported endpoints for total store revenue, not cumulative nine-month sales or an audited organic-revenue figure.
Which platforms were involved in the rebuild?
The store started on WordPress and WooCommerce. MooseRank rebuilt it as a custom Next.js site and added MedusaJS as the commerce backend. The owner confirms that the resulting setup allowed agents to deploy updates to the site.
What did the new setup enable?
The owner confirms that the custom Next.js website and MedusaJS commerce-backend setup allowed agents to deploy site updates. This connected the rebuilt store to an agent-driven implementation process during the engagement.
What search growth is reported?
MooseRank previously reported approximately 100 to 3,000 monthly Google Search clicks over nine months for this peptide client, based on Google Search Console. The underlying export, exact comparison windows and chart are not published in this case. Search clicks are distinct from visits, orders and revenue.
Can the revenue increase be attributed entirely to SEO or the rebuild?
The supplied account does not isolate the contribution of SEO, the platform rebuild, agent-driven updates or other trading factors. It reports total store revenue during the engagement. Organic-attributed purchases, profit and incremental revenue are not quantified.
Why is the client anonymous, and when did the campaign run?
The client cannot be named publicly. The case therefore omits its name, domain and identifying store screenshots. The owner supplied a nine-month duration; exact kickoff, launch and reporting-period dates are not published. November 3, 2026 is the account-confirmation and publication date.
Your catalog / Your platform / Your starting point
What is holding
your store back?
Bring your catalog, platform, current search data and available purchase reporting. We will discuss the opportunities, implementation scope and measures that fit your store.
Explore our ecommerce SEO service, website design and development, peptide-company SEO offer and delivery process. Ecommerce work receives a custom quote; this client's campaign fee is not published.