Claim Google Search Console + Bing Webmaster properties for the Conduction site fleet

[rubenvdlinde]

What

Claim each Conduction property in Google Search Console and Bing Webmaster Tools, generate the verification tokens, and drop them into the matching docusaurus.config.js files. Preset 3.6.0+ already accepts the tokens via a searchConsoleVerification option and emits the right <meta> tags automatically; we just need real tokens.

Why

Without verified properties:

• We can't see Search Console crawl errors, coverage reports, or CWV field data per property.
• We can't submit sitemaps to Bing through the console UI.
• We can't access Bing AI Performance reports (the new dashboard that shows citation counts from Copilot / ChatGPT Search / Perplexity).
• We can't see search-query data (which terms bring traffic to which app).

The SEO baseline campaign shipped everything except this. Tokens are the last gate.

Properties to claim (18 total)

Property	URL	Owner
Marketing site	https://www.conduction.nl	ops
opencatalogi docs	https://opencatalogi.conduction.nl	ops
openregister docs	https://openregister.conduction.nl	ops
openconnector docs	https://openconnector.conduction.nl	ops
docudesk docs	https://docudesk.conduction.nl	ops
mydash docs	https://mydash.conduction.nl	ops
zaakafhandelapp docs	https://zaakafhandelapp.conduction.nl	ops
pipelinq docs	https://pipelinq.conduction.nl	ops
procest docs	https://procest.conduction.nl	ops
decidesk docs	https://decidesk.conduction.nl	ops
softwarecatalog docs	https://softwarecatalog.conduction.nl	ops
scholiq docs	https://scholiq.conduction.nl	ops
nldesign docs	https://nldesign.conduction.nl	ops
shillinq docs	https://shillinq.conduction.nl	ops
openbuilt docs	https://openbuilt.conduction.nl	ops
doriath docs	https://doriath.conduction.nl	ops
app-versions docs	https://app-versions.conduction.nl	ops
larpingapp docs	https://larpingapp.conduction.nl	ops

Per-property steps

1. Google Search Console: https://search.google.com/search-console, "Add property" → URL prefix → paste the property URL → choose HTML tag verification. Copy the value from <meta name="google-site-verification" content="..." />.
2. Bing Webmaster Tools: https://www.bing.com/webmasters, "Add a site" → URL prefix → paste the property URL → choose Option 1 (HTML Meta Tag). Copy the value from <meta name="msvalidate.01" content="..." />.
3. (Optional) DuckDuckGo doesn't have a console; Bing feeds it.
4. (Optional) Yandex Webmaster and Pinterest are supported by the preset too but lower priority.

Where the tokens go

Each consuming site's docusaurus.config.js has a scaffold block. For conduction-website it's at line ~140 and currently commented:

// searchConsoleVerification: {
//   google: '...',
//   bing:   '...',
// },

Uncomment, paste the tokens for that specific property, commit + push. The preset emits the meta tags on next build.

For the 17 fleet docs sites, the same scaffold can be added to each docs/docusaurus.config.js. The preset accepts the option transparently, so the change per site is one block of 4 lines.

Acceptance criteria

• All 18 properties claimed in Google Search Console
• All 18 properties claimed in Bing Webmaster Tools
• Sitemaps submitted to both consoles (Search Console under "Sitemaps", Bing under "Sitemaps")
• searchConsoleVerification block populated in each site's docusaurus.config.js
• After deploy, view-source:<site> shows both meta tags rendered
• Search Console + Bing Webmaster start reporting crawl + coverage data (gives a 1-2 day window)

Related

• Preset 3.6.0 release notes for searchConsoleVerification option
• AI baseline campaign (2026-05-18) that wired the scaffold and validator
• IndexNow setup (separate follow-up) for faster Bing recrawl

[rubenvdlinde]

Domain property set up for conduction.nl via DNS TXT verification. Covers www + all 17 *.conduction.nl subdomains automatically — no per-app preset wiring required.

Already showing 186 klikken in performance, so data collection is live.

Follow-up the user can do in the GSC UI at their own pace (not Claude-shipable):

• Submit each subdomain's sitemap individually: https://www.conduction.nl/sitemap.xml, https://openregister.conduction.nl/sitemap.xml, … (one per fleet site). With a domain property each shows up as a discoverable surface.
• Check 'Pagina-indexering' after a week to confirm Google has crawled the new Per-app docs title format fix (drop "OpenRegister | OpenRegister" duplication) #80 titles and Page-specific meta descriptions on per-app docs sites #81 descriptions.
• Watch Core Web Vitals report after ~28 days for the Core Web Vitals: bundle render-blocking CSS + lazy-load below-fold images #79 lazy-stylesheet impact at p75.