How to get Google traffic to a public Discord storefront

Why Buyer Discovery Needs Both Discord Commands and Public Web URLs

/store, /products, and /buy serve people already in the server. The public store page is the URL you can share and the URL Google can read. You need both.

Optimizing Your Storefront Slug, Product Titles, and Descriptions

Name the product the way a buyer would search: the script, the template, the role, the price context. A title like 'test product 2' will not rank and, if the store looks like a test, Cartcord keeps it out of the index.

Using Store Documentation Pages to Rank for Setup and Troubleshooting Keywords

Install steps, supported versions, and refund rules are the pages people search after they buy, and sometimes before. Pro and Enterprise can publish those docs.

Using Coupons and Free Claims to Drive Community Traffic

A launch coupon or a 100% claim on Pro gets members to try the product. It does not replace a clear public page. Use both.

Written by the Cartcord team that builds the Discord store bot, PayPal checkout, and delivery pipeline.

The public URL is the page Google can read

Slash commands are for members who are already in the server. Google cannot run /buy. The public storefront and the doc pages are the URLs a search engine can fetch. Use a readable slug, a product title that says what the file is, and a description that says the price, the delivery, and who it is for. A title like 'pack v3 final' does not rank. 'QBCore police MDT script' can. Cartcord does not guarantee a ranking. It gives you a stable URL, a single H1 on the marketing pages, and docs you can write in full sentences.

Test stores should not be in the index. Names that contain test, demo, sandbox, sample, temp, or example, stores with no active products, and stores with no PayPal are marked noindex and left out of the sitemap. A real store with products and PayPal can be indexed. The footer badge on that storefront points back to Cartcord so a buyer who likes the shop can open their own.

Docs and coupons are the long-tail and the share

A doc page titled with the install problem people search for is more useful than another homepage paragraph. Pro and Enterprise include those docs. Write the steps you already paste in tickets. Coupons and free claims are how a launch post spreads inside Discord. They are not a substitute for a clear product title. The announcement generator can draft the Discord message. The public URL in that message is what a search engine, and a member who is not online yet, can open later.

Plans stay server-wise. Free is $0 with 3 products and 3 orders a month, which is enough to prove one offer. Basic is $29.99 with 25 products and 100 orders. Pro is $59.99 with 150 products, 1,000 orders, coupons, themes, and store docs, and it is the plan most active stores should use. Enterprise is $129.99 with unlimited products and orders, fraud guard, and signed webhooks. None of those prices is a percentage of the sale. PayPal's own processing fee still applies, and Cartcord does not hold the payout. Buyers browse and start checkout with /store, /products and /buy; web purchase recovery is available through Your purchases. There is no cart command and no extra checkout command. They can also open the public store URL. After PayPal captures the payment, delivery is a file link you host yourself, one unused license key from your pool, a private URL, a Discord role granted once, or a manual order that stays pending until staff act. Optional timed passes require an available expiry service; payments do not recur. Basic+ supports private uploads with short-lived signed links or optional 24-hour single-use downloads within the published storage limits.

The operating rules that do not change with the niche

For a public storefront you want search engines to read, the sale is finished only when PayPal has captured the payment and the delivery you configured has been sent. Cartcord takes 0% of that order. The monthly cost is the server plan, not a slice of revenue. PayPal still charges its processing fee, and that fee is between you and PayPal. Cartcord never holds a balance you later withdraw, so Cartcord does not impose a wallet payout schedule; PayPal can still apply fees, holds or account restrictions.

Keep the command list short when you announce a public storefront you want search engines to read. Members run /store to see the shop, /products to browse, and /buy to pay. They can also use the public store URL, which is the address a person outside the server, and a search engine, can open. Do not invent a cart command. Do not ask them to open a ticket to pay for something the bot can already deliver. Tickets stay for support and for the rare order you marked as manual.

