Bing Knowledge Panels: The Dennis Yu Experiment

Bing ranked my homepage and About page first and second when we searched for “Dennis Yu.” The same page also showed a Hong Kong film director and an investment researcher named Dennis Yu. I didn’t see a knowledge panel for me. That’s where I’m starting this experiment.

I’ve shown my Google Knowledge Panel in a previous article. Now I want to see what carries over to Bing. I’ll use my own name as the case and keep a dated record of what we change and what Bing actually shows. If Bing never gives me a panel, that belongs in the record too.

What Bing showed on November 13, 2026

We ran two desktop searches in English while signed out. This is one browser sample. Use the links below to compare with what you see in your own market.

• Dennis Yu. My homepage and official bio were the first two web results. LinkedIn and YouTube followed. Bing’s LinkedIn result headline named Local Service Spotlight, while a separate “Works For” field displayed BlitzMetrics. The film director’s Wikipedia page and the research analyst’s employer bio also appeared. The sidebar showed related searches. We saw no person panel for me.
• Dennis Yu Local Service Spotlight. The company site led the web results, followed by my LinkedIn profile and the company’s About page. My homepage and bio also appeared. We saw no person panel for me on this query either.

My first question is where that conflicting employment label came from. I’ll compare Bing’s snippet with the current LinkedIn Experience entry and the bio it can crawl before changing anything. The other Dennis Yus have every reason to show up for their own names. Our job is to make my company, work, and official profiles easy to connect. The Chiang Mai SEO Conference agenda independently documents my November 12 talk, “The Last SEO Play: How To Trade Rankings For Equity.” It supports the speaking credit. My About page and the company site are where I’d verify my current role.

Can you claim a Bing knowledge panel?

I didn’t find a documented Microsoft workflow equivalent to Google’s person-panel claim. Microsoft still describes Bing Pages as a beta for managing a brand presence. On November 13, its official Get Started link led to a “Page not found” screen, so I couldn’t verify an application path. Microsoft directs business owners to Bing Places for local listings and points to Bing’s Feedback link for factual errors in results. Microsoft’s Bing support guide.

The Bing checklist I’m using

1. Record the starting search. Run the exact name and the name plus company while signed out. Save the date, country or market, device, exact query, and a screenshot. Record organic results, namesakes, and whether a person panel appeared. Repeat on mobile and in your main customer market before generalizing.
2. Check the person’s official bio and profiles. Start with one canonical About URL. Compare the visible role, company, and official links with LinkedIn, YouTube, and the company bio. Check that the existing Person markup reflects visible facts. Use sameAs for verified profiles of the same person. Use event and publisher pages as evidence for specific claims.
3. Verify the site and inspect the important URLs. Check whether the site already exists in Bing Webmaster Tools. If it doesn’t, add it directly or import an existing verified Google Search Console property. Then inspect the homepage and About page for crawl, index, and markup status. Inspect the article URL too if you manage the site that publishes it. Check sitemap processing. If the site already has IndexNow, use it for changed URLs and verify the submission. An accepted submission tells you that Bing received the notification. Check the index separately. URL Inspection, Sitemaps, IndexNow, and site verification.
4. Correct a specific fact when you can prove it. Fix the source you control first. If Bing still presents a concrete error after the source is updated and recrawled, use the Feedback link where available. Include the query, the exact incorrect field, what it should say, and a public URL that backs it up.
5. Measure the outcomes independently. Each week, repeat the same searches and log panel appearance, the facts shown, and any namesake mix-ups. In Webmaster Tools, track URL indexing and Bing search impressions and clicks. If AI Performance is available, log citations to your pages as their own metric. A citation is evidence that a page was used as a source in a supported AI answer. Microsoft’s AI Performance documentation.

For Google, see our complete Google Knowledge Panel guide, the claim and merge walkthrough, and the free book Dylan Haugen and I wrote. The work of checking identity and gathering corroboration carries over. The Google Knowledge Graph scores and claim steps belong to Google.

