AI Agent for WordPress vs WordPress AI plugin: Site management or built-in AI features?

Graphic showing WooCommerce product price settings on the left and an AI assistant prompt updating sale prices on the right.

If you open Settings > Connectors on a WordPress 7 site, a banner at the top invites you to install the AI plugin by WordPress, which uses AI to write titles and excerpts from your draft, generate alt text for your images, or suggest meta descriptions. But did you know you can go much further than this with an AI Agent for WordPress, which goes beyond content creation into using AI for actual WordPress management?

AI Agent for WordPress vs the WordPress AI plugin is a comparison between two tools built for different halves of running a site. WordPress’ AI plugin adds AI features to your editor and admin screens, while an AI Agent for WordPress carries out site management through a chat. Both can run at the same time, on one connection.

Key takeaways:

  • AI Agent for WordPress vs WordPress AI plugin comes down to editing versus operating. One helps you produce content in the editor, while the other also helps you with WordPress admin tasks: WooCommerce store management, technical maintenance, and bulk operations across multiple sites.
  • The AI plugin needs its own provider account: install a connector for an AI provider, generate an API key, paste it in, and manage the usage bill. The agent’s connector activates without a key, so there’s nothing to create or maintain.
  • Both can run on one connection. Connect SiteGround AI once, and WordPress’ AI plugin uses it for editor features while the agent handles management, with no provider account or API key of your own.
  • You don’t have to choose. The two sit in different layers with separate settings and separate interfaces, so running both is the setup that matches how many small business owners work.

What each one does today

As with AI plugins and AI Agents as a whole, the shortest way to hold the difference here is this: the official WordPress AI plugin puts AI features inside WordPress screens, and an AI Agent like SiteGround’s AI Agent for WordPress is an admin assistant you talk to.

WordPress’ AI plugin

The official WordPress AI plugin (called AI Experiments until version 0.6.0, which is why older articles use that name) is published by WordPress.org and installed from the plugin directory like any other. Version 1.3.0 arrived in August 2026, and the plugin now has more than 40,000 active installations.

Its features cluster in three places:

  • In the editor, it generates titles, excerpts, slugs, and meta descriptions that pass through to your SEO plugin, translates selected paragraphs and headings, summarizes long posts, suggests categories and tags, offers type-ahead suggestions as you write, and can shorten, expand, or rephrase a passage you’ve selected. 
  • In the Media Library, it writes alt text one image at a time or in bulk, and generates images from your post content. 
  • On the Comments screen, it scores comments for toxicity and sentiment, helps you moderate them, and drafts replies.

For example, a Generate Image button appears next to Add Media File in your Media Library, and Generate Image is added to the Media menu in the sidebar, so creating an image from a description happens in the same place you’d normally upload one.

A screenshot of the WordPress Media Library dashboard with red circles highlighting two Generate Image buttons—one in the left admin sidebar navigation under the Media menu, and another at the top of the page next to the Add Media File button. A top notification banner reads "WordPress 7.1 is available! Please update now." above an alert noting that plugins are requesting access to AI connectors.

The plugin holds no AI account of its own, so you install a separate AI Connector plugin for whichever provider you want (OpenAI, Google Gemini, Anthropic Claude, or Ollama if you’d rather run a local, free option), add that provider’s API key under Settings > Connectors, then go to Settings > AI to switch AI on globally, and only then turn on the individual features you want. Everything’s opt-in, and nothing runs unless you trigger it.

Editorial Notes is the feature that changes a working day. It reviews your post block by block and leaves suggestions on grammar, readability, accessibility, and SEO, and a companion feature applies those suggestions back into the content for you.

Pro tip: Check which editor you use before installing WordPress’ AI plugin. It works in the Block Editor only, and WordPress has said Classic Editor support isn’t planned. If your pages are built with Elementor, Divi, or another builder that relies on the Classic Editor plugin, you can install it, switch every feature on, open a post, and find nothing there. Reviewers on the plugin page have hit exactly this. Open any post and look at how you edit it before you spend time on setup.

AI Agent for WordPress

The AI Agent for WordPress is a conversational AI assistant for WordPress management: rather than clicking through admin screens, you ask for what you need, and it carries out the task. It reaches your site through a plugin called AI Agent by SiteGround, which is what gives it access to your content, plugins, users, and settings. 

Here’s what you can do with the AI Agent for WordPress:

  • Complete content management. You can ask for a post and get the whole thing, written, illustrated, categorized, tagged, and published, from one prompt. Content updates work the same way, and because the agent makes only the change you asked for, your Gutenberg blocks and shortcodes come out the other side intact.
  • WooCommerce store management. Ask it to reduce every price in a category by 20%, and it ripples through the catalog in minutes rather than an afternoon of copying and double-checking. It also finds orders and pulls the customer details, changes order statuses, creates coupons, and answers questions about your sales when you’d rather not build a report.
  • Technical website maintenance. This is the work that keeps a site secure without ever feeling like a good use of your day, and you can hand most of it over. Ask what’s installed and you get a clean audit, ask it to update your plugins and it does, and you can tell it to back the site up first.
  • Managing multiple WordPress sites at once. If you look after more than one site, everything above runs across all of them from a single instruction. Update a plugin everywhere, add an editor to every site, or check who has admin access across a whole portfolio, without logging into each one in turn.

For example, you can ask it to run a full WordPress security maintenance review with one simple prompt, and it produces the lot: what needs updating, which protections are already on and which aren’t, an account setting that’s giving away more than it should, and comments waiting to be checked. It then offers to apply the safe changes for you.

Screenshot of a WordPress dashboard alongside the AI Agent by SiteGround panel displaying a security maintenance review for dimitarganev.com with the status "Overall status: Needs attention."

The same nine tasks, run through both

We set up a test site with WordPress’ AI plugin and AI Agent for WordPress installed together, and asked both for the same nine things:

TaskWordPress’ AI pluginAI Agent for WordPress
Generate a post titleYes, from the Block EditorYes, from one prompt
Create an excerptYes, from the Block EditorYes, from one prompt
Generate image alt textYes, per image or as a bulk action from the Media LibraryYes, from one prompt
Suggest a meta descriptionYes, in the editor or SEO panel when the feature is enabledYes, from one prompt
Summarize several postsYes, as a bulk action from the Posts listYes, from one prompt
Update a pluginNot possible. No plugin-management write abilityYes, from one prompt
Change a user roleNot possible. No user-management write abilityYes, from one prompt
Update WooCommerce pricesNot possible. No WooCommerce write abilityYes, from one prompt
Apply a change to multiple sitesNot possible. No multi-site operation abilityYes, from one prompt

So WordPress’ AI plugin is single-screen assistance: you’re already editing something, you click a button Generate, and it helps with what’s in front of you.

The AI Agent for WordPress is task execution by instruction, where one prompt can trigger a whole workflow, including operational changes, bulk work, WooCommerce tasks, and actions across several sites when those exist.

Governance: credentials, approvals, and what gets logged

For  WordPress AI site management, what each tool is allowed to do matters as much as how good the output is. WordPress’ AI plugin is governed like a feature layer inside your admin, so the controls are about connectors, approvals, logging, key handling, and which experiments you’ve switched on. 

The AI Agent for WordPress is governed like an operator, because it performs real actions on your site, so control shifts to your WordPress roles, the connection you authorized, an activity log, and human confirmation through a feature called Power Mode before anything high-impact runs.

Governance questionWordPress’ AI pluginAI Agent for WordPress
Who can use the connectionA Connector Approvals experiment requires explicit administrator approval before any plugin or theme can use the AI connectors set up on your siteAccess follows your WordPress roles and capabilities through the connection to your AI Studio workspace, and impactful operations are gated by both permission and confirmation
How credentials are protectedA Key Encryption experiment encrypts provider API keys at rest using bundled libsodium. Without it, keys sit in the standard WordPress connector storageNo provider API key is stored on your WordPress site at all. Authentication runs through the AI Studio connection instead
What gets loggedAn AI Request Logging experiment records AI requests, with logs under Tools and a public logging APIActivity and usage records, an activity log you can filter by category, token usage and balance, chat history, and a live view of what the agent is doing
What requires confirmationEvery feature is opt-in and manually triggered, so nothing runs without you asking for itPower Mode is required for high-impact work: deletions, bulk changes, user changes, settings changes, and WooCommerce actions
What happens on a live siteAdds AI features inside the admin and Block Editor. It is not a site-operations tool for plugins, users, prices, or settingsExecutes real changes on the connected site, including creating, editing, publishing, updating, and deleting, which is why the confirmation step exists
Editorial controlGuidelines lets AI features respect site-wide editorial standards you define onceConstraints are set per request, such as brand voice, length, or summarize only and change nothing. There is no site-wide equivalent
Scope of what it can touchIts editor, media, and comment features generate and apply content changes. The five abilities it exposes to outside tools are read-onlyWrite operations across content, media, plugins, themes, users, roles, and settings, plus WooCommerce products, orders, prices, stock, and coupons

Can you use WordPress AI plugin and AI Agent for WordPress together?

Yes, and there’s nothing to configure to make it work. The two sit in different places, so they don’t compete for anything.

WordPress’ AI plugin lives inside your admin, adding buttons to the editor, the Media Library, and the Comments screen. The agent reaches your site through its own connection to AI Studio and works from a chat. They have separate settings, separate interfaces, and separate provider setups, so switching one off leaves the other running. And if you connect SiteGround AI as your WordPress AI provider, the same connection can support both.

Pro tip: Try the agent first, since its connector lets the plugin work without a provider key of your own, and you can connect SiteGround AI to WordPress in about a minute.

AI Agent for WordPress vs WordPress AI plugin: which should you choose?

The right choice depends on where your WordPress work usually happens.

When to choose WordPress’ AI plugin

Choose the official WordPress AI plugin when you want AI built into the WordPress editing experience. It’s best for people who spend a lot of time writing, editing, publishing, and refining content directly in the Block Editor.

Its value is strongest at the moment of content creation. You’re looking at a post, page, image, or comment, and the AI tools are available in that same context. That makes it useful for generating or improving alt text, writing titles and excerpts, creating meta descriptions, summarizing long content, translating blocks, rephrasing selected passages, and getting editorial suggestions for readability, accessibility, grammar, and SEO.

The tradeoff is setup and ownership. You need to be comfortable configuring an AI provider, connecting it to WordPress, managing credentials, and understanding the usage costs that come from that provider. You should also be comfortable testing features before relying on them, since the official plugin is still experimental.

When to choose AI Agent for WordPress for site management

Choose AI Agent for WordPress when the work you need help with is broader than writing or editing a single piece of content. The difference becomes clear with WordPress admin tasks, and they usually involve searching, navigating, checking, changing, and repeating.

The value grows with the size of the job. Updating one plugin manually is quick. Updating eleven plugins, repricing thirty products, finding all draft posts missing excerpts, checking stock across a category, or creating a group of pages is where a conversational instruction becomes genuinely useful. The agent is especially helpful when the task crosses multiple areas of WordPress, such as content, media, settings, plugins, menus, and WooCommerce.

It’s also a better fit for users who don’t want to manage their own AI provider account for every workflow. With the AI Agent for WordPress, the assistant works through AI Studio and the connected WordPress site, so the setup is simpler from the user’s point of view. On SiteGround-hosted sites, hosting-level backups add another layer of reassurance for operational work, especially when updating plugins or making larger site changes.

When to use both

Use both when your WordPress work moves back and forth between content creation and site administration often enough. This usually applies to small business owners, agencies, publishers, and WooCommerce store managers who are not only writing content, but also maintaining the site around that content. If you publish articles, update product pages, manage media, adjust menus, check plugins, create offers, review orders, and improve existing pages, the two tools solve different parts of the same week.

You can use the agent to prepare or organize the work, then use the plugin to refine the content in the editor, then return to the agent for follow-up actions across the site. That creates a workflow where AI is not limited to a single screen or a single type of task.

Match the tool to the work, and consider running both

Comparing AI Agent for WordPress with the WordPress AI plugin comes down to how much of your WordPress work you want AI to help with, and where that work happens. If the work is mainly writing, editing, translating, summarizing, or improving content inside the editor, the plugin can be all you need. If the work extends across the rest of the site, including plugins, settings, products, menus, media, reports, and repeated admin tasks, the agent is the better fit.

For many people running a small business site, the answer may be both. The plugin gives you AI where you create and refine content, while the agent gives you AI where you manage and maintain the site around that content. Because they operate in different parts of the workflow, they can run alongside each other rather than instead of each other.

FAQs

AI Agent for WordPress vs WordPress AI plugin: what is the difference?

The difference between AI Agent for WordPress and the WordPress’ AI plugin is what each one can do to your site. The plugin adds AI features to your editor and admin screens, while the abilities it exposes to outside tools are read-only. AI Agent for WordPress performs operations, including updating plugins, editing products, changing user roles, and adjusting settings.

Which is better for managing a WordPress site?

AI Agent for WordPress is better for managing a WordPress site, because management means changing things and the plugin cannot manage plugins, users, settings, or WooCommerce operations. WordPress’ AI plugin is better for producing content inside the editor.

Is the WordPress’ AI plugin an AI agent?

No. The WordPress’ AI plugin is not an AI agent. It generates and applies content inside the editor, the Media Library, and the Comments screen, but it cannot manage plugins, users, settings, or WooCommerce. WordPress does list a Site Agent on the plugin’s roadmap, but it has not shipped.

Can the WordPress’ AI plugin update plugins, products or users?

No. The WordPress’ AI plugin cannot update plugins, products, or users. It can change content through its editor, media, and comment features, but site management sits outside what it does.

Does the WordPress AI plugin need separate API keys for ChatGPT, Claude and Gemini?

The WordPress AI plugin needs separate provider API keys for ChatGPT, Claude, and Gemini if you connect each provider yourself, since every provider requires its own account, key, and bill. Connecting SiteGround AI instead registers a provider with no API key, and WordPress’ AI plugin can use that same connection.

Can I use WordPress’ AI plugin and AI Agent for WordPress together?

Yes. You can use WordPress’ AI plugin and AI Agent for WordPress together on the same site. The plugin uses the SiteGround AI connector as its AI provider for editor features, while the agent handles site management, so one connection covers both.

Which tool is better for WooCommerce?

AI Agent for WordPress is better for WooCommerce, because store work means creating and editing products, managing orders, and changing prices, which are write operations. WordPress’ AI plugin can help write product descriptions in the editor but cannot update the products themselves.

Which option is easier for a beginner?

AI Agent for WordPress is easier for a beginner, because there is no provider account to open and no API key to generate, and you describe what you want in ordinary language. WordPress’ AI plugin is simple to use once connected, but connecting a provider yourself is the step that stops most non-technical owners.

Where to sell handmade items: How to turn your homemade products into a real business

Abstract of selling homemade products such as jewelry online

Your kitchen table is covered in jewelry, candles, soap, you name it, and everyone keeps asking if you sell it. Time to make that a yes. Selling homemade and handmade products means picking a channel that matches what you’re making, pricing around that channel’s fees, and building toward your own online store once the per-sale cut starts eating into your margin. Start with a low-commitment channel to test demand, then move to your own site once fees justify the switch.

Key takeaways:

  • Marketplaces and your own store solve different problems: one gets you selling online fast, the other keeps more of each sale once fees start adding up.
  • Cost-plus pricing needs to include your time and overhead, not just materials, or you’re not actually pricing a business.
  • If wholesale is ever a real possibility, price for it from day one: a direct-to-consumer price alone can lock you out of a retail deal later.
  • Owning your own store also means owning the customer relationship, since marketplaces typically restrict using buyer data for marketing beyond the platform.
  • Test demand with a small batch, a local pop-up, or a limited listing before committing to a full production run.
  • Most hobby sellers can start as a sole proprietor; forming an LLC can wait until inventory, risk, or income grows enough to justify it.

Here’s the full six-step path, starting with the one decision everything else depends on: knowing you actually have something worth selling.

Step 1: Decide what to make and validate there’s demand

If you already have a product idea, this step tells you whether it’s worth building a business around before you sink money into inventory. Every step after this one assumes you’ve settled on a specific product.

How to spot a profitable homemade product idea

A good homemade product idea hits three marks:

  1. Repeatable to make. You can produce it again and again without the process draining you.
  2. Real margin. Materials, your time, and what it sells for actually pencil out once you do the math.
  3. Existing demand. People are already searching for or buying similar items somewhere.

Jewelry, candles, and soap tend to score well on the margin test because materials cost is low relative to perceived value. That is, a product that takes four hours to make and sells for $15 fails that test even if the other two check out.

Quick ways to test demand before you invest

Testing an idea doesn’t require betting on a full production run. Four low-cost ways to validate first:

  • A local pop-up or craft fair table. A weekend at a market tells you more about real buying behavior than weeks of guessing.
  • A small social test batch. Post a handful of finished pieces on social media or in a relevant community and watch for actual purchase interest, not just likes.
  • A limited marketplace listing. List five to ten units on Etsy before committing to a full production run.
  • A quick, no-code website. Setting up a basic online store lets you test a real product page and checkout without weeks of setup or a full marketplace commitment.

If none of those produce interest, that’s useful information too. It’s cheaper to learn that from ten units than from two hundred.

None of this replaces a lawyer or accountant, but you need to know what to check before you take your first payment. Keep this practical: flag what applies to you, then confirm the specifics for your state and product category.

Do you need a business license or LLC?

