BNI PROJECT — PASTE INTO THE VIBE PROJECT FOR bni.imediaaudiences.com

Goal: publish and maintain the SEO setup in this BNI referral project. Do not recreate the website or change its design, member introductions, pricing, booking, phone numbers, signup links, or existing helpful Vibe links.

ALREADY IMPLEMENTED IN THIS PROJECT
- Automatic /sitemap.xml server route: discovers the registered public routes and expands the member route directly from src/lib/members.ts. Current expected coverage is 28 canonical URLs — /, /chapter, and 26 members. No hand-maintained public/sitemap.xml remains.
- public/robots.txt: allows crawling, references https://bni.imediaaudiences.com/sitemap.xml, and retains the currently published crawler/content-signal permissions without changing AI data-use policy.
- src/lib/seo.ts, used by the home, chapter, and member routes: one self-referencing canonical per page, unique titles and descriptions including member business names, Open Graph and Twitter sharing metadata, and head-managed JSON-LD.
- JSON-LD: Organization, Josh Iverson Person, WebSite, WebPage/CollectionPage, a factual primary image, the three visible Service offerings on introduction pages, and the directory's ItemList. The shared agency ID is https://imediaaudiences.com/#organization. No invented ratings, prices, addresses, FAQs, or breadcrumb hierarchy.
- Unknown members throw a router notFound response and receive noindex metadata. Valid pages explicitly opt into index, follow; the root fallback is noindex, follow.
- public/llms.txt: optional AI-readable description of this site and the two related iMedia sites.
- Footer links to the XML sitemap and SEO handoff.

PUBLISH / MAINTAIN
1. Inspect the current project before editing; do not duplicate these features.
2. Publish THIS project only to https://bni.imediaaudiences.com. Do not publish the BNI project to the Vibe marketing domain: its canonical addresses and member links deliberately target BNI.
3. Confirm the live /sitemap.xml is served by src/routes/sitemap[.]xml.ts and returns XML, not the old two-entry generated file or an HTML shell. The route now owns this URL. public/robots.txt and public/llms.txt remain owned static files. The publisher/CDN must not shadow the sitemap server route with an older generated sitemap; if it does, the deployment team must correct routing precedence before sign-off.
4. The endpoint reads the registered routes on each request; dynamic member paths come from the same roster that renders /chapter. It evaluates each candidate with the server router, includes only successful 200 render results with explicit index metadata and exactly one matching BNI canonical, and excludes redirect/not-found/error results, noindex metadata or route headers, routes without page metadata, SSR-disabled routes, auth/private route branches, and routes with beforeLoad guards. New public static routes with proper head metadata are discovered automatically. For other future dynamic public routes, provide concrete published paths with staticData.sitemapPaths. To explicitly exclude a route or branch set staticData.sitemap to false. Future guarded-but-public routes need an intentional review rather than automatic inclusion. Public cache freshness is at most five minutes. This is application-level validation, not proof that CDN redirects, response headers, or deployment availability are correct; test those after publishing.
5. Canonicals: root ends in /; member and chapter paths have no trailing slash. Configure permanent redirects for alternate host/protocol/slash forms at the hosting layer if available. Preserve query parameters used for attribution while canonicalizing to clean URLs. Do not create redirect loops.
6. Verify server HTML for /, /chapter, /tracy, and /andre: correct title/description, exactly one canonical on the BNI domain, index/follow, visible content, and valid JSON-LD. Verify /not-a-real-member returns HTTP 404 with noindex. Do not treat a client-rendered error screen alone as proof of 404 status.
7. Existing profile photos are used for social cards. Test the live previews; a custom landscape share image can be added later, but do not invent an asset or claim an uncreated image exists.
8. Member pages share service content. Do not manufacture testimonials, add keyword-stuffed doorway text, or promise all 26 will index. With each member's approval, genuinely useful original referral context may improve differentiation. Search engines may still group similar introductions.
9. Keep contextual links to https://vibe.imediaaudiences.com/ for website plans and https://imediaaudiences.com/ for the agency. No cross-domain canonicals merely to transfer rankings.
10. Verify an imediaaudiences.com Domain property in Search Console via DNS with the domain owner, then submit the three distinct sitemap URLs listed in the handoff. If using URL-prefix properties, verify and submit each under its matching HTTPS host. Import/verify the same sites in Bing Webmaster Tools.

POST-PUBLISH CHECKLIST FOR THE OWNER
- Open https://bni.imediaaudiences.com/sitemap.xml and robots.txt; confirm XML vs HTML and no accidental noindex headers on public landing pages.
- Google URL Inspection: /, /chapter, /tracy, /andre. Review Google's chosen canonical after crawling; indexing is not guaranteed.
- Run Rich Results Test and Schema Markup Validator. Not every valid schema type earns a rich result.
- Test mobile rendering and Core Web Vitals; preserve image dimensions and lazy loading below the fold.
- Keep staging/preview hosts out of search using the host's access controls or X-Robots-Tag: noindex. Do not put a noindex header on the production domain.
- Do not add fake lastmod dates. The installed sitemap omits them; only add truthful page-change dates.

LIMITS
Read /seo/verification-report.txt for the baseline retrieved in this review and the unverified production checks. The public BNI sitemap still listed only two URLs when retrieved; the prepared endpoint and its expected 28-URL coverage have not been published here.
Publishing, DNS verification, redirects, Search Console/Bing submissions, and live HTTP validation require the owner or deployment team. This handoff does not perform them. Technical SEO, related-site links, schema, and llms.txt do not guarantee rankings, indexing, traffic, or AI citations.