Bing Webmaster Tools and Google Search Console in practice

On November 13, a Bing Webmaster Tools welcome email for Billy Batt’s site recommended a sitemap, URL submission, a submission API, and user management. We opened the actual properties before acting. Here’s what we learned and the checklist we’ll run on the next site.

Learn, Do, Teach

• Learn. Site verification gets you into the dashboard. A sitemap helps a search engine discover pages. URL Inspection tells you how the engine handled a specific URL. We use the same sequence in both engines. Bing sitemaps · Google crawling and recrawling.
• Do. Billy’s declared sitemap index was absent from both sitemap reports. We submitted it in both. Bing processed the index successfully. Google initially showed “Couldn’t fetch” in the list, then reported “Sitemap index processed successfully” in the detail view. At that check Google still showed zero discovered pages, so the page count is a follow-up. Bing already indexed the homepage and About page. Google had indexed the exit-planning article, while Bing reported “Discovered but not crawled.” The Bing live test said it could be indexed, and Bing accepted one indexing request for the canonical URL. Its index result is still open.
• Teach. Use the exact same canonical URL in both dashboards. Record what the sitemap report says, what the indexed view says, and what the live test says. Keep the request receipt with the date. Check later for an actual index change. See how we practice Learn, Do, Teach.

Content, Checklist, Software

Content. Start with the real page and the evidence on it. Here we checked the homepage, bio, and one substantive article. Billy’s homepage was indexed even though Bing flagged its meta description length. That’s a snippet edit to evaluate separately from indexing.

1. Checklist. Open the verified property. Find the public sitemap in robots.txt and submit it only if it is missing. Verify processing. Inspect the homepage, the About page, and one representative article. Use the indexed and live views to decide whether one URL needs a request. Record property, canonical URL, date, crawl and index status, action, and evidence of the result. Use our Google Search Console checklist for the Google property and measurement setup.
2. Software. Once the checks are repeatable, use read-only index and sitemap reporting to flag exceptions. For ongoing Bing URL changes, check for an existing publisher integration and favor IndexNow when the site can send notifications after publication. Billy’s dashboard showed past Rank Math submissions, so verify the current static publisher before wiring up a second sender. Reserve the direct Bing submission API for a demonstrated need. Bing submission options. Google’s Indexing API is limited to eligible job postings and livestream pages. For ordinary Google pages, use the sitemap and URL Inspection.

Grant dashboard access only when someone needs it to do the work. After publication, check Bing Search Performance for clicks and impressions and AI Performance for citations where available. Record panel appearance from the public search result. The Bing Webmaster Tools setup and troubleshooting checklist covers property verification, sitemaps, URL Inspection, and reporting. Our Digital Plumbing guide explains where this fits in the rest of the setup.

Results log

• November 13, 2026, baseline. Checked two desktop queries. Saw a conflicting employer label and two namesakes in the exact-name results. The Bing Pages application link returned a “Page not found” screen.
• November 13, 2026, source audit. My LinkedIn headline names Local Service Spotlight. The Experience section currently lists both Local Service Spotlight (CEO) and BlitzMetrics (CTO) as present roles. That gives us a source to investigate for the competing labels. The About page’s Person markup lists Local Service Spotlight and includes a sameAs link to Wikidata Q12246156. That item mixes identifiers tied to my profile with biographical statements and Wikipedia links about a television presenter. The homepage markup did not contain that link in this check. Before requesting any Bing correction, I’ll verify the employment dates and remove the mixed Wikidata reference from my own About page through its publishing workflow.
• November 13, 2026, Webmaster Tools. DennisYu.com was present in Bing Webmaster Tools. Its imported sitemap index showed Success, and URL Inspection reported both the homepage and About page indexed. The mixed identity reference on the About page is still a separate repair. Billy’s two-console results and the indexing request are documented above. We also live-tested this article on the BlitzMetrics property and Bing accepted one indexing request. Its index result is pending.

Originally published November 13, 2026.