Most hobby sellers don’t need an LLC to start slinging handmade items or selling crafts online. A sole proprietorship, which typically requires no separate formation, covers most first-time sellers, and you can add an LLC later once revenue and liability exposure both grow enough to justify it. It starts to matter once:

  • You’re carrying real inventory instead of making pieces to order.
  • You’re shipping fragile products that could cause injury if something goes wrong.
  • Your income changes your tax situation enough to want the legal separation.

Check your state’s requirements and the U.S. Small Business Administration’s guide to business licenses and permits before you assume either way.

Permits and rules that vary by product

Non-food handmade goods like jewelry, candles, soap, art, and home decor generally face far lighter permit requirements than food items, but they’re not permit-free. Most makers in this category need to check a few things regardless of what they’re crafting:

  • A sales tax permit, since most states require you to collect and remit sales tax once you’re selling regularly, whether through a marketplace, at a fair, or from your own site.
  • A home occupation permit or local business license, if you’re producing from home and your city or county requires one for a home-based business.
  • Product-specific safety rules, which vary by category. Candles are covered by an industry fire-safety labeling standard (ASTM F2058) that most marketplaces and retailers expect even though it’s technically voluntary, and soap marketed with moisturizing or other beyond-cleansing claims shifts from the CPSC’s lighter “true soap” category into FDA cosmetic labeling rules.

Cottage food laws, allergen labeling, and health department permits sit in a separate, stricter category that applies specifically to baked goods and other food products, and those requirements shift by state and even by county. If you’re making food items rather than handmade crafts, SiteGround’s bakery website builder guide covers that compliance in more detail.

Step 3: Where to sell handmade items: marketplaces, local, or your own store

This is the decision that shapes everything after it. Your channel determines your fee structure, and your fee structure determines your price in Step 4. There’s no universally “best” option here: it depends on how much traffic you can drive yourself versus how much you’re willing to pay a platform to bring buyers to you.

Selling on marketplaces (Etsy, Amazon Handmade, and alternatives)

Etsy stacks a listing fee, transaction fee, and payment processing to land around 10-13% combined, while Amazon Handmade charges one flat 15% referral fee, and both work better than eBay or Depop for a dedicated handmade storefront. (Fees accurate as of August 2026 — always check each platform’s current seller fee page before pricing.) Those fee percentages are only part of the picture when weighing an ecommerce platform against a marketplace, which also comes down to how much control and traffic you’re trading away.

Selling locally: markets, pop-ups, and consignment

Local selling carries its own cost structure, separate from either marketplace:

  • Craft fairs and markets typically charge a flat booth fee, often $25 to $150 for a weekend, regardless of what you sell.
  • Consignment shops take a percentage cut of each sale instead, commonly 30 to 50%, in exchange for handling the retail floor space for you.

Local selling is a natural extension of the demand testing from Step 1: real buyers, no storefront commitment yet.

Selling from your own website

Your own store has no per-sale marketplace cut. On a typical $16 item, Step 4 works through the exact numbers, but that’s roughly $1.50 to $1.80 more in your pocket per sale than a marketplace takes, before you’ve changed anything about the product itself. A few other things come with owning the storefront:

  • You own the customer relationship. Etsy’s seller policy restricts using customer data beyond Etsy-related communications unless the buyer opts in elsewhere. Your own checkout can capture an email with consent, feeding straight into the repeat-customer tactics in Step 6.
  • You’re not competing in someone else’s search results. A marketplace search for “handmade ceramic mug” returns thousands of sellers ranked by that platform’s algorithm. Your own product pages compete in Google instead, where SEO effort compounds rather than resetting with every algorithm change.
  • You control the presentation. Photography, the maker story, bundling, subscriptions: marketplaces standardize these into a fixed listing format, while your own site builds the page around what actually sells your product.
  • You skip platform-mandated fees on top of your base rate, like Etsy’s Offsite Ads program, which can add another 12-15% on sales it attributes to itself.
Product page of online store that sells homemade products such as clothes

The trade-off: you’re now responsible for driving your own traffic, which is what Step 6 covers. Apparel and accessory makers should check SiteGround’s clothing website builder guide and online boutique guide for category-specific setup; food sellers should use the bakery guide referenced in Step 2 instead.

Step 4: Price your homemade products so they’re actually profitable

Pricing comes after the channel decision on purpose. The same candle needs a different price on an Etsy shop than it does on your own store, because one of those channels is taking a cut and the other isn’t.

A simple cost-plus pricing formula

Cost-plus pricing adds up materials, your time at a real hourly rate, and overhead, then layers a margin on top. Here’s a candle priced that way:

Cost componentAmount
Materials (wax, wick, container)$4.00
Time (20 min at $20/hour)$6.67
Overhead (packaging, utilities)$1.00
Base cost$11.67
+ 40% margin~$16.35
Rounded price$16-17

Skipping the “time” line is the single most common mistake first-time sellers make. If your time isn’t in the formula, you’re not running a business. You’re subsidizing one.

Pro tip: the $16-17 price above works if you’re only selling direct to customers. It falls apart if you also want to sell through shops or boutiques, because retailers who resell your product usually want to buy it at about half of what they’ll charge their own customers, a standard called keystone pricing. That’s where the math gets tight: you can’t just raise your own retail price to make room, since customers won’t pay a wildly higher price for the same candle just because a boutique might carry it someday. In practice, most makers either accept a thinner cut on wholesale orders than textbook keystone, or price a little higher from the start so there’s some room without pricing themselves out of their own direct sales. Decide which trade-off you’re making before a shop asks for wholesale terms, not after.

Factoring in shipping and packaging for fragile items

Breakable goods like ceramics, candles, and glass jewelry need protective packaging: sturdy boxes, void fill, and “fragile” handling labels can add $1 to $4 per shipment depending on item size. Skip it to save a few cents and it comes back as breakage claims, returns, and refunds, all of which cost more than the packaging would have. Build that cost into your product price or charge it separately at checkout. Either way, price it in upfront.

Adjusting your price for marketplace fees vs. your own store’s margins

Take that same $16 candle across three channels:

ChannelFeeYou net
Etsy~10-13% combined~$14.00-14.40
Amazon Handmade15% flat$13.60
Your own store2.9% + $0.30 processing~$15.24

That’s the entire argument for eventually moving toward an owned store: the product doesn’t change, but the channel decides how much of that $16 actually reaches you.

Step 5: What you need to launch your own online store

If you’ve decided your own online store is the right path, the channel comparison and fee math earlier in this guide already told you why. What’s left is a short, concrete list: five things to actually set up before you’re taking orders.

The launch checklist

  • A domain name that matches your brand and is short enough to say out loud. Your business name is the obvious first choice; if it’s taken as a .com, a close variation usually reads better to customers than an unfamiliar extension. Beyond the name itself, buying a domain involves a few checks before and after registering it that are worth getting right the first time.
  • High-performance hosting built for stores. A store handles more simultaneous visitors and heavier pages than a blog, especially around a sale or a feature in someone’s newsletter, and slow load times cost you sales directly: shoppers abandon a cart faster than they’d tolerate a slow blog post loading.
  • A payment processor connected and tested before launch, not after your first sale comes in. Run a real test purchase with a real card before you announce the store, so a broken connection doesn’t surface for the first time on a paying customer.
  • Shipping rates and zones set up to match your actual costs. This matters most for fragile items: a flat rate that doesn’t account for the extra packaging from earlier loses money on every heavier order, so build that packaging cost into the rate itself rather than absorbing it.
  • At least one full product page built and a complete test checkout run, from browsing to confirmation email, so you catch a broken step before a customer does.

SiteGround Ecommerce covers four of these in one place: domain registration, hosting built for stores, direct payment integration so orders don’t need manual reconciling against a separate processor account, and built-in shipping zone and rate tools so you can set different rates by region without a separate plugin. Its built-in AI Store Agent even gets you a head start on the fifth, generating product titles, descriptions, and categories so the test checkout is really all that’s left to do yourself. If you’re weighing it against other options, SiteGround’s guide to the best platforms to create an online store breaks down the tool-by-tool differences.

Step 6: Market your homemade business and get repeat customers

This step matters most if you’re running your own store, since a marketplace’s built-in traffic disappears once you’re on your own site, though several of the tactics below help no matter where you sell. Getting your first sale is the hard part everyone focuses on. Getting your fifth sale from the same customer is where the actual business starts.

Social media and content that actually sells

Short-form video and photo content showing your making process performs unusually well for handmade goods specifically, because the process is the product’s story. A 30-second clip of a juice being made or a ring being soldered sells more than a polished product photo alone, which is the whole logic behind marketing a small business on Instagram: show the making, not just the finished piece.

Abstract of social media marketing of homemade products such as food

Email, local SEO, and other ways to reach new buyers

Beyond social content, a short list of channels is worth setting up early:

  • Email marketing — the highest-return marketing channel for repeat buyers.
  • Local SEO — matters if you also sell at local markets or from a studio, since “handmade jewelry near me” searches convert differently than broad marketplace traffic.
  • Cross-promotion with other makers — swapping mentions or bundling with complementary sellers, especially at shared craft fairs.

These three barely scratch the surface of a full small business marketing plan, but they’re the ones with the fastest payoff for a handmade seller specifically.

Turning first-time buyers into repeat customers

Most sellers stop marketing the moment the order ships, which is exactly when a repeat customer is won or lost. Three tactics do most of the work:

  1. A packaging insert with a discount code for the next order.
  2. A direct request for a review once the order’s arrived.
  3. A follow-up email a week or two after delivery, asking how the product held up.
Welcome email example sent by an online homemade product business

Ready to turn your homemade products into a real business?

The path is the same regardless of what you’re making: validate the idea, handle the legal basics, pick a channel, price around that channel’s fees, and market for repeat business once you’re selling consistently. 

When you’re ready to run your own storefront, SiteGround Ecommerce bundles the hosting, checkout, domain, and shipping tools into one place, backed by expert support, so you can launch without stitching together separate services or learning a new platform from scratch.

[103]

Frequently asked questions

Where’s the best place to sell handmade items?

For most first-time sellers, a marketplace like Etsy is the fastest place to start because of the built-in audience, and your own store makes sense once fees start eating a meaningful cut of margin. See the marketplace, local, and own-store breakdown above for the full decision framework.

What is the best alternative to Etsy?

Amazon Handmade, eBay, and Depop are the three most common Etsy alternatives, each suited to different product types, price points, and craft businesses. Amazon Handmade is an online marketplace that tends to work best for higher-priced items, while eBay and Depop fit resale-adjacent or fashion-leaning goods.

Do I need an LLC to sell handmade items?

Usually not to start. Most hobby sellers begin as a sole proprietor and only form an LLC once sales volume, inventory risk, or tax complexity grows enough to justify the paperwork.

What is the most profitable handmade item to sell?

It depends on the difference between material cost and perceived value rather than any single “best” product. Jewelry and candles often carry strong margins because materials are cheap relative to what buyers are willing to pay, which ties back to the validation criteria in Step 1.

WordPress 7 AI features vs AI Agent for WordPress: What’s built-in and what needs an agent

A digital graphic depicting AI-assisted e-commerce price updates and automated site publishing on a dark purple background. In the foreground, a floating translucent UI window displays a user prompt, "Update my prices and republish," alongside green checkmarks for "Updating...," "Publishing...," and "Completed" next to a WordPress logo. In the background, a ceramics website preview showcases updated item prices under an "Essentials" section, featuring the "Solitude Bowl" at "$90," "Tapered Stoneware Vessel" at "$140," and "Pedestal Platter" at "$180."

You’ve probably heard that WordPress 7 brings AI into WordPress itself. But if you upgrade to WordPress 7.0 or later and go looking for AI features, you won’t find any waiting for you. What arrived is a shared infrastructure for connecting AI to your site rather than features, so on its own it changes nothing you can see in your dashboard. 

Something has to sit on top of that infrastructure, and the most capable option available today is a specialized AI Agent for WordPress: a tool that connects to your site, understands what’s on it, and carries out work across your dashboard when you ask in plain language. Comparing WordPress 7 AI features vs an AI Agent for WordPress is a question of what the platform now gives you and how much further an AI Agent takes it.

Key takeaways:

  • WordPress 7 introduced shared AI infrastructure, but no user-facing AI features out of the box. Your dashboard looks the same after the update. What arrived is a connection system that other tools build on.
  • You connect an AI provider once, in Settings > Connectors. Compatible plugins then share that connection, instead of you pasting the same API key into every plugin’s settings.
  • Most providers charge you directly for what you use. You create an account with OpenAI, Google, or Anthropic, generate an API key, and the usage is billed to you.
  • WordPress 7 AI features vs AI Agent for WordPress is a question of reach. The infrastructure connects AI to your site, while an agent like SiteGround’s AI Agent for WordPress is what actually carries out work across it through a simple chat that follows you between screens.

What WordPress 7 actually added

Until WordPress 7, there was no common system for how AI worked inside WordPress. If you wanted AI features, every plugin handled it differently. An AI writing tool connected to one service with its own API key (a unique credential that lets a plugin communicate with an AI provider). An AI SEO plugin connected to a different service with a different key, while an image generator needed a third setup. Run all three, and you were managing three sets of credentials in three settings panels, often paying for overlapping subscriptions, and none of those tools could share anything with each other. 

WordPress 7.0 (the first version of WordPress 7, which was recently followed by WordPress 7.1) solved that by building a shared AI layer directly into core (the base software that powers every WordPress site).

The new WordPress 7.0 AI Client is the part that standardizes how plugins request AI work, so a plugin now asks WordPress, and WordPress routes the request to whichever provider you’ve connected. The WordPress Connectors API powers the Connectors screen, where you manage those provider credentials in one place. And the WordPress Abilities API keeps a structured register of what your site itself can do, such as publishing a post or updating a product, so AI tools can discover what’s possible. 

To get the full picture, read our guide to how AI works in WordPress 7.0.

What happens the moment you upgrade

The only visible change for you is the new WordPress Connectors screen under Settings, where WordPress AI provider setup now happens. Open it, and you’ll find cards for the three providers WordPress features by default: OpenAI, Google Gemini, and Anthropic Claude. Each one needs an API key (a unique credential that lets your site communicate with that provider). To get one, you create an account on the provider’s website, go to their API or developer section, generate a key, and paste it into the card. From that point, whatever AI work happens on your site is billed to that account.

Beyond OpenAI, Google Gemini, and Anthropic Claude, the system is open, and community-built providers can be added from the same page, each requiring you to install its provider plugin and enter your own key. You may also see Akismet listed there, which isn’t an AI provider at all. The Connectors screen stores credentials for external services generally, and anti-spam was the first non-AI example WordPress added.

Pro tip: set a spending limit. AI providers charge per token, and WordPress has no spending cap of its own, so nothing on your site stops the meter once a connection is live. A plugin making frequent background calls, or one busy month of content, can multiply a bill before it shows up on a statement. OpenAI and Anthropic both let you set a hard monthly cap in your account settings, which takes about a minute. Google’s billing runs through Google Cloud, where the default is a budget alert that emails you rather than a limit that stops anything, so check what you’ve actually set there.

If your WordPress site is hosted on SiteGround, there’s a fourth option on that page. SiteGround AI is already installed and connected as an AI provider, with authentication handled automatically through your SiteGround account, so it appears in Connectors as already active with no API key to paste.

SiteGround AI connector card showing a "Connected" status badge and Edit link, with a note that no API key is needed — install the AI Agent by SiteGround plugin and create a free SiteGround AI Studio account to activate automatically.

The six layers between an AI model and a finished task

Let’s illustrate how you can use AI in WordPress 7 and above with an example of a simple task. Say you want to add alt text to an image you have in your WordPress Media Library, and you want to use AI to generate it right into the editor. Six things have to be in place:

What’s neededWhat it meansWhere it comes from
An AI modelThe thing that looks at a photo and writes the descriptionAn outside provider such as OpenAI, Google, or Anthropic
A connection to itPermission for your site to send requests to that providerYou, through Settings > Connectors, with your own account and API key
A standard way to askPlugins requesting AI work without writing code for each providerWordPress core, since 7.0. This is the AI Client, and it works invisibly
Permission to actWriting the result into the Alt text field, rather than only showing you wordsThe Abilities API in core, plus whatever your plugins have registered
Somewhere to ask fromA button, a screen, or a chat where you make the requestNothing in core. WordPress 7 ships no user-facing AI features at all
The finished jobYour image with alt text saved on itOnly if all five above are in place for this particular task

Everything on that list apart from the finished job is either supplied by WordPress core or connected by you in a few minutes. What core deliberately doesn’t include is anywhere to make the request, because the platform’s job is to provide the connection and leave the tools to everyone else.

Pro tip: check what your provider can’t do before you pick it. Not every provider handles every kind of request. For example, Anthropic Claude generates text but not images, so if you connect Claude alone and a plugin asks for an image, WordPress will look for another provider that can handle it and find nothing. The routing between providers is automatic, but only if you’ve connected a second one that covers the gap. If you want both text and images, that means two accounts, two API keys, and two bills to watch.

WordPress 7 AI features vs AI Agent for WordPress, layer by layer

So WordPress 7 AI features become usable once you install AI plugins that have adapted to the new infrastructure. As we found in our 2026 report on AI in WordPress for small businesses, most of those plugins focus on generating content inside the editor: titles, excerpts, alt text, images, summaries.

What extends WordPress 7’s AI features much further, and makes fuller use of them, is a specialized AI agent like SiteGround’s AI Agent for WordPress that can generate content and also handle actual WordPress management. Instead of clicking through admin screens, you describe what you need in a chat that sits in your dashboard, and it transforms tasks that typically take hours of manual admin work into minutes of conversation. Here’s how the two compare:

