# Construction Sales Guide — source ledger and release gates ## Verified source observations **AGC Business Development Forum** — https://www.agc.org/connect/agc-groups/business-development-forum The public page currently describes contractor BD topics including go/no-go decisions, proposal/pursuit management, relationships with developers and prime contractors, and business-development pipeline work. It links a public LinkedIn community and says some education requires login. This does not verify access to private content, membership or posting permission, or AGC endorsement. It does not validate a workflow, bid decision, or outcome. **Markup & Profit, Connect With Us** — https://www.markupandprofit.com/connect-with-us/ The owner page says its private Facebook group is for owners of construction-related businesses and discusses sales, contracts, and estimating. This does not verify private-group contents, enrollment or posting permission, endorsement, or any reader's eligibility. **AutonomousGTM commercial construction** — https://autonomousgtm.ai/commercial-construction This is a service-promotion destination, not an independent editorial source; it supports no editorial or performance claim. ## Editorial limits - Audience: commercial subcontractor owners and BD leads. This is subcontractor account selection, pre-bid relationship work, and estimating-capacity guidance—not equal sales coverage for general contractors. - Workflow and action recommendations are editorial, never sourced market facts. - All examples are constructed and illustrative; they do not describe actual firms, projects, conversations, results, studies, or statistics. - The sources provide no market size, invitation probability, bid-success rate, universal qualification requirement, or estimating benchmark. Verify project, GC process, contract, schedule, legal, and capacity facts directly. - No independent review, testimonials, editorial credentials, readership, studies, or customer results are claimed. - Owned and published by Sovereign Compute LLC, the company behind AutonomousGTM. ## SEO and AI-discovery foundations - Production HTML is generated as six separate static routes. The production build writes canonical HTTPS URLs on the confirmed apex `https://constructionsalesguide.com`, unique titles and descriptions, matching Open Graph and Twitter titles/descriptions, `og:url`, and a root sitemap listing only those six canonical routes. - The production root `robots.txt` allows ordinary search crawling and OAI-SearchBot retrieval, while disallowing GPTBot and Google-Extended per the selected search/retrieval-only policy. The Vite preview keeps `noindex,nofollow` route HTML, sends a dev-only `X-Robots-Tag: noindex, nofollow`, and serves a disallow-all robots file; production SEO metadata is added only to the built output. - Structured data is route-specific and limited to visible facts: Organization and WebSite on the home route; Article and BreadcrumbList on the guides; WebApplication and BreadcrumbList on the editable worksheet; AboutPage and BreadcrumbList on About. No fabricated author, publication date, rating, offer, testimonial, or result is added. - Google Search Central says AI Overviews and AI Mode use ordinary Search eligibility, with no additional technical requirements; it recommends crawlable text, internal links, and structured data that matches visible content: https://developers.google.com/search/docs/appearance/ai-features - Bing Webmaster guidance describes shared crawl/index foundations for Search, Copilot, and grounding; it recommends canonical sitemap URLs and crawlable internal links: https://www.bing.com/webmasters/help/webmaster-guidelines-30fba23a?library=true - OpenAI documents OAI-SearchBot as a ChatGPT Search crawler separate from GPTBot model-training crawling: https://platform.openai.com/docs/gptbot - Google documents Google-Extended as a separate control that does not affect inclusion or ranking in Google Search: https://developers.google.com/crawling/docs/crawlers-fetchers/google-common-crawlers - No special AI markup, invented FAQ block, or unsupported AI-discovery file is added. Existing inline source citations, explicit ownership, clear guide hierarchy, answer-first summaries, and internal links are preserved. These foundations support eligibility and clarity but do not promise rankings, traffic, or AI citations. ## Deployment and QA status - The production package build sets Vite's base to `/` and post-processes the six route files in `dist/public`; public page links and assets use root-relative URLs on the custom domain. The Replit preview remains mounted at `/construction-sales-guide/` and serves the original noindex source pages. - Replit's static output directory is `artifacts/construction-sales-guide/dist/public`. Existing route files under that directory are served directly; the configured catch-all rewrite to `/index.html` is only a fallback because static files shadow matching rewrites. See https://docs.replit.com/features/deployment-customization/static-deployments-advanced. - The confirmed canonical domain is `https://constructionsalesguide.com`; domain ownership is not evidence that it has been connected to a deployment. No account settings have been changed. - This build remains unpublished pending independent route QA. This ledger records configured build output, not live production behavior or completed independent QA.