# BEMRIX — technical SEO launch guide

Status: local, pre-launch website. No domain has been purchased or configured. No public indexing, traffic, leads or rankings are claimed.

## Configuration already implemented

- Each marketing page has its own title, description and social title. A shared 1200 × 630 social image is ready; project-specific images remain available.
- NEXT_PUBLIC_SITE_URL is the single public-origin setting. It accepts a confirmed HTTPS origin without a path, query, credentials or port. Blank is intentional before launch.
- With no origin, pages emit noindex, follow; robots.txt disallows crawling; sitemap.xml contains no URLs. Canonical links, absolute social images and organization/breadcrumb structured data are withheld rather than filled with an invented domain.
- After setting the real origin and rebuilding, marketing routes receive self-referencing canonical URLs, social images resolve to that origin, and the sitemap is populated from the service and project catalog. Query-string enquiry variations canonicalize to the clean contact path.
- Organization and WebSite JSON-LD use the visible company name and description only. Project and service pages also receive breadcrumb data. No address, ratings, reviews or social identities are invented.
- The RelayDesk demo remains noindex. Production prompt resources have an X-Robots-Tag: noindex, follow header even after launch. These controls are indexing directives, not access control for private content.
- Responsive raster previews use Next.js image optimization and size hints. Full-resolution download links and vector artwork are retained.
- Case-study CSS loads on case-study routes; shared card styles remain available to home/work pages. Tested contrast and heading issues were corrected.

## At launch

1. Purchase and connect the actual domain and choose its single preferred HTTPS hostname. Set NEXT_PUBLIC_SITE_URL to that origin in the hosting environment, then rebuild and deploy. A runtime-only environment change is insufficient for this static metadata.
2. Keep separate preview deployments unset. If a preview inherits the public origin, it may inherit public indexing behavior; use appropriate host-level preview protection as well.
3. Verify HTTPS and redirects from alternate hostnames. Hosting redirects and TLS have not been configured locally.
4. Check home, a service, a project and contact?service=website-development in rendered HTML. Confirm self-referencing canonical URLs, unique titles, actual social images and the intended robots directives.
5. Open /robots.txt and /sitemap.xml on the live domain. The sitemap should contain marketing pages, not demos, prompt books or localhost URLs. Missing pages must return HTTP 404.
6. Validate structured data against the final public URLs. Keep facts aligned with visible content; structured data does not guarantee a search feature or ranking.
7. Verify ownership in Google Search Console and submit the live sitemap. No Search Console property has been created or submitted during this work.
8. Run a fresh performance test on hosting. Local loopback measurements exclude real DNS, TLS, CDN and regional latency. Collect real visitor data when available before making Core Web Vitals claims.
9. Review real enquiry delivery before promoting the site. The current contact experience prepares an enquiry; configuring a deliverable business contact channel is a separate launch requirement.

## Measurement limits

The accompanying report uses repeated local Lighthouse mobile lab measurements. It is not a public PageSpeed Insights report, search ranking result, or real-user field measurement. No ad spend, campaign performance or client revenue result is inferred. Indexing is intentionally disabled until the confirmed domain is configured; a lower Lighthouse SEO score caused by noindex in the preview is expected and should not be “fixed” by exposing a staging site.

## Primary guidance

- Google Search Central, canonical URLs: https://developers.google.com/search/docs/crawling-indexing/consolidate-duplicate-urls
- Google Search Central, sitemap creation: https://developers.google.com/search/docs/crawling-indexing/sitemaps/build-sitemap
- Google Search Central, robots metadata: https://developers.google.com/search/docs/crawling-indexing/robots-meta-tag
- web.dev, lab versus field measurements: https://web.dev/articles/lab-and-field-data-differences
- Lighthouse, test variability: https://github.com/GoogleChrome/lighthouse/blob/main/docs/variability.md