How to create custom Magento maintenance pages

Key takeaways

• Custom Magento maintenance pages explain planned downtime.
• Magento 1 and Magento 2 use different workflows.
• Use a proper 503 response for true maintenance mode.
• Test the page, cache, mobile layout, and return-to-live process.

Magento maintenance services are essential for keeping your website running smoothly and ensuring it’s up to date with the latest security standards.

When Magento maintenance is necessary, a custom maintenance page can keep website visitors in the loop. It can explain what’s happening, share when the site may return, and make planned downtime feel more professional.

This guide explains how to create custom Magento maintenance pages in Magento 1 and Magento 2. It also explains when to use a CMS page, when a native 503 template may be better, and what to test after maintenance.

What is a Magento maintenance page?

A Magento maintenance page is the temporary page visitors see when your store is unavailable during updates, troubleshooting, deployments, or planned server work.

The default Magento maintenance page is usually vague, which can make visitors think the site is down unexpectedly. A custom page gives them more context with a clear message, expected return time, support details, and branding.

Magento maintenance page methods

There are several ways to create a Magento maintenance page. The right method depends on whether Magento can still load normally or whether the store is in true maintenance mode.

The original CMS-page approach is useful when you want a simple page that can be created from the Admin Panel. For deeper maintenance, a native 503 page or server-level page may be safer.

What should a custom Magento maintenance page include?

A custom maintenance page should be short, clear, and helpful. It should include a simple maintenance message, expected return time if available, your logo or brand styling, support contact or help link, and reassurance that the store will return soon. You can also include social links or a newsletter signup if they’re appropriate for your audience.

Keep the page mobile-friendly and avoid loading too many assets that may not work during maintenance.

How to create a custom maintenance page in Magento 1

This method creates a CMS page in Magento 1 and uses it as a temporary customer-facing page.

Step 1: Open your Magento Admin Panel and go to Pages

Navigate to the CMS dropdown on the top of your admin panel and select Pages.

Step 2: Add a new page

Under Manage Pages, select Add New Page.

Step 3: Fill in page information

In the New Page section, you’ll be prompted to provide information for your new maintenance page. Add information for Page Title, URL Key, and Status.

Use a clear URL key such as:

Step 4: Complete the Content section

Under Page Information, you’ll see Content. Clicking it will open a section for editing your maintenance page.

Add a clear message, an estimated return time if available, and any support details visitors should know.

Step 5: Remove default content

Next, go to Design under Page Information. Click Layout and select Empty from the dropdown menu. Then, save the page.

Step 6: Flush the cache

Once your new Magento maintenance service page is created, go to System on the top of your admin panel and click Cache Management. Select Flush Magento Cache.

Step 7: Go to configuration

Navigate to System and click Configuration.

Step 8: Perform the final configuration steps

Under Configuration > Web > Default Pages, enter the name of your maintenance page for the CMS Home Page and CMS No Route Page.

Set Show Breadcrumbs for CMS Pages to No, then save the configuration and flush Magento cache again.

How to create a custom maintenance page in Magento 2 with a CMS page

This method creates a Magento 2 CMS page through the Admin Panel and Page Builder.

Step 1: Go to Pages

In the Magento Admin Panel, go to Content > Elements > Pages.

Step 2: Create a new page

Click Add New Page.

Step 3: Add information for your new page

Create a suitable Page Title.

Use a clear title such as “Maintenance Page” or “We’ll Be Back Soon.”

Step 4: Use Page Builder to fill in new page content

Under the Content dropdown menu, type in a Content Heading. This step is optional. Select Edit with Page Builder, which will take you to the page editor.

You can start building your maintenance page. 

Add your message, brand image, and any helpful visitor details. If you know when your website will be back online, include that in the message.

Step 5: Update and remove default content

Under New Page, go to Search Engine Optimization. Next, enter a URL Key for your new page. It should only contain lowercase letters and hyphens.

Then go to Design. For Layout, choose Empty. Under Custom Design Update, choose the theme and layout settings that fit your page, then save your changes.

Step 6: Flush the Magento cache

Under System, navigate to Tools and then to Cache Management. Here, you can select Flush Magento Cache.

