How a Palm Beach County contractor and an AI agent rebuilt a digital presence — from a noindex tag to a self-improving website.
Randolph Scott Bell, recorded August 11, 2026: what the experiment is, why he is running it on his own seven businesses, and what he has learned directing an AI agent without writing a line of code. Twelve minutes.
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 eight 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.The fleet is split into seven named workflows rather than one generalist bot because each carries a single, non-overlapping mandate, and that separation is deliberate. Content Builder writes from the backlog; Thin-Division Builder is hard-scoped away from the construction section entirely; the Daily SEO Watchdog audits and repairs rather than authoring new sections from scratch; Weekly Design Proposal only touches the visual layer; Weekly Analytics Scorecard only reads GA4; Ship OG Image only renders share cards; Resubmit Sitemap only pings Google. A single workflow empowered to both build content and audit it would eventually grade its own homework — there would be no independent check on whether a page it wrote actually meets the site's own standards. Splitting authorship from audit means the watchdog can catch what a content run missed without any incentive, coded or otherwise, to look away.
The same logic governs design. Weekly Design Proposal benchmarks the homepage against current Awwwards, CSSDA, and siteinspire winners on its own schedule, but none of the other six workflows touch layout, CSS, or navigation — which is exactly why 24 design pull requests have shipped and merged as their own numbered track rather than folding into ordinary content commits, and why a division page can pick up 400 new words of copy on the same day a design proposal opens without the two stepping on each other's diff. Cadence follows the same risk logic: Content Builder runs twice daily and the Watchdog runs daily because search visibility compounds with every day a gap sits open, while design changes are held to a weekly rhythm because taste needs time to be judged against a moving field of award winners rather than iterated on impulse.
Resubmit Sitemap breaks that weekly-versus-daily pattern on purpose — it fires on every push that touches the sitemap, because once a page is actually live there is no reason to make Google wait to hear about it. What holds the seven together despite running on different clocks and never sharing a merge review isn't a shared brain; it's the two standing rules every one of them reads before acting — build to the current state of the art, and never write a fact that isn't already sitting in the owner's verified file. Scope keeps the bots from colliding with each other; the two rules keep them from contradicting the facts.
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 has produced its first attributable inbound business. Seven leads is a small number. It is also the first time in this project that the number is not zero — and it arrived in exactly the order Search Console predicted.
The headline finding. The owner reports two phone calls from people wanting to buy chickens from The Bell Farm, three calls to hold events at the farm — a newborn photo session, a charity event for an athletic group in Loxahatchee, and a wedding — and one call about land clearing. A construction lead also arrived through the site's own form on August 29, and exposed a notification gap: no email reached the owner, and the lead was caught only by reading the hosting platform's form counts directly. Five of the seven leads are the farm, the division Google already trusted this domain for; the first non-farm lead is land clearing, the division that received its first city landing page in August.
Scale since the August write-up. The sitemap has grown from 59 URLs on August 10 to 146 on September 4, every page written and published by the agents. On August 16 the daily run was consolidated into one orchestrated workflow that ends in exactly one commit and one deploy per day — 140 deploys had consumed 2,100 of a 1,000-credit monthly hosting allowance in the prior period, so this was a cost fix as much as an engineering one. The rule held for scheduled runs and was broken twice by manual sessions, which is itself a finding: the cost discipline lives in the automation, not in the humans.
Mobile performance is not decaying — it oscillates. Lighthouse mobile performance on the homepage read 81, 72, 85, 74, 85 and 83 across six deploys from August 23 to September 4. An earlier draft called the August 26 reading a regression from two data points. It was not, and any alarm built on a single drop would have fired falsely three days later. The corrected rule: never report a trend from two reads.
A confident false alarm. On August 26 the monitoring agent read a stale deploy identifier from the hosting API, concluded the pipeline had been down for three days, and escalated to the owner's phone — while the pipeline had deployed that morning. The failure mode of unattended monitoring is not only silence; it is confident wrongness from a single unverified source. The rule now encoded: confirm with a second read and an independent artifact before escalating.
The silent-failure hypothesis picked up a second data point. The study's working hypothesis is that hand-maintained state fails silently. On September 4 the social-media manifest — the file that tells the monthly scheduling job which photos and videos exist — was found listing 2 videos while 9 were available, and omitting whole categories of images committed weeks earlier. Nothing flagged it; TikTok and YouTube simply recycled the same two clips. The repair was the one the hypothesis prescribes: the manifest is now regenerated from disk by a deterministic script that refuses non-web-safe files, with a check mode for the daily audit. Publishing a video is now "add the file, commit."
What the owner says. "I'm very pleased with the work and progress we're doing with the SEO. I just need more of it, a lot more, for all seven divisions. I want to be number one on Google for all seven." That is the standing order for the next phase: volume across every division, one landing page per town, inside Google's trust envelope, with the farm results as proof the method works.
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.
It's the canonical form for every internal link and every sitemap entry on this site, and it isn't stylistic — Netlify serves a 301 redirect for the bare, slash-less form of a URL, and Search Console can end up dropping a page that it only ever reaches through a redirect chain instead of a direct 200 response. Every builder in the fleet writes links with the trailing slash from the start rather than relying on the redirect to clean it up after the fact.
LocalBusiness and FAQPage JSON-LD run across the site as part of the technical foundation described in the methodology above, and this very page carries BreadcrumbList and Article schema naming both authors — Claude and Randolph Scott Bell — plus a creditText line. Construction pages add Service schema on top. The reasoning is the same everywhere: structured data gives Google an explicit, machine-readable version of facts the page already states in prose, rather than asking a crawler to infer them.
Because lastmod is the field Google's crawler actually reads to decide when to re-crawl a URL — changefreq and priority are the fields most sitemaps ship and Google ignores. Every URL in the sitemap carries an accurate, per-page lastmod date rather than a static or guessed value, which is also why the sitemap gets touched and resubmitted the same day any page changes rather than on some fixed schedule.
It was 301 redirected into this hub rather than left standalone or abandoned. That single decision passed forward whatever domain history and links the old site had accumulated instead of starting from zero a second time, and it's part of the same consolidation that folded three fractured brand names — Bell Engineering, BeacCorp, and BEACCORP PM — into one identity at one domain.
“Build. Invest. Elevate.” is the enterprise's original tagline, describing the three things the business itself does across its divisions. “And Automate” is this case study's addition, naming the layer added on top over the last twelve months — the seven-workflow fleet that now writes, audits, designs, and resubmits the site's own presence daily. The word order is deliberate: automation was added after the business existed, in service of it, not the other way around.
Mostly through hard scope boundaries rather than a shared brain. Thin-Division Builder, for instance, is explicitly banned from touching the already-deep construction section — one workflow per territory, not seven workflows negotiating the same files. On top of that, two standing rules run through every bot: build to the current state of the art and explain why in the commit message, and never write a fact that isn't in the owner's verified dossier. The owner calls the ongoing tightening of those rules “refining the box.”
The drafting and code, yes — this page's own byline credits Claude as the author operating the platform. But the division of labor is specific: the human sets vision, taste, and priorities, and the AI translates that into architecture, code, and process, with every change shipping an explanation the owner can read in plain English. Design changes in particular go out as pull requests for the owner to review, not commits that land unseen.
Every bot in the fleet is required to read a single owner-verified fact file before writing anything — licenses, named projects, real numbers — so a page can't invent a credential or a price that isn't already confirmed. That's the same discipline this case study holds itself to: the numbers in it are sourced from Google Search Console, Google Business Profile, and this repository, not estimated.