Pigeon Singapore (baby care, Japanese parent) shares its name with Stovekraft Pigeon India (kitchen appliances, founded 1999). The Indian-appliance overlap on pigeon.com.sg has already fallen to 0.4% of clicks in the last 90 days — the bigger problem is that 87% of all clicks are still branded queries. Hardening the brand entity in Google's Knowledge Graph is what unlocks the non-brand 13%.
Each layer addresses a different surface where Google resolves entities. Homepage signals are necessary but not sufficient — sitewide rules, geographic targeting, and Knowledge Graph authority all reinforce each other.
Six testable, time-boxed outcomes. Measured at T+30, T+60, T+90 post-ship.
Bundled under extended REV-09 scope. Effort 1 day. Ships Mon Jun 1. Each "Before" below was verified by fetching the live homepage. The keystone is enriching the existing Organization schema (Change 4) — every other product/page schema references it.
curl https://pigeon.com.sg/ on 2026-04-29):
Organization schema with @id, name "Pigeon Singapore", 4 social profile sameAs entries, and a working WebSite + SearchAction with the right cross-reference. The fixes below are additions and replacements, not full rewrites.
| Before (verified live) | Home | Celebrate babies the way they are - Pigeon |
| After | Pigeon Singapore | Baby Feeding, Nursing & Care Products |
| Length | 58 chars (current: 51) |
| Contains | brand Pigeon + country Singapore + topical baby, feeding, nursing, care |
| Before (verified live) | The name that spells comfort and convenience, Pigeon is today the market leader in mother and baby care products. Global no.1 choice… |
| After | Official Pigeon Singapore — Japanese-designed baby bottles, teats, nursing essentials and care products. Trusted by Singapore parents for over 30 years. Shop now. |
| Length | 158 chars (current: ~155) |
| Contains | Pigeon Singapore + Japanese-designed + Singapore parents + 30 years (current copy mentions none of these) |
| Before (verified live) | Become A Pigeon Go Green Ambassador |
| After | Pigeon Singapore — Baby Care Products Since 1957 |
| The current H1 is a campaign-promo banner — it tells Google nothing about who Pigeon Singapore is. Replace with a brand-statement H1 that pins the entity to baby care + Japanese parent + 1957 founding. Stovekraft Pigeon was founded 1999, so year-pinning creates entity separation on a dimension Google explicitly tracks. | |
@id "https://pigeon.com.sg/#organization", name "Pigeon Singapore", plus 4 social sameAs entries (Facebook, Instagram, YouTube, TikTok). The job is to enrich — not to add a duplicate block.
Per Moz Brand Entity SEO guidance, organization schema should "go beyond the Google recommended fields" to harden the entity in the Knowledge Graph. The fields missing from the existing schema are:
parentOrganization — links Pigeon SG to Pigeon Corporation JapanfoundingDate + foundingLocation on the parentareaServed — geographic binding to SingaporeknowsAbout — topical binding (baby bottle, nursing, etc.)sameAs array (currently socials only)Final Organization block (existing values preserved, missing fields added):
{ "@context": "https://schema.org", "@type": "Organization", "@id": "https://pigeon.com.sg/#organization", "name": "Pigeon Singapore", "alternateName": "Pigeon SG", "url": "https://pigeon.com.sg", "logo": "https://pigeon.com.sg/logo.png", "parentOrganization": { "@type": "Corporation", "name": "Pigeon Corporation", "url": "https://www.pigeon.com/global/", "foundingDate": "1957-08", "foundingLocation": { "@type": "Place", "name": "Tokyo, Japan" }, "sameAs": [ "https://en.wikipedia.org/wiki/Pigeon_Corporation", "https://www.wikidata.org/wiki/Q11331467" ] }, "areaServed": { "@type": "Country", "name": "Singapore" }, "knowsAbout": [ "baby bottle", "infant feeding", "nursing", "baby care", "newborn", "breastfeeding" ], "sameAs": [ "https://www.facebook.com/PigeonSG", "https://www.instagram.com/pigeonsingapore", "https://sg.linkedin.com/company/pigeon-singapore" ] }
@id — unique identifier; every other schema references this to form a connected entity graphparentOrganization.sameAs → Wikidata Q11331467 — disambiguates to Pigeon Corporation Japan, not StovekraftareaServed: Singapore — geographic bindingknowsAbout — topical binding (zero kitchen-appliance terms)Run through Google Rich Results Test. Must return "Organization detected" with no errors. Verify Wikidata Q11331467 still resolves to Pigeon Corporation Japan before push (Wikidata IDs occasionally get merged/redirected).
SearchAction and publisher.@id correctly referencing #organization. No new code needed — only validate it persists after the Layer 1 ship via Google Rich Results Test.
For reference, the existing block:
{ "@context": "https://schema.org", "@type": "WebSite", "@id": "https://pigeon.com.sg/#website", "url": "https://pigeon.com.sg/", "name": "Pigeon Singapore", "publisher": { "@id": "https://pigeon.com.sg/#organization" }, "potentialAction": { "@type": "SearchAction", "target": { "@type": "EntryPoint", "urlTemplate": "https://pigeon.com.sg/?s={search_term_string}" }, "query-input": "required name=search_term_string" } }
The publisher.@id reference ties the WebSite schema back to the Organization — Google uses this to understand "this website IS this organization."
Add to <head> of homepage and every page via theme template:
<link rel="alternate" hreflang="en-SG" href="https://pigeon.com.sg/" /> <link rel="alternate" hreflang="x-default" href="https://pigeon.com.sg/" />
Add this one-sentence paragraph above the first section on the homepage:
This creates the co-occurrence pattern Google uses for entity resolution:
Body copy is where entity resolution is actually earned, not just declared.
Reference this standard from every SEO ticket before ship. Already maps to 7 existing ClickUp tasks (REV-02, REV-03, REV-04, REV-06, REV-07, REV-08, REV-10).
Every page title MUST contain at least one of: Singapore, baby, nursing, feeding, newborn, infant.
| Homepage | Pigeon — Home |
| Pigeon Singapore | Baby Feeding, Nursing & Care Products | |
| Collection | SofTouch Bottles | Pigeon |
| SofTouch Baby Bottles Singapore | Pigeon | |
| Product | Smart Bottle Warmer | Pigeon |
| Pigeon Smart Bottle Warmer Singapore | For Baby Milk | |
| Blog | 5 Tips for New Parents |
| 5 Feeding Tips for New Parents in Singapore | Pigeon | |
| Warranty | Warranty Registration | Pigeon |
| Baby Product Warranty Registration | Pigeon Singapore |
Every meta description MUST mention "Pigeon Singapore" (not just "Pigeon") within the first 120 characters.
Every long-form article MUST include this sentence (or variant) in the first 200 words:
Variants accepted as long as they preserve the four co-occurrence signals: Pigeon + Japan + 1957 + baby.
Every Product schema on shop.pigeon.com.sg MUST reference the homepage Organization via @id:
{ "@type": "Product", "brand": { "@id": "https://pigeon.com.sg/#organization" } }
Without @id, Google sees N disconnected "Pigeon" brand mentions and still can't resolve which Pigeon you are.
Any Organization reference anywhere on the site MUST use:
"@id": "https://pigeon.com.sg/#organization"
Never inline a fresh Organization object. The homepage is the canonical entity. Everything else references it.
Do not use words that overlap with the Indian appliance category anywhere on the site:
| Task | What the standard changes |
|---|---|
| REV-02 | Bottlefeeding hub refresh — Rules 1, 2, 3 apply |
| REV-03 | BYOB content cluster (3 posts) — Rules 1, 2, 3 each post |
| REV-04 | 6 collection meta + intros — Rules 1, 2 each |
| REV-06 | Top 5 product meta + schema — Rules 1, 2, 4, 5 |
| REV-07 | Next 15 products — same as REV-06 |
| REV-08 | Baby Fair July content (4 posts) — Rules 1, 2, 3 each |
| REV-10 | Publish 4 drafted blog articles — Rules 1, 2 audited |
Goes early because it unblocks clean SG-only measurement for all downstream entity work. Effort 0.5 day. Owner: SEO lead.
Explicitly set Singapore for both pigeon.com.sg and shop.pigeon.com.sg. The .sg ccTLD auto-targets but we confirm and log.
en-SG on every page · WordPress: Yoast SEO. Shopify: theme template emits in <head>.
x-default points to the primary .sg homepage.
Not a crawl block — a measurement fix. Weekly success reports filter India out so the team tracks SG performance, not noise.
curl -s https://pigeon.com.sg/ | grep hreflang returns 2+ linesOwner: Link-building + SEO leads. Effort 5+ days spread across Q3. First milestone Jul 15. Blocked by REV-09 — Organization schema must be live before this work has anything to attach to.
Q11331467 (confirmed via Wikidata API; Q11336692 is a different entity — "ヘンテコ忍者")Domains whose links reinforce the SG + baby-care entity context:
Via Kalicube Knowledge Graph API Explorer. Tracks whether Pigeon Singapore is resolving as its own entity, in what context, and whether confusion with Stovekraft is decreasing month over month.
The plan stages itself: REV-19 unblocks measurement first, REV-09 ships the homepage signals, REV-20 builds long-range Knowledge Graph authority once the homepage is live.
| Week | Action | Owner | Depends on |
|---|---|---|---|
| Apr 21–27 | Approve plan: REV-09 extension + REV-19 + REV-20 + standard reference on 7 tasks | Strategy lead | — |
| Apr 27 – May 1 | REV-19 · GSC + hreflang + India exclusion | SEO lead | GSC access + WP admin |
| May 4 – 8 | Standard applied to REV-04 (collection meta) + REV-06 (top 5 products) as they ship | SEO lead + editor | Shopify access (secured), standard doc written |
| May 11 – 29 | Standard applied to REV-02, REV-03, REV-07, REV-08, REV-10 as each ships | Editor + exec | Same |
| Mon Jun 1 | REV-09 extended ships · all 7 homepage changes | SEO lead + dev | WP admin access |
| Jul 15+ | REV-20 · Knowledge Graph milestones begin (Wikidata verified, GBP optimized, first 2 SG backlinks) | Link-building + SEO leads | REV-09 live |
| Jul – Sep | Ongoing KG work · 5 SG backlinks total · monthly KG health check | Link-building lead | — |
| Sep / Oct | T+90 measurement against success criteria | Team | All layers shipped |
Google Knowledge Graph changes take 30–90 days to propagate. Don't expect immediate SERP changes after ship.
We can reduce our share of their traffic signal but not eliminate it. Both brands are real businesses with real audiences.
Our disambiguation helps us, doesn't hurt them. They aren't actively contaminating us — Google is.
By editors who see them as promotional. Edits must be neutrally written, sourced, and follow Wikidata style guidelines. Use a real account, not a throwaway.