Delivery for a public storefront you want search engines to read is one of five setups. A file uses an external URL or a Basic+ protected managed version. Managed uploads allow 25 MiB per file and 250 MiB reserved storage per store. A license key is one unused line from the pool, and a resend repeats that same line. A private URL is a link. A role is granted after capture. Optional timed passes require a live expiry service and are paid once, without recurring billing. A manual order stays pending and pings staff with the buyer details and the instructions you wrote. Publish guard is what stops the product going live while PayPal, the delivery, or the stock is missing.

Pick the plan from the order count, not from a feeling about the niche. Free covers 3 products and 3 orders a month. Basic is $29.99 for 25 products and 100 orders. Pro is $59.99 for 150 products and 1,000 orders, and it adds coupons, themes, store docs and scoped merchant API keys. Enterprise is $129.99 when you need unlimited volume, fraud guard, and signed webhooks. The example of 10% on $5,000 is a $500 scenario input, not a statement of any vendor's current rate. Pro is $59.99 and none of the $5,000. Use the fee calculator for your own sales number, and read pricing before you promise a buyer a feature that sits on a higher plan.

When a public storefront you want search engines to read is live, check three things after the first real payment. The PayPal capture should show on the order. The delivery status should show sent, or pending if the buyer's DMs were closed. The public store URL should be the same shop the commands show, so a member who shares the link is not sending people to an empty page. If a name looks like a test, a demo, or a sandbox, or the shop has no products, that storefront is noindex and stays out of the sitemap. A real shop with products can be indexed. From any of these guides you can open pricing, the fee calculator, and the solution pages linked under the article.

A clean launch for a public storefront you want search engines to read is a short announcement, not a new website. Name the server, list the three products with their prices and whether the buyer receives a file, a key, a link, or a role, and tell them the commands. The announcement generator on the tools page drafts that message. The fee calculator puts a percentage marketplace next to the flat plan so the owner can see the year, not just the first sale. Pricing is the page that states Free, Basic, Pro, and Enterprise without a sales adjective doing the work. Those three links are the next step after this article, and they are the same facts the rest of the site is willing to stand behind.

Buyer recovery, refunds and feature boundaries

Use Your purchases with the original Discord login to recover eligible content. A paid order can have failed, pending or held delivery. Fix the underlying issue and retry the existing order instead of charging again. Basic adds protected file versions, Pro adds API keys for product/order reads and non-key stock updates, and Enterprise adds risk review and signed webhooks.

The merchant issues refunds in PayPal. Verified completed partial refunds preserve access; cumulative full refunds close new delivery access and queue eligible saved role removals through the scheduled access service. New recovery/staff bot commands still have a separate rollout. Existing signed links and downloaded copies cannot be universally recalled. Signed license verification with device limits is available only after developer integration. Optional single-use downloads protect managed uploads, not external URLs. Timed passes require a ready expiry service and are blocked for new setup while it is unavailable. Pro+ creator referrals issue store coupon rewards after qualifying paid delivery; they do not create cash balances or automatic payouts. Basket checkout, component bundles, recurring buyer billing, seller Stripe/crypto checkout, game-server command delivery and automatic booking are not released.

Verify the page that a crawler actually receives

Open a product URL directly in a new browser tab and inspect its initial HTML. The title, description, canonical URL, visible product copy, and structured data should identify that product. A JavaScript app that serves the same homepage metadata on every URL can confuse a social preview even when the browser eventually shows the correct page. Cartcord's build pipeline emits public HTML and excludes ineligible storefronts from the sitemap. The deployment still needs to serve those files before its general single-page-app fallback.

Treat translated pages as a complete set. Each language needs its own readable content and canonical URL, with reciprocal hreflang links to the other published versions. A language flag alone does not translate a listing. Merchant-authored names and descriptions remain the merchant's content, so write those for the intended audience. After publication, inspect representative URLs in Search Console and compare submitted sitemap entries with indexed pages. A valid sitemap helps discovery; it is not a promise that Google will index every product or award a particular ranking.

Frequently asked questions