How to Import Sitemaps and Search Console URLs into Promptwatch
How we import sitemaps and Search Console URLs into Promptwatch so page inventory sits next to crawler logs.
Crawler logs without a page list are a firehose. On Professional, Business, or an agency plan, we import sitemaps and, when GSC is connected, Search Console URLs into Promptwatch so inventory sits next to the fetches. Essential can hold the inventory but has no listed crawler-log allowance. Indexing status and AI crawler reads on the same URL is the view we want before we rewrite anything.
The reason we want that view is simple. A crawler log tells you a bot fetched a path. It does not tell you whether that path is a page you care about, a parameter variant, or a staging URL that leaked into production. The page list is what turns raw fetch rows into a question you can answer: did the bot read a real page, and did that page ever get cited. Without the inventory, you are reading logs in one tab and your sitemap in another, matching by eye. With the inventory imported, the join happens inside the project, and the gap between "fetched" and "cited" becomes a ticket.
This is not a second sitemap for "AI." We upload the sitemap the site already ships. If they have more than one (blog vs app, locale vs locale), we add those too. Multiple sitemaps per project is supported. Add every sitemap the site already publishes. One project per hostname.
Sitemaps first
Add the sitemap URLs the CMS or the framework already exposes. We do not generate a fake sitemap in a spreadsheet and call it GEO. If the sitemap is stale, that is a CMS ticket, not a Promptwatch setting. The inventory has to reflect what the site actually serves, because every later filter runs against it. A sitemap that lists deleted URLs, or omits new ones, makes the log view lie to you in both directions.
A stale sitemap hurts in two ways at once. A deleted URL still in the sitemap shows up as "fetched but gone," and the team chases a page that no longer exists. A new URL missing from the sitemap shows up as "never fetched," and the team assumes the bot ignored it when the real cause is that the inventory never listed it. Both errors start in the CMS, not in the visibility tool. Fix the sitemap at the source, then import.
Do we need GSC if we already have sitemaps? Sitemaps are enough to start inventory. GSC URL import is how we catch pages Google has that the sitemap omitted. We still connect GSC read-only on retainers because we also want query import. The URL list is a bonus. The two lists answer different questions. The sitemap is what the site declares. GSC is what Google actually indexed. The gap between them is where the interesting tickets live.
Inventory is the allowlist we filter logs against. When ChatGPTBot hits a URL we do not recognize, we want to know whether it is a param variant, a staging leak, or a page that should have been in the sitemap. When a URL is in the sitemap and never fetched, that is the cheaper miss. See Cloudflare crawler logs and how to get cited by ChatGPT. Connect crawler logs (Cloudflare or the CDN they actually use). Filter logs to inventory URLs. File engineering tickets for fetches that fail. File content tickets for fetches that never get cited. The two ticket types go to two different teams, and that separation is the point of doing the work inside one project instead of a spreadsheet.
GSC URLs as the second list
Settings then Google Search Console. Org read-only OAuth. One property per project. Optional auto URL import plus URL Inspection. Performance sync can pull up to a year of clicks, impressions, CTR, and position. Promptwatch never writes to GSC.
Will import submit the sitemap to Google? No. The GSC connection does not write. Submit and removals stay in Search Console. That boundary matters. We do not want a visibility tool pushing sitemap changes into Google on our behalf, because the sitemap is a source of truth we control through the CMS, not through a third party.
Auto URL import puts GSC pages into the same inventory. That catches URLs Google knows that the sitemap forgot (or the opposite). Turn on auto URL import if we want Google's page list in the same inventory. URL Inspection is there when we need Google's view next to a crawler row. We do not inspect every URL for sport. Use URL Inspection on the few URLs in the SOW.
Query import into Prompt Explorer is a different button. Topics are not pages. Do both if the SOW includes prompts and logs. Connection steps: connect Search Console. Google's generative AI performance reports stay in Search Console for Overviews. They do not replace the sitemap inventory next to crawler logs. Overviews impressions are a Google surface, not a ChatGPT prompt, and the two numbers should not be mixed in one column.
Local businesses still need the local SEO playbook for GBP and location pages. Importing those location URLs is useful. It does not rank the pack. A location URL in inventory tells you whether a crawler fetched the page. It does not move the map pin.
Plan and hygiene
Professional is $245/mo with 25M crawler logs. Kick-off is $199/mo with 10M logs, unlimited projects and prompts, and 10 seats. Business is $579/mo and 100M logs. Essential is $95/mo with MCP and API, but it has no listed crawler-log allowance and is not the plan for this inventory-plus-logs workflow. Explore is free, 10 ChatGPT prompts. G2: 4.7/5.
We do not import a sitemap and then ignore it. Someone checks new URLs after a Webflow publish. Drafts we pushed from Promptwatch should appear in inventory after they go live, not while they are still ?draft. After a Webflow publish, confirm the live URL is in a sitemap or in the GSC list. A draft URL in inventory is noise, because a crawler fetching a draft tells you nothing about the live page.
No instant alerts when a sitemap URL 404s. We catch it in the same weekly pass as the rest of Agent Analytics. The weekly cadence is deliberate. Daily alerts on every 404 would train the team to ignore the channel. A weekly pass that classifies fetch failures and content misses is the workflow that actually gets tickets filed and closed.
FAQ
Do we need GSC if we already have sitemaps?
Sitemaps are enough to start inventory. GSC URL import is how we catch pages Google has that the sitemap omitted. We still connect GSC read-only on retainers because we also want query import.
Will import submit the sitemap to Google?
No. The GSC connection does not write. Submit and removals stay in Search Console.
Is this a second sitemap for AI?
No. We upload the sitemap the site already ships. If they have more than one (blog vs app, locale vs locale), we add those too.
If you want inventory wired, hello@1001seomedia.com. Send the sitemap URLs and the Search Console property.