WordPress 7 on its ownAI Agent for WordPress
What it isInfrastructure: a shared way for plugins to reach AI providersA WordPress AI management assistant that reads and acts on your site, delivered as a chat in your WordPress admin
What you get after setupA connected provider, and plugins that can use itA chat you can ask for work, available on every admin screen
What it can do for youNothing directly. It enables other toolsContent, plugins, themes, products, orders, users, site structure, and bulk changes
How you use itYou configure the connection. Compatible plugins use it on your behalfYou describe what you want in plain language
SetupA provider account, an API key, and that provider’s plugin activatedUp and running for SiteGround-hosted sites. For sites hosted elsewhere, it’s a lightweight plugin 
Who pays for AI usageYou, directly to the provider you connectedCovered by your AI Studio workspace, with usage visible in one place
Works onWordPress 7.0 and later Any WordPress site, with the Connectors entry appearing on 7.0 and later

Do you need an AI Agent for WordPress after WordPress 7?

It depends on what you want the AI to do. The useful way to decide is by the job rather than the product label.

When WordPress 7 and AI plugins are enough

If your goals are highly focused and repeatable, standard AI plugins are often all you need. In-editor tools like Jetpack AI are excellent for drafting and rewriting copy right where you type, while established SEO tools like Yoast and Rank Math are perfect for page-by-page metadata, schema suggestions, and content scoring.

Stick with AI plugins working with WordPress 7’s infrastructure if:

  • You’re comfortable running an AI provider account. For developers and agencies, choosing the model and controlling spending at the provider level is a feature rather than a cost.
  • You only need depth in a single, isolated area. If your primary AI need is a dedicated customer support chatbot to capture leads on your homepage, or a tool to optimize an individual post’s SEO, a purpose-built single-function plugin is the right tool for the job.
  • You already have tools that work. Our guide to choosing between AI plugins and AI agents makes the case that these categories aren’t exclusive, and many growing sites end up running both.

When you need a WordPress AI management assistant instead

Content creation is only a fraction of running a website. For small businesses, the real time-sink is the endless operational overhead: managing product catalogs, processing store orders, auditing user permissions, and keeping multiple domains synchronized. Because these tasks happen entirely outside the post editor, standard in-editor AI content generators cannot help you.

A site-connected management agent like SiteGround’s AI Agent for WordPress is built specifically for operations, making it the perfect fit if:

  • You want to bypass the complexity of API keys and provider billing. Juggling developer dashboards for multiple AI models is an administrative headache. With the AI Agent for WordPress, there are no raw API keys to generate, copy, or maintain. All usage of leading models is consolidated under a single subscription
  • You need system-wide operations, not just text generation. Standard AI plugins are isolated to the block editor or SEO fields. By contrast, an AI Agent for WordPress connects directly to your site and can manage posts, media, pages, users, themes, plugins, and WooCommerce products and orders. It is an operations manager, not just a writer.
  • You need to execute the same change across hundreds of items. Manually updating prices on 300 WooCommerce products or adding missing alt text to your entire media library takes hours of clicking. An AI Agent for WordPress can make these sweeping database modifications instantly in response to a single prompt, saving you from clicking 300 times.
  • You manage multiple websites. Instead of logging into five different dashboards to perform routine updates, you can activate the AI Agent plugin on multiple WordPress installs and orchestrate actions across all of your selected domains simultaneously from a single, unified chat.
AI Agent by SiteGround chat panel with category buttons (Most Popular, Create & Generate, Audit & Optimize, Bulk Actions) and a list of suggested actions for site speed, security, SEO audit, and update checks.

What changes when you connect SiteGround AI as your WordPress AI provider 

Setting up an AI provider the standard way means a developer dashboard, a key you generate and paste in, and a bill you keep an eye on. Connecting SiteGround AI removes all three at once. There are no API keys to generate, copy, or maintain, and no separate bills from different AI providers to track. All your usage consolidates into a single AI Studio subscription, so you get one predictable monthly bill and a clear view of what you’ve used.

As your WordPress 7 AI provider, SiteGround AI powers the standard editor capabilities that any connected provider can handle. It also activates the AI Agent for WordPress, which appears as a chat box in the bottom corner of your admin dashboard. The chat is persistent, so it stays with you as you move between screens rather than being something you open, use, and close.

Behind both of those, it removes a decision most small business owners don’t have the time to make. With a provider connected directly, you’re choosing which AI model runs each request: the fast ones are cheap and shallow, the powerful ones are slower and better at hard problems.

SiteGround AI routes each request to the model that suits it. For instance, if you ask the AI Agent for WordPress for quick advice about a plugin, it goes to something light like Gemini Flash for an instant answer. Ask for something heavier, like analyzing your site database or generating secure code to update your settings, and it routes to a more powerful model such as Gemini Pro or Claude Opus. You get the right level of intelligence for each task without learning the differences between models.

WordPress 7 made your site AI-ready, not AI-managed

What all this means for you is that WordPress 7 AI features vs AI Agent for WordPress isn’t really a choice between two products. The infrastructure connects AI to your site, while an agent is what turns that connection into work getting done. One is the wiring, the other is what you plug into it. 

So the real question isn’t which one to pick, but how much of your WordPress work you want AI to help you with. 

Do WordPress 7.0 AI features include an AI assistant?

No. WordPress 7.0 ships AI infrastructure rather than AI features: the AI Client, which standardizes how WordPress communicates with AI services, and the Connectors screen, where you manage provider credentials. To get anything you can click, you install an AI plugin on top.

Can WordPress 7.0 manage plugins and WooCommerce by itself?

No. WordPress 7.0 cannot manage plugins or WooCommerce by itself. It provides the connection layer and a register of actions your site can perform, but core includes no screen or chat where you can request that work.

What is the difference between WordPress 7.0 AI and an AI agent?

The difference between WordPress 7.0 AI and an AI agent is what each one does. WordPress 7.0 connects your site to an AI provider so compatible plugins can use it. An AI agent for WordPress reads your site and acts on it, handling plugins, products, orders, and users through a chat in your admin.

Do I still need an AI agent after upgrading to WordPress 7.0?

You still need a WordPress AI management assistant such as AI Agent for WordPress after upgrading to WordPress 7.0 if you want help with site management rather than writing. The infrastructure connects AI to your site but does not provide a conversational management interface by itself, and WordPress’s own AI plugin covers the post editor only.

What do the AI Client, Connectors screen, and Abilities API each do?

The AI Client standardizes how plugins request AI work. The Connectors screen is where you connect provider accounts so plugins can share one connection. The Abilities API keeps a structured register of what your site can do, so AI tools can discover which actions are available.

Do I need separate API keys for OpenAI, Claude, and Gemini?

Yes, you need separate API keys for OpenAI, Claude, and Gemini if you connect them individually. Each provider needs its own account, its own API key entered in Settings > Connectors, and its own provider plugin activated. Connecting SiteGround AI instead registers a provider automatically, with no API key at any stage.

Is SiteGround AI Studio an AI provider or an AI agent?

Both roles come from the same plugin. SiteGround AI acts as your AI provider in Settings > Connectors, and the AI Agent for WordPress is the chat that reads and acts on your site. The AI Agent by SiteGround plugin is what connects your site to both.

What happens when AI Studio is connected to WordPress?

When AI Studio is connected to WordPress, SiteGround AI is registered automatically in Settings > Connectors and marked as connected, with no API key required. The AI Agent for WordPress becomes available as a chat across your admin, and you can switch either layer off independently.

AI email templates vs. AI email generators: what’s the difference?

Smiling woman holding a laptop showing an eco-friendly product email, with an AI chat panel generating subject lines beside her

An AI email template generator hands you a fixed layout with placeholder text. An AI email generator writes the real thing on the spot, no placeholders standing in for finished copy. One saves you from designing a layout. The other saves you from staring at a blank subject line field at 4pm on a Friday.

Key takeaways:

  • A real email generator writes copy specific to your message; a template generator assembles a layout and fills it with generic filler text.
  • SiteGround Email Marketing’s Generate with AI feature drafts a full email for you, copy and design, and you can still edit everything it creates in the no-code builder.
  • If your layouts already look right and writing is the slow part, an AI email template generator won’t fix that; you need something that drafts copy.
  • Picking the right ai email template generator depends on which part of your workflow, design or writing, is actually the bottleneck.

How AI email generators work

An AI email generator writes and designs a complete email from a short prompt: subject line, preheader, and body, drafted specifically for what you’re sending, not filled in from a template. You describe the message, and the tool does the writing; you still decide what it says.

Create Campaign modal with 'Generate with AI' option selected, a campaign named Summer Deals, and a highlighted Continue button

What a generator actually gives you

  • You give it a prompt or brief: audience, goal, tone, sometimes a past campaign or product feed as context.
  • An LLM drafts the actual send-ready text: subject line, preview text, body copy, and CTA language, generated for that specific message, not pulled from a filler bank.
  • Some tools layer in personalization tokens or brand-voice tuning, trained on your past sends, at this stage.
  • Layout is often secondary or absent; many generator tools hand you the copy and expect you to drop it into whatever template you already have.

That’s also where SiteGround Email Marketing’s Generate with AI feature has a specific step worth knowing about: describe your business and the email you want, or start from a preset (Promotional, Newsletter, Announcement, Welcome, Event invitation). Then it plays your answers back in a short summary before writing anything, so you can catch a mismatch before you’re looking at a finished draft. Confirm it, and the draft opens straight into the builder you’re already using to edit.

Generation doesn’t have to mean starting from a blank prompt either. Inside a SiteGround Email Marketing template, sparkle icons let you generate a subject line, preheader, image, or block of text on the spot, so a pre-made layout and AI-written copy aren’t mutually exclusive.

SiteGround Email Marketing editor showing the Generate with AI button next to the subject line and preheader fields

Where the human touch still comes in

A finished draft is rarely finished. Brand voice doesn’t come built in, you usually need to feed it sample copy first, and keeping that voice active long-term is often a paid feature.

Personalization works the same way: it needs a real data source behind it, a CRM or your past sends, or the “personalized” line is just a placeholder with a nicer name. That’s exactly why the last pass is yours: a generator hands you a draft, not a finished decision about tone or structure.

None of this replaces email copywriting instinct. A generator hands you a draft, not a finished decision about tone or structure.

How AI email template generators work

Where an AI email generator writes the message, an AI email template generator builds the shell it goes into. 

Give it a prompt, an industry, or a brand asset, and it assembles pre-built blocks, header, hero image, footer, into a structure, then fills the gaps with placeholder text you’re expected to replace yourself. The layout is done. The writing isn’t.

What a template generator actually gives you

  • You give it a starting point: a prompt, an industry or use-case selection, or an existing brand asset like a logo or color palette.
  • It matches that input against a library of pre-built block layouts (header, hero image, product grid, CTA button, footer) and assembles them into a structure.
  • It fills placeholder text and image slots with generic filler copy pulled from the matched category, not copy written for your specific message.
  • You then edit that filler manually in a drag-and-drop or block-based editor before sending.

While SiteGround Email Marketing’s templates aren’t AI-assembled, they solve the same starting problem: pick a pre-built layout and skip designing from scratch, then write directly into it with the manual builder.

Email template picker showing categories like Basic Layouts, Newsletter, and Promotional, with a grid of layout options including Product Update, Showcase, and Announcement formats

Where template generators fall short

The layout arrives finished, but the words don’t. If you need five different promotional emails this month, a template generator saves you from rebuilding the structure five times, but you’re still writing five sets of subject lines and body copy from scratch.

That’s the gap an email marketing design process alone doesn’t close. It’s also why “free ai email template generator” and “ai html email template generator” searches usually lead to the same disappointment: a nice-looking shell with nothing written inside it.

AI email template generators vs. AI email generators: which one fits your workflow

What it doesWhat it doesn’tBest forExample tools
Template generatorAssembles a pre-built layout from blocksWrite your actual messageRecurring formats with a fixed lookMailmodo, Venngage, Figma plugins
Email generatorDrafts subject line, preheader, and body from a promptGuarantee a finished layoutNew copy for a specific campaignSiteGround Email Marketing (Generate with AI)

Ask yourself:

  1. Do you need the same layout with new content each time, like a weekly newsletter? A template generator is enough.
  2. Does the copy need to change per recipient or campaign? You need an email generator.
  3. Does brand voice consistency matter more than speed? Lean template generator; email generator output needs heavier editing.
  4. Are you already on a platform with templates built in, like SiteGround Email Marketing? Check what it already covers first. Some platforms, SiteGround Email Marketing included, now generate the copy too, so a separate tool may not be necessary at all.

Worth noting how AI is changing marketing more broadly here: the line between these two categories keeps blurring as more platforms build generation directly into their editors, rather than treating it as a separate product.

When to use an AI email template generator

Reach for a template generator if the layout is what’s actually slowing you down: you’re comfortable writing your own copy, but rebuilding a header, hero image, and footer from scratch every send wastes time you don’t have. This is the more common starting point for anyone new to email marketing, since a working layout is the first thing you need before copy matters at all.

When to use an AI email generator

Reach for an email generator if writing is the bottleneck, not design: you know roughly what the email needs to say, but turning that into a finished subject line and body copy is what eats the afternoon. This is also where it’s worth checking your existing platform before adding another AI tool to your stack, since more email platforms now build generation in directly.

The right AI email generator for your next campaign

Whichever bottleneck you’re solving for, layout or copy, SiteGround Email Marketing covers both without asking you to bring in a separate tool.

Use Generate with AI to build a whole campaign from scratch: describe your business, your audience, and the tone you’re going for, or start from a preset and a complete draft, subject line, preheader, and body, opens straight into the builder. 

Or start from a template and use the sparkle icons within it to generate a subject line, preheader, image, or block of text as you go, without building the whole thing from a prompt.

[58]

Frequently asked questions about AI email template generators

What’s the difference between an email template and an AI email generator?

An email template is a pre-built layout you fill in yourself; an AI email generator writes the subject line, preheader, and body for you based on a prompt.

Can AI write the whole email, not just the template?

Yes. Different tools do different jobs: some, such as the template generators covered earlier, hand you a layout and expect you to write the copy yourself. Others are built as full email generators from the start. SiteGround Email Marketing’s Generate with AI feature works this way: it drafts the whole email, subject line, preheader, and body, from a prompt or preset, not just a layout with gaps to fill.

Do I need an AI generator if my email platform already has templates?

It depends on whether writing or layout is your bottleneck; some platforms, including SiteGround Email Marketing, now include both in one tool, so check before adding a separate one.

Are AI email generators free?

Some AI email generators are free: SiteGround Email Marketing’s free plan includes access to Generate with AI, while several standalone template tools also offer free tiers with limited features.

Email warmup: How to go from a cold domain to a trusted sender 

Woman working on a laptop with UI overlays showing domain reputation climbing, 99% deliverability, and a primary inbox with excellent sender reputation

A new domain gets treated as suspicious by mailbox providers before a single email goes out, regardless of how good your content is. Warming up fixes that by building a sending pattern mailbox providers learn to trust over time.

Key takeaways:

  • Email warmup works by gradually increasing send volume while building engagement signals, typically 4 to 8 weeks for a brand-new domain to reach full sending volume.
  • A domain with no sending history and a domain quiet for 60+ days follow the same ramp. A migrated domain with clean history is the one that can move faster, and only if its metrics hold up.
  • Opens are a weaker trust signal than they used to be, since Apple Mail Privacy Protection can register a false open regardless of real engagement.
  • Stopping warmup the moment you hit target volume is one of the most common ways senders undo weeks of progress.

What email warmup does to your sender reputation

A domain builds its reputation through behavior: how much it sends, how consistently, and how recipients respond. A domain with no history that suddenly sends hundreds of messages looks exactly like a spam operation to Gmail, Outlook, or any other provider, even if every word of the content is legitimate. Email warmup is the process of building that pattern deliberately: sending a small, steady volume, growing it over time, and letting real engagement (opens, replies, and clicks) tell providers this domain is worth trusting.

This is why warmup sits downstream of sender reputation rather than replacing it. Reputation is the thing providers are actually scoring. Warmup is how you earn a good one before you need it, instead of finding out you don’t have one the day your first real campaign lands in spam.

How the email warmup ramp works

Warmup works by ramping: gradually increasing how much email you send from a domain while building up engagement signals like opens and replies that mailbox providers read as trust markers. Opens are a weaker signal than they used to be. Apple Mail Privacy Protection can register a false open whether or not someone actually looked at the message, so replies and clicks carry more weight than open rate alone.

Which of the three cases below applies to you comes down to one thing: whether the domain has sent email before, and if it has, whether that sending stopped recently or a long time ago.

If your domain has never sent email before

This is the slowest ramp, and it needs one thing in place before it starts: SPF, DKIM, and DMARC (the records that prove your domain isn’t being spoofed) all confirmed working. Warmup builds trust on top of authentication, not instead of it. Take a domain registered this month for a new product launch, with zero sending history. There’s nothing to lean on here, so the ramp starts at the lowest volume and climbs the most gradually of the three cases.

If you’re warming up a domain you’re migrating

Ramp speed here depends entirely on whether the sending history you’re bringing over was clean. Say a domain is moving from another host, and it was sending consistently with a low bounce rate. That domain can move through warmup faster than the brand-new case, since some trust carries over from the previous sending pattern. It’s not automatic, though. You need to verify that history is clean rather than assume it is.

