iMEDIA AUDIENCES — TECHNICAL SEO REVIEW AND DEPLOYMENT STATUS

STATUS: PREPARED IN THE BNI PROJECT; NOT PUBLISHED OR PRODUCTION-VERIFIED

This report separates current source changes from the existing public deployment. Do not treat the source changes or the TypeScript check as proof of a successful launch.

PROJECT SCOPE
The current project is the BNI introduction site, with canonical domain https://bni.imediaaudiences.com. It is not the separate Vibe marketing project or the WordPress website. No marketing design, navigation, visible introduction/service copy, branding, contact actions, or analytics settings were changed.

PUBLIC BASELINE RETRIEVED DURING THIS REVIEW
- https://bni.imediaaudiences.com/ — readable public introduction and service content, chapter links, Josh's profile photo, and existing links to Vibe were retrieved. The fetched title was "Meet Josh Iverson — iMedia Audiences", not the more specific title currently configured in source.
- https://bni.imediaaudiences.com/tracy — Tracy's personalized introduction and service content were retrieved. The fetched title was "Tracy introduces Josh Iverson — iMedia Audiences".
- https://bni.imediaaudiences.com/sitemap.xml — retrievable content listed only / and /chapter. This does NOT demonstrate that the new automatic member-page coverage is deployed.
- https://bni.imediaaudiences.com/robots.txt — retrievable text allows public crawling, references the BNI sitemap, and includes existing crawler/content-signal permissions. Those permissions are retained in the prepared robots file; no security exclusions were present in either reviewed version.
- https://vibe.imediaaudiences.com/ — readable website plans, comparisons, FAQs, and examples were retrieved. This separate project was not edited.
- https://vibe.imediaaudiences.com/sitemap.xml — retrievable content listed 13 URLs, matching the existing downloadable reference. Individual inner routes were not audited in this review.
- https://imediaaudiences.com/ — readable WordPress agency content was retrieved, with title "HOME - iMedia Audiences". This separate site was not edited.
- https://imediaaudiences.com/robots.txt — references /wp-sitemap.xml and includes the Yoast crawl block with an empty Disallow directive.
- https://imediaaudiences.com/wp-sitemap.xml — retrieved index content lists child sitemaps for posts, pages, categories, tags, and users.
These content retrievals confirm accessible content only. They do not constitute a raw HTTP-status, redirect-chain, response-header, complete head-tag, canonical, schema-validation, or production performance audit. Previously reported HTTP statuses, MIME types, Yoast schema IDs, and /sitemap_index.xml failure are not re-certified by this review.

PREPARED CHANGES
1. Replace the manually maintained BNI XML with a /sitemap.xml server endpoint. It discovers registered public page routes and expands the member route from the same roster used by the directory. The expected current total is 28 URLs, not a permanently hardcoded count.
2. Before including a candidate, load it through the server router and require its successful 200 render result, explicit index metadata, and exactly one matching self-canonical. Exclude redirect, error, not-found, noindex, SSR-disabled, auth/private, and guarded route branches. Unknown member slugs are not generated. Deduplicate URLs. Do not include unrelated domains or preview-host addresses.
3. Do not fabricate lastmod dates. None are emitted because no trustworthy per-page content modification dates are recorded.
4. Generate from the deployed route/roster definitions on each sitemap request; allow shared caching for at most five minutes. New public static routes with appropriate page metadata are discovered. Future dynamic page types must provide their concrete published paths with staticData.sitemapPaths. Explicit exclusions use staticData.sitemap = false.
5. Preserve page-specific titles, descriptions, self-canonicals, Open Graph and Twitter information. Source review found one primary H1 per real page and descriptive image alternatives. The installed head manager deduplicates titles and named/property metadata using the deepest route, so the root noindex fallback does not duplicate or override valid page index metadata. Keep the fallback for missing routes.
6. Add factual Service entities for the three visible offerings and primary-image information to the existing Organization, Person, WebSite, WebPage/CollectionPage, and directory ItemList graph. No fabricated reviews, ratings, addresses, FAQ markup, or invented breadcrumb hierarchy.
7. Retain useful crawlable ecosystem links and preserve each site's own canonical identity. The main agency Organization ID remains https://imediaaudiences.com/#organization.

REQUIRED BEFORE PRODUCTION SIGN-OFF
1. The owner must publish this project to bni.imediaaudiences.com. Publishing is not available from this editing session; no publish action occurred here.
2. Confirm /sitemap.xml reaches the automatic server endpoint rather than an old generated/static file or HTML shell. It must return 200 with an XML content type, exactly the current public canonical pages, and no invented dates. Compare all member paths against the directory. Allow at most five minutes for shared caching, or purge the CDN during launch.
3. Confirm every sitemap URL returns HTTP 200 WITHOUT following a redirect. Check the exact canonical, final host, index directive, and absence of a conflicting X-Robots-Tag header. Application router checks cannot detect CDN-level redirects, headers, DNS errors, or hosting outages.
4. Check /robots.txt is public and references the BNI sitemap without blocking public scripts, styles, images, or landing pages. Preserve any host-level security exclusions.
5. Inspect raw server HTML for /, /chapter, /tracy, /andre, and the remaining public member pages: exactly one meaningful H1, title, description, canonical, and each social property; the correct BNI canonical; visible content before JavaScript; valid factual JSON-LD. Verify unknown and nested nonexistent paths return actual HTTP 404 plus noindex, not a 200 error screen.
6. Verify HTTP/HTTPS, www/non-www, slash, and tracking variants resolve/canonicalize consistently without chains or loops. Preserve attribution parameters used by analytics. Keep preview/staging hosts out of search with hosting controls without applying production noindex headers.
7. Validate structured data with Schema Markup Validator and Google's Rich Results Test. Review mobile usability and Core Web Vitals after deployment. No performance measurement or third-party rich-result validation was run here.
8. Verify Search Console ownership (prefer a DNS-verified imediaaudiences.com Domain property covering all subdomains), then submit each site's OWN live sitemap separately. For URL-prefix properties use the matching host. Verify/import sites into Bing Webmaster Tools and submit there too. The owner or team must perform these authenticated actions.
9. Use URL Inspection on the homepages and representative service/member pages; later check Google's chosen canonicals and indexing decisions. Similar member introductions may be grouped or not indexed. Do not promise indexing, rankings, traffic, rich results, or AI citations.

OTHER-SITE HANDOFFS
- Vibe website: apply /seo/vibe-website-prompt.txt in the separate project, verify its real routes, then publish and test that site independently.
- WordPress: send /seo/wordpress-team-handoff.txt to the WordPress team. Keep an automatic, verified active index and consolidate schema through its existing SEO plugin. The brief's historical implementation details must be rechecked before acting.
- Do not put all three hosts in one urlset or deploy the BNI site to both subdomains. Do not canonicalize unique subdomain pages to the agency homepage.

OWNER ACTIONS STILL OUTSTANDING
Publishing, production status/header/canonical verification, exact XML endpoint precedence, full sitemap-URL audit, DNS and redirects, Search Console/Bing access and submissions, third-party schema/performance tests, and implementation in the other two projects. This review is not a claim that any of those steps are complete.