When your website goes down, the natural instinct is to put up a friendly “We’ll be back soon” page. Many WordPress sites do this automatically during updates, hosting trouble or a plugin crash. The catch is the status code that page is sent with. Google’s John Mueller recently explained, in a LinkedIn reply reported by Search Engine Roundtable on 17 November 2026, why serving that message with a 200 (success) code is a bad idea. If your clinic, shop or coaching site is your main source of enquiries, this is worth five minutes of your week.
What Mueller actually warned about
Someone asked whether a “back soon” page sent with a 200 status is likely to cause trouble if the outage lasts only a few hours, or whether the risk only applies to long downtime. According to the Search Engine Roundtable report, Mueller named two concerns.
- Indexing the wrong text. Google may index your page with the “try again later” wording that was visible during the outage. Mueller noted this fixes itself once the real content returns.
- Duplicate removal. If other sites show the same generic message, Google can treat those pages as duplicates and drop them. Recovery can take a while, because duplicate pages tend to be crawled less often.
In plain words: a 200 code tells Google “this page is fine, this is the content.” If the content is really an apology, that is what Google may store.
What Google’s own documentation says about status codes
Google’s Search Central page on HTTP and network errors points the same way. It says a 2xx response makes content eligible for processing, but a 2xx status does not guarantee indexing. It also explains that a page returning 200 whose content looks like an error, such as an empty page or an error message, is reported in Search Console as a soft 404. Google’s advice is simple: the status code and the page content should match.
For genuine server errors, the same document says Google slows its crawling temporarily, keeps already-indexed URLs at first, and eventually drops URLs that keep returning errors. Once your server returns normal responses again, Google gradually raises the crawl rate back up. That is the behaviour you want during a short outage: a clear error signal, then a quick return to normal.
Why this matters for a local business
Imagine a restaurant in Bengaluru whose site goes down on a Friday evening after a hosting migration. Customers searching for the menu or booking link land on a blank maintenance page. If that page was served as a normal 200, you have two problems at once: customers cannot book, and Google may be recording a thin, error-like page for your most important URLs. Many Indian small-business sites sit on shared hosting with a “maintenance mode” plugin switched on during updates, so this is not a rare situation.
It also affects your Google Business Profile indirectly. The website link on your profile points at your homepage or a landing page. If that page is broken or showing an apology for days, visitors from Maps bounce, and you have wasted the click.
Website Development · FSK Digital Marketing
A fast website built to bring in calls.
From ₹24,999 one-time
How to check what your site sends when it is down
You do not need a developer for the first check. Follow these steps:
- Switch on your maintenance mode plugin or ask your host how their maintenance page works.
- Open your homepage in a private browser window and confirm you see the maintenance message.
- Use a free header-checker tool, or the browser’s developer tools (Network tab), to read the status code of that page.
- If it says 200, change the setting so the page sends a 503 (service unavailable) instead. Most maintenance plugins have a toggle for this.
- Turn maintenance mode off, reload, and confirm the normal page returns a 200 and the real content.
- In Search Console, look at the Pages report for soft 404 entries and fix any that are real pages.
A 503 is the standard way to say “temporarily unavailable, come back later”. Google’s documentation describes how it slows crawling and waits rather than treating your content as gone, as long as the error does not persist.
Mistakes to avoid
- Leaving maintenance mode on overnight “just in case”. Persistent errors can lead to dropped URLs.
- Using one generic message across many pages. That is exactly the duplicate pattern Mueller mentioned.
- Redirecting every URL to the homepage during an outage. This confuses visitors and crawlers alike.
- Forgetting plugin updates. Many outages come from an update gone wrong, so test on a staging copy first.
- Never checking uptime. Use a free uptime monitor that emails you when the site stops responding.
A simple routine for owners who do not touch the code
If you run a clinic, a coaching centre or a shop and a freelancer manages your site, turn this into a short routine instead of a technical project. Ask them three questions: what does our maintenance page send, who gets an alert when the site is down, and when did we last test a restore from backup? Write the answers in a shared note. If they cannot answer, that is useful information too. Check the Pages report in Search Console once a month, and after every outage look for new soft 404 entries. This takes ten minutes and keeps small hosting problems from turning into weeks of lost enquiries.
Build a site that rarely needs a “back soon” page
The best fix is fewer outages. A well-built site on reliable hosting, with tested updates and a proper error page, makes this problem rare. At FSK we build mobile-first business sites with speed and call or WhatsApp conversion in mind, and we set up the basics that protect you when something does go wrong. You can read about our WordPress website development service, or see how a related Google change affects your Maps visibility in our post on the November 2026 core update. If you would rather talk it through, visit our contact page.
Frequently asked questions
Is a short outage of a few hours a real risk?
The Search Engine Roundtable report says Mueller was asked exactly this. He described the indexing risk as one that corrects itself when the real content returns, while the duplicate issue can take longer to recover from. Sending the right error code from the start avoids both.
Which status code should my maintenance page use?
A 503 is the usual choice for temporary downtime, because Google’s documentation says it slows crawling temporarily instead of treating the page as final content. Check your plugin or host for a setting that sends it.
How do I know if Google has indexed my error page?
Search for your business name with your site’s address in Google, and check the Pages report in Search Console for soft 404 warnings. If you see error text in the results, fix the status code and request re-indexing of the affected URLs.
Your next step this week: test what your site sends during maintenance, switch it to a 503 if needed, and set up an uptime alert. If you want a site that is fast, stable and built to turn visitors into calls, we are happy to help.
Website Development · FSK Digital Marketing
A fast website built to bring in calls.
From ₹24,999 one-time