If you’re reactivating a domain that’s gone quiet

Mailbox providers treat a long gap in sending as a reset, not a pause. A domain that sent regularly two years ago, then went quiet for eight months, doesn’t get to pick up where it left off. 

The ramp for this case follows the same schedule as a brand-new domain, not a lighter version of it, since a gap that long is enough for providers to have stopped trusting the old pattern entirely.

How fast can you actually ramp up?

The schedule below isn’t one formula, and it isn’t always a fixed week count either. New and dormant domains follow the same calendar-based schedule. A migrated domain works differently: how fast it moves depends on its metrics, not the week number.

New domain: 4 to 8 weeks

This is the full week-by-week ramp for a new domain: one that’s never sent email before. Follow it in order, only moving to the next week once the current week’s metrics are healthy.

WeekEmails/dayFocus
15-10Known contacts only, real two-way replies
215-25Keep bounce rate (emails that couldn’t be delivered) at zero
330-50Monitor inbox placement (whether you’re landing in the inbox or spam) closely
475-100Check domain reputation health (your overall trust score with mailbox providers)
5++20% per weekContinue only as long as metrics stay healthy

Migrated domain: faster, but only as long as your metrics hold

A migrated domain is one that’s moving its sending to a new host or platform while keeping its existing sending history. This starts one tier higher than the new-domain schedule, since some trust can carry over from that history. It only works as long as your metrics stay within the thresholds below.

WeekEmails/dayFocus
120-30Skip the lowest tier, since some trust carries over. Keep bounce under 2%
240-70Continue only if bounce stays under 2% and complaints (recipients marking you as spam) under 0.1%
375-100+Approaching full volume, same metric gates apply
If either threshold is crossed at any point—Drop back to the new-domain schedule instead

If the bounce rate or complaint history on the old domain wasn’t clean, follow the new-domain schedule instead. A migration doesn’t guarantee a faster ramp. It just makes one possible. As a working line: a bounce rate that’s stayed under 2% counts as clean; anything higher and the domain should be treated as if it’s starting from zero.

Dormant domain: same schedule as a new domain

A dormant domain is one that sent email regularly at some point, then stopped for an extended stretch (weeks or months) before picking sending back up. This is the identical schedule as the new-domain table above, not a separate one. A gap in sending is enough to erase the trust a domain had built before, so it starts from the same place.

WeekEmails/dayFocus
15-10Known contacts only, real two-way replies
215-25Keep bounce rate at zero
330-50Monitor inbox placement 
475-100Check domain reputation health 
5++20% per weekContinue only as long as metrics stay healthy

Mailbox providers treat inactivity as a reset. A domain quiet for less than 30 days can often resume closer to its old pace; past 30 days, treat it cautiously; past 60 days, run it as close to the new-domain schedule as this one, since providers no longer have recent data to trust.

Whichever table applies to you, one thing holds across all three: a clean early stretch isn’t permission to skip ahead. Mailbox providers watch the pattern over time, not a single good week, so jumping two tiers because the first few days looked fine tends to undo the progress those days bought you.

Do you need a tool for email warmup?

If you’re warming up one domain, you don’t need to pay for a warmup tool. Free email warmup just means sending to real contacts yourself and tracking replies by hand, and that’s enough for most senders. 

Paid email warmup tools and software exist mainly for agencies or teams juggling several domains at once, where tracking each one manually gets tedious. Those email warmup services automate the tracking, but the underlying schedule doesn’t change. For one domain, doing it yourself is the easier starting point.

Warmup is done. Don’t flip the switch and walk away.

Reputation built during warmup doesn’t hold on its own once the ramp ends. If sending suddenly goes quiet, or jumps straight to full campaign volume the day warmup finishes, the trust you spent weeks building starts eroding immediately. The safer move is to taper into your regular sending pattern, not switch into it.

That’s exactly the kind of ongoing sending SiteGround Email Marketing is built to support once your domain has earned its reputation. Instead of managing the transition manually, you can move straight from a warmed-up domain into scheduled campaigns and automations without a hard cutover moment where your sending pattern changes overnight.

[58]

Frequently asked questions about email warmup

How long does email warmup take?

A brand-new domain typically needs 4 to 8 weeks to reach full sending volume. A migrated domain with a clean history can move faster, but the pace depends on keeping bounce and complaint rates low, not a fixed timeline. A dormant domain coming back into use follows the same schedule as a brand-new one.

What happens if you skip warmup and send at full volume anyway?

Mailbox providers see a sudden spike from a domain with no track record and treat it the same way they’d treat a spam operation. Expect a sharp jump in bounce rate, emails routing straight to spam instead of the inbox, and in worse cases, the domain landing on a blocklist. Recovering from that takes longer than warming up would have in the first place.

Can you warm up more than one domain at once?

Yes, but each domain needs its own separate ramp. Warmup builds reputation per domain, so running two schedules in parallel doesn’t speed either one up, it just means tracking two sets of numbers instead of one. This is the exact situation where manually tracking everything gets tedious, and where the paid tools mentioned earlier tend to earn their cost.

How do you know if warmup is failing?

Watch the same metrics the schedule already tracks: bounce rate climbing past 2%, complaints climbing past 0.1%, or inbox placement dropping instead of holding steady. Any one of those showing up mid-ramp means the volume increased faster than the domain’s reputation could support, and the fix is to hold at the current volume, or drop back a tier, rather than pushing forward.

Can you warm up an email address for free?

Yes. Manual warmup, sending to real contacts who open and reply, costs nothing but the time it takes. Paid tools exist to automate that tracking, but they’re not required to warm up an address.

Does email warmup work the same way with Outlook and Microsoft accounts?

The core mechanism (gradual volume, real engagement) applies across providers, but the specific signals each one weighs, and how quickly each resets trust after inactivity, aren’t identical between Gmail, Outlook, and other providers.

You don’t need a developer to add Stripe to your website

A digital graphic illustrating an AI-assisted Stripe payment integration set against a blue gradient background. In the center, a product card displays a "Roaster's Choice Pack" coffee item priced at "$24.00" alongside an active "Stripe Integration" toggle switch. Overlaying the product card on the right is a dark "Payment Details" form with fields for email and credit card information above a blue "PAY $24.00" button being clicked by a cursor. In the bottom left, a prompt card shows the user query "Let customers pay on my site..." followed by an AI status reading "Updating ...".

You’ve probably heard that Stripe is one of the best ways for a small business to take payments, and whoever told you was right. But what’s less widely known is how much of it you can set up yourself: actually, you can add Stripe without a developer for most of what small businesses actually sell. 

Stripe’s no-code tools cover one-time payments, subscriptions, free trials, invoices, and donations, and they’ve absorbed a lot of what used to need custom work. What still needs building is anything that has to happen in your own system after the money arrives (and you can build it pretty easily with AI).

Key takeaways:

  • You can add Stripe without a developer for most of what small businesses sell. Products, services, deposits, donations, and memberships are all covered by tools Stripe built for people who don’t write code.
  • You can start before launching your website. A payment link is a ready-made checkout page with its own web address, which you can email, text, print as a QR code, or put on social media.
  • All of it happens in the Stripe Dashboard, which is the website you log into to run your Stripe account. It’s where you create payment links, see who paid, and change your settings. Nothing there involves code.
  • Taking the money and your own system knowing the money arrived are two separate jobs. You can use an AI builder to put the checkout inside your own site while Stripe keeps handling the transactions.

How to add Stripe without a developer: what you can do with no code

The way to add Stripe without code is to just open a Stripe account, which will give you access to the Stripe Dashboard, a website you log into the same way you’d log into your email. The account itself takes about ten minutes to open, though there are a few things to settle before you take Stripe live, including your bank details, your business information, and how your name appears on customers’ card statements.

The main tool in the Stripe Dashboard is the payment link: a checkout page that Stripe builds and hosts for you, with its own web address. You create it by naming what you’re selling and what it costs, and Stripe gives you back a URL. Anyone who opens that URL sees a proper checkout page with your logo on it, pays by card or Apple Pay or Google Pay, and gets a receipt. The money lands in your bank account, and you get an email telling you it happened.

A screenshot of the Stripe landing page for Payment Links featuring the headline "Create a link. Sell anywhere." and a call-to-action button reading "Create a payment link." On the right, a floating checkout preview card displays a skincare product bundle titled "Pure kit" priced at "€65.00," featuring an Apple Pay option, credit card details entry fields, country selection dropdown set to "Bulgaria," and a dark "Pay €65.00" button against floating chat message bubbles in the background.

That’s already enough to add a payment to a website without a developer, and you can even do it before officially launching your website. You can put the link in an email to a client, send it by text, turn it into a QR code for a menu or a market stall, or post it on Instagram. If you already have a website, you can paste in a small snippet Stripe provides to turn it into a buy button on your own page.

By the way, this no-code side covers more things than you’d expect: 

What you want to doHow it works with no codeWorth knowing before you start
Sell a product or serviceCreate a payment link with a fixed price and share it, or embed it as a buy button on your siteOver 40 payment methods and 35-plus languages are handled for you, with Apple Pay and Google Pay switched on automatically
Charge monthly or yearlyCreate the same kind of link with a recurring price instead of a one-off oneStripe handles the renewals, the failed cards, and the receipts. You don’t manage any of it
Offer a free trialTurn on a trial when you create the subscription link, and choose whether to ask for a card up frontSwitch on the reminder emails as well, because Stripe pauses a trial if no card has been added by the time it ends
Bill a client for agreed workSend a Stripe invoice, which is a hosted page they can pay and download for their recordsUsually a better fit than a payment link when the amount changes from job to job
Take tips or donationsCreate a link where the customer chooses the amountThere’s a default ceiling of 10,000 USD per payment, and this option doesn’t work for recurring gifts
Show your prices on your siteBuild a pricing table in the Dashboard and paste the snippet onto your pagePairs well with payment links for memberships, courses, or software
Add extras at checkoutTurn on optional add-on items, discount codes, and shipping rates when you create the linkAll of it is configured with dropdowns and text fields
Limit how many people can buySet a cap on how many times a link can be paid, after which it stops workingUseful for event tickets, limited stock, or a launch offer

Complex operations like recurring billing (charging monthly or yearly) sound like the point where you’d need help, because someone has to charge the card every month or stop charging when people cancel, but Stripe takes care of all of that. You just set a price and a frequency, share the link, and it runs. This way, you can easily build a subscription business in an afternoon.

Free trials go one step further: you can let someone start a trial without giving you a card at all, which removes the biggest reason people abandon a signup. The catch is small and worth setting up at the same time: unless you switch on the emails that prompt them to add a card before the trial ends, Stripe pauses the subscription rather than charging them. Turn those on when you create the link, and it takes care of itself.

Pro tip: Make your first payment link before you decide anything else. It costs nothing, takes about five minutes, and it’s the fastest way to find out whether you need anything more. Create one for the thing you sell most often and send it to yourself. You’ll see exactly what your customer sees, what the receipt looks like, and what lands in your inbox when it’s paid. Plenty of people discover at that point that the job is already done, and the ones who don’t now know precisely which part is missing, which is a much better position to be in than guessing.

Where the no-code path runs out

Stripe’s no-code tools have their limitations, which might affect you depending on what you sell and how you deliver it:

The limitWhat it means for youWhen it becomes a problem
Your website learns nothingStripe emails you and shows the payment in your Dashboard. It doesn’t tell your site, your database, or your member areaWhen paying is supposed to grant access, confirm a booking, or start something automatically
Limited design controlYou can add your logo, pick your background and button colors, and choose from a set of preset fonts. You can’t change the layoutWhen you’ve paid for a designed site and the checkout page looks like a different company
Customers leave your site to payClicking your buy button takes them to a Stripe page, then brings them back afterwardRarely, in practice. Most people recognize Stripe and trust it. It bothers some brands more than their customers
Everything has to be a fixed productPayment links are built around items with set prices, so variable amounts mean creating a lot of links or asking customers to type a numberWhen you quote every job differently, which is most consultants, trades, and agencies
Caps on pay-what-you-wantA default maximum of 10,000 USD per payment, and no support for recurring amountsLarge deposits, retainers, and donation programs. The cap can be raised by asking Stripe
No rules of your ownAnything conditional, like different pricing for different customers or a follow-up that happens automaticallyThis is the genuine dividing line between configuring and building

The first limitation is probably the most significant one: Stripe has no connection to whatever you’ve built, so it can’t log a customer into a members area, mark an order as paid in your booking system, add someone to a course, or update a record in the spreadsheet you run your business on. 

For a lot of small businesses, that’s completely fine. If you take a deposit and then phone the customer to arrange the work, nothing needed to happen automatically. If you sell a physical product and pack it yourself, an email telling you to pack it is all you need. The gap only becomes a problem when the payment is supposed to update a record in an app you already built.

When do you need a developer for Stripe?

Picture someone paying you, and ask what needs to happen the moment the payment goes through. If the answer is that you find out and the money reaches your bank, you’re good to go. You can build the whole thing yourself this afternoon. If the answer involves something else happening, without you doing it, keep reading.

You don’t need a developer if Stripe’s tools are enough

You can accept Stripe payments without a developer if you’re selling a set number of things at set prices, taking deposits or donations, running a subscription, or invoicing clients for work you’ve agreed to. You also need to be comfortable with customers paying on Stripe Checkout, which is the hosted page they get sent to. For most small businesses, that’s a non-issue and occasionally an advantage, since people recognize the name.

That covers a lot of real businesses. A consultant selling three service packages, a restaurant taking deposits, a gym running memberships, a charity collecting donations or even a full ecommerce platform all sit comfortably inside the no-code surface. 

You might need a developer if you want more than the Stripe Dashboard

You’ve outgrown Stripe’s no-code options when paying has to give someone access to something you’ve built, when the checkout needs to sit on your own page with your own design, when the amount is worked out rather than picked from a list, or when something has to happen by itself once the money arrives.

A membership site is a good example: someone pays, and they should be able to log in and see the content immediately. Stripe can take that payment perfectly well, but it has no way to create their account or let them in. 

However, custom payment builds can get expensive. That’s why you should also know that needing more than the Stripe Dashboard and needing to hire a developer aren’t the same thing. There’s a route in between.

The middle path: add Stripe to your own site or app without custom code

What if you can get the checkout on your own site, styled like the rest of it, connected to whatever should happen next, and you still don’t write any code? 

An AI builder for launching without developers can do exactly this by building the connection for you. You describe the payment behavior you want, and it builds the checkout into your site and connects your own Stripe account, with the card handling still happening on Stripe’s side. Because the flow lives in your app, it can also do what payment links can’t: update a record, grant access, or mark an order paid when the payment succeeds. 

If you use an advanced AI builder like Coderick AI, it will read the payment intent in your prompts and will show a Stripe connection card inside the chat interface:

Example of connecting Stripe payments to a client's AI built website

From there it’s a few clicks and one paste. You click Connect, and Coderick AI asks for a key from your Stripe account.

Stripe issues what it calls a Restricted Key, which starts with rk_, and it isn’t your account password. It can only do the specific things Coderick AI needs, and you can change its permissions or switch it off from your Stripe Dashboard whenever you want. 

Once the key validates, the card flips to Connected and Coderick sets up the rest in the background: your product list, and the connection that listens for payments. When someone buys, Stripe confirms the payment back to your site and your order records update to paid without anyone touching them.

Read our guide to setting up Stripe inside Coderick AI to learn about the full process (which takes about a minute). 

What to check before you take real payments

Whichever route you take with Stripe, spend twenty minutes on these four checks before a real customer pays you.

  • Pay yourself in test mode. Stripe gives every account a test mode, which is a complete copy of the system where nothing is real. You can put a fake card through your own checkout and watch the whole thing work without any money moving. Switch it on, buy your own product, and see what happens.
  • Try a card that fails. Stripe publishes test card numbers that are designed to be declined. Use one and check that nothing gets marked as paid, and that the customer sees something sensible rather than a blank page.
  • Find out where the notification goes. Know which inbox receives the payment email and who actually reads it. A payment nobody notices for three days is a fulfillment problem, and it’s the most common one.
  • Look at what the customer sees afterward. The confirmation page and the receipt are part of what they’re buying, and both can be edited. Check that they say something you’d be happy to receive.

Pro tip: Run the same test on your phone. You’ll do the four checks above on whatever you built the site on, which is almost certainly a desktop. Most of your customers won’t be. Checkout is the part of a site most likely to behave differently on a small screen, and it’s the part where a problem costs you the sale rather than a page view. Repeat your test order on a phone before you do anything else. And if you’ve built the store around that checkout with AI, there are eight things worth verifying before real money moves.

Stripe without a developer: the 10-minute test

Whether you can add Stripe without a developer has almost nothing to do with how technical you are. It comes down to one thing: whether anything has to happen after the payment. If the money arrives and an email telling you about it is the whole job, you can have this working before the end of the day, for free, using tools Stripe built for exactly this.

If something on your own site does have to change when someone pays, that’s a genuinely different piece of work. It’s still not a reason to hire a developer, because the gap between a Stripe-hosted link and a custom build is now filled by AI builders that do the connecting for you.

So answer the question before you spend anything on custom development. Open Stripe, make a payment link for the thing you sell, and send it to yourself. Ten minutes later you’ll know whether you’re finished or whether you need the middle path, and either answer saves you a quote you didn’t need.

[96]

FAQs

Do I need a developer to add Stripe to my website?

