Choose a property, a small URL sample and one question before starting. Search engine reports help locate symptoms, but they do not replace checking server responses, source markup or the rendered page. Ask the assistant to say which facts it retrieved and which checks require you to inspect the site.
Review sitemap health, robots.txt and noindex alongside these questions.
Check discovery and sitemap inputs
List the sitemaps submitted for my Google property. Include the reported counts, errors and warnings, and identify files I should check directly.
Returns sitemap report evidence and a file review list for you.
List sitemap URLs for this site in each connected source. Flag differences and fields that are unavailable rather than assuming identical engine reports.
Returns a cross-source submission inventory with explicit gaps in the evidence.
Audit the canonical URLs in this sitemap for Google index status. Report progress, remaining URLs and the continuation offset for the next batch.
Returns an inspection-based check of the URLs you expect in search.
Based on the reported sitemap errors, list checks I should make on the file URL, XML and listed pages. Separate evidence from suggestions.
Returns a troubleshooting sequence without claiming the assistant crawled your site.
Inspect canonical and indexing evidence
Inspect these old and replacement URLs after my migration. Show index status, last crawl and canonical information for each supplied URL.
Returns recorded Google inspection details to compare with your migration plan.
Inspect these parameter variants and the clean URL. Compare their reported canonicals and flag differences from the preferred URL I specify.
Returns duplicate-URL evidence for a canonical review on your own site.
Inspect this page for rich result findings. Summarize what the inspection reports and identify what still needs a direct markup check.
Returns available rich result evidence without promising enhanced search appearance.
For this unindexed page, show the inspection evidence and suggest which access, directive and content checks I should perform next.
Returns a scoped checklist rather than an unsupported diagnosis of the cause.
Review other engines and close the loop
For my connected Bing site, list crawl issues by issue type and HTTP code. Include affected URLs so I can verify server behavior.
Returns engine-reported crawl failures organized for a direct technical review.
For my connected Yandex site, show the site summary and reported problems by severity. Keep the engine’s findings separate from proposed fixes.
Returns pages-in-search context, excluded pages and reported Yandex site problems.
Before resubmitting this corrected sitemap, explain which connected sources can accept it and what information is needed. Wait for my confirmation before submitting.
Returns a concrete submission plan for a later approved write action.
Summarize our technical findings as confirmed report evidence, direct site checks still needed and a small set of URLs to reinspect after fixes.
Returns a handoff that distinguishes retrieved evidence from work still outstanding.
Use the answers carefully
mowteng never edits your site's pages. Sitemap and URL submissions are write actions, marked so assistants ask before running them. Bulk Google inspection uses the property's 2,000-per-day quota. Keep a small set of representative URLs for retesting after you fix a shared cause, then expand the review if the evidence warrants it.