"0 URLs, 1 error" in Search Console: when it's a real problem and when it isn't
If you opened Google Search Console, looked at your sitemap report, and saw a row that says '0 URLs' with a red '1 error' next to it, you're in the right place. Here's exactly what's going on, when it matters, and when it doesn't.
Table of contents
What "0 URLs, 1 error" actually means
A sitemap is a list of URLs you're asking Google to crawl. The format is XML — a <urlset> tag wrapping one<url> entry per page. When Google fetches the file, it counts the entries inside.
If the count is zero — meaning the file exists, the XML is valid, but there are no <url> entries — Google logs it as an error in the Sitemaps report. The wording is misleading because nothing is actually broken. The file works. It's just empty right now.
This shows up in two specific situations on a healthy site, and both are usually harmless.
Case 1: News sitemap is empty
Google News sitemaps follow a different rule than regular sitemaps: they're only allowed to contain articles published within the last48 hours. If you publish a new blog post on Monday, it's eligible to appear in your news sitemap until Wednesday morning, then it falls off automatically.
For most Colorado businesses — HVAC companies, law firms, dentists, roofers — this means the news sitemap is empty almost all the time. You're not publishing daily, so there's nothing recent enough to include. The "1 error" is permanent until your publishing cadence changes.
The honest fix: if you don't publish at least 2–3 new articles per week, remove the news sitemap from your sitemap index entirely. Google News indexing is a niche feature for actual news publishers (newspapers, magazines, daily blogs). For a typical local service business, your blog content gets indexed perfectly well via your regular sitemap — no news sitemap required.
Case 2: DB-backed / published-articles sitemap is empty
Many modern websites separate their content into two sitemap groups: one for the static pages built into the site (services, locations, about, contact) and one for content stored in a database — usually AI- or editorially-published articles that get added over time.
When the database table is empty (no published articles yet), the sitemap is empty too. Same "0 URLs, 1 error" outcome. The fix is nothing — the sitemap will populate itself the moment the first article publishes, and the error will clear on Google's next crawl (usually within a few days).
If you've had the empty published-articles sitemap submitted for weeks and still haven't shipped any content, that's a content problem, not a sitemap problem. The sitemap is correctly reporting that you have nothing to show.
The rule of thumb
Use this simple decision tree when you see "0 URLs, 1 error" in Search Console:
- Will this sitemap have content soon? Leave it. The error resolves automatically when the first URL appears.
- Will it always be empty? Remove it from your sitemap index and unsubmit it from Search Console.
- Was it accidentally created by a plugin or template?Delete the file from the server and unsubmit it.
The mistake to avoid: panicking and deleting your entire sitemap infrastructure because one row is red. The other 6 or 7 sitemap rows next to it are likely showing "Success" with hundreds of URLs each — those are doing exactly what they should.
How to clean it up in Search Console
If you decide to remove an empty sitemap, the cleanup is two steps:
- Remove it from your sitemap index file. Most sites have a master
sitemap.xmlthat points to sub-sitemaps likesitemap-cities.xmlandsitemap-news.xml. Edit the index to remove the line that references the empty one. - Unsubmit it in Search Console. Go toSitemaps → click the row → click the three-dot menu →Remove sitemap. Within a few days the row disappears from your report.
If you want to keep the file but have it report "Success / 0 URLs" instead of "1 error," configure it to return a valid empty<urlset> document (the wrapper tag with no children). Some Google Search Console configurations treat that as success rather than error.
What you can safely ignore — and what you can't
Here's the full picture of which Search Console sitemap states matter and which don't:
- Success, N URLs: Working as intended. Nothing to do.
- Success, 0 URLs (or "1 error" with 0 URLs):Empty sitemap. Almost always harmless. Apply the rule of thumb above.
- Couldn't fetch: Real problem. Your sitemap URL is returning a 404 or 500. Fix the route immediately — Google can't read it at all.
- Has errors: Real problem. Click into the report to see which URLs are broken or which lines are malformed XML.
- Invalid sitemap: Real problem. The XML is malformed. Validate it with a sitemap validator and fix the syntax.
The pattern: anything that prevents Google from reading the file is urgent. Anything that just means "we read it and it was empty" is not.
If you're a Colorado business owner who'd rather have someone else manage this and a hundred other small SEO health-check items, that's what we do at Colorado Web Impressions. We monitor Search Console for our clients monthly and triage exactly these kinds of "is this a problem?" questions so you don't have to.
Frequently asked questions
Will Google penalize my site for an empty sitemap?+
No. Google does not penalize sites for empty sitemaps. The 'error' label in Search Console is a status indicator, not a ranking factor. Your other sitemaps and pages are crawled and ranked completely independently of this one row.
Should I delete the empty sitemap file?+
Only if you don't plan to populate it. If it's a news sitemap and you don't publish news daily, yes — remove it from your sitemap index. If it's a published-articles sitemap and you'll be publishing soon, leave it. The error will resolve on its own as soon as the first URL appears.
What about /image-sitemap.xml or /video-sitemap.xml showing the same error?+
Same logic. An empty image sitemap means no <image:image> entries were emitted. Either remove it from the sitemap index until you have media to list, or wait for the next build cycle to populate it. Neither version harms your rankings.
How is this different from a real sitemap error?+
A 'real' sitemap error is malformed XML, an HTTP 500 response, an unreachable URL, or URLs that violate your robots.txt. Those should be fixed immediately because they block Google from reading the sitemap at all. '0 URLs, 1 error' means Google read the file fine — it was just empty. Big difference.
Can I just leave it and forget about it?+
Yes, in most cases. The empty-sitemap error doesn't compound, doesn't escalate, and doesn't bleed into other Search Console reports. The only practical reason to clean it up is to keep your sitemap report visually green so real errors stand out the next time one shows up.
Want us to do this for your Colorado business?
Owner-led strategy from our Colorado Springs HQ. No contracts, no outsourcing.