You don’t need a developer to add Stripe to your website for most common cases. Stripe’s no-code tools handle one-time payments, subscriptions, free trials, invoices, and donations. You need help when a payment has to change something in your own system, when the checkout must sit on your own branded page, or when amounts and rules are custom.

Can I add Stripe to my website without hiring a developer?

Yes. You can add Stripe to your website without hiring a developer by creating a payment link in the Stripe Dashboard and pasting Stripe’s snippet onto your page as a buy button. You can also skip the website entirely and share the link by email, text, or QR code.

Can I use Stripe without writing code?

Yes. You can use Stripe without writing code through payment links, invoices, quotes, pricing tables, and subscriptions, all created in the Stripe Dashboard. Stripe notifies you when someone pays and deposits the money in your bank account, so no code is needed for the payment itself.

What is the easiest way to add Stripe payments to a website?

The easiest way to add Stripe payments to a website is to create a payment link in the Stripe Dashboard and embed it as a buy button. It takes about five minutes, costs nothing to set up, and requires no code.

What Stripe payment flows can I launch without custom code?

Without custom code you can launch one-time product sales, monthly or yearly subscriptions, free trials that start without card details, tips, donations, pay-what-you-want payments up to a default cap, invoices, quotes, and a pricing table on your own site.

Can I accept subscriptions without a Stripe developer?

Yes. You can accept subscriptions without a Stripe developer by creating a payment link with a recurring price. Stripe handles renewals, failed cards, and receipts. You can also offer a free trial without asking for a card, as long as you switch on the reminder emails that prompt customers before the trial ends.

Can I accept one-time payments without a Stripe developer?

Yes. You can accept one-time payments without a Stripe developer using a payment link, an invoice, or a buy button on your own page. All three are created in the Stripe Dashboard and need no code.

Can I build a payment-ready website without a developer?

Yes. You can build a payment-ready website without a developer by using an AI builder to create the site and the checkout together, connected to your own Stripe account. Stripe still handles the card details, and because the checkout lives in your site, the payment can also update your own records.

What makes a great auto repair shop website (and how to build one)

Abstract of an auto repair shop website

Someone’s check-engine light comes on at 11 p.m., and they’re already searching for a repair shop online. What they find in the next ten seconds decides a lot: can they tell a shop won’t rip them off, get a sense of what the repair might cost, and grab a slot without waiting until morning to call? That’s what good auto shop website design actually has to do. Most repair shop sites can’t. Here’s what it takes to be the one that can, and how to build it.

Key takeaways:

  • A Google Business Profile listing gets a shop found, but it can’t book an appointment or explain a price. Good auto shop website design does both, which is exactly where a shop can pull ahead of competitors still relying on a listing alone.
  • Repair shops are a famously low-trust category. Customers expect to be oversold or overcharged, so a homepage with certifications and reviews upfront is the first thing that earns a booking, or loses one.
  • Selling more than labor online works: brake pads, wiper blades, prepaid oil-change bundles, and gift cards are realistic add-ons for most auto repair shop websites.
  • Eight build steps take a shop from a bare domain to a live site that books appointments and takes payment.
  • An ecommerce platform can make all of this easier to build and maintain than piecing together separate tools.

Why your repair shop needs a website

Most auto repair shop websites, when a shop has one at all, still read like a business card: name, phone number, hours. These details alone won’t book an appointment, explain a price, or show a single review. That’s the bar most competitors are clearing, barely, which leaves plenty of room for your auto repair website to do better.

Your shop can go several steps further by letting someone book a slot, see a price range, and read a few reviews before they ever pick up the phone. This pulls ahead of every other business that’s still relying on a listing alone. That’s the opportunity the rest of this guide is built around.

What makes a great auto repair shop website

A great auto repair shop website has six things: a homepage that builds trust in seconds, a services and pricing page, online booking, a way to sell parts or gift cards, a reviews and photo section, and consistent local SEO details.

That’s the short version, useful as a quick gut check before a redesign or a first build. Each item gets its own breakdown in the next section. For everything else worth checking before launch, from favicon sizing to alt text, the 17-step website checklist covers the rest.

Must-have features and pages for an auto repair shop website

These are the building blocks of solid auto repair shop website design, adapted to the realities of turning wrenches and rotating tires. 

A homepage that builds trust instantly

Auto repair is a famously low-trust category. Customers assume they’ll be oversold or overcharged before they’ve even called, so a homepage that establishes credibility in the first few seconds earns bookings that a generic “welcome to our shop” page won’t. We’ve probably all been there as customers ourselves.

The credibility we and customers seek comes from a specific, short list: shop name, a hero image, one clear call to action (book now or call), and trust signals like years in business, certifications, and a testimonial snippet. That’s the whole list, and it needs to load fast, since it’s doing more work here than on most small business sites. The same homepage design essentials that work for any small business apply here, just with the trust signals turned up.

An auto repair shop website that builds trust with testimonials and professional branding

Services and pricing page

Spell out the actual services on offer, so nobody has to call and guess what’s covered. It’s good for SEO too: a page that names specific services (brake repair, oil changes, transmission work) can rank for those exact searches in a way a blanket “car repair services” page never will.

Not every service needs the same treatment:

  • Standardized jobs (oil changes, tire rotations, brake pads): a “starting at” price or a range
  • Complex or variable repairs (transmission work, engine diagnostics, anything where labor time depends on what’s actually wrong once the shop looks): a quote request instead of a guessed number

Either way, disclose the pricing structure upfront: a diagnostic fee, plus labor, plus parts. Naming that structure clearly heads off the “why wasn’t I told the real price” complaint the industry is known for.

And one detail worth stating outright, because it does real trust-building work: if the diagnostic fee gets credited toward the repair when the customer proceeds, say so on the page, not just at the counter. A services page built to convert makes that kind of disclosure part of the page itself, instead of burying it in fine print.

Online booking and appointment scheduling

An embedded booking widget lets customers grab a slot without calling, but a repair shop’s booking needs are more particular than most service businesses. Three things to keep in mind:

  • Bay and technician capacity. A shop can only run as many jobs at once as it has bays and techs, so slots need to reflect real capacity, not arbitrary 30-minute blocks.
  • Parts lead time. A job needing an ordered part can’t actually be booked until the part is in hand.
  • Deposits on big jobs. Brakes, transmission, and engine work require ordering parts upfront, so a deposit at booking protects the shop if the customer backs out after the part is already on order.
Online booking and appointment scheduling on an auto repair shop website

The setup for all three lives in the build-steps section below.

Online payments and a parts or merch store

We’re not talking about adding every sellable item and service to an online store; that’s surely overkill for any auto repair shop website design. Instead, consider offering the things a repair shop can actually sell online: things like brake pads, wiper blades, and air fresheners; prepaid oil-change or seasonal tire-changeover bundles; and gift cards for future service.

Setting this up uses the same ecommerce website approach any small store relies on, just pointed at a different set of products. Not sure it’s right for your shop? Imagine this scenario: during the holidays someone wants to give the car lover in their life a $60 gift card to get some goodies for their ride. If your car repair business offers that, it means a small side revenue stream that most competitors leave on the table entirely — plus the potential for a new loyal client.

Most repair work is invisible once it’s done. Nobody can look at a car and see a rebuilt transmission, so this goes beyond the single testimonial already teased on the homepage. It lands either further down that same page or as its own dedicated reviews and gallery page, and might include:

  • A short block of customer testimonials, pulled from Google reviews or collected directly
  • A small before-and-after gallery for jobs that are visibly verifiable, like body work, paint, or detailing

A customer who can see the dent is gone, or reads that someone else’s transmission got fixed without a hitch, tends to believe the same will happen to theirs.

Location, hours, and contact details for local SEO

Name, address, and phone number need to be consistent everywhere the shop is listed, not just the website. Google and other platforms cross-check these citations, mentions on Yelp, Apple Maps, industry directories, and so on, to confirm a business is legitimate. Consistency like this is a big part of what small business local SEO actually comes down to.

On the site itself:

  • An embedded map
  • Posted hours
  • Complete contact details in one place: address, phone, email, and social links, not just a name and a form
Auto repair shop website contact page with an embedded map for location

A quick citation audit (tools like BrightLocal, Whitespark, or Moz Local) catches any leftover listing with an old address or phone number worth cleaning up. Beyond that, contact page mistakes like burying the page somewhere hard to find or leaving out half the business info are what send visitors away before they ever reach out.

SiteGround Ecommerce covers most of the above must-haves directly: the homepage, the services and pricing page, and the store, all built without writing code, on hosting designed for speed and reliability. Calendly connects in a few clicks for the booking calendar. SEO basics come built into the platform too, so there’s no separate technical setup standing between the site and actually getting found.

Start building your online shop now>>

How to build your auto repair shop website step by step

We’ve covered the important features, now for how to build them, one step at a time. 

Step 1: Choose a domain name

Register a domain before anything else. It’s the one piece needed no matter which builder or platform comes next, so lock it in first: the shop name, a close variation, or the city plus “auto repair” if the exact name is already taken.

Keep it short and literal. Customers searching for the shop by name should be able to guess the URL, and a domain name that’s easy to say over the phone saves spelling it out every time someone asks.

search field for finding and buying your perfect domain name

Step 2: Pick a website builder 

Hiring a developer to hand-code a site is unnecessary for what a repair shop actually needs, and it comes with a bigger bill and longer wait. A website builder gets a working site live without writing a line of code.

Look for a platform that:

  • Bundles hosting with the builder, so there’s no separate hosting decision to make
  • Supports embedding a booking widget
  • Has ecommerce functionality available, now or later, if selling parts, packages, or gift cards online is part of the plan
  • Makes day-to-day updates, hours, the service menu, photos, simple enough to do between jobs

If updating the site takes longer than fixing a flat tire, it’s the wrong platform. A website builder built for non-developers should make an update like that a two-minute job, not a ticket to the web guy or gal.

Pro tip: New SiteGround customers get the domain free for the first year (.com, .org, .eu, or .net) when signing up for a hosting plan, so there’s no separate charge if that’s the platform of choice. 

Step 3: Build your homepage and add trust signals

Place the hero image, add the primary call-to-action button, and write the one-line trust statement: years in business, certifications, or a “family-owned since [year]” line if that’s true. Add the testimonial snippet decided on earlier.

Keep the above-the-fold section to those four elements. Every extra bit of info crammed above the fold pushes the contact or booking button further down the page, and that button is the one thing this homepage exists to get clicked.

Step 4: Add your services and pricing page

Here’s what to be sure to include on your services and pricing page:

  • Either a service list or a pricing table block, whichever the platform supports
  • The diagnostic-fee-plus-labor-plus-parts structure, spelled out in plain language
  • Whether the diagnostic fee gets credited toward the repair, stated clearly
  • Each service listed by its real name, since that’s what people search for, then described by the problem it actually solves: “Brake Pad Replacement, stops that grinding noise before it wears into the rotors”
  • A booking or call CTA near the top of the page, and again after the pricing breakdown

Step 5: Set up online booking and accept payments

There are different ways to go about this, but an easy, common way is with Calendly:

  • Set a daily or weekly cap on each event type, and use round-robin scheduling to spread jobs across whichever techs are free. It’s a rough stand-in for real bay and technician capacity, and not exact tracking. (Note that round-robin scheduling across multiple techs needs Calendly’s Teams or Enterprise plan, worth confirming before counting on it.)
  • Connect Stripe to Calendly so a deposit gets collected right at booking for big-ticket jobs like brakes or transmission work.
  • For parts-pending jobs, manually unpublish that slot or mark it request-only, so nothing gets booked before the part is actually in hand.

Worth noting: Booking and deposits run through Calendly and Stripe. The parts, packages, and gift cards from the checklist earlier are a separate piece: a small store on the same site, which a platform like SiteGround Ecommerce handles without a separate plugin or a second login to manage. Connect Stripe once inside Calendly for deposits, and once inside the ecommerce dashboard for the store, both are quick, one-time setups. 

Whichever tools get used, test both flows before going live: book a slot and pay a deposit through Calendly, then buy a gift card through the store, and confirm everything lands where it’s supposed to. Accepting payments online is the one step where a mistake actually costs a customer money, so it earns the extra test run.

  • Add a testimonials section to the homepage or its own page, and feature a handful of the shop’s best reviews there
  • Upload the before-and-after photos, captioned with what was actually done (not just “brake job,” but “front brake pads and rotors replaced”). Consider linking out to the service page itself
  • Organize the gallery by job type if there are more than a handful of photos, so a customer looking for detailing work isn’t scrolling past ten transmission photos to find it

Step 7: Optimize for local SEO and mobile

  • Add the shop’s address, hours, and phone number, if they aren’t already live from an earlier step
  • Set up or confirm the Google Business Profile listing, since it’s the thing that actually surfaces the site in local search results
  • Check the site on an actual phone, not just a resized browser window

Most local searches for a repair shop happen on mobile, so a mobile-friendly design that loads fast and keeps the contact button within thumb’s reach matters more here than almost anywhere else on the page.

auto repair shop website design optimized for mobile

Step 8: Launch, test, and promote your site

Before flipping the switch, check every link and confirm the site renders correctly on both a phone and a tablet. The booking and payment flow already got tested in step 5, so this final pass is just for everything else.

Publishing the site doesn’t bring in bookings on its own, though. Nobody’s searching for a shop they’ve never heard of, so the next few channels do the actual work of getting you that first appointment.

  • Reviews and your Google Business Profile. Ask every satisfied customer for a review right after pickup, while the job is still fresh. A shop’s star rating is often the deciding factor between two options with similar prices, and social proof like reviews and before-and-after photos tend to tip the scale.
  • Paid ads. Google’s Local Services Ads are built specifically for trades like this: pay per lead instead of per click, a “Google Guaranteed” badge after a license and background check, and placement above the regular map pack. It’s an ongoing budget line, and not a one-time cost, but for a category where most searches are “near me, today,” it can outperform organic reach alone while the site is still new to search. Small business marketing covers this alongside other channels worth testing at launch.
  • Local directories and citations. Remember: name, address, and phone number need to stay identical everywhere the shop is listed, the same citation consistency covered earlier, now extended to Yelp, Apple Maps, and any local Chamber of Commerce directory.
  • Local social and community presence. Post in neighborhood Facebook groups or on Nextdoor, sponsor a local car show or little league team, and consider a referral discount for customers who send a friend. Social media marketing covers where to focus first when there’s no existing following to build from.
  • Collect an email at every visit, and give the website its own way to capture emails too, such as a simple signup form or a small discount for joining. Email marketing can help you build a relationship with someone beyond the one repair that brought them in, and repair shops live on this kind of repeat business. 

Your website should work as hard as your shop does

Homepage, pricing, booking, payments, reviews, and local SEO: that’s the full list, and every step above tackles checking one of those six boxes. Building all of this from scratch could certainly be complicated and overwhelming, but it doesn’t have to be. SiteGround Ecommerce handles the easy build, booking-friendly functionality, the store, and the hosting in one place. Start with the checklist above, and get your auto repair shop live so that you can start reaping the benefits.

[103]

Frequently asked questions

Do I need a website for my auto repair shop?

Yes. A Google Business Profile listing gets a shop found, but it won’t let customers book a slot, see the pricing structure, or buy a gift card, all things a real website handles on its own.

What should be on an auto repair shop website?

At minimum: a trust-building homepage, a services and pricing page, online booking, a way to sell parts or gift cards, a reviews and photo gallery, and consistent local SEO details like name, address, and phone number.

Can I sell parts or accept payments online from my repair shop website?

Yes. Brake pads, wiper blades, prepaid maintenance bundles, and gift cards are all realistic products for a repair shop to sell online, with the setup covered in the online payments and store step above.

How do customers book appointments online?

They pick an open slot from an embedded booking widget or calendar, the same way they’d book a haircut or a dentist appointment, and get a confirmation without ever picking up the phone.

How much does it cost to build an auto repair shop website?

A DIY build on an all-in-one platform typically runs $10 to $30 a month, plus a domain fee of around $12 to $60 a year. Hiring an agency for a custom build costs considerably more. For the fuller breakdown, how much a website costs in 2026 walks through what drives the price up or down.

Payment gateway fees and costs: what small businesses should expect

Abstract image of payment gateway fees

At first blush, payment gateway fees seem pretty straightforward: a processor takes a small cut of every transaction, and that’s the end of it. But when all is said and done, that also means getting checkout live, keeping it running, covering the fees that only show up when something goes sideways, and cleaning up after any mistakes that show up three months in. Knowing these costs beforehand turns a surprise bill into a number you already expected.

Key takeaways:

  • Payment gateway fees typically run around 2.9% plus $0.30 per online card transaction in the US, but that line is rarely the full bill.
  • Checkout setup cost ranges from minutes to connect payments through an existing platform to several weeks for a custom developer build.
  • Whether checkout, inventory, and order records stay connected automatically or need manual wiring by hand depends entirely on which setup approach is used.
  • Hidden payment gateway fees, including refund fees, dispute fees, currency conversion, PCI compliance charges, and platform-level transaction fees, add up fast when nobody’s tracking them.
  • A payment dispute typically triggers a $15 flat fee on top of the disputed amount, refunded by some processors on a win, kept by most on a loss.
  • Subscription businesses carry extra payment costs beyond one-time sellers: failed-renewal churn, plus often a separate billing-tool fee on top of standard processing.
  • Disconnected tools, a payment processor that doesn’t talk to your accounting software or CRM, cost more in reconciliation time than in fees.

What are payment gateway fees, really?

