Five minutes. Every address delivered.
A Thursday afternoon at Peak Cycle Co., an example bike shop on WordPress. Here’s sitemap monitoring finding the problem, step by step.
- Step 1 · 2:00 pm
Open the tree.
Every sitemap you’ve submitted in Search Console, grouped under your site. Each one shows how many pages it lists, with a green, amber or red mark from what Google reported.
QueryCatch · Sitemaps4 sitemaps · 1,354 pagespeakcycle.example- post-sitemap.xml64 pages
- page-sitemap.xml12 pages
- product-sitemap.xml1,240 pages
- product_cat-sitemap.xml38 pages
- Step 2 · 2:01 pm
Spot the red mark.
Red means Google reported errors for that sitemap. Amber means warnings. You know which file to look at without digging through Search Console.
QueryCatch · Sitemaps · product-sitemap.xml - Step 3 · 2:03 pm
Check the file still works.
One click checks the sitemap file is still there. This one moved when the shop changed SEO plugins, so the fix is a two-minute job in the plugin’s settings.
QueryCatch · Sitemaps · product-sitemap.xml - Step 4 · 2:05 pm
Catch the forgotten one.
Each sitemap shows when it was last submitted to Search Console. Anything older than 90 days gets an “Old sitemap” flag, a nudge to resubmit after big changes.
QueryCatch · Sitemaps4 sitemaps · 1,354 pagespeakcycle.example- post-sitemap.xml64 pages
- page-sitemap.xmlOld sitemap
- product-sitemap.xml1,240 pages
- product_cat-sitemap.xml38 pages
2:06 pm
Route fixed. Back to the bikes.
