How a Palm Beach County contractor and an AI agent rebuilt a digital presence — from a noindex tag to a self-improving website.
In mid-2025, Randolph Scott Bell — a Florida state-certified general contractor, roofer, licensed community association manager, real estate sales associate, LEED AP, and farmer — had a business empire spanning seven divisions and a web presence that was actively working against him.
His previous website carried a noindex tag that told Google to ignore it entirely. His brand identity was fragmented across three different business names. His decades of licenses, projects, and credentials were invisible online.
Twelve months later, randolphscottbell.com is a 59-page hub-and-spoke website that designs, writes, optimizes, and submits itself to Google — autonomously, every day — through a fleet of seven AI-powered GitHub Actions workflows. Google's index went from effectively one page in early July 2026 to 32 indexed pages five weeks later. The site earned a cinematic, award-candidate homepage, structured data across every division, a local citation network spanning nine platforms, and a self-correcting SEO feedback loop that pings Google automatically every time any page changes.
This case study documents what was taken over, how the methodology works, what it took to teach a self-described novice to direct AI development ("vibe coding"), the hurdles that nearly derailed the project, and the roadmap for staying ahead. It is written by the AI that did the work, with the owner's numbers and the receipts to back it.
Bell Engineering and Construction Corporation, doing business as BeacCorp Property Management, has operated in Palm Beach County since 2009. By 2025 the enterprise spanned construction, roofing, property and HOA management, land clearing, an agritourism farm in Loxahatchee, a food truck built from a 1979 Blue Bird bus, real estate, and consulting.
The digital footprint told none of that story. The legacy WordPress site carried a noindex directive — a single line of code instructing search engines to pretend the business did not exist. The brand was split across "Bell Engineering," "BeacCorp," and "BEACCORP PM," fracturing whatever authority Google might have assigned. There was no structured data, no coherent sitemap, and no connection between the divisions.
The first strategic decision was consolidation: one name, one domain, one architecture. Everything would live under the owner's personal brand at randolphscottbell.com — "Build. Invest. Elevate." — with each division as a spoke off a central hub. The old standalone construction site was 301 redirected into the hub, passing its history forward instead of abandoning it. Name, address, and phone data was standardized to a single canonical form across the web, anchored to the founding year 2009.
One name, one domain, one architecture — each division a spoke off a central hub.
The ranking method rests on four pillars, applied in strict order.
Clean URL architecture with canonical trailing slashes, LocalBusiness and FAQPage JSON-LD structured data, a disciplined XML sitemap with accurate per-URL lastmod dates (the field Google actually reads for re-crawl decisions — most sites ship changefreq and priority, which Google ignores), Open Graph and Twitter share cards, and Google Analytics 4 wired sitewide.
And the guardrails matter as much as the velocity. The owner initially wanted a 1,000-page blitz. The AI counseled against it: Google's scaled-content abuse policies poison a domain's future, and new domains cannot get mass pages indexed anyway. The negotiated cadence — roughly 90 substantive pages per month, throttled automatically if Search Console shows pages stuck in "Discovered — currently not indexed" — keeps growth inside Google's trust envelope.
Every page is a real page: service pages, buyer guides, seasonal menus, city-specific landing pages modeled on what actually ranks in each niche. Competitive analysis showed the winning local pattern is one landing page per micro-location — Loxahatchee, Loxahatchee Groves, The Acreage as separate pages, not one county page — and the site builds toward that pattern division by division.
Google Business Profiles for the flagship businesses, then a tiered citation campaign — Bing Places, Houzz, Yelp, Nextdoor, Thumbtack, Roaming Hunger and StreetFoodFinder for the food truck — each profile fully built out with licenses, verified credentials, photography from real projects, and imported reviews. Tier two targets trade associations and chambers; tier three, booking platforms and press.
A daily SEO watchdog audits the live site, a weekly analytics scorecard reads GA4, a weekly indexing watch reads Search Console trends, and — the piece that makes it self-correcting — every content push automatically resubmits the sitemap to Google through the Search Console API, so the gap between publishing and Google knowing is minutes, not weeks.
The site is maintained by seven GitHub Actions workflows powered by Claude through anthropics/claude-code-action.
lastmod on all 56 URLs, added share-card metadata, built the homepage FAQ with FAQPage schema, and added contextual deep links, all in a single supervised run.AI writes the pages; the facts come from a human-verified single source of truth.
The owner writes no code. Twelve months ago he deployed his first website by dragging a folder into Netlify — and learned, the hard way, that you drag the inner folder containing index.html, not the wrapper. Today he directs a seven-workflow autonomous development operation.
That transition is the real story of this project, and it rests on a division of labor: the human sets vision, taste, and priorities; the AI translates them into architecture, code, and process; and every change ships with an explanation the owner can read in plain English.
The teaching method was incident-driven. When a browser editing glitch inserted two stray em dashes into line one of a workflow file and silently took the Daily SEO Watchdog offline — GitHub Actions rejected the entire file over two invisible characters — the repair became a lesson in why YAML fails, how to read an Actions error, and why verification after every edit is non-negotiable. When the owner's Google Cloud organization turned out to prohibit downloadable service-account keys, the workaround — keyless Workload Identity Federation, scoped so only this exact repository can impersonate the service account — became a lesson in why the more secure path was also the more elegant one. When Publer rejected an entire month of social posts over a date format, and Google Business Profile rejected 23 posts as near-duplicates, the fixes were written into the automation prompts themselves so the same mistake became structurally impossible.
That last point is the compounding trick: every failure gets encoded back into the system as a rule. The owner calls it "refining the box." The box gets refined continuously.
Every failure gets encoded back into the system as a rule. The owner calls it "refining the box."
The honest list, because a case study without failures is an advertisement.
New-domain indexing lag was the most stubborn: pages sat in "Discovered — currently not indexed" for weeks while Google decided whether to trust the domain — the cure was patience, lastmod discipline, and automatic resubmission, not more pages.
The scaled-content temptation required the AI to talk its own operator out of a 1,000-page order — the most valuable "no" of the project.
A pre-2026 vendor legacy left the owner, in his words, "set behind a year" by the old noindex site.
Naming collisions meant an unrelated petting-zoo farm with a nearly identical name outranked the real Bell Farm on branded searches, demanding aggressive entity disambiguation through structured data and citations.
Platform quirks — duplicate-post filters, CSV date formats, one-minute scheduling collisions — each cost a working session before being written into the rules.
And model economics turned out to be a real operating decision: the bots were pinned to a cheaper model to control API spend, the output quality was measured against the premium model, and the fleet was moved back to the premium model where quality mattered — a cost-quality dial most businesses running AI have not yet learned to turn deliberately.
Google's index grew from roughly one page in early July 2026 to 32 indexed pages by August 10, with 59 URLs now in the sitemap and the remainder moving through Google's pipeline. Sitemap reads by Google now happen same-minute on resubmission. The Bell Farm Google Business Profile holds a 4.7-star rating with 260 profile views and 61 customer interactions in the last month. Tier one citations are live on nine platforms, with contractor licenses independently verified on Thumbtack.
The homepage shipped a cinematic title-card hero with a scroll-driven manifesto, and 24 design-proposal pull requests have been shipped and merged. Two portfolio projects are published on Houzz, and the local press and association pipeline is staged. The site publishes and deepens content daily without human intervention — the natural spring soak page recently went from 1,035 to 3,328 words in one autonomous watchdog run.
These are early-innings numbers, stated plainly: a domain this young competing in local Florida contracting will take months more to own its money keywords. The point of the case study is not that the destination has been reached — it is that the machine that gets there is built, running, and improving itself.
The plan for continued leadership follows the same best-practices discipline.
Content: complete the thin-division buildout — the land clearing division's first city page shipped this week — and extend the proven city-page pattern across every division.
Authority: move the citation campaign into tier two — builder associations, agritourism associations, the chamber — then the reviews engine: every completed job generates a review request, Google first, Houzz and Yelp alternating, never bulk, never incentivized.
Design: continue benchmarking the homepage against current award winners and submit to the 2026 galleries — the application this case study accompanies.
Automation: progressively move every recurring decision into the workflows — the standing instruction is that the site should require the owner's taste, not the owner's time.
Measurement: weekly indexing verdicts throttle content velocity up or down against live Search Console data, keeping growth permanently inside Google's trust envelope.
The site should require the owner's taste, not the owner's time.
The thesis of this project is simple. AI did not replace the contractor. It gave a one-man, seven-division business the digital operations department that only national franchises used to afford — and it gets a little better at the job every single day.