Crawl diagnostics · Beginner · 15 minutes, then read the data
How to submit a sitemap to google — Submitting It Takes a Minute. The Coverage Report Is the Point
You submitted the sitemap months ago and never opened the report that would have told you exactly which pages Google refused to index, and why.
The short answer
Submitting the sitemap is one paste into Search Console; the diagnostic value is entirely in the coverage report you read afterwards. It lists every URL Google discovered, which ones it crawled, which ones it indexed and — for the rest — the specific reason it declined, which is where most unanswered ranking questions have been sitting all along.
Two technical details make the file worth crawling. An accurate lastmod, so recrawls are prompted by real changes rather than by a timestamp your plugin rewrites nightly, and a list restricted to canonical, indexable URLs. This runbook covers both, plus how to see Googlebot's actual behaviour in your own access log.
By the HostingFast team · Reviewed 24 August 2026
Beginner
Reader level
5
Stages to work through
Free
Cost of asking
Proven
Proven on our own hardware
Fifteen minutes of setup and a habit afterwards. Assumed: you can find your sitemap URL and open a log file. Not assumed: that submitting a file is the same thing as being indexed, because those two are barely related.
The output you want is not a green tick, it is a list. Specifically, the list of URLs Google chose not to index, with a reason next to each one — because that list is a work queue rather than a status.
You already have a sitemap. Check it is telling the truth
WordPress core generates one at wp-sitemap.xml, and most SEO plugins generate their own index instead, commonly at sitemap_index.xml. Load whichever applies and read it. You are checking three things: that the URLs are canonical and absolute, that noindexed and redirected pages are absent, and that the lastmod values reflect real edits.
That last one matters more than people expect. A lastmod rewritten on every cache flush teaches a crawler to ignore the field, which costs you the one signal that reliably prompts a recrawl after a genuine update. If your plugin does that, turn lastmod off rather than publish a value that is wrong.
Verify by DNS, then submit once
Domain-level verification via a DNS TXT record covers every subdomain and both protocols in one property, which saves you maintaining four overlapping properties that each hold a quarter of the picture. Add the record at your DNS provider and verify; it stays valid as long as the record stays in place.
Then paste the sitemap path into the Sitemaps section once. There is no benefit in resubmitting: the crawler refetches the file on its own schedule, and repeated submissions do not accelerate anything. Nothing on this page speeds up indexing; it makes indexing observable.
Read coverage as data, not as a verdict
The report splits your URLs into indexed and not indexed, with a reason on each exclusion: crawled but not indexed, discovered but not crawled, duplicate without a user-selected canonical, blocked by robots.txt, redirect, soft 404. Each reason implies a different fix, and most of them are fixes to the site rather than appeals to Google.
Discovered but not crawled in volume is the one to take seriously, because it usually means crawl capacity is being spent elsewhere — on faceted URLs, on paginated archives, or on a server that responds slowly enough that the crawler backs off. That is a performance problem wearing an SEO costume.
Then look at your own logs
Search Console tells you what Google decided; the access log tells you what Google did. Filter your log for the crawler's user agent and you can see which paths it spends its requests on, how often it returns, and what status codes it received. Sites with a crawl problem almost always have an obvious pattern of wasted requests in there.
Response time is part of that picture, since a crawler slows down against a slow origin. LiteSpeed is compiled into our web server and cached hits never enter PHP, which keeps the response times a crawler measures low without you configuring anything. Bing Webmaster Tools will import your Search Console setup in a couple of minutes if you want the second data source.
What the crawler measures when it visits
Crawl rate responds to how quickly your origin answers, and here that is a LiteSpeed cache compiled into the web server sitting on NVMe storage. Cached responses never enter PHP, which is why the response times a crawler records stay low without any tuning on your part.
NVMe storage and LiteSpeed caching power every tier, from the entry plan upward — speed is the baseline here rather than an upsell.
- Cached responses served without entering PHP at all
- NVMe storage on every tier, entry plan included
- Raw access logs in the panel, for the crawler's real behaviour
- Engineers on shift if a crawl pattern needs explaining
Why HostingFast
Standard on every plan
The report is the deliverable
You leave with the list of URLs Google declined and the reason for each, which is a work queue rather than a status light.
lastmod treated as a signal
An accurate timestamp prompts recrawls; one rewritten nightly teaches the crawler to ignore the field entirely.
One property, whole picture
DNS-level verification covers every subdomain and protocol, instead of four properties each holding a quarter of your data.
Crawl waste made visible
The access log shows where requests actually go, which is how faceted URLs and endless pagination get caught.
Performance in the SEO frame
Discovered but not crawled is frequently a response-time problem, and this page says so rather than blaming the sitemap.
A second data source
Bing Webmaster Tools imports the same setup in minutes, and it is the submission most sites never bother to make.
Quick Start
From order to online
- 1
Open the sitemap you already generate
wp-sitemap.xml from core, or the plugin's own index. Confirm the URLs are canonical and absolute and that noindexed pages are not in the list.
- 2
Check what lastmod is doing
It should change when content changes and not otherwise. A value rewritten on every cache flush is worse than no value at all.
- 3
Verify at domain level
A DNS TXT record gives you one property covering every subdomain and both protocols, rather than four partial views of the same site.
- 4
Submit once, then read coverage
Paste the path, then go to the coverage report. The exclusion reasons are the output; resubmitting the file achieves nothing.
- 5
Cross-check against your access log
Filter for the crawler's user agent and look at which paths it spends requests on. Wasted crawl shows up as an obvious pattern.
Built In
Loaded onto every plan
- LiteSpeed caching compiled into the server, not bolted on by plugin
- NVMe SSD storage on every tier, including the entry plan
- cPanel — the control panel most of the industry already runs
- Per-site PHP version switching from the control panel
- Free SSL on every plan, reissued automatically before it can expire
- Staging environments for rehearsing a change before it ships
- Daily backups on every plan, with restores you run yourself from the panel
- WordPress Toolkit, with updates handled for you
- A renewal price identical to the one you signed up at
- Human support on duty every hour of every day
Frequently Asked
What people ask us most often
Does an accurate lastmod actually change how often a page is recrawled?
It is a signal a crawler can use, and it only works if it is honest. A lastmod that changes when the content changes helps a recrawl arrive after a genuine update; a lastmod rewritten on every cache flush trains the crawler to ignore the field. If your plugin cannot be accurate, publishing no lastmod is the better option.
Which sitemap does WordPress core produce, and does it clash with my plugin's?
Core generates wp-sitemap.xml, and most SEO plugins disable it and publish their own index instead — typically sitemap_index.xml. Having both live is untidy rather than harmful, but submit only one and make sure the other is not advertising URLs the first one deliberately excluded.
How do I see Googlebot's real behaviour in the access log?
Filter the raw access log in the panel for the crawler's user agent, then group by path and status code. You will usually find requests concentrated on something you did not intend — faceted parameters, endless pagination, an old feed — and that is crawl capacity not being spent on the pages you care about.
Should paginated archive pages be in the sitemap at all?
Generally no. Sitemaps are for canonical, indexable destinations, and page four of a category archive is neither the canonical home of anything nor a page anybody should land on from search. Leave them crawlable through links, keep them out of the file, and let the sitemap stay a clean statement of what you actually want indexed.
Keep reading
How to Update WordPress Safely
Treat every update as a release: snapshot, order, rehearse on staging, then re-measure response time — beginner, roughly 20 minutes per cycle.
How to Minify CSS and JavaScript
Measure render-blocking milliseconds, then change one flag at a time with the console open — intermediate, roughly 30 minutes.
DNS (Domain Name System) (Glossary)
The lookup layer that turns a name into an address, including the TXT record this verification needs.
Ecommerce Hosting
Fast, hardened foundations for online stores on any platform.
WooCommerce Hosting
Store-ready hosting with Redis caching and headroom reserved for checkout traffic.
Changing hosts? Run through our checklist first.
A straightforward sequence for a switch your visitors never feel: which files move first, how to shift email across without losing a single message, the right moment to repoint DNS, and the two mistakes behind almost all the downtime we get asked to rescue.
Give the crawler a quick origin.
LiteSpeed compiled into the server, NVMe on every tier, raw access logs in the panel, and a renewal price that does not move.
View Ecommerce Hosting plans