Compare Google and Bing Indexing Evidence
Each Search Engine observes a URL on its own schedule and returns different fields. Keep both dates beside their evidence.
Check both connections
Use Choose access to connect Google and Bing in the same mode. Confirm that the URL belongs to the selected Site. Hosted Bing commands use a hosted Site ID. Local Bing commands use the exact URL printed by bing sites.
gscdump sites --json
gscdump bing sites --jsonRead Google evidence
gscdump inspect https://example.com/blog/post --site example.com --jsonRecord the inspection time, verdict, last crawl, and canonical fields when present. Absent fields mean Google did not return them. See Indexing Evidence for saved observations and quotas.
Read Bing evidence
gscdump bing inspect https://example.com/blog/post \
--site s_SITE_ID --mode hosted --jsonWith local Bing credentials, run:
gscdump bing inspect https://example.com/blog/post \
--site https://example.com/ --mode local --jsonHosted mode reads saved Bing Indexing Evidence; Local mode asks Bing directly. The Bing reference covers credentials and result errors. An unknown result does not prove absence from Bing's index.
Compare only shared facts
| Search Engine | Observation date | Crawl evidence | Canonical or verdict | Unknown fields |
|---|---|---|---|---|
| Copy from inspection | Copy if present | Copy if present | List missing fields. | |
| Bing | Copy from Bing result | Copy if present | Copy if present | List missing fields. |
Fill this table from the command results. Do not copy one Search Engine's verdict into the other row. A crawl observation does not prove indexing.
Follow up in each Search Engine
Check the page's response, canonical, robots rules, and sitemap in each tool. Recheck after the next dated observation. If traffic also fell, use Traffic drop. More URL checks: Check visibility.