Step 7: Perform the last configuration steps

Navigate to the Default Page settings. Under Stores in the left-hand panel, go to Settings > Configuration, then select General. From Web under General, scroll down until you see Default Pages.

Under CMS Home Page and CMS No Route Page, enter the name of the custom maintenance page you’ve just created. For Show Breadcrumbs for CMS Pages, select No. Click Save Config.

Flush cache again after saving the configuration.

How to create a native Magento 2 custom 503 maintenance page

A native 503 page customizes Magento’s error processor. This is the better fit for true maintenance mode because it doesn’t depend on a normal CMS page loading through Magento.

Step 1: Create a custom errors folder

Access your Magento installation through SSH, SFTP, or FTP.

Create a custom folder here:

Copy this file:

into the custom folder.

Step 2: Register the custom skin

Copy or rename:

to:

Then update the skin value:

Step 3: Customize the design

Edit:

Add your maintenance message, logo, styling, support details, and return-time information.

Keep the design simple. If your page relies on assets that may not load during maintenance, visitors may see a broken layout.

Magento 1 custom 503 page note

Magento 1 also uses an /errors/ directory for error page templates. Common files include:

Copy default files before editing so you can restore the original templates if needed.

Server-level maintenance page option

A server-level static page can help during deeper infrastructure work where PHP or Magento may not load reliably.

This option may be useful during PHP version changes, web server changes, major deployments, core file changes, database maintenance, or situations where Magento cannot process its own 503 page.

For NGINX or Apache rules, work with a developer or hosting provider. A small configuration error can block valid traffic or keep the store in maintenance longer than intended.

How to enable and disable Magento 2 maintenance mode

After your template is ready, you can manage Magento 2 maintenance mode with CLI commands.

Enable maintenance mode:

Allow a developer IP address:

Disable maintenance mode:

After disabling maintenance mode, clear Magento, server, and CDN cache if the maintenance page still appears.

How Magento 1 maintenance mode works

Magento 1 maintenance mode commonly uses a maintenance.flag file in the Magento root directory. When the file exists, Magento shows the maintenance response. When the file is removed, the store returns to normal.

Test custom Magento 1 maintenance pages before planned downtime so you know what customers will see.

503 status and SEO considerations

For true maintenance mode, the maintenance page should return a 503 Service Unavailable response where appropriate.

A 503 response tells search engines the downtime is temporary. Avoid returning 200 OK for a real outage page or 404 Not Found for planned downtime.

Cache and CDN considerations

After updating the maintenance page and flushing Magento cache, also clear server cache, CDN cache, full-page cache, and browser cache during testing. Cache layers can keep an old maintenance page visible after the page has been updated or disabled.

Post-maintenance checklist

After maintenance:

• Disable maintenance mode
• Clear Magento cache
• Clear CDN and server cache
• Confirm the custom page no longer appears
• Test the homepage, category pages, product pages, cart, and checkout
• Test customer login
• Check mobile layout
• Review logs for errors
• Remove temporary server rules or IP allowlists if no longer needed

Common Magento maintenance page mistakes

Common mistakes include mixing Magento 1 and Magento 2 paths, editing the wrong folder, forgetting to clear cache, using a CMS page during true maintenance mode, returning the wrong HTTP status, or leaving maintenance mode enabled after work is complete.

Magento custom maintenance page FAQs

Getting started with custom Magento maintenance pages

Custom Magento maintenance pages help communicate planned downtime, but the best method depends on whether Magento is still loading normally or the store is in true maintenance mode.

Start by deciding whether you need a CMS page, native 503 template, or server-level page. Then create the page in staging and test it before planned maintenance.

Custom maintenance pages work best when your Magento environment, cache layers, server configuration, and support are easy to manage. Explore Liquid Web Magento hosting for infrastructure and support built to help handle Magento maintenance with confidence.

• Magento 2 help — frequently asked questions
• Magento 2 go-live checklist
• Speeding up a slow-loading Magento 2 Dashboard
• RabbitMQ and Magento 2 on managed hosting by Liquid Web
• Magento 2 Admin Panel — optimizing loading speeds for admins
• Magento 2 CAPTCHA

Edith Fernandez