# Magento 2 Quick Setup Check: A Post-Install Audit Every Store Should Run

![Magento 2 quick setup check editorial hero](images/magento-2-quick-setup-check.webp)

## Overview

A fresh Magento 2 install is not a finished store.

Default settings are designed to start the application - not to run a real shop.

Stores that skip the post-install audit usually discover problems later:

- Wrong currency on invoices
- Missing emails
- Broken indexes
- Search returning nothing
- Robots.txt blocking the whole site

The key point:
**A 30-minute setup check now prevents weeks of confusing bugs later.**

This guide walks through every setting a Magento 2 store should verify before going live.

---

![Magento 2 quick setup check candid lifestyle scene](images/magento-2-quick-setup-check-lifestyle.webp)

## Why a Setup Check Matters

### 1. Default Settings Are Generic

Out of the box, Magento uses:

- A placeholder timezone
- A demo currency
- Generic email addresses
- Empty SEO fields

None of these are right for a real store.

---

### 2. Bugs Hide Until Real Customers Hit Them

Some settings only matter:

- During checkout
- When emails are sent
- When search engines crawl
- When indexes run on cron

A working homepage proves nothing.

---

### 3. Fixing Live Is Always Worse

Wrong currency on a placed order is messy.

Wrong store email on a transactional template is messy.

Catch these before customers see them.

---

## The Magento 2 Setup Check (Step by Step)

### Step 1 - Confirm Magento Mode

Magento should run in:

- **Production mode** for live stores
- **Developer mode** only on local / staging

Check with:

```
php bin/magento deploy:mode:show
```

Switch with:

```
php bin/magento deploy:mode:set production
```

---

### Step 2 - Verify Base URLs

Go to:
**Stores > Configuration > General > Web**

Confirm:

- Base URL (Unsecure)
- Base URL (Secure)
- Both end in a trailing slash
- Both match the actual domain

Then enable:

- Use Secure URLs on Storefront = Yes
- Use Secure URLs on Admin = Yes

---

### Step 3 - Set the Correct Timezone, Locale, Currency

**Stores > Configuration > General > General**

Set:

- Country (default)
- Timezone
- Locale

**Stores > Configuration > General > Currency Setup**

Set:

- Base currency
- Default display currency
- Allowed currencies

If you serve multiple regions, configure per store view.

---

### Step 4 - Update Store Emails

**Stores > Configuration > General > Store Email Addresses**

Replace every default email (sales@example.com, etc.) with real, monitored addresses.

These addresses appear on:

- Order confirmations
- Invoice emails
- Customer welcome emails

Default addresses make a store look unfinished.

---

### Step 5 - Configure Cron

Cron drives:

- Indexers
- Email queue
- Sitemap generation
- Currency rates
- Catalog price rules

Verify with:

```
crontab -l -u <magento-user>
```

For Magento 2.4.x the only required cron entry is:

```
* * * * * php /path/to/magento/bin/magento cron:run
```

You can also let Magento install it for you:

```
php bin/magento cron:install
```

If cron is not running, almost nothing automated works.

---

### Step 6 - Check Indexers

```
php bin/magento indexer:status
```

All indexers should show:

- Index status: Ready
- Update on: Schedule (recommended for production)

Reindex if any are stuck:

```
php bin/magento indexer:reindex
```

---

### Step 7 - Confirm Search Engine

For real stores, Magento needs:

- OpenSearch - the recommended default from Magento 2.4.6 onward
- Or Elasticsearch 8 - still supported on 2.4.6+ but flagged deprecated in the engine dropdown
- Or Elasticsearch 7 - the default on Magento 2.4.0-2.4.5

**Stores > Configuration > Catalog > Catalog > Catalog Search**

Verify:

- Search engine
- Server hostname / port
- Index prefix

Then test the connection.

---

### Step 8 - Search Engine Robots and Sitemap

The default robots meta tag is set per store view in:

**Content > Design > Configuration > [edit your store view] > Other Settings > Search Engine Robots**

For live stores, set:

- Default Robots = INDEX, FOLLOW

For the actual `robots.txt` file, edit `pub/robots.txt` (or the equivalent in your deployment). Magento does not generate it automatically.

Generate a sitemap:

**Marketing > SEO & Search > Site Map > Add Sitemap**

Then submit it in Google Search Console and Bing Webmaster Tools.

---

### Step 9 - SSL Certificate and HTTPS

Confirm:

- Certificate is installed
- Auto-renewal is configured
- All admin and frontend URLs use HTTPS

Run an external check (e.g. SSL Labs) to confirm grade A.

---

### Step 10 - Configure Cache and Sessions

**Production stores should use:**

- Redis (or Valkey) for cache and sessions
- Varnish for full page cache

A clean Magento install uses file-based cache. That works for a demo, not a real store.

---

### Step 11 - Tax and Shipping Sanity Check

Add:

- Tax rates for every region you sell to
- Shipping methods customers will actually see

Place a test order to confirm:

- Tax appears correctly
- Shipping calculates correctly
- Totals match expectations

---

### Step 12 - Place a Real Test Order

End the audit with a full checkout.

Confirm:

- Order email arrives
- Invoice email arrives
- Currency, totals, address all correct
- Stock decrements properly
- Customer account works

This catches more issues than any individual settings check.

---

## Common Setup Mistakes

### Mistake 1 - Leaving Demo Data in Place

Magento sample data is great for testing.

It is not safe for production.

Remove it before launch.

---

### Mistake 2 - Default Admin URL

The default `/admin` URL is the first thing bots try.

Change it in:

```
app/etc/env.php
```

Or set it during install. A custom path drastically reduces brute-force attempts.

---

### Mistake 3 - No 2FA

Magento 2 includes Two-Factor Authentication.

Enable it for every admin user.

---

### Mistake 4 - Forgetting Backups

Before a store goes live, set up:

- Daily database backups
- File system backups
- Off-site storage

Test the restore process at least once.

---

## Where Moogento Fits

Several Moogento modules support the post-launch operations layer:

- **AuditEasy** - tracks admin and customer activity, flags risky changes
- **Pulse** - performance and revenue dashboards so issues surface fast
- **NoMoreSpam / NoMoreSpamPro** - blocks spam registrations and orders before they hit email queues

These do not replace the setup check - they make sure the running store stays healthy.

---

## Real-World Impact

Stores that complete a structured setup check before launch typically:

- Avoid the "first day in production" panic
- Ship with correct emails, taxes, and currencies
- Run faster from day one
- Spend less time on early support tickets

## FAQs

### What's the first thing to check after installing Magento 2?
Switch to production mode and confirm base URLs and store emails are real.

### Do I need to change the default admin URL?
Yes - a custom admin path is one of the easiest, highest-impact security wins.

### How often should I rerun the setup check?
After every major upgrade, theme change, or migration.

### Why are my Magento emails not sending?
Almost always cron, queue, or sender address. Step 4 and Step 5 in this guide cover both.

### Is OpenSearch required for Magento 2?
OpenSearch is the recommended default from Magento 2.4.6 onward. Elasticsearch 8 is still selectable on 2.4.6+ but flagged deprecated. Earlier Magento versions use Elasticsearch 7.

---

## Next Steps

To get a Magento 2 store launch-ready:

- Run every step in this guide before opening to customers
- Place at least one real test order
- Schedule a follow-up audit one week after launch
- Pair the setup check with a security review

Setup is boring. Setup is also where most launch problems hide.