Payment gateway fees are the cut a payment processor keeps for handling a card transaction, usually a percentage of the sale, plus a small flat fee. Here’s what that looks like on a single transaction:

  1. A gateway captures the customer’s card details at checkout.
  2. A processor moves the money and takes its cut. For example, Stripe fees are 2.9% plus $0.30 per successful US card charge, with no monthly fee on its Standard plan.
  3. The payout lands in the business’s bank account a few days later, minus that fee.
A diagram showing the flow of how payments work online, from the customer to checkout, payment gateway, payment processor, and bank account

That fee, though, is the smallest number when it comes to how businesses accept payments online, and the one most comparison articles stop at. It doesn’t cover what it takes to get checkout live or keep it running, which is where the real budget lives.

Note: All fees and plan details in this article are as of August 2026. Stripe’s the running example throughout this piece because its pricing is public and it’s a common default for small businesses; PayPal, Square, and other major processors land in a similar range, just with their own rate cards, so the cost categories below apply no matter which one ends up running checkout. Getting these Stripe basics down early makes the rest of this easier to follow.

What it costs to get payments live

Indeed, most people underestimate the total cost of taking payments. They see the processor’s fee and stop there, and yet, in practice, there’s a lot more to actually getting paid. Part of that is dictated by your setup approach, which determines how much time you’ll be spending getting everything live. 

What kind of setup complexity are you looking at? It comes down to who builds the payment experience and where it lives. That splits into five basic setups:

  1. DIY with Stripe’s API (Stripe Elements): you write the code yourself, and the payment form lives directly on your own site. Best suited to a business owner comfortable coding a fairly simple checkout personally, using Stripe’s own building blocks rather than hiring anyone.
  2. Stripe Checkout: Stripe hands over a pre-built, hosted page; customers get redirected there and back.
  3. Coderick AI (SiteGround’s AI website and app builder): describing the store to it is the entire setup step, no custom Stripe build required. The store, products, and checkout flow live inside your site’s own design; the payment window itself, where the card gets entered, is Stripe’s. No page to design, no API to wire up. The screenshot below shows this step in action: Coderick AI registering Stripe’s own confirmation webhook, the internal signal that tells the app a payment succeeded, not a connection to any outside tool.
Example of connecting Stripe payments to a client's AI built website
  1. Custom development: a hired developer builds it, anything from a simple embedded form to a multi-step, split-payment checkout. Unlike DIY, someone else does the coding, which removes the ceiling DIY has on complexity, at the cost of paying for that work instead of spending your own time.
  2. A full ecommerce platform, such as SiteGround Ecommerce: signing up for the platform is the setup step. Checkout lives inside the platform’s own storefront, with Stripe (or an equivalent) running underneath.

That last one is a bigger decision than the other four: it comes with a storefront and product catalog attached, not just a way to take payments. That bigger footprint earns its keep for a catalog-driven store that needs shipping, tax, and marketing tooling built in from day one. For a handful of products or a single checkout flow, it’s often more machinery than the job needs, and Coderick AI or Stripe Checkout gets there faster.

Time and cost still swing widely across all five, though. Here’s the breakdown:

Checkout setup cost

ApproachSetup timeSetup costTypically used for
DIY with Stripe’s APIA few hours to a few days$0 in tool fees, unpaid time spent building itDevelopers writing their own integration by hand
Stripe CheckoutA few hours$0 setup fee, standard processing rateA fast payment page that doesn’t touch the site’s design
Coderick AISame day$10 to $40 a month, no developer invoiceGetting a store live the same day without writing or hiring for code
Custom developmentTwo to six-plus weeks$5,000 to $50,000-plus upfront, then hourly for changesComplex logic: marketplaces, split payments, unusual rules
Full ecommerce platformA few minutes to a few hours to connect payments$18 to $36 a month, no separate developer cost A full storefront and checkout bundled into one signup

That table covers building a checkout, five ways to do it. For anyone comparing a lighter ecommerce setup against building everything from scratch, the fifth row is the one to study most closely. Turning any of these into a working checkout that can actually run a business adds to the payment integration cost, regardless of approach.

What payment integration cost actually includes

Moving the money is the easy part. A working checkout also needs:

  • Order confirmation emails: a basic payment receipt often comes free once that setting’s turned on, but a proper order confirmation with your own branding and order details is usually separate logic that needs building or wiring up.
  • Tax calculation: applying the right ecommerce sales tax based on where the customer’s buying from. Stripe Tax is available with its own fee whether Stripe runs directly or through an ecommerce platform’s tax settings (as seen below); otherwise it’s a dedicated tax service or manual handling.
Choosing configuration of the Basic Tax Setup with SiteGround Ecommerce
  • Inventory updates: no payment processor tracks what’s in stock, that’s a store feature, not a payment one.
  • Refund handling your team can use without needing direct access to the processor’s own dashboard: most processors already have a one-click refund button built in, so this only becomes a build item if refunds need to happen from your own admin panel or CRM instead, and even then, the processor’s own API key needs refund permissions specifically enabled for it to actually work.

Who this applies to: DIY, Stripe Checkout, and custom development mean connecting these pieces (confirmations, tax, inventory, refunds) by hand, self-taught code or a developer’s invoice. A full ecommerce platform ships with them already built in; Coderick AI can build the same pieces if specifically asked, but that takes prompting and testing, not something that comes bundled by default.

None of this applies to a single one-off payment, a portfolio deposit, a restaurant reservation hold, an event ticket, as a hosted payment link or an embedded pay button covers these simple payment flows instead. An ongoing store needs all of it. 

Payment maintenance costs after launch

Payment maintenance costs don’t show up on the invoice for getting checkout live. They only start once a checkout’s actually been running for a while, and they come in two flavors: keeping tools connected to each other, and handling renewal payments that don’t go through cleanly if the plan includes subscriptions. Let’s break it down.

How disconnected tools add to your maintenance costs

Watch for this pattern: checkout runs through one tool, bookkeeping happens in a separate accounting app, and payment status in your CRM or project tool sits disconnected from both. Disconnected integrations like this turn every sale into:

  • Copying the transaction into the books by hand
  • Updating the order or client record separately
  • Matching any refund across all three, so nothing gets missed

For agencies invoicing multiple clients, closing this exact gap, checkout status not showing up where the client record lives, is usually the difference between faster client payments and constantly chasing down who’s actually paid.

Who this applies to: all five setups. Custom development can have an accounting or CRM connection built in, for a price. The other four handle payment confirmation internally, that’s how any checkout works at all, but none of them expose a way to connect out to a separate accounting or CRM tool.

The fix: a manual routine, though what that actually looks like depends on the setup:

  • Full ecommerce platform: often handled through a built-in order export.
  • Coderick AI: doesn’t include one by default, but it can be asked to add an export option, and refined further with more specific instructions if needed. It still can’t create a live connection to an external accounting or CRM tool.
  • DIY and Stripe Checkout: writing that export step yourself.
  • No export at all: block off ten minutes a week to copy new orders and refunds into the books and the client tracker by hand.

Recurring payment costs for subscription businesses

Anyone building a subscription business should budget for involuntary churn from the start. Imagine: a card expires or a bank declines a renewal, the subscription lapses unless something catches it, and sales go down. Two things reduce this:

  • Automatic retries: re-attempting a failed renewal a few times over one to two weeks, sometimes on by default, sometimes a setting to turn on
  • Card-expiration emails: sent before the renewal date instead of only after it fails, though this is often a setting that needs switching on rather than something that happens automatically

Who this applies to: it depends on whether a subscription layer already sits on top of the processor. A full ecommerce platform or a dedicated subscription app usually handles both without the business owner touching a setting; wiring a processor directly means checking what’s on by default and switching on the rest.

There’s a second cost to plan for on top of that: processors that offer dedicated subscription tools, automated invoicing, retries, dunning, usage tracking, often charge extra for it. For example, Stripe’s version, Stripe Billing, adds a flat 0.7% of subscription volume on top of its standard 2.9% plus $0.30 per charge. Treat both the churn risk and this extra billing fee as built-in costs of running subscriptions at all, not one-off surprises to troubleshoot later.

The hidden costs behind payment gateway fees

Maintenance costs show up on a predictable timeline, whether or not anything goes wrong. Hidden payment gateway fees are different: they only show up when something other than a clean, successful sale happens. Refunds, disputes, and a handful of smaller charges all live here.

  • Refund fees: most processors don’t charge extra to process a refund, but they typically don’t return the original processing fee either. Refund a $50 sale, and the $1.75 already paid to accept it (2.9% plus $0.30) is usually gone for good.
  • Dispute fees: a chargeback usually triggers a separate $15 flat fee on top of the disputed amount, refunded by some processors if the merchant wins, kept by most if they lose.
  • Currency conversion and cross-border fees: expect another percentage point or two on top of the standard rate whenever a customer pays in a different currency or from a different country.
  • Monthly minimums and PCI compliance fees: PCI compliance is the security standard card networks require for handling card data safely, usually confirmed through a short questionnaire. Modern processors like Stripe handle most of this through their own checkout tools, so it rarely shows up as a separate charge. Traditional merchant account providers are a different story: some still charge a monthly non-compliance fee, often $20 to $100, for skipping the paperwork.

Platform fees stacked on top of processing fees

Some ecommerce platforms and website builders add their own per-transaction cut on top of whatever the payment processor already charges. That’s a second fee stacked on every sale, not a replacement for the first, and it’s easy to miss when comparing platforms by their processing rate alone.

Who this applies to: the ecommerce platform route specifically. DIY, Stripe Checkout, custom development, and Coderick AI don’t have a platform layer sitting between the processor and the sale, so there’s no platform fee. SiteGround Ecommerce, for example, drops that extra fee entirely on its Grow and Scale plans, leaving just standard processing, a detail that matters when comparing platforms for selling digital or physical products. Sell runs $18 a month plus the 3% fee, Grow is $24 with none, so past roughly $200 in monthly sales, upgrading pays for itself.

The three different SiteGround Ecommerce plans - Sell, Grow and Scale

Common payment setup mistakes that cost you more later

Every cost covered so far is baked into how payments work, no mistake required. What follows is different: these are payment launch risks, avoidable and rare on launch day itself. They show up the first time something other than a clean transaction happens: the first refund, the first disputed charge, the first server change. 

1. Never testing a real transaction end to end

A checkout that “looks” done and a checkout that’s actually processed a real card, a refund, and a confirmation email are different things. Test all three before launch, including what a customer sees when a card gets declined.

Who this applies to: every setup, regardless of path.

2. Moving hosting without re-checking payment notifications

A site migration is a common place for this exact mistake to surface: moving a live site to new hosting can leave the automatic message a processor sends to confirm a payment pointed at a server that no longer exists, so an order shows “confirmed” on the site while the payment never actually clears on the backend. That kind of gap can run for a couple of days before a customer emails to ask where their order is.

Who this applies to: self-managed hosting, DIY or custom development. A managed platform like Coderick AI or a full ecommerce platform includes hosting already set up for the merchant, so there’s no server to move or a payment notification to break in the first place.

3. Leaving test API keys live in production

Real charges silently fail, or a store looks like it’s taking payments when it’s actually just running in test mode, when test and live keys get mixed up.

Who this applies to: DIY and custom development, where a live key can end up hardcoded into exposed project files. Coderick AI has a dedicated popup for pasting in a Stripe restricted key, separate from typing it into the chat or the project’s code directly. It’s still worth confirming it’s the right key, test or live, each time.

4. Treating PCI compliance as optional

It isn’t a suggestion. For Stripe-based setups, skipping it usually doesn’t show up as its own line item, since Stripe absorbs most of the compliance work into its own tools, but it still raises liability if a breach happens.

Who this applies to: everyone, though the consequence differs by setup. For example, when it comes to Coderick AI, customers enter their card details directly through Stripe, so Coderick AI itself never handles the card data, and there’s no PCI compliance for Coderick AI to carry in the first place. On a traditional merchant account, it’s more direct: skipping it is how a monthly non-compliance fee ends up on a statement.

So, what do payment gateway fees really cost?

Here’s what all of this can look like in practice for a small store doing around $5,000 a month in sales, 100 orders averaging $50 each:

CostAmountThe math
Processing fees$1752.9% + $0.30 per order, across 100 orders
Platform fee (Sell tier)$1503% of $5,000 in monthly sales
One dispute$15Flat fee per chargeback
Total$340

That’s before the one-time cost of getting checkout live in the first place, or the cost of fixing a mistake made at launch. 

Payment gateway fees, and what comes next

Payment gateway fees are the smallest, most visible line in this whole picture. The real total is provider fees plus setup time plus ongoing maintenance plus whatever a rushed launch costs to fix later, and that last category is the one most small businesses pay for without ever seeing it itemized. Which of these apply, and how much, depends entirely on the path in question.

Coderick AI’s distinct advantage in this comparison is the build process itself: whatever gets described (checkout, inventory tracking, order records) comes out connected, and updates work the same way, describing a change instead of filing one with a developer. That’s what makes it the right fit for a single checkout or a lean store built around exactly what’s needed. Build with Coderick AI to get the same connected checkout without paying a developer to build it.

[96]

Frequently asked questions

What are payment gateway fees?

Payment gateway fees are what a payment processor charges to move money from a customer’s card to a business’s bank account, typically a percentage of the sale plus a small fixed amount per transaction.

What do payment gateway fees include beyond transaction fees?

Payment gateway fees themselves usually cover just the per-transaction rate. The broader payment gateway costs around them, refund handling, dispute fees, currency conversion, and monthly minimums, gets billed separately and often gets missed when comparing providers.

What hidden payment gateway fees should small businesses know about?

Hidden payment gateway fees include refund fees (the processing fee that doesn’t come back on a refund), dispute fees, cross-border and currency conversion charges, and PCI compliance fees for skipping the annual security questionnaire.

How much does it really cost a small business to take payments online?

The real cost of taking payments online is the processing rate plus setup time plus ongoing maintenance plus the cost of fixing launch mistakes, not just the percentage listed on a pricing page. The processing rate alone is usually the smallest piece of that total.

What does checkout setup cost for a website?

Checkout setup cost for a website ranges from minutes to connect payments through an existing platform to several weeks and several thousand dollars with a custom developer build.

What does payment integration cost for a small business?

Payment integration cost for a small business covers more than connecting a processor: order confirmation emails, tax calculation, inventory syncing, and refund handling all need building or configuring too.

What payment maintenance costs continue after launch?

Payment maintenance costs after launch include handling failed or expired cards, retrying subscription renewals, and keeping payment records synced with accounting or CRM tools.

What payment setup mistakes make online payments more expensive?

Payment setup mistakes that make online payments more expensive include skipping end-to-end testing, missing a payment notification update after a hosting migration, mixing up test and live API keys, and treating PCI compliance as optional.

Do refund fees and dispute fees increase payment costs?

Yes. Refund fees and dispute fees increase payment costs because most processors keep the original processing fee on a refund and charge a separate flat fee for every dispute, refunded by some processors on a win, kept by most on a loss.

Is Stripe Checkout cheaper than building a custom checkout?

Stripe Checkout is usually cheaper than building a custom checkout, since it skips developer hours entirely, though Stripe checkout in Coderick AI can be faster still because it handles the surrounding integration work, such as order records and confirmation emails, too.

How to sell beauty products online: A 7-step guide to launching your store

abstract of how to sell beauty products online

Yes, you can make real money selling beauty products online, whether that’s a lip oil you’ve been mixing in your kitchen or a wholesale account with a supplier three time zones away. Getting there takes the right niche, some unglamorous legal groundwork, and an online store that ticks all the right boxes to make your business a success.

Key takeaways:

  • Private label, reselling, and handmade aren’t interchangeable: each comes with a different cost structure, margin, and workload.
  • Legal and licensing requirements run deeper for beauty than for most product categories, and skipping them is the fastest way to get a store shut down.
  • Compliance isn’t just federal. State-level rules can apply based on where your customer lives, not where your business is registered.
  • Registering a business name and legally owning that name are two different things, and conflating them is a common early mistake.
  • An all-in-one platform handles most of the technical setup, from product variants to payments, which is central to how to sell beauty products online without hiring a developer.
  • Photography and honest ingredient information do more for conversion than traffic volume, regardless of which business model you choose.

Step 1: Choose your beauty niche and business model

The beauty industry has room for another brand: U.S. shoppers are on pace to spend $30.73 billion on beauty and personal care products online in 2026, growing roughly 8.4% a year, faster than any other beauty sales channel, according to Statista. 

But if you plan to jump in, first you must start with a decision that shapes everything else: are you formulating, reselling, or making the product yourself? Most sellers land in one of three lanes, and each one comes with a different cost structure and a different list of Step 2’s legal boxes to check.

Private label

Partner with a manufacturer that already has a formula, a moisturizer base, a lip gloss, a shampoo, and put your own name, packaging, and branding on it.

  • Choose from an existing formula menu instead of commissioning one from scratch
  • Minimum order quantities are manageable for a first-time seller
  • Margins run higher than reselling, since you’re not the tenth seller of an identical product

Reselling

Buy finished, branded beauty products at wholesale and mark them up. It’s the more straightforward way to sell cosmetic products online if you’d rather test a niche than build a formula.

  • Fastest route to inventory: no formulation or packaging decisions to make
  • Thinnest margins of the three models
  • Bound by the brand’s minimum advertised price rules, so pricing isn’t fully yours either

Handmade beauty products

