Ops note

Search indexing (public‑safe)

A one‑page operator checklist for Google Search Console and Bing Webmaster Tools. The goal is simple: grow discovery without bloating the homepage, and route search traffic to the verified procurement/audit funnel.

CopyOps

Copy block (paste once)

A short, pasteable block for internal ops notes or vendor tickets. This does not change site policy — it only documents the canonical workflow.

Pasteable block

Submit only the core sitemap: https://meridianverity.com/sitemap-core.xml (ref: /sitemap.xml · /sitemap-archive.xml)
Primary entrypoints: /trust-center/ · /executive/ · /procurement/ · /verify/
FAQ (visible): /explainers/#faq (snippet clarity; rich results not guaranteed)
Receipt Finder: https://meridianverity.com/search/ (⌘K/Ctrl+K)
Ops note: https://meridianverity.com/press/ops/seo/ (noindex; public‑safe)

SitemapsOperational policy

Submit core only

Submit the core sitemap to Search Console / Bing. Treat the archive sitemap as reference only.

Canonical submission

https://meridianverity.com/sitemap-core.xml

Reference (do not submit unless needed):

/sitemap.xml /sitemap-archive.xml

TargetsWhere search should land

High‑signal entrypoints

/executive/ — board/CEO briefing
/trust-center/ — auditors start here
/verify/ — offline verification
/procurement/ — ticket pack / DSSE flow
/explainers/ — FAQ for snippet clarity (rich results not guaranteed)

Google Search ConsoleWeekly

Checklist

Verify the property for https://meridianverity.com/ (domain or URL‑prefix).
Submit sitemap-core.xml only. Keep archive as reference.
Coverage: investigate sudden spikes in Excluded or Crawled — currently not indexed.
Manual actions / Security issues: confirm none.
URL inspection for key entrypoints after releases: /executive/, /trust-center/, /verify/, /procurement/.
Core Web Vitals: watch regressions; prioritize stability over cosmetic churn.

Bing Webmaster ToolsWeekly

Checklist

Verify site ownership (domain or URL‑prefix).
Submit sitemap-core.xml only.
Crawl control: confirm no accidental blocks beyond /archive/ / internal tools.
Indexing: spot check the same key entrypoints as Google.

Search appearanceFAQ

FAQ for snippet clarity (not a promise)

Use FAQ markup only when the Q&A is visible on the page and matches 1:1.
Prioritize human clarity and stable snippets; rich results eligibility varies and may be limited.
Roll out slowly: validate one surface (e.g., /explainers/) before expanding.

This page is an operations note. It is informational, public‑safe, and non‑binding unless incorporated into signed artifacts or contracts.