Make the product yourself: cold-process soap, whipped body butter, small-batch lip balm, really any body products mixed in your own kitchen or a rented commercial space.

  • Full creative control over the formula, packaging, and branding
  • The model most associated with wanting to sell beauty products from home
  • You’re the manufacturer of record, so every compliance box in Step 2 is yours to check

Whichever lane you pick, most beginners are working with limited capital, so it’s worth pairing your niche decision with a plan for starting an online store on a budget before you spend on inventory or a logo designer.

Business modelStartup costControl over formulaTypical margin
Private labelLow to moderateChoose from existing formulasHigher
ResellingLowNoneLower
HandmadeLow, but time-intensiveFullHighest, if priced right
A quick disclaimer before the specifics: this section is a general overview, not legal advice. Requirements, fees, and exemption thresholds shift by state, product type, and over time, so confirm current rules for your specific product and location with your state’s licensing office, the FDA, or a lawyer before you rely on any number below.

This step is an easy one to procrastinate over, but it’s also the one most likely to shut your store down if you ignore it. So let’s break it down so that you can check it off your list.

Registering your beauty business

A sole proprietorship has no state filing fee to form and works fine for testing the water, but your personal assets aren’t separated from your business liabilities, which matters in a category prone to allergic-reaction claims.

  • Sole proprietorship: no state formation fee, though a DBA filing (needed if you’re selling under a brand name rather than your own legal name, which most beauty sellers are) typically runs $10 to $100
  • LLC: $35 to $500 in one-time state filing fees, separates personal and company assets. Several states also charge an ongoing annual franchise tax on top of that filing fee. California’s is $800 a year minimum, regardless of income, so check your state’s full cost, not just the filing fee
  • EIN: free and instant from the IRS, needed once you open a business bank account or hire anyone

Worth noting: Most beauty sellers make the jump to an LLC once they’re taking real orders.

Getting a seller’s permit and sales tax basics

Most states require a seller’s permit before you can legally collect ecommerce sales tax, and you’ll need one in your home state at minimum, plus any state where you have nexus (a warehouse, an employee, or enough sales volume). Handmade cosmetics and private label products are generally taxed the same way as any other tangible good, though a few states carve out exceptions for specific categories, so it’s worth a quick check with your state’s department of revenue before you launch.

FDA cosmetic regulations and MoCRA compliance

The Modernization of Cosmetics Regulation Act (MoCRA), in effect since 2023, requires most facilities that manufacture or process cosmetics to register with the FDA and list every product they sell, including its ingredients.

  • Facility registration renews every two years, anchored to your facility’s own initial registration date rather than a single fixed deadline. Facilities that registered back in 2024 are hitting their first renewal window this year
  • New products must be listed within 120 days of hitting the market
  • A small-business exemption applies if your average annual revenue is under $1 million

The exemption doesn’t cover everyone, though. It doesn’t apply if your products:

  • Come into contact with the eyes, like mascara or eyeliner
  • Are injected
  • Are ingested
  • Are intended to alter appearance for more than 24 hours, like gel nail polish or brow tint

Cosmetic labeling requirements

Every cosmetic label needs a handful of required elements, split across the front-facing panel and the ingredient panel.

  • Identity statement: what the product is, like “facial moisturizer,” on the front panel
  • Net quantity of contents: also on the front panel
  • Ingredient list: standardized INCI names, short for International Nomenclature of Cosmetic Ingredients, in descending order by weight (anything under 1% can be listed in any order after the rest)
  • Warning statement: required wording for certain product types, such as aerosols
  • Name and address of whoever’s responsible for the product

Product liability insurance for beauty sellers

Allergic reactions and skin irritation complaints happen even with a well-tested formula, and a single claim can outstrip whatever you’d saved by skipping insurance. General liability policies that include product coverage for small or home-based beauty sellers typically run a few hundred dollars a year for $1 million to $2 million in coverage through insurers that specialize in handmade goods, and most don’t require a storefront or employees to qualify.

State-specific rules to watch

Federal rules aren’t the only ones that apply. California’s Proposition 65 requires a clear and reasonable warning before selling a product containing a listed chemical to a California resident, and it applies based on where your customer lives, not where your business is registered, so an online store based in Ohio can still trigger it. Businesses with fewer than 10 employees are formally exempt, but the exemption doesn’t change the fact that liability follows the sale, not the location.

Search the USPTO’s trademark database before you commit to a name, and ideally before you order packaging with that name printed on it. This clearance check is free and worth doing no matter when, or whether, you file a formal application.

  • Search the USPTO database for exact and confusingly similar marks
  • Check your state’s business entity registry, plus your target domain and social handles, for the same name already in use
  • A DBA lets you legally operate under a name, but it doesn’t protect that name or stop someone else from using something similar

Formal federal registration is a bigger, later step, and plenty of small or home-based sellers reasonably wait until the business has traction before filing. If and when you do:

  • USPTO filing fee: $350 per class, using pre-approved goods and services descriptions to avoid extra surcharges
  • Attorney-assisted filing typically runs $750 to $1,750 all in for a single class; self-filing skips that cost but carries more risk of a rejected application
  • Budget 10 to 14 months from filing to registration in a clean case, and longer if the USPTO issues an office action, which happens to the majority of applications

Whether or not you file this year, getting your branding basics locked in early, name, logo, and visual identity together, makes that clearance search easier because you’re evaluating one direction instead of five.

Step 3: Source reliable suppliers or manufacturers

Sourcing is where your business model from Step 1 becomes a real supply chain, and vetting takes longer than most first-time sellers budget for.

Private label manufacturers

Vetting a private label manufacturer comes down to three things: their formula catalog, their minimum order, and their paperwork.

  • Minimum orders typically run a few hundred to a few thousand units per SKU
  • Many offer sample kits so you can test formulas before committing
  • Ask for a certificate of analysis and safety data sheet for every formula under consideration, not just the ones you like on first smell

White-label manufacturers

White-label takes private label (Step 1) one step further: you’re picking from the manufacturer’s existing packaging too, not just the formula.

  • Cuts development time further than private label
  • Leaves you with less to differentiate on besides branding and marketing
  • Often the fastest route to a finished, ready-to-sell product

Wholesale suppliers

Finding a legitimate wholesale account takes more digging than searching “wholesale beauty supplier” and picking the first result.

  • Contact the brand directly to ask about an authorized reseller or wholesale account, since going through an unauthorized middleman raises the risk of gray-market or counterfeit stock
  • Ask directly whether the supplier allows resale on your own branded website, since some agreements restrict sales to marketplaces only
  • Get the wholesale price list and minimum order requirements in writing before you commit, terms quoted verbally tend to shift

Vetting three or four manufacturers before you commit eats real hours, and building time-saving systems for running your online business early pays off long after sourcing wraps up.

Step 4: Build your store

This is where niche, licensing, and suppliers turn into an actual beauty ecommerce store a customer can buy from.

Choose how to sell

Beauty sellers face the same ecommerce platform vs. marketplace decision every seller does, and it comes down to the same three tradeoffs: cost, control, and where your buyers actually come from.

Selling on marketplaces

Marketplaces hand you built-in traffic and a checkout system you don’t have to build, which makes them a fast, cheap way to test whether a product sells before you invest in a full storefront.

  • Fees stack up fast: Etsy, for example, charges a $0.20 listing fee per item that renews every four months until it sells, a 6.5% transaction fee, and roughly 3% plus $0.25 in payment processing, adding up to close to 10% in combined fees before advertising even enters the picture
  • You don’t own the customer relationship or email list, just the individual transactions that pass through
  • The marketplace can change its fee structure, algorithm, or policies without asking you first, and your customer base goes with it if your account is ever suspended

Building your own branded store

A branded store trades that percentage cut on every sale for a flat cost that doesn’t change with volume, so the math tips further in your favor the more you sell.

  • You own the customer relationship, the email list, and every piece of data that comes through checkout
  • Building an ecommerce website today means picking a platform that bundles the catalog, checkout, shipping, and tax into one system, instead of stitching together a separate builder, payment processor, and tax tool the way it used to work
  • The tradeoff is traffic: a new store starts with zero visitors, and every one has to come from search, social, ads, or word of mouth, the same cost a marketplace charges you in fees instead

Feature strong product photography

Beauty sells on visuals more than almost any other category, so the platform you build on needs strong image zoom and gallery support built in, since a swatch that looks muddy on a phone screen costs you the sale before the description even loads. Mobile-first matters even more here: beauty discovery happens overwhelmingly on phones, through social feeds and search, not desktop browsing.

Add product variants for shades, scents, and sizes

A lipstick that comes in 12 shades doesn’t need 12 separate product pages. Managing shade, scent, and size as variants on a single listing keeps your catalog manageable and keeps your SEO from splitting across duplicate pages competing with each other.

Selecting product variants such as scent on a product page

Write product descriptions that include ingredients and compliance info

This is where Step 2’s labeling requirements actually show up on the page: the full ingredient list in INCI names, net weight, and any required warning statement belong in the description or a dedicated specs section of each product detail page, not buried in a PDF nobody opens. Customers increasingly check ingredient lists before buying, so treating that information as a selling point, not a compliance afterthought, works in your favor.

Accept secure payments

Whatever platform you choose, checkout should accept the payment methods your customers already trust: credit and debit cards, digital wallets like Apple Pay and Google Pay, PayPal, and for some categories, bank transfers or cash on delivery.

If you want the mechanics of how to accept payments online spelled out step by step, including PCI compliance basics, that’s worth a closer look before you go live.

Handle shipping, including restricted items

Configure your shipping methods (zones, rates, and carrier options) before your first sale, and keep a running list of restricted items like aerosols and alcohol-based products (perfume, some nail polishes) so you don’t overlook them, since carrier rules for these vary by transport method.

Where SiteGround Ecommerce fits in
SiteGround Ecommerce brings everything in this step together in one system: storefront setup, product variants, photography-friendly templates, optimized product pages, and payments and shipping. All of it runs on SiteGround’s platform, with support available around the clock if something trips you up. That’s the assembly work most beauty sellers dread, already done.
Starting building your online store now>>

Step 5: Create product pages that convert browsers into buyers

Traffic doesn’t matter if the product page doesn’t close the sale, and beauty shoppers are unusually skeptical, since they’re putting the product on their skin. Whether you’re figuring out how to sell makeup products online or building a skincare line, product pages carry the weight of proof.

Product photography 

Beauty shoppers need to see more than a pretty bottle before they trust a new brand on their skin.

  • The product in its packaging
  • Swatched on skin in natural light
  • A close-up of texture or size
Product images in natural light and consistently designed on an online store

A single hero shot with perfect studio lighting looks nice but doesn’t answer the question every beauty shopper actually has: what does this look like on a real person? Good ecommerce website design ideas that convert treat photography as functional information, and not just decoration.

Descriptions

Lead with what the product does and who it’s for, then back it up with the ingredient list and texture details a skincare or makeup shopper actually reads before buying. Following basic SEO for ecommerce product pages, working the way real consumers search into your titles and descriptions naturally, helps you get found for the exact terms beauty shoppers already use.

Pro tip: Need a little copywriting inspiration? A built-in AI writer, like SiteGround’s, makes it extra easy to craft the perfect product description on the fly.

Example of writing a product description with the help of AI in a website builder

Customer reviews

“Will this work on my skin type” isn’t something a spec sheet can answer, which is why reviews and social proof matter more in beauty than in almost any other category. Displaying star ratings and written reviews directly on the product page, especially ones mentioning skin type or shade match, does more for conversion than almost any other single design decision you’ll make.

Certifications and safety claims

If a product is cruelty-free, vegan, or dermatologist-tested, say so clearly, and only if it’s actually true. Overstating a certification you don’t hold is exactly the kind of overclaiming that erodes trust fast in a category where customers already read labels closely.

Trust signals and badges

A few small additions reduce the hesitation beauty shoppers feel before trying a new brand on their face.

  • Secure checkout badges
  • Clear return policies
  • Visible customer service contact information
Example website with a shipping policy in the footer transmitting trust

None of this replaces a good product, but it removes the friction that stops an otherwise interested buyer from finishing checkout.

Step 6: Market your launch and land your first sales

Hitting publish doesn’t summon customers (wouldn’t that be nice?). Nobody’s going to stumble onto a brand-new beauty website by accident, which means the next three things matter as much as everything you just built.

Social media marketing

Instagram and TikTok are where beauty discovery happens, which is why social media marketing is the highest-leverage channel for a new brand: short-form video (a shade swatch, a texture close-up, a quick tutorial) tends to outperform static product photos when you have no existing audience.

Paid ads

A modest budget on Instagram, TikTok, or Google ads can get your first sales moving faster than organic reach alone, especially when you’re starting with zero followers and zero reviews. Target narrow (skincare for combination skin, not “beauty” in general) and track cost per click and conversion rate before scaling spend. Small business marketing covers paid ads alongside the other channels worth testing at launch.

Influencer seeding

Sending product to micro-influencers, typically 10,000 to 100,000 followers, in exchange for honest coverage, not a guaranteed post, usually delivers a better return than paying a handful of larger creators for one sponsored post. Disclose the relationship clearly. The FTC requires it, and skipping it is the kind of shortcut that backfires publicly.

Email marketing

Capture emails from day one, even before launch, with a waitlist or early-access offer. A beginner’s guide to ecommerce email marketing is worth reading before your first campaign, since a solid welcome sequence is what turns a new subscriber into a first customer for a brand nobody’s heard of yet.

Step 7: Track performance and scale

Launching is the easy part. Knowing whether it’s working matters just as much, especially once you’re deciding what to reorder. Three numbers are worth watching from day one:

  • Conversion rate: Ecommerce conversion rates for beauty tend to run a bit higher than the overall ecommerce average, since it’s a repeat-purchase category, but the exact number varies a lot by source and by price point.
  • Average order value (AOV): Bundling complementary products (a cleanser with a moisturizer, a shade with a matching lip color) and setting a free-shipping threshold just above your current average order value are the two most reliable levers for raising AOV without discounting.
  • Repeat purchase rate: Skincare and haircare are consumable products, so this matters here more than in almost any other category. As your catalog and traffic grow, website speed matters just as much as it did on launch day, since a slower site quietly erodes the repeat purchases you worked hard to earn.

When and how to expand your product line

Expand once you have reliable repeat purchase data telling you what customers already buy together or ask for in reviews, not before. A second product launched too early, before the first one has proven demand, usually just splits your limited marketing budget and inventory cash two ways instead of growing the business.

Your beauty brand is ready to launch

Seven steps, one honest sequence for how to sell beauty products online: pick your niche and business model, handle the legal and licensing groundwork that’s easy to overlook, source suppliers you’ve actually vetted, build a branded storefront, write product pages that earn trust, market the launch, then track the numbers that tell you what to do next. None of it requires a developer, a warehouse, or six figures of startup capital.

SiteGround Ecommerce is built to get a beauty brand from idea to first sale without the technical detour. Product variants, secure payments, shipping, and tax all live in one place, so the time you’d spend wiring plugins together goes into your formula, your photos, and your first hundred customers instead.

[103]

Frequently asked questions

What is the best platform to sell beauty products?

It depends on whether you’re starting small by testing a niche on a marketplace or building a branded store for the long haul. For a branded store, look for an all-in-one platform, like SiteGround Ecommerce, that bundles hosting, payments, and shipping, with real human support if something goes wrong.

Do I need a license to sell beauty products online?

There’s no single “beauty license,” but you’ll typically need a business registration, a seller’s permit for sales tax, and, unless you qualify for the small-business exemption, FDA facility registration and product listing under MoCRA if you manufacture or process cosmetics.

Can I sell homemade beauty products online?

Yes, but “homemade” doesn’t mean unregulated: you’ll still need business registration, compliant labeling, and, depending on your revenue and product type, FDA facility registration under MoCRA. Product liability insurance is worth budgeting for too, since a single allergic-reaction claim can cost more than years of premiums combined.

What are the best beauty products to sell online?

Skincare is the largest beauty category by sales, accounting for roughly a third of the U.S. beauty and personal care market, according to Grand View Research, with moisturizers and cleansers as the most consistently repurchased individual products.

Is reselling beauty products profitable?

Reselling can be profitable, especially as a low-cost way to test a niche, but margins run thinner than private label, since you don’t control the wholesale price and you’re bound by the brand’s minimum advertised price policy.

Web app ideas for beginners: 10 AI projects to start this weekend

Header image of a hand holding a smartphone with a web app dashboard and floating Planner, Quote Planner, and No Code labels.

The hardest part of a first web app isn’t the building. It’s picking something small enough to finish. Most web app ideas lists hand you a marketplace, call it a weekend project, and move on. These 10 web app ideas for beginners are genuinely weekend-sized: one job each, no payments, no integrations, and a copy-ready prompt to start from.

A simple beginner web app is a single-purpose tool that collects, organizes, or calculates one kind of information for a small group of people. It has one main screen, one type of data, and no dependency on outside accounts or services. Think guest list, packing planner, or quote calculator instead of platform.

Key takeaways:

  • The 10 simple web app ideas below share the same shape: one screen, one data type, and zero third-party integrations, which is what keeps a first build inside two days instead of two months.
  • A first version should hold about 5 fields and 1 view. Anything you add beyond that roughly doubles the number of things that can break before you finish.
  • Payments, user accounts, notifications, and file uploads are the four features that turn a weekend project into a month-long project. Leave all four out of version 1.
  • Every idea here works with data you already have on your phone or in a spreadsheet, so you can test with 20 real entries the same day you build.
  • Each idea includes a success check that takes under 5 minutes, because an app that looks finished and an app that works are different things.
  • Coderick AI comes with a SiteGround hosting plan rather than a separate subscription, and every plan includes at least one project slot, which is all a first build needs.

What makes a simple web app idea small enough for a weekend

A weekend-sized app stores one kind of thing and answers one question about it. A guest-list tracker stores guests and answers “how many people are coming?” A packing planner stores items and answers “what haven’t I packed?” The moment an app has to answer two unrelated questions, it needs two data models, two screens, and roughly four times the testing.

Four properties separate an easy web app to build from a project that stalls:

  • One data type. Guests, items, recipes, or ideas. Not guests and vendors and invoices.
  • No money. As soon as a payment is involved, you inherit refunds, receipts, tax, and failure states.
  • No permissions. If the app doesn’t need to know who’s looking at it, you skip login screens, roles, and password resets entirely.
  • Data you already own. No scraping, no external feeds, no API keys.

This is where AI web app ideas for beginners differ from the classic beginner tutorial. The best apps to build with AI are the ones you can describe in a sentence, not the ones with the longest feature list. With vibe coding, you describe the tool in plain language and the builder generates the interface, the data structure, and the logic behind it. That changes what counts as beginner-sized. The limiting factor is no longer your coding ability. It’s how clearly you can describe one small job.

10 simple web app ideas to build with AI this weekend

Each idea below gives you three things: the boundary of the first version, a starter prompt you can paste into an AI builder, and a success check to run before you call it done. The prompts follow the same five-part structure used in other vibe coding prompts: context, goal, constraints, output, and success criteria. Adapt the details, keep the structure.

1. Event RSVP and guest-list tracker

An RSVP tracker collects names and responses for one event and shows a live headcount. It’s the smallest useful app most people can name, and it replaces a group chat where three people said “maybe” and nobody counted.

First version: one event, a form with name, email, attending (yes/no/maybe), and number of extra guests. One table of responses. A confirmed headcount at the top.

Leave out: multiple events, reminder emails, seating charts, ticket sales.

Build a single-page RSVP app for one private event. Visitors fill in a form with name, email, attending (yes, no, or maybe), and number of extra guests. Below the form, show a table of all responses and a large confirmed headcount that counts only “yes” responses plus their extra guests. No login, no payments, no email sending. Success: submitting the form adds a row instantly and the headcount updates without a page reload.

Coderick AI generating an RSVP web app from a natural language prompt with a live preview.

Success check: add 5 test guests including one “maybe” and one with 2 extra guests. The headcount should read 3 higher than the number of yes rows, and the maybe should not be counted.

2. Decision matrix for comparing options

A decision matrix scores options against weighted criteria and ranks them. It’s useful for choosing a laptop, a supplier, or an apartment, and it’s a good beginner app idea because the entire app is arithmetic on a grid.

First version: add up to 6 options as rows, up to 5 criteria as columns, a 1 to 5 weight per criterion, a 1 to 10 score per cell, and an automatic total with the winner highlighted.

Leave out: saving multiple matrices, sharing, templates, collaborative scoring.

Build a single-page decision matrix web app. Users add options as rows and criteria as columns. Each criterion has a weight from 1 to 5. Each cell takes a score from 1 to 10. Calculate a weighted total per option, sort options by total, and highlight the top row. Everything happens on one screen with no accounts. Success: changing any weight or score immediately reorders the ranking.

Success check: enter 3 options, then change one criterion’s weight from 1 to 5. If the ranking doesn’t move when the weight of a criterion you scored unevenly changes, the math is wrong.

3. Household inventory catalog

A household inventory catalog lists what you own, where it is, and what it cost. People build it for insurance claims, moves, or simply to stop buying a fourth pair of scissors.

First version: item name, room, purchase date, value, notes. A filter by room. A total value that reflects the current filter.

Leave out: photo uploads, barcode scanning, warranty reminders, insurance report exports.

Build a household inventory web app. Each item has a name, room, purchase date, estimated value, and a notes field. Show all items in a sortable table with a dropdown filter by room and a total estimated value above the table. The total must reflect the active filter. No image uploads, no accounts. Success: filtering to one room updates both the visible rows and the total.

Success check: enter 15 items across 3 rooms, then filter to the room with the most expensive item. The total has to drop, and it has to match the sum of the visible rows.

4. Reading or watchlist tracker

A watchlist tracker holds the books, films, or courses you mean to get to and moves them through three states. It’s one of the most common beginner web app project ideas because every list app you’ve tried is either too heavy or wants an account.

First version: title, type, status (want to start, in progress, finished), a 1 to 5 rating on finished items, and one short note. Two views: “up next” and “finished”.

Leave out: importing from external catalogs, cover art, friends, recommendations, reading streaks.

Build a personal watchlist web app. Each entry has a title, type (book, film, or show), status (want to start, in progress, finished), an optional rating from 1 to 5, and a one-line note. Show two tabs: “Up next” listing everything not finished, and “Finished” listing finished items sorted by rating. Status changes with one click from the row. No accounts, no external data sources. Success: marking an item finished moves it out of “Up next” and into “Finished” immediately.

Success check: mark an in-progress item as finished. It should disappear from “up next” in the same click, without a refresh.

5. Trip packing planner

A packing planner turns “did I pack the charger?” into a checklist you reuse for every trip. It’s the easiest of these apps to test, because the test is whether your checkmarks survive closing the browser.

First version: items grouped into 4 or 5 categories, a checkbox per item, a progress count, and a “clear all checks” button so the list is reusable.

Leave out: weather lookups, multiple simultaneous trips, shared lists, per-person packing.

Build a reusable trip packing checklist web app. Items are grouped under categories such as Clothes, Toiletries, Tech, and Documents. Each item has a checkbox. Show a packed count like “12 of 25 packed” at the top. Include a button to reset all checkboxes for the next trip, and let users add or delete items. Checked state must persist between visits. No accounts. Success: checking items, closing the browser, and returning shows the same items still checked.

Success check: check 10 of 25 items, close the tab, and open the app again. If the checks are gone, the app isn’t saving data. It’s redrawing it.

6. Recipe organizer and meal shortlist

A recipe organizer stores the meals you actually cook and builds a shopping list from the ones you pick for the week. This is where a small app beats a notes file, because a notes file can’t combine ingredients.

First version: recipe name, tags, ingredient list, and a “shortlist” toggle. One combined shopping list built from the shortlisted recipes, with duplicate ingredients merged into a single line.

Leave out: nutrition data, serving-size scaling, cooking instructions, grocery integrations.

Build a recipe organizer web app. Each recipe has a name, up to 3 tags, and a list of ingredients as free text lines. Users can toggle any recipe into a weekly shortlist. Generate a combined shopping list from all shortlisted recipes, merging identical ingredient names into one line with a count of how many recipes need them. No nutrition data, no accounts. Success: shortlisting two recipes that both need onions shows onions once, marked as needed by 2 recipes.

Success check: shortlist 3 recipes that share an ingredient. That ingredient must appear exactly once in the shopping list. If it appears three times, the merge logic didn’t happen.

7. Content idea organizer

A content idea organizer holds post ideas with their hook, channel, and status so they stop living in six different places. It’s one of two lightweight business tools on this list, and it stays small because it never touches a publishing API.

First version: idea title, channel, hook (one line), status (idea, drafting, scheduled, published), and target date. A board or table grouped by status with a count per group.

Leave out: publishing to social platforms, performance analytics, team assignment, approval workflows.

Build a content idea organizer web app. Each idea has a title, channel (blog, newsletter, or social), a one-line hook, a status (idea, drafting, scheduled, or published), and a target date. Group ideas by status with a count in each group heading, and let users change status from the idea itself. Sort within each group by target date, soonest first. No external publishing, no accounts. Success: changing an idea’s status moves it to the correct group and updates both counts.

Success check: move an idea from “idea” to “drafting”. Both group counts must change in the same action. One count moving is a partial update, which is a bug you’ll otherwise find weeks later.

8. Feedback and idea-voting board

A voting board collects suggestions and lets people upvote them, so the loudest request stops being the one that arrived most recently. Keep it to one board and it stays a weekend project.

First version: submit an idea with a title and one-line description, an upvote button per idea, a sort by votes, and a simple one-vote-per-browser check.

Leave out: accounts, comments, moderation queues, public roadmaps, status labels.

Build a public idea voting board web app. Anyone can submit an idea with a title and a one-line description. Each idea shows an upvote button and a vote count, and the list sorts by votes with the highest first. Prevent the same browser from voting twice on the same idea by storing votes locally. No accounts, no comments, no moderation. Success: voting twice on the same idea from the same browser increases the count only once.

Success check: vote on the same idea twice from one browser, then once from a different browser or a private window. The count should go from 0 to 1 to 1 to 2.

9. Simple quote or estimate calculator

A quote calculator turns your pricing rules into a form that produces a number. It’s the most immediately useful of these no-code app ideas for anyone who currently answers “how much?” by opening a spreadsheet.

First version: service type, quantity, up to 3 add-ons with fixed prices, and a total with a plain-text summary the visitor can copy. Prices live in the app. No payment.

Leave out: taking payment, invoices, client accounts, regional tax rules, saved quotes.

Build a quote estimate calculator web app for a service business. The form has a service type dropdown with 3 options at fixed base prices, a quantity field, and 3 optional add-on checkboxes with fixed prices. Show a running total that updates as the visitor changes any field, plus a copyable plain-text summary listing every line item and the total. Do not collect payment or personal data. Success: the total always equals base price times quantity plus the checked add-ons.

Success check: run 3 jobs you’ve actually quoted in the past 6 months through the calculator. If any result is more than 10% off what you charged, your pricing rules aren’t what you thought they were, which is worth knowing before a client uses the form.

Web app quote calculator with service selection, optional add-ons, quantity controls, and an automatically calculated total.

10. Plant-care or habit tracker

A recurring-task tracker records when you last did something and tells you what’s due today. Watering plants is the friendly version. It works identically for filters, medication reminders, or a workout schedule.

First version: item name, frequency in days, last-done date, and a “due today” list at the top. One button per item that sets last-done to today.

Leave out: push notifications, streaks and badges, multiple users, photo logs.

Build a recurring care tracker web app. Each item has a name, a frequency in days, and a last-done date. Calculate the next due date from the last-done date plus the frequency, and show a “Due now” section at the top listing every item whose due date has passed. Each item has a “Done today” button that sets last-done to today’s date and moves it out of the due list. No notifications, no accounts. Success: an item with a 3-day frequency last done 4 days ago appears in “Due now”.

Success check: create an item with a 3-day frequency and backdate the last-done field by 4 days. If it doesn’t appear as due, the date math is off by a day, which is the single most common bug in this app.

How to choose which web app idea to build first

Pick the idea whose data already exists somewhere you can copy from in 10 minutes. That’s the whole decision. If the guest list is in your phone, build the RSVP tracker. If your pricing rules are in a spreadsheet, build the quote calculator. An app you can fill with real data on day one gets tested honestly. An app that needs invented data gets admired and abandoned.

Three filters, in order:

  1. Will you use it within 7 days? A packing planner before a trip gets used.
  2. Do you already have 20 real entries? Twenty rows is enough to expose bad sorting, broken filters, and layouts that only work with three items.
  3. What happens if it’s wrong? A miscounted headcount is an inconvenience. A wrong invoice is a problem. Start where mistakes are cheap.
If you want toBuildData it storesReusable after?
Organize a personal eventRSVP and guest-list trackerNames, responsesYes, per event
Make a hard choiceDecision matrixOptions, weighted scoresYes, any decision
Prepare for insurance or a moveHousehold inventory catalogItems, rooms, valuesOngoing
Stop losing track of mediaReading or watchlist trackerTitles, statuses, ratingsOngoing
Travel without forgetting thingsTrip packing plannerItems, checked stateYes, every trip
Plan the week’s cookingRecipe organizerRecipes, ingredientsWeekly
Keep creative work movingContent idea organizerIdeas, status, datesOngoing
Prioritize customer requestsFeedback and voting boardSuggestions, votesOngoing
Answer pricing questions fasterQuote calculatorPricing rulesOngoing
Remember recurring tasksPlant-care or habit trackerItems, frequency, datesOngoing

Tool choice matters less than scope, with one exception: whether the app can save data without you setting up a database. A tracker that forgets everything on refresh isn’t a tracker. An AI website builder that works without code and generates its own backend removes that step, which is the difference between a working app and a pretty mockup.

What to leave out of your first version

Cut every feature that requires a second screen. Most beginner web app projects fail on scope, not on prompting, and the same four features are responsible: user accounts, payments, notifications, and file uploads. Each one brings its own error states, and error states are where beginners run out of weekend.

What to leave out, and what to do instead:

  • User accounts. Instead, keep the app private by keeping the URL private. Add authentication in version 2, once you know the app is worth logging into.
  • Payments. Instead, output a total and a copyable summary. Take the money the way you take it now.
  • Notifications. Instead, show a “due now” or “waiting on you” section at the top of the screen. The app tells you when you open it.
  • File and photo uploads. Instead, use a text field for the detail you’d have captured in the image, such as a serial number or a link.
  • Multi-user editing. Instead, one person edits and everyone else reads.

There’s a practical reason to be strict here beyond time. Every refinement prompt spends some AI tokens, and simpler prompts consume fewer of them. A tight first version leaves you tokens to fix what testing reveals. A sprawling first version spends them arguing with a login screen you didn’t need. This is the most common of the AI app builder mistakes beginners make, and it happens before a single prompt is written.

How to test a small web app before anyone else sees it

Run five checks in this order. They take about 10 minutes together and they catch nearly everything that goes wrong in an app this size.

  1. The empty state. Load the app with zero entries. It should say something useful, not show a broken table or a total of NaN.
  2. Twenty real entries. Paste in actual data, not “test test test”. Real data has long names, missing fields, and duplicates, and it breaks layouts that three tidy rows never will.
  3. The refresh test. Enter data, close the tab, reopen the app. Anything that disappears was never saved.
  4. The phone test. Open it on your phone. Tables are the usual casualty. If you can’t read a row without pinching, the app needs a stacked layout on narrow screens.
  5. The wrong-input test. Type a word in a number field. Leave a required field blank. Enter a date in the past. The app should refuse politely instead of crashing or saving nonsense.

Fix one thing per prompt. Bundling five fixes into one instruction makes it hard to tell which change caused which result, and it’s how working features get quietly overwritten. Version control and staging exist for exactly this: if a refinement makes things worse, revert to the last good version instead of prompting your way back out. Testing in small loops like this is the core of a repeatable vibe coding workflow, and it’s what separates a build that survives contact with real users from one that doesn’t.

When all five checks pass, show it to one person who wasn’t involved. Watch them use it without explaining anything. Whatever they hesitate over is your version 2 list, and it will be shorter and more accurate than the feature list you would have invented on your own.

Start with one idea this weekend

Any of these 10 simple web app ideas is small enough to go from prompt to working app in a weekend, provided you hold the line on scope. One data type, one screen, no payments, and 20 rows of real data to test against. The idea that gets finished is almost never the most ambitious one on the list. It’s the one whose data you already had.

You can build any of them with Coderick AI, which turns a plain-language description into a working app with hosting, SSL, a generated backend, and version control included from the first prompt. Access comes with a SiteGround hosting plan, the only thing left to decide this weekend is which of the 10 ideas you’ll actually use.

[96]


Frequently asked questions (FAQ)

What are some simple web app ideas I can build with AI?

Simple web app ideas that work well with AI builders include an RSVP and guest-list tracker, a weighted decision matrix, a household inventory catalog, a watchlist tracker, a trip packing planner, a recipe organizer, a content idea organizer, an idea-voting board, a quote calculator, and a recurring-task tracker. All 10 store one type of data and answer one question about it.

What web apps can beginners build without coding?

Beginners can build any simple web app without coding that collects, organizes, or calculates data without needing payments, logins, or outside services. Trackers, checklists, calculators, and simple catalogs all qualify. You describe the tool in plain language, and the builder generates the interface and the data structure for you.

Which web app ideas can be finished in a weekend?

Web app ideas for beginners that can be finished in a weekend have one data type, about 5 fields, and one or two views. A packing checklist, a decision matrix, or a quote calculator fits comfortably. Anything with user accounts, payments, or multiple connected record types does not, regardless of how simple the pitch sounds.

How do I choose a simple web app idea?

Choose the idea whose data you can copy from somewhere in 10 minutes and that you’ll use within the next 7 days. Those two conditions matter more than how interesting the idea is, because they’re what get the app tested with real information instead of placeholder rows.

What should a beginner web app include?

A beginner web app should include one input form, one list or table view, one calculated summary such as a count or total, and data that persists after a refresh. That’s the complete requirement. Everything else is version 2.

What features should I leave out of my first web app?

Leave out user accounts, payments, notifications, file uploads, and multi-user editing. Each one adds error states that take longer to handle than the core app itself. Keep the app private by keeping the URL private, and output a copyable summary instead of processing payments.

Can Coderick AI build a web app from a prompt?

Yes. Coderick AI builds a web app from a plain-language prompt, then refines it through continued chat instructions. It generates the interface and the backend together, and includes hosting, SSL, custom domains, user authentication, and version control on paid plans, so there’s no separate infrastructure to configure. 

How should I test a small AI-built web app?

Test a small AI-built web app in five passes: load it empty, add 20 real entries, refresh to confirm data was saved, open it on a phone, and feed it wrong input such as text in a number field. Fix one problem per prompt so you can tell which change fixed what.